Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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
34 changes: 22 additions & 12 deletions bindings/protocols/modbus/index.html
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 All @@ -196,8 +196,9 @@ <h3>URL terms</h3>
<tr>
<td><code>modv:unitID</code></td>
<td>
The Unit ID is technically not needed for ModbusTCP, since the IP-address works as unique identifier,
but for compatibility reasons it MUST be included
Sometimes also called the Slave or Server ID, the Unit ID is technically not needed for ModbusTCP, since
the IP-address works as unique identifier, but for compatibility reasons it MUST be included. Mostly
between 1 and 247 but 255 is technically possible
</td>
<td>required</td>
<td><a href="http://www.w3.org/2001/XMLSchema#integer">integer</a></td>
Expand Down Expand Up @@ -246,8 +247,8 @@ <h3>Form terms</h3>
<tr>
<td><code>modv:timeout</code></td>
<td>
Modbus response maximum waiting time. Defines how much time the runtime should wait until it receives a
reply from the device.
Maximum waiting time for a response. Defines how much time the runtime should wait until it receives a
reply from the device. Defined as integer of milliseconds.
</td>
<td>optional</td>
<td><a href="http://www.w3.org/2001/XMLSchema#integer">integer</a></td>
Expand Down Expand Up @@ -431,7 +432,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 +450,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 +459,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 +468,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 +477,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 +488,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 +497,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
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
42 changes: 24 additions & 18 deletions bindings/protocols/modbus/ontology.html
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,10 @@
</head>
<body>
<section id="abstract">
<p>Vocabulary to represent Modbus messages in RDF.</p>
<p>
This document defines a vocabulary to represent Modbus messages in RDF. Even though it is provided by the Web of
Things, it can be used independently.
</p>
</section>
<section id="sotd">
<p>
Expand Down Expand Up @@ -436,7 +439,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 All @@ -448,7 +451,7 @@ <h4>hasAddress</h4>
<tr>
<td>Range</td>
<td>
<code><a href="http://www.w3.org/2001/XMLSchema#integer">integer</a></code>
<code><a href="http://www.w3.org/2001/XMLSchema#unsignedShort">unsignedShort</a></code>
</td>
</tr>
</tbody>
Expand Down Expand Up @@ -546,7 +549,7 @@ <h4>hasPollingTime</h4>
<tr>
<td>Range</td>
<td>
<code><a href="http://www.w3.org/2001/XMLSchema#integer">integer</a></code>
<code><a href="http://www.w3.org/2001/XMLSchema#unsignedInt">unsignedInt</a></code>
</td>
</tr>
</tbody>
Expand All @@ -567,7 +570,7 @@ <h4>hasQuantity</h4>
<tr>
<td>Range</td>
<td>
<code><a href="http://www.w3.org/2001/XMLSchema#integer">integer</a></code>
<code><a href="http://www.w3.org/2001/XMLSchema#unsignedShort">unsignedShort</a></code>
</td>
</tr>
</tbody>
Expand All @@ -577,8 +580,8 @@ <h4>hasQuantity</h4>
<h4>hasTimeout</h4>
<p>IRI: <code>https://www.w3.org/2019/wot/modbus#hasTimeout</code></p>
<span
>Modbus response maximum waiting time. Defines how much time the runtime should wait until it receives a
reply from the device.</span
>Maximum waiting time for a response. Defines how much time the runtime should wait until it receives a
reply from the device. Defined as integer of milliseconds.</span
>
<table class="def">
<tbody>
Expand All @@ -591,7 +594,7 @@ <h4>hasTimeout</h4>
<tr>
<td>Range</td>
<td>
<code><a href="http://www.w3.org/2001/XMLSchema#integer">integer</a></code>
<code><a href="http://www.w3.org/2001/XMLSchema#unsignedInt">unsignedInt</a></code>
</td>
</tr>
</tbody>
Expand All @@ -601,8 +604,9 @@ <h4>hasTimeout</h4>
<h4>hasUnitID</h4>
<p>IRI: <code>https://www.w3.org/2019/wot/modbus#hasUnitID</code></p>
<span
>The Unit ID is technically not needed for ModbusTCP, since the IP-address works as unique identifier, but
for compatibility reasons it MUST be included</span
>Sometimes also called the Slave or Server ID, the Unit ID is technically not needed for ModbusTCP, since
the IP-address works as unique identifier, but for compatibility reasons it MUST be included. Mostly between
1 and 247 but 255 is technically possible</span
>
<table class="def">
<tbody>
Expand All @@ -615,7 +619,7 @@ <h4>hasUnitID</h4>
<tr>
<td>Range</td>
<td>
<code><a href="http://www.w3.org/2001/XMLSchema#integer">integer</a></code>
<code><a href="http://www.w3.org/2001/XMLSchema#unsignedByte">unsignedByte</a></code>
</td>
</tr>
</tbody>
Expand Down Expand Up @@ -744,7 +748,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 +778,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 +793,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 +808,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 +823,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 +840,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 +855,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
Loading
Loading