No Cat, no FLDGI read
Posted: 07 Feb 2015, 16:32
Good morning everyone
I'm having difficulty and can't seem to dope it out. Running yaesu 857d, Log4om, fldigi, Windos7 Home Premium, and using a RT systems USB 62 cable to the radio. I can't seem to get Log4om to read the log in fldigi and bring it over so that QSOs can be sent to qrz, eqsl and eventually LOTW. The path to fldigi should be correct, communicator should be configured, log4om should be running as an admin. The comm port should be correct (comm3). My guess is that the comm setting is that something in windows is off but I need a few ideas on what to double check and or look into.
Likewise, no cat control. Cluster does work fine, communicator is started and everything, omni rig seems to be running, omni should match fldigi and log4om. 857d is set for cat under menu 20.
I would appreciate any advice. This will be great once it is up and running - I've never used logging software before (new general ham) and it should make things much easier. Thanks for any help you can provide. Scott.
I'm having difficulty and can't seem to dope it out. Running yaesu 857d, Log4om, fldigi, Windos7 Home Premium, and using a RT systems USB 62 cable to the radio. I can't seem to get Log4om to read the log in fldigi and bring it over so that QSOs can be sent to qrz, eqsl and eventually LOTW. The path to fldigi should be correct, communicator should be configured, log4om should be running as an admin. The comm port should be correct (comm3). My guess is that the comm setting is that something in windows is off but I need a few ideas on what to double check and or look into.
Likewise, no cat control. Cluster does work fine, communicator is started and everything, omni rig seems to be running, omni should match fldigi and log4om. 857d is set for cat under menu 20.
I would appreciate any advice. This will be great once it is up and running - I've never used logging software before (new general ham) and it should make things much easier. Thanks for any help you can provide. Scott.