Please check the following items in order.
1. Physical connection (cables and wiring)
・Checking for disconnection and poor contact
Please check that there are no cable breaks or connector contact issues. Pay special attention when the cables are used in movable sections.
・Type of wiring
For connection between a PC and an instrument, please normally use a "cross-wired" cable. Cables manufactured by our company are cross-wired.
2. Communication setting (baud rate, terminator)
・Matching settings
Please check that the communication settings such as baud rate, data bits, and parity completely match on both devices. If they do not match, communication will not be established.
・Adjusting the baud rate
If the communication speed is too high, errors are more likely to occur. In case of trouble, try lowering the speed to 9600 bps or 4800 bps to see if it improves the situation.
・Terminator (Line feed code)
Configure this according to the device specifications (such as CR+LF or CR). If set incorrectly, it may cause no response or errors.
3. PC setting and driver
・COM port number
In Device Manager, check the assigned COM port number. If you are using a USB conversion cable, the number may change depending on the connection port or after a restart.
・USB converter driver
Please check that the driver for the converter is installed correctly and that it is the latest version compatible with your operating system (such as Windows 10/11).
4. Command transmission and timing
・Command syntax and sequence
Please check that there are no unnecessary characters (such as spaces or NULL) included in the command.
・Wait time (transmission interval)
When sending commands consecutively, please either check the response or set an appropriate wait time. If the interval is too short, the measuring instrument may not be able to process them.
・Restarting the device
If communication becomes unstable, turn the power of both devices off and on again, clear the buffer, and then retry.
Use general-purpose communication software to send a simple command and check the response. This allows you to determine whether the issue lies in the created program or in the device settings.
