Download SM-Ethernet User Guide
Transcript
Data access using Modbus TCP/IP takes the form of a request for data by the master, followed by a response from the slave indicating either success (response), or failure (exception response) as shown in Figure 12-2. If no response is received this indicates that the message has not been received or the node is unable to reply. Figure 12-2 Modbus TCP/IP- request, response, exception Function Code Response Data PDU (Response) Function Code Function Data PDU (Request) Exception Data Getting started Function Code PDU (Exception Response) Table 12.1 MBAP Description Transaction identifier MSB. Transaction identifier LSB. Protocol identifier MSB. Protocol identifier LSB. Length MSB. Length LSB. Unit identifier. Security Table 12.2 PDU PDU Diagnostics Consists of Function code, 1 byte Request Function data, > 1 byte Function code, 1 byte Response Response data, > 1 byte Exception Error code, 1 byte Response Exception code, 1 byte Quick reference If accessing one of the SM-Applications parameters (menus 7x, 8x or 9x) on a drive with more than one SM-Applications module installed, the message will be routed to the SM-Applications module installed in the lowest slot number, if this is undesireable then the direct access parameters (menus 10x, 11x, 12x, etc) should be used. Advanced features NOTE Web page FTP/custom Applications basics pages The following tables document the structure of the MBAP and PDU, specifically the functions of each data byte within the overall message structure. Protocols MBAP and PDU message structure Byte 0 1 2 3 4 5 6 Safety Mechanical Electrical Introduction information installation installation 12.5.2 Data access Glossary of terms Index SM-Ethernet User Guide Issue: 6 www.controltechniques.com 109