¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. N2adr-Sdr
  2. Topics

Quisk Version 4.1.51 November 2019

 

I fixed a bug in the "small screen" code when using the new wx version 4. Thanks to Martin Schaller for pointing out that underflows from the Soapy sample source should not count as errors.
?
This version fixes the Linux installation errors "ImportError: No module named _quisk". It also provides a way to run either Python2 or Python3 quisk when both are installed. To do that use "python2 -m quisk" or "python3 -m quisk".
?
The new installation instructions are here: http://james.ahlstrom.name/quisk/docs.html#Installation
?
Jim
N2ADR
Sid Boyce
 

Thanks Jim,
Tested OK HL2 with ODROID-C2.
Tomorrow will test on Standalone HiQSDR and report.
73 ... Sid.

On 23/11/2019 22:00, jimahlstrom wrote:
I fixed a bug in the "small screen" code when using the new wx version 4. Thanks to Martin Schaller for pointing out that underflows from the Soapy sample source should not count as errors.
This version fixes the Linux installation errors "ImportError: No module named _quisk". It also provides a way to run either Python2 or Python3 quisk when both are installed. To do that use "python2 -m quisk" or "python3 -m quisk".
The new installation instructions are here:
Jim
N2ADR
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
 

Thanks Jim,
Tested OK HL2 with ODROID-C2 - 7 inch LCD and on HiQSDR standalone also? ODROID-C2 and 7 inch LCD.
73 ... Sid.

On 23/11/2019 22:00, jimahlstrom wrote:
I fixed a bug in the "small screen" code when using the new wx version 4. Thanks to Martin Schaller for pointing out that underflows from the Soapy sample source should not count as errors.
This version fixes the Linux installation errors "ImportError: No module named _quisk". It also provides a way to run either Python2 or Python3 quisk when both are installed. To do that use "python2 -m quisk" or "python3 -m quisk".
The new installation instructions are here:
Jim
N2ADR
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
 


Ubuntu 18:04:
make quisk3 and make soapy3? compiles without errors
when in the main Quisk directory:
./quisk does not work
python3 ./quisk.py works

On Sat, Nov 23, 2019 at 11:00 PM jimahlstrom <jahlstr@...> wrote:
I fixed a bug in the "small screen" code when using the new wx version 4. Thanks to Martin Schaller for pointing out that underflows from the Soapy sample source should not count as errors.
?
This version fixes the Linux installation errors "ImportError: No module named _quisk". It also provides a way to run either Python2 or Python3 quisk when both are installed. To do that use "python2 -m quisk" or "python3 -m quisk".
?
The new installation instructions are here:
?
Jim
N2ADR
 

Hello Peter,

"python3 quisk.py" works because you specified the correct Python. "./quisk.py" fails because your default Python is Python2. When both Python2 and Python3 are installed, we are stuck with specifying the correct Python for the Quisk we are using.

Jim
N2ADR
 

LinuxMint 19.1: Downloaded tarball and expanded.
make (with no parms) compiles without errors
The last line says to "make soapy2".
running "make soapy2" results in an error 'No rule to make target soapy2'

running "make soapy" compiles with no errors and quisk runs fine.
Also the SDRPlay error count is fixed.
 

Hello Mike,

Yes there is an error in the makefile. Use "make soapy" instead of "make soapy2" to make the Python2 version until I get this fixed.

Jim
N2ADR
 

I forgot my attachment, sorry...

Mike N8OOU

Screenshot from 2019-11-24 06-39-07.png

 

Hi Jim

Have build 51 running under Python 3.8 on WIndows 10 (32 bit) with G7LHS SDR.
Runs fine with a couple of exceptions
1. whilst executing quisk.py directly works, quisk.exe does nothing
2. FDV button is greyed out
Will try to investigate some more tomorrow.
Dave
Gil Cross
 

¿ªÔÆÌåÓý

??? ??? Wondering if this Dave Roberts was an converter engineer at AC Spark Plug??????????????? K8EAG


On 11/24/2019 5:33 PM, dave.roberts via Groups.Io wrote:

Hi Jim

Have build 51 running under Python 3.8 on WIndows 10 (32 bit) with G7LHS SDR.
Runs fine with a couple of exceptions
1. whilst executing quisk.py directly works, quisk.exe does nothing
2. FDV button is greyed out
Will try to investigate some more tomorrow.
Dave

 

Sorry, no. Electronic engineer, ex British Telecom research and ex Mastercard.
Gil Cross
 

¿ªÔÆÌåÓý

??? ??? Thank you, Dave??????????????? K8EAG????? Gil


On 11/25/2019 5:14 AM, dave.roberts via Groups.Io wrote:

Sorry, no. Electronic engineer, ex British Telecom research and ex Mastercard.

 

Hi Jim

Update. Tried installing on my main dev machine - same versions but this is 64 bit windows 10. Installed 64 bit version of python 3.8. With this build I can't load a comms dll that the 'LHS SDR uses. Specifically a 32 bit windows MFC dll.?
Error traceback below.?Tried rebuilding dll with VS2019 as both win32 and x64 dll, get same response.?

Does it need to be 32 bit python for quisk?

Dave
------------------------------------------
Traceback (most recent call last):
? File "C:\Users\Dave\AppData\Local\Programs\Python\Python38\Lib\site-packages\quisk\quisk.py", line 3560, in OnInit
? ? if self.local_conf.GetHardware():
? File "C:\Users\Dave\AppData\Local\Programs\Python\Python38\Lib\site-packages\quisk\configure.py", line 244, in GetHardware
? ? application.Hardware = dct['Hardware'](application, conf)
? File ".\quisk_hardware_adt.py", line 23, in __init__
? ? self.adt_dll = windll.LoadLibrary(".\\adt-buddy.dll")
? File "C:\Users\Dave\AppData\Local\Programs\Python\Python38\lib\ctypes\__init__.py", line 447, in LoadLibrary
? ? return self._dlltype(name)
? File "C:\Users\Dave\AppData\Local\Programs\Python\Python38\lib\ctypes\__init__.py", line 369, in __init__
? ? self._handle = _dlopen(self._name, mode)
OSError: [WinError 193] %1 is not a valid Win32 application
OnInit returned false, exiting...
 

When running Python or anything else, the main program and all DLLs must be the same; 32 or 64 bit. That is why Quisk is available for both. You can use either Quisk to work with what you have.

Jim
N2ADR
 

That's what I assumed - what threw me was the python error message "OSError: [WinError 193] %1 is not a valid Win32 application" when this is 64 bit and it gave the same message when I tried 32 and 64 bit builds of the DLL

Will play some more....

Dave
 
Edited

Have sorted out my 64 bit version problem. Calling a 64 bit DLL from Python with pointers to data is a bit tedious I must say!

As per 32 bit versions Jim, when run under windows 10 with 64 bit Python 3.8, the FDV button is greyed out and the executable quisk.exe returns an error code 0x01 and does not start up quisk.
Update: "ok = QS.freedv_open()" returns 0. Not yet set up to trace into the binary files (sorry)

Apart from that, all runs fine for me

Dave
 

Hello Dave,

I am shipping a FreeDV DLL but it is for 32-bit Windows. I will have to figure out how to make a 64-bit version and how to keep them separate.

Jim
N2ADR
 

Hi Jim

Apologies for the delay in replying. The problem is also present in the 32 bit version - Windows 10 32 bit, 32 bit Python 3.8. FreeDV button greyed out. Just in case it was path related I copied the freedv dlls to the quisk folder but no joy.

Dave

1 - 18 of 18