Keith VE7GDH: if you don't mind, What is the correct syntax for sending a message to another station. Thanks
--- In [email protected], "John Magda" <jjma...@...> wrote: > > Keith, > what an awesome lesson, and I am humbled. I have watched this process and > own a T2 and have watched it on the TNC/computer, but you summed it up in a > few sentences with real examples. Hats off to your teaching talent. > Thank you. > John - kb4yfk, Williamsburg,va (kb4yfk-14 mostly.) > > _____ > > From: [email protected] [mailto:[email protected]] On Behalf > Of Keith VE7GDH > Sent: Tuesday, July 14, 2009 11:35 AM > To: [email protected] > Subject: Re: [tracker2] Acknowledgement of message received. > > > > > > Adrian (callsign?) wrote... > > > Is there a way to test to see of the T2 is sending a acknowledgement > > to the message sender? Currently persons sending me messages say > > they never get an acknowledgement. > > Sure. Just power up another radio and a TNC and fire up a terminal > program and watch what your T2 is sending while another station sends a > message to the T2. If you studied the "APRS spec" so you understood the > correct syntax, you could even send a message from that TNC to the T2. > > :<callsign> :hello...{01 > > You might see something like this in your terminal program: > > :VE7GDH-2 :hello...{01 > > VE7GDH-2>APOT21,SSI [07/14/2009 08:23:43]: <UI>: > :VE7GDH :ack01 > > The first line was typed into a terminal program with the TNC in > converse mode and with the MON ON in the TNC so I could see what was > being received. The colon makes it a message. VE7GDH-2 was that station > it was sent to. It happens to be using a T2-135.The second line is the > ACK coming back from the other station via the digi SSI. It was sent to > VE7GDH which was the station that originated the message. > > If you don't have another TNC, just connect your T2 to a terminal > program and type "K" and hit enter to put it in converse mode and > proceed to send a message to yourself. Don't forge to turn MON ON so you > can see what if anything comes back. For it to work, you would need to > hear your message coming back from a digipeater... e.g. PATH WIDE2-1 > should hopefully get you to the nearest WIDEn-N digi. If he digi hears > your message, and if you hear it coming back from the digi, your T2 > should respond and try and send itself an ACK. It would look something > like the following. > > :VE7GDH-2 :hello me...{05 > > <Digi Echo> > VE7GDH-2>APOT21,SSI*::VE7GDH-2 :hello me...{05 > > From VE7GDH-2: hello me... > > <Digi Echo> > VE7GDH-2>APOT21,SSI*::VE7GDH-2 :ack05 > > It's too bad you didn't give your callsign (and the SSID in your T2) so > we could have looked to see what your T2 was sending... including > message ACKs if they made it to an IGate. > > Of course, you could just go to aprs.fi and look up the callsign in the > T2 and look at the raw data. Again, you would have to be making it to an > IGate for that to work. > > 73 es cul - Keith VE7GDH > -- > "I may be lost, but I know exactly where I am!" >
