Hit a brick wall on Page 1, Step 1, as I always do!
wfview Settings - I’m not seeing any auto discovery happening. No rig model number or CI-V address shown. I assume the rig has to be ON, but if wfview can’t find the rig how can it turn it ON…and if it’s not ON how can it find the rig?
Note: I am connected to my host computer in VE3 via Chrome Remote Desktop as I do the installation and setup.
BTW, no word on where to install the files; no Setup program. I copied everything from the unzipped folder into C;\wfview. Hope that’s OK.
Auto will ‘definitely’ not work on Windows as all it does is select COM1. This is something that we will improve in future releases as it is mainly geared towards Linux.
You are best to check the log file to see if the port is being opened correctly as it is possible that Win4icom is not closing the port?
It’s not considered good practice to create temporary files in the same location as the program which is why we put them in the default temporary directory.
It looks like you have ‘Connect over LAN’ selected which is designed for radios with Ethernet or WiFi. You need to select ‘Connect over USB’ to connect to a 7300.
Didn’t know I had to restart every time I saved settings. If it were me, I’d put a small note below the Save Settings button to that effect.
I’ve had USB connection set since I first opened the program. So what do I do with this logfile? Does more stuff keep getting added to it if I try again? Do I delete it and start again?
It’s not considered good practice to create temporary files in the same location as the program which is why we put them in the default temporary directory.
Consider adding a View Logfile button on the Settings page. Never heard of Powershell; had to Google it first.