{"id":1512,"date":"2026-03-10T18:21:18","date_gmt":"2026-03-10T17:21:18","guid":{"rendered":"https:\/\/eltra.bfenterprise.it\/encoder-pedia\/cose-il-protocollo-modbus\/"},"modified":"2026-04-02T11:18:45","modified_gmt":"2026-04-02T09:18:45","slug":"what-is-the-modbus-protocol","status":"publish","type":"page","link":"https:\/\/eltra.bfenterprise.it\/en\/encoder-pedia\/what-is-the-modbus-protocol\/","title":{"rendered":"What is the Modbus protocol?"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-medium wp-image-504\" src=\"https:\/\/eltra.bfenterprise.it\/wp-content\/uploads\/2026\/03\/modbus-300x96.png\" alt=\"modbus\" width=\"300\" height=\"96\" srcset=\"https:\/\/eltra.bfenterprise.it\/wp-content\/uploads\/2026\/03\/modbus-300x96.png 300w, https:\/\/eltra.bfenterprise.it\/wp-content\/uploads\/2026\/03\/modbus-768x245.png 768w, https:\/\/eltra.bfenterprise.it\/wp-content\/uploads\/2026\/03\/modbus-600x191.png 600w, https:\/\/eltra.bfenterprise.it\/wp-content\/uploads\/2026\/03\/modbus.png 800w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\" \/><\/p>\n<p><strong>MODBUS<\/strong>\u00a0is an application layer messaging protocol, positioned at layer 7 of the OSI model. Provides client\/server communication between connected\u00a0devices on different types of buses or networks.<\/p>\n<p>The de facto industry serial standard since 1979,\u00a0<strong>MODBUS<\/strong>\u00a0continues to enable millions of automation devices to communicate.<br \/>\n<strong>MODBUS<\/strong>\u00a0is a request\/response protocol and offers services specified by function codes.\u00a0<strong>MODBUS<\/strong>\u00a0function codes are elements of Request\/Response PDUs.<\/p>\n<p><strong>STRUCTURE OF MODBUS RTU TELEGRAMS<\/strong><\/p>\n<p>In order to make settings in the device, the respective Modbus registers must be addressed via a telegram.\u00a0The basic structure of a Modbus telegram is shown below:<\/p>\n<table>\n<tbody>\n<tr>\n<td>Start<\/td>\n<td>Indirizzo<\/td>\n<td>Funzione<\/td>\n<td>Data<\/td>\n<td>CRC<\/td>\n<td>Stop<\/td>\n<\/tr>\n<tr>\n<td>3,5 byte<\/td>\n<td>1 byte<\/td>\n<td>1 byte<\/td>\n<td>N x 8 bits<\/td>\n<td>2 bytes<\/td>\n<td>3,5 bytes<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>The data area has a different structure depending on whether the telegram is a request or a reply and on the function code used.<\/p>\n<p>In RTU mode, messages begin with a silent interval of at least 3.5 characters. Depending on the transmission speed set in the network, this interval is\u00a0most easily implemented as a multiple of the duration of one character.<br \/>\nThe first field subsequently transmitted is the device address in the range 01&#8230;F7h (247d), (248-255 are reserved for Modbus).\u00a0Allowed characters for all fields: hexadecimal 0-9, A-F.\u00a0Networked devices constantly monitor the network bus, even during \u2018silence\u2019 intervals.When the first field (address field) is received, the device decodes it to determine whether the message is directed to it.\u00a0After the last character transmitted, an identical interval of at least 3.5 characters indicates the end of the message, a new message can begin after this\u00a0interval.<\/p>\n<p>The complete telegram must be transmitted as a continuous data stream. In the case of a silent interval of more than 1.5 characters before the end of\u00a0the telegram, the receiving device deletes the message and assumes that the next byte is the address field of a new message.<\/p>\n<p>Similarly, if a new message begins before the end of the 3.5 character silence interval, the receiving device will consider this new message as a continuation\u00a0of the previous message. This will trigger an error, as the value in the final CRC field will not be valid for combined messages.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>MODBUS\u00a0is an application layer messaging protocol, positioned at layer 7 of the OSI model. Provides [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":721,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"footnotes":""},"class_list":["post-1512","page","type-page","status-publish","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/eltra.bfenterprise.it\/en\/wp-json\/wp\/v2\/pages\/1512","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/eltra.bfenterprise.it\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/eltra.bfenterprise.it\/en\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/eltra.bfenterprise.it\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/eltra.bfenterprise.it\/en\/wp-json\/wp\/v2\/comments?post=1512"}],"version-history":[{"count":3,"href":"https:\/\/eltra.bfenterprise.it\/en\/wp-json\/wp\/v2\/pages\/1512\/revisions"}],"predecessor-version":[{"id":1523,"href":"https:\/\/eltra.bfenterprise.it\/en\/wp-json\/wp\/v2\/pages\/1512\/revisions\/1523"}],"up":[{"embeddable":true,"href":"https:\/\/eltra.bfenterprise.it\/en\/wp-json\/wp\/v2\/pages\/721"}],"wp:attachment":[{"href":"https:\/\/eltra.bfenterprise.it\/en\/wp-json\/wp\/v2\/media?parent=1512"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}