Log4OM

Hi all

I've got a confusing issue with my FT450D.

I use Log40M for logging and Wsjtx for FT8. omnirig is the only easy rig control option.

If I use omnirig in rig split mode, the computer doesn't control VFOB so tx frequency is always wrong. If I change band, VFOB stays on the last band.

If I use fake it split mode, the rig goes up or diwn 500Hz each time i transmit but doesn't go back. So it wanders out of band and the rx frequency leaves the ft8 frequency.

I've tried Hamlib, but that keeps giving me an io error in wsjtx.

Flrig works in wsjtx but occasionally crashes and I can't make a serial spliter work for log40m.

Would be grateful for ideas!

It is essential that you install Log4OM, WSJT, Omnirig and JTAlert, if you use it, all to 'Run as an administrator' as detailed on page 1 of our quick start guide and page 9 of our user manual and in the Log4OM YouTube quick start tutorial?

Failure to run ALL of the above programs as detailed will result in issues!

Secondly have you tried both of the Omnirig FT450 ini files?

Please also state what operating system you are using and which version of Log4OM, we always require this information!

Thanks
I've tried both those - no luck.
Runnging WIndows 10 64 bit and the latest Log40M download

M0IUS wrote: 03 Feb 2019, 09:00 Thanks
I've tried both those - no luck.
Runnging WIndows 10 64 bit and the latest Log40M download

Again!

Did you install Log4OM, WSJT, Omnirig and JTAlert, if you use it, all to 'Run as an administrator' as detailed on page 1 of our quick start guide and page 9 of our user manual and in the Log4OM YouTube quick start tutorial?

Failure to run ALL of the above programs as detailed will result in issues!


When you say the latest what actual Log4OM release number please, have had people say the latest and it turned out they were running 4 year old releases!

Yes, I am running as administrator amd installed as administrator.
Running 1.36.0

Do you have TeamViewer or Skype on your WSJT computer, if you have I will try to assist you direct

Seem to have fixed it! I changed my USB serial cable to a proper serial interface card and cable.

Thanks for confirming that it was nothing wrong with Log4OM