You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@plc4x.apache.org by cd...@apache.org on 2024/02/14 07:41:08 UTC
(plc4x) branch develop updated: fix: Fixed several issues with the new generated-documentation.
This is an automated email from the ASF dual-hosted git repository.
cdutz pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/plc4x.git
The following commit(s) were added to refs/heads/develop by this push:
new 2ab1795b35 fix: Fixed several issues with the new generated-documentation.
2ab1795b35 is described below
commit 2ab1795b35597c10b7713d67ec2bb1cbacc3e4e4
Author: Christofer Dutz <cd...@apache.org>
AuthorDate: Wed Feb 14 08:39:15 2024 +0100
fix: Fixed several issues with the new generated-documentation.
---
plc4j/drivers/all/src/site/generated/ads.adoc | 4 ++--
plc4j/drivers/all/src/site/generated/logix.adoc | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/plc4j/drivers/all/src/site/generated/ads.adoc b/plc4j/drivers/all/src/site/generated/ads.adoc
index ade9f4e502..ea9d3780d9 100644
--- a/plc4j/drivers/all/src/site/generated/ads.adoc
+++ b/plc4j/drivers/all/src/site/generated/ads.adoc
@@ -35,9 +35,9 @@
|Supported Transports 4+|
- `tcp`
5+|Config options:
-|`target-ams-net-id` |STRING | |required |AMS-Net-Id of the target.
+|`target-ams-net-id` |STRING | |required |AMS-Net-Id of the target. An AMS-Net-Id has the regular format of an IPv4 IP-Address, however with 6 segments instead of 4.
|`target-ams-port` |INT | |required |AMS port of the target.
-|`source-ams-net-id` |STRING | |required |AMS-Net-Id of the source.
+|`source-ams-net-id` |STRING | |required |AMS-Net-Id of the source. An AMS-Net-Id has the regular format of an IPv4 IP-Address, however with 6 segments instead of 4.
|`source-ams-port` |INT | |required |AMS port of the source.
|`timeout-request` |INT |4000| |Default timeout for all types of requests.
|`load-symbol-and-data-type-tables` |BOOLEAN |true| |Configures, if when connecting the data-type- and symbol-table should be read. This is an optimization that can help in cases, where the PLC program is pretty large and downloading the full tables is causing problems. When disabled, symbolic addresses will manually be resolved as soon as an address is used.
diff --git a/plc4j/drivers/all/src/site/generated/logix.adoc b/plc4j/drivers/all/src/site/generated/logix.adoc
index 7ae3002a5f..1570070b57 100644
--- a/plc4j/drivers/all/src/site/generated/logix.adoc
+++ b/plc4j/drivers/all/src/site/generated/logix.adoc
@@ -35,7 +35,7 @@
|Supported Transports 4+|
- `tcp`
5+|Config options:
-|`communication-path` |STRING | | |The communication path allows for connection routing across multiple backplanes. It uses a common format found in logix controllers.
+|`communication-path` |STRING | | |The communication path allows for connection routing across multiple backplanes. It uses a common format found in Logix controllers.
It consists of pairs of values, each pair begins with either 1 (Backplane) or 2 (Ethernet), followed by a slot in the case of a backplane address,
or if using Ethernet an ip address. e.g. [1,4,2,192.168.0.1,1,1] - Routes to the 4th slot in the first rack, which is a ethernet module, it then connects to the address 192.168.0.1, then finds the module in slot 1.
|`backplane` |INT | | |Without using routing information the backplane defaults to 1. This is overridden if communicationPath is provided.