CIV Transceive was on. It is now responding after I disconnected and reconnected the USB cable. Maybe the USB port was still allocated to the previous program.
I am having issues connecting my Win 10 machine to the 7300. I have the RT systems rt-42 USB cable. Same one that I use for the programming of the 7300. I cannot seem to get the radio and the program to communicate. I have followed the getting started portion of the manual and there is no comms. Is there an issue with that RT42 usb cable that is not compatible?
The RT-42 is just a standard USB cable so it should be fine. Can you check the Windows Device Manager? If you right-click on the Windows āstartā button, you can select Device Manager.
Under Ports (COM & LPT) you should be able to see the device called something like āSilicon Labs CP210x USB to UART Bridgeā. After the name, it should say (COMx) and that is the port you need to select in wfview.
I am seeing the same thing on my ICOM 7300 with my Windows 10 machine. I have the driver installed and WSJT-X works fine and Iām able to control the rig with it. I donāt have it open when I try to use Wfview and I only get the blue and green circle on the bottom bar after setting the COM Port explicitly. This was after I got the app to successfully work on my M1 MacBook Pro with the Universal Binary without changing any rig settings. I did power cycle the rig just to make sure nothing else was strange after that.
I see from the other thread that you got it working by factory resetting your IC7300. If you are using WSJT-X then it is most likely because Hamlib is disabling CI-V transceive mode on your rig. This needs to be enabled for wfview to work.
Ok. I was able to get it to work on Windows 10 by turning CI-V transceive off, power cycling the radio, turning CI-V transceive on and power cycling the radio one more time. Iām not sure if those power cycles were necessary, but I was able to control the rig remotely after that. After using wfview and using the radio I was unable to connect to the Com Port with WSJT-X after that without power cycling the radio. This program looks awesome though and I look forward to it getting better and better.
ā
I have to edit this post as Iām a new user and it wonāt let me reply again so I hope you see this.
I manually set my baud rate to 115,200 on the 7300 and after running WSJT-X I have to disconnect / reconnect the rig for Wfview to connect the rig. No power cycling is necessary. After running Wfview, I get āRig Control Errorā trying to open WSJT-X. The error is:
Hamlib error: Command rejected by the rig
set_cache_freq: set VFR=VFOB to freq=0
So it seems like neither program leaves the radio in a workable state for each other. Is this something that I could build the app locally and get you and additional debug info? Would that be helpful?
Hi! I just downloaded wfview to my Win10 computer and tried to use it with my IC-7300. Wfview does not see the rig. I successfully use WSJT-X, Logger32, and MMSSTV over the USB connection with no problems. I have tried all of the things mentioned in the dialog above to no avail. Any further suggestions?
Yes. I also tried the suggested sequence of turning off the rig power between changing those settings. It was in the ON mode when I started, BTW. I saw the note about that on the web pages and checked it before installing wfview. I also tried rebooting the computer. The USB drivers are installed and look correct.
There is one difference in my IC-7300 setup and the settings in your slides. You have CI-V USB Port set to āUnlink from [REMOTE].ā Mine is set to āLink to [REMOTE].ā I changed that setting, but still no connection to the rig from wfview. However, all of my other apps stopped working properly. I changed it back to my previous setting.
You have to unlink first, and then it will actually let you set the baud to 115200. If it is set to ālinkā, then it wonāt actually set the baud.
The newest firmware for the 7300 defaults to āunlinkā for this reason, but if you ran your rig prior, it stays at whatever setting you have used before. So try setting the UNLINK and then set the baud rate and see what happens.
The baud rate was set to 115200 when I tried it in UNLINK mode in my previous message (I failed to mention that). And no other programs are running that would access the rig port. At one point I rebooted Win10 to make sure there wasnāt some befuddled port locking mechanism. Iām happy to work with you to debug this, so please let me know anything youād like to try.
We are probably at the point of checking the log file, Log file | wfview shows how to view it. You are mainly looking for lines headed āSerialā as we want to make sure wfview is opening the serial port successfully.
That is telling us that wfview couldnāt open the serial port. Are you certain that nothing else has the serial port open? Omni-rig can often be a culprit here, if you have any programs that use it, Omni-rig will connect to your rig(s) in the background.
This is really weird. I just relaunched wfview and it started working. I have changed nothing since the last attempt. Will play with it and let you know how it goes.
Don
P.S. here is the log data for the startup that worked in case it is of use to youā¦
2021-05-11 18:53:33.831 INF system: Starting wfview
2021-05-11 18:53:34.944 DBG system: Loading settings from ā\HKEY_CURRENT_USER\Software\wfview\wfviewā
2021-05-11 18:53:34.975 DBG gui: Got Audio Output: āDefault Output Deviceā
2021-05-11 18:53:34.975 DBG gui: Got Audio Input: āDefault Input Deviceā
2021-05-11 18:53:34.990 DBG default: Getting server config
2021-05-11 18:53:34.990 DBG default: setState 1
2021-05-11 18:53:34.990 DBG default: setState 0
2021-05-11 18:53:34.990 DBG default: setState 1
2021-05-11 18:53:35.189 DBG serial: Opened port: āCOM3ā
2021-05-11 18:53:35.189 DBG serial: Could not open pseudo terminal port, please restart.
2021-05-11 18:53:35.314 DBG system: Received CommReady!!
2021-05-11 18:53:35.330 DBG rig: Using incomingCIVAddr: (int): 148 hex: 94
2021-05-11 18:53:35.330 DBG rig: Have rig ID: decimal: 148
2021-05-11 18:53:36.417 DBG system: Could not find modulation input: 2
2021-05-11 18:53:37.617 DBG system: Could not find modulation input: 2
2021-05-11 18:53:38.711 DBG rig: Received 0x15 center span data: for frequency 2500
