I wanted to use the digirig mobile with the FT-897 and VARA FM. Audio in/out are ok, Digirig creates a comport on my computer. I cannot get the PTT working, whatever I try.
I have the original Digirig FT-897 cables connected to the radio. I thought the digirig creates the PTT on the 6 pin Din connector when I set the comport in VARA FM to the correct baudrate and comport. I also tried setting the Yaesu radio with CAT Control, Com4, 4800 Baud, did not work.
The Digirig is in its default configuration (no traces cut)
The CAT port of the FT897 seems to work, tried it with winlink express and the frequency is set correctly.
My configuration of VARA was correct. I tried the same configuration on another PC and it worked. After a lot of try and error I found a solution. I changed the comport setting from COM4 to COM16. I have no idea why COM4 did not work, it was not used by another program, it was ok in device manager, the silab driver was the same and latest version.
Thank you for the update and for posting the solution.
Maybe there was some software locking your COM4. The serial ports require exclusive access so once one app connects it, nothing else can use it.
I am trying to configure DIREWOLF to work with my DigiRig mobile. I am using PINPOINT software and want to have the DIREWOLF be the TNC. I have gone to the author forums (i.e. DireWolf, APRS, etc) and canât seem to find anyone who can get this to work. I have no problem decoding packets. DigiRig works fine with FLDIGI and WSJT-x on my rig. I am using a Windows 11 laptop. I canât get the rig to key up with the software and when I do the rig remains in TX and I have to CTRL-C to disconnect. Is VARA a better solution than DireWolf?
Any help would be much appreciated. Of course, I have spent hours on this trying to get it to work.
Direwolf and Vara are not interchangeable as they implement different transfer protocols so you should be using one that matches the digipeater you are connecting.
With Digirig Mobile youâll need to configure PTT by RTS. From other discussions on this subject the configuration line should look something like this (obviously referencing the device matching Digirig in your system):
PTT /dev/ttyUSB0 RTS
The sticky PTT can be the results of RFI. See âsticky PTTâ section in the troubleshooting guide for tips on diagnosing and solutions.
pinpoint (or any other aprs mapper/tracker) + vara is in minimal use compared to mappers/trackers + packet.
it is NOT used on the north american aprs frequency of 144.390
that is reserved for traditional aprs packet activity.
vara aprs makes good use of HF in areas that have no vhf coverage.
there are very few hf stations gating aprs traffic though.
and unlink vhf aprs, you wont hear your beacon repeated back.
(nor can you make use of two way aprs traffic)
finding out if your beacon was gated or not would require looking it up on the internet via aprs.fi.
so, it depends on your use case as to which direction to head. so to speak.
if youâre using windows, iâd recommend trying uz7ho soundmodem to shake things out.
it has âdrop downâ menus for selecting the different ptt methods and does a fine job acting as a software TNC between the digirig/audio device and the pc software.
direwolf works well also and is configured for ptt as suggested earlier.