Troubleshooting/diagnostics

General checks:

• Check the hardware and software requirements described in this documentation (TwinCAT version, CE image version, etc.);
• Check the installation instructions (e.g. installation of the CAB files on a CE system);
• If connection problems occur, the PING command can be used to determine whether the communication partner can be reached via the network connection. If this is not the case, check the network configuration and the firewall settings;
• Sniffer tools such as Wireshark® enable logging of the entire network communication. The log can then be analyzed by Beckhoff support staff;
• Check the configuration of the data points (type, address of the information object, etc.);
• Check whether the other communication partner outputs an error code;
• Activate the debug output when establishing and terminating the connection and/or the ASDU data. Open the TwinCAT System Manager and activate the LogView window. Check the debug output.
• Check the use of the FB_SocketCloseAll function block and the LISTEN_MODE_CLOSEALL parameter if you communicate via several TCP/IP connections (server/clients) in a runtime system.
  If you have several connections, only activate one instance of the FB_SocketCloseAll function block once in the initialization step at program start.
  The LISTEN_MODE_CLOSEALL parameter may no longer be used in this case;

High-level interface:

• Especially at the central station:
• Check whether the FB_IEC870_5_104Master function block outputs an error code/error source;
• Compare/check the compatibility list of the central station with the compatibility list of the substation;
• Check whether the network address and port number that you transfer to the FB_IEC870_5_104Master function block are correct;
• Check the protocol parameters set on the FB_IEC870_5_104Master function block (iK, iW, t0, t1, t2, t3, APDULength, etc.). Compare the protocol parameters with the parameters in the substation;
• Check the system parameters set on the FB_IEC870_5_104Master function block (ASDU address, length of the ASDU address, length of the information object address, length of the cause of transfer COT, etc.). Compare the system parameters with the parameters in the substation;
• Check the parameters set on the FB_IEC870_5_104Master function block for cyclic data acquisition (initialization sequence, cyclic general interrogation, cyclic counter interrogation, cyclic test commands, etc.);
• Especially at the substation:
• Check whether the FB_IEC870_5_104Slave function block outputs an error code/error source;
• Check the compatibility list of the substation with the compatibility list of the central station;
• Check whether the input parameters that you transfer to the F_CreateServerHnd function are correct (network address, port number, etc.);
• Check the protocol parameters set on the FB_IEC870_5_104Slave function block (iK, iW, t0, t1, t2, t3, APDULength, etc.). Compare the protocol parameters with the parameters in the control station;
• Check the system parameters set on the FB_IEC870_5_104Slave function block (ASDU address, length of the ASDU address, length of the information object address, length of the cause of transfer COT, etc.). Compare the system parameters with the parameters in the control station;

Low-level interface:

• Check whether the FB_IEC870_5_104TProtocol function block outputs an error code;
• Compare/check the compatibility list of the central station with the compatibility list of the substation;
• Check whether the network address and port number that you transfer to the F_CreateServerHnd function or to the FB_ClientServerConnection or FB_ServerClientConnection function block are correct;
• Check the protocol parameters set on the FB_IEC870_5_104TProtocol function block (iK, iW, t0, t1, t2, t3, APDULength, etc.). Compare the protocol parameters with the parameters of the communication partner;
• Check the address lengths configured on the TX/RX data buffer (instance of ST_IEC870_5_101TBuffer): length of the ASDU address, length of the information object address, length of the cause of transfer, max. ASDU length. Compare the address lengths with the configuration of the communication partner;