|
|
Post by vk6cr on Jan 25, 2024 7:48:17 GMT
I set up JTDX/JTAlert and Log4OM so long ago that memory of it has faded. After being off-line for a while due to antenna problems, I connected everything (maybe) up again. For some reason I have lost CAT and nothing I can think of to fix it works. Software was not uninstalled, but an upgrade to Win 11 was. Serial port/USB convertor connected, port speed etc set.
I found a post that talked of setting up legacy items in Win 11, so I have followed that and created a COM3, but its showing an error: "This device cannot start. (Code 10)
this device which does not exist was specified."
Next suggestion I found was to download the latest Hamlib, which I also did and installed in the default directory.
Current setup: FT847, Win 11 Pro, JTDX 2.2.159
Could somebody suggest what (simple) thing I have missed? Audio is fine with the G4ZLP interface. 73 Ian vk6cr
EDIT JTDX error message is: "Hamlib error: IO error while opening connection to rig"
|
|
|
|
Post by Wolfgang OE1MWW on Jan 25, 2024 8:30:12 GMT
Ian,
not quite clear, how you connected the FT847 to your PC.
In the device manager (Win+R and enter devmgmt.msc) you should see the com port coming and going
if you power up/down or disconnect / connect the FT847. In the FT847 you have to set com speed
and the same settings msut be set in JTDX.
Do not 'create' a com port, Windows will assign it.
|
|
|
|
Post by Arvo ES1JA on Jan 25, 2024 8:30:35 GMT
Error message says all, com3 not working.
|
|
|
|
Post by vk6cr on Jan 25, 2024 8:50:09 GMT
Ian, not quite clear, how you connected the FT847 to your PC. In the device manager (Win+R and enter devmgmt.msc) you should see the com port coming and going if you power up/down or disconnect / connect the FT847. In the FT847 you have to set com speed and the same settings msut be set in JTDX. Do not 'create' a com port, Windows will assign it. There were no com ports showing in Device Manager. As changing to Win 11 is possibly the only variable, I searched and came across a piece about how to create Comm Ports for Win 11 and tried that.
Speed settings have been checked and are unchanged. Is there a driver needed? It really has been so long since I installed it all, haven't had to change it and I really can't remember the details.
EDIT: I have found an unknown USB Device for which it states "Device settings for USB\VID_0000&PID_0002\8&2efe0359&0&6 were not migrated from previous OS installation due to partial or ambiguous device match." Might this be the answer.
EDIT 2: Nope that wasn't it, uninstalled that USB device and removed the CAT serial/USB dongle . After a reboot it was still in Device Manager.
|
|
|
|
Post by w9mdb on Jan 25, 2024 13:20:04 GMT
|
|
|
|
Post by vk6cr on Jan 25, 2024 14:02:41 GMT
Thanks Mike, I'll try that utility in the morning. I've had odd messages when switching USB ports before, so worth checking. |
|
|
|
Post by vk6cr on Jan 26, 2024 3:50:15 GMT
Tried the UDSBDeview idea, but no progress. I think its down to the serial convertor device being incompatible or failing. Nothing on the device to identify the maker, so a blind alley.
|
|
|
|
Post by vk6cr on Jan 26, 2024 14:23:56 GMT
Researching this issue has rather opened my eyes to how things have moved on. Having used them for may years now, from the original days of Whisper, it might be opportune to acquire a more recent model of radio and look at other modes.
|
|
|
|
Post by w9mdb on Jan 26, 2024 14:26:09 GMT
Have you also removed anything in View/Show Hidden Devices?
|
|
|
|
Post by vk6cr on Jan 27, 2024 0:28:19 GMT
Have you also removed anything in View/Show Hidden Devices? I have now. There was a COM3 and a FTDI driver, which I think may have been either the testing of a Beast ADSB receiver or CHIRP.
UPDATE. Mike, I removed the 'hidden' COM3 and FTDI driver and then I reinstalled the driver. No advance, but next told it to do a driver update (which for once it searched and actually came back with driver updated) and Com3 popped up with the correct settings retained.
I think that's about all I did and now its working again.Thanks for the pointers.
|
|
