I must have had the squelch turned up when I reported it did not key up connected to the laptop PC.
With the radio off, and all connections to the PC connected (and squelch turned all the way down), when I power on the radio, it goes right into transmit and I hear it on the other radio, just like it does when I attempt to connect on Woad.
We’re yet to determine how squelch causes radio to keyup, but for the clarification can you confirm that the radio doesn’t key up when just the cable is connected if the squelch is enabled?
Ok, so it appears that the received audio somehow bleeds into the PTT circuit and triggers it. Interestingly enough though the received audio should stop once the radio is transmitting which in turn should have stop the transmission.
Do you happen to have a continuity tester to confirm that connections are correct in the cable and there are no unwanted connections? Here’s how things should look like:
The differentiator is audio from the radio (tip contact on Digirig side), the effect is the PTT (ring 2 contact which is also connected via resistor to ring 1 on Digirig side). If I had to guess there must be a short somewhere between those two lines either in the cable or in the radio. I haven’t received any reports of this issue before and you tested with multiple models of the radio so this has to be the specific cable you got. You can re-test it with the continuity tester again or I can just arrange a replacement when they’re back in stock.
Denis, I received the replacement DigiRig cable for my FT60 (not the DigiRig Lite), and it is doing the same thing that as noted above. I have been looking at various websites and videos, along with instructions for my FT60 to try to find out what I am doing wrong. I even programmed the Winlink frequencies for my area (145.0500, 145.0700) into memory slots, thinking there was an issue operating from VFO. With just the DigiRig cable (no DigiRig Lite) connected (and squelch all the way down) as soon as I turn the radio on it goes into transmit. NOTE: I also tried it on a second FT60 that I have access to, and it did the same thing, I MUST be doing something wrong, or overlooking something hopefully obvious.