Order Tray | Contact Us | Home | SIG Lists

[aprssig] aprssig Digest, Vol 69, Issue 6

Matt a projecthiker at yahoo.com
Sun Mar 7 21:33:20 UTC 2010


thought about a nextel version for mobile aprs. I have a 8350i blackberry nextel. iphone has an app why cant we. Also someone who can do echolink that app would be nice for blackberry.


----- Original Message ----
From: "aprssig-request at tapr.org" <aprssig-request at tapr.org>
To: aprssig at tapr.org
Sent: Sat, March 6, 2010 7:00:02 AM
Subject: aprssig Digest, Vol 69, Issue 6

Send aprssig mailing list submissions to
    aprssig at tapr.org

To subscribe or unsubscribe via the World Wide Web, visit
    https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
or, via email, send a message with subject or body 'help' to
    aprssig-request at tapr.org

You can reach the person managing the list at
    aprssig-owner at tapr.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of aprssig digest..."


Today's Topics:

   1. Mobile Success With  APRS Messenger PSK-63 on 30 Meters
      (Stephen H. Smith)
   2. Re: Mobile Success With APRS Messenger PSK-63 on 30 Meters
      (Chris Moulding)
   3. APRS Messenger on 30 Meters (John McHugh)
   4. Re: APRS satellite Launch 11 March CALL SIGN ?? (Steve Noskowicz)
   5. FW: APRS community resource (Robert Bruninga)
   6. Re: APRS satellite Launch 11 March CALL SIGN ?? (Robert Bruninga)
   7. BPQ32_4.10m_2010305 is available for download (Ron Stordahl N5IN)
   8. Re: APRS Messenger on 30 Meters (Stephen H. Smith)
   9. Re: APRS Messenger on 30 Meters (John McHugh)
  10. Re: Mobile Success With APRS Messenger PSK-63 on 30 Meters
      (Stephen H. Smith)
  11. Re: APRS Messenger on 30 Meters (Stephen H. Smith)
  12. Re: APRS Messenger on 30 Meters (Stephen H. Smith)


----------------------------------------------------------------------

Message: 1
Date: Fri, 05 Mar 2010 04:43:56 -0800
From: "Stephen H. Smith" <wa8lmf2 at aol.com>
Subject: [aprssig] Mobile Success With  APRS Messenger PSK-63 on 30
    Meters
To: TAPR APRS Mailing List <aprssig at tapr.org>
Message-ID: <4B90FC8C.3090104 at aol.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Thursday Feb 4th about 5:30 PM Pacific time (i.e. just before sunset 
local time) I successfully exchanged two APRS messages with  WB8SKP-2 in 
Kentucky from my mobile in Los Angeles, over a path of about 1700 miles 
(2700 KM).

I was running about 50 watts peak output from my FT-857 into a Yaesu 
ATAS-100 mini-screwdriver ant mounted on the trunk lid of my Jetta TDI, 
on 30 meters 10.149.700 Mhz.     The narrowband PSK mode is incredibly 
more effective than conventional AX25 FSK from a weak mobile!     One 
message acked after only one transmission. the other took three tries.

Next week on my trip to Las Vegas for the Wireless Communications Expo, 
I will using my big high-efficiency W6HIQ "Hi-Q" screwdriver instead.  
Hopefully more contacts if HF propagation cooperates!


------------------------------------------------------------------------

--

Stephen H. Smith    wa8lmf (at) aol.com
EchoLink Node:      WA8LMF  or 14400    [Think bottom of the 2M band]
Skype:        WA8LMF
Home Page:          http://wa8lmf.net

NEW!    Universal HF/VHF/UHF Antenna Mounting System
  http://wa8lmf.net/mobile/UniversalAntMountSystem.htm

"APRS 101"  Explanation of APRS Path Selection & Digipeating
  http://wa8lmf.net/DigiPaths

Updated "Rev H" APRS            http://wa8lmf.net/aprs
Symbols Set for UI-View,
UIpoint and APRSplus:





------------------------------

Message: 2
Date: Fri, 05 Mar 2010 13:03:52 +0000
From: Chris Moulding <chrism at crosscountrywireless.net>
Subject: Re: [aprssig] Mobile Success With APRS Messenger PSK-63 on 30
    Meters
To: TAPR APRS Mailing List <aprssig at tapr.org>
Message-ID: <4B910138.2060200 at crosscountrywireless.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

I'm working on the GPS mobile tracker version of APRS Messenger over the 
weekend. All being well it should be ready for your trip.

Tx PTT will be on the existing com port and the GPS input will be any 
other serial or USB port. GPS input will be 4800 bd NMEA looking for the 
$GPRMC string.

I'll post information on APRSSIG when it's ready.

73,

Chris, G4HYG

Chris Moulding
Cross Country Wireless (2009) Ltd
7 Thirlmere Grove, Bolton, Lancs, BL4 0QB, UK
Tel/fax: +44(0)1204 410626
Mobile:  +44(0)7752 391908
Website: http://www.crosscountrywireless.net
Company number 6780346 registered in England and Wales  



Stephen H. Smith wrote:
> Thursday Feb 4th about 5:30 PM Pacific time (i.e. just before sunset 
> local time) I successfully exchanged two APRS messages with  WB8SKP-2 
> in Kentucky from my mobile in Los Angeles, over a path of about 1700 
> miles (2700 KM).
>
> I was running about 50 watts peak output from my FT-857 into a Yaesu 
> ATAS-100 mini-screwdriver ant mounted on the trunk lid of my Jetta 
> TDI, on 30 meters 10.149.700 Mhz.     The narrowband PSK mode is 
> incredibly more effective than conventional AX25 FSK from a weak 
> mobile!     One message acked after only one transmission. the other 
> took three tries.
>
> Next week on my trip to Las Vegas for the Wireless Communications 
> Expo, I will using my big high-efficiency W6HIQ "Hi-Q" screwdriver 
> instead.  Hopefully more contacts if HF propagation cooperates!
>
>
> ------------------------------------------------------------------------
>
> -- 
>
> Stephen H. Smith    wa8lmf (at) aol.com
> EchoLink Node:      WA8LMF  or 14400    [Think bottom of the 2M band]
> Skype:        WA8LMF
> Home Page:          http://wa8lmf.net
>
> NEW!    Universal HF/VHF/UHF Antenna Mounting System
>  http://wa8lmf.net/mobile/UniversalAntMountSystem.htm
>
> "APRS 101"  Explanation of APRS Path Selection & Digipeating
>  http://wa8lmf.net/DigiPaths
>
> Updated "Rev H" APRS            http://wa8lmf.net/aprs
> Symbols Set for UI-View,
> UIpoint and APRSplus:
>
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>



------------------------------

Message: 3
Date: Fri, 05 Mar 2010 09:11:11 -0500
From: John McHugh <johnk.mchugh at bellsouth.net>
Subject: [aprssig] APRS Messenger on 30 Meters
To: TAPR APRS Mailing List <aprssig at tapr.org>
Message-ID: <4B9110FF.6090409 at bellsouth.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed



I was just looking at this program. It looks great and is a good idea to 
allow existing TNCs to be used for regular APRS functions.

My setup is a FT-840 into a KAM and using UI-View for APRS.
The audio from the 840 comes from the backpanel into the KAM and tx 
audio and PTT from the KAM goes into the mike connector on the front.
Now to use APRS Messenger it looks like I need rx audio into my sound 
card (I guess a Y connector) but how do I get tx audio and ptt back to 
the 840?
The way I see it APRS Messenger and the KAM-UIview are not related 
except that you use 2100Hz as the PSK tone
Is it possible to run APRS and Messenger at the same time? What am I 
missing?

Thanks,

John

-- 
John Mc Hugh, K4AG
Coordinator for Amateur Radio  
National Hurricane Center, WX4NHC
Home page:- http://www.wx4nhc.org





------------------------------

Message: 4
Date: Fri, 5 Mar 2010 08:26:33 -0800 (PST)
From: Steve Noskowicz <noskosteve at yahoo.com>
Subject: Re: [aprssig] APRS satellite Launch 11 March CALL SIGN ??
To: bruninga at usna.edu, TAPR APRS Mailing List <aprssig at tapr.org>
Message-ID: <413616.58670.qm at web112601.mail.gq1.yahoo.com>
Content-Type: text/plain; charset=iso-8859-1




What is the APRS call sign?


I posted this for the local club and someone wants to watch it on the net.

Steve


> East Coast APRS Satellite Launch 11
> March!
> 
> You will be able to see it too over most of the
> mid-atlantic.? I
> don't see a launch time or any other info yet.? Here
> is what I
> have received:
> -----------------------------------------------------
> 
> A sounding rocket with amateur satellite operating on
> 144.39 MHZ
> APRS will rise to 100 miles or so for an 8 minute
> mission.? The
> rocket (I think) is the Hall 12.067.
> 
> The payload is called SOCEM/ADAMASat.? There is a
> computer
> program and GUI to interface to your PC so you can grab
> the
> telemetry live.? It is on:
> http://ssl.engr.uky.edu/adamasat_free_gui.exe
> 
> It's a one shot deal, so I'm gonna have a backup TNC and
> HYPERTERM collecting everything.???
> ??? 
> ADAMASat is the Antenna Deployment and Mono-filament
> Actuator
> Satellite. It's a 2U CubeSat designed by Kentucky Space as
> part
> of SOCEM, the Sub-Orbital CubeSat Experimental Mission.
> ADAMASat, which is scheduled to launch on Hall 12.067 out
> of
> Wallops Flight Facility on 11 March, will fly in space for
> roughly 8 minutes performing an engineering experiment and
> transmitting data down to Earth via APRS packets. 
> 
> More information on ADAMASat is available at
> http://ssl.engr.uky.edu/suborbital/adamasat Kentucky
> Space is
> hereby releasing to the AMSAT-NA community the ADAMASat
> FREE
> GUI, a free 32-bit Windows binary for amateur radio
> operators in
> the Eastern United States who are interested in tracking
> ADAMASat on its launch day. The GUI is a standalone
> application
> and upon opening it on his/her computer, the HAM will be
> greeted
> with a popup window which explains the steps required to
> track
> the payload. 
> 
> All that is needed is a Windows machine, a radio and TNC
> which
> can receive on 144.390 MHz, a serial or USB cable, and a
> suitable location. The GUI parses the APRS packets as they
> are
> received, graphing temperatures on-board the payload and
> reporting status of the mission in real-time. It also
> includes
> instructions on e-mailing the packet log to Kentucky Space
> to
> aid in post-processing, and a built-in aggregator for the
> official ADAMASat Twitter RSS feed. 
> 
> Disclaimer: Kentucky Space provides the GUI "as is"
> without
> warranties of any kind, and shall not incur any liability
> for
> any damages connected to the use of the GUI.
> ??? ??? 
> 
> 
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
> 


      



------------------------------

Message: 5
Date: Fri, 5 Mar 2010 12:21:34 -0500
From: "Robert Bruninga" <bruninga at usna.edu>
Subject: [aprssig] FW: APRS community resource
To: "'TAPR APRS Mailing List'" <aprssig at tapr.org>
Message-ID: <D47B5100D4FF4BB0B219F44FF8A809EF at ewlab.usna.edu>
Content-Type: text/plain;    charset="us-ascii"

A local club denied a member's requrest to install APRS on the
club tower...

Reasons given in unanimously voting down the proposal were.
1) We know where we are, APRS provides no value to us.
2) Our town is small, we do not need GPS tracking for emergency
comms

To which I sent back the comment, that generally, APRS is
installed in an area as a local community resource for mobles
and visitors and travelers and is not necessarily of immediate
value to own members.  You do it for the greater ham
community... But again, it points out that most non-APRS hams
see APRS only for tracking, and not as a community resource.  So
here is one of my replies...

-------
I think the reason I promote the info distribution aspect of
APRS is because I generally believe that people are not
interested in things that do not provide them personal benefit
or advantage.  This is not a selfish thing, it is just human
nature.

The point being that everyone that wants to be tracked is
already doing it on APRS.  And after 18 years of APRS, those
that do, do.  Those that don't never will.  They'd have to live
on mars not to be aware of how APRS can let others track them.
But the benefit to the driver of a tracking TX device is just
not there.

On the otherhand.  If people realize that APRS lets them receive
and display information to them about everything going on around
them in ham radio, then their inner ham-radio-read-the-mail
instinct gets interested.  Now there is something they can see
the benefit of every time they get in the mobile.

The growth curve of APRS as a tracking system peaked 10 years
ago and will not go higher because of all the "I dont care if
people know where I am" attitude that prevails in the other 95%
of ham radio operators.  But of that other 95%, almost -none- of
them are aware of what APRS can do for them individually as a
receive system.

And unlike promoting the tracking side, (anyone can go look at
APRS.FI), there is no easy way for the  have-nots to see what
they are missing with respect to the receive side of APRS.
Unless they see it there on the front panel of their radio, they
do not know it exists.

Even for me, tracking myself has little appeal.  Its there,
done.  Nice to have.  But what I thurst for is seeing what
others are doing, and getting info about ALL activities and
local resources in ham radio while I am mobile (the only place I
have time to play radio).  BUT, a large majority of APRS users
who are into APRS only for tracking, are also oblivious to
receiving and display in their mobile, so even they do not see
the benefit of putting out local sources of info for those
-receiving- mobiles in need of local info.  So unless info is
being put-out there, then there is nothing to see...  Hence the
LOCAL INFO initiative: www.aprs.org/localinfo.html

Hope that helps explain my approach.

>   Hams who are not familiair with APRS only see maps
>   and think it
>   is a vehicle tracking system showing mobiles on
>   maps.  And that
>   (a transmit function from the mobile) is just *not
>   at all* what
>   it was designed for .  No.  The purpose of APRS is
>   the opposite.
>   The purpose of APRS was and always has been, the
>   *reception* by
>   the mobile operator, commuter or ham radio traveler
>   of
>   immediate, relevant, local FRONT-PANEL information
>   to drivers
>   and mobile operators of all amateur radio activities
>   in range.
>   That is why you now see APRS FRONT PANEL Displays
>   (not maps) on
>   most new Radios and HT's.
>
>   Think of it as the single-channel information
>   resource (144.39)
>   anywhere in NorthAmerica that alerts mobile hams to
>   every ham
>   activity, and resource, net or meeting in the local
>   area, and
>   even traffic jams and accidents.
>
>   I have spent the majority of the last decade trying
>   to overcome
>   this missunderstood outward view of APRS by
>   non-users, and
>   trying to show how this incorrect vehicle-tracking
>   view of APRS
>   is of little benefit to ham radio.  The real value
>   of APRS is in
>   the local real-time front-panel distribution of
>   immediate local
>   information it provides TO users while mobile in an
>   area (with
>   no other knowledge of local ham radio resources).
>
>   As APRS mobiles drive anywhere in America, they
>   expect to see on
>   the front panel of their APRS radios all the
>   information on such
>   things as local repeater frequency, tones, offset,
>   net times,
>   meeting dates, hamfests, announcements and
>   bulletins.  This has
>   nothing to do with maps, or GPS or vehicle
>   tracking.  The maps
>   are just the dull outward view as seen by non-APRS
>   users.
>   Please see the web page www.aprs.org/localinfo.html
>
>   And since I am an annual vacationer in Lewes, I
>   enjoy seeing all
>   this information when I drive in (if it is
>   available).  With
>   this background, I can add a little to some common
>   missunderstandings often voiced at local clubs:
>
>   *  There is no value-added to the local club..
>
>   This is true (in a way), because locals are already
>   aware of all
>   local info.  The value of APRS is to visitors and
>   commmuters
>   needing local info in real time. On the other hand,
>   members can
>   consider that the value to the local club comes when
>   they drive
>   their mobiles out of their local area and hope to
>   see the local
>   information in OTHER areas they drive through.  They
>   hope other
>   clubs have an APRS presence on 144.39.  In
>   otherwords, clubs do
>   not put up APRS network support necessarily for
>   their own local
>   benefit, but to serve the greater national community
>   of hams as
>   they travel.  And not just for APRS, but to alert
>   travelers when
>   they are in range of the local voice repeater and
>   how to tune it
>   in.  The new Kenwood APRS radios will even tune to
>   the local
>   voice repeater with the press of a single button
>   when it is in
>   range of an APRS beacon from a repeater site.  Far
>   better than
>   looking through 10,000 listings in a repeater
>   guide.  Is great
>   for meeting new faces and visitors.
>
>   * Our town is small and does not need APRS Vehicle
>   Tracking
>
>   See above.  APRS is not a vehicle tracking system. 
>   It is the
>   opposite.  It serves out real-time text, info,
>   messages and
>   visual information to mobiles.  This is of great
>   value during
>   emergencies and drills when much information needs
>   to get out to
>   individual mobiles wihtout having to pass the
>   traffic by voice.
>   Oh, and of course, it allows GLOBAL text messaging
>   to anyone
>   with an HT or radio.
>
>   * The noisy APRS tone bursts are anoying...
>
>   One does not listen to 144.39 data by ear except
>   with CTCSS 100
>   set.  That way, there is nothing to hear on the APRS
>   channel.
>   However, knowing that every APRS mobile in North
>   America is
>   simultaneously listening by ear on that channel with
>   CTCSS100
>   means that ANY APRS mobile in range can be contacted
>   anytime,
>   anywhere by just making a direct voice call with PL
>   100 and then
>   QSY'ing to a simplex frequency.  In this way it is
>   even better
>   than 52, because you *know* he is listening, and you
>   *know* he
>   is on this frequency always.
>
>   * APRS is expensive...
>
>   Yes, there  are many new APRS radios with APRS front
>   panel
>   displays and it is good to see the manufacturers
>   catching up to
>   this fascinating new way of distributing local info
>   to mobile
>   operators.  But innexpensive kits are available to
>   add APRS
>   displays to any mobile using any old spare radio. 
>   The
>   Byonics.COM TinyTrack-4 with LCD display is well
>   under $100 and
>   makes a great club project...  An APRS community
>   node is very
>   simple, just a low power radio and a TNC in many
>   cases (hooked
>   to a nice high antenna).
>
>   Anyway, please help us spread the word of what APRS
>   is and what
>   it is not.  Another good article was in september
>   2008 QST
>   describing what APRS is (and it is not vehicle
>   tracking)...
>
>   I send this not in support of any particular
>   location of APRS in
>   your community, that is a completely local issue,
>   but just to
>   support the general concept and understanding of
>   APRS.  The
>   maximum advantage of APRS as a resource is when it
>   covers
>   generally the same footprint as a local repeateer or
>   club.  This
>   then provides everyone in that range, the common
>   information
>   displays relevant to that area.  And alerts them to
>   the central
>   voice repeater where everyone hangs out.
>
>   Bob Bruninga
>   WB4APR




------------------------------

Message: 6
Date: Fri, 5 Mar 2010 13:36:02 -0500
From: "Robert Bruninga" <bruninga at usna.edu>
Subject: Re: [aprssig] APRS satellite Launch 11 March CALL SIGN ??
To: "'Steve Noskowicz'" <noskosteve at yahoo.com>,    "'TAPR APRS Mailing
    List'" <aprssig at tapr.org>
Message-ID: <0DD840D0BE2F42C597AE56634796318C at ewlab.usna.edu>
Content-Type: text/plain;    charset="iso-8859-1"

Steve,
I found a link on the web page:
http://ssl.engr.uky.edu/suborbital/socem

Tha says that the packets will be sent under the call sign,
KJ4HVJ. 

Hope that helps
Bob, WB4aPR

> -----Original Message-----
> From: Steve Noskowicz [mailto:noskosteve at yahoo.com] 
> Sent: Friday, March 05, 2010 11:27 AM
> To: bruninga at usna.edu; TAPR APRS Mailing List
> Subject: Re: [aprssig] APRS satellite Launch 11 March CALL
SIGN ??
> 
> 
> 
> 
> What is the APRS call sign?
> 
> 
> I posted this for the local club and someone wants to watch 
> it on the net.
> 
> Steve
> 
> 
> > East Coast APRS Satellite Launch 11
> > March!
> > 
> > You will be able to see it too over most of the
> > mid-atlantic.? I
> > don't see a launch time or any other info yet.? Here
> > is what I
> > have received:
> > -----------------------------------------------------
> > 
> > A sounding rocket with amateur satellite operating on
> > 144.39 MHZ
> > APRS will rise to 100 miles or so for an 8 minute
> > mission.? The
> > rocket (I think) is the Hall 12.067.
> > 
> > The payload is called SOCEM/ADAMASat.? There is a
> > computer
> > program and GUI to interface to your PC so you can grab
> > the
> > telemetry live.? It is on:
> > http://ssl.engr.uky.edu/adamasat_free_gui.exe
> > 
> > It's a one shot deal, so I'm gonna have a backup TNC and
> > HYPERTERM collecting everything.???
> > ??? 
> > ADAMASat is the Antenna Deployment and Mono-filament
> > Actuator
> > Satellite. It's a 2U CubeSat designed by Kentucky Space as
> > part
> > of SOCEM, the Sub-Orbital CubeSat Experimental Mission.
> > ADAMASat, which is scheduled to launch on Hall 12.067 out
> > of
> > Wallops Flight Facility on 11 March, will fly in space for
> > roughly 8 minutes performing an engineering experiment and
> > transmitting data down to Earth via APRS packets. 
> > 
> > More information on ADAMASat is available at
> > http://ssl.engr.uky.edu/suborbital/adamasat Kentucky
> > Space is
> > hereby releasing to the AMSAT-NA community the ADAMASat
> > FREE
> > GUI, a free 32-bit Windows binary for amateur radio
> > operators in
> > the Eastern United States who are interested in tracking
> > ADAMASat on its launch day. The GUI is a standalone
> > application
> > and upon opening it on his/her computer, the HAM will be
> > greeted
> > with a popup window which explains the steps required to
> > track
> > the payload. 
> > 
> > All that is needed is a Windows machine, a radio and TNC
> > which
> > can receive on 144.390 MHz, a serial or USB cable, and a
> > suitable location. The GUI parses the APRS packets as they
> > are
> > received, graphing temperatures on-board the payload and
> > reporting status of the mission in real-time. It also
> > includes
> > instructions on e-mailing the packet log to Kentucky Space
> > to
> > aid in post-processing, and a built-in aggregator for the
> > official ADAMASat Twitter RSS feed. 
> > 
> > Disclaimer: Kentucky Space provides the GUI "as is"
> > without
> > warranties of any kind, and shall not incur any liability
> > for
> > any damages connected to the use of the GUI.
> > ??? ??? 
> > 
> > 
> > _______________________________________________
> > aprssig mailing list
> > aprssig at tapr.org
> > https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
> > 
> 
> 
>      
> 




------------------------------

Message: 7
Date: Fri, 5 Mar 2010 11:32:22 -0800 (PST)
From: Ron Stordahl N5IN <ronn5in-aprssig at yahoo.com>
Subject: [aprssig] BPQ32_4.10m_2010305 is available for download
To: TAPR APRS Mailing List <aprssig at tapr.org>
Message-ID: <592342.93241.qm at web63506.mail.re1.yahoo.com>
Content-Type: text/plain; charset=us-ascii

APRSSig users of BPQ32 are notified that BPQ32_4.10m_2010305 is now available for download at http://groups.yahoo.com/group/BPQ32/

Ron Stordahl, N5IN




------------------------------

Message: 8
Date: Fri, 05 Mar 2010 11:51:31 -0800
From: "Stephen H. Smith" <wa8lmf2 at aol.com>
Subject: Re: [aprssig] APRS Messenger on 30 Meters
To: TAPR APRS Mailing List <aprssig at tapr.org>
Message-ID: <4B9160C3.5090201 at aol.com>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"

On 3/5/2010 6:11 AM, John McHugh wrote:
>
>
> I was just looking at this program. It looks great and is a good idea 
> to allow existing TNCs to be used for regular APRS functions.
>
> My setup is a FT-840 into a KAM and using UI-View for APRS.
> The audio from the 840 comes from the backpanel into the KAM and tx 
> audio and PTT from the KAM goes into the mike connector on the front.
> Now to use APRS Messenger it looks like I need rx audio into my sound 
> card (I guess a Y connector) but how do I get tx audio and ptt back to 
> the 840?
> The way I see it APRS Messenger and the KAM-UIview are not related 
> except that you use 2100Hz as the PSK tone
> Is it possible to run APRS and Messenger at the same time? What am I 
> missing?
>


YES!      At least you can receive on both at the same time.    At RF, 
the PSK63 carrier is 300 Hz higher than the higher of the two FSK tones 
used by "classic" FSK AX25.   (The actual RF freqs for the classic FSK 
are  10.149.200 and 10.149.400 while the PSK63 frequency is 
10.149.700.)  Thus the receiver can be tuned so that all the tones are 
in the passband, and audible at the same time, in a manner similar to 
receiving multiple stations simultaneously within the receiver passband 
on PSK31.


Assumng operation alongside  standard 1600/1800 Hz "KAM tones" for AX25 
FSK APRS:

      Use the 2100 Hz version of APRS Messenger
      and set radio to      10.147.600 MHz   USB.

            -or-

      Use the 1300 Hz version of APRS Messenger
      and set radio to      10.151.000   LSB

On transmit, "Y" the audio outputs of the sound card and TNC together 
with a pair of resistors.   Diode "OR" the PTT lines of the sound card 
and TNC together so that either device can key the transmitter.  If you 
really want to get fancy, take the PTT from the sound card, invert it 
and feed it into the external carrier detect of the KAM so that PTT on 
the sound card will prevent the KAM from trying to transmit.




APRS Messenger can pass received posits to UIview for display along side 
the ones from the KAM.

1)     Seach for [SERVER] in UIview32.ini .     Change the line just 
below to read "  PORT=14580 "   This sets UIview's "Local Server" to 
port 14580.

2)     In UIview's "Setup, APRS Server Setup", check the box "Enable 
Local Server".   Exit UIview and restart the program.

3)     In APRS Messenger, replace "rotate.aprs2.net" with "localhost" in 
the "APRS-IS Server" box.  Click "Connect to APRS Server".


APRS Messenger is hard wired to use port 14580 for IP connections.  
These changes cause APRS Messenger to connect to the local port 14580 in 
UIview, rather than port 14580 of a "real" server out on the Internet.

o    Any posits received on PSK63 will appear on your UIview map.

o    PKS63 stations will show in UIview's "Stations Heard" list.

o    PSK63 posits will be passed to the Internet by UIview, just like 
the ones from the KAM,  if UIview is operating as an igate logged into a 
"real" APRS server..


------------------------------------------------------------------------

--

Stephen H. Smith    wa8lmf (at) aol.com
EchoLink Node:      WA8LMF  or 14400    [Think bottom of the 2M band]
Skype:        WA8LMF
Home Page:          http://wa8lmf.net

NEW!    Universal HF/VHF/UHF Antenna Mounting System
  http://wa8lmf.net/mobile/UniversalAntMountSystem.htm

"APRS 101"  Explanation of APRS Path Selection & Digipeating
  http://wa8lmf.net/DigiPaths

Updated "Rev H" APRS            http://wa8lmf.net/aprs
Symbols Set for UI-View,
UIpoint and APRSplus:



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tapr.org/pipermail/aprssig/attachments/20100305/4045ddc2/attachment-0001.htm>

------------------------------

Message: 9
Date: Fri, 05 Mar 2010 15:14:54 -0500
From: John McHugh <johnk.mchugh at bellsouth.net>
Subject: Re: [aprssig] APRS Messenger on 30 Meters
To: TAPR APRS Mailing List <aprssig at tapr.org>
Message-ID: <4B91663E.5090606 at bellsouth.net>
Content-Type: text/plain; charset="us-ascii"; Format="flowed"

Stephen,

Thanks for the info. That's what I had figured. Maybe I'll look at my 
other radio because it has a PKT socket on the back panel, then I can 
input thru' that for the KAM and thru' the mike for the APRS messenger

I was monitoring since about 7pm last night until now and saw the following

WB2LMV-63>APSK63:=4145.20N\07422.27W&
KB1TCE-9>APSK63:=4402.92N/06906.20W&Owl's Head, Maine FN54kb
NH7C-63>APSK63:=3904.83N\07709.22W-Team Wamuran QRP
KB2HSH>APSK63:Buffalo, NY USA FN02ox
WB8SKP-2>APSK63:=3643.91N\08807.88W- / v 2.34 EM56
KD4MOJ-63>APSK63:=3027.27N\08420.80W- APRS Messenger 2.35/ HalfW Sloper 30w

John, K4AG
Miami


Stephen H. Smith wrote:

> On 3/5/2010 6:11 AM, John McHugh wrote:
>
>>
>> The way I see it APRS Messenger and the KAM-UIview are not related 
>> except that you use 2100Hz as the PSK tone
>> Is it possible to run APRS and Messenger at the same time? What am I 
>> missing?
>>
>
>
> YES!      At least you can receive on both at the same time.    At RF, 
> the PSK63 carrier is 300 Hz higher than the higher of the two FSK 
> tones used by "classic" FSK AX25.   (The actual RF freqs for the 
> classic FSK are  10.149.200 and 10.149.400 while the PSK63 frequency 
> is 10.149.700.)  Thus the receiver can be tuned so that all the tones 
> are in the passband, and audible at the same time, in a manner similar 
> to receiving multiple stations simultaneously within the receiver 
> passband on PSK31.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tapr.org/pipermail/aprssig/attachments/20100305/0df1c1ec/attachment-0001.htm>

------------------------------

Message: 10
Date: Fri, 05 Mar 2010 12:54:08 -0800
From: "Stephen H. Smith" <wa8lmf2 at aol.com>
Subject: Re: [aprssig] Mobile Success With APRS Messenger PSK-63 on 30
    Meters
To: TAPR APRS Mailing List <aprssig at tapr.org>
Message-ID: <4B916F70.4080303 at aol.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

On 3/5/2010 5:03 AM, Chris Moulding wrote:
> I'm working on the GPS mobile tracker version of APRS Messenger over 
> the weekend. All being well it should be ready for your trip.
>
> Tx PTT will be on the existing com port and the GPS input will be any 
> other serial or USB port. GPS input will be 4800 bd NMEA looking for 
> the $GPRMC string.
>
> I'll post information on APRSSIG when it's ready.
>
> 73,
>
> Chris, G4HYG
>


1)     I am using a VOX-keyed soundcard interface so the PTT com port 
isn't an issue to me.  However, TXD is,  since some VOX devices are 
"slow on the draw". To guarantee that they are fully keyed before the 
data starts, it would be good to allow 50-100 milliseconds or so of tone 
before any data starts.

Details of my homebrew tone-keyed interface (which keys in 5 
milliseconds) are here on my website:

<http://wa8lmf.net/ham/tonekeyer.htm>

A good commercial alternative that is also tone-keyed, and needs no 
serial port control, is the TigerTronics SignaLink at:

<http://tigertronics.com>

The "USB" version of this device is actually an entire second card 
dedicated to ham purposes in a box at the end of a USB cable.  It 
"automagically" shows up as "Generic USB Sound Device" when plugged into 
a USB port on any  system running Win 2K or higher.  No driver installs 
required at all!


2)     I use the "XPort" com port splitter to share my GPS data with 
several programs at once.   If you maintain the COM1 through COM16 range 
of choices for the GPS input as well as for the current  TNC/PTT choice, 
there should be no problems.


3)     Would it be possible to cause all the radio button choices on the 
startup screen to be saved  into an .ini file?   It would be very 
convenient to have these settings be "sticky".  Especially now that one 
has to check the correct tone each time.  (And I, at least, have to 
choose a non-default sound card each time since my system has three of 
them, and will soon also be having to choose the GPS port each time ).

In the mobile environment, one is constant starting up and shutting 
down.  I use the UIview Scheduler to automatically start up several 
related programs each time I start UIview. However, currently I have to 
start Messenger separately and manually, since it's start-up requires 
operator interaction each time.


4)      Yet another tone freq request (!!).     I use a TigerTronics 
TigerTrak APRS tracker on classic FSK AX25 HF. The TigerTrak uses the 
oddball tone pair of 1100 and 1300 for 300 baud HF mode.   I would like 
to be able to beacon with both the Tigertrak on FSK, and APRS Messenger 
on PSK63 with the same setup.  This would require a tone frequency of 
1600 Hz for Messenger, if running on USB.

Do the 700 Hz and 1500 Hz tones have any special significance?  In 
Europe perhaps???  Could they be dropped in the interest of 
simplicity?    I would also think that labels to the right of whatever 
tones remain might be useful to minimize user confusion. Something like:


O   1300 Hz - Radio on  10.151.00 LSB for KAM

O   1600 Hz - Radio on  10.148.10 USB for TigerTrak

O   1800 Hz - Radio on  10.151.50 LSB for AGWpe Free

O   2100 Hz - Radio on  10.147.60 USB for KAM


I realize this assumes everyone is on 30 meters -- perhaps there could 
be a "Hide/Show HInts" check box.......


------------------------------------------------------------------------

--

Stephen H. Smith    wa8lmf (at) aol.com
EchoLink Node:      WA8LMF  or 14400    [Think bottom of the 2M band]
Skype:        WA8LMF
Home Page:          http://wa8lmf.net

NEW!    Universal HF/VHF/UHF Antenna Mounting System
  http://wa8lmf.net/mobile/UniversalAntMountSystem.htm

"APRS 101"  Explanation of APRS Path Selection & Digipeating
  http://wa8lmf.net/DigiPaths

Updated "Rev H" APRS            http://wa8lmf.net/aprs
Symbols Set for UI-View,
UIpoint and APRSplus:







------------------------------

Message: 11
Date: Fri, 05 Mar 2010 12:56:27 -0800
From: "Stephen H. Smith" <wa8lmf2 at aol.com>
Subject: Re: [aprssig] APRS Messenger on 30 Meters
To: TAPR APRS Mailing List <aprssig at tapr.org>
Message-ID: <4B916FFB.4040709 at aol.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

On 3/5/2010 12:14 PM, John McHugh wrote:
> Stephen,
>
> Thanks for the info. That's what I had figured. Maybe I'll look at my 
> other radio because it has a PKT socket on the back panel, then I can 
> input thru' that for the KAM and thru' the mike for the APRS messenger
>
> I was monitoring since about 7pm last night until now and saw the 
> following
>
> WB2LMV-63>APSK63:=4145.20N\07422.27W&
> KB1TCE-9>APSK63:=4402.92N/06906.20W&Owl's Head, Maine FN54kb
> NH7C-63>APSK63:=3904.83N\07709.22W-Team Wamuran QRP
> KB2HSH>APSK63:Buffalo, NY USA FN02ox
> WB8SKP-2>APSK63:=3643.91N\08807.88W- / v 2.34 EM56
> KD4MOJ-63>APSK63:=3027.27N\08420.80W- APRS Messenger 2.35/ HalfW 
> Sloper 30w
>
> John, K4AG
> Miami


If you had been monioring about a hour and a half earlier, you probably 
would have seen me actually exchange two-way messaging with WB8SKP-2 
from my mobile in Los Angeles.





------------------------------

Message: 12
Date: Fri, 05 Mar 2010 12:58:42 -0800
From: "Stephen H. Smith" <wa8lmf2 at aol.com>
Subject: Re: [aprssig] APRS Messenger on 30 Meters
To: TAPR APRS Mailing List <aprssig at tapr.org>
Message-ID: <4B917082.4090605 at aol.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

On 3/5/2010 12:56 PM, Stephen H. Smith wrote:
> On 3/5/2010 12:14 PM, John McHugh wrote:
>> Stephen,
>>
>> Thanks for the info. That's what I had figured. Maybe I'll look at my 
>> other radio because it has a PKT socket on the back panel, then I can 
>> input thru' that for the KAM and thru' the mike for the APRS messenger
>>
>> I was monitoring since about 7pm last night until now and saw the 
>> following
>>
>> WB2LMV-63>APSK63:=4145.20N\07422.27W&
>> KB1TCE-9>APSK63:=4402.92N/06906.20W&Owl's Head, Maine FN54kb
>> NH7C-63>APSK63:=3904.83N\07709.22W-Team Wamuran QRP
>> KB2HSH>APSK63:Buffalo, NY USA FN02ox
>> WB8SKP-2>APSK63:=3643.91N\08807.88W- / v 2.34 EM56
>> KD4MOJ-63>APSK63:=3027.27N\08420.80W- APRS Messenger 2.35/ HalfW 
>> Sloper 30w
>>
>> John, K4AG
>> Miami
>
>
> If you had been monioring about a hour and a half earlier, you 
> probably would have seen me actually exchange two-way messaging with 
> WB8SKP-2 from my mobile in Los Angeles.
>
>



OOPS!  Forgot you are on Eastern time; I am on Pacific here in Los 
Angeles!    You would have had to be listening around 8:30 Eastern to 
have heard my "QSO".



------------------------------

_______________________________________________
aprssig mailing list
aprssig at tapr.org
https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig


End of aprssig Digest, Vol 69, Issue 6
**************************************



      



More information about the aprssig mailing list