With v1.4.16 I have to start SmartSDR two times to get the FlexControl to work. I down grade to v1.4.11 and it works like it should. In v1.4.16 this only happens when I shutdown the computer and 6300 and power supply. If I leave the power supply and radio on the FlexControl works first time when I start the computer. Anyone else seeing this? The FC shows up in Device Manger every time. I double check it before I state SmartSDR for the second time.
Thanks for helping
We believe it has something to do with how SmartSDR is detecting the presence of a FlexControl that is connected to your PC. We investigated it yesterday and will continue to look into it next week. At this point restarting SmartSDR or possibly disabling and re-enabling it in the Setup is how to mitigate the issue.
I am running WIN7 Pro 64. Flex control is on com12.
I notice in CAT that com4 / 14 is gone. Windows control panel sees it but not CAT.
I add a comport13 / 23 in CAT, reassign it and it turns to 4/14.
The part that makes no sense is that at this point the flex knob starts working.
Devil if I know, glad you're on the job Tim.
Lemme know what you figure out.
It must be a very intermittent problem. I had the same problem with the Flex Control not working on reboot of the computer and 6500 shut down... Attached it via DDUtil and all fine.. Went back to controlling it on SmartSDR and has worked just fine for 2 days now with reboots, etc..
So not sure myself what is happening, sure flex will get a grip on it..
73s Jim K4JAF
If I disable and enable the flex control driver in the device manager MMC then it's detected by SSDR the moment the device becomes active again and becomes usable.
However from power on the Flex control is not seen in SSDR, if you open the FC applet in SSDR it shows that the flex control is not present even when it is working as expected.
However and of interest DDUtil cannot take control of the knob as it says the com port is in use by another program - which I assume is SSDR even though it cannot use the control nor see its presence it has still flagged the port for itself.
No amount of reboots helps only the disable and enable the driver in the hardware MMC.
Turning of/on SSdr had no effect.
Unplugging the FC and replugging fixed it.
This incident happened just recently after I decided to download and play with ddutil for the very first time. The reason I downloaded it was simply to observe the termperature. So I fiddled with ddutil for a while then closed it and haven't used it since.
Windows 8.1 here...
Happened only one time and not since then.