This is a continuation of a previous thread whose subject matter had drifted from its starting point. Essentially, this relates to a problematic update of Quisk running on an RPi P400 with the default rpi 32-bit operating system. The original installation of Quisk and Hamlib from the RPi repository produced workable results, though interaction was appreciably slow. The update of Quisk from PyPi corrected a minor annoyance, but also exposed a more serious hamlib/rigctl problem.
Here, I am responding to this posting from the previous thread:?
/g/n2adr-sdr/message/2803??That post suggests Quisk's interaction with hamlib is failing because Quisk emulates hamlib/rigctld, but has not kept up with hamlib evolution. An incompatibility may have crept in, I guess.
To test, I installed Quisk 4.2.20 and Hamlib 4.6~git. Then I did a simple command-line experiment with rigctl communicating with Quisk to first set and then get frequency. In that particular experiment, setting the frequency worked, but the subsequent read-back was wrong. The read-back was off by 5khz.
I then re-installed WSJTX from the RPi respository. WSJTX was unable to maintain correct frequency sync with Quisk. I believe WSJTX attempts to sync up about once per second. If it happens to come up in sync, it quickly wanders off in a seemingly random way.
Attempts to set and get frequency through one of Quisk's virtual serial ports yield similarly erratic results.
It occurs to me the result might be different with a 64-bit OS installation, but doing that experiment is non-trivial with my setup, so I have not yet done it.
Comments?
