2.16 Details on ProtocolsNo-protocol Communications2-410No-protocol CommunicationsMessage StructureWhen no-protocol communications is set as the communications protocol, application data is handled as ageneral-purpose message. When sending and receiving data, each message consists of two fields: a headerand the application data field.The header is for TCP/IP and UDP/IP connections and is used only for Ethernet communications. Userprograms do not need to be aware of this header because it is automatically appended and removed in the218IFD.The application data field can be formatted as required by the application. The application data field hasthe following message structure.The difference compared to using the general-purpose messaging mode with the Extended MEMOBUSprotocol is that the 218 header is not appended before the application data. General-purpose Message CommandsGeneral-purpose message commands can be set as required by the application.General-purpose Binary ModeIn no-protocol communications, the values of the MW hold registers in the Machine Controller are sentand received in the application data field.Communications Protocol Code ReferenceNo-protocol BIN General-purpose Binary Mode (page 2-410)No-protocol ASCII General-purpose ASCII Mode (page 2-411)Ethernet communications will use either binary or ASCII data based on the code setting in the connec-tion parameters.Header Application dataGeneral-purpose MessageApplication will use only this field.TCP/IP header(only for Ethernetcommunications)Note7 • • • • • • • • • 0(L)(H)(L)(H)(L)(H)(L)(H)CommandContents ofMWContents ofMW + 1Contents ofMW + n - 1The contents of the MW toMW + n -1 hold registers in theMachine Controller are set in these fields.No response is returned when a message is sent.