Dan,
?
Thanks for the kudos.? Got some even better news for you, if you'd like to eliminate the TCP/IP "layer" completely on the packet side, but get it to work on the DRATS repeater/reflector software.? I will have to give credit to?Joe Thielen?at the Toledo Mobile Radio Association, who showed me their setup for their TNC to DRATS repeater port.? Turns out that the configuration software in DRATS has a bug that puts an extra : after the com port setting for the tnc.? That gums up the works and causes it to error out when it is trying to open ports.
?
In our case, our original config file had:
?
devices = [('net:192.168.1.147:20011', ''), ('tnc:COM6:0:', '9600')]
?
We changed it to:
?
devices = [('net:192.168.1.147:20011', ''), ('tnc:COM6:0', '9600')]
?
Once the extra colon (:) was removed, we were able to get the TNC to talk directly to the DRATS repeater/reflector software with no problems.
?
The file is named repeater.config and can be found by doing a search on your hard drive.? It will be in different locations depending upon which operating system you are running.
?
We went the "extra mile" and installed the AGWPE Express software, which is normally used for tying RMS Express to a soundcard TNC.? Instead, we tied a "virtual" com port to the IP port of the UZ7HO soundcard software (typically 8000 by default).? That allowed us to use the above tnc setting to drive a sound card.? Information about that handy software can be found at .
?
So we use the soundcard for DRATS and left our old TNC for BPQ32 (all on the same frequency, but two different radios).? So our users can do old fashioned AX.25 packet to our BBS, or go all out on the DRATS software.
?
Hope that helps you and many others out!
?
Best Regards,
Jeff Scoville AE5ME
