Rob, et al.:
1. Hardware flow control is enabled using RTS/DTR - does you serial port provide hardware flow control?
? ? If not, are you shorting the pins to "fake" hardware flow control
? ? KISS mode pretty much requires hardware flow control on hardware TNCs because the speed of the attached device vs. 'on air' device is almost always way different.
? ? The TNC and computer need some sort of control to ensure the buffers don't overrun.? In APRS, the packets are typically small, but it still becomes an issue.
Flow control on the serial port, either the native serial port or the USB to FTDI adapter is set to 'None'.
I'm not shorting any pins.? No physical changes have been made to either cables or ports.
The KISS exit common and pretty common (192, 255, 192) .
The Tera Term Pro macro would be a line of just?
? ? ?sendln 192 255 192
To enter KISS mode, the lines (2 required)
; send interface command to set KISS mode
? ? ?sendln 'INTFACE KISS'
; delay 50 ms (may not be required, but helps on some setups.??
? ? ?mpause 50
; send RESET? typically needs to be sent with 500 ms of the INTFACE (at least on my KPC3 that was true)
? ? ?sendln 'RESET'
I did try the INTFACE KISS command but not the RESET.? I'll have to try that and see what happens.
Additionally, I installed PinPoint APRS and tried it.? I get the same behavior except that PinPoint provides a Communications Monitor Window where I can see the raw traffic from the TNC but still nothing appears on the map.
Thanks, I'll try the KISS change again.
Carmine, K3CWP
