[nos-bbs] Anyone using the NinoTNC on JNOS

Jay Nugent jjn at nuge.com
Sat Jan 16 03:02:48 EST 2021


Greetings,
    I had hoped that with the demise of the YNC-Pi that the newly 
introduced NinoTNC would be a great substiture.  Where the TNC-Pi used the 
Pi's 40-pin I/O connector, the NinoTNC uses a USB interface.

    So I set up the attach as follows:

   attach asy <device> <-> <mode> <label> <bufsize> <mtu> [<speed>] <flags>
   attach asy  ttyACM0  -   ax25  144.93     576     256    57600


    This appeared to look promising, as packets would get transmitted just 
fine, and it looked like receive was working, but about 90% of the packets 
received never get delivered over the USB to JNOS.

    Incoming packets are detected by the NinoTNC, it indicates they were 
properly received, and it indicates that they were sent up the USB.  But 
it takes *several* packets before the "connected" appears on JNOS, and on 
rare occasions I might actually see the signon.

    The NinoTNC LEDs all indicated that the packet was received and 
decoded.  Sometimes packets are displayed, but the data is missing 
characters or is partially garbled.  My initial thoughts were that the 
USB was running too fast, hence the garbling.  So I dropped the USB speed 
to 19200 - but that didn't work at all.  NinoTNC USB is probably hard 
coded to 57600 I presume?

    There are some <flags> that *may* be need to be set to better control 
the buffers?


    So my question is, has anyone sucessfully used the NinoTNC with JNOS?


    Thanks!
       --- Jay WB8TKL





More information about the nos-bbs mailing list