I'm writing a winkey client that I'd like to be able to generate its own sidetone through the computer audio interface. I recognize that I'll have to generate the tone and deal with the os side of things myself. That said, I just want to make sure there is no way to get real time tx key line events via winlink (or any other way) over serial.
Presuming there isn't, I was thinking of overriding the WINKEY_2_SUPPORT status message (0xC8), with a feature flag, to indicate when the tx line state changes so that I know when to start/stop the sidetone on the computer. This is obviously breaking the winkey standard, so I may also add a, also non-standard, command that has to be called to enable it once the host is opened.
Do you see any issues with this approach? I recognize that 1200 baud is pretty slow to get accurate timing out of this, but I'm hoping that with the 9600 "high" baud mode that it'll be good enough.
I'm writing a winkey client that I'd like to be able to generate its own sidetone through the computer audio interface. I recognize that I'll have to generate the tone and deal with the os side of things myself. That said, I just want to make sure there is no way to get real time tx key line events via winlink (or any other way) over serial.
Presuming there isn't, I was thinking of overriding the WINKEY_2_SUPPORT status message (0xC8), with a feature flag, to indicate when the tx line state changes so that I know when to start/stop the sidetone on the computer. This is obviously breaking the winkey standard, so I may also add a, also non-standard, command that has to be called to enable it once the host is opened.
Do you see any issues with this approach? I recognize that 1200 baud is pretty slow to get accurate timing out of this, but I'm hoping that with the 9600 "high" baud mode that it'll be good enough.
Thanks a bunch!