Skip to content

Modbus Address Range Explanation #472

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
egekorkan wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Modbus Address Range Explanation #472

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
9ca9647
explain modbus address ranges
egekorkan Aug 19, 2026
a6b90a8
add range to modv:address
egekorkan Aug 19, 2026
9196ec1
correct ranges of terms
egekorkan Aug 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 17 additions & 8 deletions bindings/protocols/modbus/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -186,7 +186,7 @@ <h3>URL terms</h3>

<tr>
<td><code>modv:address</code></td>
<td>Specifies the starting address of the Modbus operations</td>
<td>Specifies the starting address of the Modbus operations. Between 0 and 65535</td>
<td>required</td>
<td><a href="http://www.w3.org/2001/XMLSchema#integer">integer</a></td>
</tr>
Expand Down Expand Up @@ -431,7 +431,7 @@ <h3>Function</h3>
<td><code>readDiscreteInput</code></td>
<td>Read Discrete Inputs</td>
<td>2</td>
<td>Read Physical Discrete Inputs (bit access). Address range 10001-19999</td>
<td>Read Physical Discrete Inputs (bit access). Usually in the address range 10001-19999</td>
</tr>

<tr></tr>
Expand All @@ -449,7 +449,7 @@ <h3>Function</h3>
<td><code>readHoldingRegisters</code></td>
<td>Read Multiple Holding Registers</td>
<td>3</td>
<td>Read Multiple Holding Registers (16 bit access). Address range 40001-49999</td>
<td>Read Multiple Holding Registers (16 bit access). Usually in the address range 40001-49999</td>
</tr>

<tr></tr>
Expand All @@ -458,7 +458,7 @@ <h3>Function</h3>
<td><code>readInputRegisters</code></td>
<td>Read Multiple Input Registers</td>
<td>4</td>
<td>Read Multiple Physical Input Registers (16 bits). Address range 30001-39999</td>
<td>Read Multiple Physical Input Registers (16 bits). Usually in the address range 30001-39999</td>
</tr>

<tr></tr>
Expand All @@ -467,7 +467,7 @@ <h3>Function</h3>
<td><code>writeMultipleCoils</code></td>
<td>Write Multiple Coils</td>
<td>15</td>
<td>Write Multiple Physical Coils (internal bits). Address range 00001-09999</td>
<td>Write Multiple Physical Coils (internal bits). Usually in the address range 00001-09999</td>
</tr>

<tr></tr>
Expand All @@ -476,7 +476,9 @@ <h3>Function</h3>
<td><code>writeMultipleHoldingRegisters</code></td>
<td>Write Multiple Holding Registers</td>
<td>16</td>
<td>Write Multiple Holding Registers (output registers, 16 bit). Address range 40001-49999</td>
<td>
Write Multiple Holding Registers (output registers, 16 bit). Usually in the address range 40001-49999
</td>
</tr>

<tr></tr>
Expand All @@ -485,7 +487,7 @@ <h3>Function</h3>
<td><code>writeSingleCoil</code></td>
<td>Write Single Coil</td>
<td>5</td>
<td>Write Single Physical Coil (internal bit). Address range 00001-09999</td>
<td>Write Single Physical Coil (internal bit). Usually in the address range 00001-09999</td>
</tr>

<tr></tr>
Expand All @@ -494,12 +496,19 @@ <h3>Function</h3>
<td><code>writeSingleHoldingRegister</code></td>
<td>Write Single Holding Register</td>
<td>6</td>
<td>Write Single HoldingRegister (internal bits). Address range 40001-49999</td>
<td>Write Single HoldingRegister (internal bits). Usually in the address range 40001-49999</td>
</tr>

<tr></tr>
</tbody>
</table>
<p class="note">
The address ranges indicated are based on the observations of the Modbus community and are not part of the
official Modbus specification. While you can use any address within the 0-65535 range, it is recommended for
new devices to adhere to these ranges for better compatibility with existing Modbus devices and systems. A WoT
Consumer application should not assume that a specific address range is used for a particular type of register
or coil, and should always use the Thing Description as the source of truth.
</p>
</section>
<section id="payloaddatatype">
<h3>Payload DataType</h3>
Expand Down
7 changes: 7 additions & 0 deletions bindings/protocols/modbus/index.template.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -261,6 +261,13 @@ <h3>Function</h3>
%s
</tbody>
</table>
<p class="note">
The address ranges indicated are based on the observations of the Modbus community and are not part of the
official Modbus specification. While you can use any address within the 0-65535 range, it is recommended for
new devices to adhere to these ranges for better compatibility with existing Modbus devices and systems. A WoT
Consumer application should not assume that a specific address range is used for a particular type of register
or coil, and should always use the Thing Description as the source of truth.
</p>
</section>
<section id="payloaddatatype">
<h3>Payload DataType</h3>
Expand Down
18 changes: 10 additions & 8 deletions bindings/protocols/modbus/ontology.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -436,7 +436,7 @@ <h3>Datatype Properties</h3>
<section>
<h4>hasAddress</h4>
<p>IRI: <code>https://www.w3.org/2019/wot/modbus#hasAddress</code></p>
<span>Specifies the starting address of the Modbus operations</span>
<span>Specifies the starting address of the Modbus operations. Between 0 and 65535</span>
<table class="def">
<tbody>
<tr>
Expand Down Expand Up @@ -744,7 +744,7 @@ <h4>Read Device Identification</h4>
<section>
<h4>Read Discrete Inputs</h4>
<p>IRI: <code>https://www.w3.org/2019/wot/modbus#readDiscreteInput</code></p>
<span>Read Physical Discrete Inputs (bit access). Address range 10001-19999</span>
<span>Read Physical Discrete Inputs (bit access). Usually in the address range 10001-19999</span>
<table class="def">
<tbody>
<tr>
Expand Down Expand Up @@ -774,7 +774,7 @@ <h4>Read File Record</h4>
<section>
<h4>Read Multiple Holding Registers</h4>
<p>IRI: <code>https://www.w3.org/2019/wot/modbus#readHoldingRegisters</code></p>
<span>Read Multiple Holding Registers (16 bit access). Address range 40001-49999</span>
<span>Read Multiple Holding Registers (16 bit access). Usually in the address range 40001-49999</span>
<table class="def">
<tbody>
<tr>
Expand All @@ -789,7 +789,7 @@ <h4>Read Multiple Holding Registers</h4>
<section>
<h4>Read Multiple Input Registers</h4>
<p>IRI: <code>https://www.w3.org/2019/wot/modbus#readInputRegisters</code></p>
<span>Read Multiple Physical Input Registers (16 bits). Address range 30001-39999</span>
<span>Read Multiple Physical Input Registers (16 bits). Usually in the address range 30001-39999</span>
<table class="def">
<tbody>
<tr>
Expand All @@ -804,7 +804,7 @@ <h4>Read Multiple Input Registers</h4>
<section>
<h4>Write Multiple Coils</h4>
<p>IRI: <code>https://www.w3.org/2019/wot/modbus#writeMultipleCoils</code></p>
<span>Write Multiple Physical Coils (internal bits). Address range 00001-09999</span>
<span>Write Multiple Physical Coils (internal bits). Usually in the address range 00001-09999</span>
<table class="def">
<tbody>
<tr>
Expand All @@ -819,7 +819,9 @@ <h4>Write Multiple Coils</h4>
<section>
<h4>Write Multiple Holding Registers</h4>
<p>IRI: <code>https://www.w3.org/2019/wot/modbus#writeMultipleHoldingRegisters</code></p>
<span>Write Multiple Holding Registers (output registers, 16 bit). Address range 40001-49999</span>
<span
>Write Multiple Holding Registers (output registers, 16 bit). Usually in the address range 40001-49999</span
>
<table class="def">
<tbody>
<tr>
Expand All @@ -834,7 +836,7 @@ <h4>Write Multiple Holding Registers</h4>
<section>
<h4>Write Single Coil</h4>
<p>IRI: <code>https://www.w3.org/2019/wot/modbus#writeSingleCoil</code></p>
<span>Write Single Physical Coil (internal bit). Address range 00001-09999</span>
<span>Write Single Physical Coil (internal bit). Usually in the address range 00001-09999</span>
<table class="def">
<tbody>
<tr>
Expand All @@ -849,7 +851,7 @@ <h4>Write Single Coil</h4>
<section>
<h4>Write Single Holding Register</h4>
<p>IRI: <code>https://www.w3.org/2019/wot/modbus#writeSingleHoldingRegister</code></p>
<span>Write Single HoldingRegister (internal bits). Address range 40001-49999</span>
<span>Write Single HoldingRegister (internal bits). Usually in the address range 40001-49999</span>
<table class="def">
<tbody>
<tr>
Expand Down
22 changes: 11 additions & 11 deletions bindings/protocols/modbus/ontology.ttl
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -144,7 +144,7 @@ binding:assignment rdf:type owl:AnnotationProperty .
:hasAddress rdf:type owl:DatatypeProperty ;
rdfs:domain :Request ;
rdfs:range xsd:integer ;
rdfs:comment "Specifies the starting address of the Modbus operations"@en ;
rdfs:comment "Specifies the starting address of the Modbus operations. Between 0 and 65535"@en ;
Comment thread
danielpeintner marked this conversation as resolved.
Outdated
rdfs:label "hasAddress"@en ;
binding:assignment binding:required .

Expand Down Expand Up @@ -254,7 +254,7 @@ binding:assignment rdf:type owl:AnnotationProperty .
rdfs:comment "Function code identifies the operation requested by client, indicates to the server what kind of action to perform. For a normal response, the server simply echoes to the request the original function code."@en ;
rdfs:label "Function"@en .


### https://www.w3.org/2019/wot/modbus#PayloadDataType
:PayloadDataType rdf:type owl:Class ;
owl:equivalentClass [ rdf:type owl:Class ;
Expand Down Expand Up @@ -283,7 +283,7 @@ binding:assignment rdf:type owl:AnnotationProperty .
:FunctionField rdf:type owl:Class ;
rdfs:subClassOf :Payload ;
rdfs:comment """Function Field class represents the value of the function in a Modbus frame. Each operation identified with a human readable name have a corresponding code.
The response function code corresponds exactly to the request function code sent by the client when no error occurs.
The response function code corresponds exactly to the request function code sent by the client when no error occurs.
On the contrary, the response operation is identified with an error code or exception function code corresponding to the request function code + 0x80."""@en ;
rdfs:label "Function Field" .

Expand Down Expand Up @@ -334,7 +334,7 @@ On the contrary, the response operation is identified with an error code or exce
### https://www.w3.org/2019/wot/modbus#DataRequest
:DataRequest rdf:type owl:Class ;
rdfs:subClassOf :DataField ;
rdfs:comment """Data request contains additional information sent from a client to server that the server uses to take the action defined by the function code.
rdfs:comment """Data request contains additional information sent from a client to server that the server uses to take the action defined by the function code.
This can include items like register address, the quantity of items to be handled, and the count of actual data bytes in the field.

The data request field may be nonexistent (zero length) in certain kind of requests, in this case the server does not require any additional information. The function code alone specifies the action."""@en ;
Expand Down Expand Up @@ -495,7 +495,7 @@ The data request field may be nonexistent (zero length) in certain kind of reque
:Function ;
:readFrom :DiscreteInput ;
:hasCodeNumber 2 ;
rdfs:comment "Read Physical Discrete Inputs (bit access). Address range 10001-19999"@en ;
rdfs:comment "Read Physical Discrete Inputs (bit access). Usually in the address range 10001-19999"@en ;
rdfs:label "Read Discrete Inputs"@en .


Expand All @@ -504,7 +504,7 @@ The data request field may be nonexistent (zero length) in certain kind of reque
:Function ;
:readFrom :HoldingRegister ;
:hasCodeNumber 3 ;
rdfs:comment "Read Multiple Holding Registers (16 bit access). Address range 40001-49999"@en ;
rdfs:comment "Read Multiple Holding Registers (16 bit access). Usually in the address range 40001-49999"@en ;
rdfs:label "Read Multiple Holding Registers"@en .


Expand All @@ -513,7 +513,7 @@ The data request field may be nonexistent (zero length) in certain kind of reque
:Function ;
:readFrom :InputRegister ;
:hasCodeNumber 4 ;
rdfs:comment "Read Multiple Physical Input Registers (16 bits). Address range 30001-39999"@en ;
rdfs:comment "Read Multiple Physical Input Registers (16 bits). Usually in the address range 30001-39999"@en ;
rdfs:label "Read Multiple Input Registers"@en .


Expand All @@ -522,7 +522,7 @@ The data request field may be nonexistent (zero length) in certain kind of reque
:Function ;
:writesOn :Coil ;
:hasCodeNumber 15 ;
rdfs:comment "Write Multiple Physical Coils (internal bits). Address range 00001-09999"@en ;
rdfs:comment "Write Multiple Physical Coils (internal bits). Usually in the address range 00001-09999"@en ;
rdfs:label "Write Multiple Coils"@en .


Expand All @@ -531,7 +531,7 @@ The data request field may be nonexistent (zero length) in certain kind of reque
:Function ;
:writesOn :HoldingRegister ;
:hasCodeNumber 16 ;
rdfs:comment "Write Multiple Holding Registers (output registers, 16 bit). Address range 40001-49999"@en ;
rdfs:comment "Write Multiple Holding Registers (output registers, 16 bit). Usually in the address range 40001-49999"@en ;
rdfs:label "Write Multiple Holding Registers"@en .


Expand All @@ -540,7 +540,7 @@ The data request field may be nonexistent (zero length) in certain kind of reque
:Function ;
:writesOn :Coil ;
:hasCodeNumber 5 ;
rdfs:comment "Write Single Physical Coil (internal bit). Address range 00001-09999"@en ;
rdfs:comment "Write Single Physical Coil (internal bit). Usually in the address range 00001-09999"@en ;
rdfs:label "Write Single Coil"@en .


Expand All @@ -549,7 +549,7 @@ The data request field may be nonexistent (zero length) in certain kind of reque
:Function ;
:writesOn :HoldingRegister ;
:hasCodeNumber 6 ;
rdfs:comment "Write Single HoldingRegister (internal bits). Address range 40001-49999"@en ;
rdfs:comment "Write Single HoldingRegister (internal bits). Usually in the address range 40001-49999"@en ;
rdfs:label "Write Single Holding Register"@en .

### https://www.w3.org/2019/wot/modbus#readFileRecord
Expand Down
Loading