Typical errors
(Original Document)
About us
Case 1
ERR flashing
Results
After loading the project, the TSX PBY 100 module’s ERR LED flashes
Causes
Actions
The TSX PBY 100 module is not recognized by the processor and has no configuration data.
  • Test whether the Control Expert configuration corresponds to the actual configuration,
  • Test whether the processor, Control Expert and TSX PBY 100 software versions are compatible.
Case 2
ERR lit
Results
After loading the project, the TSX PBY 100 module’s ERR LED remains permanently on.
Causes
Actions
Profibus DP cabling problem
  • Disconnect the TSX PBY 100 module from the connection terminal and reinitialize the processor,
  • If the module starts correctly following this action, there is a short circuit or a wire inversion in the cabling.
Physical problem resulting from the connection terminal or PCMCIA card
  • If the module does not start correctly, cut the power supply to the connection terminal and change the connection terminal and if necessary the PCMCIA card (the TAP and the card must be changed when the module is switched off).
PCMCIA card software problem
  • Test the software version of the card, it must be V5.02I or above.
Problem with the loaded configuration
  • Test the master module error codes and the input/output error codes,
  • Test the error codes via the diagnostics function.
Case 3
Line fault
Results
After loading a project, some bus slaves start and become faulty.
Causes
Actions
A line termination is detected but it is not at the end of the bus.
  • Test all the Profibus DP connectors and place the bus termination at the end of the line.
Case 4
Faulty slave
Results
A bus slave is faulty but has not caused a bus error.
Causes
Actions
The slave has some input/output errors or configuration error or the watchdog is inactive
  • Test the slave diagnostics data via the debugging screen.
Case 5
Delay in starting up the slave
Results
Bus slaves do not react immediately to start-up without causing a bus error. After a while, the slave starts.
Causes
Actions
Some slaves require a control command before being activated. These slaves have been too slow to react to the first command sent
  • Modify the bus parameters to delay the sending of the first command.
  • Add 5 time units to the Timeout.
Case 6
Slaves faulty intermittently
Results
Some slaves are intermittently faulty.
Causes
Actions
Slaves are subject to cabling or electromagnetic compatibility faults, but the TSX PBY 100 module tries to reactivate them
  • Reset all the diagnostics counters using the SEND_REQ function,
  • Test if the TSX PBY 100 module has received the new diagnostics.
Case 7
Bus hardware fault
Results
The %IWr.m.0.243.7 bit is activated, indicating one or more bus hardware faults and all the devices transmit their diagnostics data.
Causes
Actions
The bus is subject to cabling faults, connection faults, line termination faults or connection terminal faults. Because of this the slaves transmit their diagnostics and fill the receive zone with diagnostics.
  • Check the cabling and line terminations, in particular the connectors whose terminations are activated but not located at the end of the bus,
  • Reinitialize BUS_FLT (%IWr.m.0.243.7) by:
    • switching off and then switching on the PLC,
    • reinitializing the PLC,
    • disconnecting and reconnecting the TSX PBY 10 module while switched on,
    • downloading a new project,
    • resetting all the diagnostics counters using the SEND_REQ function.