Our team can receive serial position output data from the USB-to-PC method, but we require RS-232, so we bought the extension cable to use the ‘UART’ position output method. 2.14 Reachview version. We have connected the RX, TX, and ground pins in accordance with the datasheet. We have matched the baud rates, serial port number, stop bit, etc. We tried different output formats NMEA, LLH, etc. Windows 10. We are using a NETmate USB 2.0 - RS-232 converter. There are no nonsense string outputs being received - it appears there is no output whatsoever.
Can you suggest some debugging possibilities or steps we didn’t consider?
Thanks for your suggestion and assistance, Tatiana. We have supplied the putty output screenshot as requested, along with settings in case an error of some type can be found there. Despite being able to receive via the USB-to-PC mode, but not via UART setting, we’re having difficulty identifying the cause of this issue.
A loopback test was performed on the pins of the RS-232 to USB converter using putty, and it was successful. So it does appears that neither the serial port, nor the converter is the problem.
Shouldn’t we see voltage changes that change with the NMEA message / signal being sent for RS-232? Here is a picture of the signal on the oscilloscope measuring the TX and GND pins.
The problem has been identified. One Reach RS+ device we bought has a faulty RS-232 port. For the other units we have, the RS-232 port works just fine.