Packet radio
Messing around with packet today via the FT817 and Windows 10 PC. I'm getting used to two programs, WinRPR which supports Robust packet, and, of course, UZ7HO's SoundModem.
There was a lot of APRS activity via RP on 10.1473MHz USB and it all decodes nicely in WinRPR.
Then on to SoundModem on 14.105MHz LSB (Network105). There were a few more decodes since I took the screenshot.
My next step is to find a client to tx APRS.
You should also read:
Packet mailbox NoV
I now have a NoV for GB7RVB, a packet mailbox on 144.950MHz. It is currently set for AFSK AX25 at 1200 baud, though may move to more modern IL2P 4800 baud after trials. It is located here in IO93eu and I would be interested in reports if anyone manages to connect to it. The only service currently enabled is local chat. Early days... it's a bit of a backwater here with no packet and hardly any APRS activity. Maybe this will start it as there are moves elsewhere to build up a national packet network. If one or two other nodes pop up between here and the emerging networks we could make links. If you do not have a hardware TNC it is possible to use software, for example I have successfully used QtSoundModem to drive a Signalink and my FT817, and QtTermTCP to connect via AGW to the modem, with the FT817 set to 144.950 and packet mode. GB7RVB is currently based on the LinBPQ package and runs on a Raspberry Pi 3B, with a NinoTNC (see my earlier post about having built that). It is currently driving an FTM100 set for 5W but will be using a Tait…
Continue reading...Packet progress...
I actually achieved something. Makes a change! At this stage I must state that I overlooked the fact I have an FTM100 and it has a suitable interface! Ok, no way I am going to fiddle soldering a 10-pin mini-DIN plug even if I had one, so I ordered a CT167 cable from www.JGTech.com which arrived within two days. I already had a stock of D9 plugs. With the NinoTNC connected to the Windows PC the APRSIS32 software could send and receive APRS to/from my FT2D (no APRS activity round here other than a receive-only igate). But packet was a tad more problematic. I wanted to use the Windows PC + Signalink + FT817 setup which means using QtSoundModem on the PC, but I also needed a program to talk to the TNC. QtTermTCP will via KISS but neither the Mac or Linux version had KISS anywhere to be seen, only AGW. And any mix of QtSoundModem and QtTermTCP on the Windows PC generally resulted in nothing talking to anything, which is probably my fault but it definitely got in the way. So... I set up an old Pi 3B with the LinBPQ software, connected the NinoTNC / FMT100 to…
Continue reading...Radio moves
I've had the FT817 attached to the MacBook of late, just for VHU/UHF use, but the poor old Mac struggles if I dare to use anything other than wsjt-x. I want a Mac Mini... but anyway, that aside I decided to move the radio over to the Windows PC now. wsjt-x installed easily as usual and all works. The only issue I can see is how Windows messes up its USB ports if I switch the FT450D in. Currently I have that configured to switch between the Linux PC and the Windows PC so I can use VARA / VarAC and other such things on HF via the FT450D. I just use a USB switch obtained via Amazon which seems to work ok. The FT450D side of things comes in as COM6 and the FT817 now comes as COM4, no idea how Windows decides to allocate those. Time will tell...
Continue reading...