Another way to view this issue is to look at the dance going on between A) Log4OM, B) OmniRig and C) the rig. Yes, OmniRig provides for a RTTY mode between OmniRig and the Rig - and it is implemented via the OmniRig - xxx.ini file. So if OmniRig is commanded by software (Log4OM or any other logger using OmniRig) to go "Digital", OmniRig reads the xxx.ini file and sees the rig's RTTY command, if set by the user.
BUT, between Log4OM and OmniRig - there is only a pmDIG_L and pmDIG_U command to choose from for digital modes. There are NO sub-commands available to the developer. No pmRTTY command which Lele could use to tell OmniRig go RTTY. So Lele and Log4OM are left to say go "Digital", or pmDig_L, then OmniRig reads the xxx.ini file, which has the appropriate entry for setting the rig to RTTY, if that is what the user has chosen for their default digital mode.
So, technically Alex has provided for RTTY, but only between OmniRig and the rig. He has not provided the software designer the ability to call specifically for RTTY, versus any other digital commands. The only modes which OmniRig allows the software to call are the ones shown in your xxx.ini file under the Set Mode section - specifically pmCW_U, pmCW_L, pmSSB_U, pmSSB_L, pmDIG_U, pmDIG_L, pmAM, pmFM.
Here is the link to the OmniRig file structure from Alex's website, which describes what modes are available to the developer.
http://www.dxatlas.com/OmniRig/IniStru.txt The modes are listed in Section 4.
Dave, If you can convince Alex to expand that list of commands (between the software and OmniRig), I will buy you a beer! And be forever grateful!
Doug - W7DRM