开云体育

*** Quisk started on linux at Sun Nov 24 11:09:34 2024
WxPython 4.2.1 gtk3 (phoenix) wxWidgets 3.2.4
Start of wdsp
Found public wdsp
Wdsp version 118
Library wdsp is active
Open channel 1
Traceback (most recent call last):
? File "hermes/quisk_widgets.py", line 78, in OnAtu
? ? if not self.hardware.io_board.have_IO_Board:
? ? ? ? ? ?^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'Hardware' object has no attribute 'io_board'
Traceback (most recent call last):
? File "hermes/quisk_widgets.py", line 78, in OnAtu
? ? if not self.hardware.io_board.have_IO_Board:
? ? ? ? ? ?^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'Hardware' object has no attribute 'io_board'
Traceback (most recent call last):
? File "hermes/quisk_widgets.py", line 78, in OnAtu
? ? if not self.hardware.io_board.have_IO_Board:
? ? ? ? ? ?^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'Hardware' object has no attribute 'io_board'
Closing Remote Control connection

?

I do have an IO board installed and working properly and am able to customize it to operate my peripherals. It appears to me that Quisk does not interrogate the board on startup as the case REG_FIRMWARE_MAJOR: and case REG_FIRMWARE_MINOR: in the IO board firmware is never called. I believe that piHPSDR does not use these calls to detect the board either but uses other methods to see if it is installed or not.

?

The error messages are not an issue in terms of operating Quisk and cause no problems but I'm simply not comfortable with not understanding what is going on.

?

73 de Graeme ZL2TE