OpenCom asserts dtr?

[menchar]

Does OpenComConfig / OpenCom in the CVI rs-232 library always assert DTR?  Is this documented anywhere that I'm missing - I don't see it in the help for the rs-232 library.

Menchar

[menchar]

To answer my own question -

Yes, it's described in the help for the rs-232 library - use ComSetEscape

BUT - some, if not a lot, of the semantics of this function depend upon the serial driver being used.  So, for example, if I'm using a plain vanilla Windows 32 bit serial driver from, say Win2K or WinXP, how in the world do I figure out what the driver supports?  And if I'm using the NI serial driver, how do I figure out which escape codes it supports?

Thanks.

Menchar

[Mert_A.]

As the function help for ComSetEscape says,

Not all device drivers support all escape codes. ComSetEscape returns Unknown System Error (-1) when the device driver does not support a particular escape code.

Unfortunately, we can't make any further claims about which codes will or won't be supported by a particular driver.

Mert A.
National Instruments

[menchar]

Hi Mert -

Well, surely someone at NI could tell us what escape codes the NI Windows kernel mode serial driver supports ...

And to further answer my own question, the Windows SDK shows in the EscapeCommConfiguration call what the Win32 API supports.

Blanding out the help so as to never be wrong in re Windows Vs. Linux doesn't help a lot.  While I appreciate the desire to be platform neutral, I suspect most developers are firmly in one camp or the other.

Menchar