The transceiver uses Yaesu’s MiniDin6 connector for audio and PTT. This matches audio cable from Yaesu FT8xx kit and 9600 baud cable.
There is no connection for serial CAT control so Digirig in any configuration can be used with this radio.
The connector pinout is on page 12 of the manual.
Can confirm.
This setup also works with the older version FT-8800, FT-8800R and FT-8800E.
I’ve recently built the 9600 cable based on the schematic. I am considering purchase but i want to see it work with the interface i have before buying a whole new setup which i will prob do so I’m not without my digi-rig on my tx500.
I have an issue where ptt is engaged fully and i cant see why. Ive double and triple check the setup and 99% sure the cable is correct. The one thing that im thinking is the shield from the mini-din side is not connected to anything. its not shown on the schematic. this i feel is prob something to do with it? id very much appreciate a check.
I’m by no means an expert but I’ve been methodical in making the cable. i have a digirig for my tx500 but reading the content this should work with the ft8800.
Thanks in advance.
Owen
Is PTT also engaged when the cable is not connected to anything on Digirig’s end of the cable?
Hi thanks for replying, I’m very aware how much effort you put into this product and forum and I’m very grateful.
No, PTT only engages when the .3.5mm jack is plugged into the audio port on the digirig. I’ve double checked scheme and continuity and it matches and no shorts between pins.
I am configuring Direwolf on an RPI. Perhaps I should check levels on Alsamixer? Perhaps this is engaging PTT via audio output.
O
Ok messing with audio levels in the RPI has not effect on PTT
Ah, RPi is a material bit of info. See if gpsd is active in the system. Digirig is using the same serial chipset and sometimes Linux takes it for a GPS receiver activating RTS signal keying up the radio.
Some relevant discussions: https://forum.digirig.net/search?q=gpsd
Interesting, ill check this out today, though I’m reasonably sure this pi was a fresh flash for building a BBS packet RMS node. My existing node uses a vintage tnc. I’m keen to have some alternative hardware.
Perhaps some other service is gabbing the port/device in a similar way.
Ok, this is 100% a software issue in the Pi (more accurately, a user issue). I checked the configuration in Direwolf and wondered, as I had not specified a PTT device—mistakenly thinking that I didn’t need to—if this was causing some default behavior in the interface. So, I tried a few configurations and solved the issue!
In the Direwolf PTT config section, I enabled the following. Here is the segment from the Direwolf configuration that I changed:
type or paste code
# The transmitter Push to Talk (PTT) control can be wired to a serial port
# with a suitable interface circuit. DON'T connect it directly!
#
# For the PTT command, specify the device and either RTS or DTR.
# RTS or DTR may be preceded by "-" to invert the signal.
# Both can be used for interfaces that want them driven with opposite polarity.
#
# COM1 can be used instead of /dev/ttyS0, COM2 for /dev/ttyS1, and so on.
#
#PTT COM1 RTS
#PTT COM1 RTS -DTR
PTT /dev/ttyUSB0 RTS
#PTT /dev/ttyUSB0 RTS -DTRhere
I’m such a noob at this stage I can’t concentrate long enough to decide why this was an issue. I’m willing to bet someone will beat me to it, but I’ll come back and update if I figure it out in more detail.
Thank you for sharing the solution. Glad to hear your setup is up and running.