开云体育

Hi Jim, For some reason the previous thread is locked. Below is the snippet with the change from reply[0] to reply but with the parameters being used. Quisk eventually fails. The Quisk output file is multus-out (attached). Please keep in mind that Quisk runs fine if the print ("TransferIn got", reply) is commented out. I can live without the print statement as it only used for debugging purposes. The question is how do I signal Quisk to go into TX mode, turn on the PTT button and set the button directly to the right of it to TX def PollCwKey(self): # Called frequently by Quisk to check the CW key status global ptt_count global ptt_on # now = datetime.now() ptt_count -= 1 if ptt_count == 0: # print(now) reply = self.TransferIn(0xA5, 1) #INTERROGATE THE STATE OF THE MULTUS PTT SWITCH ptt_count = 200 print ("TransferIn got", reply) return # Quisk is always in Rx Below is the snippet with the parameters commented out and unused. Quisk fails. The Quisk output file is multus-1.out def PollCwKey(self): # Called frequently by Quisk to check the CW key status #global ptt_count #global ptt_on # now = datetime.now() #ptt_count -= 1 #if ptt_count == 0: # print(now) reply = self.TransferIn(0xA5, 1) #INTERROGATE THE STATE OF THE MULTUS PTT SWITCH #ptt_count = 200 print ("TransferIn got", reply) return # Quisk is always in Rx 73, Ron

Hi Folks, Jim was very gracious and provided the code modifications to integrate our product (Multus SDR, LLC. - Proficio Mark II) into Quisk. The rig functions perfectly particularly in CW mode. The Mark II has a built in CW keyer and Jim did a great job of allowing the rig to be QSK capable. The Mark II also has a PTT connector so that a switch (foot switch, etc) may set the rig into TX mode. This was not implemented so I have decided to attempt to do implementation. Jim's implementation of CW polls the rig to determine if the key is active via polling the rig via its USB connection. I need to do something similar to poll the rig to determine if the PTT connection is active. Jim provided the basics of do this and it works as I can see the rig being polled when I put the rig firmware into debug mode. OK, I have almost zero experience with Python. I am an old school C programmer with some C# experience. We (Multus SDR) have our own application called MSCC which is a combination of C# (for the GUI) and C for the back end servers, but for a number of reasons we are dropping support which I will not bore you with in favor of Quisk. Quisk is now our preferred SDR host application. So, I am asking for help with implementing the PTT function. I have included our quisk_hardware.py file. The short of what needs to be accomplished is Quisk needs activate the PTT button and display TX in the button immediately to right of it. Also Quisk needs to placed into TX mode. The question is: how do I do that? Below is are snippets of the hardware file where Quisk is polling the rig for the state of the PTT connection. I have "piggy backed" on the function Jim provided for polling the rigs CW key connection. I admit this might be the completely wrong place to do this, but it does work for polling the rigs PTT connection. previous_ptt = 0 ptt_count = 200 def TransferIN(self, address, message): # If message is an int, convert it to bytes if isinstance(message, int): message = message.to_bytes(1, 'big') # Here, message is mutable (bytes), so we can modify it if self.usb_dev: # Assuming IN is defined somewhere as a constant for the direction result = self.usb_dev.ctrl_transfer(IN, address, self.si570_i2c_address + 0x700, 0, message) # Update message with the result if needed message[:] = result # This updates the original message in place return message # Return the potentially modified message def PollCwKey(self): # Called frequently by Quisk to check the CW key status global previous_ptt global ptt_count ptt = bytearray(1) # Start with a mutable bytearray ptt_count -+ 1 #NO NEED TO POLL THE PTT CONNECTION AS FAST AS POLLING FOR THE CW KEY if ptt_count == 0: self.TransferIN(0xA5, ptt) # ptt will be modified in place. THIS IS WHERE QUISK POLLS THE RIGS PTT CONNECTION #IF PTT EQUALS ONE (1) PLACE QUISK INTO PTT MODE (AND TURN ON THE PTT BUTTON AND DISPLAY TX IN BUTTON NEXT TO IT #IF PTT EQUALS ZERO (0) TAKE QUISK OUT OF PTT MODE ptt_count = 200 #if ptt != previous_ptt: #print ("PTT") #print ("ptt:{}, previous_ptt:{}".format(ptt, previous_ptt)) #previous_ptt = ptt[0] return # Quisk is always in Rx Thanks, Ron W4MMP

Hello all, I must be doing something wrong. Between Thetis and Quisk, the reception and quality of filters are several orders of magnitute greater on Thetis. So much so, that I can't imagin anyone using Quisk over Thetis. However people do use Quisk, so I must be doing something wrong. A station that I can hear clearly and without any noise on Thetis, will have very poor signal to noise ratio on quisk. Also, if I try using NR2 (why is there no NR1?), the signal will be distorted beyond understanding and turning NR2 off again will do nothing, so I have to restart Quisk to remove the distortion from NR2. If I click NB and choose 1, 2 or 3, nothing happens at all. It is as if the button doesn't work. If, however, I choose SNB, I get the same kind of distortion I get from NR2 and I will have to restart Quist to remove it. I like Quisks interface and would like to use it instead of Thetis, so I would appriciate any help in resolving this Hardware: Hermes Lite 2 with n2adr and IO board Lenovo P50 laptop Software: Windows 10 and Quisk version 4.2.38 Thanks Peter

I just install quisk on a linux ubuntu 24lts with the same "quisk_settings.json" file as on my windows computer. ( actually, using a HL1 prototype ) On windows , NR2 works well, on linux, the button stays black. Any adjustment to do ?

This is a bugfix release. I fixed a bug in the Hamlib serial port when using a physical TTY instead of a pseudo-tty. The Hamlib ZZFA command now changes the receive frequency instead of the transmit frequency. I fixed some window sizing issues. Jim N2ADR

Quisk now has a new option "Fixed tune offset" on the Config/radio/Options screen. This is meant for Softrock radios that need a constant audio frequency to simplify amplitude and phase corrections. The value zero means no change to Quisk tuning. Otherwise enter the fixed frequency offset from center. If you are using the obsolete "mouse_tune_method = 1" please delete it and use this new feature. If you use softrock_tune_vfo.py as your hardware file, you should replace it with softrock/hardware_usb.py. Quisk now works on Python 3.12. And I fixed a bug in the small screen graph width. Jim N2ADR

Hi, This is most likely my first post to this group. We (Multus SDR) are moving to Quisk for our preferred SDR host application for a number of reasons, among them the cross platform capabilities. This leads me to the question I have. For at least one of our products we have implemented an embedded RPi 4 (or 5). Raspberry has moved to using the back end Wayland platform for the desktop. Question: Does Python3 / Quisk play nice with Wayland? There is a configuration option to have Raspberry O.S. (bookworm) to revert to using X-windows. (Note: We are currently testing Quisk on a Raspberry Pi Zero 2 (bookworm) that only supports X-windows due to its hardware complement. Quisk is running OK on it (just a bit slow). The point is Quisk runs fine on bookworm with the X-windows back end). So, once again, does Python3 / Quisk play nice with Wayland? Regards, Ron

I've created a hardware file for the HL2 controlled by an ICOM RC-28 remote encoder: https://github.com/haklein/quisk-hl2-rc28/blob/main/hermes_hardware.py Maybe that's helpful for someone else, too, 73 OE6HKE

Hi All, Just a quick note of praise to Jim, N2ADR, about Quisk. Over the years I’ve used Quisk on Windows and Linux with success but it has never been a quick and easy process. Connecting digital apps was also somewhat challenging. I haven’t used Quisk in a while but with the IQ balance adjustment available for softrock type radios I decided to give it another go on windows. I must say setup was a breeze other than one issue I’ll cover below. Setup and configuration of WSJT-X and Fldigi went smoothly following the directions. IMHO Quisk has become a mature and capable program that I’ll be recommending to folks. The only issue I had was with how you install WSJT-X. Way back many years ago I was told to always install WSJT-X and WSPR to the system path. I don’t remember the reason now but that is how I’ve done it for many years. The issue is, if you have WSJT-X installed to the system path and you try and run Quisk with a softrock type radio, Quisk will not load. Quisk was working until I installed WSJT-X so I uninstalled it and reinstalled using default path and Quisk worked normally again. Thanks again Jim for your many years of developing Quisk into a very capable and easy to use program! -- 73, Stew N8VET

I have tried all of the normal clicks and keys to fill in the address settings and cannot cause anything to enter. I am using a laptop and cannot figure this out. Thanks Ron Mathis W0RGM

I added two new color schemes by Michael, DK1MI. The On/Off button color and text color can now be configured. (Michael, send me the final colors). There are a few other small changes. Jim N2ADR

Hi All, Latest Windows. Completely updated. My x220i crashed so I updated. System: Device name xxxxxxxx Processor 13th Gen Intel(R) Core(TM) i7-1365U 1.80 GHz Installed RAM 32.0 GB (31.7 GB usable) Device ID 9C63A6CE-DF50-48F2-964E-4FCAEXXXXXX Product ID 00355-61526-85347-AAOEM System type 64-bit operating system, x64-based processor Pen and touch Touch support with 10 touch points All install works fine: python -m pip install --upgrade pip python -m pip install --upgrade setuptools python -m pip install --upgrade wxPython python -m pip install --upgrade pyserial It completely fails on next: python -m pip install --upgrade quisk I have the VC environment installed: VS 17.10 with libraries. No problem. I could spend hours fixing this, but I figured I would try here first. Here is log from windows power shell : PS C:\Users\guy> python -m pip install --upgrade quisk Collecting quisk Using cached quisk-4.2.35.tar.gz (5.1 MB) Installing build dependencies ... done Getting requirements to build wheel ... done Preparing metadata (pyproject.toml) ... done Building wheels for collected packages: quisk Building wheel for quisk (pyproject.toml) ... error error: subprocess-exited-with-error <<<<<<<<< Error and see end. odd × Building wheel for quisk (pyproject.toml) did not run successfully. │ exit code: 1 ╰─> [131 lines of output] running bdist_wheel running build running build_py creating build creating build\lib.win-amd64-cpython-312 creating build\lib.win-amd64-cpython-312\quisk copying .\configure.py -> build\lib.win-amd64-cpython-312\quisk copying .\dxcluster.py -> build\lib.win-amd64-cpython-312\quisk copying .\filters.py -> build\lib.win-amd64-cpython-312\quisk copying .\midi_handler.py -> build\lib.win-amd64-cpython-312\quisk copying .\portaudio.py -> build\lib.win-amd64-cpython-312\quisk copying .\quisk.py -> build\lib.win-amd64-cpython-312\quisk copying .\quisk_conf_defaults.py -> build\lib.win-amd64-cpython-312\quisk copying .\quisk_conf_kx3.py -> build\lib.win-amd64-cpython-312\quisk copying .\quisk_conf_model.py -> build\lib.win-amd64-cpython-312\quisk copying .\quisk_conf_openradio.py -> build\lib.win-amd64-cpython-312\quisk copying .\quisk_conf_peaberry.py -> build\lib.win-amd64-cpython-312\quisk copying .\quisk_conf_sdr8600.py -> build\lib.win-amd64-cpython-312\quisk copying .\quisk_conf_sdriq.py -> build\lib.win-amd64-cpython-312\quisk copying .\quisk_conf_win.py -> build\lib.win-amd64-cpython-312\quisk copying .\quisk_hardware_fifisdr.py -> build\lib.win-amd64-cpython-312\quisk copying .\quisk_hardware_fixed.py -> build\lib.win-amd64-cpython-312\quisk copying .\quisk_hardware_hamlib.py -> build\lib.win-amd64-cpython-312\quisk copying .\quisk_hardware_hl2_oob.py -> build\lib.win-amd64-cpython-312\quisk copying .\quisk_hardware_model.py -> build\lib.win-amd64-cpython-312\quisk copying .\quisk_hardware_sdr8600.py -> build\lib.win-amd64-cpython-312\quisk copying .\quisk_hardware_sdriq.py -> build\lib.win-amd64-cpython-312\quisk copying .\quisk_utils.py -> build\lib.win-amd64-cpython-312\quisk copying .\quisk_vna.py -> build\lib.win-amd64-cpython-312\quisk copying .\quisk_wdsp.py -> build\lib.win-amd64-cpython-312\quisk copying .\quisk_widgets.py -> build\lib.win-amd64-cpython-312\quisk copying .\softrock_tune_vfo.py -> build\lib.win-amd64-cpython-312\quisk copying .\__init__.py -> build\lib.win-amd64-cpython-312\quisk copying .\__main__.py -> build\lib.win-amd64-cpython-312\quisk creating build\lib.win-amd64-cpython-312\quisk\n2adr copying .\n2adr\conf1.py -> build\lib.win-amd64-cpython-312\quisk\n2adr copying .\n2adr\conf2.py -> build\lib.win-amd64-cpython-312\quisk\n2adr copying .\n2adr\conf3.py -> build\lib.win-amd64-cpython-312\quisk\n2adr copying .\n2adr\conf3A.py -> build\lib.win-amd64-cpython-312\quisk\n2adr copying .\n2adr\conf4.py -> build\lib.win-amd64-cpython-312\quisk\n2adr copying .\n2adr\conf5.py -> build\lib.win-amd64-cpython-312\quisk\n2adr copying .\n2adr\conf6.py -> build\lib.win-amd64-cpython-312\quisk\n2adr copying .\n2adr\conf7.py -> build\lib.win-amd64-cpython-312\quisk\n2adr copying .\n2adr\hl2_

Will someone point me to the documentation on a new install of Quisk on Ubuntu 24.04. Thanks Ron Mathis W0RGM

There is a new item "File play level" on the Config/radio/Sound screen to reduce the volume when playing files. Use it to reduce the volume of the CQ message relative to radio sound. Dan, AI2M, provided a patch to compile in MacOS on Apple Silicon. Thanks Dan! I am working on better amplitude and phase adjustments when using SoftRock radios. The new corrections screen has a spreadsheet to display the VFO and tune offset. And there is a feature to automatically measure the corrections when using a signal generator as a source. If you use Quisk with SoftRock or similar radios, please let me know what you think. Jim N2ADR

Last Friday (7/12) I was attempting to set up static ip addresses on my HL2 & Laptop-based Quisk. I tried various combinations using the IP related fields: “Hermes Known IP”, “IP Change”, “Eeprom IP usage”, “Eeprom IP Address”. While it appeared that the static address in the HL2 took, Quisk was never able to connect using static addresses. I was successful at getting APIPA to work (269.254.x.x addresses) but never on static. I was routinely able to get quisk to find and control the hl2 using APIPA. Late Friday I shut down the HL2. Early this week I tried again but found I can no longer connect via ethernet to the hl2. I see the link light and some activity light but Quisk never finds the HL2. Also, the frequency of the activity light is much diminished from what I’ve seen before. Also, several fields that I was seeing last Friday no longer appear in the Config | HL2 tab. Specifically “Eeprom IP Usage”, “Eeprom MAC usage”, “Eeprom IP address”, “Eeprom MAC Address” are missing. Hermes code version and board ID have not changed. What could be wrong? Is there a way to reset the HL2 and/or rewrite eeprom? Do I need to rewrite the FPGA (without ethernet since it won’t connect). Do I need to blow away and reinstall quisk (I’m on version 4.2.31; current version is 4.2.35 so I’m pretty up to date).

For the Hermes-Lite2 the inhibit Tx function (CN8) now releases the Spot button. Quisk displays the band plan below the X-axis as colored bars, and there are eighteen possible colors. If you hover the mouse over a bar, Quisk now displays the name of the mode. Recall that there is a dialog box so you can set the band plan to what you want. Jim N2ADR