I upgraded from 2.01 to 2.03 this morning and lost the ability to TX both from FLDIGI and JTDX. RX continues to work fine. WFview PTT can still activate the radio for TX, but neither third party software can activate the radio.
Can you please enable debug logging and rigctld logging in the Log window of wfview, attempt key and unkey via an external program, and then press “send to termbin” and of course paste the url returned to your next support forum post?
Sorry, didn’t mean WSJT-X, JTDX. I just show a lot of traffic, much faster queries than is really useful. Around 10-15 times per second but sometimes in bursts (1ms apart) it seems. Can you see if you can lower the rate of polling?
@phil
The command being sent seems to be “T VFOA 1” and “T VFOA 0”
WSJX will TX, but I had migrated away from it because it doesn’t seem to like Pipewire.
Frequency readings for JS8Call nor FLDIGI are not updating to match WFView. These two will no longer activate the WFView TX either.
Since your reply, In JTDX I’ve tried decreasing the polling speed, I’ve disabled split and tried to fake it, set mode to none & data packet, but I have had no luck. JTDX “Text CAT” shows green, but PTT does nothing to WFView.
Using the Test PTT in JTDX triggers a hamlib vfo parameter error.
This means the audio device selected on your computer is not correct. Please try some other audio devices available in the audio device menu. You may need to change the mic gain using your PC’s audio settings.
PS: You can see movement on the TxAudio meter even when you are not transmitting. So you will be able to see pretty quickly once you have it set correctly.
I tried my laptop audio input device using every device available (microphone, loopback1, loopback2), and although the computer’s audio meter responds to the hardware device setting, WFView does not move in any of these three settings.
To be clear, in the WFview setting do I need to use a different input loopback device than hw:loopback_1, dev 0? Or are you asking me to change my laptop’s input device setting?
Furthermore, would my laptop’s audio setting explain why my third party apps are getting the VFO error?
And again, thanks everyone for the help. I was preparing for Winter Field day thinking updating software would be helpful, not expecting to encounter a different set of puzzles.
The JTDX app sends a command we did not know at the time we created version 2. You’ll just have to wait for us to add that command into wfview before it works.
As for the input device in wfview, my recommendation is that you begin by setting it to your computer’s microphone and just verify that it works. You have to disconnect from the radio, select the audio device that looks the most like “microphone” and then connect and try to speak and see that audio meter move. If it does not move, you likely have the wrong device selected and/or improper mic gain within your operating system. On my linux system, I can usually select “Default” and get the mic.
If you want to send us a log file we can look at the audio devices and help you figure out which one is probably the microphone.
Once you get that working, then we can try the loopback devices. You need two devices, one for transmit and one for receive, and yes, it is hard to tell which is which. If you figure out how to name them, let us know!!
Hello All.
Yesterday I checked the mode on Radio and WfView, both un USB-D1. No Tx in digimode.
did we need to exchand any menu in radio, to TX digi in REMOTE?
About CW speed, I check also and see this:
We exchange the speed in software, take efect on radio, but the speed still the same in software.