I've used UiView and I'm sad to hear that the author of that program has become silent key. APRS is my main focus on amateur radio...because the technology side is what got me interested in it. I am a software engineer, and I decided that the software side of this is needing some updating. I have begun programing an IGate/Digipeater program that will simply the installation and setup of this.
This program is running as a service...meaning no matter if you log off, the program will continue to run. Any program that runs in a server environment should really be run as services. However I do have a GUI that allows you to configure the Windows service.
This week, I am coding the actual functionality of the program, and will do the integration with the TNCs later. I have never done any programming where integrating with hardware, so I'm not sure how that will work, but I'll cross that bridge when I get there. Basically, what I am asking is what are the most popular TNCs...and where is the documentation to them? I'll need to know some hardware specifications so I can know how to communicate with them.
Is there anything that you can think of that would be beneficial to this software?
Make it KISS compliant - that way it'll work on most any TNC, even some of the purpose built limited function jobbies that don't cost both arms and a leg.
Cross platform - Gotta be able to run on *nix. Special if I'm going to be running a public facing I-gate/server setup, no way would I ever consider doing it on a MS platform. Cost, reliability, security, etc, etc...
KA7O - what you're wanting is already available - look at DigiNed. I'm currently in the planning mode for an APRS digi here in SEKS - I'm planning to repurpose one of my old Cobalt RAQ machines (old 150MHz MIPS little-endian CPU) running Debian and the built-in Linux AX.25 stack.
MGZ - Definately write to KISS mode, but thing is, many digipeaters are in remote mountaintop areas, and don't actually have a computer driving them - rather the digi function is all handled in firmware. For a location connected to a computer, usually being in the home, an I-Gate is a much more common function, with perhaps limited wide1-1 fill-in digi capability.
Make sure to also read up on the N-mode digis (new paradigm) - it changes things a little, and you want your software to be capable of handling that.
I am a Windows developer. I have little experience in Java so I don't have enough to develope an application like this. Again it's going to be a Windows service that runs in the background. I am aware of the new paradigm, and also the KISS protocol for TNCs.
KA7O - what you're wanting is already available - look at DigiNed. I'm currently in the planning mode for an APRS digi here in SEKS - I'm planning to repurpose one of my old Cobalt RAQ machines (old 150MHz MIPS little-endian CPU) running Debian and the built-in Linux AX.25 stack.
More power to ya, man. Having choices is the name of the game.
For digi use - we mostly use UIDIGI 'round here. EPROMs on MFJ-1270s - tanks. We currently have 3 up. Cheap, reliable and robust as all get out. I have to agree, the idea of using a PC for a digipeater is less than attractive. BUT, the thought of having another I-gate/server option - now there's a winning game.
I'm Writing an IGate and Digipeater Program
Linear Mode
