{"id":1731,"date":"2017-03-08T20:20:21","date_gmt":"2017-03-08T20:20:21","guid":{"rendered":"https:\/\/novanta.com\/robotics-automation\/modbustcp-vs-mcodetcp-overview\/"},"modified":"2017-03-08T20:20:21","modified_gmt":"2017-03-08T20:20:21","slug":"modbustcp-vs-mcodetcp-overview","status":"publish","type":"page","link":"https:\/\/novanta.com\/robotics-automation\/modbustcp-vs-mcodetcp-overview\/","title":{"rendered":"Modbus\/TCP vs MCode\/TCP Overview"},"content":{"rendered":"\n\n\n
\n\t
  1. MODBUS\/TCP (Connect to port 502)<\/strong>\r\nMODBUS\/TCP is a standard protocol designed for multidrop networks based on a client-server architecture communicating over TCP\/IP.<\/li>
  2. MCode\/TCP (Connect to port 503)<\/strong>\r\nMCode\/TCP is a protocol based upon the MDrive programming language using 1 and two character mnemonics.<\/li><\/ol>\n\n\r\nDepending on the port selected (ip.address:502 or ip.address:503) the device operation will differ significantly. When connected to port 502 the device will respond to standard MODBUS\/TCP function code formats. Commands will map to register addresses and follow the MODBUS\/TCP message format. Most importantly, MODBUS\/TCP follows a client-server networking model. The device is able to receive commands in immediate mode only.\r\n\r\nWhen connected to port 503, the device will operate like the RS-422\/485 products with the exception that party mode commands and features are disabled, as multi-drop communications are addressed via IP.\r\n\n

    Comparison<\/h3>\n\n\r\n\n
    \r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n
    Function<\/th>\r\nMODBUS\/TCP<\/strong><\/td>\r\nMCode\/TCP<\/strong><\/td>\r\n<\/tr>\r\n
    Networking model<\/td>\r\nServer (Client-Server network)<\/td>\r\nProgrammable node<\/td>\r\n<\/tr>\r\n
    Port<\/td>\r\n502<\/td>\r\n503<\/td>\r\n<\/tr>\r\n
    Command format<\/td>\r\n6 standard function codes, 2 mfg specific function codes<\/td>\r\nStandard MCode mnemonics<\/td>\r\n<\/tr>\r\n
    Programmable<\/td>\r\nNo<\/td>\r\nYes – Standard MCode program format<\/td>\r\n<\/tr>\r\n
    Communication modes<\/td>\r\nImmediate mode functions only<\/td>\r\nImmediate and program mode<\/td>\r\n<\/tr>\r\n
    Complexity<\/td>\r\nComplex<\/td>\r\nSimple 1 and 2 character mnemonics<\/td>\r\n<\/tr>\r\n
    Compatibility with programs from RS-422\/485 MDrive products<\/td>\r\nNone<\/td>\r\nFully compatible with non-party mode programs.<\/td>\r\n<\/tr>\r\n
    Recommended use<\/td>\r\nUse in systems unified by the MODBUS protocol.<\/td>\r\nUse in systems where multiple device types communicating using the same protocol isn’t required.<\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table><\/figure>\n\n\r\n\n

    MCode\/TCP (Port 503)<\/h3>\n\n\r\nMCode is the programming and control language utilized by MDrive Motion Control products developed to communicate over RS-422\/485. MCode\/TCP is MCode communicating over TCP\/IP. The language consists of an extensive command set made up of 1 and 2 character mnemonics.\r\n\r\nWhen connected to ip.address:503 the MDrive will automatically be in MCode\/TCP mode. In this mode the device is fully programmable and will operate identical to the RS-422\/485 products with the exception that multidrop communication is accomplished using individual IP addresses instead of party-mode names. Global commands are sent using the UDP protocol to address 255.255.255.255.\r\n\r\nThe key advantages of MCode\/TCP:\r\n\n