To adequately perform serial port debugging it is advisable to have a great tool to assist you. RS232 Monitor is a software application that helps you identify and diagnose serial communication errors. With this RS232 debugging software you can easily track down the problem and get it fixed.
For serial communication to operate successfully, both ends of the conversation need to employ identical software settings. An example is where both the controlling and controlled device have the same parity setting or use the same BaudRate. Failure to set these correctly will disable the serial transmission.
You can find and set these parameters in the software’s status bar which provides information about the serial port and signal lines.
Serial port control information:
- nBaudRate: Defines the serial port baud rate. Possible values are: 110, 300, 600, 1200, 2400, 4800, 9600, 14400, 19200, 38400, 56000, 57600, 115200, 128000 and 256000. By default, 110 value is taken.
- nDataLength: Defines data lengths in a packet. Possible values are 5, 6, 7 and 8. The default value is 7 bits.
- cParity: Defines parity in one of the following values: (E)ven, (O)dd, (M)ark, (S)pace, or (N)one. By default (N)one is taken.
- nStopBits: Defines a number of stop bits. Possible values are: “1”, “1,5” and “2”. The default value is “1”.
- cHandflow: Defines flow control value. Possible values are Hardware (P), Xon/Xoff (X) and None. The default value is None.
Serial/modem control lines state:
- RTS: Request to Send line indicator
- CTS: Clear to Send line indicator
- DSR: Data Send Ready line indicator
- DCD: Data Carrier Detect line indicator
- DTR: Data Terminal Ready line indicator
- RI: Ring line indicator
The gray circle stands for the undetermined state. The red circle stands for a low line level, and the green circle stands for a high line level.
RS232 debug software: user manual
Once you have configured the settings in the software you can start using COM Port Debugger to collect data from your system’s COM ports. Follow these steps to start start monitoring serial data:
1. Launch Serial Data Debugger.
2. Choose “Session >>> New session” from the main menu, use the CTRL+N shortcut or click “New” on the main toolbar.
3. The “New monitoring session” window will be displayed:
Select how you want to view your data using the visualizers that will be employed during the session.
- Line view displays detailed information about the data transmitted through a specific serial line.
- Terminal view displays the data as ASCII characters in a text console.
- Table view displays recorded IRPs in a table format.
- Dump view displays all of the sent and received data passed through the serial line.
- Modbus view displays received and sent Modbus data (RTU and ASCII).
By using the “Start monitoring now” and “Start in new window” checkboxes you can control the characteristics of a new monitoring session.
Capture options allow you to determine which events you wish to monitor from these choices: Create/Close, Read/Write or Device Control.
4. Click “Start monitoring” to start the new monitoring session after selecting the settings.
A new monitoring window will be opened by the RS232 Debugger, displaying the data using the previously selected visualizers.
5. Save a session by choosing “Session >>> Save session/Save session As” from the main menu. You can also or click “Save” on the main toolbar, or press the CTRL+S keyboard shortcut.
Cables can pose a potential source of an RS232 error. Correctly cabling the device to the serial interface is essential to creating a viable connection.
A common problem when technicians attempt to debug RS232 issues is that the wiring between the control system and the device has not been done correctly.
Most control systems only require that two wires are connected to the controlled device. This connection is between the Transmit (XMT) and Ground (GND) pins on the control system which are connected to the controlled device’s Receive (RCV) and Ground (GND) pins.
A third wire is employed when the controlled device is expected to send a response to the controller. If you are using a computer’s serial port to control peripheral equipment, this is the standard wiring diagram.
The type of cable that you use can impact the ability to create a serial communication channel. You might need to use either a straight-through cable or a null-modem cable. Straight-through cables are equipped with a male connector at one end and a female connector on the other side. A female connector is on both ends of a null-modem cable. You need to use the correct cable for your application or you will not successfully set up connectivity.
Incorrect wiring can be the source of errors when connecting a device to its control system.
When terminal block type connectors are used, you can test the voltage with a voltmeter. This will help determine if the connection has been correctly implemented.
With the interconnecting cable in place and the voltmeter set to "DC", test the voltage between the RCV pin and the GND pin on the terminal block connector. You should look for a reading that falls between_12V and _6V. The XMT line should have the same reading.
If you have connected the lines between the control system and the controlled device and the voltmeter displays a steady reading of 0 volts, there is a high probability that you have the Receive and Transmit lines reversed (Fig. 4).
Serial Port Monitor is a professional-grade serial port debugging tool that will prove instrumental in troubleshooting and resolving problems with serial communication. This COM port debugging tool deserves to be part of your software arsenal if you work with serial interfaces and devices.