Schneider TSX17 serial communication upgrade and replacement

Receive data: Call the TEXT block, specify the receive buffer address, and select "Receive with timeout" for the request code.

Suggest polling the status word in the loop to ensure communication is complete before proceeding to the next step. For multi frame long data, it is necessary to write a simple state machine to manage frame numbering and verification.

Common troubleshooting and maintenance

Based on years of on-site experience, TSX 17 communication related faults are mainly concentrated in the following categories. The following provides a systematic troubleshooting approach.

6.1 PLC unable to communicate with module

Phenomenon: Status word display module does not exist or communication timeout.

Possible reasons:

Module not correctly inserted into I/O slot or power not supplied

PL7-2 language card does not support this communication function

The configuration table was not sent correctly (or sent at the wrong time)

Troubleshooting steps:

Check the indicator lights on the module (if any). In most cases, the LED lights up after the module is powered on.

Confirm that the PL7-2 language card model installed in the CPU slot is consistent with the document requirements.

Forcefully ensure that the configuration block is executed only once at the beginning of the program, and use a timer to delay sending for several scanning cycles.

6.2 RS232 communication data error or garbled code

Phenomenon: Received characters but data error, or no response at all.

Possible reasons:

The baud rate, data bits, parity check do not match the other device

Cable wiring errors (most common problem)

Poor grounding leads to common mode interference

Troubleshooting steps:

Use serial monitoring tools (such as PC+serial assistant) to monitor the TX/RX lines of TSX 17 and confirm the actual waveform and bitrate.

Verify cable connection: The RS232 port of TSX SCG 1131 uses a standard DB9 male connector, with pin definitions of 2-TX, 3-RX, 5-GND. Cross connection (2-3, 3-2, 5-5) is required for communication with PC.

Check if the shielding layer is single ended grounded to avoid ground circulation.

6.3 UNI-TELWAY bus communication failure

Phenomenon: The master station cannot access the slave station, or the server is unresponsive.

Possible reasons:

Bus terminal resistance not set correctly

Duplicate station address

Cable breakage or non-standard tap changer (such as not using TSX SCA 62)

Troubleshooting steps:

Check if terminal resistors (usually 120 Ω) are configured at both ends of the bus.

Verify the addresses of all sites (configured through PL7-2) to ensure uniqueness.

Dismantle the site in sections and use resistance measurement method to check the bus continuity and short circuit situation.

Confirm that all T-connections are through TSX SCA 62 sockets and cannot be directly connected with three-way terminals.

6.4 Modbus communication timeout or abnormal response

Phenomenon: After the master station sends a request, the slave station does not respond or responds incorrectly.

Possible reasons:

Wrong setting of slave station address

Function code or register address not supported

Response exceeds timeout (e.g. slave scan cycle too long)

Troubleshooting steps:

Use Modbus scanning tools (such as ModScan) to independently test the slave station and determine whether the problem is caused by the slave station itself or the bus.

In the text block call of TSX 17 program, appropriately increase the timeout setting value (such as 500 ms).

Confirm whether the slave device supports the current requested function code (such as 03 read hold register, 06 write single register, etc.).

6.5 Intermittent communication interruption or data loss

Phenomenon: Most of the time it is normal, but occasionally data is lost or errors are reported.

Possible reasons:

Electrical interference (during the operation of frequency converters and contactors)

Power supply fluctuation

RS232 cable too long (over 15 meters)

Troubleshooting steps:

Check if the communication cable is laid separately from the power cable (minimum distance of 30cm).

Add a magnetic ring (ferrite) to the RS232 cable.

If the distance is indeed long, consider replacing it with an RS485 converter or fiber optic modem.

Add retry mechanism in PLC program: automatically resend up to 3 times when timeout or verification error is detected.

Replacement and upgrade strategy for discontinued modules

Considering that TSX SCG 1131, SCG 1161, and TSX 17 ACC5 have all been discontinued, the following are three feasible response plans, ranked by recommendation level.

7.1 Purchase high-quality second-hand/refurbished modules

Purchase tested inventory modules from professional second-hand automation equipment suppliers such as Artisan Technology Group, Radwell, etc. These modules typically come with a short-term warranty (30-90 days), which can help the equipment run for several more years.

Notes:

Confirm that the supplier has a functional testing process (such as verifying each port and protocol).

Require clear product images and batch numbers to avoid counterfeit products.

Try to purchase spare modules in the same batch.

7.2 Using Protocol Conversion Gateway to Implement Communication Upgrade