Log4OM

I would just like to start with a BIG Thanks to all at Log40m for making this fantastic software. I am a big user of this and have been using it for 2 years.
The problem I have is with a FT-747GX and CAT control so that I can click on the spots and automatically change frequency. If I can get this working it would be fantastic!
I know the radio is old but the CAT does work with another free logging software. When I try and set it up with Omnirig I get absolutely nothing, I have tried running it with the Client.exe and all it reports is Rig not responding. The baud rate, bit rate port number etc etc is correct both on the software and Port on the PC control panel. I have upgraded the Silicon USB to Uart bridge driver that is supposed to be Windows 10 friendly and still nothing.
If I try with the Hamlib option I get some success, Hamlib goes green and CAT goes green and I can click on the spots to the left and it changes frequency on my rig all seems good for about 30 seconds then the CAT disconnects.
I wonder if it is a Windows 10 issue?

Any help would be most appreciated

I would try a factory reset of the 747 and then start again with the set up of baud rate etc

Older Yaesu radios do not work very well with the higher baud rates so try 4800 or 9600

I always found Hamlib to be fairly useless whereas Omnirig seems to work with virtually any radio

Thamks Terry,
I have just had a look at the log and this is what Hamlib is doing

conf=stop_bits=2,dtr_state=ON,rts_state=ON --ptt-file=COM3 --ptt-type=RIG -v
2016-10-21 06:18:23.2414 INFO: HamlibManagement: CAT HAMLIB POLLING START REQUEST (50 ms delay)
2016-10-21 06:18:23.2904 INFO: HamlibManagement: DAEMON STARTED
2016-10-21 06:18:25.2445 INFO: HamlibManagement: CAT HAMLIB POLLING STARTED localhost:8083
2016-10-21 06:19:00.6405 INFO: HamlibManagement: CAT HAMLIB received no answer from radio. Exiting...
2016-10-21 06:19:00.6465 INFO: HamlibManagement: CAT HAMLIB POLLING exited


I will try the reset of the rig.

m6wrh wrote:Thamks Terry,
I have just had a look at the log and this is what Hamlib is doing

conf=stop_bits=2,dtr_state=ON,rts_state=ON --ptt-file=COM3 --ptt-type=RIG -v
2016-10-21 06:18:23.2414 INFO: HamlibManagement: CAT HAMLIB POLLING START REQUEST (50 ms delay)
2016-10-21 06:18:23.2904 INFO: HamlibManagement: DAEMON STARTED
2016-10-21 06:18:25.2445 INFO: HamlibManagement: CAT HAMLIB POLLING STARTED localhost:8083
2016-10-21 06:19:00.6405 INFO: HamlibManagement: CAT HAMLIB received no answer from radio. Exiting...
2016-10-21 06:19:00.6465 INFO: HamlibManagement: CAT HAMLIB POLLING exited


I will try the reset of the rig.

This usually indicates an incorrect setting like baud rate, com port, stop bits or DTR/RTS settings

Thanks Terry,
I will try tweaking the settings. Funny thing is it dies work for around 30 seconds perfectly. I can see the CAT icon on the rig going on and off every few seconds as if it is polling. So I am guessing the cable and Rig are OK.

Thanks again for your help on this.
Wayne
2E0DYP