Log4OM

Try to add this to your FT-891.ini
Unfortunately I don't have an FT-891, otherwise I could test myself. This is try and error....


73
Roland

This is good reference to the Omni-Rig ini file structure http://www.dxatlas.com/omnirig/IniStru.txt

One question what is the output if you execute command 'ST; in DX Commander ?

I made the change suggested to the .ini file and selected that as my rig in OmniRig. No change. Still getting the Split indication with TX in A and RX on B.

Just to confirm, in the FT891 Ini in OmniRig I replaced

[STATUS5]
;not supported

with
[STATUS5]
Command=(ST;)
ReplyEnd=(;)
Validate=(ST.
Flag1=(......1.)|pmSplitOn
Flag2=(......0.)|pmSplitOff

No joy.

I am way beyond my area of expertise, so any help would be appreciated.

One question what is the output if you execute command 'ST; in DX Commander ?

??

Here is what I came up with, very similar to your solution:
[STATUS5]
Command=(ST;)
ReplyEnd=(;)
Validate=(ST.
Flag1=(..0)|pmSplitOff
Flag2=(..1)|pmSplitOn
Flag3=(..2)|pmSplitOn

This works well with the Omnirig client.exe test program.

I am wondering what LOG4OM does with these Omnirig codes? The more I am looking at the CAT structure for the FT891, I am thinking it is a bit limited versus other rigs, including Yaesu rigs. So what does LOG4OM do with the pmSplitOff, pmSplitOn codes? More specifically, how is the Split button on the LOG4OM UI activated? What information is being read from Omnirig to determine the rig's Split status?

SOLVED!!!

I corrected the Flag functions in the Status5 section to the following:


[STATUS5]
Command=(ST;)
ReplyEnd=(;)
Validate=(ST.
Flag1=(..0.)|pmSplitOff
Flag2=(..1.)|pmSplitOn
Flag3=(..2.)|pmSplitOn

Now the UI in LOG4OM is working perfectly.

Wow, what a colaboration.

Where can I post the revised .ini?

Send it to Alex by email

Who is Alex???

wo9b wrote: ↑05 Feb 2020, 16:52Who is Alex???

That guy that writes Omnirig and all of the other Afreet software