16392 & 16408 errors w/ serial com example receiving GPS data.

[subsea]

Get errors and "Serial PortBytes..." error message alternating with garbled data (no recognizable characters). Once in a great while I will see a few characters of good data when starting up from a closed LabView. Multiline standard GPS ASCII message w/ leading "$" cr lf. Works with Hyperterm. Have successfully received many other types of messages. Same symptom w/ Windows 98 & XP Pro. Tried latest serpdrv driver w/ same problem. I've read something about "breaks" causing these errors? Any ideas.

Thanks,
Larry

[TongY]

The error 16392 is a framing error, you need to check that all the port settings (baud rate, handshaking mode, parity, etc.) are the same for both ports involved in the data transfer. Make sure that both ports are configured the same way. Another possibility is that you have conflicting versions of the LabVIEW serpdrv file on your system. Make sure there is only one copy of the serpdrv file on the various drives in your system.

http://digital.ni.com/public.nsf/websearch/0D912F6326294125862561FD005C6871

Error 16408 occurs when there is break condition.The Windows serial driver asserts the CE_BREAK and CE_FRAME error:

CE_BREAK: Occurs when the line goes dead for a period longer than (start bits) + (data bits) + (parity bits) + (stop bits). This can occur if two devices are not talking at the same speed; for example, one is talking at 1192 baud and the other at 1210 baud, when they are supposed to be at 1200 baud.

CE_FRAME: (Framing Error) Occurs when it does not see the requested number of bytes (data packet) in the data stream; for example, if it misses a stop bit in the data stream. Perhaps the stop bits were corrupted in some manner. Alternatively, the receiver may be configured to expect two stop bits, but the transmitter is only sending one. If a framing error is suspected or reported then the first thing to check is the configuration between the transmitter and receiver.

Check your instrument's user manual for the settings you should use in your serial communications. Then check the current settings of your COM port and the Serial Port Init.vi, to make sure that they are set to the values required by your instrument. Slowing down the BAUD rate can sometimes help alleviate these errors.

http://digital.ni.com/public.nsf/websearch/CA231AD7FE5337A7862569190071940D?OpenDocument