Replies: 2 comments 2 replies
-
|
A few questions that may solve the Problem:
|
Beta Was this translation helpful? Give feedback.
-
|
Yes to the first 2 questions and I am using cloudlog-rigctl-interface Looking in the browser console, I see: |
Beta Was this translation helpful? Give feedback.
-
|
Don't know Cloudlog-rigctl. Sure you filed the issue at the right repo? |
Beta Was this translation helpful? Give feedback.
-
|
Cloudlog-rigctl is a python script that sends the radio frequency and mode to wavelog via the API (https://github.com/Manawyrm/cloudlog-rigctl-interface). Referenced here: https://github.com/wavelog/Wavelog/wiki/Radio-Interface Since the info is appearing in the hardware interface screen and changes as I change frequencies/modes), I am fairly sure that the data is being sent (and received) by wavelog correctly. It is just when I open the QSO tab that the data seems to be missing. But, where it says (on the QSO page) 'polling', did something change where wavelog now reaches out to get the frequency info versus before where I would send the data in? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Since updating to version 2.2, when I go to the Live QSO interface, it is not filling in the frequency/mode info from the radio, despite the fact that it shows the correct information on the hardware page.
The hardware page shows:
The frequency and mode are correct and if I change the radio, it tracks.
Going to the QSO screen, I see the radio and it shows
so the frequency information is missing.... This worked prior to the 2.2 release.
Was there a change made in 2.2 (and I did not see the info) or does anybody know what else I can check?
Marc
Beta Was this translation helpful? Give feedback.
All reactions