On Mon, Jun 4, 2012 at 10:26 AM, Chuck Henderson
<rpt2@chuck.midlandsnetworking.com> wrote:
APRSTT on my systems works for some call signs but not for some others.
Here is an example from the aprs.fi raw log.
Can anyone shed some light on why N9DOA shows up as "[Invalid object]"?
Is it a problem with aprs.fi or with the code in app_rpt, or with the way I setup rpt.conf?
Chuck
2012-06-04 14:05:58 UTC: WB9UUS-R>APRS,TCPIP*,qAC,CORE-2:=4030.48N/08859.28WrPHG9580/AllStar Node 27468
2012-06-04 14:06:08 UTC: WB9UUS-R>APSTAR,TCPIP*,qAC,CORE-2:;WB9UUS-12*140608z4030.38N708859.28WAAsterisk app_rpt user
2012-06-04 14:38:05 UTC: WB9UUS-R>APSTAR,TCPIP*,qAC,CORE-2:;N9DOA-12*143805z4030.28N908859.28WAAsterisk app_rpt user [Invalid object]
2012-06-04 15:00:22 UTC: WB9UUS-R>APSTAR,TCPIP*,qAC,CORE-2:;WB9UUS-12*150021z4030.38N908859.28WAAsterisk app_rpt user
2012-06-04 15:13:33 UTC: WB9UUS-R>APSTAR,TCPIP*,qAC,CORE-2:;N9DOA-12*151333z4030.28N708859.28WAAsterisk app_rpt user [Invalid object]
2012-06-04 15:52:32 UTC: WB9UUS-R>APSTAR,TCPIP*,qAC,CORE-2:;WB9UWA-12*155231z4030.18N708859.28WAAsterisk app_rpt user
2012-06-04 15:52:39 UTC: WB9UUS-R>APRS,TCPIP*,qAC,CORE-2:=4030.48N/08859.28WrPHG9580/AllStar Node 27468
The reason is that APRS object names must be padded on the right to be exactly 9 characters. WB9UUS-12 is 9 characters, but N9DOA-12 is only 8 --- you need to pad it out with spaces so the payload is:
;N9DOA-12 *151333z4030.28N708859.28WAAsterisk app_rpt user