Instrument Control (GPIB, Serial, VISA, IVI)

Which PXI controller are u using? Does it specify the baudrates to be used for its RS-232?

The controller is a NI PXI-8106 Core 2 Duo 2.16 GHz Controller with Real-Time Embedded Software. The serial port is described as 16550 RS-232. This post says that the system should be able to handle 115.2 kbps: http://digital.ni.com/public.nsf/allkb/01E1586616FD650886257440006E44EB

The system works at 9600, 14,400, 19,200, and 38,400 bps, but I am unable to communicate at baud rates of 57,600 and 115,200 bps. This is strange, because in the previous (USB) configuration (using the same code), I was able to communicate at 115.2 kbps

Kate,

I would suspect the serial cable- length or shielding.  I'm not a big fan of the FTDI driver but it, ostensibly, provided a "repeater" in the RS-232 data.   If this system is using an RS-232 to TTL converter consider placing the converter on the far end.

Do you get any errors reported from the instrument driver? I would suspect that you are probably encountering overrun errors on that built-in port. The built-in port on all of our PXI controllers is a standard 16550 UART, which only has a 16-byte FIFO. This means that if you have a lot of high priority work happening on your RT system, you may be starving the thread which services the serial port.

The first step will be to look for errors from the instrument driver. Hopefully it will propagate any VISA errors back out to you.

-Jason S.

I don't think that it's a cable length problem. The cable is designed for RS-232/422 use, and it's actually transmitting data in the RS-422 format. The cable is 30' long, well under the recommended maximum length for RS-422.

I have a powered 232/422 converter at the RS-232 end to adapt the instrument's 422 signal to the 232 format accepted by the PXI. The adaptor has a maximum baud rate of 115.4 kps.

Hi Kate,

How much data are you reading back at the VISA read? Have you tried increasing the default Timeout value?

Here's a KnowledgeBase article that discusses this error more in-depth.

If increasing the timeout doesn't solve the problem, could you post your code so we can take a look? As you said, the hardware shouldn't be limiting the baud rate.

Take care!