search

ea4k / klog

KLog is a multiplatform free hamradio logger. It runs natively on Linux, macOS and Windows.
https://www.klog.xyz
GNU General Public License v3.0
75 stars 25 forks source link

klog possibly causing mayhem when rig mode is changed from MEM to VFO with freedv #594

Closed barjac closed 1 year ago

barjac commented 1 year ago

I have been spending a lot of time experimenting with FreeDV digital voice and am using my rig memories to store the DV preferred frequencies. I am having a problem between klog and freedv 'sometimes' when I switch from Memory mode to VFO mode. It only happens with klog in use and if I stop klog the problem goes away instantly.

The problem exhibits itself as rapid switching between VFO and MEM mode ad infinitum until klog is killed. This does not happen with klog on it's own. Only when both klog and freedv are both running. I have seen this before with klog and wsjtx if I remember correctly so I am now becoming more inclined to blame klog for this.

Can you think of anything that klog does that may cause this? klog is in hamlib 'read only' mode using netrigctl, so could it be trying to write and reset the mode?

As yet I do not have a reliable way to reproduce. When I do I will post rigctld logs here.

barjac commented 1 year ago

I have just built the latest git version of freedv which now has the option to use a 'read only' for frequency and mode. I am still seeing the same issue with this option set but something is causing the rig to start switching rapidly between memory and vfo when memory mode is exited manually at the radio.

barjac commented 1 year ago

Changed summary as in wsjtx it is not normal to use memories as wsjtx frequency control is always used. With freedv it is more likely that random frequencies could be used for operation.

barjac commented 1 year ago

Fixed and does not affect klog so closing as INVALID :)