So, we talked in Synchronet Sysops and via email about some packet-related stuff.
echicken
So, we talked in Synchronet Sysops and via email about some packet-related stuff. KD8NCV was also asking some related questions in here recently. I added a bunch of files to the Synchronet CVS (cvs.synchro.net) today that may be of use.
If we could get all the TNC enabled BBSes to join, and have links to each other like say a menu that telgates to the other board, then at least the packet hams will have a reason to roam around and call more the oneI will be calling soon...
BBS....
I have the basic TNC .js setup and working on the BBS here, and am working o getting the other .js scripts to work as well.
Which script is it that you've got working - ax25call.js?
The AX.25 library I've written still has some bugs. Connections will recover from errors sometimes, sometimes not so much - I'm working on finishing up that part of the code. So, it's not a finished product and it may not be totally usable for you yet. However, if you're interested in testing it and letting me know what happens, it would be a great help.
I setup the ax25call.js and it shows the screen. But at this point I have n been able to get it to connect or work the TNC...
I am thinking it programs the TNC to fast?
A time limit in the door may be needed... I seen a connection in the stable version for over a hour with no activity....
Since only one person at a time can use it, we may have to limit the amount time it can be used per session?
I tried to set the time option in the door menu, but it did not kick the use after 30 mins...
Was that the "Monitor Time Left" option on the external, or was it the "Maximum Time" option? The latter won't do anything in this case -
Do you have a "kiss.ini" file in your sbbs/ctrl/ directory? That's where you configure the TNC, including which serial port it's on and the baud
rate between computer and TNC. If the baud rate set there is correct, too fast shouldn't be a problem.
Is the TNC definitely in KISS mode?
100% not sure about this one. Let me see if I can paste a display Z here... --------
DISPLAY A,C,I,L,M,T,Z
cmd:display z
...
--------
It does not display it, but KISS ON is set.
It's definitely not in KISS mode. In KISS mode, the TNC isn't (particularly) usable from a terminal emulator; it should only be
exchanging KISS frames with your computer, rather than responding to
textual commands like "display Z".
So, while it does say "KISS ON" is set, there are probably additional steps that you need to take in order to put it into KISS mode. IIRC the PK-88 manual does go into a bit of detail about this process (section 5, page 52 if memory serves.)
So, while it does say "KISS ON" is set, there are probably additional steps that you need to take in order to put it into KISS mode. IIRC the PK-88 manual does go into a bit of detail about this process (section 5, page 52 if memory serves.)
Now when I enter the program, the Sta and Con leds flash back and forth, but it still kicks me out of the script, and the TNC does not TX the radio or attempt to connect to the other station...
in the terminal server screen, I see
Node 1 kc7stw-0->W7TA-4 : U_FRAME_SABM
(this line shows 5 times,)
Node 1 kc7stw-0 failed to connect to W7TA-4
Subject: Re: AX.25 packet radio & Synchronet
@VIA: ECBBS
@MSGID: <4FA6D67B.1443.dove-ham@bbs.electronicchicken.com>
@REPLY: <4FA6BF3B.1259.dove-ham@phantomrage.org>
@TZ: c12c
Re: Re: AX.25 packet radio & Synchronet
By: Phantomrage to echicken on Sun May 06 2012 11:13:15
Now when I enter the program, the Sta and Con leds flash back and forth, it still kicks me out of the script, and the TNC does not TX the radio or attempt to connect to the other station...
in the terminal server screen, I see
Node 1 kc7stw-0->W7TA-4 : U_FRAME_SABM
(this line shows 5 times,)
Node 1 kc7stw-0 failed to connect to W7TA-4
Okay, well at least the script is exiting for a good reason now - what you'r seeing there is the script attempting to connect to the other station five times, then failing. This is expected behavior.
Of course, since the TNC isn't keying up your radio something else must be going on. Unfortunately there's nothing I can do to the software to fix thi a TNC in KISS mode is supposed to key up and transmit once it receives a fra from the host (your computer) so either it's not entirely set up for KISS mo yet or something else is going on on the TNC side. I'll take a look at the PK-88 manual later on and see if there are any other hints in there.
Hopefully I'll have a PK-88 and maybe some other TNCs to test with in the ne future. I'm planning to scour the Hamvention flea market with an eye peeled for packet gear.
echicken
electronic chicken bbs - bbs.electronicchicken.com - 416-273-7230
if a ham has a wild time with 2 girls. is that a ham sandwich?
Okay, well at least the script is exiting for a good reason now - what you're seeing there is the script attempting to connect to the other
station five times, then failing. This is expected behavior.
Of course, since the TNC isn't keying up your radio something else must be going on. Unfortunately there's nothing I can do to the software to fix this - a TNC in KISS mode is supposed to key up and transmit once it receives a frame from the host (your computer) so either it's not entirely set up for KISS mode yet or something else is going on on the TNC
Hopefully I'll have a PK-88 and maybe some other TNCs to test with in the near future. I'm planning to scour the Hamvention flea market with an eye peeled for packet gear.
I will do some testing on the TNC and see what I come up with. Good to know that once in kiss there really is no (buffer) lets say in the TNC.. Just I have info, and pass it out over the air..
I will look around, and see what other TNCs I can find here. and send them you in the mail for testing. I seem to come into a few for free. So far I just have a old PK88.. But if it works once it is setup I will not need any more TNCs so again if I find them, I can send them to you for testing.
Well, if the TNC receives a valid AX.25 frame encapsulated in a KISS frame from the host, it should send it out over the air once the frequency is open.
Does the other station have to be in KISS mode?
If so, that may be the issue, since NO-ONE around here uses KISS....
Then errors with,
E:\sbbs\exec\ax25call.js line 51: TypeError: inputLine.getkey is not a function
Then errors with,
E:\sbbs\exec\ax25call.js line 51: TypeError: inputLine.getkey is not a function
To start with, grab an up to date copy of exec/load/inputline.js from the Synchronet CVS. Also, make sure that you don't have another copy of inputline.js in e:\sbbs\exec or e:\sbbs\mods.
To start with, grab an up to date copy of exec/load/inputline.js from the Synchronet CVS. Also, make sure that you don't have another copy of inputline.js in e:\sbbs\exec or e:\sbbs\mods.
Does kiss have a way to set this TX delay before sending the data packets?
Or does setting the TNC TXDELAY option then placing it in KISS mode do the same?
To start with, grab an up to date copy of exec/load/inputline.js from the Synchronet CVS. Also, make sure that you don't have another copy of inputline.js in e:\sbbs\exec or e:\sbbs\mods.
Whether those settings survive the switch into KISS mode would depend on
the TNC, but I suspect they would not in most cases. However, KISS does have some provisions for setting txdelay among other things. That's something that I don't yet have support for, but could add in easily. I'll look into that later on.
Not sure how to test this. Need to read about kiss, and figure out how to a a TX delay. I will do some reading today since the wife is sick and in bed have some free time.
const KISS_TXD = (1<<0);// TX delay
(I wish I had a reference for java)
Sysop: | Chris Crash |
---|---|
Location: | Huntington Beach, CA. |
Users: | 557 |
Nodes: | 8 (0 / 8) |
Uptime: | 100:57:46 |
Calls: | 10,385 |
Files: | 5 |
Messages: | 360,835 |