Order Tray | Contact Us | Home | SIG Lists

[aprssig] Local Repeater Displays on Mobiles

Robert Bruninga bruninga at usna.edu
Wed Jan 24 01:52:04 UTC 2007


> Hi Bob, I suspect many people (like me) were sending
> the repeater objects from their client station....
> So now I've moved my repeater object to the UIDIGI
> node beacon text but there is a problem.
> 
> ;146.670- *111111z4612.74N/06320.46WrPHG8560 IRLP 2030
> 
> Shows up as a fixed station with the senders CALL.

ARGH!!  You are right.  OK, here is the receommended new format
that will work.  We will send the objects in 3rd party format so
that the PHG will work correctly.

BT }146.670->APOBJ:4612.74N/06320.46WrPHG8560 IRLP2030 VE1CRA

These will all be sent to the APOBJ TOCALL and we can use that
as the universal indicator of a permanent object.

> A second problem I see with having the object name as
> the repeater frequency instead of its callsign is the
> duplication problem where popular repeater frequencies
> will overwrite each other.

Ah, but only on FINDU and other global collectors of data.  The
purpose of these local objects is locally only.  And there would
never be two repeaters on the same frequency in the same area.
The fix is for FINDU and other collectors of global data to
recognize that the TOCALL of APOBJ specifies a permanent object
that should not be overwirtten by anyone except the original
sender.

Thanks for the feedback.  Ill fix the other docs.  Besides, this
format is slightly shorteer anyway...

Bob, WB4APR

> > 
> >> If you would take a look at W0GQ-R.  Did I do it
> correct?
> > 
> > ;W0GQ-R *192245z4158.56N/09140.24Wr146.745- PL open
> > 
> > Well, actually no.  But thanks for asking..  I see a
> few
> > improvements that can be made.
> > 
> > 1) Only the call shows on the map/D700 and not the
> freq.
> > 2) It does not include the PHG data for displaying
> its range
> > 3) It did not use the 111111z standard to make it
> permanent.
> > 
> > So here is how I recommend it:
> > 
> > ;146.745- *111111z4158.56N/09140.24WrPHGxxxx PL is
> open W0GQ-R
> > 
> > That fixes all the problems and by adding the word
> "is", then it
> > fits nicely on the display of a D7 or D700 mobile. 
> You fill in
> > the values for the xxxx PHG digits.  If you don't
> know, just
> > tell me the estimated Height above average terrain
> in the area,
> > the estimated power, any favored direction, and the
> estimated
> > antenna gain and Ill send you back the right values.
> > 
> > Doing it the way I recommended, it will show on a D7
> mobile
> > display as:
> > 
> > +------------+
> > | 146.745-   |
> > | PL is OPEN |
> > |  W0GQ-R    |
> > +------------+
> > 
> > And the PHG data would show as:
> > 
> > +-------------+
> > | 146.745-    |
> > | pw 9W h0040'|
> > | ant6dB omni |
> > +-------------+
> >  
> > If it was running 9 watts at 40 feet with a 6 dB
> omni antenna.
> > Most APRS clients would then plot a range circle
> around that
> > repeater to show it's useable range if requested.
> > 
> > Thanks
> > Bob, Wb4APR
> > 
> > 
> >> Thanks,
> 
> 
> 
>  
> ______________________________________________________________
> ______________________
> Expecting? Get great news right away with email Auto-Check. 
> Try the Yahoo! Mail Beta.
>
http://advision.webevents.yahoo.com/mailbeta/newmail_tools.html 
> 
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
> 





More information about the aprssig mailing list