I use kcat all the time and it works great. I use fldigi only now and then. But I built fldigi from source yesterday, to get all the new-and-improved, all looked clean. But now doesn't work with kcat.
?
I wish I had tried this before blowing away my old fldigi. I can't say what version it was, or if for sure it would have worked yesterday. But it used to work.
?
fldigi version 4.2.06
kcat version 1.2.5
?
Sequence & Symptoms:
- start fldigi
- some alsa lib errors, JackShmReadWritePtr messages
- some complaints about not being able to open sockets
- But it starts up and shows a nice normal looking window.
- start kcat - no indicated issues
?
I start fldigi in a terminal window and after starting kcat I can see that the two are talking over the xmlrpc link, constant streaming of freq/band/mode messages in the fldigi terminal window that look ok.
Frequency, mode, bandwidth are the same in both gui windows.
If I change mode or bandwidth on kcat, fldigi tracks. Likewise if I change mode or bandwidth from fldigi, kcat tracks.
===> If I try to change frequency from kcat, it won't, meaning it briefly shows the changed frequency then jumps back.
===> If I change frequency from fldigi, fldigi updates the display as if normal, but nothing happens on the kcat end (stays stuck on same freq as when started).
If I close fldigi, kcat can then manage the frequency as normal. So it would seem fldigi is not allowing kcat to change frequency.
?
I think this setup worked a few months ago. kcat has not changed. fldigi has changed.?
I would try building a downlevel fldigi to test against but I don't know how, and can't find instructions.
?
Any suggestions appreciated.
?
Bill N7DZ
?