I’m upgrading the radio on my AllStarLink node from a Baofeng/AIOC to a Yaesu FT-1900R using the Digirig. I’ve searched a bunch for answers/help with getting the PTT to work to no avail so far. I saw the thread about modifying a previous version of the hardware (1.9 I think) to allow ASL3 to key the Yaesu but I have version 1.11 and they’re not quite the same.
Does anyone know what I can do to allow the Yaesu to work with Asterisk and the Digirig? I have no problem soldering something if it isn’t too complicated. Thanks for reading!
The configuration pads are the same between 1.9 and 1.11, but you don’t need to make any changes for PTT to work. In Digirig Mobile this is done via the RTS signal of the serial port and it’s the same regardless of the serial lines configuration.
Here’s some relevant info from the web:
Key Steps and Settings:
Configuration File: Edit /etc/asterisk/simpleusb.conf (if using simpleusb) or /etc/asterisk/rpt.conf.
PTT Type: Set pttType = RTS to use the RTS pin for PTT, or pttType = DTR to use the DTR pin.
Device Node: Ensure the devicenode matches your serial device, for example: devicenode=/dev/ttyUSB0.
Active Low/High: If the PTT is reversed, you may need to set invertptt=1 in the configuration.
Quick reply, thank you! I’ve tried every combination of PTT with both SimpleUSB and USBRadio. I’m noticing now too that keying up the node (even though it shows audio coming in through the tune CLI) doesn’t actually trigger anything. It never beeps after receiving a transmission.
Weirdly, minicom will key up the radio as soon as it opens but Asterisk does nothing. This may be an ASL3 issue and not the Digirig as it seems to be correct, including the cables I got. I can key up shorting the ring and sleeve. Unless I’m missing something obvious, I should probably post on the ASL forums instead.
my allstarlink nodes are from way back so the information i give is most likely OUT OF DATE
allstarlink uses GPIO of the cm108 ‘style’ soundcards for ptt
almost period
i used, way back, a parallel port channel driver to get an old g.e. mastr II base to ptt.
no serial port channel driver was available.
so, the ‘modification’ to a digirig MOBILE was to get the GPIO tap out to the radio cables.
(minicom is asserting RTS when opened and that is what is keying the radio)
i haven’t done that nor remember what thread the details were in but that is what you’re looking for.
other than that, the digirig LITE uses GPIO natively.
i realise that doesn’t help your case, just fyi.
Are you saying the lite version would work with this radio? Did I buy the wrong Digirig for the 1900 and ASL3? I’ve verified the wiring is good and the radio keys testing with WSJT-X on Windows. I’ve been unsuccessful getting ASL3 to recognize incoming transmissions or to get it keying up the radio on Debian.
what i’m saying is:
allstarlink, as far as i know, does NOT support ptt via RTS (comport) which is what the digirig MOBILE uses.
the digirig LITE uses GPIO/CM108 for ptt which is what allstarlink uses since inception.
the digirig lite has no comport therefore no CAT/CI-V/remote control capability but you’re not using that anyway for your allstarlink setup.
(if i were building new allstarlink nodes, i’d buy digirig LITEs because they are exactly like my ancient homebrew modified FOBs or bought allstarlink fob/dongles)
NOW, wsjt-x does support ptt via RTS as well as cat/ci-v/remote control so the digirig mobile is great for that.
the digirig mobile has the cm108 ‘style’ audio chip so the gpio is there but not brought out to the cable connections. (allstarlink can identify the correct audio device is present and toggle the gpio but since it’s not connected to the radio ptt, the radio never keys up)
