I've finished my vp-digi TNC board (KISS enabled board, not a fully featured TNC with AGW) and I'm playing with packets.
I'm able to use the TNC just fine using e.g. QtTermTcp in linux or Tera
But, I can send commands to the TNC just fine using the terminal and I see it's responses. And the TNC starts in KISS mode after startup. So, it
So, I'm not sure if I'm missing something. It seems like paKet should support KISS enabled devices. So, is there a need for some driver to make
I'm able to use the TNC just fine using e.g. QtTermTcp in linux or Tera Term windows, but there's one computer where I'd like to run a DOS terminal app.
If you can send keyboard commands to the TNC and it responds to them,
then it's not in KISS mode. You didn't mention, but are you taking steps to exit KISS mode prior to using QtTermTcp or TeraTerm?
I'm not familiar with your TNC or paKet so can't say much more except the problem likely boils down to "TNC not in KISS mode" or "incorrect serial port configuration (in paKet, I suppose)".
use Minicom or whatever terminal (Telix, Telemate, etc). Then I can put them in KISS mode and use kissattach for the ax.25 tools or run an APRS app or whatever.
Have you tried your TNC with anything like Xastir or YAAC or PinPoint
I was able to run BPQ32 on the same computer with the TNC just fine. So, I'm not sure what's causing paKet program not to work.
I'm not familiar with the kissattach command - I've read it is used to map a AX.25 network device. Why do you need that? To emulate a full TNC capability
Sysop: | Xerxes |
---|---|
Location: | Azle, Texas |
Users: | 131 |
Nodes: | 10 (0 / 10) |
Uptime: | 26:33:33 |
Calls: | 3,172 |
Calls today: | 0 |
Files: | 195 |
U/L today: |
0 files (0K bytes) |
D/L today: |
0 files (0K bytes) |
Messages: | 363,306 |
Posted today: | 0 |