Getting started with YAAC
|
Got it loaded in a Linux Mint computer. Using an MFJ-1274 TNC with RAM upgrade and latest (1.1.9) TNC-2 firmware. I went through the configuration wizard and set everything up, proper serial port, speed, etc. With the Serial_TNC port page, I hit the TEST PORT button and see the data coming from the TNC. The text is somewhat garbled and each line overwrites the previous line, making it hard to read. I see callsigns, site aliases, and seemingly random characters. But I get no data showing on the map. I check View > Raw Packets and nothing shows on the window.
Xastir shows all kinds of data, so I know the TNC and radio configurations should be right. Any ideas where to check? tnx es 73, Michael WA7SKG |
|
Changed the TNC to 8N1 on the COM port. Now the data shown in the Test Port button now shows the normal readable traffic seen in Xastir or minicom. But still nothing shows in the Raw Packet Sniffer, nor does anything show on the map.
toggle quoted message
Show quoted text
Still confused. Michael WA7SKG Michael WA7SKG wrote on 12/17/19 6:18 PM: Got it loaded in a Linux Mint computer. Using an MFJ-1274 TNC with RAM upgrade and latest (1.1.9) TNC-2 firmware. I went through the configuration wizard and set everything up, proper serial port, speed, etc. With the Serial_TNC port page, I hit the TEST PORT button and see the data coming from the TNC. The text is somewhat garbled and each line overwrites the previous line, making it hard to read. I see callsigns, site aliases, and seemingly random characters. But I get no data showing on the map. I check View > Raw Packets and nothing shows on the window. |
|
Yes, it is in KISS mode. The weird thing I don't understand is why do I see good information in the TEST PORT window, but nothing in the Raw Packet Sniffer?
toggle quoted message
Show quoted text
Michael WA7SKG Andrew P. wrote on 12/18/19 4:04 AM: Did you remember to put the TNC into KISS mode (either manually, or using YAAC's automatic command sending in the Serial_TNC port driver)? The weird characters were probably the ones with parity bit set while receiving packets in command mode. |
|
Oops. Actually, it wasn't all the way in KISS mode. At the cmd: prompt I got KISS ON. I missed the restart. I closed everything and accessed the TNC with minicom and gave (another, I know I did it previously) the RESTART command and started seeing strange things instead of the readable text I saw before. Fired up YAAC again and now the Raw Packet Sniffer is cranking out packets and stuff is starting to populate the map.
toggle quoted message
Show quoted text
Thanks for your help. This map is so much easier to navigate than Xastir. I can drag it around and zoom in and out with the scroll wheel. Michael WA7SKG Michael WA7SKG wrote on 12/18/19 7:58 AM: Yes, it is in KISS mode. The weird thing I don't understand is why do I see good information in the TEST PORT window, but nothing in the Raw Packet Sniffer? |
|
Well, I thought YAAC would do it, but it apparently did not. I initially selected TNC2:KISS ON\r\wRESTART\r but that does not seem to do anything. I can't find anything in the TAPR Command Reference to give multiple commands at one time.
toggle quoted message
Show quoted text
This leads me to another question, how do I get the TNC out of KISS mode when I am done with YAAC? In our area, we have increasing conventional non-APRS packet operation with BBSs, etc. I have to be in regular mode to use these, but it seems that now my TNC is in KISS mode, it is there forever. The TAPR Command Reference does not really say a lot about this, except that to manually restore from KISS mode, I must open the TNC, remove power, and remove the battery for several minutes, then start from scratch. Seems to me there must be a better way. I know with Xastir, the interface configuration can specify start-up and shut-down files with command sequences. Michael WA7SKG Andrew P. wrote on 12/18/19 9:04 AM: Re: being in KISS mode: that's why I recommend letting YAAC do it instead of doing manually. Tht way, you don't forget to issue one of the commands. :-) |
|
In my initial search, I only found the YAAC home page (). I was thinking there isn't a whole lot of detail here. After further searching, I accidentally found the help page () which led me to the serial page (). If I had found this page earlier, it may have saved me a lot of time and questions. Might I request you consider putting a link to this very helpful information on your home page?
toggle quoted message
Show quoted text
However, I find for whatever reason, the string KISS ON\r\wRESTART\r wasn't working. I tried KISSM\r and that worked! And, it reset from the KISS mode when exiting YAAC. I went back and tried the built-in KISS ON\r\wRESTART\r again, and now that works, too. I must have fat-fingered something along the line. Now it is running, I am getting data, it starts and stops properly, and I can move on trying to decipher what I am looking at. Thanks again for all your help, and especially with your patience with me. Michael WA7SKG Andrew P. wrote on 12/18/19 11:31 AM: YAAC should do it. The \r in the command string says to send a carriage return (Enter key if you hand-typed it to the TNC), and the \w says to wait for the next command prompt. Note that specifying the command sequence only does something if you save the configuration change; then it closes the port and reopens it according to the updated configuration. |
Michael WA7SKG