This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/plc4x-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 04a0a02 Site checkin for project PLC4X: Jenkins Tools
04a0a02 is described below
commit 04a0a0252143db6587f441e9cc828171ba5343e0
Author: jenkins <[email protected]>
AuthorDate: Mon Feb 17 15:30:36 2020 +0000
Site checkin for project PLC4X: Jenkins Tools
---
images/tutorials/modbus/ModbusPal-1.png | Bin 0 -> 133977 bytes
images/tutorials/modbus/ModbusPal-2.png | Bin 0 -> 267000 bytes
images/tutorials/modbus/ModbusPal-3.png | Bin 0 -> 148179 bytes
images/tutorials/modbus/ModbusPal-4.png | Bin 0 -> 167981 bytes
images/tutorials/modbus/ModbusPal-5.png | Bin 0 -> 76694 bytes
images/tutorials/modbus/ModbusPal-6.png | Bin 0 -> 99660 bytes
images/tutorials/modbus/ModbusPal-7.png | Bin 0 -> 228335 bytes
images/tutorials/modbus/ModbusPal-8.png | Bin 0 -> 122029 bytes
images/tutorials/modbus/ModbusPal-9.png | Bin 0 -> 99947 bytes
plc4j/users/gettingstarted.html | 382 ---------------------
sitemap.html | 4 +-
users/download.html | 3 +
users/gettingstarted.html | 3 +
users/index.html | 3 +
users/industry40.html | 3 +
users/integrations/apache-calcite.html | 3 +
users/integrations/apache-camel.html | 3 +
users/integrations/apache-edgent.html | 3 +
users/integrations/apache-iotdb.html | 3 +
users/integrations/apache-kafka.html | 3 +
users/integrations/apache-nifi.html | 3 +
users/integrations/apache-streampipes.html | 3 +
users/integrations/eclipse-ditto.html | 3 +
users/integrations/elastic-logstash.html | 3 +
users/integrations/index.html | 3 +
users/opm.html | 3 +
users/plc4j/gettingstarted.html | 3 +
.../{gettingstarted.html => virtual-modbus.html} | 359 ++++++++++++++++++-
users/protocols/ab-eth.html | 3 +
users/protocols/ads.html | 3 +
users/protocols/bacnetip.html | 3 +
users/protocols/deltav.html | 3 +
users/protocols/df1.html | 3 +
users/protocols/ethernet-ip.html | 3 +
users/protocols/index.html | 3 +
users/protocols/knxnetip.html | 3 +
users/protocols/modbus.html | 3 +
users/protocols/opc-ua.html | 3 +
users/protocols/s7.html | 3 +
users/protocols/simulated.html | 3 +
users/security.html | 3 +
users/testing.html | 3 +
users/tools/connection-pool.html | 3 +
users/tools/index.html | 3 +
users/tools/opm.html | 3 +
users/tools/scraper.html | 3 +
users/tools/testing.html | 3 +
47 files changed, 454 insertions(+), 396 deletions(-)
diff --git a/images/tutorials/modbus/ModbusPal-1.png
b/images/tutorials/modbus/ModbusPal-1.png
new file mode 100644
index 0000000..064e116
Binary files /dev/null and b/images/tutorials/modbus/ModbusPal-1.png differ
diff --git a/images/tutorials/modbus/ModbusPal-2.png
b/images/tutorials/modbus/ModbusPal-2.png
new file mode 100644
index 0000000..755fb9a
Binary files /dev/null and b/images/tutorials/modbus/ModbusPal-2.png differ
diff --git a/images/tutorials/modbus/ModbusPal-3.png
b/images/tutorials/modbus/ModbusPal-3.png
new file mode 100644
index 0000000..9a9420e
Binary files /dev/null and b/images/tutorials/modbus/ModbusPal-3.png differ
diff --git a/images/tutorials/modbus/ModbusPal-4.png
b/images/tutorials/modbus/ModbusPal-4.png
new file mode 100644
index 0000000..85378e3
Binary files /dev/null and b/images/tutorials/modbus/ModbusPal-4.png differ
diff --git a/images/tutorials/modbus/ModbusPal-5.png
b/images/tutorials/modbus/ModbusPal-5.png
new file mode 100644
index 0000000..878b62e
Binary files /dev/null and b/images/tutorials/modbus/ModbusPal-5.png differ
diff --git a/images/tutorials/modbus/ModbusPal-6.png
b/images/tutorials/modbus/ModbusPal-6.png
new file mode 100644
index 0000000..413e1ef
Binary files /dev/null and b/images/tutorials/modbus/ModbusPal-6.png differ
diff --git a/images/tutorials/modbus/ModbusPal-7.png
b/images/tutorials/modbus/ModbusPal-7.png
new file mode 100644
index 0000000..6b580db
Binary files /dev/null and b/images/tutorials/modbus/ModbusPal-7.png differ
diff --git a/images/tutorials/modbus/ModbusPal-8.png
b/images/tutorials/modbus/ModbusPal-8.png
new file mode 100644
index 0000000..2daaf07
Binary files /dev/null and b/images/tutorials/modbus/ModbusPal-8.png differ
diff --git a/images/tutorials/modbus/ModbusPal-9.png
b/images/tutorials/modbus/ModbusPal-9.png
new file mode 100644
index 0000000..2e56f24
Binary files /dev/null and b/images/tutorials/modbus/ModbusPal-9.png differ
diff --git a/plc4j/users/gettingstarted.html b/plc4j/users/gettingstarted.html
deleted file mode 100644
index 0881933..0000000
--- a/plc4j/users/gettingstarted.html
+++ /dev/null
@@ -1,382 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
- <html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
-<head>
- <meta http-equiv="Content-Type"
content="text/html; charset=UTF-8"/>
- <title>PLC4X – </title>
- <script src="../../js/jquery.slim.min.js" type="javascript"></script>
- <!--script src="../../js/popper.min.js" type="javascript"></script-->
- <script src="../../js/bootstrap.bundle.min.js" type="javascript"></script>
- <!-- FontAwesome -->
- <link rel="stylesheet" href="../../css/all.min.css" type="text/css"/>
- <!-- Bootstrap -->
- <link rel="stylesheet" href="../../css/bootstrap.min.css" type="text/css"/>
- <!-- Some Maven Site defaults -->
- <link rel="stylesheet" href="../../css/maven-base.css" type="text/css"/>
- <link rel="stylesheet" href="../../css/maven-theme.css" type="text/css"/>
- <!-- The PLC4X version of a bootstrap theme -->
- <link rel="stylesheet" href="../../css/themes/plc4x.css" type="text/css"
id="pagestyle"/>
- <!-- A custom style for printing content -->
- <link rel="stylesheet" href="../../css/print.css" type="text/css"
media="print"/>
-
- <meta http-equiv="Content-Language" content="en"/>
-
-</head>
-<body class="composite">
-<nav class="navbar navbar-light navbar-expand-md bg-faded
justify-content-center border-bottom">
- <!--a href="/" class="navbar-brand d-flex w-50 mr-auto">Navbar 3</a-->
- <a href="https://plc4x.apache.org/"; id="bannerLeft"><img
src="../../images/apache_plc4x_logo_small.png" alt="Apache PLC4X"/></a>
- <button class="navbar-toggler" type="button" data-toggle="collapse"
data-target="#collapsingNavbar3">
- <span class="navbar-toggler-icon"></span>
- </button>
- <div class="navbar-collapse collapse w-100" id="collapsingNavbar3">
- <ul class="navbar-nav w-100 justify-content-center">
- <li class="nav-item">
- <a class="nav-link"
href="../../index.html">Home</a>
- </li>
-
<li class="nav-item">
- <a class="nav-link"
href="../../users/index.html">Users</a>
- </li>
- <li class="nav-item">
- <a class="nav-link"
href="../../developers/index.html">Developers</a>
- </li>
- <li class="nav-item">
- <a class="nav-link"
href="../../apache/index.html">Apache</a>
- </li>
- </ul>
- <ul class="nav navbar-nav ml-auto justify-content-end">
- <li class="nav-item row valign-middle">
- <a href="https://www.apache.org/events/current-event.html";
class="col"><img src="https://www.apache.org/events/current-event-234x60.png";
alt="Apache Events"/></a>
- <div class="col">
- <a href="https://www.apache.org/"; id="bannerRight"><img
src="../../images/apache_logo_small.png" alt="Apache Software Foundation"/></a>
- </div>
- </li>
- </ul>
- </div>
-</nav>
-<div class="container-fluid">
- <div class="row h-100">
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
<main role="main" class="ml-sm-auto px-4 w-100 h-100">
- <div class="sect1">
-<h2 id="getting_started">Getting Started</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="using_the_plc4x_api_directly">Using the PLC4X API directly</h3>
-<div class="paragraph">
-<p>In order to write a valid PLC4X Java application, all you need, is to add a
dependency to the <code>api module</code>.
-When using Maven, all you need to do is add this dependency:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre> <dependency>
- <groupId>org.apache.plc4x</groupId>
- <artifactId>plc4j-api</artifactId>
- <version>{project-version}</version>
- </dependency></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>This will allow you to write a valid application, that compiles fine.
-However in order to actually connect to a device using a given protocol, you
need to add this protocol implementation to the classpath.</p>
-</div>
-<div class="paragraph">
-<p>For example in order to communicate with an <code>S7 device</code> using
the <code>S7 Protocol</code>, you would need to add the following
dependency:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre> <dependency>
- <groupId>org.apache.plc4x</groupId>
- <artifactId>plc4j-driver-s7</artifactId>
- <version>{project-version}</version>
- <scope>runtime</scope>
- </dependency></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>So as soon as your project has the API and a driver implementation
available, you first need to get a <code>PlcConnection</code> instance.
-This is done via the <code>PlcDriverManager</code> by asking this to create an
instance for a given <code>PLC4X connection string</code>.</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre>String connectionString = "s7://10.10.64.20/1/1";
-
-try (PlcConnection plcConnection = new
PlcDriverManager().getConnection(connectionString)) {
-
- ... do something with the connection here ...
-
-}</pre>
-</div>
-</div>
-<div class="paragraph">
-<p>PLC4X generally supports a very limited set of functions, which is not due
to the fact, that we didn’t implement things, but that PLCs generally
support a very limited set of functions.</p>
-</div>
-<div class="paragraph">
-<p>The basic functions supported by PLCs and therefore supported by PLC4X
are:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>Read data</p>
-</li>
-<li>
-<p>Write data</p>
-</li>
-<li>
-<p>Subscribe for data</p>
-</li>
-<li>
-<p>Execute functions in the PLC</p>
-</li>
-<li>
-<p>List resources in the PLC</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>In general we will try to offer as many features as possible.
-So if a protocol doesn’t support subscription based communication it is
our goal to simulate this by polling in the background so it is transparent for
the users.</p>
-</div>
-<div class="paragraph">
-<p>But there are some cases in which we can’t simulate or features are
simply disabled intentionally:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>If a PLC and/or protocol don’t support executing of functions, we
simply can’t provide this functionality.</p>
-</li>
-<li>
-<p>We will be providing stripped down versions of drivers, that for example
intentionally don’t support any writing of data and executing of
functions.</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>Therefore we use metadata to check programmatically, if a given feature is
available:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre>// Check if this connection support reading of data.
-if (!plcConnection.getMetadata().canRead()) {
- logger.error("This connection doesn't support reading.");
- return;
-}</pre>
-</div>
-</div>
-<div class="paragraph">
-<p>As soon as you have ensured that a feature is available, you are ready to
build a first request.
-This is done by getting a <code>PlcRequestBuilder</code>:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre>// Create a new read request:
-// - Give the single item requested the alias name "value"
-PlcReadRequest.Builder builder = plcConnection.readRequestBuilder();
-builder.addItem("value-1", "%Q0.4:BOOL");
-builder.addItem("value-2", "%Q0:BYTE");
-builder.addItem("value-3", "%I0.2:BOOL");
-builder.addItem("value-4", "%DB.DB1.4:INT");
-PlcReadRequest readRequest = builder.build();</pre>
-</div>
-</div>
-<div class="paragraph">
-<p>So, as you can see, you prepare a request, by adding items to the request
and in the end by calling the <code>build</code> method.</p>
-</div>
-<div class="paragraph">
-<p>The request is sent to the PLC by issuing the <code>execute</code> method
on the request object:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre>CompletableFuture<? extends PlcReadResponse> asyncResponse =
readRequest.execute();
-asyncResponse.whenComplete((response, throwable) -> {
- ... process the response ...
-});</pre>
-</div>
-</div>
-<div class="paragraph">
-<p>In general all requests are executed asynchronously.
-So as soon as the request is fully processed, the callback gets called and
will contain a <code>readResponse</code>, if everything went right or a
<code>throwable</code> if there were problems.</p>
-</div>
-<div class="paragraph">
-<p>However if you want to write your code in a more synchronous fashion, the
following alternative will provide this:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre>PlcReadResponse response = readRequest.execute().get();</pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Processing of the responses is identical in both cases.
-The following example will demonstrate some of the options you have:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre>for (String fieldName : response.getFieldNames()) {
- if(response.getResponseCode(fieldName) == PlcResponseCode.OK) {
- int numValues = response.getNumberOfValues(fieldName);
- // If it's just one element, output just one single line.
- if(numValues == 1) {
- logger.info("Value[" + fieldName + "]: " +
response.getObject(fieldName));
- }
- // If it's more than one element, output each in a single row.
- else {
- logger.info("Value[" + fieldName + "]:");
- for(int i = 0; i < numValues; i++) {
- logger.info(" - " + response.getObject(fieldName, i));
- }
- }
- }
- // Something went wrong, to output an error message instead.
- else {
- logger.error("Error[" + fieldName + "]: " +
response.getResponseCode(fieldName).name());
- }
-}</pre>
-</div>
-</div>
-<div class="paragraph">
-<p>In the for loop, we are demonstrating how the user can iterate over the
address aliases in the response.
-In case of an ordinary read request, this will be predefined by the items in
the request, however in case of a subscription response, the response might
only contain some of the items that were subscribed.</p>
-</div>
-<div class="paragraph">
-<p>Before accessing the data, it is advisable to check if an item was
correctly returned.
-This is done by the <code>getResponseCode</code> method for a given alias.
-If this is <code>PlcResponseCode.OK</code>, everything is ok, however it could
be one of the following:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>NOT_FOUND</p>
-</li>
-<li>
-<p>ACCESS_DENIED</p>
-</li>
-<li>
-<p>INVALID_ADDRESS</p>
-</li>
-<li>
-<p>INVALID_DATATYPE</p>
-</li>
-<li>
-<p>INTERNAL_ERROR</p>
-</li>
-<li>
-<p>RESPONSE_PENDING</p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>Assuming the return code was <code>OK</code>, we can continue accessing the
data.</p>
-</div>
-<div class="paragraph">
-<p>As some addresses support reading arrays, with the method
<code>getNumberOfValues</code> the user can check how many items of a given
type are returned.
-For convenience the response object has single-argument methods for accessing
the data, which default to returning the first element.</p>
-</div>
-<div class="literalblock">
-<div class="content">
-<pre>response.getObject(fieldName)</pre>
-</div>
-</div>
-<div class="paragraph">
-<p>If you want to access a given element number, please use the two-argument
version instead:</p>
-</div>
-<div class="literalblock">
-<div class="content">
-<pre>response.getObject(fieldName, 42)</pre>
-</div>
-</div>
-<div class="paragraph">
-<p>PLC4X provides getters and setters for a wide variety of Java types and
automatically handles the type conversion.
-However when for example trying to get a long-value as a byte and the
long-value exceeds the range supported by the smaller type, a
<code>RuntimeException</code> of type
<code>PlcIncompatibleDatatypeException</code>.
-In order to avoid causing this exception to be thrown, however there are
<code>isValid{TypeName}</code> methods that you can use to check if the value
is compatible.</p>
-</div>
-</div>
-</div>
-</div>
- </main>
- <footer class="pt-4 my-md-5 pt-md-5 w-100 border-top">
- <div class="row justify-content-md-center" style="font-size: 13px">
- <div class="col col-6 text-center">
- Copyright © 2017–2020 <a
href="https://www.apache.org/";>The Apache Software Foundation</a>.
-All rights reserved.<br/>
- Apache PLC4X, PLC4X, Apache, the Apache feather logo, and
the Apache PLC4X project logo are either registered trademarks or trademarks of
The Apache Software Foundation in the United States and other countries. All
other marks mentioned may be trademarks or registered trademarks of their
respective owners.
- <br/><div
style="text-align:center;">Home screen image taken from <a
- href="https://flic.kr/p/chEftd";>Flickr</a>, "Tesla
Robot Dance" by Steve Jurvetson, licensed
- under <a
href="https://creativecommons.org/licenses/by/2.0/";>CC BY 2.0 Generic</a>,
image cropped
- and blur effect added.</div>
- </div>
- </div>
- </footer>
- </div>
-</div>
-
-<!-- Bootstrap core JavaScript
-================================================== -->
-<!-- Placed at the end of the document so the pages load faster -->
-<script src="../../js/jquery.slim.min.js"></script>
-<script src="../../js/popper.min.js"></script>
-<script src="../../js/bootstrap.min.js"></script>
-<script type="text/javascript">
- $('.carousel .carousel-item').each(function(){
- var next = $(this).next();
- if (!next.length) {
- next = $(this).siblings(':first');
- }
- next.children(':first-child').clone().appendTo($(this));
-
- for (let i = 0; i < 3; i++) {
- next=next.next();
- if (!next.length) {
- next = $(this).siblings(':first');
- }
- next.children(':first-child').clone().appendTo($(this));
- }
- });
-</script>
-</body>
-</html>
\ No newline at end of file
diff --git a/sitemap.html b/sitemap.html
index f9f68f2..23e7249 100644
--- a/sitemap.html
+++ b/sitemap.html
@@ -122,7 +122,9 @@
<ul>
-<li><a href="users/plc4j/gettingstarted.html">Java</a></li></ul></li>
+<li><a href="users/plc4j/gettingstarted.html">Java</a></li>
+
+<li><a href="users/plc4j/virtual-modbus.html">Virtual Modbus</a></li></ul></li>
<li><a href="users/protocols/index.html">Protocols</a>
diff --git a/users/download.html b/users/download.html
index ff05096..5cbb14b 100644
--- a/users/download.html
+++ b/users/download.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<a href="../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
</li>
+ <li class="nav-item">
+ <a href="../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
diff --git a/users/gettingstarted.html b/users/gettingstarted.html
index 1995ade..67686fb 100644
--- a/users/gettingstarted.html
+++ b/users/gettingstarted.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<a href="../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
</li>
+ <li class="nav-item">
+ <a href="../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
diff --git a/users/index.html b/users/index.html
index 7996f1a..e0a9d0a 100644
--- a/users/index.html
+++ b/users/index.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<a href="../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
</li>
+ <li class="nav-item">
+ <a href="../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
diff --git a/users/industry40.html b/users/industry40.html
index e26f834..429fc6d 100644
--- a/users/industry40.html
+++ b/users/industry40.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<a href="../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
</li>
+ <li class="nav-item">
+ <a href="../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
diff --git a/users/integrations/apache-calcite.html
b/users/integrations/apache-calcite.html
index 471c14b..3158c3b 100644
--- a/users/integrations/apache-calcite.html
+++ b/users/integrations/apache-calcite.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<a href="../../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
</li>
+ <li class="nav-item">
+ <a href="../../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
diff --git a/users/integrations/apache-camel.html
b/users/integrations/apache-camel.html
index 99e384a..8570b05 100644
--- a/users/integrations/apache-camel.html
+++ b/users/integrations/apache-camel.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<a href="../../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
</li>
+ <li class="nav-item">
+ <a href="../../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
diff --git a/users/integrations/apache-edgent.html
b/users/integrations/apache-edgent.html
index 0fb24eb..1675493 100644
--- a/users/integrations/apache-edgent.html
+++ b/users/integrations/apache-edgent.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<a href="../../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
</li>
+ <li class="nav-item">
+ <a href="../../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
diff --git a/users/integrations/apache-iotdb.html
b/users/integrations/apache-iotdb.html
index 6db6213..bd62e7d 100644
--- a/users/integrations/apache-iotdb.html
+++ b/users/integrations/apache-iotdb.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<a href="../../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
</li>
+ <li class="nav-item">
+ <a href="../../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
diff --git a/users/integrations/apache-kafka.html
b/users/integrations/apache-kafka.html
index a1fe48b..3f6a29e 100644
--- a/users/integrations/apache-kafka.html
+++ b/users/integrations/apache-kafka.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<a href="../../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
</li>
+ <li class="nav-item">
+ <a href="../../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
diff --git a/users/integrations/apache-nifi.html
b/users/integrations/apache-nifi.html
index d805e8b..1e7c1f2 100644
--- a/users/integrations/apache-nifi.html
+++ b/users/integrations/apache-nifi.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<a href="../../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
</li>
+ <li class="nav-item">
+ <a href="../../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
diff --git a/users/integrations/apache-streampipes.html
b/users/integrations/apache-streampipes.html
index 1bc5a6e..7a6929c 100644
--- a/users/integrations/apache-streampipes.html
+++ b/users/integrations/apache-streampipes.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<a href="../../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
</li>
+ <li class="nav-item">
+ <a href="../../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
diff --git a/users/integrations/eclipse-ditto.html
b/users/integrations/eclipse-ditto.html
index 8297048..ae11395 100644
--- a/users/integrations/eclipse-ditto.html
+++ b/users/integrations/eclipse-ditto.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<a href="../../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
</li>
+ <li class="nav-item">
+ <a href="../../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
diff --git a/users/integrations/elastic-logstash.html
b/users/integrations/elastic-logstash.html
index fce43d2..bd6959e 100644
--- a/users/integrations/elastic-logstash.html
+++ b/users/integrations/elastic-logstash.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<a href="../../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
</li>
+ <li class="nav-item">
+ <a href="../../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
diff --git a/users/integrations/index.html b/users/integrations/index.html
index 16a613a..46ce55a 100644
--- a/users/integrations/index.html
+++ b/users/integrations/index.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<a href="../../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
</li>
+ <li class="nav-item">
+ <a href="../../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
diff --git a/users/opm.html b/users/opm.html
index e3735fa..eacecbc 100644
--- a/users/opm.html
+++ b/users/opm.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<a href="../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
</li>
+ <li class="nav-item">
+ <a href="../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
diff --git a/users/plc4j/gettingstarted.html b/users/plc4j/gettingstarted.html
index a54cabc..e98c144 100644
--- a/users/plc4j/gettingstarted.html
+++ b/users/plc4j/gettingstarted.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<strong class="nav-link">Java</strong>
</li>
+ <li class="nav-item">
+ <a href="../../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
diff --git a/users/plc4j/gettingstarted.html b/users/plc4j/virtual-modbus.html
similarity index 62%
copy from users/plc4j/gettingstarted.html
copy to users/plc4j/virtual-modbus.html
index a54cabc..ce9a83e 100644
--- a/users/plc4j/gettingstarted.html
+++ b/users/plc4j/virtual-modbus.html
@@ -75,7 +75,10 @@
<a href="../../users/gettingstarted.html"
class="nav-link">Getting Started</a>
<ul class="flex-column pl-4 nav">
<li class="nav-item">
- <strong class="nav-link">Java</strong>
+ <a href="../../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
+ </li>
+ <li class="nav-item">
+ <strong class="nav-link">Virtual Modbus</strong>
</li>
</ul>
</li>
@@ -219,10 +222,268 @@
</nav>
<main role="main"
class="ml-sm-auto px-4 col-sm-pull col-md-9 col-lg-10 h-100">
<div class="sect1">
-<h2 id="getting_started">Getting Started</h2>
+<h2 id="playing_around_with_apache_plc4x_with_a_virtual_modbus_plc">Playing
around with Apache PLC4X with a virtual Modbus PLC</h2>
<div class="sectionbody">
+<div class="paragraph">
+<p>If you want to get started with Apache PLC4X, but don’t have any PLC
at hand, this tutorial will demonstrate how you can use a virtual <code>Modbus
Slave</code> software to simulate communication with <code>Modbus</code>
enabled PLCs.</p>
+</div>
+<div class="paragraph">
+<p>Such a fully open-source software is <code>ModbusPal</code> which is
available from <a href="http://modbuspal.sourceforge.net/";>here</a>.</p>
+</div>
+<div class="paragraph">
+<p>All you need, is to download the file called <code>ModbusPal.jar</code>.</p>
+</div>
<div class="sect2">
-<h3 id="using_the_plc4x_api_directly">Using the PLC4X API directly</h3>
+<h3 id="setting_up_the_virtual_modbus_slave">Setting up the virtual Modbus
Slave</h3>
+<div class="paragraph">
+<p>In order to run the software, you just need to execute the following
command in the same directory you downloaded the Jar to:</p>
+</div>
+<div class="literalblock">
+<div class="content">
+<pre>java -jar ModbusPal.jar</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>After this you will see the ModbusPal UI, which will look like this:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="../../images/tutorials/modbus/ModbusPal-1.png" alt="ModbusPal 1"
width="300"/>
+</div>
+<div class="title">Figure 1. ModbusPal Main UI</div>
+</div>
+<div class="paragraph">
+<p>Here be sure that the <code>TCP port</code> is set to <code>502</code>
(Which is the default Modbus port).</p>
+</div>
+<div class="paragraph">
+<p>Next click on <code>Add</code> to add a new Modbus slave:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="../../images/tutorials/modbus/ModbusPal-2.png" alt="ModbusPal 2"
width="300"/>
+</div>
+<div class="title">Figure 2. ModbusPal Add slave UI</div>
+</div>
+<div class="paragraph">
+<p>Select a <code>Slave ID</code> as well as a <code>name</code>.</p>
+</div>
+<div class="paragraph">
+<p>After clicking on <code>Add</code> your new Modbus slave is ready to
start.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="../../images/tutorials/modbus/ModbusPal-3.png" alt="ModbusPal 3"
width="300"/>
+</div>
+<div class="title">Figure 3. ModbusPal Main UI with one started slave</div>
+</div>
+<div class="paragraph">
+<p>By clicking on the <code>Run</code> button your slave is generally ready to
communicate.</p>
+</div>
+<div class="paragraph">
+<p>However up until now this new wouldn’t have anything to share as we
haven’t created any resources, so it would be an empty slave.</p>
+</div>
+<div class="paragraph">
+<p>So as last steps, we have to create some resources to access.</p>
+</div>
+<div class="paragraph">
+<p>In order do to this, click on the <code>eye</code> icon of your newly
created slave.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="../../images/tutorials/modbus/ModbusPal-4.png" alt="ModbusPal 4"
width="300"/>
+</div>
+<div class="title">Figure 4. ModbusPal Main UI with one slave</div>
+</div>
+<div class="paragraph">
+<p>This will bring up an editor in which we can add some so-called
<code>Holding registers</code> and some <code>Coils</code>.</p>
+</div>
+<div class="paragraph">
+<p>Let’s start with adding some Holding registers.</p>
+</div>
+<div class="paragraph">
+<p>So make sure <code>Holding registers</code> is selected and then click on
the <code>Add</code> button:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="../../images/tutorials/modbus/ModbusPal-6.png" alt="ModbusPal 6"
width="300"/>
+</div>
+<div class="title">Figure 5. Holding register view</div>
+</div>
+<div class="paragraph">
+<p>The tool will suggest creating <code>65536</code> new registers, I usually
create 10 or so.</p>
+</div>
+<div class="admonitionblock tip">
+<table>
+<tr>
+<td class="icon">
+<div class="title">Tip</div>
+</td>
+<td class="content">
+When I use ths tool some times I have to click the <code>Add</code> button
more than once as the editor doesn’t always open the first time.
+</td>
+</tr>
+</table>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="../../images/tutorials/modbus/ModbusPal-7.png" alt="ModbusPal 7"
width="300"/>
+</div>
+<div class="title">Figure 6. Add Holding register dialog</div>
+</div>
+<div class="paragraph">
+<p>After this the <code>Holding register</code> tab should look like this:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="../../images/tutorials/modbus/ModbusPal-9.png" alt="ModbusPal 9"
width="300"/>
+</div>
+<div class="title">Figure 7. Add Holding register dialog</div>
+</div>
+<div class="paragraph">
+<p>Now do the same on the <code>Coils</code> tab, which should look like this
after that:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="../../images/tutorials/modbus/ModbusPal-8.png" alt="ModbusPal 8"
width="300"/>
+</div>
+<div class="title">Figure 8. Add Holding register dialog</div>
+</div>
+<div class="paragraph">
+<p>As a last step, I would suggest to open the <code>Console</code>.</p>
+</div>
+<div class="paragraph">
+<p>You can do this by clicking on the <code>Console</code> button of the main
UI.</p>
+</div>
+<div class="paragraph">
+<p>This will open the following window:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="../../images/tutorials/modbus/ModbusPal-5.png" alt="ModbusPal 5"
width="300"/>
+</div>
+<div class="title">Figure 9. Console</div>
+</div>
+<div class="paragraph">
+<p>Here ModbusPal will log every important event …​ especially
when getting new connections from PLC4X.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="some_modbus_basics">Some Modbus basics</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>In general Modbus only knows two types of data: <code>Coils</code> and
<code>Registers</code>.</p>
+</div>
+<div class="paragraph">
+<p>Coils are always simple <code>bits</code> or <code>boolean</code> values
and Registers are always <code>16 bit short values</code>.</p>
+</div>
+<div class="paragraph">
+<p>However there are different types of these and they have different
names:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><code>Discrete Inputs</code> (Boolean values) (read-only)</p>
+</li>
+<li>
+<p><code>Coils</code> (Boolean values) (read-write)</p>
+</li>
+<li>
+<p><code>Input Registers</code> (16 bit short values) (read-only)</p>
+</li>
+<li>
+<p><code>Holding Registers</code> (16 bit short values) (read-write)</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>For Modbus there is no universally agreed upon notation for addresses,
however as the addresses are extremely simple, in PLC4X we address these as
follows:</p>
+</div>
+<table class="tableblock frame-all grid-all stretch">
+<caption class="title">Table 1. Table Title</caption>
+<colgroup>
+<col style="width: 50%;"/>
+<col style="width: 50%;"/>
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Modbus Type</th>
+<th class="tableblock halign-left valign-top">PLC4X Address Syntax</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Discrete
Inputs</p></td>
+<td class="tableblock halign-left valign-top"><p
class="tableblock"><code>discrete-input:{start-number}</code> or
<code>discrete-input:{start-number}[{number-of-elements}]</code></p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p
class="tableblock">Coils</p></td>
+<td class="tableblock halign-left valign-top"><p
class="tableblock"><code>coil:{start-number}</code> or
<code>coil:{start-number}[{number-of-elements}]</code></p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Input
Registers</p></td>
+<td class="tableblock halign-left valign-top"><p
class="tableblock"><code>input-register:{start-number}</code> or
<code>input-register:{start-number}[{number-of-elements}]</code></p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Holding
Registers</p></td>
+<td class="tableblock halign-left valign-top"><p
class="tableblock"><code>holding-register:{start-number}</code> or
<code>holding-register:{start-number}[{number-of-elements}]</code></p></td>
+</tr>
+</tbody>
+</table>
+<div class="paragraph">
+<p>All addresses support a notation with and without a size. If the size is
not specified, then PLC4X assumes a size of <code>1</code>.</p>
+</div>
+<div class="paragraph">
+<p>A PLC4X connection-string generally has the same structure for all
drivers:</p>
+</div>
+<div class="literalblock">
+<div class="content">
+<pre>{driver-name}:{transport-name}://{transport-config}?{parameters}</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>The fragments <code>transport-name</code> and <code>parameters</code> herby
are usually optional, as every driver can support a default-transport, which is
used if the transport is omitted.
+Also are most drivers implemented in a way that doesn’t require any
parameters.
+These are only required if the connection requires some non-default
settings.</p>
+</div>
+<div class="paragraph">
+<p>For Modbus the typical transports are:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>tcp (transport-config is the ip or host-name of the slave and can be
suffixed by a port separated from the ip/host with <code>:</code>)</p>
+</li>
+<li>
+<p>serial (transport-config is the device name of the serial interface)</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>If we have setup ModbusPal as described above and are running this on the
same computer, the connection string to connect to this should be:</p>
+</div>
+<div class="literalblock">
+<div class="content">
+<pre>modbus://localhost</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>If you stated ModbusPal on a port different from Modbus' default port
<code>502</code> you would have to also provide this port in the connection
string.</p>
+</div>
+<div class="paragraph">
+<p>So assuming you started it on port 1502, then the connection string would
look as follows:</p>
+</div>
+<div class="literalblock">
+<div class="content">
+<pre>modbus://localhost:1502</pre>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="writing_code">Writing code</h2>
+<div class="sectionbody">
<div class="paragraph">
<p>In order to write a valid PLC4X Java application, all you need, is to add a
dependency to the <code>api module</code>.
When using Maven, all you need to do is add this dependency:</p>
@@ -232,7 +493,7 @@ When using Maven, all you need to do is add this
dependency:</p>
<pre> <dependency>
<groupId>org.apache.plc4x</groupId>
<artifactId>plc4j-api</artifactId>
- <version>0.5.0</version>
+ <version>{project-version}</version>
</dependency></pre>
</div>
</div>
@@ -241,25 +502,27 @@ When using Maven, all you need to do is add this
dependency:</p>
However in order to actually connect to a device using a given protocol, you
need to add this protocol implementation to the classpath.</p>
</div>
<div class="paragraph">
-<p>For example in order to communicate with an <code>S7 device</code> using
the <code>S7 Protocol</code>, you would need to add the following
dependency:</p>
+<p>For example in order to communicate using the <code>Modbus</code> protocol,
you would need to add the following dependency:</p>
</div>
<div class="listingblock">
<div class="content">
<pre> <dependency>
<groupId>org.apache.plc4x</groupId>
- <artifactId>plc4j-driver-s7</artifactId>
- <version>0.5.0</version>
+ <artifactId>plc4j-driver-modbus</artifactId>
+ <version>{project-version}</version>
<scope>runtime</scope>
</dependency></pre>
</div>
</div>
+<div class="sect2">
+<h3 id="connecting">Connecting</h3>
<div class="paragraph">
<p>So as soon as your project has the API and a driver implementation
available, you first need to get a <code>PlcConnection</code> instance.
This is done via the <code>PlcDriverManager</code> by asking this to create an
instance for a given <code>PLC4X connection string</code>.</p>
</div>
<div class="listingblock">
<div class="content">
-<pre>String connectionString = "s7://10.10.64.20";
+<pre>String connectionString = "modbus://localhost";
try (PlcConnection plcConnection = new
PlcDriverManager().getConnection(connectionString)) {
@@ -313,6 +576,9 @@ So if a protocol doesn’t support subscription based
communication it is ou
<div class="paragraph">
<p>Therefore we use metadata to check programmatically, if a given feature is
available:</p>
</div>
+</div>
+<div class="sect2">
+<h3 id="reading_data">Reading Data</h3>
<div class="listingblock">
<div class="content">
<pre>// Check if this connection support reading of data.
@@ -331,15 +597,20 @@ This is done by getting a
<code>PlcRequestBuilder</code>:</p>
<pre>// Create a new read request:
// - Give the single item requested the alias name "value"
PlcReadRequest.Builder builder = plcConnection.readRequestBuilder();
-builder.addItem("value-1", "%Q0.4:BOOL");
-builder.addItem("value-2", "%Q0:BYTE");
-builder.addItem("value-3", "%I0.2:BOOL");
-builder.addItem("value-4", "%DB.DB1.4:INT");
+builder.addItem("value-1", "coil:1");
+builder.addItem("value-2", "coil:3[4]");
+builder.addItem("value-3", "holding-register:1");
+builder.addItem("value-4", "holding-register:3[4]");
PlcReadRequest readRequest = builder.build();</pre>
</div>
</div>
<div class="paragraph">
-<p>So, as you can see, you prepare a request, by adding items to the request
and in the end by calling the <code>build</code> method.</p>
+<p>So, as you can see, you prepare a request, by adding items to the request
and in the end by calling the <code>build</code> method.
+Hereby the first string value is simply an alias you can give the the address
as this is usually a more readable way.
+The second argument is then the address string itself.</p>
+</div>
+<div class="paragraph">
+<p>In above example we didn’t add <code>discrete-input</code> and
<code>input-registers</code> as ModbusPal doesn’t seem to support
these.</p>
</div>
<div class="paragraph">
<p>The request is sent to the PLC by issuing the <code>execute</code> method
on the request object:</p>
@@ -449,6 +720,68 @@ However when for example trying to get a long-value as a
byte and the long-value
In order to avoid causing this exception to be thrown, however there are
<code>isValid{TypeName}</code> methods that you can use to check if the value
is compatible.</p>
</div>
</div>
+<div class="sect2">
+<h3 id="writing_data">Writing Data</h3>
+<div class="paragraph">
+<p>The code for writing is very similar to the code for reading, however when
creating the write request, we have to pass in the data alongside the field
definitions.</p>
+</div>
+<div class="paragraph">
+<p>While all of the 4 field types support reading from, only the
<code>coil</code> and <code>holding-register</code> field types support writing
to.
+If you attempt to write to these, this will result in errors.</p>
+</div>
+<div class="paragraph">
+<p>So again, we first check if this driver supports writing (Some drivers such
as passive-mode drivers or read-only versions might generally not support
writing):</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>// Check if this connection support reading of data.
+if (!plcConnection.getMetadata().canWrite()) {
+ logger.error("This connection doesn't support writing.");
+ return;
+}</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>As soon as you have ensured that a feature is available, you are ready to
build a first request.
+This is done by getting a <code>PlcRequestBuilder</code>:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>// Create a new read request:
+// - Give the single item requested the alias name "value"
+PlcWriteRequest.Builder builder = plcConnection.writeRequestBuilder();
+builder.addItem("value-1", "coil:1", true);
+builder.addItem("value-2", "coil:3[4]", true, false, true, true);
+builder.addItem("value-3", "holding-register:1", 42);
+builder.addItem("value-4", "holding-register:3[4]", 1, 2, 3, 4);
+PlcWriteRequest writeRequest = builder.build();</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>You can see that for every element that should be written, the same number
of arguments have to be provided.</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>PlcWriteResponse response = writeRequest.execute().get();</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>Actually executing the write operation is almost identical to the reading,
with the only difference, that the result only provides status codes and no
values.</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>for (String fieldName : response.getFieldNames()) {
+ if(response.getResponseCode(fieldName) == PlcResponseCode.OK) {
+ logger.info("Value[" + fieldName + "]: successfully written to
device.");
+ }
+ // Something went wrong, to output an error message instead.
+ else {
+ logger.error("Error[" + fieldName + "]: " +
response.getResponseCode(fieldName).name());
+ }
+}</pre>
+</div>
+</div>
+</div>
</div>
</div>
</main>
diff --git a/users/protocols/ab-eth.html b/users/protocols/ab-eth.html
index 7816b87..73c2077 100644
--- a/users/protocols/ab-eth.html
+++ b/users/protocols/ab-eth.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<a href="../../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
</li>
+ <li class="nav-item">
+ <a href="../../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
diff --git a/users/protocols/ads.html b/users/protocols/ads.html
index bdca23d..73727ba 100644
--- a/users/protocols/ads.html
+++ b/users/protocols/ads.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<a href="../../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
</li>
+ <li class="nav-item">
+ <a href="../../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
diff --git a/users/protocols/bacnetip.html b/users/protocols/bacnetip.html
index c3b9c48..84b06df 100644
--- a/users/protocols/bacnetip.html
+++ b/users/protocols/bacnetip.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<a href="../../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
</li>
+ <li class="nav-item">
+ <a href="../../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
diff --git a/users/protocols/deltav.html b/users/protocols/deltav.html
index 6871fac..04c90a3 100644
--- a/users/protocols/deltav.html
+++ b/users/protocols/deltav.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<a href="../../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
</li>
+ <li class="nav-item">
+ <a href="../../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
diff --git a/users/protocols/df1.html b/users/protocols/df1.html
index 8564a60..83142a5 100644
--- a/users/protocols/df1.html
+++ b/users/protocols/df1.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<a href="../../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
</li>
+ <li class="nav-item">
+ <a href="../../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
diff --git a/users/protocols/ethernet-ip.html b/users/protocols/ethernet-ip.html
index 588d0c6..8bd0ed0 100644
--- a/users/protocols/ethernet-ip.html
+++ b/users/protocols/ethernet-ip.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<a href="../../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
</li>
+ <li class="nav-item">
+ <a href="../../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
diff --git a/users/protocols/index.html b/users/protocols/index.html
index 9d3af49..7db63a8 100644
--- a/users/protocols/index.html
+++ b/users/protocols/index.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<a href="../../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
</li>
+ <li class="nav-item">
+ <a href="../../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
diff --git a/users/protocols/knxnetip.html b/users/protocols/knxnetip.html
index 38c5b3e..3d85a3a 100644
--- a/users/protocols/knxnetip.html
+++ b/users/protocols/knxnetip.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<a href="../../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
</li>
+ <li class="nav-item">
+ <a href="../../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
diff --git a/users/protocols/modbus.html b/users/protocols/modbus.html
index b3d594e..7f0e79f 100644
--- a/users/protocols/modbus.html
+++ b/users/protocols/modbus.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<a href="../../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
</li>
+ <li class="nav-item">
+ <a href="../../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
diff --git a/users/protocols/opc-ua.html b/users/protocols/opc-ua.html
index 18945e6..33fcf5e 100644
--- a/users/protocols/opc-ua.html
+++ b/users/protocols/opc-ua.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<a href="../../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
</li>
+ <li class="nav-item">
+ <a href="../../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
diff --git a/users/protocols/s7.html b/users/protocols/s7.html
index dd85a63..3c99e5f 100644
--- a/users/protocols/s7.html
+++ b/users/protocols/s7.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<a href="../../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
</li>
+ <li class="nav-item">
+ <a href="../../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
diff --git a/users/protocols/simulated.html b/users/protocols/simulated.html
index cd8b679..1001746 100644
--- a/users/protocols/simulated.html
+++ b/users/protocols/simulated.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<a href="../../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
</li>
+ <li class="nav-item">
+ <a href="../../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
diff --git a/users/security.html b/users/security.html
index ce51297..ee845c4 100644
--- a/users/security.html
+++ b/users/security.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<a href="../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
</li>
+ <li class="nav-item">
+ <a href="../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
diff --git a/users/testing.html b/users/testing.html
index 5475790..f86c816 100644
--- a/users/testing.html
+++ b/users/testing.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<a href="../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
</li>
+ <li class="nav-item">
+ <a href="../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
diff --git a/users/tools/connection-pool.html b/users/tools/connection-pool.html
index fc12116..79c8e99 100644
--- a/users/tools/connection-pool.html
+++ b/users/tools/connection-pool.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<a href="../../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
</li>
+ <li class="nav-item">
+ <a href="../../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
diff --git a/users/tools/index.html b/users/tools/index.html
index 45b74b0..2b9bb7e 100644
--- a/users/tools/index.html
+++ b/users/tools/index.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<a href="../../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
</li>
+ <li class="nav-item">
+ <a href="../../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
diff --git a/users/tools/opm.html b/users/tools/opm.html
index cbc8c5d..e1f9547 100644
--- a/users/tools/opm.html
+++ b/users/tools/opm.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<a href="../../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
</li>
+ <li class="nav-item">
+ <a href="../../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
diff --git a/users/tools/scraper.html b/users/tools/scraper.html
index dc1f2c9..593563c 100644
--- a/users/tools/scraper.html
+++ b/users/tools/scraper.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<a href="../../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
</li>
+ <li class="nav-item">
+ <a href="../../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
diff --git a/users/tools/testing.html b/users/tools/testing.html
index d564a97..deb2454 100644
--- a/users/tools/testing.html
+++ b/users/tools/testing.html
@@ -77,6 +77,9 @@
<li class="nav-item">
<a href="../../users/plc4j/gettingstarted.html"
class="nav-link">Java</a>
</li>
+ <li class="nav-item">
+ <a href="../../users/plc4j/virtual-modbus.html"
class="nav-link">Virtual Modbus</a>
+ </li>
</ul>
</li>
![https://www.apache.org/events/current-event-234x60.png"](https://www.apache.org/events/current-event-234x60.png"){kind=link}