Chapter 5
Troubleshooting
In the case that the diagnostic tools of the REX Control System (e.g. RexView) report unexpected or incorrect values of inputs or outputs, it is desirable to test the functionality outside the REX Control System (command line tools, Modbus simulators, etc.). Also double check the configuration – the most common problems include:
- Hardware problem – incorrect wiring (cross-cable vs. direct-cable, connector pinout), TTL vs. RS232 signal levels, signal polarity, etc.
- The configured serial channel is occupied by another program
- The device uses non-standard Modbus implementation (byte-order or word-order)
- The device is very slow and needs longer Sync. time
- Incorrect Slave address or register number.
- Mismatch in readable and writable flags.
- The signal is defined in inappropriate configuration file (when using multiple Modbus lines).
- Changing the parameters from algorithm. Check the values, especially during startup phase.
In the case that the given input or output works with other software tools and does not work in the REX Control System, report the problem to us, please. E-mail is preferred, reach us at support@rexcontrols.com. Please include the following information in your description to help us process your request as soon as possible:
- Identification of the REX Control System you are using. Simply export it to a file using the RexView program (Target Licence Export).
- Short and accurate description of your problem.
- The configuration files of the REX Control System (.mdl and .rio files) reduced to the simplest case which still demonstrates the problematic behavior.
[Previous] [Back to top] [Up] [Next]