On Mon, Feb 08, 2021 at 11:21:15AM -0800, we recorded a bogon-computron collision of the <curt.w...@gmail.com> 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 > <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]] > > > _______________________________________________ > > > 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[http://xastir.org/mailman/listinfo/xastir] > > _______________________________________________ > > Xastir mailing list > > Xastir@lists.xastir.org > > http://xastir.org/mailman/listinfo/xastir > > > > -- > Curt, WE7U http://xastir.org http://www.sarguydigital.com > _______________________________________________ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Tom Russo KM5VY Tijeras, NM echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] _______________________________________________ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
