Hi Andy,
thanks for the report.
Am Sun, 23 Jan 2011 21:05:45 +0000
schrieb Andy Summers<address@hidden>:
There's a bug in netkeyer.c since TLF-1.0.0 that I can't figure out.
Its symptoms are that when in SSB mode and you hit, say, F1 to send
that recorded message, cwdaemon gets a PTT=1 command but gets another
PTT=1 at the end of the message when it should get PTT=0. The effect
is that the rig is permanently keyed after pressing the F-key.
I will look into it. But it will be a busy week here and it is possible
that I will find time only the next weekend.
In meantime can you please start cwdaemon with a '-n' switch added.
Then it will not go to daemon and output debug messages what it is
doing.
Try the PTT (for the new and old version) and send us the results. That
would be helpful.
Btw, which version of cwdaemon do you use?
73, de Tom DL1JBE.
I've had a look, but I'm confused because the correct string seems to
be sent to the sendto() system call. Even more confusing is if I edit
callinput.c so it sends PTT=0 at the beginning of the message, it
still asserts PTT!
If I revert to netkeyer.c from TLF-0.9.31 PTT works OK again, but I
don't see that much is changed in that file. Another weird thing is
that if I go back to the new version, recompile, it stops working
properly, then go back to the old version and it still doesn't work.
If I then do 'touch netkeyer.h' and recompile it's fixed again.
There's no difference between the two .h files.
My feeling is that sendto() is getting upset somehow, but I'm not
good enough with C to work it out.
Has anyone else seen this, and/or does anyone have any ideas? For the
time being, I'm using netkeyer.c from TLF-0.9.31.
73 Andy, G4KNO.