[aprssig] Comment String Display Viewer

[Robert Bruninga]

> Have added our Tidewater wide area coverage 2m voice repeater:
> http://www.findu.com/cgi-bin/find.cgi?call=146.970-R

Will show on 10x10 D7 as:

146.970-R
NoTn R50m
Net - 9PM 

Will show on 10x10x8 D700 as:

146.970-R
NoTn R50m
Net - 9PM 
WA4KXV 

Will show on 14x14x14 D710 as:

146.970-R
NoTn R50m Net
- 9PM WA4KXV 
Wide Coverage

If there is no tone, then I think it will be OK to eliminate
that field and you can move things left to display more maybe..

> and our local club meeting:
> http://www.findu.com/cgi-bin/find.cgi?call=VBARC

Will show on the D7 as:

VBARC
VBARC Mtg 
St Andrews

On the D700 as:

VBARC
VBARC Mtg 
St Andrews
Mtg1stTH

On the D710 as:

VBARC
VBARC Mtg St A
ndrews Mtg1stT
H-w4ug.com

Because of the longer lines on the D710, we have asked kenwood
to include an auto-wordwrap-on-space in their next version so
that things formatted for the D7 and D700 will also line up on
the D710.  Then this would show as:

VBARC
VBARC Mtg St
Andrews Mtg1st
TH-w4ug.com
 
> While trying to format the comments for each so they would 
> display correctly on the D700/D710/D7/HamHUD it occurred that 
> someone with some programming prowess might be able to 
> develop an extremely useful web based tool.
> 
> Perhaps something that would let you enter a hypothetical 
> comment line to see how it would display on the various 
> radios.  Thus facilitating the choice of an adequate 
> "universal" comment string...  I would be happy to
> host it if that was an issue.

Great idea!
Thanks

Bob, Wb4aPR
> 
> -----Original Message-----
> From: aprssig-bounces at lists.tapr.org 
> [mailto:aprssig-bounces at lists.tapr.org]
> On Behalf Of Bob Bruninga 
> Sent: Saturday, August 18, 2007 2:42 PM
> To: aprssig at lists.tapr.org
> Subject: [aprssig] Local Repeater Initiative Progress!
> 
> Progress on Voice Repeater Objects!
> 
> This is good news for APRS mobile travlers to see the local 
> recommended
> repeater frequency on the front panel of their radios no 
> matter where they
> travel.
> 
> Just checked the web page and we are up to about 204 voice 
> repeater objects
> from an initial 87 back when we started pushing this 
> initiative in January.
> The goal, is one local voice repeater frequency object for 
> every APRS New-N
> digipeater.  (Probably about 1000).
> 
> See web page:
> http://www.ew.usna.edu/~bruninga/localinfo.html
> 
> The breakdown down is as follows:
> 
> 147 MHz = 61
> 146 MHz = 62
> 145 MHz = 33
> 44X MHz = 48
> 
> Of course, only the KPC3+, UIDIGI-ROM and probably DIGI_NED 
> can do these
> objects, and that is OK.  That's most of the digipeaters in
the USA.
> 
> The format is very specific to be compatible with D7, D700 
> and HAMhud mobile
> display devices.  See the web page.  The new D710 can even 
> tune to these
> objects with the simple press of the TUNE button.
> 
> What we are trying to do is get human QSO's back into the
mobile radio
> experience.  When you get this FREQUENCY object added to the 
> digipeater in
> your area, then also monitor it and QSO those visiting APRS 
> mobiles as they
> pass through...
> 
> Also run Voice Alert to pick up any simplex QSO's.  If you 
> have a spare
> unused 2m rig in the shack, you can monitor Voice Alert 
> (144.39 with CTCSS
> 100).  But please do not connect this radio to packet.  We do 
> not want any
> home stations transmitting Voice Alert PL-100 packets 24/7 !!!
> 
> I'm visiting in Fredericksburg VA, and there is a signal 
> TXing VOice-Alert
> PL-100 all day, and I cannot get any response from him.  
> REMEMBER!  Voice
> Alert is an active CQ and it is inconsiderate to other
listeners to be
> banging out "CQ's" and not being there for a response.
> 
> WB4APR, Bob
> 
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
> 
> 
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
>