The latest development copy of NOSaprs (for both TNOS and JNOS systems now) --------------------------------------------------------------------------- * Just take the update kit and extract it over top of your TNOS 2.40 or JNOS 1.11f source distribution (that *should* be all there is to it). Yeh okay ... --------------------------------------------------- FIRST - two fixes : Apparently some people have indicated that if NOSaprs gets an EMAIL request, it crashes. I believe the problem stems from not enough STACK space - so I have bumped up the size of the stack for the APRS_NET process. I hope this fixes it once and for all ! I have made it so that the APRS broadcasts now do the POSITION first, the STATUS last. Previously it has always been the STATUS going out first, however many APRS clients will not recognize a station or object till they see the position first. Previously, this would result in programs like UI-View to completely ignore the initial STATUS. -------------------------------------------- NEW WX Feature (as of July 1) : NOSaprs will now read a data file with WX information, and broadcast it using a DIFFERENT callsign than the NOSaprs igate (logon) call. The new autoexec.nos entries are similar to the following : aprs wx call ve4klm-11 aprs wx stat "Weather Station - Crestview District" aprs wx pos "4953.22N/09718.35W_" aprs wx data "/tmp/wx.data" aprs wx timer 30 NOTE : the posit currently is hardcoded to use the '!' as DTI, the status of course goes out as a '>' DTI value. The format of the data in the 'wx.data' file MUST be like the following : _c248s008g010t075r000p000P000h55b10120wWXD The leading '_' is crucial. It is the DTI. If you don't know anything about APRS wx formats, then DO NOT use this feature. ----------------------------------------- LASTLY - other new features below : 1) Create a new directory (WARNING - you MUST do this) ! cd /jnos (if TNOS, then usually it would be cd /nos instead) mkdir msgdb NOTE : depending on how often you use the aprs message center features of NOSaprs, this directory will get filled up with data files (one for each message you have ever sent or received). Since this is a development version, I have yet to come up with an archive feature to maintain the directory. In other words, keep an eye on it, and feel free to purge it from time to time. Final version will deal with this, but not the present development version. 2) Make sure you have the 'tr' and 'cut' programs installed in your linux, as well as the 'tail' and 'head' programs. These are required for the new browser based APRS message center. 3) Changes to autoexec.nos 'start 14501' is now 'start aprs 14501' 'start 44825' is now 'start aprs 44825' 4) New web based APRS Message Center Add 'start aprs 45845' to your autoexec.nos Then use your internet browser, go to the URL below : http://yourmachine:45845 NOTE: by default, you will NOT be able to send messages or change your options. Only monitoring is available. If you want specific clients to be able to SEND messages and change options, then you need to configure the IP address or addresses of the client or clients. Use the following new NOSaprs command to do this : aprs calls ip45845 ... IMPORTANT: this browser based APRS message center is available for both the Igate and Server compile AND the "end-user" compile (below). FOR JNOS -------- 5a) To compile NOSaprs without the Internet System stuff, just add the option '-DAPRSC' to the end of the PATCHES define in the makefile, for example : PATCHES = -DAPRSD -DJNOSAPRS -DAXUDP -DAPRSC Leave the '-DAPRSC' off if you want the usual APRS Igate and Server. Note that the "end-user" compile will reduce the number of NOSaprs commands, so if you happen to have an autoexec.nos that was used for the Igate compile, and you run the "end-user" compile, it will complain about unknown commands, which is normal of course. This is cool. You can now use the web based APRS message center on your end-user JNOS box and talk APRS over RF like the other software out there. FOR TNOS (read all of 5a above, then note the following difference) -------- 5b) Add the -DAPRSC to your makefile.inc or other appropriate area, since the TNOS makefile stuff is a bit more intricate (and there is no PATCHES type define for TNOS). 6) Crude Kantronics TNC support that will pipe any MONITOR ON data (from say a KPC-2) to the APRS internet system. Perhaps this will be nice for HF monitoring only. AFTERNOTE (Sept 14) - I found out a few days ago that my KPC-2 has a late enough version of eprom in it, and believe it or not, KISS mode is supported by the KPC-2 (all you do via minicom is issue the commands, INTERFACE KISS, then RESET, then disconnect from minicom). So in hindsite this little TIP project was perhaps a *make work* project for me HI HI ... It was educational anyways, I've left the code in place, perhaps it could be useful somewhere. Add the following to your autoexec.nos, make sure your KPC is attached to proper serial port. # 13May2004, Maiko, This is now our Kantronics monitor tnc port attach asy ttyS2 - ax25 aprshf 4096 256 9600 f # I don't think the following are needed, but what the heck param aprshf 1 0 param aprshf 2 256 # 128 param aprshf 3 1 param aprshf 5 1 Now from your NOS console, issue 'tip aprshf aprs', go to the session window, hit enter a few times to make sure you see the 'cmd:' prompt typical of a KPC tnc. Issue the command 'MON ON' to make sure monitoring is enabled. This is VERY CRUDE, perhaps enable debug to make sure that any APRS frames are correctly showing in the log. Then turn debug off. The only way to disable this is to go back to the session screen and issue 'MON OFF', or you can 'detach aprshf'. That's all for now. More work in progress (as time permits). 73 Maiko Langelaar / VE4KLM July 1, 2004 (JNOS) Sept 13, 2004 (TNOS)