PTT Triggered by DATA with cat control (V drop from 3.3v to 1.5v on PTT line when serial data is being sent to radio)
Closed this issue · 16 comments
Sorry for yet another issue to respond to! I know you're busy and I hate taking up your time
I wired up my FT-857D to an AIOC. It works well. I can use it like a digirig with audio and PTT, and I can also do cat control and programming. However, I cant do cat control and audio in and out at the same time. If I have both cables plugged in at once, it constantly toggles PTT over and over again for very short intervals (same speed as the TX of data).
Is this expected behavior? Is it possible to do something like CAT control while also using the soundcard and PTT features of the AIOC perhaps by adding another component in my wiring or by rearranging the wires some?
Probing with the multimeter, PTT and PTT GND isnt shorted when TXing serial data, but when it's not transmitting serial data (to the radio) the voltage is 3.3 volts across PTT and PT GND. When it transmits, the voltage drops to 1.5v. From my understanding, this is enough to trigger a lot of PTT circuits despite the standard being 2v (only .2 v off)
Compare this to when PTT is actually triggered, and the voltage is 0.
One possible workaround it to add a switch to my PTT line and simply use CAT PTT when doing rig control.
Wanted to add, this happens on both the standard and virtual ptt firmware.
Tested this on a few more radios (FT-100d, 878d, Xiegu G90) and am having the same issue. When any data communication goes on, it triggers PTT.
Sorry to bug ya! Just wanted to add some activity here in case this issue got lost in the inbox. You're likely just busy with things which I totally get. @skuep
Not lost at all! Just a bit swamped with work and health currently. I am planning to look into it this or next weekend.
Gotchya, thanks so much Simon! I certainly get that.
Sorry for yet another issue to respond to! I know you're busy and I hate taking up your time
I wired up my FT-857D to an AIOC. It works well. I can use it like a digirig with audio and PTT, and I can also do cat control and programming. However, I cant do cat control and audio in and out at the same time. If I have both cables plugged in at once, it constantly toggles PTT over and over again for very short intervals (same speed as the TX of data).
Okay, so we are now getting into the hacky territory? :-) That's not a HT right? That's a "real" radio, that you can remotely control (CAT) and has audio in/out. I like this, and I think the AIOC should be able to work with something like this. The AIOC has been designed with HT's in mind, so that means the serial port and PTT can only work exclusively (because they are on the same pad essentially). But those radios should be close enough to make it work.
Is this expected behavior? Is it possible to do something like CAT control while also using the soundcard and PTT features of the AIOC perhaps by adding another component in my wiring or by rearranging the wires some?
If I understand you correctly, that is the (current) expected behaviour. Due to the PTT line being connected to the TXD (Radio RXD) line, the firmware is designed to clear any PTT when it receives a "write serial data" command from the PC. That alone should probably be an issue or is it? Or does the PC only send commands to the radio during transmit silence (PTT off)? Then it should be okay.
However, the second (your) problem is, that the PTT and Radio-RXD are shorted on the AIOC. Thus, each time the PC sends some data, the PTT pin state will change! (They are connected after all. This is not a problem with HT's since this situation does not arise.)
Currently, I can see the following solution:
- Remove R13, this will remove the PTT from the serial line. The problem should be gone, but you won't have any PTT anymore
- Connect your PTT wire directly to one of the pads of where R13 (see image) was
For a better solution, I could offer you the PTT2 pin (see image in grey), which is currently only accessible using the CM108 feature on GPIO3. It would require some firmware changes to make it configurable, so that the AIOC uses PTT2 pin instead of PTT(1). Since I have configurability of the AIOC planned for the near future (using a simple python tool), this could be a good solution. In this case, you won't need to solder anything (since PTT1 will not interfere with any serial commands) and the radio's PTT will be controlled using the "exclusive" PTT2 pad which does not share functionality.
Btw, why is the MIC ground connected to the serial pin? Is that correct?
All good ideas. Currently leaving PTT disconnected is my solution, since CAT control can work to trigger PTT, although I'd like to have the ability to hotswap between rig control ptt and AIOC's ptt without having to flip a switch or solder or something (as some apps dont support rig control).
Removing R13 and connecting to that PTT pad in red, that would isolate PTT from the rest? That sounds like a good temporary solution.
The firmware to use PTT2 would be excellent down the road once the python script is done more.
As far as MIC ground connected there, that's what is expected for the official kenwood jack connection standard. I think it works because it gets shorted when PTT is triggered, which it always would be for most MIC input... hmmm
For reference, I based this on:
and
I think I had one customer wire it to the same ground as speaker and it also worked, so that might be better for compatibility.
Thanks so much for your help!
@skuep - was thinking it might be beneficial to start an issue to track the python script. I'd also be willing to put $100 towards your development process of this PTT firmware and the management script. Let me know if this would be significantly helpful.
I think issue #30 is already a good start. You can consolidate your feature request proposal regarding configurability of PTT2 in that issue.
I am sorry that I have not yet gotten around to do it. Unfortunately until mid of September I am still not able to, due to work travel. Thanks for your offer anyway but I think I would rather remain independent :-)
I think issue #30 is already a good start. You can consolidate your feature request proposal regarding configurability of PTT2 in that issue.
I am sorry that I have not yet gotten around to do it. Unfortunately until mid of September I am still not able to, due to work travel. Thanks for your offer anyway but I think I would rather remain independent :-)
I missed #30, thanks! All totally understandable, and no rush. Just figured if it helped I wouldnt mind throwing support your way with no strings or expectations. I pray work and travel goes well!
Have you had another go at the feature? Would be interesting to know if changing to the PTT2 setting works using the HID Python script.
I have not, missed your comment on the phython script! I'll have to take a look and figure out how to use it in the coming weeks!
Good news, the next hardware revision will have a split-pad for the PTT1/RX signal so you can actually use both signals separately, if you're not using the K1 layout.
Also, PTT1 and PTT2 will be input-capable as well.
I will close this issue for now. I will let everyone know when the next hardware revision arrives.
Hi @skuep,
Picking up on this project again. Trying to refresh my memory on some of this. Got busy moving / graduating / getting married.
Not sure if it's available yet - Where can I download the second hardware revision? Id like to take advantage of the split ptt and serial pads on my next big order.
I also hope to customize the design a bit to add some resistors and bring the output serial voltage down to 3.3v on an optional pad.