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" <curt.w...@gmail.com> 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 <curt.w...@gmail.com> 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 > <ericchamberl...@mail.com> 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 > > ROCKET|!&#c'?|!w5f! > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,191401,A,4015.8930,N,07946.0789,W,000,169,080221,,*0C|!'#c'@|!w<r! > > > > > > > > > > > > From: "Jason KG4WSV" <kg4...@gmail.com> > > > > 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 <ericchamberl...@mail.com> > > > 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" <kg4...@gmail.com> > > > > > > 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 <ericchamberl...@mail.com> > > >> 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]] > > _______________________________________________ > > 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 -- 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
