Serial communication via NIMAX okay but not through LabView

[CoreyNE]

I am trying to communicate with a device via the serial port.  In MAX, I configured the port (28800, 8, N, 2, RTS/CTS).  In the test panel I can send an identification query (ID? \r) and get a response.  If I try this through a LabView VI, where I open a VISA session, set the COM port parameters and then try the ID query, I don't get a response. 

I also noticed that if I try the ID query in MAX, but use a USB-serial adapter, I don't get any response. 

I'm sure I'm missing some simple nuace of serial communications.  Any thoughts?

Thanks.

[Dennis_Knutson · Accepted solution]

In LabVIEW, my guess is that you are not correctly sending the \r. In order to do this, you need to have the string control/constant set for '\' Codes Display. If you had posted your code, it would have helped to see if that or something else is wrong. Did you try one of the example programs before trying to write your own?

I've never had a problem using a USB-RS232 adapter. Is the new port actually listed in MAX and can you use Hyperterminal with it?

[Coq_Rouge]

if you want to send \r codes you have to set your control or constant to what modus. Else you will send \r as ascii. Se picture. Just right click on the control with your mouse

[CoreyNE]

Good points about configuring the control for the backslash code - I forgot about that.  The USB-serial port is listed in MAX, and I know I have used this type of port with Hyperterminal before.  I can't use Hyperterminal to communicate with this device because Hyperterminal doesn't support a baud rate of 28800.

[CoreyNE]

Good points about configuring the control for the backslash code - I forgot about that.  The USB-serial port is listed in MAX, and I know I have used this type of port with Hyperterminal before.  I can't use Hyperterminal to communicate with this device because Hyperterminal doesn't support a baud rate of 28800.

[CoreyNE]

Thanks again.  I changed the backslash code setting and it worked.  I like it when simple problems have a simple solution.  I will have to retry the USB-serial cable again to see if I was making a similar simple mistake there.