Re: [Xastir] Tinytrak TNC not opening interface
Eric, This document goes back to the beginning of KISS around 1986/87 http://www.ka9q.net/papers/kiss.html Ray vk2tv On 9/2/21 8:25 am, Eric Chamberlain wrote: Thanks Tom. I'm not sure I seen any written specification for KISS, so that helps. Also, nice signature. Pipes are always fitting for hams. Sent: Monday, February 08, 2021 at 4:16 PM From: "Tom Russo" To: "Xastir - APRS client software discussion" Subject: Re: [Xastir] Tinytrak TNC not opening interface This is still not KISS, it's regular ASCII APRS packets. It needs to be a Serial TNC and not a Serial KISS TNC interface in Xastir. If it still hangs trying to open the interface, though, the issue is not with the data but with the serial port configuration --- either something's amiss with permissions, settings, or the port name. On Mon, Feb 08, 2021 at 10:14:28PM +0100, we recorded a bogon-computron collision of the flavor, containing: Here's the new packet data from putty with the updated TT3 configuration: KC3OBB-1>APT314,WIDE1-1,WIDE2-1:!4015.89N/07946.07W>198/000/TT3 ROCKET|!&#
Re: [Xastir] Tinytrak TNC not opening interface
It’s been a while since I ran xastir on the Mac, but I rarely have serial port permissions problems on the Mac. Sorry if I’m repeating someone else, but make sure that there is no start or stop scripts on that port in xastir. -Jason > On Feb 8, 2021, at 3:49 PM, Eric Chamberlain wrote: > > I will admit, I missed that AMODE setting when I was reading those commands. > Yeah its probably TEXT. Now that I know about the 4555 permission and the > use of root permissions and the dialout group, I went back over to the RPi > where I actually want to run this. I set it to Serial TNC and everything > works now. I see packets coming in the view-incoming data window. And the > transmitter is showing up on my map along with its vector. For the > startup/shutdown scripts, I specified empty files since it doesn't seem to > have commands necessary to get going. I appreciate everyone's help today. > I'll keep looking at why my mac isn't opening the port correctly, but I won't > bother you until I resolve it. Hopefull this thread will nonetheless be > useful for other hams getting started on APRS. > > The backstory to this project is for my kids to run the hound dog afield and > have a RPi running APRS to track it. That's why you see the KC3OBB, my son. > I'm AB3OO. My daughter is working on hers so she can get a callsign on the > TT3. I chose these devices in particular for their light portability, > despite their less common usage among the ham community. If you ever see > either of these callsigns on APRS from 15642, you'll know we're chasing some > game. Thanks again everyone. > 73 > Eric AB3OO > > > > > Sent: Monday, February 08, 2021 at 4:31 PM > From: "Brett Friermood" > To: "Xastir - APRS client software discussion" > Subject: Re: [Xastir] Tinytrak TNC not opening interface > Eric, > > If you haven't seen it yet, the quick start guide for the TinyTrak4 is > available here: > https://www.byonics.com/downloads/TinyTrak4%20Quick%20Start%20Guide%20v0.7.pdf > This as well as the full manual have a lot more information on > configuration, but here is a list of steps to switch it over to KISS mode > quickly: > > - Configure Putty for the proper port and 19200 baud > - Cycle the power on the TT4 and watch for "Press ESC 3 times to enter TT4 > Options Menu" > - Press the escape key 3 times quickly and the TNC will enter menu mode > - Type "AMODE" and it will output the currently configured operating mode. > (Most likely "TEXT" judging by your posted output) > - Type "AMODE KISS" to change the operating mode > > Brett KQ9N > > >> On Mon, Feb 8, 2021 at 3:25 PM Eric Chamberlain >> wrote: >> >> Thanks Tom. I'm not sure I seen any written specification for KISS, so >> that helps. Also, nice signature. Pipes are always fitting for hams. >> >> >> >> >> Sent: Monday, February 08, 2021 at 4:16 PM >> From: "Tom Russo" >> To: "Xastir - APRS client software discussion" >> Subject: Re: [Xastir] Tinytrak TNC not opening interface >> This is still not KISS, it's regular ASCII APRS packets. It needs to be >> a Serial TNC and not a Serial KISS TNC interface in Xastir. >> >> If it still hangs trying to open the interface, though, the issue is not >> with >> the data but with the serial port configuration --- either something's >> amiss >> with permissions, settings, or the port name. >> >> On Mon, Feb 08, 2021 at 10:14:28PM +0100, we recorded a bogon-computron >> collision of the flavor, containing: >>> Here's the new packet data from putty with the updated TT3 configuration: >>> >>> KC3OBB-1>APT314,WIDE1-1,WIDE2-1:!4015.89N/07946.07W>198/000/TT3 >> ROCKET|!
Re: [Xastir] Tinytrak TNC not opening interface
I will admit, I missed that AMODE setting when I was reading those commands. Yeah its probably TEXT. Now that I know about the 4555 permission and the use of root permissions and the dialout group, I went back over to the RPi where I actually want to run this. I set it to Serial TNC and everything works now. I see packets coming in the view-incoming data window. And the transmitter is showing up on my map along with its vector. For the startup/shutdown scripts, I specified empty files since it doesn't seem to have commands necessary to get going. I appreciate everyone's help today. I'll keep looking at why my mac isn't opening the port correctly, but I won't bother you until I resolve it. Hopefull this thread will nonetheless be useful for other hams getting started on APRS. The backstory to this project is for my kids to run the hound dog afield and have a RPi running APRS to track it. That's why you see the KC3OBB, my son. I'm AB3OO. My daughter is working on hers so she can get a callsign on the TT3. I chose these devices in particular for their light portability, despite their less common usage among the ham community. If you ever see either of these callsigns on APRS from 15642, you'll know we're chasing some game. Thanks again everyone. 73 Eric AB3OO Sent: Monday, February 08, 2021 at 4:31 PM From: "Brett Friermood" To: "Xastir - APRS client software discussion" Subject: Re: [Xastir] Tinytrak TNC not opening interface Eric, If you haven't seen it yet, the quick start guide for the TinyTrak4 is available here: https://www.byonics.com/downloads/TinyTrak4%20Quick%20Start%20Guide%20v0.7.pdf This as well as the full manual have a lot more information on configuration, but here is a list of steps to switch it over to KISS mode quickly: - Configure Putty for the proper port and 19200 baud - Cycle the power on the TT4 and watch for "Press ESC 3 times to enter TT4 Options Menu" - Press the escape key 3 times quickly and the TNC will enter menu mode - Type "AMODE" and it will output the currently configured operating mode. (Most likely "TEXT" judging by your posted output) - Type "AMODE KISS" to change the operating mode Brett KQ9N On Mon, Feb 8, 2021 at 3:25 PM Eric Chamberlain wrote: > Thanks Tom. I'm not sure I seen any written specification for KISS, so > that helps. Also, nice signature. Pipes are always fitting for hams. > > > > > Sent: Monday, February 08, 2021 at 4:16 PM > From: "Tom Russo" > To: "Xastir - APRS client software discussion" > Subject: Re: [Xastir] Tinytrak TNC not opening interface > This is still not KISS, it's regular ASCII APRS packets. It needs to be > a Serial TNC and not a Serial KISS TNC interface in Xastir. > > If it still hangs trying to open the interface, though, the issue is not > with > the data but with the serial port configuration --- either something's > amiss > with permissions, settings, or the port name. > > On Mon, Feb 08, 2021 at 10:14:28PM +0100, we recorded a bogon-computron > collision of the flavor, containing: > > Here's the new packet data from putty with the updated TT3 configuration: > > > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:!4015.89N/07946.07W>198/000/TT3 > ROCKET|!
Re: [Xastir] Tinytrak TNC not opening interface
Eric, If you haven't seen it yet, the quick start guide for the TinyTrak4 is available here: https://www.byonics.com/downloads/TinyTrak4%20Quick%20Start%20Guide%20v0.7.pdf This as well as the full manual have a lot more information on configuration, but here is a list of steps to switch it over to KISS mode quickly: - Configure Putty for the proper port and 19200 baud - Cycle the power on the TT4 and watch for "Press ESC 3 times to enter TT4 Options Menu" - Press the escape key 3 times quickly and the TNC will enter menu mode - Type "AMODE" and it will output the currently configured operating mode. (Most likely "TEXT" judging by your posted output) - Type "AMODE KISS" to change the operating mode Brett KQ9N On Mon, Feb 8, 2021 at 3:25 PM Eric Chamberlain wrote: > Thanks Tom. I'm not sure I seen any written specification for KISS, so > that helps. Also, nice signature. Pipes are always fitting for hams. > > > > > Sent: Monday, February 08, 2021 at 4:16 PM > From: "Tom Russo" > To: "Xastir - APRS client software discussion" > Subject: Re: [Xastir] Tinytrak TNC not opening interface > This is still not KISS, it's regular ASCII APRS packets. It needs to be > a Serial TNC and not a Serial KISS TNC interface in Xastir. > > If it still hangs trying to open the interface, though, the issue is not > with > the data but with the serial port configuration --- either something's > amiss > with permissions, settings, or the port name. > > On Mon, Feb 08, 2021 at 10:14:28PM +0100, we recorded a bogon-computron > collision of the flavor, containing: > > Here's the new packet data from putty with the updated TT3 configuration: > > > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:!4015.89N/07946.07W>198/000/TT3 > ROCKET|!
Re: [Xastir] Tinytrak TNC not opening interface
Thanks Tom. I'm not sure I seen any written specification for KISS, so that helps. Also, nice signature. Pipes are always fitting for hams. Sent: Monday, February 08, 2021 at 4:16 PM From: "Tom Russo" To: "Xastir - APRS client software discussion" Subject: Re: [Xastir] Tinytrak TNC not opening interface This is still not KISS, it's regular ASCII APRS packets. It needs to be a Serial TNC and not a Serial KISS TNC interface in Xastir. If it still hangs trying to open the interface, though, the issue is not with the data but with the serial port configuration --- either something's amiss with permissions, settings, or the port name. On Mon, Feb 08, 2021 at 10:14:28PM +0100, we recorded a bogon-computron collision of the flavor, containing: > Here's the new packet data from putty with the updated TT3 configuration: > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:!4015.89N/07946.07W>198/000/TT3 > ROCKET|!
Re: [Xastir] Tinytrak TNC not opening interface
This is still not KISS, it's regular ASCII APRS packets. It needs to be a Serial TNC and not a Serial KISS TNC interface in Xastir. If it still hangs trying to open the interface, though, the issue is not with the data but with the serial port configuration --- either something's amiss with permissions, settings, or the port name. On Mon, Feb 08, 2021 at 10:14:28PM +0100, we recorded a bogon-computron collision of the flavor, containing: > Here's the new packet data from putty with the updated TT3 configuration: > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:!4015.89N/07946.07W>198/000/TT3 >
Re: [Xastir] Tinytrak TNC not opening interface
Here's the new packet data from putty with the updated TT3 configuration: KC3OBB-1>APT314,WIDE1-1,WIDE2-1:!4015.89N/07946.07W>198/000/TT3
Re: [Xastir] Tinytrak TNC not opening interface
No. Once that has been applied (assuming the executable is in that spot anyway, change the path to match yours) and the binary is owned by root, Xastir will change the effective user ID to "root" at the point it needs to open a port, then will go back to the user you started Xastir from immediately after, so it's reasonably safe security-wise. What it will do is tell you whether there's a permission issue or user/group ownership issue with that port. Xastir should be able to open the port in that instance. On Mon, Feb 8, 2021 at 1:06 PM Eric Chamberlain wrote: > > Curt, are you asking if I'm able to execute the /usr/local/bin/xastir when > 4755 has been applied? > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Tinytrak TNC not opening interface
Curt, are you asking if I'm able to execute the /usr/local/bin/xastir when 4755 has been applied? ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Tinytrak TNC not opening interface
As a check about the ownership/permissions on the port, you might do a "chmod 4755 /usr/local/bin/xastir" as root to set the SUID bit in the executable. If Xastir works for you then, it's an ownership/group/permissions issue with that port. We need to set that bit on Linux in order to open an AX.25 networking port. That's its main use. On Mon, Feb 8, 2021 at 12:36 PM Eric Chamberlain wrote: > > It's sending NMEA because I accidentally set that on the transmitter, I > vaguely remember that being set on the list of things. So that's my bad. > But yeah it still hangs on the open(). I added NOBLOCK to the flags to force > it to come back, it returns with an errno 2, no such file or directory. It > appears to open the port for reading, ie it doesn't send a fail when it > attempts to read, but instead throws an errno 35, resource temporarily > unavailable, when attempting to write to the port. I did a chown root:wheel > to the xastir executable so that it would match the /dev/tty.usbserial-1430, > but that didn't work either. > > I'll go grab the transmitter and fix that in the meanwhile. > > From: "Curt Mills" > > Since it's not KISS you can _try_ the Serial TNC interface with it, > but I don't know what the command-set for the TNC4 looks like so don't > know whether Xastir would be able to talk to it. If it's TAPR TNC-2 > compatible to some degree, then it might work. > > On Mon, Feb 8, 2021 at 11:21 AM Curt Mills wrote: > > > > If putty sees that, then it's not KISS. That looks like normal TNC > > ASCII output, not KISS. > > > > On Mon, Feb 8, 2021 at 11:16 AM Eric Chamberlain > > wrote: > > > > > > The code hangs at this line, so the mutex is opened. > > > port_data[port].channel = open(port_data[port].device_name, > > > O_RDWR|O_NOCTTY); > > > > > > Jason, I think its in KISS. Regarding the readable payload with binary > > > garbage, I'm getting it. Here's some of what putty sees, so I think the > > > baud rate is good too. > > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:>MT-Omega v1.47 > > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,190857,A,4015.8900,N,07946.0796,W,000,057,080221,,*03/TT3 > > > ROCKET|!"#c'6|!w!x! > > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,190958,A,4015.8927,N,07946.0753,W,000,169,080221,,*0D|!##c':|!w:Q! > > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,191059,A,4015.8942,N,07946.0762,W,000,169,080221,,*05|!$#c'<|!wGY! > > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,191159,A,4015.8922,N,07946.0766,W,000,169,080221,,*06|!%#c'>|!w5]! > > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,191300,A,4015.8922,N,07946.0776,W,000,169,080221,,*09/TT3 > > >
Re: [Xastir] Tinytrak TNC not opening interface
It's sending NMEA because I accidentally set that on the transmitter, I vaguely remember that being set on the list of things. So that's my bad. But yeah it still hangs on the open(). I added NOBLOCK to the flags to force it to come back, it returns with an errno 2, no such file or directory. It appears to open the port for reading, ie it doesn't send a fail when it attempts to read, but instead throws an errno 35, resource temporarily unavailable, when attempting to write to the port. I did a chown root:wheel to the xastir executable so that it would match the /dev/tty.usbserial-1430, but that didn't work either. I'll go grab the transmitter and fix that in the meanwhile. From: "Curt Mills" Since it's not KISS you can _try_ the Serial TNC interface with it, but I don't know what the command-set for the TNC4 looks like so don't know whether Xastir would be able to talk to it. If it's TAPR TNC-2 compatible to some degree, then it might work. On Mon, Feb 8, 2021 at 11:21 AM Curt Mills wrote: > > If putty sees that, then it's not KISS. That looks like normal TNC > ASCII output, not KISS. > > On Mon, Feb 8, 2021 at 11:16 AM Eric Chamberlain > wrote: > > > > The code hangs at this line, so the mutex is opened. > > port_data[port].channel = open(port_data[port].device_name, > > O_RDWR|O_NOCTTY); > > > > Jason, I think its in KISS. Regarding the readable payload with binary > > garbage, I'm getting it. Here's some of what putty sees, so I think the > > baud rate is good too. > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:>MT-Omega v1.47 > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,190857,A,4015.8900,N,07946.0796,W,000,057,080221,,*03/TT3 > > ROCKET|!"#c'6|!w!x! > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,190958,A,4015.8927,N,07946.0753,W,000,169,080221,,*0D|!##c':|!w:Q! > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,191059,A,4015.8942,N,07946.0762,W,000,169,080221,,*05|!$#c'<|!wGY! > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,191159,A,4015.8922,N,07946.0766,W,000,169,080221,,*06|!%#c'>|!w5]! > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,191300,A,4015.8922,N,07946.0776,W,000,169,080221,,*09/TT3 > >
Re: [Xastir] Tinytrak TNC not opening interface
Jason, I think its in KISS. Regarding the readable payload with binary garbage, I'm getting it. Here's some of what putty sees, so I think the baud rate is good too. KC3OBB-1>APT314,WIDE1-1,WIDE2-1:>MT-Omega v1.47 KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,190857,A,4015.8900,N,07946.0796,W,000,057,080221,,*03/TT3 ROCKET|!"#c'6|!w!x! That's definitely NOT KISS and that's not "binary gargage" as that's almost all plain text. True binary data coming from APRS in KISS form would look like for six received packets (each question mark represent a non-ASCII binary value): -- ?h@`??l???|??l???b@??d@??200Ah Solar Generator???n`??l???`??l??b@??d@??`2.hl >/'"3y}|!e%e']|!wA:!|3??@@`??l???b?l??@@??@082002z3755.50N/12 P ?dj?`??l???d??l???b@@??=3658.94N/12200.92W-Cap in Santa Cruzt Diablo/A=003624=003624 -- As you can see, most of the data received in KISS form is binary but there is some human readible text in there (GPS coordinates, beacon string data, etc). In your example, you're non-KISS output, you should read it as: KC3OBB-1 - sender's callsign and SSID Strange, this callsign isn't found in aprs.fi - maybe you're not on 144.390Mhz? APT314 - sending packets from a TinyTrack III - http://aprs.org/aprs11/tocalls.txt WIDE1-1,WIDE2-1 - sending to both forms of APRS packet distributions MT-Omega v1.47 - Seems this TNC is sending out it's model and version number Next packet $GPRMC - This seems like an unexpanded GPS location The next oath does include the packet's position, etc. including an identifier of "TT3 ROCKET" meaning it's a TinyTrack tracker The binary data behind that string might be some sort of embedded telemetry data. You'll need to make sure you have a valid script in your Xastir install to enable KISS on your TNC and restart it go be active: https://xastir.org/index.php/XASTIR_Manual#Serial_KISS_TNC --David KI6ZHD ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Tinytrak TNC not opening interface
Since it's not KISS you can _try_ the Serial TNC interface with it, but I don't know what the command-set for the TNC4 looks like so don't know whether Xastir would be able to talk to it. If it's TAPR TNC-2 compatible to some degree, then it might work. On Mon, Feb 8, 2021 at 11:21 AM Curt Mills wrote: > > If putty sees that, then it's not KISS. That looks like normal TNC > ASCII output, not KISS. > > On Mon, Feb 8, 2021 at 11:16 AM Eric Chamberlain > wrote: > > > > The code hangs at this line, so the mutex is opened. > > port_data[port].channel = open(port_data[port].device_name, > > O_RDWR|O_NOCTTY); > > > > Jason, I think its in KISS. Regarding the readable payload with binary > > garbage, I'm getting it. Here's some of what putty sees, so I think the > > baud rate is good too. > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:>MT-Omega v1.47 > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,190857,A,4015.8900,N,07946.0796,W,000,057,080221,,*03/TT3 > > ROCKET|!"#c'6|!w!x! > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,190958,A,4015.8927,N,07946.0753,W,000,169,080221,,*0D|!##c':|!w:Q! > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,191059,A,4015.8942,N,07946.0762,W,000,169,080221,,*05|!$#c'<|!wGY! > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,191159,A,4015.8922,N,07946.0766,W,000,169,080221,,*06|!%#c'>|!w5]! > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,191300,A,4015.8922,N,07946.0776,W,000,169,080221,,*09/TT3 > >
Re: [Xastir] Tinytrak TNC not opening interface
On Mon, Feb 08, 2021 at 11:21:15AM -0800, we recorded a bogon-computron collision of the flavor, containing: > If putty sees that, then it's not KISS. That looks like normal TNC > ASCII output, not KISS. Not kiss, and not even regular APRS posits --- those are the goofy old-school NMEA type APRS packets. But regardless, this should be a Serial TNC in Xastr, not a Serial KISS TNC interface. Why the code is hanging on the port open is quite another question, and I can't help there as I have no experience with Xastir on Macs. Making sure that the baud rate and other port parameters in Xastir match those that putty is using is the only thing I could suggest. If there's a way to make the TT4 actually speak KISS on that serial port it would probably be better than using this old-school NMEA format, though. > On Mon, Feb 8, 2021 at 11:16 AM Eric Chamberlain > wrote: > > > > The code hangs at this line, so the mutex is opened. > > port_data[port].channel = open(port_data[port].device_name, > > O_RDWR|O_NOCTTY); > > > > Jason, I think its in KISS. Regarding the readable payload with binary > > garbage, I'm getting it. Here's some of what putty sees, so I think the > > baud rate is good too. > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:>MT-Omega v1.47 > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,190857,A,4015.8900,N,07946.0796,W,000,057,080221,,*03/TT3 > > ROCKET|!"#c'6|!w!x! > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,190958,A,4015.8927,N,07946.0753,W,000,169,080221,,*0D|!##c':|!w:Q! > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,191059,A,4015.8942,N,07946.0762,W,000,169,080221,,*05|!$#c'<|!wGY! > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,191159,A,4015.8922,N,07946.0766,W,000,169,080221,,*06|!%#c'>|!w5]! > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,191300,A,4015.8922,N,07946.0776,W,000,169,080221,,*09/TT3 > >
Re: [Xastir] Tinytrak TNC not opening interface
If putty sees that, then it's not KISS. That looks like normal TNC ASCII output, not KISS. On Mon, Feb 8, 2021 at 11:16 AM Eric Chamberlain wrote: > > The code hangs at this line, so the mutex is opened. > port_data[port].channel = open(port_data[port].device_name, O_RDWR|O_NOCTTY); > > Jason, I think its in KISS. Regarding the readable payload with binary > garbage, I'm getting it. Here's some of what putty sees, so I think the baud > rate is good too. > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:>MT-Omega v1.47 > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,190857,A,4015.8900,N,07946.0796,W,000,057,080221,,*03/TT3 > ROCKET|!"#c'6|!w!x! > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,190958,A,4015.8927,N,07946.0753,W,000,169,080221,,*0D|!##c':|!w:Q! > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,191059,A,4015.8942,N,07946.0762,W,000,169,080221,,*05|!$#c'<|!wGY! > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,191159,A,4015.8922,N,07946.0766,W,000,169,080221,,*06|!%#c'>|!w5]! > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,191300,A,4015.8922,N,07946.0776,W,000,169,080221,,*09/TT3 >
Re: [Xastir] Tinytrak TNC not opening interface
The code hangs at this line, so the mutex is opened. port_data[port].channel = open(port_data[port].device_name, O_RDWR|O_NOCTTY); Jason, I think its in KISS. Regarding the readable payload with binary garbage, I'm getting it. Here's some of what putty sees, so I think the baud rate is good too. KC3OBB-1>APT314,WIDE1-1,WIDE2-1:>MT-Omega v1.47 KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,190857,A,4015.8900,N,07946.0796,W,000,057,080221,,*03/TT3 ROCKET|!"#c'6|!w!x! KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,190958,A,4015.8927,N,07946.0753,W,000,169,080221,,*0D|!##c':|!w:Q! KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,191059,A,4015.8942,N,07946.0762,W,000,169,080221,,*05|!$#c'<|!wGY! KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,191159,A,4015.8922,N,07946.0766,W,000,169,080221,,*06|!%#c'>|!w5]! KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,191300,A,4015.8922,N,07946.0776,W,000,169,080221,,*09/TT3
Re: [Xastir] Tinytrak TNC not opening interface
Are you sure it’s in KISS mode? That would equate to a bunch of binary garbage for the packet headers plus some readable text that’s the payload. And maybe triple check the baud rate? -Jason > On Feb 8, 2021, at 6:30 AM, Eric Chamberlain wrote: > > That certainly prevents the port from blocking. The interface in xastir > returns as 'up' but it doesn't appear to be reading packets off the TNC in > the view-incoming data window. Looking in putty it still shows the incoming > packets. So its not quite fixed yet. > > > > > From: "Jason KG4WSV" > > Try the /dev/cu.whatever device special file. > > It’s been a few years but when I hit the same problem (well, Kermit not > putty) switching to cu did the trick. > > -Jason > >> On Feb 7, 2021, at 8:44 PM, Eric Chamberlain >> wrote: >> >> I've been trying to configure an interface to read the tinytrak4 TNC, which >> is supposed to operate as KISS according to their docs. When I run PuTTY on >> the /dev/tty.usbserial-1430 port I can see packets coming in from a test >> transmitter. I close putty and open xastir so the port isn't blocking. When >> I go to start the TNC interface, in mac it hangs without messages in the >> terminal window. On the putty it doesn't hang but there's nothing. There are >> never incoming packets from the view data window. Unfortunately, Byonics say >> they don't know much about xastir. I've tried this both on my mac and my >> raspberry. The cable setup works for programming and PuTTY, so I don't think >> its that or drivers. I think it comes down to settings. Is there anything I >> can try? >> ___ >> Xastir mailing list >> Xastir@lists.xastir.org >> http://xastir.org/mailman/listinfo/xastir > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir[http://xastir.org/mailman/listinfo/xastir] > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Tinytrak TNC not opening interface
That code looks familiar for some reason... Look at xastir/src/util.c On Mon, Feb 8, 2021 at 8:28 AM Eric Chamberlain wrote: > > Tracing the hang further, it gets to the begin_critical_section mutex call, > so it's blocking on that, but it's an extern reference in util.h. Do you > happen to know what library that is sourced from? > > > > > From: "Eric Chamberlain" > > I went ahead and added my userid to the wheel group but no effect. Also I ran > debug level 3. It gave me the Opening a Serial KISS device output before > hanging. I added some output to the source and remade the file to output the > other serial variables, here's what came out. > > Port Available 1 > Opening a Serial KISS TNC device > Dev Type 10 > Dev baud rate 19200 > Dev style 0 > > I'm going to look at what comes next after this add_device call. > > > From: "Curt Mills" > > The permissions are R/W for user/group/other, so I don't think you > need to add yourself to the wheel group for this. Perhaps one of the > OSX guys can comment on that though. I don't run OSX. > > On Mon, Feb 8, 2021 at 7:30 AM Eric Chamberlain > wrote: > > > > I haven't set debug yet, but I wanted to respond with the ls -l output > > first. > > crw-rw-rw- 1 root wheel 18, 4 Feb 8 10:26 /dev/tty.usbserial-1430 > > > > I'm logged in as user ericchamberlain and groups looks like: > > staff access_bpf everyone localaccounts _appserverusr admin _appserveradm > > _lpadmin _appstore _lpoperator _developer _analyticsusers > > com.apple.access_ftp com.apple.access_screensharing com.apple.access_ssh > > com.apple.access_remote_ae com.apple.sharepoint.group.1 > > > > So yeah, I'm not a member of wheel group. > > > > > > > > > > From: "Curt Mills" > > > > File -> Configure -> Change Debug Level can change it while it's > > running. You need to start Xastir from a console/xterm/etc in order to > > see them. > > > > See the file DEBUG_LEVELS for info on which ones to try. > > > > The sources are the result of a LOT of people over the years, starting > > with Frank Gianandrea who initially wrote it. Thank them. ;-) > > > > The port to use if you're using a TNC4 in KISS mode is the "Serial > > KISS TNC" interface. I've used that with H/W full-blown TNC's and with > > my TNC-X. > > > > More than likely it's a group/permissions problem with the interface. > > Do an "ls -l" against the port you're using and report back with the > > string for it including owner/group/permissions. > > > > Also report back what "groups" shows when logged-in as the user you're > > starting Xastir as. BTW: Don't run Xastir as root. > > > > > > On Mon, Feb 8, 2021 at 6:58 AM Eric Chamberlain > > wrote: > > > > > > Hey Curt. I've seen your comments in the source code, thanks for your > > > work. I've used both serial TNC interface and serial KISS TNC interface. > > > Based on the /dev/cu comment, I guess it hangs because of blocking(?). I > > > don't believe there is a permission on that port. I can apply a generic > > > username (guest) in putty with the autologin username without problem. > > > > > > Is there a debugging #define in the source I can build against to get > > > more information while the interface is opening? > > > > > > > > > > > > > > > From: "Curt Mills" > > > > > > Which type of interface are you using in Xastir? > > > > > > Did you add your username to the dialout group? > > > > > > What are the permissions on the port you're trying to use? > > > > > > On Mon, Feb 8, 2021 at 4:31 AM Eric Chamberlain > > > wrote: > > > > > > > > That certainly prevents the port from blocking. The interface in xastir > > > > returns as 'up' but it doesn't appear to be reading packets off the TNC > > > > in the view-incoming data window. Looking in putty it still shows the > > > > incoming packets. So its not quite fixed yet. > > > > > > > > > > > > > > > > > > > > From: "Jason KG4WSV" > > > > > > > > Try the /dev/cu.whatever device special file. > > > > > > > > It’s been a few years but when I hit the same problem (well, Kermit not > > > > putty) switching to cu did the trick. > > > > > > > > -Jason > > > > > > > > > On Feb 7, 2021, at 8:44 PM, Eric Chamberlain > > > > > wrote: > > > > > > > > > > I've been trying to configure an interface to read the tinytrak4 > > > > > TNC, which is supposed to operate as KISS according to their docs. > > > > > When I run PuTTY on the /dev/tty.usbserial-1430 port I can see > > > > > packets coming in from a test transmitter. I close putty and open > > > > > xastir so the port isn't blocking. When I go to start the TNC > > > > > interface, in mac it hangs without messages in the terminal window. > > > > > On the putty it doesn't hang but there's nothing. There are never > > > > > incoming packets from the view data window. Unfortunately, Byonics > > > > > say they don't know much about xastir. I've tried this both on my mac > > > > > and my raspberry. The cable setup works for programming and PuTTY, so > > > > > I don't think
Re: [Xastir] Tinytrak TNC not opening interface
Tracing the hang further, it gets to the begin_critical_section mutex call, so it's blocking on that, but it's an extern reference in util.h. Do you happen to know what library that is sourced from? From: "Eric Chamberlain" I went ahead and added my userid to the wheel group but no effect. Also I ran debug level 3. It gave me the Opening a Serial KISS device output before hanging. I added some output to the source and remade the file to output the other serial variables, here's what came out. Port Available 1 Opening a Serial KISS TNC device Dev Type 10 Dev baud rate 19200 Dev style 0 I'm going to look at what comes next after this add_device call. From: "Curt Mills" The permissions are R/W for user/group/other, so I don't think you need to add yourself to the wheel group for this. Perhaps one of the OSX guys can comment on that though. I don't run OSX. On Mon, Feb 8, 2021 at 7:30 AM Eric Chamberlain wrote: > > I haven't set debug yet, but I wanted to respond with the ls -l output first. > crw-rw-rw- 1 root wheel 18, 4 Feb 8 10:26 /dev/tty.usbserial-1430 > > I'm logged in as user ericchamberlain and groups looks like: > staff access_bpf everyone localaccounts _appserverusr admin _appserveradm > _lpadmin _appstore _lpoperator _developer _analyticsusers > com.apple.access_ftp com.apple.access_screensharing com.apple.access_ssh > com.apple.access_remote_ae com.apple.sharepoint.group.1 > > So yeah, I'm not a member of wheel group. > > > > > From: "Curt Mills" > > File -> Configure -> Change Debug Level can change it while it's > running. You need to start Xastir from a console/xterm/etc in order to > see them. > > See the file DEBUG_LEVELS for info on which ones to try. > > The sources are the result of a LOT of people over the years, starting > with Frank Gianandrea who initially wrote it. Thank them. ;-) > > The port to use if you're using a TNC4 in KISS mode is the "Serial > KISS TNC" interface. I've used that with H/W full-blown TNC's and with > my TNC-X. > > More than likely it's a group/permissions problem with the interface. > Do an "ls -l" against the port you're using and report back with the > string for it including owner/group/permissions. > > Also report back what "groups" shows when logged-in as the user you're > starting Xastir as. BTW: Don't run Xastir as root. > > > On Mon, Feb 8, 2021 at 6:58 AM Eric Chamberlain > wrote: > > > > Hey Curt. I've seen your comments in the source code, thanks for your work. > > I've used both serial TNC interface and serial KISS TNC interface. Based on > > the /dev/cu comment, I guess it hangs because of blocking(?). I don't > > believe there is a permission on that port. I can apply a generic username > > (guest) in putty with the autologin username without problem. > > > > Is there a debugging #define in the source I can build against to get more > > information while the interface is opening? > > > > > > > > > > From: "Curt Mills" > > > > Which type of interface are you using in Xastir? > > > > Did you add your username to the dialout group? > > > > What are the permissions on the port you're trying to use? > > > > On Mon, Feb 8, 2021 at 4:31 AM Eric Chamberlain > > wrote: > > > > > > That certainly prevents the port from blocking. The interface in xastir > > > returns as 'up' but it doesn't appear to be reading packets off the TNC > > > in the view-incoming data window. Looking in putty it still shows the > > > incoming packets. So its not quite fixed yet. > > > > > > > > > > > > > > > From: "Jason KG4WSV" > > > > > > Try the /dev/cu.whatever device special file. > > > > > > It’s been a few years but when I hit the same problem (well, Kermit not > > > putty) switching to cu did the trick. > > > > > > -Jason > > > > > > > On Feb 7, 2021, at 8:44 PM, Eric Chamberlain > > > > wrote: > > > > > > > > I've been trying to configure an interface to read the tinytrak4 TNC, > > > > which is supposed to operate as KISS according to their docs. When I > > > > run PuTTY on the /dev/tty.usbserial-1430 port I can see packets coming > > > > in from a test transmitter. I close putty and open xastir so the port > > > > isn't blocking. When I go to start the TNC interface, in mac it hangs > > > > without messages in the terminal window. On the putty it doesn't hang > > > > but there's nothing. There are never incoming packets from the view > > > > data window. Unfortunately, Byonics say they don't know much about > > > > xastir. I've tried this both on my mac and my raspberry. The cable > > > > setup works for programming and PuTTY, so I don't think its that or > > > > drivers. I think it comes down to settings. Is there anything I can try? > > > > ___ > > > > Xastir mailing list > > > > Xastir@lists.xastir.org > > > > http://xastir.org/mailman/listinfo/xastir > > > ___ > > > Xastir mailing list > > > Xastir@lists.xastir.org > > >
Re: [Xastir] Tinytrak TNC not opening interface
I went ahead and added my userid to the wheel group but no effect. Also I ran debug level 3. It gave me the Opening a Serial KISS device output before hanging. I added some output to the source and remade the file to output the other serial variables, here's what came out. Port Available 1 Opening a Serial KISS TNC device Dev Type 10 Dev baud rate 19200 Dev style 0 I'm going to look at what comes next after this add_device call. From: "Curt Mills" The permissions are R/W for user/group/other, so I don't think you need to add yourself to the wheel group for this. Perhaps one of the OSX guys can comment on that though. I don't run OSX. On Mon, Feb 8, 2021 at 7:30 AM Eric Chamberlain wrote: > > I haven't set debug yet, but I wanted to respond with the ls -l output first. > crw-rw-rw- 1 root wheel 18, 4 Feb 8 10:26 /dev/tty.usbserial-1430 > > I'm logged in as user ericchamberlain and groups looks like: > staff access_bpf everyone localaccounts _appserverusr admin _appserveradm > _lpadmin _appstore _lpoperator _developer _analyticsusers > com.apple.access_ftp com.apple.access_screensharing com.apple.access_ssh > com.apple.access_remote_ae com.apple.sharepoint.group.1 > > So yeah, I'm not a member of wheel group. > > > > > From: "Curt Mills" > > File -> Configure -> Change Debug Level can change it while it's > running. You need to start Xastir from a console/xterm/etc in order to > see them. > > See the file DEBUG_LEVELS for info on which ones to try. > > The sources are the result of a LOT of people over the years, starting > with Frank Gianandrea who initially wrote it. Thank them. ;-) > > The port to use if you're using a TNC4 in KISS mode is the "Serial > KISS TNC" interface. I've used that with H/W full-blown TNC's and with > my TNC-X. > > More than likely it's a group/permissions problem with the interface. > Do an "ls -l" against the port you're using and report back with the > string for it including owner/group/permissions. > > Also report back what "groups" shows when logged-in as the user you're > starting Xastir as. BTW: Don't run Xastir as root. > > > On Mon, Feb 8, 2021 at 6:58 AM Eric Chamberlain > wrote: > > > > Hey Curt. I've seen your comments in the source code, thanks for your work. > > I've used both serial TNC interface and serial KISS TNC interface. Based on > > the /dev/cu comment, I guess it hangs because of blocking(?). I don't > > believe there is a permission on that port. I can apply a generic username > > (guest) in putty with the autologin username without problem. > > > > Is there a debugging #define in the source I can build against to get more > > information while the interface is opening? > > > > > > > > > > From: "Curt Mills" > > > > Which type of interface are you using in Xastir? > > > > Did you add your username to the dialout group? > > > > What are the permissions on the port you're trying to use? > > > > On Mon, Feb 8, 2021 at 4:31 AM Eric Chamberlain > > wrote: > > > > > > That certainly prevents the port from blocking. The interface in xastir > > > returns as 'up' but it doesn't appear to be reading packets off the TNC > > > in the view-incoming data window. Looking in putty it still shows the > > > incoming packets. So its not quite fixed yet. > > > > > > > > > > > > > > > From: "Jason KG4WSV" > > > > > > Try the /dev/cu.whatever device special file. > > > > > > It’s been a few years but when I hit the same problem (well, Kermit not > > > putty) switching to cu did the trick. > > > > > > -Jason > > > > > > > On Feb 7, 2021, at 8:44 PM, Eric Chamberlain > > > > wrote: > > > > > > > > I've been trying to configure an interface to read the tinytrak4 TNC, > > > > which is supposed to operate as KISS according to their docs. When I > > > > run PuTTY on the /dev/tty.usbserial-1430 port I can see packets coming > > > > in from a test transmitter. I close putty and open xastir so the port > > > > isn't blocking. When I go to start the TNC interface, in mac it hangs > > > > without messages in the terminal window. On the putty it doesn't hang > > > > but there's nothing. There are never incoming packets from the view > > > > data window. Unfortunately, Byonics say they don't know much about > > > > xastir. I've tried this both on my mac and my raspberry. The cable > > > > setup works for programming and PuTTY, so I don't think its that or > > > > drivers. I think it comes down to settings. Is there anything I can try? > > > > ___ > > > > Xastir mailing list > > > > Xastir@lists.xastir.org > > > > http://xastir.org/mailman/listinfo/xastir > > > ___ > > > Xastir mailing list > > > Xastir@lists.xastir.org > > >
Re: [Xastir] Tinytrak TNC not opening interface
The permissions are R/W for user/group/other, so I don't think you need to add yourself to the wheel group for this. Perhaps one of the OSX guys can comment on that though. I don't run OSX. On Mon, Feb 8, 2021 at 7:30 AM Eric Chamberlain wrote: > > I haven't set debug yet, but I wanted to respond with the ls -l output first. > crw-rw-rw- 1 root wheel 18, 4 Feb 8 10:26 /dev/tty.usbserial-1430 > > I'm logged in as user ericchamberlain and groups looks like: > staff access_bpf everyone localaccounts _appserverusr admin _appserveradm > _lpadmin _appstore _lpoperator _developer _analyticsusers > com.apple.access_ftp com.apple.access_screensharing com.apple.access_ssh > com.apple.access_remote_ae com.apple.sharepoint.group.1 > > So yeah, I'm not a member of wheel group. > > > > > From: "Curt Mills" > > File -> Configure -> Change Debug Level can change it while it's > running. You need to start Xastir from a console/xterm/etc in order to > see them. > > See the file DEBUG_LEVELS for info on which ones to try. > > The sources are the result of a LOT of people over the years, starting > with Frank Gianandrea who initially wrote it. Thank them. ;-) > > The port to use if you're using a TNC4 in KISS mode is the "Serial > KISS TNC" interface. I've used that with H/W full-blown TNC's and with > my TNC-X. > > More than likely it's a group/permissions problem with the interface. > Do an "ls -l" against the port you're using and report back with the > string for it including owner/group/permissions. > > Also report back what "groups" shows when logged-in as the user you're > starting Xastir as. BTW: Don't run Xastir as root. > > > On Mon, Feb 8, 2021 at 6:58 AM Eric Chamberlain > wrote: > > > > Hey Curt. I've seen your comments in the source code, thanks for your work. > > I've used both serial TNC interface and serial KISS TNC interface. Based on > > the /dev/cu comment, I guess it hangs because of blocking(?). I don't > > believe there is a permission on that port. I can apply a generic username > > (guest) in putty with the autologin username without problem. > > > > Is there a debugging #define in the source I can build against to get more > > information while the interface is opening? > > > > > > > > > > From: "Curt Mills" > > > > Which type of interface are you using in Xastir? > > > > Did you add your username to the dialout group? > > > > What are the permissions on the port you're trying to use? > > > > On Mon, Feb 8, 2021 at 4:31 AM Eric Chamberlain > > wrote: > > > > > > That certainly prevents the port from blocking. The interface in xastir > > > returns as 'up' but it doesn't appear to be reading packets off the TNC > > > in the view-incoming data window. Looking in putty it still shows the > > > incoming packets. So its not quite fixed yet. > > > > > > > > > > > > > > > From: "Jason KG4WSV" > > > > > > Try the /dev/cu.whatever device special file. > > > > > > It’s been a few years but when I hit the same problem (well, Kermit not > > > putty) switching to cu did the trick. > > > > > > -Jason > > > > > > > On Feb 7, 2021, at 8:44 PM, Eric Chamberlain > > > > wrote: > > > > > > > > I've been trying to configure an interface to read the tinytrak4 TNC, > > > > which is supposed to operate as KISS according to their docs. When I > > > > run PuTTY on the /dev/tty.usbserial-1430 port I can see packets coming > > > > in from a test transmitter. I close putty and open xastir so the port > > > > isn't blocking. When I go to start the TNC interface, in mac it hangs > > > > without messages in the terminal window. On the putty it doesn't hang > > > > but there's nothing. There are never incoming packets from the view > > > > data window. Unfortunately, Byonics say they don't know much about > > > > xastir. I've tried this both on my mac and my raspberry. The cable > > > > setup works for programming and PuTTY, so I don't think its that or > > > > drivers. I think it comes down to settings. Is there anything I can try? > > > > ___ > > > > Xastir mailing list > > > > Xastir@lists.xastir.org > > > > http://xastir.org/mailman/listinfo/xastir > > > ___ > > > Xastir mailing list > > > Xastir@lists.xastir.org > > > http://xastir.org/mailman/listinfo/xastir[http://xastir.org/mailman/listinfo/xastir][http://xastir.org/mailman/listinfo/xastir[http://xastir.org/mailman/listinfo/xastir]][http://xastir.org/mailman/listinfo/xastir[http://xastir.org/mailman/listinfo/xastir][http://xastir.org/mailman/listinfo/xastir[http://xastir.org/mailman/listinfo/xastir]]] > > > ___ > > > Xastir mailing list > > > Xastir@lists.xastir.org > > > http://xastir.org/mailman/listinfo/xastir[http://xastir.org/mailman/listinfo/xastir][http://xastir.org/mailman/listinfo/xastir[http://xastir.org/mailman/listinfo/xastir]] > > > > > > > > -- > > Curt, WE7U > >
Re: [Xastir] Tinytrak TNC not opening interface
I haven't set debug yet, but I wanted to respond with the ls -l output first. crw-rw-rw- 1 root wheel 18, 4 Feb 8 10:26 /dev/tty.usbserial-1430 I'm logged in as user ericchamberlain and groups looks like: staff access_bpf everyone localaccounts _appserverusr admin _appserveradm _lpadmin _appstore _lpoperator _developer _analyticsusers com.apple.access_ftp com.apple.access_screensharing com.apple.access_ssh com.apple.access_remote_ae com.apple.sharepoint.group.1 So yeah, I'm not a member of wheel group. From: "Curt Mills" File -> Configure -> Change Debug Level can change it while it's running. You need to start Xastir from a console/xterm/etc in order to see them. See the file DEBUG_LEVELS for info on which ones to try. The sources are the result of a LOT of people over the years, starting with Frank Gianandrea who initially wrote it. Thank them. ;-) The port to use if you're using a TNC4 in KISS mode is the "Serial KISS TNC" interface. I've used that with H/W full-blown TNC's and with my TNC-X. More than likely it's a group/permissions problem with the interface. Do an "ls -l" against the port you're using and report back with the string for it including owner/group/permissions. Also report back what "groups" shows when logged-in as the user you're starting Xastir as. BTW: Don't run Xastir as root. On Mon, Feb 8, 2021 at 6:58 AM Eric Chamberlain wrote: > > Hey Curt. I've seen your comments in the source code, thanks for your work. > I've used both serial TNC interface and serial KISS TNC interface. Based on > the /dev/cu comment, I guess it hangs because of blocking(?). I don't believe > there is a permission on that port. I can apply a generic username (guest) in > putty with the autologin username without problem. > > Is there a debugging #define in the source I can build against to get more > information while the interface is opening? > > > > > From: "Curt Mills" > > Which type of interface are you using in Xastir? > > Did you add your username to the dialout group? > > What are the permissions on the port you're trying to use? > > On Mon, Feb 8, 2021 at 4:31 AM Eric Chamberlain > wrote: > > > > That certainly prevents the port from blocking. The interface in xastir > > returns as 'up' but it doesn't appear to be reading packets off the TNC in > > the view-incoming data window. Looking in putty it still shows the incoming > > packets. So its not quite fixed yet. > > > > > > > > > > From: "Jason KG4WSV" > > > > Try the /dev/cu.whatever device special file. > > > > It’s been a few years but when I hit the same problem (well, Kermit not > > putty) switching to cu did the trick. > > > > -Jason > > > > > On Feb 7, 2021, at 8:44 PM, Eric Chamberlain > > > wrote: > > > > > > I've been trying to configure an interface to read the tinytrak4 TNC, > > > which is supposed to operate as KISS according to their docs. When I run > > > PuTTY on the /dev/tty.usbserial-1430 port I can see packets coming in > > > from a test transmitter. I close putty and open xastir so the port isn't > > > blocking. When I go to start the TNC interface, in mac it hangs without > > > messages in the terminal window. On the putty it doesn't hang but there's > > > nothing. There are never incoming packets from the view data window. > > > Unfortunately, Byonics say they don't know much about xastir. I've tried > > > this both on my mac and my raspberry. The cable setup works for > > > programming and PuTTY, so I don't think its that or drivers. I think it > > > comes down to settings. Is there anything I can try? > > > ___ > > > Xastir mailing list > > > Xastir@lists.xastir.org > > > http://xastir.org/mailman/listinfo/xastir > > ___ > > Xastir mailing list > > Xastir@lists.xastir.org > > http://xastir.org/mailman/listinfo/xastir[http://xastir.org/mailman/listinfo/xastir][http://xastir.org/mailman/listinfo/xastir[http://xastir.org/mailman/listinfo/xastir]][http://xastir.org/mailman/listinfo/xastir[http://xastir.org/mailman/listinfo/xastir][http://xastir.org/mailman/listinfo/xastir[http://xastir.org/mailman/listinfo/xastir]]] > > ___ > > Xastir mailing list > > Xastir@lists.xastir.org > > http://xastir.org/mailman/listinfo/xastir[http://xastir.org/mailman/listinfo/xastir][http://xastir.org/mailman/listinfo/xastir[http://xastir.org/mailman/listinfo/xastir]] > > > > -- > Curt, WE7U > http://xastir.org[http://xastir.org][http://xastir.org[http://xastir.org]] > http://www.sarguydigital.com[http://www.sarguydigital.com] > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir[http://xastir.org/mailman/listinfo/xastir][http://xastir.org/mailman/listinfo/xastir[http://xastir.org/mailman/listinfo/xastir]] > ___ > Xastir mailing list >
Re: [Xastir] Tinytrak TNC not opening interface
File -> Configure -> Change Debug Level can change it while it's running. You need to start Xastir from a console/xterm/etc in order to see them. See the file DEBUG_LEVELS for info on which ones to try. The sources are the result of a LOT of people over the years, starting with Frank Gianandrea who initially wrote it. Thank them. ;-) The port to use if you're using a TNC4 in KISS mode is the "Serial KISS TNC" interface. I've used that with H/W full-blown TNC's and with my TNC-X. More than likely it's a group/permissions problem with the interface. Do an "ls -l" against the port you're using and report back with the string for it including owner/group/permissions. Also report back what "groups" shows when logged-in as the user you're starting Xastir as. BTW: Don't run Xastir as root. On Mon, Feb 8, 2021 at 6:58 AM Eric Chamberlain wrote: > > Hey Curt. I've seen your comments in the source code, thanks for your work. > I've used both serial TNC interface and serial KISS TNC interface. Based on > the /dev/cu comment, I guess it hangs because of blocking(?). I don't > believe there is a permission on that port. I can apply a generic username > (guest) in putty with the autologin username without problem. > > Is there a debugging #define in the source I can build against to get more > information while the interface is opening? > > > > > From: "Curt Mills" > > Which type of interface are you using in Xastir? > > Did you add your username to the dialout group? > > What are the permissions on the port you're trying to use? > > On Mon, Feb 8, 2021 at 4:31 AM Eric Chamberlain > wrote: > > > > That certainly prevents the port from blocking. The interface in xastir > > returns as 'up' but it doesn't appear to be reading packets off the TNC in > > the view-incoming data window. Looking in putty it still shows the incoming > > packets. So its not quite fixed yet. > > > > > > > > > > From: "Jason KG4WSV" > > > > Try the /dev/cu.whatever device special file. > > > > It’s been a few years but when I hit the same problem (well, Kermit not > > putty) switching to cu did the trick. > > > > -Jason > > > > > On Feb 7, 2021, at 8:44 PM, Eric Chamberlain > > > wrote: > > > > > > I've been trying to configure an interface to read the tinytrak4 TNC, > > > which is supposed to operate as KISS according to their docs. When I run > > > PuTTY on the /dev/tty.usbserial-1430 port I can see packets coming in > > > from a test transmitter. I close putty and open xastir so the port isn't > > > blocking. When I go to start the TNC interface, in mac it hangs without > > > messages in the terminal window. On the putty it doesn't hang but there's > > > nothing. There are never incoming packets from the view data window. > > > Unfortunately, Byonics say they don't know much about xastir. I've tried > > > this both on my mac and my raspberry. The cable setup works for > > > programming and PuTTY, so I don't think its that or drivers. I think it > > > comes down to settings. Is there anything I can try? > > > ___ > > > Xastir mailing list > > > Xastir@lists.xastir.org > > > http://xastir.org/mailman/listinfo/xastir > > ___ > > Xastir mailing list > > Xastir@lists.xastir.org > > http://xastir.org/mailman/listinfo/xastir[http://xastir.org/mailman/listinfo/xastir][http://xastir.org/mailman/listinfo/xastir[http://xastir.org/mailman/listinfo/xastir]] > > ___ > > Xastir mailing list > > Xastir@lists.xastir.org > > http://xastir.org/mailman/listinfo/xastir[http://xastir.org/mailman/listinfo/xastir] > > > > -- > Curt, WE7U http://xastir.org[http://xastir.org] http://www.sarguydigital.com > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir[http://xastir.org/mailman/listinfo/xastir] > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Tinytrak TNC not opening interface
Hey Curt. I've seen your comments in the source code, thanks for your work. I've used both serial TNC interface and serial KISS TNC interface. Based on the /dev/cu comment, I guess it hangs because of blocking(?). I don't believe there is a permission on that port. I can apply a generic username (guest) in putty with the autologin username without problem. Is there a debugging #define in the source I can build against to get more information while the interface is opening? From: "Curt Mills" Which type of interface are you using in Xastir? Did you add your username to the dialout group? What are the permissions on the port you're trying to use? On Mon, Feb 8, 2021 at 4:31 AM Eric Chamberlain wrote: > > That certainly prevents the port from blocking. The interface in xastir > returns as 'up' but it doesn't appear to be reading packets off the TNC in > the view-incoming data window. Looking in putty it still shows the incoming > packets. So its not quite fixed yet. > > > > > From: "Jason KG4WSV" > > Try the /dev/cu.whatever device special file. > > It’s been a few years but when I hit the same problem (well, Kermit not > putty) switching to cu did the trick. > > -Jason > > > On Feb 7, 2021, at 8:44 PM, Eric Chamberlain > > wrote: > > > > I've been trying to configure an interface to read the tinytrak4 TNC, > > which is supposed to operate as KISS according to their docs. When I run > > PuTTY on the /dev/tty.usbserial-1430 port I can see packets coming in from > > a test transmitter. I close putty and open xastir so the port isn't > > blocking. When I go to start the TNC interface, in mac it hangs without > > messages in the terminal window. On the putty it doesn't hang but there's > > nothing. There are never incoming packets from the view data window. > > Unfortunately, Byonics say they don't know much about xastir. I've tried > > this both on my mac and my raspberry. The cable setup works for programming > > and PuTTY, so I don't think its that or drivers. I think it comes down to > > settings. Is there anything I can try? > > ___ > > Xastir mailing list > > Xastir@lists.xastir.org > > http://xastir.org/mailman/listinfo/xastir > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir[http://xastir.org/mailman/listinfo/xastir][http://xastir.org/mailman/listinfo/xastir[http://xastir.org/mailman/listinfo/xastir]] > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir[http://xastir.org/mailman/listinfo/xastir] -- Curt, WE7U http://xastir.org[http://xastir.org] http://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir[http://xastir.org/mailman/listinfo/xastir] ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Tinytrak TNC not opening interface
Which type of interface are you using in Xastir? Did you add your username to the dialout group? What are the permissions on the port you're trying to use? On Mon, Feb 8, 2021 at 4:31 AM Eric Chamberlain wrote: > > That certainly prevents the port from blocking. The interface in xastir > returns as 'up' but it doesn't appear to be reading packets off the TNC in > the view-incoming data window. Looking in putty it still shows the incoming > packets. So its not quite fixed yet. > > > > > From: "Jason KG4WSV" > > Try the /dev/cu.whatever device special file. > > It’s been a few years but when I hit the same problem (well, Kermit not > putty) switching to cu did the trick. > > -Jason > > > On Feb 7, 2021, at 8:44 PM, Eric Chamberlain > > wrote: > > > > I've been trying to configure an interface to read the tinytrak4 TNC, > > which is supposed to operate as KISS according to their docs. When I run > > PuTTY on the /dev/tty.usbserial-1430 port I can see packets coming in from > > a test transmitter. I close putty and open xastir so the port isn't > > blocking. When I go to start the TNC interface, in mac it hangs without > > messages in the terminal window. On the putty it doesn't hang but there's > > nothing. There are never incoming packets from the view data window. > > Unfortunately, Byonics say they don't know much about xastir. I've tried > > this both on my mac and my raspberry. The cable setup works for programming > > and PuTTY, so I don't think its that or drivers. I think it comes down to > > settings. Is there anything I can try? > > ___ > > Xastir mailing list > > Xastir@lists.xastir.org > > http://xastir.org/mailman/listinfo/xastir > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir[http://xastir.org/mailman/listinfo/xastir] > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Tinytrak TNC not opening interface
That certainly prevents the port from blocking. The interface in xastir returns as 'up' but it doesn't appear to be reading packets off the TNC in the view-incoming data window. Looking in putty it still shows the incoming packets. So its not quite fixed yet. From: "Jason KG4WSV" Try the /dev/cu.whatever device special file. It’s been a few years but when I hit the same problem (well, Kermit not putty) switching to cu did the trick. -Jason > On Feb 7, 2021, at 8:44 PM, Eric Chamberlain wrote: > > I've been trying to configure an interface to read the tinytrak4 TNC, which > is supposed to operate as KISS according to their docs. When I run PuTTY on > the /dev/tty.usbserial-1430 port I can see packets coming in from a test > transmitter. I close putty and open xastir so the port isn't blocking. When I > go to start the TNC interface, in mac it hangs without messages in the > terminal window. On the putty it doesn't hang but there's nothing. There are > never incoming packets from the view data window. Unfortunately, Byonics say > they don't know much about xastir. I've tried this both on my mac and my > raspberry. The cable setup works for programming and PuTTY, so I don't think > its that or drivers. I think it comes down to settings. Is there anything I > can try? > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir[http://xastir.org/mailman/listinfo/xastir] ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Tinytrak TNC not opening interface
Try the /dev/cu.whatever device special file. It’s been a few years but when I hit the same problem (well, Kermit not putty) switching to cu did the trick. -Jason > On Feb 7, 2021, at 8:44 PM, Eric Chamberlain wrote: > > I've been trying to configure an interface to read the tinytrak4 TNC, which > is supposed to operate as KISS according to their docs. When I run PuTTY on > the /dev/tty.usbserial-1430 port I can see packets coming in from a test > transmitter. I close putty and open xastir so the port isn't blocking. When > I go to start the TNC interface, in mac it hangs without messages in the > terminal window. On the putty it doesn't hang but there's nothing. There > are never incoming packets from the view data window. Unfortunately, Byonics > say they don't know much about xastir. I've tried this both on my mac and my > raspberry. The cable setup works for programming and PuTTY, so I don't think > its that or drivers. I think it comes down to settings. Is there anything I > can try? > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
