RMS Packet Gateway experiments Windows Version

How to set up an RMS Packet Gateway.  

First of all you have to register it.  I am not there yet since I am still in an experimental stage.  I want to understand how it works before I get it registered and known to the whole world.  I also want to get it right.   The permanent installation will be linux based (I think).   But the easy way to understand the technology is to put up a windows implementation and get a base understanding.   I followed the instructions closely and I got it to work.   These are the two models I have working on the bench reliably.

RMS Relay is normally not necessary.  But in this case since I was not going to register the test setup and I wanted to mail to stay local, RMS Relay gave me that option.

Now that I have something reliable working as a model I can move on to getting the software running in a more permanent configuration.   The hope is that I can get the right Hub/Host software running on a Raspberry PI and go from there.

Kenwood TH-72D TNC Hint

Well I am doing a comparison between the software TNCs , Direwolf, UZ7HO sound modem, AGWPE and have introduced the Hardware TNC that is built into my Kenwood TH-72D handheld unit.     It was fairly easy to move from doing APRS to being a KISS TNC.   Just press the TNC button on the front panel until you see the message move from APRS12 to PACKET12 and make sure the USB port is on and you are set.  

Weird problem is that it would work intermittently.   Worked pretty well and would drop loose a packet or two and work again.    I wound up looking at various setting and then turned off the GPS and everything started working perfectly.     I am guessing the GPS was adding some data to serial stream and corrupting some of the AX.25 packets.  

So the hint.    Turn off the GPS if using the unit as a generic TNC.

What is Winlink?

A new video has been released.  It is pretty good for people wanting to know what is winlink

https://youtu.be/qGhUfW8pjY8

RMS Express P2P over VHF/UHF

Getting the software TNC working was in preparation for getting RMS-Express point to point working.   It worked and was very simple.

I used the 441.025 and listened for a few min to make sure no one was using the frequency.

Both sides were set to use 1200 baud packet on the RF side.

Side A was a PC connected to an Icom IC-7100 using a USB cable and that was it.
   On this PC I had the RMS-Express, Direwolf and C7200 software packages running.

Side B was a second PC connected to a Kenwood TH-D72 using a USB Cable
   On this PC only RMS-Express was needed and the builtin software in RMS-Express
   The TH-D72 was set to use the Packet12 TNC (selected using the TNC button on the faceplate)

I set Side A to be KK4SIH-4 and Side B to be KK4SIH-7

On the A side I started up the Packet P2P server inside of RMS Express

On the B side I created a message destined for KK4SIH-4 and clicked on the P2P button before moving it to the outbox.   Then opened a Packet P2P session and hit start.

The message transferred with no issues.   It also worked in reverse.

The next step is to see if I can get 9600 baud working .

TS-590 USB Drivers

I was setting up a new PC to work with the Kenwood TS590s and it took me a minute to find the right drivers.   Figured I would put up a pointer for the next time I need to do it.

http://www.silabs.com/products/mcu/pages/usbtouartbridgevcpdrivers.aspx

VHF/UHF Packet Radio Frequencies

What is the packet radio frequencies in the VHF and UHF bands?

From http://www.soundcardpacket.org/8frequencies.htm

In the US, most packet activity is found on the 2 meter band:

2 meters:  Baud rate is typically 1200. he most common frequencies are 144.93, 145.01, 145.03, 145.05, 145.07, 145.09 and 145.53 MHz, but you may find it anywhere between 144.90-145.10 and between 145.50-145.80. The baud rate used is 1200.

1.25 meters (220 band): most packet heard in this band will be "backbone" traffic between network nodes and BBSs. It will not be an access band for users. 
70 cm (440 band):  The packet allocation for the band (mixed mode segment) is 432.10-432.30 and 432.40-433.00. Packet should not be used below 432.00. By local option, packet could also be used from 442.000 to 445.950 and 446.100 to 448.000. Baud rate may be 9600 or 1200. 

I looked at the Florida Repeater Council Bandplan - http://florida-repeaters.org/bandplans.htm
   2m packet radio is at 144.900 - 145.100
   70cm  packet radio is at  430.050 - 430.95 for 100 khz channels
                                           431.025 - 431.950 for 25 khz channels
                                           440.975 - 441.075 for 25 khz channels


The key I was told the other day was to listen for a while before you use one of them.  That is a given,  but a smart thing to remember.  

I will probably do my experiments on UHF to stay as far out of the way of the busy 2m band as possible.    I am going to listen, but probably use one of these: 440.9500, 440.9750, 441.0000, 441.0250, 441.0500, 441.0750 which are being recommended by the Kentucky Packet Network group.   I think that will keep me out of everyones way.

APRSIS32 and the IC7100

I continue to play with packet radio using the ICOM IC-7100.   Today I verified things were working using APRSIS32.   There are several versions and you can get it here: http://aprsisce.wikidot.com

APRSIS32 is an APRS application for the PC.   It has a nice graphical interface with maps and everything would would like to see for APRS including messaging.  Take a look:

How I got it to work and what you need to work:

Needed:
  APRSIS32
  CAT7200
  DIREWOLF software TNC

So the keys -
- Install the USB drivers for the 7100 on the PC -  This is a one time thing.

- You have to start CAT7200 before you you start direwolf.   CAT7200 is the software that makes the PTT work on the 7100.  The quick hints are this is that I and using com6 for the Application Port and I have the CAT port set to com4, 19200, 88.   Remember to click the "open" button or you will be scratching your head as to why nothing transmitting.

- Start up direwolf next.   The lines I changed in the direwolf configuration are:
    ADEVICE 0 0
    Channel 0
       MYCALL KK4SIH-4
       PTT COM6 RTS
    Channel 1
       MYCALL KK4SIH-4
       KISSPORT 8100
And that was if for the changes to the direwolf configuration
The start up direwolf

- Set radio to 144.390 FM-D   (North American APRS channel)
     (make sure it is in data mode or the sound card tone are not modified in the radio)

- Start up APRSIS32
     Had to set up the port but it walked me through that
     Make sure the PORT settings have Bulletin/Obj, Messages, Xmit Enable and Beacon Checked
          (could not get messages to work until then)
      Make sure the GENERAL configuration has your callsign-ssid set correct

- Click transmit at the top of the screen and see if everything is working.

To verify things are working you can check at http://aprs.fi

Looking there you can see it was working and can pass messages:
2015-04-11 15:59:58 EDT: KK4SIH-4>APWW10,KD4MOJ-7,WIDE1*,WIDE2-1,qAR,AE4S::KK4SIH-7 :message test
2015-04-11 16:01:49 EDT: KK4SIH-4>APWW10,KD4MOJ-7,WIDE1*,WIDE2-1,qAR,AE4S::KK4SIH-7 :message test [Duplicate message content]
2015-04-11 16:03:00 EDT: KK4SIH-7>APK003,KD4MOJ-7,WIDE1*,WIDE2-1,qAR,AE4S::KK4SIH-4 :got message{13
2015-04-11 16:03:03 EDT: KK4SIH-4>APWW10,KD4MOJ-7*,WIDE1*,WIDE2-1,qAR,KD4MOJ-9::KK4SIH-7 :AA:okk
2015-04-11 16:03:03 EDT: KK4SIH-4>APWW10,KD4MOJ-7*,WIDE1*,WIDE2-1,qAR,KD4MOJ-9::KK4SIH-7 :ack13

Hopefully these tips will help me remember, and anyone out there who may want to do it as well.

ICOM 7100 PTT

OK -  Last night the ICOM 7100 drove me insane.  I am working on getting a software TNC working and could get everything working but nothing was being transmitted.  I ran around in circles until I read on the net that the ICOM USB radios (like the 7100) will only do PTT using CAT commands.   Well that explained everything.

I found a program a nice gentleman in the UK wrote, G8BPQ called CAT7200 (http://www.cantab.net/users/john.wiseman/Documents/CAT7200.html)  that works around the problem.   It creates a virtual COM port to do the PTT with and when it sees RTS on that virtual port it sends the corresponding ICOM CI-V PTT command down the right port and everything works as expected.

His web page explains the process for installing it very well.   Worked like a charm.

Now I have APRS running through the 7100 

Note that this works for not just the ICOM IC-7100, but also for the IC-7200,  IC-7410, IC-7600 and the IC-9100 as well.


To give credit where credit is due, Google brought me to the following website as a starting point:
http://www.vk3bq.com/2014/12/04/icom-ic-9100-rts-cat-control/