I haven’t tried it on Mojave, it was built on Big Sur using the 11.3 Platform API though so it’s quite possible that it won’t work.
I have now got an older version of Xcode installed which uses the 10.5 Platform API so is more likely to work on older versions. I wanted to do this anyway as we make extensive use of Qt in wfview and the latest version of QT5 is only tested with the older Platform API.
I will try to get it packaged-up and uploaded to the website soon.
Looking into this a bit further, The Platform API version matches the lowest version of Mac OS that the app will support.
The current build was using 11.3 of the API which is for Big Sur so it will not work on earlier versions
I have just compiled using 10.15 which is for Catalina. I will have a look to see if I can get on older version, say 10.13 which “should” work with all versions from High Sierra onwards.
What I don’t know though is if we will lose any functionality as the version of Qt that we are using is designed to use 10.15?
Unfortunately this is a more complicated fix as Qt have not yet released a version that supports Apple Silicon (M1) and wfview relies heavily on the Qt framework, I don’t have a date for when this will be available sadly.
I am using MacOS Mojave 10.14.6 and the May 18 build on MacOS and Win10 (server).
The rig is an IC-7410 working fine with Win10 WFview, incl rig control, as far as I can tell.
On the Mac the WFview app comes up nicely. The S meter works, and I can hear the rig RX audio. I am correctly logged in to the WFview server, but have no working rig control from the Mac. Frequency display is erratic, and often out of sync with the rig.
Band and frequency changes on the mac do not get copied to the server and rig.
CI-V Transceive is ON. The server (wfview on Win10) works fine, so assume the comms between the Win 10 server and IC-7410 works. The Mac app recognizes the 7410 in the bottom right of the screen.
You make a good point. If the server end of it is working, I’d expect any client to work as well. Hmm. And it shows IC-7410 in the bottom right, so you’re mostly there.
Actually, I think I know what it is. There is a bug, I will fix it. It has to do with the client side assuming the rig is a roaring-fast ethernet-connected radio, when in reality, it is peddling along at 19200 baud. We have to communicate between the server and the client for proper expectations.
I may “quick fix” this by just saying that we know which rigs are OEM-network and which rigs aren’t. Let me talk with Phil and see what he thinks would be best.
I believe we have fixed the bug(s) that you experienced. In a day or two you will see a new build for windows, mac, and linux, which addresses this issue.
I tested by using my IC-7300 set at 4800 baud, and I now can say this works really well. The s-meter is more fluid than before, and remote operation works very well. Tuning feels responsive despite the low baud rate. We now adjust the timing of our commands to the rig’s baud rate, even if the connection is over a network.
Hi Elliott,
Thanks for being responsive. I have upgraded the MacOS from Mojave to Big Sur.
That made a big difference and now I have rig control as well as receive audio.
Frequency synchronization between radio, Win10 wfview server and Mac client app is not quite stable. The timing adjustment to the rig baudrate that you mentioned for an upcoming build may fix that. Lookin’ forward to the new release.
That’s good news. I looked at the schematic for the IC-7410, and it has a genuine serial port inside, with separate TXD and RXD. If you keep “CI-V Echo OFF” then I think your experience will be pretty good.