开云体育

OK. Starting with quisk at 3903, as with previous tests, here's your first sequence: ~ $ rigctl -m 10 Rig command: f Frequency: 3903000 Rig command: F 7071000 Rig command: f Frequency: 7067000 Rig

So the next question is what if you keep rigctl runn? rigctl -m 10 f F 7071000 f f F 7072000 f f Does Quisk follow and you get the right answers every time? One other possiblity rigctl -m 10

This version adds more support for the Hermes Lite2 IO board. Jim N2ADR

Just for grins, I did a couple more combinations where I set quisk's frequency on its display and then tried a read-back from rigctl . Here's the sequence: Set quisk to 7072000, then: rigctl -m 10 f

Mike, This is interesting. I fired up the rpi P400 and quisk, and did what you asked, though quisk was initially at 3903000 rather than 7060000. The response was correct. I then followed that with

I can't duplicate the problem here.? I get the actual frequency Quisk shows every time. So what happens with this.... rigctl -m 10 f F 7071000 f I get this... rigctl -m 10 f F 7071000 f 7060000

Mike, I'm replying to your message sent before Jim responded. First, your command line didn't work. I'm guessing you meant this, " rigctl -m 10 -vvvvv -Z f >log.txt 2>&1". The log file from that is

I need to know what the problem is.....What's not working?? I'm lost now in this thread.

I downloaded Hamlib 4.6~git and built rigctl. I tested rigctl with my Quisk 4.2.22 using model 10. The "F" and "f" commands worked fine. This is still on Ubuntu 64-bit. I can alter Quisk's Hamlib code

Model 10 does not exist in Hamlib 4.3.1 It's in the latest....https://n0nb.users.sourceforge.net/ Mike W9MDB

I tested Quisk 4.2.22 with rigctl 4.3.1 on my Ubuntu 64-bit system using rig model 2 and the "F" and "f" commands worked fine. I tried using your model 10 but my rigctl reports that there is no model

rigctl -m 10 f -vvvvv -Z >log.txt 2>&1 And send me the log.txt file please. Mike W9MDB

There is another little factoid that may be relevant. It does not seem to matter how long one waits to enter the read-back command. I waited several minutes and did this again, having left quisk tuned

I'm sorry for the slow reply. Life sometimes interferes with ham radio ;-) The log is attached. FYI, at the time I issued your diagnostic command, quisk was tuned somewhere in the 80 meter band. Your

Two things you should be able to do.... #1 Run "top" to see which process is taking the most? CPU time #2 Run "strace" on the process ID to see what it is doing. Mike W9MDB

Interesting to hear you are seeing it on another linux version. I'm still working on it, but the most effective change I made was to lengthen the SSB TX delay a great deal. I'm using the maximum I can

Hi, I see similar behaviour on Fedora 37. If I hit the 'Tune' button in wsjtx for the first time the HL2 output power slightly rises from 0 up to 5 W in cca. 2 seconds or so. After that it works OK. I

OK, I've confirmed that if I Hide the Quisk window while running WSJTx (by minimizing it in the window manager), the problem completely disappears. I think something in Quisk's display routines is

Even More info: When I configured WSJTX, I failed to set the Mode in the Radio dialog to Data/Pkt. Doing so has very much reduced the problem. Now it only seems to occur the first time I transmit

More info: I've tried raising the Debug level from 0 With it set to 0, I always see the slow ramp up when I press Tune With it set to 1, I only see it once every few times - the rest of the time, full