开云体育

I need to update the report on 4.2.19 running on RPi OS on a P400. Though it initially seemed to clear the minor hitches encountered in 4.1.77 (the RPi pre-packaged version), 4.2.19 has so far proved unstable and not really usable. Audio may run on start-up, but not always. Toggling the "ON" button may temporarily get audio running, but it soon becomes choppy and then stops. Control communications are also problematic. Wsjtx, configured to use "Hamlib NET rigctl", fails to correctly coordinate frequency settings with quisk 4.2.19. Wsjtx either throws a timeout error box relating to hamlb or it displays a frequency that is not exactly what quisk displays. The wsjtx frequency display changes on its own every few seconds, without user input, suggesting it gets flaky data from quisk/hamlib when it periodically queries (once a second, by default configuration)? A separate, homebrew tcl/tk script for remote control fails similarly, though it uses one of quisk's virtual serial ports for communication of tuning and other control data. Its queries are asynchronous, user triggered and are relatively infrequent.

That brings to mind some recent prior experience with hamlib rigctl. Having used an older version of command-line rigctl reliably for quite some time on a linux mint 19.2 installation on a laptop PC, the newer version on the RPi P400 was much slower. Investigating further by watching rigctl responses on a terminal, there were apparently intermediate processes running until throwing a time-out error, though commands would eventually complete after the time-outs. Similar exercise of the old version of rigctl showed no such errors or delayed execution. Unfortunately, I don't recall hamilb version numbers.

I should also note that the RPi P400 seems to still perform normally with audio from other sources. Internet radio through the browser is working fine, for example.

I will continue to investigate as time permits.

bruce ag5gt