2.16 Details on ProtocolsExtended MEMOBUS Protocol2-3782.16 Details on ProtocolsThis section provides details on the Extended MEMOBUS protocol, MEMOBUS protocol, and no-proto-col communications.Extended MEMOBUS ProtocolMessage StructureThe following message structure is used in Ethernet communications. Use this as reference when develop-ing a PC-based application.When the Extended MEMOBUS protocol is used to send and receive data, each message consists of threefields: a header field, a 218 header field, and the application data field.The header is used for TCP/IP and UDP/IP. User programs do not need to be aware of this header becauseit is automatically appended and removed in the 218IFD.The 218 header is required when using the Extended MEMOBUS protocol for Ethernet communications.User programs also do not need to be aware of the 218 header because it is automatically appended andremoved in the 218IFD.The actual data for the Extended MEMOBUS protocol is stored in the application data field.When communicating between a 218IFD and a host computer, the application on the host computer mustappend and remove the 218 header.The application data field contains the following parameter structure based on the combination of commu-nications protocol and the code that is specified.Communications Protocol Code ReferenceMEMOBUS message communications BIN MEMOBUS Binary Mode (page 2-381)MEMOBUS message communications ASCII MEMOBUS ASCII Mode (page 2-400)General-purpose message communica-tions (no-protocol) BIN General-purpose Message Binary Mode (page 2-400)General-purpose message communica-tions (no-protocol) ASCII General-purpose Message ASCII Mode (page 2-401)HeaderMEMOBUS or General-purpose MessageApplication will use only thisfield.218 headerTCP/IP header218 header Application data