On Thu, Jul 16, 2009 at 8:39 PM, Adrian Miura<[email protected]> wrote:
> I also set COMMENT to : Auto reply from KD5HTZ-9
>
> So if you want send a message you should get an auto reply.
>From the T2 manual:
COMMENT <string>
Sets beacon text / comment string, up to 64 characters.
STATUS <0‐255>
Status packets are sent every n transmissions, or if set to 0, status text is
sent as part of the position packet.
Setting the COMMENT only configures the unit to send a message in the
comment section of a packet, or as a separate status packet, depending
upon the STATUS value.
I'm not trying to be a pain, but do you understand what a message ACK is?
See below:
I sent a message to SPLSTD, and get an ack back from the OT2, the OT2
responds to my INFO command request, and my UI-View station responds
back to the OT2 with an ack.
2009-07-15 17:15:05 MDT: VE6SRV>APRS,WIDE1-1*,WIDE2-2::SPLSTD :cmd info{AF}af
2009-07-15 17:15:09 MDT: SPLSTD>APOT21,WIDE2-2::VE6SRV :ackAF}af
2009-07-15 17:15:12 MDT: SPLSTD>APOT21,EDMNTN*,WIDE2-1::VE6SRV
:TEMP:40C VOLT:13.88 RX:14954 FCS:2287 DIGI:41218 CFG1{ag
2009-07-15 17:15:12 MDT: VE6SRV>APRS,WIDE1-1*,WIDE2-2,::SPLSTD :ackag
In APRS, only messages ever get acks... nothing else.
With the messages that you are sending to Keith, we can see acks
coming back via the APRS-IS... the question is, are you seeing Keith's
ack on RF locally?
James
VE6SRV
