开云体育

Hi Jim, I hooked up a MIFI unit to emulate a real life internet connection, but it did not work out. All forwarding was set as laid out in the Remote documentation, but to no avail. I called the MIFI (server) using its URL as well as the actual WAN IP address, but no succes. The round trip delay is fairly high, 50 to 200 ms, hence I wonder if that could be the cause why connection was not established? 73s, Peter, PA3BIY

Hello all, I just joined the group. I had bought the hiqtrx with the Hiqsdr board quite a few years ago and got distracted back then. I’m dusting it off and want to program the flash memory with new programs for the FPGA. I know I need a usb blaster and a special cable. Do I need to make up that cable myself? Can someone help me out with part numbers and pin outs? TNX, Jeff - W1NC

Hi Jim, While setting up a control head, I cleared all the band buttons, as the control head needs to serve as a pandapter (I have more questions how to connect to the remote unit using just the HiQSDR platform, but I think I should ask Ben). After I cleared the band buttons and restarted Quisk it crashed (it won't start at all) with this message: Traceback (most recent call last): File "/usr/local/lib/python3.8/dist-packages/quisk/quisk.py", line 4093, in OnInit self.bandBtnGroup.SetLabel(self.lastBand, do_cmd=True, direction=0) File "/usr/local/lib/python3.8/dist-packages/quisk/quisk_widgets.py", line 1423, in SetLabel self.RbDialog.RbGroup.SetLabel(label, False) File "/usr/local/lib/python3.8/dist-packages/quisk/quisk_widgets.py", line 1223, in SetLabel func = "%s.SetLabel" % self.idName AttributeError: 'RadioButtonGroup' object has no attribute 'idName' OnInit returned false, exiting... I have purged Quisk and re-installed, but to no avail, it keeps crashen. Any clue how I can reset Quisk? 73's, Peter, PA3BIY

Hi Jim, My colleague Ed Murphy (GM3SBC) and I have been developing the Globemaster SDR over the past few years (more info here). We have been using Quisk 4.1.41 for some time now, although we're very keen to upgrade to 4.2.9 to take advantage of new features such as remote operation. The Globemaster hardware handles the CW modes - keyer detect (iambic or straight modes), semi break-in, auto tx/rx change over etc. To achieve this we configure Quisk in receive mode, full duplex, with the sidetone going out on the transmit channel. The Globemaster then modulates the sidetone in line with the CW keyer and mode. During CW transmission the receive channel is muted by the Globemaster and unmuted when the CW keyer is inactive. Our support file invokes the QS.set_fdx(1), QS.set_key_down(1) and QS.set_transmit_mode(1) when the Quisk mode changes to CWU or CWL. This works well, with Quisk outputting a continuous sidetone on the transmit channel whilst simultaneously receiving. With Quisk 4.2.9 this no longer works, the set_transmit_mode() method is no longer available, we have tried XXset_transmit_mode() but so far we have not been able to get a stable sidetone on the transmit channel. We have occasionally observed a sporadic sidetone during debug, but this hasn't been repeatable, but it does indicate that a stable sidetone might be achievable. Any help you can provide to assist with our debug would be greatly appreciated. Kind regards Andy

Hi all, As others have confirmed, WSJT-X seems to work well running on the Control Head (operator's) computer. I'm a newbie with WSJT-X, so I've been timid about Tx, but Rx seems to work well (I tried WSPR, FT8, FT4) and I've tried brief Tx with WSPR on 80m with Hermes Lite 2. From my East Coast USA station, my sig was detected as far away as West Coast USA and Europe ... cool! A couple of bugs -- On Linux Ubuntu desktop, I connected WSJT-X to Quisk via WSJT-X settings Radio->Rig "Hamlib NET rigctl", Network Server "localhost:4532", with PTT set to "CAT", and Audio->SoundCard set to Input "QuiskDigitalOutput.monitor" and Output "QuiskDigitalInput" (both mono) ... This (basically) works well, however: 1) Hermes Lite 2 band filters are (apparently) not switched when WSJT-X changes bands, even though Quisk's band buttons respond properly on both Control Head and Remote Radio. Symptom: When changing from lower frequency band to higher frequency band, Rx signals are severely attenuated. Workaround: Click on Control Head Quisk's (correct) band button once after changing bands using WSJT-X; healthy Rx signal level returns. 2) WSJT-X "Tune" button has no effect on Quisk. THANKS!! -- Ben, AC2YD --

I improved the Config/Config and Config/TxAudio screens and added help buttons for all items. The File Record button no longer overwrites an existing file. It creates a new file each time it is pressed. Enter a base name and the files will be base001.wav, base002.wav, etc. Decide on a directory for these files, perhaps the Music directory on your computer or a special directory. Files will accumulate there, and must deleted. The File Play names will follow the File Record names so that pressing Play after Record plays the current recording. I had to change a lot of logic for this, and there may be bugs. So please test. I fixed some bugs in the new Quisk Remote feature by Ben, AC2YD. The Spot slider is now initialized. I fixed the bugs in the Split feature. Please test, and if there are any remaining bugs, please report them. I will add a feature to reduce the sample rate from 48 ksps to 8 or 12 ksps as the next step. I didn't add it now because it may cause problems. Maybe it will increase latency, or the added processing will be too much for a Raspberry Pi used as a remote. Jim N2ADR

I'm now up and running with remote Quisk. It works amazingly well and are very, very easy to set up! I will not be able to use it efficiently at my remote site where I use 4G cellular connection in the outskirts of the cell tower coverage though as the bandwidth of 1.7MBit/s in both directions will both be more than my available bandwidth from time to time and will also eat my limited data available. My plan is to replace this rig with my HL2 when possible to get the more competent rig at home. I use WFView today to control an IC-7300 which uses opus 1ch codec with very good both latency and quality. The bandwidth for the entire remote control is around 120kbit/s which is very more what my connection will cope with. I have also previously used mumble to transport the audio on the side which also had low bandwidth codecs with very good audio quality if the settings are correct. My questions are if there are soon to be a more efficient coding planned to implemented for Quisk remote or if it would be possible to locally route the audio at the remote site somehow via an external program such as mumble to manually reduce the bandwidth? Bj?rn SM0SBL

I have been really excited by the new remote operation functionality. At last I can use my HL2 fully :o) I have set my radio up using the remote_hermes.py at the remote site connected to my HL2 and the control_hermes.py at my client computer. Everything seam to work except for the NR2 button. On my remote site the NR2 button is whited out. It is 'pushed' at the remote GUI when I 'push' it locally but nothing happens and I cannot 'push' but NR2 button on the remote GUI at the radio. Is this a known issue or something I have not set up correctly? I'm running 4.2.9 at my local Windows and 4.2.8 at my remote Raspberry. Maybe this is my problem even though I don't see any notes about this? I think my main problem is that the Raspberry that is actually controlling my radio does not support NR2 for some reason. If I control my HL2 directly from my windows laptop the NR2 button really activates something but the sound is as it was piped through a long plumbing pipe and it does not get back to normal when turning NR2 off again. I need to restart Quisk to make the audio sound good again. My remote is on a Raspberry PI running HamPi and my local is Windows 10

Hello group, I want to take the next step and access my Hermes-Lite via the internet and have absolutely no experience with this. I am happy to do the learning necessary to set my self up but would appreciate if someone could guide me to the first step of deciding the best way to approach this. Should I do this via VNC or will the encryption latency be too great? Perhaps ddns might be the best approach and like all hams I like a freebie so are there too many fishhooks in the free sites and should I take a subscription? Maybe there is yet another approach that I have not thought about or someone knows of a web site where the procedure has been well explained that I could follow. I would appreciate any information that I can get. 73, Graeme ZL2APV

This is an update to the new Quisk Remote feature by Ben, AC2YD. I fixed the problem with the favorites screen and the station buttons below the X-axis. I fixed the "Failure in OnFreedvMenu" bug. Jim N2ADR

Found in 4.2.9 (but likely present in earlier releases): I stopped the Control Head (Win 10) by clicking the "On" button ... as expected, the remote connection closes, radio sound stops, and graph and waterfall freeze ... When I click the "On" button again, things reconnect, radio sound comes through, but the graph and waterfall disappear, and all the front panel buttons appear in the top of the Quisk window. Also, on the Remote Radio (RaspPi 4 HLT2), I see a debug message on the Remote Radio saying "ERR_UNRECOGNIZED_CMD: On;0" I am happy that the remote radio does *not* turn off when I click the Control Head "On" button ... It's rare that I do such a thing, and I want the Remote Radio to stay on and available ... I was just trying to pause things to read a debug message. -- Ben, AC2YD --

Found in 4.2.9 (but likely present in earlier Remote Quisk releases): Remote Quisk Split mode (CW-U) transmits on the Rx frequency (I got caught by the "DX Frequency Police" for D60AE!). Work-around: Click "Reverse Rx and Tx" twice ... this works while in Split mode, but then when leaving Split mode, the radio is tuned to the Split Mode Tx frequency, rather than the un-split Rx/Tx frequency ... Workaround: tune to a new frequency. Also, the Remote Radio Split button label gets out of sync with "Lock Tx Frequency" checked state ... if checked, button shows "Split" ... if unchecked, button shows "LkSplit". Control Head Split button label properly tracks "Lock Tx Frequency" state. -- Ben, AC2YD --

This is an update to the new Quisk Remote feature by Ben, AC2YD. Please test. Midi now works with the control head. For HermesLite2, the RfLna is correctly initialized. I changed the ports to 4585:TCP control; 4586: graph data; 4587:radio sound and mic. This should work correctly with NAT. The main documentation page docs.html which is available from the Help button now describes the remote feature in more detail. Jim N2ADR

As thetis got TCI support recently, I was wondering if there are any plans to provide a TCI interface in quisk. This would e.g. allow to use the SDC CW skimmer on Linux, or JTDX without any loopback audio devices. TCI is a simple rig control protocol on top of a websocket, and can also transport I/Q samples. It seems to gain traction beyond expert electronics recently, e.g. the RF-Kit Amp also supports TCI. 73 OE6HKE

Hi all, I'm attaching the Remote Quisk prototype/development design doc I mentioned in recent email, to make it easier to find. It includes some considerations for using WiFi (especially, eliminating periodic background scans for APs; these interrupt data flow by tuning away from the WiFi channel in use!), including some software tools that I found to help analyze WiFi performance. I wrote it originally in mid-2021, sent it to [email protected] at that time, then updated it in May 2022, and sent that update to Jim. NOTE: The document was written before Jim integrated my development prototype into Quisk ... you may find some discrepancies with Jim's exact implementation, especially since we are going through some debugging changes ... however, quite a bit of the document is helpful for understanding how it works. I'm very grateful to Jim for integrating this capability into Quisk!! -- Ben, AC2YD --

This is an experimental release to test the new Quisk radio remote control software written by Ben Cahill, AC2YD. This allows Quisk running on a local PC to control a remote radio. The remote radio is connected to a PC also running Quisk. Ben has tested this on SoftRock CW operation. The current test version supports SoftRock and HermesLite2. Jim N2ADR