[aprssig] Help with repeater beacon

[Randy Love]

We have 147.18MTC and 146.90PTK working here in SE Michigan.
I have them in my D710 working all the time.
The packets look like this:

;146.90PTK*020150z4238.68N/08317.87WrPHG7450 T100 R25m Net Th8PM Mg1stWe

;147.18MTC*111111z4237.83N/08302.69WrT100 USECA rptr (location approx)

The first is an object created and put out by UI-View32 from our EOC station
with the additional text formed manually.

The latter is put out via APRSIS32 from my home station.

73,
Randy
WF5X


On Thu, Feb 17, 2011 at 5:38 AM, Pentti Gronlund <pentti.gronlund at tut.fi>wrote:

> John Gorkos writes:
>
> > We're having some problems with the "TUNE" function of D710s and D72s in
> the
> > Atl area.
> >
> > I'm beaconing the following text from my Tx/Igate:
> > ;147.15NGA*111111z3414.21N/08409.60WrT143 R60m NET2000TU Cumming,GA
> > which seems to match, per character, what's on the localinfo.html page:
> > ;FFF.FFxyz*111111zDDMM.hhN/DDDMM.hhWrTnnn RXXm NETxxxxxx MTGxxxxx
> .........
>
> John,
>
> This works with D710's here:
>
> ;145.750-C*111111z6129.78N/02343.89Er1750 -060 R40k Tampere   OH3RNE
>
> Maybe Kenwood's implementation needs the 6th digit or the direction
> of offset, or both?
>
> Benjamin OH3BK
> --
>                Live Reports from the Taxman's Paradise!
>
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20110217/8265ad0e/attachment.html>