Keyboard Shortcuts
Likes
- N2adr-Sdr
- Messages
Search
Re: Quisk and Gnuradio
Hello Bruce.
I was using GNU Radio and GNU Radio Companion several years ago, with Softrocks, our Charleston SDR, and other early SDRs.? Then a few years later I tried to reuse my old GNU Radio designs, but they wouldn't work.? Same with some of the other older SDR software, such as SDR Shell. I ran into two problems, which have led me to limiting my Linux exposure, after being an early adopter.? The first, with GNU Radio and GRC, was that "they" decided to deprecate many/most functions and function names.? So, I needed to rework everything I had done.? Nope.... The second was software and links to software libraries and functions kept being changed to other locations, breaking previously successful builds (such as DSP library locations).? I got tired of "fixing" problems related to these changes, and reduced my Linux operations.? I used to like working with Linux, but the constant changes and "deprecations" killed that interest. I also dislike where Ubuntu went with their desktop..... 73, Terry, N4TLF (formally WB4JFI) |
Re: using FDX in SSB
Gil Cross
开云体育??? Hi, Jim. Thanks for the quick reply. Just gave it a try and in order to then hear the other station I have to unmute and since I use vox that is very cumbersome. My contact buddy did bring up a second receiver and said he could watch ones own signal on the graph, shall see.......Think your suggestion would be ok for AM style chats because you would be clicking PTT off as well as mute... ??? ??? the old guy???? Gil??? K8EAG
On 2/3/2020 12:53 PM, jimahlstrom
wrote:
Hi Gil, |
Quisk and Gnuradio
Hi Jim,
I am intrigued by the open-source gnuradio toolkit and, particularly, the associated graphical tool known as gnu radio companion (GRC). The essential toolkit includes various chunks of code for signal processing and hardware interaction. GRC provides a graphical means to link the chunks by means of signal flow graphs. My understanding is that the heavy duty signal processing is implemented in C++ while python scripting underlies the GRC graphs. One can build and test SDR code with GRC and then export the result, and put a custom GUI in front of it. There appears to be good and growing support for the toolkit. That seems to come from academics who value it as a teaching tool, as well as others who find it useful to tap into a wealth of existing code rather than start from scratch to build things. How reasonable would it be to try re-constructing Quisk in the gnuradio toolkit, with GRC? That might expand the community of folks able to contribute to hardware adaptations and various signal processing opportunities. It might also lower the barrier to newbies hoping to figure out how Quisk is built and, therefore, how to extend it or customize it for various purposes. Having not yet tried to dig into Quisk's innards, I have no idea whether that is crazy talk or easily done or, more likely, something in between. Have you or other community members given any thought to this? cheers, Bruce, ag5gt |
Re: Error building latest QUISK on Windows10
Hello Terry,
Compiling Quisk for Windows is difficult. That is why I supply four binaries for Windows, Python2 or 3 in 32-bit or 64-bit versions. Just use your Python to install Quisk, and it will select the correct version. I was away skiing. I am now back, but will leave next Sunday for another ski trip. If I don't answer, that is why. Jim N2ADR |
Re: Problem with Quisk and LimeSDR/soapy
My miss read ... steve is on Windows .... I'm familiar with linux/openSUSE On Sun, Feb 2, 2020, 8:10 AM Michael Durkin via Groups.Io <Kc7noa=[email protected]> wrote:
|
Re: Problem with Quisk and LimeSDR/soapy
Steve ... are you on windows or linux? On Sun, Feb 2, 2020, 7:46 AM <steve@...> wrote: Wonder if anyone can help with this one. |
Problem with Quisk and LimeSDR/soapy
Wonder if anyone can help with this one.
Trying to use qusk to drive a lime SDR mini with the soapy interface. Downloaded and installed pothos SDR 2020-02-26. It complained on installation that it could not set the path (too long) but checking the path settings, it appears to reference the pothos\bin folder. Don't know fit wants another path setting. Got nothing at all until we copied the soapySDR.dll into the quisk\soapypkg folder. It now gives us the hardware setup page from which we can try to select the device but no devices are listed. Checking with SoapySDRUtil the line SDR is indeed present and found. System is windows 10, 64 bit, 64 bit Python 3.8 with Quisk 4.1.52. Any help gratefully received Steve |
Re: Error building latest QUISK on Windows10
Hi Terry
Just put it in the main source folder along with all the other header files. The problem I got was after that in the handling of complex numbers. I think Quisk (correct me if wrong Jim) uses C99 native complex, and conversions to the FFTW representation, but VS2019 does not implement complex this way, instead using Microsoft's Complex class. This means conversions are tricky (aka not sure how to do it - tried many things). Changing VS project options to the Microsoft Clang option improved matters a lot but still yields errors. Installing quisk with pip is quite separate to VS. Follow Jim's installation guide for that. The other thing to be careful of of course is the installation of python itself but VS should pick that up correctly. I got into a bit of a mess initially, probably caused by VS2015 Python support, ended up removing the installations done via VS and installed python outside of VS then let the IDE find it, which it did. Dave |
Re: Openradio and Quisk
开云体育Thanks Jim, I took your start on getting this to work and with a number of changes, probably for python3, it works nicely.? I did a pull request where I got the original code, and the changes were accepted. Thanks & 73, Rob KL7NA On 1/16/20 12:31 AM, jimahlstrom via
Groups.Io wrote:
Hello Rob, -- Rob Frohne, Ph.D. P.E. E. F. Cross School of Engineering Walla Walla University 100 SW 4th Street College Place, WA 99362 (509) 527-2075 |
Re: Quisk Version 4.1.52 December 2019
Hi Jim,
This seemed like a good thing to try. I finally found a few minutes to do it. Changing to DEBUG = 1 produced quite a string of messages that I can't immediately make much sense of, with QUISK never actually starting. FWIW, here's what spews out: bruce@bruce-Latitude-E6420:~$ quisk & [1] 3689 bruce@bruce-Latitude-E6420:~$ Traceback (most recent call last): ? File "/usr/local/lib/python3.6/dist-packages/quisk/softrock/hardware_usb.py", line 76, in open ??? usb_dev.set_configuration()??????? # and to David, AE9RB, for the fix. ? File "/usr/lib/python3/dist-packages/usb/core.py", line 869, in set_configuration ??? self._ctx.managed_set_configuration(self, configuration) ? File "/usr/lib/python3/dist-packages/usb/core.py", line 102, in wrapper ??? return f(self, *args, **kwargs) ? File "/usr/lib/python3/dist-packages/usb/core.py", line 148, in managed_set_configuration ??? self.backend.set_configuration(self.handle, cfg.bConfigurationValue) ? File "/usr/lib/python3/dist-packages/usb/backend/libusb1.py", line 794, in set_configuration ??? _check(self.lib.libusb_set_configuration(dev_handle.handle, config_value)) ? File "/usr/lib/python3/dist-packages/usb/backend/libusb1.py", line 595, in _check ??? raise USBError(_strerror(ret), ret, _libusb_errno[ret]) usb.core.USBError: [Errno 16] Resource busy Startup freq 14080000 Run freq 14080000 Traceback (most recent call last): ? File "/usr/local/lib/python3.6/dist-packages/quisk/quisk.py", line 3929, in OnInit ??? self.OpenHardware() ? File "/usr/local/lib/python3.6/dist-packages/quisk/quisk.py", line 4009, in OpenHardware ??? self.config_text = Hardware.open() ? File "/usr/local/lib/python3.6/dist-packages/quisk/softrock/hardware_usb.py", line 101, in open ??? print ('Address 0x%X' % usb_dev.ctrl_transfer(IN, 0x41, 0, 0, 1)[0]) ? File "/usr/lib/python3/dist-packages/usb/core.py", line 1043, in ctrl_transfer ??? self.__get_timeout(timeout)) ? File "/usr/lib/python3/dist-packages/usb/backend/libusb1.py", line 883, in ctrl_transfer ??? timeout)) ? File "/usr/lib/python3/dist-packages/usb/backend/libusb1.py", line 595, in _check ??? raise USBError(_strerror(ret), ret, _libusb_errno[ret]) usb.core.USBError: [Errno 32] Pipe error OnInit returned false, exiting... bruce@bruce-Latitude-E6420:~$ debug Re-setting to DEBUG = 0 restores normal operation. I'm afraid I still have too much to learn about quisk to do anything with this. Unless this triggers some useful insight on your part, I'm inclined to let it go for the moment. Quisk really is working nicely in all important respects. Bruce, ag5gt |
Re: charleston-sdr support
开云体育I haven’t been keeping up with the Charleston SDR with Quisk.? But, I
can catch up with this in a little while since there still seems to be some
interest!? I will wade into Quisk and fix it up.
?
Linux will probably first, since Windows has a different driver system
(IIRC).
73, Terry, N4TLF (formally WB4JFI)
?
? From: Mario
Roessler
Sent: Thursday, January 30, 2020 4:48 PM
Subject: [n2adr-sdr] charleston-sdr support ?
Hi, Mario |
charleston-sdr support
Hi, Mario |