* * JNOS 2.0f3 * * This is a COMPLETE snapshot of my (linux) development system * * That means that MY config.h is included - September 15, 2008 * The main reason I am releasing this is because I have a working hostmode driver for the PK-232MBX (pakratt 232) AEA modem (tnc). This release allows you to run a pactor port and accept incoming connections from Airmail or other clients. I'm not ready to release an official version, so this is being made available for those who want to play and test stuff for me. If you have not done so already, you can read the details of the previous two betas (see 'what's been done so far' or 'older news archives' section) to see what else has changed from the last official JNOS 2.0f release. NOTE : this is not a patch ! This is a copy of my entire development system. Getting this latest software ---------------------------- Download the following file (use 'wget' or 'curl' if you want) : http://www.langelaar.net/projects/jnos2/J20f3/J20f3.tar.gz Do a 'gunzip J20f3.tar.gz', followed by a 'tar xvf J20f3.tar'. This will create a 'jnos2' directory in the currently directory. How to compile -------------- Change into the 'jnos2' directory, and enter the command, 'make'. *** Don't panic if you see compile warnings, just ignore them *** This generates a 'jnos' binary. Put it under your /jnos runtime directory. Configuration ------------- There are two new files you need to put under your /jnos runtime directory : 232.cfg This one contains all the TNC parameters needed in order for the new JNOS 2.0f3 hostmode driver to work properly. 232.nos This one is sourced from the command line (or from within the autoexec.nos, and starts the Pactor listener. You can download these files (browser, wget, curl) using the URLs below : http://www.langelaar.net/projects/jnos2/J20f3/232.cfg http://www.langelaar.net/projects/jnos2/J20f3/232.nos Preliminaries ------------- Do NOT 'source 232.nos' until you have done the following first : Even though there is code to put the TNC into hostmode, this beta still requires you to make sure that the PK232 is in command mode, and that you have the correct baud rate in affect. I use minicom, set the baud rate of the program to 9600 baud, and all you need is to make sure that the cmd: prompt can be made to appear. Once you have the cmd: prompt appearing, then quit minicom (don't reset the tnc). Edit the 232.cfg file, the only thing you need to change is the MYPT parameter. It's currently set to my callsign (VE4KLM). PLEASE MAKE SURE you change the callsign to your own ! This requirement will be taken out at a later date, and the callsign will be taken from mycall or something like that. Start the Pactor Listener ------------------------- Enter the command, 'source 232.nos' from the JNOS console or you can put it at the end of your 'autoexec.nos' file. The first time ever, you should see the automatic initialization of the TNC into hostmode for you. You can watch the sequence by turning on HFDD debugging (hfdd debug). Once the init is finished, alot of polling stuff will be sent to the log file, so unless you need to send me debug info, I would suggest you switch HFDD debugging off again (and leave it off). Just type in 'hfdd debug' again to stop the debugging. Note the 'hfdd debug' is a toggle command. You don't specify the value ON or OFF - it just changes from ON to OFF to ON to OFF, and so on, each time you type in the command, 'hfdd debug'. Once the listener is going, try and see if you can get a remote pactor client like Airmail or whatever to connect to your JNOS 2.0f3 system. I am actually quite pleased with the results of this hostmode driver. There are some pretty nice features in the PK232 firmware that I have been sure to use, resulting in good performance and consistency of operation. Hopefully actual on-air (HF) use will show the same. What about outgoing calls ------------------------- Yes, you can do a 'mbox kick ' and JNOS 2.0f3 will initiate an outgoing connect to a remote pactor system. It will actually connect, and the remote system will be able to send it's SID and all that, but I have run into a problem where a suddent disconnect is happening. So that part is not available in working form, but you can try it to see what happens if you really really want. Things to look out for ---------------------- 1. Multiple messages downloaded from JNOS to Airmail result in message bleedover when you actually look at the messages on the Airmail side. I'm not sure what the cause is, but for example, if you send two msgs, then the first message contains a portion of the second one (or some thing like that). 2. If you have run previous beta versions (JNOS 2.0f1, 2.0f2) then you might want to check your /tmp directory for tons of JNOS temporary files (format : fileXXXXX) and delete them. The previous betas had the 'unlink' command commented out (for debugging) and I had forgot to put them back in. In this release (2.0f3) you don't have to worry about it, I did put them back in. 3. The JNOS 2.0f3 hostmode driver disconnects very quickly when it is done with the forward session. You might find that Airmail will require you to manually disconnect (or force a disconnect) when done. IMPORTANT : That's why it's important for a HUMAN to be sitting at the Airmail client. Automated clients will sit there for a few minutes, and tie up the frequency trying to disconnect, when JNOS is already done. I am working to find a solution to this. 4. There is no FEC yet. In other words you can't broadcast your station ID from jnos (yet). I actually forgot to put it in before releasing this, but no worries - it will appear in the next update anyways. That's all for now. Have fun - feedback & test results are more then welcome. ---- 73 de Maiko Langelaar / VE4KLM http://www.langelaar.net/jnos2