electronics-tech wrote:First off, Scott, I do have lots of experience with DDutil. The problem I am having is that SmartSDR is supported BUT PowerSDR of any kind is not by Steve. He even told me so. So Thetis is also not supported. Well, at least to my knowledge.
That's just Steve's way of saying "I have no idea if any of this works with Thetis (it does) and I don't want to expend any effort to support my old work, I have moved on." Which is totally fair. But the old stuff does work with Thetis. Remember, it's all just CAT commands and the commands DDUtil supports for PowerSDR are the exactly the same in Thetis.
So, I tried one last time with 3.2.6.22. And no go. This is running on Windows 10 Pro-64 in Bootcamp on a high end iMAC core i7. Which runs all of my PowerSDR and VSP and VAC softwares.
With Bootcamp all bets are off. Steve did some weird stuff on the serial port IO and I've even had trouble with it on Windows from time to time. Whether or not it would work in Bootcamp is more than I can say. The classic serial comm's symptom with DDUtil is no connection to the radio.
Start the program and get it talking to Thetis. Thetis CAT port Comm 12 and DDutil Com11. You can see in VSP that it knows Thetis is there and and is attached to Com12 . However, NO Radio shows up in the DDutil panel.
And there you go: serial comm's problems with DDUtil. This has been an issue since DDUtil V3 was a baby, with PowerSDR, and when Steve did support it. I complained and he told me in no uncertain terms there was nothing wrong with it.
I've had much better luck using VSPE from Eterlogic because I found VSPM to be unstable. Again, something weird about how the serial comm's are implemented. I'm no developer, and nobody has access to the source for VSPM or DDUtil, so who can say exactly what might be wrong with it?
Then I go through the motions of installing the CIV-Comm adapter...
There's no point in that until you solve the radio connection problem.
To add insult. When I close DDutil. And re-start. It just crashes with a .Net Framework error, and I have to delete the config file again to start all over and end in the same loop.
I'm going to blame Bootcamp
I guess this is just not going to work Scott. Unless you have some words of wisdom here.????
Beg, borrow or steal a real Windows 10 machine. Make sure it is 100% up to date. Install VSPE. If you are super paranoid, install PowerSDR, but I'd just go with Thetis. You can also try going back in time a little further. Just grab an even older version than 3.2.6.22 from the directory I linked in the first post above.
But 3.2.6.22 should work. It works for me, I'm running it right now with Thetis.

- Capture4.JPG (689.05 KiB) Viewed 50290 times