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 2025/03/29 15:34:17 UTC

(plc4x-build-tools) branch develop updated: chore: Removed the site skin, as it's no longer needed chore: Updated the pom.xml to the latest apache parent chore: Updated the NOTICE and LICENSE files.

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-build-tools.git


The following commit(s) were added to refs/heads/develop by this push:
     new f368524  chore: Removed the site skin, as it's no longer needed chore: Updated the pom.xml to the latest apache parent chore: Updated the NOTICE and LICENSE files.
f368524 is described below

commit f368524950d93421c93a4f5dd8ee5286e16a58b9
Author: Christofer Dutz <ch...@c-ware.de>
AuthorDate: Sat Mar 29 16:33:38 2025 +0100

    chore: Removed the site skin, as it's no longer needed
    chore: Updated the pom.xml to the latest apache parent
    chore: Updated the NOTICE and LICENSE files.
---
 LICENSE                                            |   13 -
 code-generation/NOTICE                             |    2 +-
 code-generation/pom.xml                            |    2 +-
 code-generation/{ => types-base}/LICENSE           |    0
 jenkins.pom                                        |    2 +-
 plc4x-site-skin/.mvn/extensions.xml                |   28 -
 plc4x-site-skin/.mvn/jvm.config                    |    1 -
 .../.mvn/wrapper/maven-wrapper.properties          |   19 -
 plc4x-site-skin/LICENSE                            |  202 ---
 plc4x-site-skin/NOTICE                             |    5 -
 plc4x-site-skin/README                             |   41 -
 plc4x-site-skin/RELEASE_NOTES                      |   43 -
 plc4x-site-skin/mvnw                               |  259 ---
 plc4x-site-skin/mvnw.cmd                           |  149 --
 plc4x-site-skin/pom.xml                            |  450 ------
 plc4x-site-skin/src/it/plc4x-website/pom.xml       |  306 ----
 .../src/main/script/preSiteGeneration.groovy       |   98 --
 .../src/site/asciidoc/apache/index.adoc            |   20 -
 .../src/site/asciidoc/developers/architecture.adoc |  162 --
 .../src/site/asciidoc/developers/building.adoc     |  163 --
 .../site/asciidoc/developers/code-gen/index.adoc   |  443 ------
 .../developers/code-gen/language/freemarker.adoc   |  193 ---
 .../asciidoc/developers/code-gen/protocol/df1.adoc |   94 --
 .../developers/code-gen/protocol/mspec.adoc        |  485 ------
 .../src/site/asciidoc/developers/conferences.adoc  |   49 -
 .../src/site/asciidoc/developers/contributing.adoc |  208 ---
 .../src/site/asciidoc/developers/decisions.adoc    |   66 -
 .../src/site/asciidoc/developers/index.adoc        |   59 -
 .../asciidoc/developers/infrastructure/ci.adoc     |   40 -
 .../asciidoc/developers/infrastructure/index.adoc  |   22 -
 .../asciidoc/developers/infrastructure/issues.adoc |   24 -
 .../asciidoc/developers/infrastructure/sonar.adoc  |   24 -
 .../asciidoc/developers/infrastructure/vm.adoc     |  102 --
 .../developers/infrastructure/website.adoc         |  177 ---
 .../asciidoc/developers/infrastructure/wiki.adoc   |   24 -
 .../src/site/asciidoc/developers/jqassistant.adoc  |  126 --
 .../src/site/asciidoc/developers/maturity.adoc     |   76 -
 .../site/asciidoc/developers/preparing/index.adoc  |   75 -
 .../site/asciidoc/developers/preparing/linux.adoc  |  155 --
 .../site/asciidoc/developers/preparing/macos.adoc  |  123 --
 .../asciidoc/developers/preparing/windows.adoc     |  122 --
 .../developers/protocols/ads/protocol.adoc         |  198 ---
 .../developers/protocols/eip/protocol.adoc         |  132 --
 .../site/asciidoc/developers/protocols/index.adoc  |   23 -
 .../asciidoc/developers/release/build-tools.adoc   |  397 -----
 .../site/asciidoc/developers/release/index.adoc    |   20 -
 .../site/asciidoc/developers/release/release.adoc  |  626 --------
 .../asciidoc/developers/release/validation.adoc    |  130 --
 .../src/site/asciidoc/developers/team.adoc         |   90 --
 .../src/site/asciidoc/developers/tools.adoc        |   32 -
 .../site/asciidoc/developers/tutorials/index.adoc  |   20 -
 .../tutorials/testing-serializers-and-parsers.adoc |  146 --
 .../developers/tutorials/writing-driver.adoc       |   57 -
 .../it/plc4x-website/src/site/asciidoc/index.adoc  |  242 ---
 .../src/site/asciidoc/protocols/ab-eth/index.adoc  |   33 -
 .../src/site/asciidoc/protocols/ads/index.adoc     |   25 -
 .../src/site/asciidoc/protocols/canopen/index.adoc |   39 -
 .../src/site/asciidoc/protocols/delta-v/index.adoc |  197 ---
 .../site/asciidoc/protocols/delta-v/read-data.adoc | 1655 --------------------
 .../protocols/delta-v/reverse-engineering.adoc     |  252 ---
 .../site/asciidoc/protocols/ehtercat/index.adoc    |   28 -
 .../site/asciidoc/protocols/ethernet-ip/index.adoc |   30 -
 .../src/site/asciidoc/protocols/features.adoc      |   87 -
 .../src/site/asciidoc/protocols/index.adoc         |   51 -
 .../src/site/asciidoc/protocols/modbus/index.adoc  |   26 -
 .../src/site/asciidoc/protocols/opc-ua/index.adoc  |   28 -
 .../src/site/asciidoc/protocols/s7/index.adoc      |  289 ----
 .../site/asciidoc/protocols/s7/s7comm-plus.adoc    |   38 -
 .../src/site/asciidoc/protocols/s7/s7comm.adoc     |  144 --
 .../src/site/asciidoc/users/adopters.adoc          |   64 -
 .../asciidoc/users/blogs-videos-and-slides.adoc    |   49 -
 .../site/asciidoc/users/commercial-support.adoc    |   51 -
 .../src/site/asciidoc/users/download.adoc          |  399 -----
 .../users/getting-started/general-concepts.adoc    |  109 --
 .../site/asciidoc/users/getting-started/index.adoc |   28 -
 .../site/asciidoc/users/getting-started/plc4c.adoc |   18 -
 .../asciidoc/users/getting-started/plc4cs.adoc     |   18 -
 .../asciidoc/users/getting-started/plc4go.adoc     |  328 ----
 .../site/asciidoc/users/getting-started/plc4j.adoc |  302 ----
 .../asciidoc/users/getting-started/plc4py.adoc     |  215 ---
 .../users/getting-started/using-snapshots.adoc     |   59 -
 .../users/getting-started/virtual-modbus.adoc      |  364 -----
 .../src/site/asciidoc/users/index.adoc             |  441 ------
 .../src/site/asciidoc/users/industry40.adoc        |  124 --
 .../users/integrations/apache-calcite.adoc         |   24 -
 .../asciidoc/users/integrations/apache-camel.adoc  |   22 -
 .../asciidoc/users/integrations/apache-edgent.adoc |   20 -
 .../asciidoc/users/integrations/apache-iotdb.adoc  |   62 -
 .../asciidoc/users/integrations/apache-kafka.adoc  |  239 ---
 .../asciidoc/users/integrations/apache-nifi.adoc   |  155 --
 .../users/integrations/apache-streampipes.adoc     |   24 -
 .../asciidoc/users/integrations/eclipse-ditto.adoc |   25 -
 .../asciidoc/users/integrations/eclipse-milo.adoc  |  123 --
 .../site/asciidoc/users/integrations/index.adoc    |   20 -
 .../src/site/asciidoc/users/issues.adoc            |   24 -
 .../src/site/asciidoc/users/preparing-issues.adoc  |   19 -
 .../src/site/asciidoc/users/protocols/ab-eth.adoc  |   24 -
 .../src/site/asciidoc/users/protocols/ads.adoc     |   63 -
 .../src/site/asciidoc/users/protocols/bacnet.adoc  |   52 -
 .../src/site/asciidoc/users/protocols/c-bus.adoc   |   24 -
 .../src/site/asciidoc/users/protocols/can.adoc     |   71 -
 .../src/site/asciidoc/users/protocols/canopen.adoc |  182 ---
 .../src/site/asciidoc/users/protocols/ctrlx.adoc   |   24 -
 .../src/site/asciidoc/users/protocols/deltav.adoc  |   20 -
 .../src/site/asciidoc/users/protocols/df1.adoc     |   20 -
 .../src/site/asciidoc/users/protocols/eip.adoc     |   58 -
 .../src/site/asciidoc/users/protocols/firmata.adoc |   97 --
 .../site/asciidoc/users/protocols/genericcan.adoc  |  105 --
 .../site/asciidoc/users/protocols/iec-60870.adoc   |   24 -
 .../src/site/asciidoc/users/protocols/index.adoc   |  389 -----
 .../site/asciidoc/users/protocols/knxnetip.adoc    |   44 -
 .../src/site/asciidoc/users/protocols/logix.adoc   |   68 -
 .../src/site/asciidoc/users/protocols/modbus.adoc  |  209 ---
 .../src/site/asciidoc/users/protocols/opcua.adoc   |  175 ---
 .../asciidoc/users/protocols/open-protocol.adoc    |   24 -
 .../src/site/asciidoc/users/protocols/plc4x.adoc   |   61 -
 .../site/asciidoc/users/protocols/profinet.adoc    |  117 --
 .../src/site/asciidoc/users/protocols/s7.adoc      | 1152 --------------
 .../site/asciidoc/users/protocols/simulated.adoc   |  120 --
 .../src/site/asciidoc/users/security.adoc          |   26 -
 .../site/asciidoc/users/tools/capture-replay.adoc  |   62 -
 .../asciidoc/users/tools/connection-cache.adoc     |  130 --
 .../site/asciidoc/users/tools/connection-pool.adoc |   79 -
 .../src/site/asciidoc/users/tools/index.adoc       |   20 -
 .../src/site/asciidoc/users/tools/opm.adoc         |   73 -
 .../src/site/asciidoc/users/tools/scraper.adoc     |  235 ---
 .../src/site/asciidoc/users/tools/testing.adoc     |  163 --
 .../src/site/asciidoc/users/transports/can.adoc    |   77 -
 .../src/site/asciidoc/users/transports/index.adoc  |   28 -
 .../asciidoc/users/transports/pcap-replay.adoc     |   68 -
 .../site/asciidoc/users/transports/raw-socket.adoc |   52 -
 .../src/site/asciidoc/users/transports/serial.adoc |   55 -
 .../site/asciidoc/users/transports/socketcan.adoc  |   67 -
 .../src/site/asciidoc/users/transports/tcp.adoc    |   52 -
 .../src/site/asciidoc/users/transports/udp.adoc    |   52 -
 .../src/site/resources-filtered/plc4x-doap.rdf     |  189 ---
 .../it/plc4x-website/src/site/resources/.asf.yaml  |   19 -
 .../it/plc4x-website/src/site/resources/.htaccess  |   20 -
 .../resources/css/bootstrap-responsive.min.css     |   20 -
 .../plc4x-website/src/site/resources/css/site.css  |   91 --
 .../site/resources/images/apache_brooklyn_logo.png |  Bin 4892 -> 0 bytes
 .../src/site/resources/images/apache_logo.png      |  Bin 16457 -> 0 bytes
 .../site/resources/images/apache_logo_small.png    |  Bin 7763 -> 0 bytes
 .../site/resources/images/apache_mynewt_logo.png   |  Bin 157734 -> 0 bytes
 .../site/resources/images/apache_plc4x_logo.png    |  Bin 46022 -> 0 bytes
 .../resources/images/apache_plc4x_logo_small.png   |  Bin 10460 -> 0 bytes
 .../site/resources/images/background-index-3.png   |  Bin 1258500 -> 0 bytes
 .../resources/images/community-contribute-fork.png |  Bin 195211 -> 0 bytes
 .../contributing-github-create-pull-request.png    |  Bin 112177 -> 0 bytes
 .../resources/images/contributing-github-fork.png  |  Bin 96553 -> 0 bytes
 .../images/integrations/apache_calcite_logo.svg    |  346 ----
 .../images/integrations/apache_camel_logo.png      |  Bin 15358 -> 0 bytes
 .../images/integrations/apache_hop_logo.png        |  Bin 75995 -> 0 bytes
 .../images/integrations/apache_iotdb_logo.png      |  Bin 54876 -> 0 bytes
 .../images/integrations/apache_kafka_logo.png      |  Bin 78411 -> 0 bytes
 .../images/integrations/apache_nifi_logo.svg       |   19 -
 .../integrations/apache_streampipes_logo.png       |  Bin 24942 -> 0 bytes
 .../images/integrations/eclipse_ditto_logo.png     |  Bin 3371 -> 0 bytes
 .../images/integrations/elastic_logstash_logo.png  |  Bin 9241 -> 0 bytes
 .../images/integrations/nifi/add-processor.png     |  Bin 25508 -> 0 bytes
 .../nifi/configure-processor-properties.png        |  Bin 36219 -> 0 bytes
 .../integrations/nifi/configure-scheduling.png     |  Bin 37276 -> 0 bytes
 .../images/integrations/nifi/configured-flow.png   |  Bin 130333 -> 0 bytes
 .../integrations/nifi/configured-log-processor.png |  Bin 54626 -> 0 bytes
 .../nifi/configured-plc4x-source-processor.png     |  Bin 41203 -> 0 bytes
 .../integrations/nifi/configuring-connection.png   |  Bin 39490 -> 0 bytes
 .../images/integrations/nifi/empty-nifi-flow.png   |  Bin 74244 -> 0 bytes
 .../integrations/nifi/list-of-plc4x-processors.png |  Bin 103175 -> 0 bytes
 .../images/integrations/nifi/running-flow.png      |  Bin 59506 -> 0 bytes
 .../src/site/resources/images/iot-lab.jpg          |  Bin 664977 -> 0 bytes
 .../src/site/resources/images/languages/c_logo.png |  Bin 23215 -> 0 bytes
 .../site/resources/images/languages/cs_logo.png    |  Bin 98426 -> 0 bytes
 .../site/resources/images/languages/go_logo.png    |  Bin 30834 -> 0 bytes
 .../site/resources/images/languages/java_logo.png  |  Bin 88149 -> 0 bytes
 .../resources/images/languages/python_logo.png     |  Bin 98345 -> 0 bytes
 .../neo4j-intellij-database-connections-view.png   |  Bin 54579 -> 0 bytes
 .../images/neo4j-intellij-query-results.png        |  Bin 177104 -> 0 bytes
 .../resources/images/neo4j-intellij-settings.png   |  Bin 75308 -> 0 bytes
 .../site/resources/images/neo4j-web-console.png    |  Bin 1194388 -> 0 bytes
 .../images/plcs/plc4x-vpn-beckhoff-route-1.png     |  Bin 99036 -> 0 bytes
 .../images/plcs/plc4x-vpn-beckhoff-route-2.png     |  Bin 87524 -> 0 bytes
 .../images/plcs/plc4x-vpn-beckhoff-route-3.png     |  Bin 185843 -> 0 bytes
 .../resources/images/plcs/plc4x-vpn-beckhoff.jpg   |  Bin 177770 -> 0 bytes
 .../images/plcs/plc4x-vpn-client-download.png      |  Bin 83864 -> 0 bytes
 .../site/resources/images/plcs/plc4x-vpn-fatek.jpg |  Bin 175304 -> 0 bytes
 .../images/plcs/plc4x-vpn-siemens-hmi.jpg          |  Bin 129282 -> 0 bytes
 .../resources/images/plcs/plc4x-vpn-siemens-s7.jpg |  Bin 146523 -> 0 bytes
 .../site/resources/images/plcs/plc4x-vpn-wago.jpg  |  Bin 195501 -> 0 bytes
 .../site/resources/images/protocols/ads-ams.png    |  Bin 13600 -> 0 bytes
 .../site/resources/images/protocols/bacnet-ip.gif  |  Bin 32674 -> 0 bytes
 .../src/site/resources/images/protocols/mi_001.png |  Bin 10574 -> 0 bytes
 ...release-git-diff-next-development-iteration.png |  Bin 134548 -> 0 bytes
 .../images/release-git-diff-prepare-release.png    |  Bin 132752 -> 0 bytes
 .../site/resources/images/release-git-history.png  |  Bin 160255 -> 0 bytes
 .../resources/images/s7-tia-device-settings.png    |  Bin 391398 -> 0 bytes
 .../site/resources/images/s7-tia-io-settings.png   |  Bin 42175 -> 0 bytes
 .../src/site/resources/images/s7_banner.png        |  Bin 42137 -> 0 bytes
 .../src/site/resources/images/s7_url.png           |  Bin 10248 -> 0 bytes
 .../src/site/resources/images/team/cdutz.png       |  Bin 66024 -> 0 bytes
 .../src/site/resources/images/team/glcj.jpg        |  Bin 38971 -> 0 bytes
 .../src/site/resources/images/team/hutcheb.png     |  Bin 89226 -> 0 bytes
 .../src/site/resources/images/team/jfeinauer.jpg   |  Bin 24689 -> 0 bytes
 .../src/site/resources/images/team/ldywicki.jpg    |  Bin 12197 -> 0 bytes
 .../src/site/resources/images/team/lott.jpg        |  Bin 635973 -> 0 bytes
 .../src/site/resources/images/team/mstrljic.jpg    |  Bin 28604 -> 0 bytes
 .../src/site/resources/images/team/sruehl.jpg      |  Bin 15008 -> 0 bytes
 .../src/site/resources/images/team/tmitsch.png     |  Bin 33005 -> 0 bytes
 .../site/resources/images/toddy-loves-apache.png   |  Bin 265483 -> 0 bytes
 .../images/tutorials/modbus/ModbusPal-1.png        |  Bin 133977 -> 0 bytes
 .../images/tutorials/modbus/ModbusPal-2.png        |  Bin 267000 -> 0 bytes
 .../images/tutorials/modbus/ModbusPal-3.png        |  Bin 148179 -> 0 bytes
 .../images/tutorials/modbus/ModbusPal-4.png        |  Bin 167981 -> 0 bytes
 .../images/tutorials/modbus/ModbusPal-5.png        |  Bin 76694 -> 0 bytes
 .../images/tutorials/modbus/ModbusPal-6.png        |  Bin 99660 -> 0 bytes
 .../images/tutorials/modbus/ModbusPal-7.png        |  Bin 228335 -> 0 bytes
 .../images/tutorials/modbus/ModbusPal-8.png        |  Bin 122029 -> 0 bytes
 .../images/tutorials/modbus/ModbusPal-9.png        |  Bin 99947 -> 0 bytes
 .../site/resources/images/tutorials/s7/s7_url.png  |  Bin 10248 -> 0 bytes
 .../images/users/companies/logo-c-ware.png         |  Bin 18489 -> 0 bytes
 .../images/users/companies/logo-codecentric.png    |  Bin 26220 -> 0 bytes
 .../images/users/companies/logo-connectorio.png    |  Bin 17271 -> 0 bytes
 .../images/users/companies/logo-industryfusion.png |  Bin 15414 -> 0 bytes
 .../companies/logo-lebbing-automation-drives.png   |  Bin 13626 -> 0 bytes
 .../images/users/companies/logo-pietrorimoldi.jpg  |  Bin 584330 -> 0 bytes
 .../users/companies/logo-pragmatic-industries.svg  |  498 ------
 .../users/companies/logo-pragmatic-minds.svg       |  714 ---------
 .../images/users/companies/logo-timecho.png        |  Bin 21130 -> 0 bytes
 .../logo_record_evolution_single_dark_bgfont.png   |  Bin 10498 -> 0 bytes
 .../users/companies/logo_unistuttgart_isw.png      |  Bin 31592 -> 0 bytes
 .../images/users/protocols/ads_banner.png          |  Bin 32795 -> 0 bytes
 .../images/users/protocols/bacnet_banner.png       |  Bin 35191 -> 0 bytes
 .../images/users/protocols/can_banner.png          |  Bin 32528 -> 0 bytes
 .../images/users/protocols/knx_banner.png          |  Bin 32859 -> 0 bytes
 .../resources/images/users/protocols/mi_001.png    |  Bin 10574 -> 0 bytes
 .../users/protocols/s7-tia-device-settings.png     |  Bin 391398 -> 0 bytes
 .../images/users/protocols/s7-tia-io-settings.png  |  Bin 42175 -> 0 bytes
 .../site/resources/images/users/protocols/s7.png   |  Bin 19399 -> 0 bytes
 .../resources/images/users/protocols/s7_alert.png  |  Bin 19948 -> 0 bytes
 .../resources/images/users/protocols/s7_banner.png |  Bin 42137 -> 0 bytes
 .../images/users/protocols/s7_caution.png          |  Bin 18944 -> 0 bytes
 .../resources/images/users/protocols/s7_danger.png |  Bin 20452 -> 0 bytes
 .../resources/images/users/protocols/s7_dont.png   |  Bin 20067 -> 0 bytes
 .../resources/images/users/protocols/s7_ex.png     |  Bin 20057 -> 0 bytes
 .../images/users/protocols/s7_important.png        |  Bin 19667 -> 0 bytes
 .../resources/images/users/protocols/s7_note.png   |  Bin 19486 -> 0 bytes
 .../resources/images/users/protocols/s7_tip.png    |  Bin 20231 -> 0 bytes
 .../resources/images/users/protocols/s7_toddy.png  |  Bin 20356 -> 0 bytes
 .../resources/images/users/protocols/s7_url.png    |  Bin 10248 -> 0 bytes
 .../images/users/protocols/s7_warning.png          |  Bin 19172 -> 0 bytes
 .../plc4x-website/src/site/resources/plc4go.html   |   41 -
 .../plc4x-website/src/site/resources/plc4x-pmc.rdf |  109 --
 .../src/it/plc4x-website/src/site/site.xml         |  168 --
 plc4x-site-skin/src/it/settings.xml                |   53 -
 .../main/resources/META-INF/maven/site-macros.vm   |  486 ------
 .../src/main/resources/META-INF/maven/site.vm      |  162 --
 .../src/main/resources/META-INF/maven/skin.xml     |   25 -
 .../src/main/resources/css/maven-base.css          |  168 --
 .../src/main/resources/css/maven-theme.css         |  155 --
 plc4x-site-skin/src/main/resources/css/print.css   |   26 -
 .../src/main/resources/css/themes/plc4x.css        |  945 -----------
 .../src/main/resources/images/expanded.gif         |  Bin 52 -> 0 bytes
 .../src/main/resources/images/external.png         |  Bin 230 -> 0 bytes
 .../src/main/resources/images/icon_error_sml.gif   |  Bin 1010 -> 0 bytes
 .../src/main/resources/images/icon_info_sml.gif    |  Bin 606 -> 0 bytes
 .../src/main/resources/images/icon_success_sml.gif |  Bin 990 -> 0 bytes
 .../src/main/resources/images/icon_warning_sml.gif |  Bin 576 -> 0 bytes
 .../src/main/resources/images/maven-feather.png    |  Bin 3581 -> 0 bytes
 .../src/main/resources/images/newwindow.png        |  Bin 220 -> 0 bytes
 pom.xml                                            |    1 -
 269 files changed, 3 insertions(+), 21627 deletions(-)

diff --git a/LICENSE b/LICENSE
index eec7469..ff9ad45 100644
--- a/LICENSE
+++ b/LICENSE
@@ -200,16 +200,3 @@
    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    See the License for the specific language governing permissions and
    limitations under the License.
-
-===============================================================
-
-The Files:
-plc4j/utils/raw-sockets/src/main/java/org/apache/plc4x/java/utils/rawsockets/RawSocketListener.java
-plc4j/utils/raw-sockets/src/main/java/org/apache/plc4x/java/utils/rawsockets/RawIpSocket.java
-plc4j/utils/raw-sockets/src/main/java/org/apache/plc4x/java/utils/rawsockets/RawSocketException.java
-plc4j/utils/raw-sockets/src/main/java/org/apache/plc4x/java/utils/rawsockets/RawSocketListener.java
-Are copyrighted by the The Netty Project which is distributed under the Apache 2.0 license.
-
-The File:
-plc4x-site-skin/src/main/resources/css/plc4x.css
-is a customized version of a field copied from https://github.com/darshandsoni/asciidoctor-skins/blob/gh-pages/css/adoc-foundation.css
\ No newline at end of file
diff --git a/code-generation/NOTICE b/code-generation/NOTICE
index 752d06e..0151f38 100644
--- a/code-generation/NOTICE
+++ b/code-generation/NOTICE
@@ -1,5 +1,5 @@
 Apache PLC4X
-Copyright 2017-2024 The Apache Software Foundation
+Copyright 2017-2025 The Apache Software Foundation
 
 This product includes software developed at
 The Apache Software Foundation (http://www.apache.org/).
\ No newline at end of file
diff --git a/code-generation/pom.xml b/code-generation/pom.xml
index 747828a..6db610f 100644
--- a/code-generation/pom.xml
+++ b/code-generation/pom.xml
@@ -28,7 +28,7 @@
   <parent>
     <groupId>org.apache</groupId>
     <artifactId>apache</artifactId>
-    <version>33</version>
+    <version>34</version>
     <relativePath />
   </parent>
 
diff --git a/code-generation/LICENSE b/code-generation/types-base/LICENSE
similarity index 100%
rename from code-generation/LICENSE
rename to code-generation/types-base/LICENSE
diff --git a/jenkins.pom b/jenkins.pom
index 6677a6e..d6e9533 100644
--- a/jenkins.pom
+++ b/jenkins.pom
@@ -26,7 +26,7 @@
     <parent>
         <groupId>org.apache</groupId>
         <artifactId>apache</artifactId>
-        <version>22</version>
+        <version>34</version>
     </parent>
 
     <groupId>org.apache.plc4x.plugins</groupId>
diff --git a/plc4x-site-skin/.mvn/extensions.xml b/plc4x-site-skin/.mvn/extensions.xml
deleted file mode 100644
index 1b3399b..0000000
--- a/plc4x-site-skin/.mvn/extensions.xml
+++ /dev/null
@@ -1,28 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
-  Licensed to the Apache Software Foundation (ASF) under one
-  or more contributor license agreements.  See the NOTICE file
-  distributed with this work for additional information
-  regarding copyright ownership.  The ASF licenses this file
-  to you under the Apache License, Version 2.0 (the
-  "License"); you may not use this file except in compliance
-  with the License.  You may obtain a copy of the License at
-
-      https://www.apache.org/licenses/LICENSE-2.0
-
-  Unless required by applicable law or agreed to in writing,
-  software distributed under the License is distributed on an
-  "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-  KIND, either express or implied.  See the License for the
-  specific language governing permissions and limitations
-  under the License.
-  -->
-<extensions xmlns="http://maven.apache.org/EXTENSIONS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-            xsi:schemaLocation="http://maven.apache.org/EXTENSIONS/1.0.0 http://maven.apache.org/xsd/core-extensions-1.0.0.xsd">
-  <!-- Currently causing a NPE when executing goals not bound to a specific maven lifecycle phase -->
-  <!--extension>
-    <groupId>com.soebes.maven.extensions</groupId>
-    <artifactId>maven-buildtime-profiler</artifactId>
-    <version>0.1.0</version>
-  </extension-->
-</extensions>
\ No newline at end of file
diff --git a/plc4x-site-skin/.mvn/jvm.config b/plc4x-site-skin/.mvn/jvm.config
deleted file mode 100644
index e2a50e0..0000000
--- a/plc4x-site-skin/.mvn/jvm.config
+++ /dev/null
@@ -1 +0,0 @@
---add-exports jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED --add-exports jdk.compiler/com.sun.tools.javac.file=ALL-UNNAMED --add-exports jdk.compiler/com.sun.tools.javac.parser=ALL-UNNAMED --add-exports jdk.compiler/com.sun.tools.javac.tree=ALL-UNNAMED --add-exports jdk.compiler/com.sun.tools.javac.util=ALL-UNNAMED
\ No newline at end of file
diff --git a/plc4x-site-skin/.mvn/wrapper/maven-wrapper.properties b/plc4x-site-skin/.mvn/wrapper/maven-wrapper.properties
deleted file mode 100644
index d58dfb7..0000000
--- a/plc4x-site-skin/.mvn/wrapper/maven-wrapper.properties
+++ /dev/null
@@ -1,19 +0,0 @@
-# Licensed to the Apache Software Foundation (ASF) under one
-# or more contributor license agreements.  See the NOTICE file
-# distributed with this work for additional information
-# regarding copyright ownership.  The ASF licenses this file
-# to you under the Apache License, Version 2.0 (the
-# "License"); you may not use this file except in compliance
-# with the License.  You may obtain a copy of the License at
-#
-#   http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing,
-# software distributed under the License is distributed on an
-# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-# KIND, either express or implied.  See the License for the
-# specific language governing permissions and limitations
-# under the License.
-wrapperVersion=3.3.2
-distributionType=only-script
-distributionUrl=https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.9/apache-maven-3.9.9-bin.zip
diff --git a/plc4x-site-skin/LICENSE b/plc4x-site-skin/LICENSE
deleted file mode 100644
index ff9ad45..0000000
--- a/plc4x-site-skin/LICENSE
+++ /dev/null
@@ -1,202 +0,0 @@
-
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS
-
-   APPENDIX: How to apply the Apache License to your work.
-
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "[]"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-
-   Copyright [yyyy] [name of copyright owner]
-
-   Licensed under the Apache License, Version 2.0 (the "License");
-   you may not use this file except in compliance with the License.
-   You may obtain a copy of the License at
-
-       https://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing, software
-   distributed under the License is distributed on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-   See the License for the specific language governing permissions and
-   limitations under the License.
diff --git a/plc4x-site-skin/NOTICE b/plc4x-site-skin/NOTICE
deleted file mode 100644
index 752d06e..0000000
--- a/plc4x-site-skin/NOTICE
+++ /dev/null
@@ -1,5 +0,0 @@
-Apache PLC4X
-Copyright 2017-2024 The Apache Software Foundation
-
-This product includes software developed at
-The Apache Software Foundation (http://www.apache.org/).
\ No newline at end of file
diff --git a/plc4x-site-skin/README b/plc4x-site-skin/README
deleted file mode 100644
index b660b79..0000000
--- a/plc4x-site-skin/README
+++ /dev/null
@@ -1,41 +0,0 @@
-PLC4X Build Tools: PLC4X Site Skin
-========================
-
-PLC4X Build Tools: PLC4X Site Skin is a sub-project of the Apache PLC4X project
-and contains all the tools needed to generate the main projects website using
-the maven site plugin.
-
-Environment
------------
-
-Currently the project is configured to require the following software:
-
-1) Java 8 JDK: For running Maven in general as well as compiling the Java and Scala
-modules `JAVA_HOME` configured to point to that.
-
-
-Getting Started
----------------
-
-Normally you wouldn't be required to build this module as the artifacts it produces
-will be made available via one of the maven repositories. However if you want to improve
-or fix the existing tools, you will have to build your version locally.
-
-You must have Java 8 installed on your system and connectivity to Maven Central
-(for downloading external third party dependencies). Maven will be automatically
-downloaded and installed by the maven wrapper `mvnw`.
-
-Build PLC4X Java jars and install them in your local maven repository
-
-$ mvn install
-
-This should make the build-tools available to the main projects build.
-In order to use your locally built version of the build-tools you should
-update the property: `plc4x-code-generation.version` in the PLC4X main pom.xml.
-
-
-
-Licensing
----------
-
-Apache PLC4X is released under the Apache License Version 2.0.
diff --git a/plc4x-site-skin/RELEASE_NOTES b/plc4x-site-skin/RELEASE_NOTES
deleted file mode 100644
index 913bfca..0000000
--- a/plc4x-site-skin/RELEASE_NOTES
+++ /dev/null
@@ -1,43 +0,0 @@
-==============================================================
-(Unreleased) PLC4X Build Tools: PLC4X Site Skin 1.2.0-SNAPSHOT
-==============================================================
-
-New Features
-------------
-
-Incompatible changes
---------------------
-
-Bug Fixes
----------
-
-==============================================================
-PLC4X Build Tools: PLC4X Site Skin 1.1.0
-==============================================================
-
-Changes:
-
-- Updated the skin to use the updated tooling for handling
-  Apache Events
-
-==============================================================
-PLC4X Build Tools: PLC4X Site Skin 1.0.0
-==============================================================
-
-This is the first official release of
-PLC4X Build Tools: PLC4X Site Skin.
-
-New Features
-------------
-
-- New `maven-site-plugin` skin
-
-Incompatible changes
---------------------
-
-- none
-
-Bug Fixes
----------
-
-- none
diff --git a/plc4x-site-skin/mvnw b/plc4x-site-skin/mvnw
deleted file mode 100755
index 19529dd..0000000
--- a/plc4x-site-skin/mvnw
+++ /dev/null
@@ -1,259 +0,0 @@
-#!/bin/sh
-# ----------------------------------------------------------------------------
-# Licensed to the Apache Software Foundation (ASF) under one
-# or more contributor license agreements.  See the NOTICE file
-# distributed with this work for additional information
-# regarding copyright ownership.  The ASF licenses this file
-# to you under the Apache License, Version 2.0 (the
-# "License"); you may not use this file except in compliance
-# with the License.  You may obtain a copy of the License at
-#
-#    http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing,
-# software distributed under the License is distributed on an
-# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-# KIND, either express or implied.  See the License for the
-# specific language governing permissions and limitations
-# under the License.
-# ----------------------------------------------------------------------------
-
-# ----------------------------------------------------------------------------
-# Apache Maven Wrapper startup batch script, version 3.3.2
-#
-# Optional ENV vars
-# -----------------
-#   JAVA_HOME - location of a JDK home dir, required when download maven via java source
-#   MVNW_REPOURL - repo url base for downloading maven distribution
-#   MVNW_USERNAME/MVNW_PASSWORD - user and password for downloading maven
-#   MVNW_VERBOSE - true: enable verbose log; debug: trace the mvnw script; others: silence the output
-# ----------------------------------------------------------------------------
-
-set -euf
-[ "${MVNW_VERBOSE-}" != debug ] || set -x
-
-# OS specific support.
-native_path() { printf %s\\n "$1"; }
-case "$(uname)" in
-CYGWIN* | MINGW*)
-  [ -z "${JAVA_HOME-}" ] || JAVA_HOME="$(cygpath --unix "$JAVA_HOME")"
-  native_path() { cygpath --path --windows "$1"; }
-  ;;
-esac
-
-# set JAVACMD and JAVACCMD
-set_java_home() {
-  # For Cygwin and MinGW, ensure paths are in Unix format before anything is touched
-  if [ -n "${JAVA_HOME-}" ]; then
-    if [ -x "$JAVA_HOME/jre/sh/java" ]; then
-      # IBM's JDK on AIX uses strange locations for the executables
-      JAVACMD="$JAVA_HOME/jre/sh/java"
-      JAVACCMD="$JAVA_HOME/jre/sh/javac"
-    else
-      JAVACMD="$JAVA_HOME/bin/java"
-      JAVACCMD="$JAVA_HOME/bin/javac"
-
-      if [ ! -x "$JAVACMD" ] || [ ! -x "$JAVACCMD" ]; then
-        echo "The JAVA_HOME environment variable is not defined correctly, so mvnw cannot run." >&2
-        echo "JAVA_HOME is set to \"$JAVA_HOME\", but \"\$JAVA_HOME/bin/java\" or \"\$JAVA_HOME/bin/javac\" does not exist." >&2
-        return 1
-      fi
-    fi
-  else
-    JAVACMD="$(
-      'set' +e
-      'unset' -f command 2>/dev/null
-      'command' -v java
-    )" || :
-    JAVACCMD="$(
-      'set' +e
-      'unset' -f command 2>/dev/null
-      'command' -v javac
-    )" || :
-
-    if [ ! -x "${JAVACMD-}" ] || [ ! -x "${JAVACCMD-}" ]; then
-      echo "The java/javac command does not exist in PATH nor is JAVA_HOME set, so mvnw cannot run." >&2
-      return 1
-    fi
-  fi
-}
-
-# hash string like Java String::hashCode
-hash_string() {
-  str="${1:-}" h=0
-  while [ -n "$str" ]; do
-    char="${str%"${str#?}"}"
-    h=$(((h * 31 + $(LC_CTYPE=C printf %d "'$char")) % 4294967296))
-    str="${str#?}"
-  done
-  printf %x\\n $h
-}
-
-verbose() { :; }
-[ "${MVNW_VERBOSE-}" != true ] || verbose() { printf %s\\n "${1-}"; }
-
-die() {
-  printf %s\\n "$1" >&2
-  exit 1
-}
-
-trim() {
-  # MWRAPPER-139:
-  #   Trims trailing and leading whitespace, carriage returns, tabs, and linefeeds.
-  #   Needed for removing poorly interpreted newline sequences when running in more
-  #   exotic environments such as mingw bash on Windows.
-  printf "%s" "${1}" | tr -d '[:space:]'
-}
-
-# parse distributionUrl and optional distributionSha256Sum, requires .mvn/wrapper/maven-wrapper.properties
-while IFS="=" read -r key value; do
-  case "${key-}" in
-  distributionUrl) distributionUrl=$(trim "${value-}") ;;
-  distributionSha256Sum) distributionSha256Sum=$(trim "${value-}") ;;
-  esac
-done <"${0%/*}/.mvn/wrapper/maven-wrapper.properties"
-[ -n "${distributionUrl-}" ] || die "cannot read distributionUrl property in ${0%/*}/.mvn/wrapper/maven-wrapper.properties"
-
-case "${distributionUrl##*/}" in
-maven-mvnd-*bin.*)
-  MVN_CMD=mvnd.sh _MVNW_REPO_PATTERN=/maven/mvnd/
-  case "${PROCESSOR_ARCHITECTURE-}${PROCESSOR_ARCHITEW6432-}:$(uname -a)" in
-  *AMD64:CYGWIN* | *AMD64:MINGW*) distributionPlatform=windows-amd64 ;;
-  :Darwin*x86_64) distributionPlatform=darwin-amd64 ;;
-  :Darwin*arm64) distributionPlatform=darwin-aarch64 ;;
-  :Linux*x86_64*) distributionPlatform=linux-amd64 ;;
-  *)
-    echo "Cannot detect native platform for mvnd on $(uname)-$(uname -m), use pure java version" >&2
-    distributionPlatform=linux-amd64
-    ;;
-  esac
-  distributionUrl="${distributionUrl%-bin.*}-$distributionPlatform.zip"
-  ;;
-maven-mvnd-*) MVN_CMD=mvnd.sh _MVNW_REPO_PATTERN=/maven/mvnd/ ;;
-*) MVN_CMD="mvn${0##*/mvnw}" _MVNW_REPO_PATTERN=/org/apache/maven/ ;;
-esac
-
-# apply MVNW_REPOURL and calculate MAVEN_HOME
-# maven home pattern: ~/.m2/wrapper/dists/{apache-maven-<version>,maven-mvnd-<version>-<platform>}/<hash>
-[ -z "${MVNW_REPOURL-}" ] || distributionUrl="$MVNW_REPOURL$_MVNW_REPO_PATTERN${distributionUrl#*"$_MVNW_REPO_PATTERN"}"
-distributionUrlName="${distributionUrl##*/}"
-distributionUrlNameMain="${distributionUrlName%.*}"
-distributionUrlNameMain="${distributionUrlNameMain%-bin}"
-MAVEN_USER_HOME="${MAVEN_USER_HOME:-${HOME}/.m2}"
-MAVEN_HOME="${MAVEN_USER_HOME}/wrapper/dists/${distributionUrlNameMain-}/$(hash_string "$distributionUrl")"
-
-exec_maven() {
-  unset MVNW_VERBOSE MVNW_USERNAME MVNW_PASSWORD MVNW_REPOURL || :
-  exec "$MAVEN_HOME/bin/$MVN_CMD" "$@" || die "cannot exec $MAVEN_HOME/bin/$MVN_CMD"
-}
-
-if [ -d "$MAVEN_HOME" ]; then
-  verbose "found existing MAVEN_HOME at $MAVEN_HOME"
-  exec_maven "$@"
-fi
-
-case "${distributionUrl-}" in
-*?-bin.zip | *?maven-mvnd-?*-?*.zip) ;;
-*) die "distributionUrl is not valid, must match *-bin.zip or maven-mvnd-*.zip, but found '${distributionUrl-}'" ;;
-esac
-
-# prepare tmp dir
-if TMP_DOWNLOAD_DIR="$(mktemp -d)" && [ -d "$TMP_DOWNLOAD_DIR" ]; then
-  clean() { rm -rf -- "$TMP_DOWNLOAD_DIR"; }
-  trap clean HUP INT TERM EXIT
-else
-  die "cannot create temp dir"
-fi
-
-mkdir -p -- "${MAVEN_HOME%/*}"
-
-# Download and Install Apache Maven
-verbose "Couldn't find MAVEN_HOME, downloading and installing it ..."
-verbose "Downloading from: $distributionUrl"
-verbose "Downloading to: $TMP_DOWNLOAD_DIR/$distributionUrlName"
-
-# select .zip or .tar.gz
-if ! command -v unzip >/dev/null; then
-  distributionUrl="${distributionUrl%.zip}.tar.gz"
-  distributionUrlName="${distributionUrl##*/}"
-fi
-
-# verbose opt
-__MVNW_QUIET_WGET=--quiet __MVNW_QUIET_CURL=--silent __MVNW_QUIET_UNZIP=-q __MVNW_QUIET_TAR=''
-[ "${MVNW_VERBOSE-}" != true ] || __MVNW_QUIET_WGET='' __MVNW_QUIET_CURL='' __MVNW_QUIET_UNZIP='' __MVNW_QUIET_TAR=v
-
-# normalize http auth
-case "${MVNW_PASSWORD:+has-password}" in
-'') MVNW_USERNAME='' MVNW_PASSWORD='' ;;
-has-password) [ -n "${MVNW_USERNAME-}" ] || MVNW_USERNAME='' MVNW_PASSWORD='' ;;
-esac
-
-if [ -z "${MVNW_USERNAME-}" ] && command -v wget >/dev/null; then
-  verbose "Found wget ... using wget"
-  wget ${__MVNW_QUIET_WGET:+"$__MVNW_QUIET_WGET"} "$distributionUrl" -O "$TMP_DOWNLOAD_DIR/$distributionUrlName" || die "wget: Failed to fetch $distributionUrl"
-elif [ -z "${MVNW_USERNAME-}" ] && command -v curl >/dev/null; then
-  verbose "Found curl ... using curl"
-  curl ${__MVNW_QUIET_CURL:+"$__MVNW_QUIET_CURL"} -f -L -o "$TMP_DOWNLOAD_DIR/$distributionUrlName" "$distributionUrl" || die "curl: Failed to fetch $distributionUrl"
-elif set_java_home; then
-  verbose "Falling back to use Java to download"
-  javaSource="$TMP_DOWNLOAD_DIR/Downloader.java"
-  targetZip="$TMP_DOWNLOAD_DIR/$distributionUrlName"
-  cat >"$javaSource" <<-END
-	public class Downloader extends java.net.Authenticator
-	{
-	  protected java.net.PasswordAuthentication getPasswordAuthentication()
-	  {
-	    return new java.net.PasswordAuthentication( System.getenv( "MVNW_USERNAME" ), System.getenv( "MVNW_PASSWORD" ).toCharArray() );
-	  }
-	  public static void main( String[] args ) throws Exception
-	  {
-	    setDefault( new Downloader() );
-	    java.nio.file.Files.copy( java.net.URI.create( args[0] ).toURL().openStream(), java.nio.file.Paths.get( args[1] ).toAbsolutePath().normalize() );
-	  }
-	}
-	END
-  # For Cygwin/MinGW, switch paths to Windows format before running javac and java
-  verbose " - Compiling Downloader.java ..."
-  "$(native_path "$JAVACCMD")" "$(native_path "$javaSource")" || die "Failed to compile Downloader.java"
-  verbose " - Running Downloader.java ..."
-  "$(native_path "$JAVACMD")" -cp "$(native_path "$TMP_DOWNLOAD_DIR")" Downloader "$distributionUrl" "$(native_path "$targetZip")"
-fi
-
-# If specified, validate the SHA-256 sum of the Maven distribution zip file
-if [ -n "${distributionSha256Sum-}" ]; then
-  distributionSha256Result=false
-  if [ "$MVN_CMD" = mvnd.sh ]; then
-    echo "Checksum validation is not supported for maven-mvnd." >&2
-    echo "Please disable validation by removing 'distributionSha256Sum' from your maven-wrapper.properties." >&2
-    exit 1
-  elif command -v sha256sum >/dev/null; then
-    if echo "$distributionSha256Sum  $TMP_DOWNLOAD_DIR/$distributionUrlName" | sha256sum -c >/dev/null 2>&1; then
-      distributionSha256Result=true
-    fi
-  elif command -v shasum >/dev/null; then
-    if echo "$distributionSha256Sum  $TMP_DOWNLOAD_DIR/$distributionUrlName" | shasum -a 256 -c >/dev/null 2>&1; then
-      distributionSha256Result=true
-    fi
-  else
-    echo "Checksum validation was requested but neither 'sha256sum' or 'shasum' are available." >&2
-    echo "Please install either command, or disable validation by removing 'distributionSha256Sum' from your maven-wrapper.properties." >&2
-    exit 1
-  fi
-  if [ $distributionSha256Result = false ]; then
-    echo "Error: Failed to validate Maven distribution SHA-256, your Maven distribution might be compromised." >&2
-    echo "If you updated your Maven version, you need to update the specified distributionSha256Sum property." >&2
-    exit 1
-  fi
-fi
-
-# unzip and move
-if command -v unzip >/dev/null; then
-  unzip ${__MVNW_QUIET_UNZIP:+"$__MVNW_QUIET_UNZIP"} "$TMP_DOWNLOAD_DIR/$distributionUrlName" -d "$TMP_DOWNLOAD_DIR" || die "failed to unzip"
-else
-  tar xzf${__MVNW_QUIET_TAR:+"$__MVNW_QUIET_TAR"} "$TMP_DOWNLOAD_DIR/$distributionUrlName" -C "$TMP_DOWNLOAD_DIR" || die "failed to untar"
-fi
-printf %s\\n "$distributionUrl" >"$TMP_DOWNLOAD_DIR/$distributionUrlNameMain/mvnw.url"
-mv -- "$TMP_DOWNLOAD_DIR/$distributionUrlNameMain" "$MAVEN_HOME" || [ -d "$MAVEN_HOME" ] || die "fail to move MAVEN_HOME"
-
-clean || :
-exec_maven "$@"
diff --git a/plc4x-site-skin/mvnw.cmd b/plc4x-site-skin/mvnw.cmd
deleted file mode 100644
index 249bdf3..0000000
--- a/plc4x-site-skin/mvnw.cmd
+++ /dev/null
@@ -1,149 +0,0 @@
-<# : batch portion
-@REM ----------------------------------------------------------------------------
-@REM Licensed to the Apache Software Foundation (ASF) under one
-@REM or more contributor license agreements.  See the NOTICE file
-@REM distributed with this work for additional information
-@REM regarding copyright ownership.  The ASF licenses this file
-@REM to you under the Apache License, Version 2.0 (the
-@REM "License"); you may not use this file except in compliance
-@REM with the License.  You may obtain a copy of the License at
-@REM
-@REM    http://www.apache.org/licenses/LICENSE-2.0
-@REM
-@REM Unless required by applicable law or agreed to in writing,
-@REM software distributed under the License is distributed on an
-@REM "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-@REM KIND, either express or implied.  See the License for the
-@REM specific language governing permissions and limitations
-@REM under the License.
-@REM ----------------------------------------------------------------------------
-
-@REM ----------------------------------------------------------------------------
-@REM Apache Maven Wrapper startup batch script, version 3.3.2
-@REM
-@REM Optional ENV vars
-@REM   MVNW_REPOURL - repo url base for downloading maven distribution
-@REM   MVNW_USERNAME/MVNW_PASSWORD - user and password for downloading maven
-@REM   MVNW_VERBOSE - true: enable verbose log; others: silence the output
-@REM ----------------------------------------------------------------------------
-
-@IF "%__MVNW_ARG0_NAME__%"=="" (SET __MVNW_ARG0_NAME__=%~nx0)
-@SET __MVNW_CMD__=
-@SET __MVNW_ERROR__=
-@SET __MVNW_PSMODULEP_SAVE=%PSModulePath%
-@SET PSModulePath=
-@FOR /F "usebackq tokens=1* delims==" %%A IN (`powershell -noprofile "& {$scriptDir='%~dp0'; $script='%__MVNW_ARG0_NAME__%'; icm -ScriptBlock ([Scriptblock]::Create((Get-Content -Raw '%~f0'))) -NoNewScope}"`) DO @(
-  IF "%%A"=="MVN_CMD" (set __MVNW_CMD__=%%B) ELSE IF "%%B"=="" (echo %%A) ELSE (echo %%A=%%B)
-)
-@SET PSModulePath=%__MVNW_PSMODULEP_SAVE%
-@SET __MVNW_PSMODULEP_SAVE=
-@SET __MVNW_ARG0_NAME__=
-@SET MVNW_USERNAME=
-@SET MVNW_PASSWORD=
-@IF NOT "%__MVNW_CMD__%"=="" (%__MVNW_CMD__% %*)
-@echo Cannot start maven from wrapper >&2 && exit /b 1
-@GOTO :EOF
-: end batch / begin powershell #>
-
-$ErrorActionPreference = "Stop"
-if ($env:MVNW_VERBOSE -eq "true") {
-  $VerbosePreference = "Continue"
-}
-
-# calculate distributionUrl, requires .mvn/wrapper/maven-wrapper.properties
-$distributionUrl = (Get-Content -Raw "$scriptDir/.mvn/wrapper/maven-wrapper.properties" | ConvertFrom-StringData).distributionUrl
-if (!$distributionUrl) {
-  Write-Error "cannot read distributionUrl property in $scriptDir/.mvn/wrapper/maven-wrapper.properties"
-}
-
-switch -wildcard -casesensitive ( $($distributionUrl -replace '^.*/','') ) {
-  "maven-mvnd-*" {
-    $USE_MVND = $true
-    $distributionUrl = $distributionUrl -replace '-bin\.[^.]*$',"-windows-amd64.zip"
-    $MVN_CMD = "mvnd.cmd"
-    break
-  }
-  default {
-    $USE_MVND = $false
-    $MVN_CMD = $script -replace '^mvnw','mvn'
-    break
-  }
-}
-
-# apply MVNW_REPOURL and calculate MAVEN_HOME
-# maven home pattern: ~/.m2/wrapper/dists/{apache-maven-<version>,maven-mvnd-<version>-<platform>}/<hash>
-if ($env:MVNW_REPOURL) {
-  $MVNW_REPO_PATTERN = if ($USE_MVND) { "/org/apache/maven/" } else { "/maven/mvnd/" }
-  $distributionUrl = "$env:MVNW_REPOURL$MVNW_REPO_PATTERN$($distributionUrl -replace '^.*'+$MVNW_REPO_PATTERN,'')"
-}
-$distributionUrlName = $distributionUrl -replace '^.*/',''
-$distributionUrlNameMain = $distributionUrlName -replace '\.[^.]*$','' -replace '-bin$',''
-$MAVEN_HOME_PARENT = "$HOME/.m2/wrapper/dists/$distributionUrlNameMain"
-if ($env:MAVEN_USER_HOME) {
-  $MAVEN_HOME_PARENT = "$env:MAVEN_USER_HOME/wrapper/dists/$distributionUrlNameMain"
-}
-$MAVEN_HOME_NAME = ([System.Security.Cryptography.MD5]::Create().ComputeHash([byte[]][char[]]$distributionUrl) | ForEach-Object {$_.ToString("x2")}) -join ''
-$MAVEN_HOME = "$MAVEN_HOME_PARENT/$MAVEN_HOME_NAME"
-
-if (Test-Path -Path "$MAVEN_HOME" -PathType Container) {
-  Write-Verbose "found existing MAVEN_HOME at $MAVEN_HOME"
-  Write-Output "MVN_CMD=$MAVEN_HOME/bin/$MVN_CMD"
-  exit $?
-}
-
-if (! $distributionUrlNameMain -or ($distributionUrlName -eq $distributionUrlNameMain)) {
-  Write-Error "distributionUrl is not valid, must end with *-bin.zip, but found $distributionUrl"
-}
-
-# prepare tmp dir
-$TMP_DOWNLOAD_DIR_HOLDER = New-TemporaryFile
-$TMP_DOWNLOAD_DIR = New-Item -Itemtype Directory -Path "$TMP_DOWNLOAD_DIR_HOLDER.dir"
-$TMP_DOWNLOAD_DIR_HOLDER.Delete() | Out-Null
-trap {
-  if ($TMP_DOWNLOAD_DIR.Exists) {
-    try { Remove-Item $TMP_DOWNLOAD_DIR -Recurse -Force | Out-Null }
-    catch { Write-Warning "Cannot remove $TMP_DOWNLOAD_DIR" }
-  }
-}
-
-New-Item -Itemtype Directory -Path "$MAVEN_HOME_PARENT" -Force | Out-Null
-
-# Download and Install Apache Maven
-Write-Verbose "Couldn't find MAVEN_HOME, downloading and installing it ..."
-Write-Verbose "Downloading from: $distributionUrl"
-Write-Verbose "Downloading to: $TMP_DOWNLOAD_DIR/$distributionUrlName"
-
-$webclient = New-Object System.Net.WebClient
-if ($env:MVNW_USERNAME -and $env:MVNW_PASSWORD) {
-  $webclient.Credentials = New-Object System.Net.NetworkCredential($env:MVNW_USERNAME, $env:MVNW_PASSWORD)
-}
-[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
-$webclient.DownloadFile($distributionUrl, "$TMP_DOWNLOAD_DIR/$distributionUrlName") | Out-Null
-
-# If specified, validate the SHA-256 sum of the Maven distribution zip file
-$distributionSha256Sum = (Get-Content -Raw "$scriptDir/.mvn/wrapper/maven-wrapper.properties" | ConvertFrom-StringData).distributionSha256Sum
-if ($distributionSha256Sum) {
-  if ($USE_MVND) {
-    Write-Error "Checksum validation is not supported for maven-mvnd. `nPlease disable validation by removing 'distributionSha256Sum' from your maven-wrapper.properties."
-  }
-  Import-Module $PSHOME\Modules\Microsoft.PowerShell.Utility -Function Get-FileHash
-  if ((Get-FileHash "$TMP_DOWNLOAD_DIR/$distributionUrlName" -Algorithm SHA256).Hash.ToLower() -ne $distributionSha256Sum) {
-    Write-Error "Error: Failed to validate Maven distribution SHA-256, your Maven distribution might be compromised. If you updated your Maven version, you need to update the specified distributionSha256Sum property."
-  }
-}
-
-# unzip and move
-Expand-Archive "$TMP_DOWNLOAD_DIR/$distributionUrlName" -DestinationPath "$TMP_DOWNLOAD_DIR" | Out-Null
-Rename-Item -Path "$TMP_DOWNLOAD_DIR/$distributionUrlNameMain" -NewName $MAVEN_HOME_NAME | Out-Null
-try {
-  Move-Item -Path "$TMP_DOWNLOAD_DIR/$MAVEN_HOME_NAME" -Destination $MAVEN_HOME_PARENT | Out-Null
-} catch {
-  if (! (Test-Path -Path "$MAVEN_HOME" -PathType Container)) {
-    Write-Error "fail to move MAVEN_HOME"
-  }
-} finally {
-  try { Remove-Item $TMP_DOWNLOAD_DIR -Recurse -Force | Out-Null }
-  catch { Write-Warning "Cannot remove $TMP_DOWNLOAD_DIR" }
-}
-
-Write-Output "MVN_CMD=$MAVEN_HOME/bin/$MVN_CMD"
diff --git a/plc4x-site-skin/pom.xml b/plc4x-site-skin/pom.xml
deleted file mode 100644
index b23431c..0000000
--- a/plc4x-site-skin/pom.xml
+++ /dev/null
@@ -1,450 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
-  Licensed to the Apache Software Foundation (ASF) under one
-  or more contributor license agreements.  See the NOTICE file
-  distributed with this work for additional information
-  regarding copyright ownership.  The ASF licenses this file
-  to you under the Apache License, Version 2.0 (the
-  "License"); you may not use this file except in compliance
-  with the License.  You may obtain a copy of the License at
-
-      https://www.apache.org/licenses/LICENSE-2.0
-
-  Unless required by applicable law or agreed to in writing,
-  software distributed under the License is distributed on an
-  "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-  KIND, either express or implied.  See the License for the
-  specific language governing permissions and limitations
-  under the License.
-  -->
-<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
-  <modelVersion>4.0.0</modelVersion>
-
-  <!--
-    This is intentionally set to the apache parent as this way
-    we can release this module separately from the rest of the project
-  -->
-  <parent>
-    <groupId>org.apache</groupId>
-    <artifactId>apache</artifactId>
-    <version>33</version>
-    <relativePath />
-  </parent>
-
-  <groupId>org.apache.plc4x.plugins</groupId>
-  <artifactId>plc4x-site-skin</artifactId>
-  <version>1.2.0-SNAPSHOT</version>
-
-  <name>PLC4X Build Tools: PLC4X Site Skin</name>
-
-  <properties>
-    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
-    <project.build.outputTimestamp>1</project.build.outputTimestamp>
-
-    <bootstrap.version>5.3.3</bootstrap.version>
-    <popper.version>2.8.0</popper.version>
-    <jquery.version>3.7.1</jquery.version>
-    <fontawesome.version>6.5.2</fontawesome.version>
-  </properties>
-
-  <scm>
-    <connection>scm:git:https://gitbox.apache.org/repos/asf/plc4x-build-tools.git</connection>
-    <developerConnection>scm:git:https://gitbox.apache.org/repos/asf/plc4x-build-tools.git</developerConnection>
-    <url>https://github.com/apache/plc4x-build-tools</url>
-    <tag>rel/plc4x-site-skin/1.0-2</tag>
-  </scm>
-
-  <build>
-    <plugins>
-      <!--
-        Download Bootstrap and Fontawesome.
-      -->
-      <plugin>
-        <groupId>com.googlecode.maven-download-plugin</groupId>
-        <artifactId>download-maven-plugin</artifactId>
-        <executions>
-          <execution>
-            <id>get-bootstrap</id>
-            <phase>generate-resources</phase>
-            <goals>
-              <goal>wget</goal>
-            </goals>
-            <configuration>
-              <url>https://github.com/twbs/bootstrap/releases/download/v${bootstrap.version}/bootstrap-${bootstrap.version}-dist.zip</url>
-              <unpack>true</unpack>
-              <outputDirectory>${project.build.directory}/dependency/bootstrap</outputDirectory>
-            </configuration>
-          </execution>
-          <execution>
-            <id>get-popper</id>
-            <phase>generate-resources</phase>
-            <goals>
-              <goal>wget</goal>
-            </goals>
-            <configuration>
-              <url>https://github.com/popperjs/popper.js/archive/v${popper.version}.zip</url>
-              <unpack>true</unpack>
-              <outputDirectory>${project.build.directory}/dependency/popper</outputDirectory>
-            </configuration>
-          </execution>
-          <execution>
-            <id>get-fontawesome</id>
-            <phase>generate-resources</phase>
-            <goals>
-              <goal>wget</goal>
-            </goals>
-            <configuration>
-              <url>https://use.fontawesome.com/releases/v${fontawesome.version}/fontawesome-free-${fontawesome.version}-web.zip</url>
-              <unpack>true</unpack>
-              <outputDirectory>${project.build.directory}/dependency/fontawesome</outputDirectory>
-            </configuration>
-          </execution>
-        </executions>
-      </plugin>
-
-      <plugin>
-        <groupId>org.apache.maven.plugins</groupId>
-        <artifactId>maven-dependency-plugin</artifactId>
-        <executions>
-          <execution>
-            <id>get-jquery</id>
-            <phase>generate-resources</phase>
-            <goals>
-              <goal>unpack</goal>
-            </goals>
-            <configuration>
-              <artifactItems>
-                <artifactItem>
-                  <groupId>org.webjars</groupId>
-                  <artifactId>jquery</artifactId>
-                  <version>${jquery.version}</version>
-                  <type>jar</type>
-                </artifactItem>
-              </artifactItems>
-              <outputDirectory>${project.build.directory}/dependency/jquery</outputDirectory>
-            </configuration>
-          </execution>
-        </executions>
-      </plugin>
-
-      <!--
-        Copy stuff from the downloaded bootstrap and fontawesome packages and hereby
-        assemble a local distribution customized to our needs.
-      -->
-      <plugin>
-        <groupId>org.apache.maven.plugins</groupId>
-        <artifactId>maven-resources-plugin</artifactId>
-        <executions>
-          <execution>
-            <id>copy-site-resources</id>
-            <phase>process-resources</phase>
-            <goals>
-              <goal>copy-resources</goal>
-            </goals>
-            <configuration>
-              <outputDirectory>${project.build.outputDirectory}</outputDirectory>
-              <resources>
-                <resource>
-                  <directory>${project.build.directory}/dependency/bootstrap/bootstrap-${bootstrap.version}-dist</directory>
-                  <includes>
-                    <include>css/*</include>
-                  </includes>
-                </resource>
-                <resource>
-                  <directory>${project.build.directory}/dependency/bootstrap/bootstrap-${bootstrap.version}-dist</directory>
-                  <includes>
-                    <include>js/*</include>
-                  </includes>
-                </resource>
-                <resource>
-                  <directory>
-                    ${project.build.directory}/dependency/fontawesome/fontawesome-free-${fontawesome.version}-web
-                  </directory>
-                  <includes>
-                    <include>css/all.min.css</include>
-                  </includes>
-                </resource>
-                <resource>
-                  <directory>
-                    ${project.build.directory}/dependency/fontawesome/fontawesome-free-${fontawesome.version}-web/webfonts
-                  </directory>
-                  <targetPath>fonts</targetPath>
-                </resource>
-                <resource>
-                  <directory>
-                    ${project.build.directory}/dependency/jquery/META-INF/resources/webjars/jquery/${jquery.version}
-                  </directory>
-                  <targetPath>js</targetPath>
-                </resource>
-                <resource>
-                  <directory>
-                    ${project.build.directory}/dependency/popper/popper-core-${popper.version}/dist/umd
-                  </directory>
-                  <targetPath>js</targetPath>
-                </resource>
-              </resources>
-            </configuration>
-          </execution>
-        </executions>
-        <!--configuration>
-          <delimiters>
-            <delimiter>@</delimiter>
-          </delimiters>
-          <useDefaultDelimiters>false</useDefaultDelimiters>
-        </configuration-->
-      </plugin>
-
-      <!--
-        The bootstrap uses "fonts" as directory for locating fonts and fontawesome uses "webfonts".
-        This plugin updates the css to also use "fonts".
-      -->
-      <plugin>
-        <groupId>com.google.code.maven-replacer-plugin</groupId>
-        <artifactId>replacer</artifactId>
-        <version>1.5.3</version>
-        <executions>
-          <execution>
-            <id>streamline-font-urls</id>
-            <!-- Only execute this for the parent module -->
-            <inherited>false</inherited>
-            <phase>process-resources</phase>
-            <goals>
-              <goal>replace</goal>
-            </goals>
-            <configuration>
-              <file>${project.build.outputDirectory}/css/all.min.css</file>
-              <replacements>
-                <replacement>
-                  <token>../webfonts/</token>
-                  <value>../fonts/</value>
-                </replacement>
-              </replacements>
-            </configuration>
-          </execution>
-        </executions>
-      </plugin>
-    </plugins>
-
-    <pluginManagement>
-      <plugins>
-        <plugin>
-          <groupId>org.apache.rat</groupId>
-          <artifactId>apache-rat-plugin</artifactId>
-          <version>0.16.1</version>
-        </plugin>
-        <plugin>
-          <groupId>org.apache.maven.plugins</groupId>
-          <artifactId>maven-clean-plugin</artifactId>
-          <version>3.4.0</version>
-        </plugin>
-        <plugin>
-          <groupId>org.apache.maven.plugins</groupId>
-          <artifactId>maven-dependency-plugin</artifactId>
-          <version>3.8.0</version>
-        </plugin>
-        <plugin>
-          <groupId>org.apache.maven.plugins</groupId>
-          <artifactId>maven-site-plugin</artifactId>
-          <version>4.0.0-M16</version>
-        </plugin>
-        <plugin>
-          <groupId>org.apache.maven.plugins</groupId>
-          <artifactId>maven-invoker-plugin</artifactId>
-          <version>3.7.0</version>
-        </plugin>
-        <plugin>
-          <groupId>org.apache.maven.plugins</groupId>
-          <artifactId>maven-resources-plugin</artifactId>
-          <version>3.3.1</version>
-        </plugin>
-        <plugin>
-          <groupId>org.apache.maven.plugins</groupId>
-          <artifactId>maven-compiler-plugin</artifactId>
-          <version>3.13.0</version>
-        </plugin>
-        <plugin>
-          <groupId>org.apache.maven.plugins</groupId>
-          <artifactId>maven-surefire-plugin</artifactId>
-          <version>3.5.2</version>
-        </plugin>
-        <plugin>
-          <groupId>org.apache.maven.plugins</groupId>
-          <artifactId>maven-jar-plugin</artifactId>
-          <version>3.4.2</version>
-        </plugin>
-        <plugin>
-          <groupId>org.apache.maven.plugins</groupId>
-          <artifactId>maven-install-plugin</artifactId>
-          <version>3.1.2</version>
-        </plugin>
-        <plugin>
-          <groupId>org.apache.maven.plugins</groupId>
-          <artifactId>maven-deploy-plugin</artifactId>
-          <version>3.1.3</version>
-        </plugin>
-        <plugin>
-          <groupId>org.apache.maven.plugins</groupId>
-          <artifactId>maven-assembly-plugin</artifactId>
-          <version>3.7.1</version>
-          <configuration>
-            <finalName>apache-plc4x-site-skin-${project.version}</finalName>
-          </configuration>
-        </plugin>
-        <plugin>
-          <groupId>com.googlecode.maven-download-plugin</groupId>
-          <artifactId>download-maven-plugin</artifactId>
-          <version>1.9.0</version>
-        </plugin>
-      </plugins>
-    </pluginManagement>
-  </build>
-
-  <profiles>
-    <profile>
-      <id>enable-all-checks</id>
-      <build>
-        <plugins>
-          <plugin>
-            <groupId>org.apache.maven.plugins</groupId>
-            <artifactId>maven-invoker-plugin</artifactId>
-            <configuration>
-              <debug>true</debug>
-              <projectsDirectory>src/it</projectsDirectory>
-              <cloneProjectsTo>${project.build.directory}/it</cloneProjectsTo>
-              <preBuildHookScript>setup</preBuildHookScript>
-              <postBuildHookScript>verify</postBuildHookScript>
-              <localRepositoryPath>${project.build.directory}/local-repo</localRepositoryPath>
-              <settingsFile>src/it/settings.xml</settingsFile>
-              <streamLogsOnFailures>true</streamLogsOnFailures>
-              <pomIncludes>
-                <pomInclude>*/pom.xml</pomInclude>
-              </pomIncludes>
-              <goals>
-                <goal>site</goal>
-              </goals>
-            </configuration>
-            <executions>
-              <execution>
-                <id>integration-test</id>
-                <goals>
-                  <goal>install</goal>
-                  <goal>integration-test</goal>
-                  <goal>verify</goal>
-                </goals>
-              </execution>
-            </executions>
-          </plugin>
-        </plugins>
-      </build>
-    </profile>
-
-    <profile>
-      <id>minify</id>
-      <build>
-        <resources>
-          <!-- exclude css and js since will include the minified version -->
-          <resource>
-            <directory>${basedir}/src/main/resources</directory>
-            <excludes>
-              <exclude>css/**</exclude>
-              <exclude>js/**</exclude>
-            </excludes>
-            <filtering>true</filtering> <!-- add skin-info -->
-          </resource>
-
-          <!-- include the print.css -->
-          <resource>
-            <directory>${basedir}/src/main/resources</directory>
-            <includes>
-              <include>css/print.css</include>
-            </includes>
-          </resource>
-
-          <!-- include minified only -->
-          <resource>
-            <directory>${project.build.directory}/${project.build.finalName}</directory>
-            <includes>
-              <include>css/plc4x-site-skin-${project.version}.min.css</include>
-              <include>js/plc4x-site-skin-${project.version}.min.js</include>
-            </includes>
-          </resource>
-        </resources>
-
-        <plugins>
-          <plugin>
-            <groupId>com.samaxes.maven</groupId>
-            <artifactId>maven-minify-plugin</artifactId>
-            <version>1.3.5.1</version>
-            <executions>
-              <execution>
-                <id>default-minify</id>
-                <phase>generate-resources</phase>
-                <goals>
-                  <goal>minify</goal>
-                </goals>
-                <configuration>
-                  <webappSourceDir>${basedir}/src/main/resources</webappSourceDir>
-                  <cssSourceDir>css</cssSourceDir>
-                  <cssSourceFiles>
-                    <cssSourceFile>maven-base.css</cssSourceFile>
-                    <cssSourceFile>maven-theme.css</cssSourceFile>
-                  </cssSourceFiles>
-                  <cssFinalFile>plc4x-site-skin-${project.version}.css</cssFinalFile>
-                  <!--jsSourceDir>js</jsSourceDir>
-                  <jsSourceFiles>
-                    <jsSourceFile>fluido.js</jsSourceFile>
-                  </jsSourceFiles>
-                  <jsFinalFile>plc4x-site-skin-${project.version}.js</jsFinalFile-->
-                </configuration>
-              </execution>
-            </executions>
-          </plugin>
-        </plugins>
-      </build>
-    </profile>
-
-    <!--
-      This profile extends the default "apache-release" configuration with automatic checksum-
-      generation for the release source artifact. It is automatically activated during the
-      release build and only needed there.
-    -->
-    <profile>
-      <id>apache-release</id>
-      <build>
-        <plugins>
-          <!--
-            Create MD5 and SHA512 checksum files for the release artifacts.
-          -->
-          <plugin>
-            <groupId>net.nicoulaj.maven.plugins</groupId>
-            <artifactId>checksum-maven-plugin</artifactId>
-            <version>1.11</version>
-            <!-- Only run this in the root module of the project -->
-            <inherited>false</inherited>
-            <executions>
-              <execution>
-                <goals>
-                  <goal>files</goal>
-                </goals>
-              </execution>
-            </executions>
-            <configuration>
-              <algorithms>
-                <algorithm>SHA-512</algorithm>
-              </algorithms>
-              <fileSets>
-                <fileSet>
-                  <directory>${project.build.directory}</directory>
-                  <includes>
-                    <include>apache-plc4x-site-skin-${project.version}-source-release.zip</include>
-                  </includes>
-                </fileSet>
-              </fileSets>
-            </configuration>
-          </plugin>
-        </plugins>
-      </build>
-    </profile>
-  </profiles>
-
-</project>
diff --git a/plc4x-site-skin/src/it/plc4x-website/pom.xml b/plc4x-site-skin/src/it/plc4x-website/pom.xml
deleted file mode 100644
index d13c860..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/pom.xml
+++ /dev/null
@@ -1,306 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
-  Licensed to the Apache Software Foundation (ASF) under one
-  or more contributor license agreements.  See the NOTICE file
-  distributed with this work for additional information
-  regarding copyright ownership.  The ASF licenses this file
-  to you under the Apache License, Version 2.0 (the
-  "License"); you may not use this file except in compliance
-  with the License.  You may obtain a copy of the License at
-
-      https://www.apache.org/licenses/LICENSE-2.0
-
-  Unless required by applicable law or agreed to in writing,
-  software distributed under the License is distributed on an
-  "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-  KIND, either express or implied.  See the License for the
-  specific language governing permissions and limitations
-  under the License.
-  -->
-<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
-
-  <modelVersion>4.0.0</modelVersion>
-
-  <parent>
-    <groupId>org.apache</groupId>
-    <artifactId>apache</artifactId>
-    <version>33</version>
-  </parent>
-
-  <groupId>org.apache.maven.skins.its</groupId>
-  <artifactId>@project.artifactId@</artifactId>
-  <version>1.0-SNAPSHOT</version>
-  <packaging>jar</packaging>
-
-  <name>@project.artifactId@ IT</name>
-  <description>
-    PLC4X is an effort to create a universal library for accessing industrial programmable logic controllers
-    using a variety of protocols using a uniform API.
-  </description>
-  <url>https://plc4x.apache.org</url>
-  <inceptionYear>2017</inceptionYear>
-
-  <scm>
-    <connection>scm:git:https://gitbox.apache.org/repos/asf/plc4x.git</connection>
-    <developerConnection>scm:git:https://gitbox.apache.org/repos/asf/plc4x.git</developerConnection>
-    <url>https://github.com/apache/plc4x</url>
-    <tag>HEAD</tag>
-  </scm>
-
-  <!-- Only configure the site distribution as the rest is handled by the apache parent -->
-  <distributionManagement>
-    <site>
-      <id>apache.website</id>
-      <url>scm:git:https://gitbox.apache.org/repos/asf/plc4x-website.git</url>
-    </site>
-  </distributionManagement>
-
-  <issueManagement>
-    <system>Jira</system>
-    <url>https://issues.apache.org/jira/browse/PLC4X</url>
-  </issueManagement>
-
-  <mailingLists>
-    <mailingList>
-      <name>Apache PLC4X Developer List</name>
-      <subscribe>mailto:dev-subscribe@plc4x.apache.org</subscribe>
-      <unsubscribe>mailto:dev-unsubscribe@plc4x.apache.org</unsubscribe>
-      <post>mailto:dev@plc4x.apache.org</post>
-      <archive>https://mail-archives.apache.org/mod_mbox/plc4x-dev/</archive>
-    </mailingList>
-    <mailingList>
-      <name>PLC4X Commits List</name>
-      <subscribe>mailto:commit-subscribe@plc4x.apache.org</subscribe>
-      <unsubscribe>mailto:commits-unsubscribe@plc4x.apache.org</unsubscribe>
-      <post>mailto:commits@plc4x.apache.org</post>
-      <archive>https://mail-archives.apache.org/mod_mbox/plc4x-commits/</archive>
-    </mailingList>
-    <mailingList>
-      <name>PLC4X Jira Notifications List</name>
-      <subscribe>mailto:issues-subscribe@plc4x.apache.org</subscribe>
-      <unsubscribe>mailto:issues-unsubscribe@plc4x.apache.org</unsubscribe>
-      <post>mailto:issues@plc4x.apache.org</post>
-      <archive>https://mail-archives.apache.org/mod_mbox/plc4x-issues/</archive>
-    </mailingList>
-  </mailingLists>
-
-  <properties>
-    <java.version>11</java.version>
-
-    <skinName>@project.name@</skinName>
-    <skinGroupId>@project.groupId@</skinGroupId>
-    <skinArtifactId>@project.artifactId@</skinArtifactId>
-    <skinVersion>@project.version@</skinVersion>
-
-    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
-    <project.reporting.outputencoding>UTF-8</project.reporting.outputencoding>
-
-    <!-- Site properties -->
-    <!-- Please check out these default skins: https://github.com/darshandsoni/asciidoctor-skins/tree/gh-pages/css -->
-    <asciidoctor-theme>asciidoctor</asciidoctor-theme>
-    <!--asciidoctor-theme>boot-cyborg</asciidoctor-theme-->
-    <asciidoctor.maven.plugin.version>3.0.0</asciidoctor.maven.plugin.version>
-    <asciidoctorj.version>3.0.0</asciidoctorj.version>
-    <asciidoctorj.diagram.version>2.3.1</asciidoctorj.diagram.version>
-    <reflow.skin.version>1.5.0</reflow.skin.version>
-    <bootstrap.version>3.3.7</bootstrap.version>
-    <jquery.version>3.3.1</jquery.version>
-    <anchorjs.version>3.2.2</anchorjs.version>
-    <fontawesome.version>5.2.0</fontawesome.version>
-    <groovy.version>4.0.23</groovy.version>
-    <pcap4j.version>1.8.2</pcap4j.version>
-  </properties>
-
-  <build>
-    <plugins>
-      <!-- Make some additional properties available to simplify keeping some content up to date -->
-      <plugin>
-        <groupId>org.codehaus.gmaven</groupId>
-        <artifactId>groovy-maven-plugin</artifactId>
-        <version>2.1.1</version>
-        <executions>
-          <!-- Do some pre-build checks and report any findings to the user -->
-          <execution>
-            <id>prerequisite-check</id>
-            <phase>validate</phase>
-            <goals>
-              <goal>execute</goal>
-            </goals>
-            <inherited>false</inherited>
-            <configuration>
-              <source>${project.basedir}/src/main/script/prerequisiteCheck.groovy</source>
-            </configuration>
-          </execution>
-          <!--
-            Set some dynamic variables which are useful for the site generation and
-            generate an 'pom.adoc' file containing them in a format asciidoc can use.
-          -->
-          <execution>
-            <id>provide-custom-properties</id>
-            <phase>pre-site</phase>
-            <goals>
-              <goal>execute</goal>
-            </goals>
-            <configuration>
-              <source>${project.basedir}/src/main/script/preSiteGeneration.groovy</source>
-            </configuration>
-          </execution>
-        </executions>
-        <dependencies>
-          <dependency>
-            <groupId>joda-time</groupId>
-            <artifactId>joda-time</artifactId>
-            <version>2.12.7</version>
-          </dependency>
-          <dependency>
-            <groupId>org.apache.groovy</groupId>
-            <artifactId>groovy</artifactId>
-            <version>${groovy.version}</version>
-          </dependency>
-          <dependency>
-            <groupId>org.pcap4j</groupId>
-            <artifactId>pcap4j-core</artifactId>
-            <version>${pcap4j.version}</version>
-          </dependency>
-          <dependency>
-            <groupId>org.pcap4j</groupId>
-            <artifactId>pcap4j-packetfactory-static</artifactId>
-            <version>${pcap4j.version}</version>
-          </dependency>
-        </dependencies>
-      </plugin>
-
-      <plugin>
-        <groupId>org.apache.maven.plugins</groupId>
-        <artifactId>maven-resources-plugin</artifactId>
-        <executions>
-          <execution>
-            <id>copy-site-resources</id>
-            <!-- Only execute this for the parent module -->
-            <inherited>false</inherited>
-            <phase>pre-site</phase>
-            <goals>
-              <goal>copy-resources</goal>
-            </goals>
-            <configuration>
-              <outputDirectory>${project.build.directory}/site</outputDirectory>
-              <resources>
-                <resource>
-                  <directory>${project.basedir}/src/site/resources-filtered</directory>
-                  <filtering>true</filtering>
-                  <targetPath>${project.build.directory}/site</targetPath>
-                </resource>
-              </resources>
-            </configuration>
-          </execution>
-          <!--
-            Copy the schemas that might be distributed throughout the codebase to a central "schemas"
-            directory so IDEs can automatically pull them in.
-          -->
-          <execution>
-            <id>copy-schemas</id>
-            <!-- Only execute this for the parent module -->
-            <inherited>false</inherited>
-            <phase>pre-site</phase>
-            <goals>
-              <goal>copy-resources</goal>
-            </goals>
-            <configuration>
-              <outputDirectory>${project.build.directory}/site</outputDirectory>
-              <resources>
-                <!-- Copy the resources for the test-suites -->
-                <resource>
-                  <directory>${project.basedir}/plc4j/utils/test-utils/src/main/resources/schemas</directory>
-                  <targetPath>${project.build.directory}/site/schemas</targetPath>
-                </resource>
-              </resources>
-            </configuration>
-          </execution>
-        </executions>
-      </plugin>
-    </plugins>
-
-    <pluginManagement>
-      <plugins>
-        <plugin>
-          <groupId>org.codehaus.gmaven</groupId>
-          <artifactId>groovy-maven-plugin</artifactId>
-          <version>2.1.1</version>
-        </plugin>
-
-        <plugin>
-          <groupId>org.apache.maven.plugins</groupId>
-          <artifactId>maven-project-info-reports-plugin</artifactId>
-          <version>3.7.0</version>
-        </plugin>
-
-        <!-- Configure the Site generation -->
-        <plugin>
-          <groupId>org.apache.maven.plugins</groupId>
-          <artifactId>maven-site-plugin</artifactId>
-          <version>3.12.1</version>
-          <configuration>
-            <!--templateFile>${session.executionRootDirectory}/src/site/template/site.vm</templateFile-->
-            <generateReports>true</generateReports>
-            <generateSitemap>true</generateSitemap>
-            <locales>en</locales>
-            <inputEncoding>${project.build.sourceEncoding}</inputEncoding>
-            <outputEncoding>${project.reporting.outputencoding}</outputEncoding>
-            <!--
-              IntelliJ can't find the asciidoc config option in the site plugin, which is correct.
-              However, this config section is used by the asciidoctor site plugin extension. So plead
-              ignore this error, it's actually ok.
-            -->
-            <!--asciidoc>
-              <requires>
-                <require>asciidoctor-diagram</require>
-              </requires>
-              <attributes>
-                <source-highlighter>prettify</source-highlighter>
-                <imagesoutdir>${project.build.directory}/site/images</imagesoutdir>
-                <pom-adoc>${project.build.directory}/pom.adoc</pom-adoc>
-              </attributes>
-            </asciidoc-->
-          </configuration>
-          <dependencies>
-            <!-- All dependencies needed by the reflow skin -->
-            <dependency>
-              <groupId>org.asciidoctor</groupId>
-              <artifactId>asciidoctor-parser-doxia-module</artifactId>
-              <version>${asciidoctor.maven.plugin.version}</version>
-            </dependency>
-          </dependencies>
-        </plugin>
-      </plugins>
-    </pluginManagement>
-  </build>
-
-  <!-- Make Snapshots of Apache projects available -->
-  <repositories>
-    <repository>
-      <id>apache-snapshots</id>
-      <url>https://repository.apache.org/content/repositories/snapshots</url>
-      <releases>
-        <enabled>false</enabled>
-      </releases>
-      <snapshots>
-        <enabled>true</enabled>
-      </snapshots>
-    </repository>
-  </repositories>
-
-  <!-- Make Snapshots of Apache plugins available -->
-  <pluginRepositories>
-    <pluginRepository>
-      <id>apache-snapshots</id>
-      <url>https://repository.apache.org/content/repositories/snapshots</url>
-      <releases>
-        <enabled>false</enabled>
-      </releases>
-      <snapshots>
-        <enabled>true</enabled>
-      </snapshots>
-    </pluginRepository>
-  </pluginRepositories>
-
-</project>
\ No newline at end of file
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/main/script/preSiteGeneration.groovy b/plc4x-site-skin/src/it/plc4x-website/src/main/script/preSiteGeneration.groovy
deleted file mode 100644
index a45757e..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/main/script/preSiteGeneration.groovy
+++ /dev/null
@@ -1,98 +0,0 @@
-/*
- * Licensed to the Apache Software Foundation (ASF) under one
- * or more contributor license agreements.  See the NOTICE file
- * distributed with this work for additional information
- * regarding copyright ownership.  The ASF licenses this file
- * to you under the Apache License, Version 2.0 (the
- * "License"); you may not use this file except in compliance
- * with the License.  You may obtain a copy of the License at
- *
- *   https://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing,
- * software distributed under the License is distributed on an
- * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- * KIND, either express or implied.  See the License for the
- * specific language governing permissions and limitations
- * under the License.
- */
-
-import org.apache.maven.repository.internal.MavenRepositorySystemUtils
-
-print "\nCalculating some additional properties:"
-// Get the current year
-def currentYear = Calendar.getInstance().get(Calendar.YEAR) as String
-print "\nCurrent year:                     " + currentYear
-project.properties['current-year'] = currentYear
-
-// Calculate some version related stuff for the main project
-def currentVersion = project.version as String
-def match = (currentVersion =~ /(\d+)\.(\d+)\.(\d+)(-SNAPSHOT)?/)
-print "\nCurrent version:                  " + currentVersion
-if (match.count >= 1) {
-    def majorVersion = match[0][1] as Integer
-    def minorVersion = match[0][2] as Integer
-    def bugfixVersion = match[0][3] as Integer
-
-    def currentFullVersion = majorVersion + "." + minorVersion + "." + bugfixVersion
-    def currentShortVersion = majorVersion + "." + minorVersion
-    def currentNextIncrementalVersion = majorVersion + "." + minorVersion + "." + (bugfixVersion + 1)
-    def currentNextMinorVersion = majorVersion + "." + (minorVersion + 1) + ".0"
-
-    print "\nCurrent full version:             " + currentFullVersion + " (current-full-version)"
-    project.properties['current-full-version'] = currentFullVersion
-    print "\nCurrent short version:            " + currentShortVersion + "   (current-short-version)"
-    project.properties['current-short-version'] = currentShortVersion
-    print "\nCurrent next incremental version: " + currentNextIncrementalVersion + " (current-next-incremental-version)"
-    project.properties['current-next-incremental-version'] = currentNextIncrementalVersion
-    print "\nCurrent next minor version:       " + currentNextMinorVersion + " (current-next-minor-version)"
-    project.properties['current-next-minor-version'] = currentNextMinorVersion
-}
-
-// Get the version of the code-generation
-codeGenerationVersion = project.properties['plc4x-code-generation.version']
-def codeGenMatch = (codeGenerationVersion =~ /(\d+)\.(\d+)\.(\d+)(-SNAPSHOT)?/)
-if (codeGenMatch.count >= 1) {
-    def codeGenMajorVersion = codeGenMatch[0][1] as Integer
-    def codeGenMinorVersion = codeGenMatch[0][2] as Integer
-    def codeGenBugfixVersion = codeGenMatch[0][3] as Integer
-    // If this is not a snapshot version, increment the minor version
-    if(codeGenMatch[0][4] == null) {
-        codeGenMinorVersion++
-    }
-
-    def codeGenerationReleaseFullVersion = codeGenMajorVersion + "." + codeGenMinorVersion + "." + codeGenBugfixVersion
-    def codeGenerationReleaseShortVersion = codeGenMajorVersion + "." + codeGenMinorVersion
-    def codeGenerationNextDevelopmentVersion = codeGenMajorVersion + "." + (codeGenMinorVersion + 1) + ".0"
-    def codeGenerationBugfixShortVersion = codeGenMajorVersion + "." + codeGenMinorVersion + "." + (codeGenBugfixVersion + 1)
-
-    print "\nNext code-generation full version:             " + codeGenerationReleaseFullVersion + " (code-generation-full-version)"
-    project.properties['code-generation-full-version'] = codeGenerationReleaseFullVersion
-    print "\nNext code-generation short version:             " + codeGenerationReleaseShortVersion + " (code-generation-short-version)"
-    project.properties['code-generation-short-version'] = codeGenerationReleaseShortVersion
-    print "\nNext code-generation development version:             " + codeGenerationNextDevelopmentVersion + " (code-generation-development-version)"
-    project.properties['code-generation-development-version'] = codeGenerationNextDevelopmentVersion
-    print "\nNext code-generation bugfix version:             " + codeGenerationBugfixShortVersion + " (code-generation-bugfix-version)"
-    project.properties['code-generation-bugfix-version'] = codeGenerationBugfixShortVersion
-}
-
-// Get the latest released version from our doap file.
-def plc4xDoapFile = new File(project.getBasedir(), "src/site/resources-filtered/plc4x-doap.rdf")
-if (plc4xDoapFile.exists()) {
-    def doapDocument = new XmlSlurper().parse(plc4xDoapFile)
-    def lastReleasedVersion = doapDocument.Project.release[0].Version.revision
-    print "\nCurrent last released version:    " + lastReleasedVersion + " (current-last-released-version)"
-    project.properties['current-last-released-version'] = lastReleasedVersion
-}
-print "\n"
-
-// Dump all maven properties into a file readable by asciidoc.
-print "\nGenerating 'pom.adoc' file in target directory (Use in adoc by including 'include::{pom-adoc} ... however this should not be required)'\n\n"
-def propertyFile = new File(project.getBasedir(), "target/pom.adoc")
-// Ensure the parent directory is created
-propertyFile.getParentFile().mkdirs()
-// Make sure the file is deleted so we don't append to an existing file
-propertyFile.delete()
-// Iterate over all properties and dump them to the file
-project.properties.each { entry -> propertyFile << ":$entry.key: $entry.value\n" }
-
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/apache/index.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/apache/index.adoc
deleted file mode 100644
index 0f7364c..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/apache/index.adoc
+++ /dev/null
@@ -1,20 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-:imagesdir: ../images/
-:icons: font
-
-== Apache
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/architecture.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/architecture.adoc
deleted file mode 100644
index 0e95ebf..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/architecture.adoc
+++ /dev/null
@@ -1,162 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-
-== Architecture of PLC4X Connections
-
-=== Simple case
-
-In this simple case, an application asks the DriverManager to forward a connection creation to the corresponding Driver implementation, which then creates both a Connection and a MessageCodec instance. The Connection is the logical link between the connection state and the MessageCodec.
-A MessageCodec uses a TransportInstance to communicate with the target device.
-
-[plantuml, target=no-restrictions-simple, format=png]
-....
-
-package Connection1 {
-Plc4xConnection1 : s7:tcp://192.168.23.30
-TcpPort1 : local-ip          192.168.23.200
-TcpPort1 : local-port      48479
-TcpPort1 : remote-ip     192.168.23.30
-TcpPort1 : remote-port 102
-}
-
-package Connection2 {
-Plc4xConnection2 : s7:tcp://192.168.23.30
-TcpPort2 : local-ip          192.168.23.200
-TcpPort2 : local-port      34555
-TcpPort2 : remote-ip     192.168.23.30
-TcpPort2 : remote-port 102
-}
-
-S7Device : local-ip     192.168.23.30
-S7Device : local-port 102
-
-Plc4xConnection1 -> TcpPort1
-Plc4xConnection2 -> TcpPort2
-TcpPort1 -> S7Device : tcp
-TcpPort2 -> S7Device : tcp
-
-....
-
-[plantuml, target=no-restrictions, format=png]
-....
-
-package "Application" {
-  [APP]
-}
-
-package "PLC4X" {
-    [Connection]
-    [ReaderWriter]
-    [MessageCodec]
-    [Transport]
-    [TransportInstance]
-    [Driver]
-}
-
-package "PLC" {
-    [Device]
-}
-
-APP -> Connection : n:1
-Connection - MessageCodec : 1:1
-Connection -- Driver : n:1
-Connection -- ReaderWriter : 1:1
-MessageCodec -- TransportInstance : 1:1
-Transport - TransportInstance : 1:1
-MessageCodec - Driver : n:1
-TransportInstance -> Device : 1:1
-
-note top of [Connection] : logical
-
-....
-
-=== Problems
-
-Serial transports based on RS475 and UDP Transports currently don't allow sharing. That means only one connection instance can have access to one RS485 or one shared local UDP Port (Multiple UDP transport instances with different local ports however are possible). As soon as one connection is established and a second connection would try to access this, this would result in errors.
-
-However, multiple devices could be attached to the same RS458 port (Modbus RTU and Modbus ASCII explicitly supports this, however using different devices using different protocols over the same port is not possible) and in BACnet connecting to multiple remote BACnet devices would require one local UDP port to be used by multiple connections.
-
-=== Protocols requiring us to use a fixed port on a non-broadcast address
-
-Some protocols, such as BACnet require remotes to send data to a fixed udp port on a non-broadcast address. This causes problems as soon as we want to connect to multiple BACnet devices from the same host as only one instance can get access to that port.
-
-[plantuml, target=shared-local-port-simple, format=png]
-....
-
-package Connection1 {
-Plc4xConnection1 : bacnet:udp://192.168.23.30
-UdpPort1 : local-ip          192.168.23.200
-UdpPort1 : local-port      47808
-UdpPort1 : remote-ip     192.168.23.30
-UdpPort1 : remote-port 47808
-}
-
-package Connection2 #red {
-Plc4xConnection2 : bacnet:udp://192.168.23.20
-UdpPort2 : local-ip          192.168.23.200
-UdpPort2 : local-port      47808
-UdpPort2 : remote-ip     192.168.23.20
-UdpPort2 : remote-port 47808
-}
-note right of UdpPort2: This local port is already owned by Connection1
-
-BACnetDevice : local-ip     192.168.23.30
-BACnetDevice : local-port 102
-
-Plc4xConnection1 -> UdpPort1
-Plc4xConnection2 -> UdpPort2
-UdpPort1 -> BACnetDevice : udp
-UdpPort2 -> BACnetDevice : udp
-
-....
-
-[plantuml, target=shared-local-port, format=png]
-....
-
-package "Application" {
-  [APP]
-}
-
-package "PLC4X" {
-    [Connection]
-    [ReaderWriter]
-    [MessageCodec]
-    [Transport]
-    [TransportInstance]
-    [Driver]
-}
-
-package "PLC" {
-    [Device]
-}
-
-APP -> Connection : n:1
-Connection - MessageCodec : n:1
-Connection -- Driver : n:1
-Connection -- ReaderWriter : 1:1
-MessageCodec -- TransportInstance : 1:1
-Transport - TransportInstance : 1:1
-MessageCodec - Driver : n:1
-TransportInstance -> Device : 1:n
-
-note top of [Connection] : logical
-
-....
-
-=== Protocols only allowing one connection at a time
-
-
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/building.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/building.adoc
deleted file mode 100644
index ce5aa78..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/building.adoc
+++ /dev/null
@@ -1,163 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-
-== Building PLC4X
-
-PLC4X is built with `Apache Maven` and we have tried to make the build as simple as possible.
-
-However PLC4X aims at providing means to communicate with PLCs of multiple vendors using a shared API but also in a variety of different languages.
-
-We have partitioned the build to allow selecting the parts that are of interest.
-This is done by selecting so-called `Maven profiles`.
-More about these later down in this manual.
-
-For your convenience we also have provided a `Maven-Wrapper`, that should allow building of PLC4X with only `Java 11` or greater as requirement.
-
-=== Requirements
-
-The only requirements to building PLC4X should be:
-
-* Java 11 JDK (or newer)
-* Git (Even if you are building the source distribution, the Kafka plugin seems to require a `git` executable being available on the systems `PATH`)
-* Apache Maven (3.6.0 or newer) *(Optional)* (See next chapter)
-
-=== Using the Maven-Wrapper
-
-The so-called `Maven-Wrapper` is used by calling the Maven-Wrapper scripts `mvnw` (Mac & Linux) or `mvnw.cmd` (Windows) instead of the default Maven commands `mvn` and `mvn.cmd`.
-
-These helpers ensure Maven is available in at least the version defined in `.mvn/maven-wrapper.properties`.
-If no suitable version can be found, it is automatically downloaded and installed alongside the project (So it doesn't have to be downloaded every time and every project can have it's own Maven version)
-
-After the script has ensured a suitable Maven version is available, this is used and all arguments and parameters are transparently forwarded to this.
-So simply adding the additional `w` to each of the Maven commands, there should be no difference to using a pre-installed Maven version.
-
-=== Using Maven
-
-This document can't provide you with all the details needed to get started with `Maven` itself.
-But there is a lot of good documentation out there.
-
-Justin McLean and Christofer Dutz even recorded a not quite 2-hour Maven training Video some time ago for another Apache project.
-
-It should handle all the details needed to get a general understanding of Maven and how it works.
-
-.Recording of a Maven Training for Apache Flex from 2016
-https://vimeo.com/167857327
-
-=== Building PLC4X with Maven
-
-As especially building the C++, and C# drivers requires building of some third party artifacts and increases build-time dramatically and requires setting up some additional third party tools, we have excluded these parts form the default Maven build.
-
-The following profiles are available:
-
-- `with-c`: Builds all C related modules
-- `with-dotnet`: Builds all C# and .Net related modules
-- `with-go`: Builds all Go related modules
-- `with-java`: Builds all Java related modules
-- `with-python`: Builds all Python related modules
-
-WARNING: As these profiles typically require some preparation and setup on your development machine, please read the link:preparing/index.html[Preparing your Computer] guide for a detailed description on this.
-
-The minimum Apache PLC4X build will build only basic code-generation modules without support for any language:
-
-    mvn install
-
-So if for example you want to build only the Java related modules, the following command will do that:
-
-    mvn -P with-java install
-
-If you want to skip the running of tests (even if this is not encouraged) you can skip them all together.
-
-    mvn -P with-java -DskipTests install
-
-All Apache PLC4X modules are built by executing the following command:
-
-    mvn -P with-c,with-dotnet,with-go,with-java,with-python install
-
-This not only builds the artifacts and creates the jar files, but also runs all unit- and integration-tests.
-
-If you want to skip the running of tests (even if this is not encouraged) you can skip them all together.
-
-    mvn -P with-c,with-dotnet,with-go,with-java,with-python install -DskipTests
-
-This will not skip the compilation of tests, however.
-
-=== Building the PLC4X Website with Maven
-
-The PLC4X Website is also part of the same GIT repository that contains the code and it is built by Maven as well.
-
-In order to build the website the following command should be sufficient:
-
-    mvn site
-
-This is just a quick-start version of the site generation, for a fully detailed documentation please read the https://plc4x.apache.org/developers/infrastructure/website.html[Website] documentation page.
-
-=== Some special Maven profiles
-
-Maven supports so-called `profiles` for customizing the build in special cases.
-We have tried to keep the number of profiles as low as possible.
-So far there is only one profile.
-
-==== `apache-release` profile
-
-This profile is automatically enabled on a release-build and it automatically creates some additional artifacts:
-
-- JavaDoc artifact
-- Sources artifact
-- Source distribution assembly
-- SHA512 checksum files for every artifact
-- PGP signature files for every artifact
-
-Generally it is not required to enable ths profile unless you are interested in these Artifacts.
-
-==== `debug-pom` profile
-
-Especially for Maven beginners, it might be difficult to understand why a module builds the way it does.
-Maven contains a lot of concepts to inherit and override settings.
-
-The `debug-pom` profile will generate the so-called `effective pom` in the modules `target` directory.
-
-This file contains 100% of the settings Maven uses to execute. All settings are inherited and overridden.
-All Properties are expanded to the value Maven uses.
-
-So whenever Maven doesn't behave the way you expect it to, just enable this profile and it should help you find out, what's going on.
-
-==== `enable-all-checks` profile
-
-Some tests of the PLC4X project do require quite a bit of time to run.
-Therefore we decided to disable these for a normal build on developer machines.
-If you want to run them locally and not rely on them being run on the CI servers, enable the `enable-all-checks` profile.
-
-=== Use the compiled library with Gradle
-
-Compiling the library as explained here add the new version in the local Maven repository (i.e. usually under `~/.m2/repository` on linux like systems), if you would like to use Gradle as Build Tool for your project you have just to use a local repository in your Gradle `build.gradle` file.
-
-Here there's an example: 
-
-[source, groovy, subs=attributes+]
-:source-highlighter: prettify
-----
-repositories {
-    mavenCentral()
-    mavenLocal()
-}
-
-dependencies {
-    implementation group: 'org.apache.plc4x', name: 'plc4j-api', version: '{current-last-released-version}'
-    implementation group: 'org.apache.plc4x', name: 'plc4j-driver-s7', version: '{current-last-released-version}'
-    implementation group: 'org.apache.plc4x', name: 'plc4j-connection-pool', version: '{current-last-released-version}'
-}
-----
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/code-gen/index.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/code-gen/index.adoc
deleted file mode 100644
index 83019d2..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/code-gen/index.adoc
+++ /dev/null
@@ -1,443 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-:imagesdir: ../../images/
-
-== Code Generation
-
-As hand-writing code for a lot of drivers in multiple languages would be quite a nightmare, we have invested a very large amount of time into finding a way to automate this.
-
-So in the end we need 3 parts:
-
-1. Protocol definition
-2. Language template
-3. A maven plugin which generates the code
-
-This maven plugin uses a given protocol definition as well as a language template and generates code for reading/writing data in that protocol with the given language.
-
-[ditaa,code-generation-intro]
-....
-                  +------------+
-                  |c05A        |
-                  |  Language  |
-       +--------->|    Base    |------------+
-       |          |            |            |
-       |          +------------+            v
-+------------+                       +------------+      +------------+
-|c05A        |                       |c05A        |      |            |
-|   Types    |                       |   PLC4X    |      |            |
-|    Base    |                       |   Maven    |----->|    Code    |
-|            |                       |   Plugin   |      |            |
-+------------+                       +------------+      +------------+
-       |          +------------+            ^
-       |          |c05A        |            |
-       |          |  Protocol  |            |
-       +--------->|    Base    |------------+
-                  |            |
-                  +------------+
-....
-
-The `Types Base` module provides all the structures the `Protocol` modules output which are then used in the `Language` templates to generate code.
-
-`Protocol Base` and `Language Base` hereby just provide the interfaces that reference these types and provide the API for the `plc4x-maven-plugin` to use.
-
-These modules are also maintained in a link:https://github.com/apache/plc4x-build-tools/tree/develop/code-generation[repository] which is separate from the rest of the PLC4X code.
-
-This is generally only due to some restrictions in the Maven build system. If you are interested in understanding the reasons - please read the chapter on `Problems with Maven` near the end of this page.
-
-Concrete link:https://github.com/apache/plc4x/tree/develop/code-generation/protocol-base-mspec[protocol spec parsers], link:https://github.com/apache/plc4x/tree/develop/code-generation/language-base-freemarker[code generators] as well as link:https://github.com/apache/plc4x/tree/develop/code-generation/language-java[templates] that actually generate code are implemented in derived modules all located under the link:https://github.com/apache/plc4x/tree/develop/code-generation[code-generat [...]
-
-We didn't want to tie ourselves to only one way to specify protocols and to generate code. Generally multiple types of formats for specifying drivers are thinkable and the same way, multiple ways of generating code are possible. Currently, however we only have one parser: `MSpec` and one generator: `Freemarker`.
-
-These add more layers to the hierarchy.
-
-So for example in case of generating a `Siemens S7` Driver for `Java` this would look like this:
-
-[ditaa,code-generation-intro-s7-java]
-....
-               +------------+
-               |c05A        |
-               |   Types    |
-       +-------|    Base    |--------+
-       |       |            |        |
-       |       +------------+        |
-       v                             v
-+------------+                +------------+
-|c05A        |                |c05A        |
-|  Protocol  |                |  Language  |
-|    Base    |                |    Base    |
-|            |                |            |
-+------------+                +------------+
-       |                             |
-       |                             |
-       v                             v
-+------------+                +------------+
-|c0BA        |                |c0BA        |
-|  Protocol  |                |  Language  |
-|    Base    |                |    Base    |
-|   MSpec    |                | Freemarker |
-+------------+                +------------+
-       |                             |
-       |                             |
-       v                             v
-+------------+                +------------+
-|c0BA        |                |c0BA        |
-|     S7     |                |    Java    |
-|  Protocol  |                |  Language  |
-|            |                |            |
-+------------+                +------------+
-       |                             |
-       |                             |
-       |       +------------+        |
-       |       |c05A        |        |
-       |       |   PLC4X    |        |
-       +------>|   Maven    |<-------+
-               |   Plugin   |
-               +------------+
-                      |
-                      |
-                      v
-               +------------+
-               |c0BA        |
-               |     S7     |
-               |    Java    |
-               |    Code    |
-               +------------+
-....
-
-The dark blue parts are the ones released externally, the turquoise ones are part of the main PLC4X repo.
-
-=== Introduction
-
-The maven plugin is built up very modular.
-
-So in general it is possible to add new forms of providing protocol definitions as well as language templates.
-
-For the formats of specifying a protocol we have tried out numerous tools and frameworks, however the results were never quite satisfying.
-
-Usually using them required a large amount of workarounds, which made the solution quite complicated.
-This is mainly the result, that tools like Thrift, Avro, GRPc, ... all are made for transferring an object structure from A to B. They lay focus on keeping the structure of the object in takt and not offer ways to control the format for transferring them.
-
-Existing industry standards, such as `ASN.1` unfortunately mostly relied on large portions of text to describe part of the parsing or serializing logic, which made it pretty much useless for a fully automated code genration.
-
-In the end only `DFDL` and the corresponding Apache project link:https://daffodil.apache.org[Apache Daffodil] seemed to provide what we were looking for.
-
-With this we were able to provide first driver versions fully specified in XML.
-
-The downside was, that the PLC4X community regarded this XML format as pretty complicated and when implementing an experimental code generator we quickly noticed that generating a nice object model would not be possible, due to the lack of an ability to model inheritance of types into a DFDL schema.
-
-In the end we came up with our own format which we called `MSpec` and is described in the link:protocol/mspec.html[MSpec Format description].
-
-=== Configuration
-
-The `plc4x-maven-plugin` has a very limited set of configuration options.
-
-In general all you need to specify, is the `protocolName` and the `languageName`.
-
-An additional option `outputFlavor` allows generating multiple versions of a driver for a given language.
-This can come in handy if we want to be able to generate `read-only` or `passive mode` driver variants.
-
-In order to be able to refactor and improve protocol specifications without having to update all drivers for a given protocol, we recently added a `protocolVersion` attribute, that allows us to provide and use multiple versions of one protocol.
-So in case of us updating the fictional `wombat-protocol`, we could add a `version 2` `mspec` for that, then use the version 2 in the java-driver and continue to use version 1 in all other languages.
-Once all drivers are updated we could eliminate the version again.
-
-Last, not least, we have a pretty generic `options` config option, which is a Map type.
-
-With options is it possible to pass generic options to the code-generation.
-So if a driver or language requires further customization, these options can be used.
-For a list of all supported options for a given language template, please refer to the corresponding language page.
-
-Currently, the `Java` module makes use of such an option for specifying the Java `package` the generated code uses.
-If no `package` option is provided, the default package `org.apache.plc4x.{language-name}.{protocol-name}.{output-flavor}` is used, but especially when generating custom drivers, which are not part of the Apache PLC4X project, different package names are better suited.
-So in these cases, the user can simply override the default package name.
-
-There is also an additional parameter: `outputDir`, which defaults to `${project.build.directory}/generated-sources/plc4x/` and usually shouldn't require being changed in case of a `Java` project, but usually requires tweaking when generating code for other languages.
-
-Here's an example of a driver pom for building a `S7` driver for `java`:
-
-[subs=attributes+]
-....
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
-  Licensed to the Apache Software Foundation (ASF) under one
-  or more contributor license agreements.  See the NOTICE file
-  distributed with this work for additional information
-  regarding copyright ownership.  The ASF licenses this file
-  to you under the Apache License, Version 2.0 (the
-  "License"); you may not use this file except in compliance
-  with the License.  You may obtain a copy of the License at
-
-      https://www.apache.org/licenses/LICENSE-2.0
-
-  Unless required by applicable law or agreed to in writing,
-  software distributed under the License is distributed on an
-  "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-  KIND, either express or implied.  See the License for the
-  specific language governing permissions and limitations
-  under the License.
-  -->
-<project xmlns="http://maven.apache.org/POM/4.0.0"
-    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-    xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
-  <modelVersion>4.0.0</modelVersion>
-
-  <parent>
-    <groupId>org.apache.plc4x.plugins</groupId>
-    <artifactId>plc4x-code-generation</artifactId>
-    <version>{current-last-released-version}</version>
-  </parent>
-
-  <artifactId>test-java-s7-driver</artifactId>
-
-  <build>
-    <plugins>
-      <plugin>
-        <groupId>org.apache.plc4x.plugins</groupId>
-        <artifactId>plc4x-maven-plugin</artifactId>
-        <executions>
-          <execution>
-            <id>test</id>
-            <phase>generate-sources</phase>
-            <goals>
-              <goal>generate-driver</goal>
-            </goals>
-            <configuration>
-              <protocolName>s7</protocolName>
-              <languageName>java</languageName>
-              <outputFlavor>read-write</outputFlavor>
-            </configuration>
-          </execution>
-        </executions>
-      </plugin>
-    </plugins>
-  </build>
-
-  <dependencies>
-    <dependency>
-      <groupId>org.apache.plc4x.plugins</groupId>
-      <artifactId>plc4x-code-generation-driver-base-java</artifactId>
-      <version>{current-last-released-version}</version>
-    </dependency>
-
-    <dependency>
-      <groupId>org.apache.plc4x.plugins</groupId>
-      <artifactId>plc4x-code-generation-language-java</artifactId>
-      <version>{current-last-released-version}</version>
-      <!-- Scope is 'provided' as this way it's not shipped with the driver -->
-      <scope>provided</scope>
-    </dependency>
-
-    <dependency>
-      <groupId>org.apache.plc4x.plugins</groupId>
-      <artifactId>plc4x-code-generation-protocol-s7</artifactId>
-      <version>{current-last-released-version}</version>
-      <!-- Scope is 'provided' as this way it's not shipped with the driver -->
-      <scope>provided</scope>
-    </dependency>
-  </dependencies>
-
-</project>
-....
-
-So the plugin configuration is pretty straight forward, all that is specified, is the `protocolName`, `languageName` and the `output-flavor`.
-
-The dependency:
-
-[subs=attributes+]
-....
-    <dependency>
-      <groupId>org.apache.plc4x.plugins</groupId>
-      <artifactId>plc4x-code-generation-driver-base-java</artifactId>
-      <version>{current-last-released-version}</version>
-    </dependency>
-....
-
-For example contains all classes the generated code relies on.
-
-The definitions of both the `s7` protocol and `java` language are provided by the two dependencies:
-
-[subs=attributes+]
-....
-    <dependency>
-      <groupId>org.apache.plc4x.plugins</groupId>
-      <artifactId>plc4x-code-generation-language-java</artifactId>
-      <version>{current-last-released-version}</version>
-      <!-- Scope is 'provided' as this way it's not shipped with the driver -->
-      <scope>provided</scope>
-    </dependency>
-....
-
-and:
-
-[subs=attributes+]
-....
-    <dependency>
-      <groupId>org.apache.plc4x.plugins</groupId>
-      <artifactId>plc4x-code-generation-protocol-s7</artifactId>
-      <version>{current-last-released-version}</version>
-      <!-- Scope is 'provided' as this way it's not shipped with the driver -->
-      <scope>provided</scope>
-    </dependency>
-....
-
-The reason for why the dependencies are added as code-dependencies and why the scope is set the way it is, is described in the <<Why are the protocol and language dependencies done so strangely?>> section.
-
-=== Custom Modules
-
-The plugin uses the https://docs.oracle.com/javase/7/docs/api/java/util/ServiceLoader.html[Java Serviceloader] mechanism to find modules.
-
-==== Protocol Modules
-
-In order to provide a new protocol module, all that is required, it so create a module containing a `META-INF/services/org.apache.plc4x.plugins.codegenerator.protocol.Protocol` file referencing an implementation of the `org.apache.plc4x.plugins.codegenerator.protocol.Protocol` interface.
-
-This interface is located in the `org.apache.plc4x.plugins:plc4x-code-generation-protocol-base` module and generally only defines three methods:
-
-....
-package org.apache.plc4x.plugins.codegenerator.protocol;
-
-import org.apache.plc4x.plugins.codegenerator.types.exceptions.GenerationException;
-
-import java.util.Optional;
-
-public interface Protocol {
-
-    /**
-     * The name of the protocol what the plugin will use to select the correct protocol module.
-     *
-     * @return the name of the protocol.
-     */
-    String getName();
-
-    /**
-     * Returns a map of type definitions for which code has to be generated.
-     *
-     * @return the Map of types that need to be generated.
-     * @throws GenerationException if anything goes wrong parsing.
-     */
-    TypeContext getTypeContext() throws GenerationException;
-
-
-    /**
-     * @return the protocolVersion is applicable
-     */
-    default Optional<String> getVersion() {
-        return Optional.empty();
-    }
-
-}
-....
-
-The `name` is being used for the module to find the right language module, so the result of `getName()` needs to match the value provided in the maven config-option `protocolName`.
-
-As mentioned before, we support multiple versions of a protocol, so if `getVersions()` returns a non-empty version, this is used to select the version.
-
-The most important method for the actual code-generation however is the `getTypeContext()` method, which returns a `TypeContext` type which generally contains a list of all parsed types for this given protocol.
-
-==== Language Modules
-
-Analog to the <<Protocol Modules>> the Language modules are constructed very similar.
-
-The `LanguageOutput` interface is very simplistic too and is located in the `org.apache.plc4x.plugins:plc4x-code-generation-language-base` module and generally only defines four methods:
-
-....
-package org.apache.plc4x.plugins.codegenerator.language;
-
-import org.apache.plc4x.plugins.codegenerator.types.definitions.ComplexTypeDefinition;
-import org.apache.plc4x.plugins.codegenerator.types.exceptions.GenerationException;
-
-import java.io.File;
-import java.util.Map;
-
-public interface LanguageOutput {
-
-    /**
-     * The name of the template is what the plugin will use to select the correct language module.
-     *
-     * @return the name of the template.
-     */
-    String getName();
-
-    List<String> supportedOutputFlavors();
-
-    /**
-     * An additional method which allows generator to have a hint which options are supported by it.
-     * This method might be used to improve user experience and warn, if set options are ones generator does not support.
-     *
-     * @return Set containing names of options this language output can accept.
-     */
-    Set<String> supportedOptions();
-
-    void generate(File outputDir, String version, String languageName, String protocolName, String outputFlavor,
-        Map<String, TypeDefinition> types, Map<String, String> options) throws GenerationException;
-
-}
-....
-
-The file for registering Language modules is located at: `META-INF/services/org.apache.plc4x.plugins.codegenerator.language.LanguageOutput`
-
-The `name` being used by the plugin to find the language output module defined by the maven config option `languageName`.
-
-`supportedOutputFlavors` provides a possible list of flavors, that can be referred to by the maven config option `outputFlavor`.
-
-`supportedOptions` provides a list of `options` that the current language module is able to use and which can be passed in to the maven configuration using the `options` settings.
-
-=== Problems with Maven
-
-==== Why are the 4 modules released separately?
-
-We mentioned in the introduction, that the first 4 modules are maintained and released from outside the main PLC4X repository.
-
-This is due to some restrictions in Maven, which result from the way Maven generally works.
-
-The main problem is that when starting a build, in the `validate`-phase, Maven goes through the configuration, downloads the plugins and configures these.
-This means that Maven also tries to download the dependencies of the plugins too.
-
-In case of using a Maven plugin in a project which also builds the maven plugin itself, this is guaranteed to fail - Especially during releases.
-While during normal development, Maven will probably just download the latest `SNAPSHOT` from our Maven repository and will be happy with this and not complain even if this version will be overwritten later on in the build.
-It will just use the new version as soon as it has to.
-
-During releases however the release plugin changes the version to a release version and then spawns a build.
-In this case the build will fail because there is no Plugin with that version to download from anywhere.
-In this case the only option would be to manually build and deploy the plugin in the release version and to re-start the release (Which is not a nice thing for the release manager).
-
-For this reason we have stripped down the plugin and its dependencies to an absolute minimum and have released that separately from the rest, hoping due to the minimality of the dependencies that we will not have to do it very often.
-
-As soon as the tooling is released, the version is updated in the PLC4X build and the release version is used without any complications.
-
-==== Why are the protocol and language dependencies done so strangely?
-
-It would certainly be a lot cleaner, if we provided the dependencies to protocol and language modules as plugin dependencies.
-
-However, as we mentioned in the previous subchapter, Maven tries to download and configure the plugins prior to running the build.
-So during a release the new versions of the modules wouldn't exist, this would cause the build to fail.
-
-We could release the protocol- and the language modules separately too, but we want the language and protocol modules to be part of the project, to not over-complicate things - especially during a release.
-
-In order to keep the build and the release as simple as possible, we built the Maven plugin in a way, that it uses the modules dependencies and creates its own Classloader to contain all of these modules at runtime.
-
-This brings the benefit of being able to utilize Maven's capability of determining the build order and dynamically creating the modules build classpath.
-
-Adding a normal dependency however would make Maven deploy the artifacts with the rest of the modules.
-
-We don't want that as both the protocol as well as the language-modules are useless as soon as they have been used to generate the code.
-
-So we use a trick that is usually used in Web applications, for example:
-Here the vendor of a Servlet engine is expected to provide an implementation of the `Servlet API`.
-It is forbidden for an application to bring this along, but it is required to build the application.
-
-For this the Maven scope `provided`, which tells Maven to provide it during the build, but to exclude it from any applications it builds, because it will be provided by the system running the application.
-
-This is not quite true, but it does the trick.
\ No newline at end of file
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/code-gen/language/freemarker.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/code-gen/language/freemarker.adoc
deleted file mode 100644
index 5c53337..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/code-gen/language/freemarker.adoc
+++ /dev/null
@@ -1,193 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-:imagesdir: ../../../images/
-
-== Apache Freemarker
-
-For the Freemarker language output we are using an unmodified version of https://freemarker.apache.org[Apache Freemarker] to generate output.
-
-The boilerplate code for providing a PLC4X language module is located in the `org.apache.plc4x.plugins:plc4x-code-generation-language-base-freemarker` maven module, inside the `FreemarkerLanguageOutput` class.
-
-This class configures a Freemarker context and provides standardized attributes inside this:
-
-- packageName: Java style package name which can be used to create some form of directory structure.
-- typeName: Simple string type name
-- type: `ComplexTypeDefinition` instance containing all the information for the type that code should be generated for.
-- helper: As some times it is pretty complicated to create all the output in Freemarker, the helper allows to provide code that is used by the template that help with generating output.
-
-A Freemarker-based output module, has to provide a set of `Template` instances as well as provide a `FreemarkerLanguageTemplateHelper` instance.
-
-In general, we distinguish between these types of templates:
-
-- `Spec Templates` (Global output generated once per driver in total)
-- `Complex Type Templates` (Generates output for a complex type)
-- `Enum Templates` (Generates output for enum types)
-- `DataIO Templates` (Generates output for reading and writing PlcValues, which are our PLC4X form of presenting input and output data to our users)
-
-For each of these, the developer can provide a list of templates, which then can generate multiple files per type (Which is important for languages such as `C` where for every type we need to generate a `Header file (.h)` and an `Implementation (.c)`)
-
-What the `FreemarkerLanguageOutput` then does, is iterate over all types provided by the protocol module, and then iterate over all templates the current language defines.
-
-The only convention used in this utility, is that the first line of output a template generates will be treated as the path relative to the base output directory.
-
-It will automatically create all needed intermediate directories and generate the rest of the input to the file specified by the first line.
-
-If this line is empty, the output is skipped for this type.
-
-=== Example `Java` output
-
-....
-package org.apache.plc4x.language.java;
-
-import com.google.googlejavaformat.java.Formatter;
-import com.google.googlejavaformat.java.FormatterException;
-import freemarker.template.Configuration;
-import freemarker.template.Template;
-import org.apache.commons.io.FileUtils;
-import org.apache.plc4x.plugins.codegenerator.protocol.freemarker.FreemarkerLanguageOutput;
-import org.apache.plc4x.plugins.codegenerator.protocol.freemarker.FreemarkerLanguageTemplateHelper;
-import org.apache.plc4x.plugins.codegenerator.types.definitions.TypeDefinition;
-import org.slf4j.Logger;
-import org.slf4j.LoggerFactory;
-
-import java.io.File;
-import java.io.IOException;
-import java.nio.charset.StandardCharsets;
-import java.util.*;
-
-public class JavaLanguageOutput extends FreemarkerLanguageOutput {
-
-    private static final Logger LOGGER = LoggerFactory.getLogger(JavaLanguageOutput.class);
-
-    private final Formatter formatter = new Formatter();
-
-    @Override
-    public String getName() {
-        return "Java";
-    }
-
-    @Override
-    public Set<String> supportedOptions() {
-        return Collections.singleton("package");
-    }
-
-    @Override
-    public List<String> supportedOutputFlavors() {
-        return Arrays.asList("read-write", "read-only", "passive");
-    }
-
-    @Override
-    protected List<Template> getSpecTemplates(Configuration freemarkerConfiguration) {
-        return Collections.emptyList();
-    }
-
-    @Override
-    protected List<Template> getComplexTypeTemplates(Configuration freemarkerConfiguration) throws IOException {
-        return Arrays.asList(
-            freemarkerConfiguration.getTemplate("templates/java/pojo-template.java.ftlh"),
-            freemarkerConfiguration.getTemplate("templates/java/io-template.java.ftlh"));
-    }
-
-    @Override
-    protected List<Template> getEnumTypeTemplates(Configuration freemarkerConfiguration) throws IOException {
-        return Collections.singletonList(
-            freemarkerConfiguration.getTemplate("templates/java/enum-template.java.ftlh"));
-    }
-
-    @Override
-    protected List<Template> getDataIoTemplates(Configuration freemarkerConfiguration) throws IOException {
-        return Collections.singletonList(
-            freemarkerConfiguration.getTemplate("templates/java/data-io-template.java.ftlh"));
-    }
-
-    @Override
-    protected FreemarkerLanguageTemplateHelper getHelper(TypeDefinition thisType, String protocolName, String flavorName, Map<String, TypeDefinition> types,
-                                                         Map<String, String> options) {
-        return new JavaLanguageTemplateHelper(thisType, protocolName, flavorName, types, options);
-    }
-
-    @Override
-    protected void postProcessTemplateOutput(File outputFile) {
-        try {
-            FileUtils.writeStringToFile(
-                outputFile,
-                formatter.formatSourceAndFixImports(
-                    FileUtils.readFileToString(outputFile, StandardCharsets.UTF_8)
-                ),
-                StandardCharsets.UTF_8
-            );
-        } catch (IOException | FormatterException e) {
-            LOGGER.error("Error formatting {}", outputFile, e);
-        }
-    }
-}
-....
-
-The `getName` method returns `Java`, this is what needs to be defined in the `plc4x-maven-plugin` configuration in the `language` option in order to select this output format.
-
-`supportedOptions` tells the plugin which `option` tags this code-generation output supports. In case of the `Java` output, this is only the `package` option, which defines the package name of the generated output.
-
-With `supportedOutputFlavors` we tell the user, that in general we support the three options: `read-write`, `read-only` and `passive` as valid inputs for the `outputFlavor` config option of the code-generation plugin.
-
-In this case Java doesn't require any global files being generated for java, so we simply return an empty collection.
-
-For complex types, we currently use two templates (however this will soon be reduced to one). So for every complex type in a protocol definition, the templates: `templates/java/pojo-template.java.ftlh` and `templates/java/io-template.java.ftlh` will be executed.
-
-In case of enum types, only one template is being used.
-
-Same as for data-io.
-
-The next important method is the `getHelper` method, which returns an object, that is passed to the templates with the name `helper`. As mentioned before, a lot of operations would be too complex to implement in pure Freemarker code, so with these helpers every language can provide a helper utility for handling the complex operations.
-
-Here an example for a part of a template for generating Java POJOs:
-
-....
-${helper.packageName(protocolName, languageName, outputFlavor)?replace(".", "/")}/${type.name}.java
-/*
- * Licensed to the Apache Software Foundation (ASF) under one
- * or more contributor license agreements.  See the NOTICE file
- * distributed with this work for additional information
- * regarding copyright ownership.  The ASF licenses this file
- * to you under the Apache License, Version 2.0 (the
- * "License"); you may not use this file except in compliance
- * with the License.  You may obtain a copy of the License at
- *
- *   https://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing,
- * software distributed under the License is distributed on an
- * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- * KIND, either express or implied.  See the License for the
- * specific language governing permissions and limitations
- * under the License.
- */
-package ${helper.packageName(protocolName, languageName, outputFlavor)};
-
-... imports ...
-
-// Code generated by code-generation. DO NOT EDIT.
-
-public<#if type.isDiscriminatedParentTypeDefinition()> abstract</#if> class ${type.name}<#if type.parentType??> extends ${type.parentType.name}</#if> implements Message {
-
-    ... SNIP ...
-
-}
-....
-
-So as you can see, the first line will generate the file-path of the to be generated output.
-
-As when creating more and more outputs for different languages, we have realized, that a lot of the code needed in the `Helper` utility repeats, we therefore introduced a so-called `BaseFreemarkerLanguageTemplateHelper` which contains a lot of stuff, that is important when generating new language output.
\ No newline at end of file
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/code-gen/protocol/df1.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/code-gen/protocol/df1.adoc
deleted file mode 100644
index ca52ae1..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/code-gen/protocol/df1.adoc
+++ /dev/null
@@ -1,94 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-
-== Example: DF1 MSpec
-
-The DF1 protocol has three basic messages: a command message, acknowledge and not acknowledge.
-A `0x10` is used as delimiter to differentiate between the messages and parts of the command message.
-
-[width="25%",cols="^,^"]
-|============
-|ACK | NAK
-
-|10 06 |10 15
-|============
-
-
-This is what a read command message looks like in full-duplex mode using CRC as checksum:
-[cols="^,^,^,^,^,^,^,^,^,^,^,^,^"]
-|===
-|Name | DLE | STX | DST | SRC | CMD | STS | TNS | ADDR | SIZE | DLE | ETX | CRC
-
-|Value | 10 | 02 | XX | XX | 01 | 00 | XX XX | XX XX | 02 | 10 | 03 | XX XX
-|===
-
-The according response with the requested byte data:
-[cols="^,^,^,^,^,^,^,^,^,^,^,^,^"]
-|===
-|Name | DLE | STX | DST | SRC | CMD | STS | TNS | DATA | SIZE | DLE | ETX | CRC
-
-|Value | 10 | 02 | XX | XX | 41 | 00 | XX XX | XX XX | 02 | 10 | 03 | XX XX
-|===
-
-Every message starts with a `DLE = 0x10`. The second byte is used to differentiate what type of message will follow.
-In the case of a command message it is `0x02`. DST and SRC specify the target and source of the message.
-`CMD = 0x01` means an unprotected read is requested, the command response code is always attained with the addition of `0x40`. STS is a status byte,
-TNS is the transaction counter that is incremented by the master and used to recognize the specific message response.
-ADDR is the memory address being requested, size specifies how many bytes are to be read.
-DLE + ETX mark the end of the message, the last two bytes are the CRC that is calculated using the previously sent bytes.
-
-Here is the MSpec to model the behaviour:
-
-....
-[discriminatedType DF1Symbol
-    [const            uint 8       messageStart 0x10]
-    [discriminator    uint 8       symbolType]
-    [typeSwitch 'symbolType'
-        ['0x02' DF1SymbolMessageFrame
-            [simple   uint 8       destinationAddress]
-            [simple   uint 8       sourceAddress]
-            [simple   DF1Command   command]
-            [const    uint 8       messageEnd 0x10]
-            [const    uint 8       endTransaction 0x03]
-            [checksum uint 16      'crc' 'STATIC_CALL("org.apache.plc4x.java.df1.readwrite.utils.StaticHelper.crcCheck", destinationAddress, sourceAddress, command)']
-        ]
-        ['0x06' DF1SymbolMessageFrameACK
-        ]
-        ['0x15' DF1SymbolMessageFrameNAK
-        ]
-    ]
-]
-
-[discriminatedType DF1Command
-    [discriminator uint 8  commandCode]
-    [simple    uint 8       status]
-    [simple    uint 16      transactionCounter]
-    [typeSwitch 'commandCode'
-        ['0x01' DF1UnprotectedReadRequest
-            [simple uint 16    address]
-            [simple uint 8     size]
-        ]
-        ['0x41' DF1UnprotectedReadResponse
-            [manualArray  uint 8 'data' terminated 'STATIC_CALL("org.apache.plc4x.java.df1.readwrite.utils.StaticHelper.dataTerminate", io)' 'STATIC_CALL("org.apache.plc4x.java.df1.readwrite.utils.StaticHelper.readData", io)' 'STATIC_CALL("org.apache.plc4x.java.df1.readwrite.utils.StaticHelper.writeData", io, element)' 'STATIC_CALL("org.apache.plc4x.java.df1.readwrite.utils.StaticHelper.dataLength", data)']
-        ]
-    ]
-]
-....
-
-The basic object is the DF1Symbol, where the second byte is used to distinguish between the different message types using a typeSwitch.
-In the case of a command message, the message frame contains the DF1Command to further differentiate between the command types.
-Currently only the unprotected read and its response are implemented.
\ No newline at end of file
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/code-gen/protocol/mspec.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/code-gen/protocol/mspec.adoc
deleted file mode 100644
index 8d19b56..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/code-gen/protocol/mspec.adoc
+++ /dev/null
@@ -1,485 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-:imagesdir: ../../../images/
-
-== The MSpec format
-
-The `MSpec` format (Message Specification) was a result of a brainstorming session after evaluating a lot of other options.
-
-We simply sat down and started to write some imaginary format (imaginary was even the initial Name we used Machine-Readable SPEC = `mspec`).
-After we had an initial format that seemed to do the trick, we then stated creating parses for this and started iteratively fine-tuning both spec and parsers as part of the process of implementing new protocols and language templates.
-
-It's a text-based format.
-
-At the root level of these specs are a set of `type`, `discriminatedType`, `dataIo` and `enum` blocks.
-
-`type` elements are objects who`s content and structure is independent of the input.
-
-An example would be the `TPKTPacket` of the `S7` format:
-
-....
-[type TPKTPacket
-    [const    uint 8                 protocolId 0x03]
-    [reserved uint 8                 '0x00']
-    [implicit uint 16                len       'payload.lengthInBytes + 4']
-    [simple   COTPPacket('len - 4') payload]
-]
-....
-
-A `discriminatedType` type, in contrast, is an object who`s content and structure is influenced by the input.
-
-Every discriminated type can contain an arbitrary number of normal fields but must contain exactly one `typeSwitch` element.
-
-For example part of the spec for the S7 format looks like this:
-
-....
-[discriminatedType S7Message
-    [const         uint 8  protocolId      0x32]
-    [discriminator uint 8  messageType]
-    [reserved      uint 16 '0x0000']
-    [simple        uint 16 tpduReference]
-    [implicit      uint 16 parameterLength 'parameter != null ? parameter.lengthInBytes : 0']
-    [implicit      uint 16 payloadLength   'payload != null ? payload.lengthInBytes : 0']
-    [typeSwitch messageType
-        ['0x01' S7MessageRequest
-        ]
-        ['0x02' S7MessageResponse
-            [simple uint 8 errorClass]
-            [simple uint 8 errorCode]
-        ]
-        ['0x03' S7MessageResponseData
-            [simple uint 8 errorClass]
-            [simple uint 8 errorCode]
-        ]
-        ['0x07' S7MessageUserData
-        ]
-    ]
-    [optional S7Parameter ('messageType')              parameter 'parameterLength > 0']
-    [optional S7Payload   ('messageType', 'parameter') payload   'payloadLength > 0'  ]
-]
-....
-
-A type`s start is declared by an opening square bracket `[` followed by the `type` or `discriminatedType` keyword, which is directly followed by a name.
-A Type definition is ended with a closing square bracket `]`.
-
-Every type definition contains a list of so-called fields.
-
-The list of available field types are:
-
-- abstract: used in the parent type declaration do declare a field that has to be defined with the identical type in all subtypes (reserved for `discriminatedType`).
-- array: array of simple or complex typed objects.
-- assert: generally similar to `constant` fields, however do they throw `AssertionExceptions` instead of hard `ParseExceptions`. They are used in combination with optional fields.
-- checksum: used for calculating and verifying checksum values.
-- const: expects a given value and causes a hard exception if the value doesn't match.
-- discriminator: special type of simple typed field which is used to determine the concrete type of object (reserved for `discriminatedType`).
-- enum: special form of field, used if an enum types property is to be used instead of it's primary value.
-- implicit: a field required for parsing, but is usually defined though other data, so it's not stored in the object, but calculated on serialization.
-- manualArray: like an array field, however the logic for serializing, parsing, number of elements and size have to be provided manually.
-- manual: simple field, where the logic for parsing, serializing and size have to be provided manually.
-- optional: simple or complex typed object, that is only present if an optional condition expression evaluates to `true` and no `AssertionException` is thrown when parsing the referenced type.
-- padding: field used to add padding data to make datastructures aligned.
-- peek: field that tries to parse a given structure without actually consuming the bytes.
-- reserved: expects a given value, but only warns if condition is not meet.
-- simple: simple or complex typed object.
-- typeSwitch: not a real field, but indicates the existence of subtypes, which are declared inline (reserved for `discriminatedType`).
-- unknown: field used to declare parts of a message that still has to be defined. Generally used when reverse-engineering a protocol. Messages with `unknown` fields can only be parsed and not serialized.
-- validation: this field is not actually a real field, it's more a condition that is checked during parsing and if the check fails, it throws a validation exception, wich is handled by
-- virtual: generates a field in the message, that is generally only used for simplification. It's not used for parsing or serializing.
-
-The full syntax and explanations of these type follow in the following chapters.
-
-Another thing we have to explain are how types are specified.
-
-In general, we distinguish between two types of types used in field definitions:
-
-- simple types
-- complex types
-
-=== Simple Types
-
-Simple types are usually raw data the format is:
-
-    {base-type} {size}
-
-The base types available are currently:
-
-- *bit*: Simple boolean value or bit.
-- *byte*: Special value fixed to 8 bit, which defaults to either signed or unsigned depending on the programming language (Java it defaults to signed integer values and in C and Go it defaults to unsigned integers).
-- *int*: The input is treated as signed integer value.
-- *uint*: The input is treated as unsigned integer value.
-- *float*: The input is treated as floating point number.
-- *string*: The input is treated as string.
-
-Then for `dataIo` types we have some additional types:
-- *time*: The input is treated as a time representation
-- *date*: The input is treated as a date representation
-- *dateTime*: The input is treated as a date with time
-
-All except the `bit` and `byte` types take a `size` value which provides how many `bits` should be read.
-For the `bit` field, this obviously defaults to 1 and for the `byte` the bits default to 8.
-
-So reading an unsigned 8-bit integer would be: `uint 8`.
-
-There is currently one special type, reserved for string values, whose length is determined by an expression instead of a fixed number of bits. It is considered a variable length string:
-
-- *vstring*: The input is treated as a variable length string and requires an expression tp provide the number of bits to read.
-
-=== Complex Types
-
-In contrast to simple types, complex types reference other complex types (Root elements of the spec document).
-
-How the parser should interpret them is defined in the referenced types definition.
-
-In the example above, for example the `S7Parameter` is defined in another part of the spec.
-
-=== Field Types and their Syntax
-
-==== array Field
-
-An `array` field is exactly what you expect.
-It generates an field which is not a single-value element but an array or list of elements.
-
-    [array {bit|byte}           {name} {count|length|terminated} '{expression}']
-
-    [array {simple-type} {size} {name} {count|length|terminated} '{expression}']
-
-    [array {complex-type}       {name} {count|length|terminated} '{expression}']
-
-Array types can be both simple and complex typed and have a name.
-An array field must specify the way it's length is determined as well as an expression defining it's length.
-Possible values are:
-- `count`: This means that exactly the number of elements are parsed as the `expression` specifies.
-- `length`: In this case a given number of bytes are being read. So if an element has been parsed and there are still bytes left, another element is parsed.
-- `terminated`: In this case the parser will continue reading elements until it encounters a termination sequence.
-
-==== assert Field
-
-An assert field is pretty much identical to a `const` field.
-The main difference however it how the case is handled, if the parsed value does not match the expected value.
-
-     [assert         {bit|byte}            {name}          '{assert-value}']
-
-     [assert         {simple-type} {size}  {name}          '{assert-value}']
-
-While a `const` field would abort parsing in total with an error, an `assert` field with abort parsing, but the error will only bubble up in the stack till the first `optional` field is found.
-
-In this case the parser will be rewound to the position before starting to parse the `optional` field and continue parsing with the next field, skipping the `optional` field.
-
-If there is no upstream `optional` field, then parsing of the message terminates with an error.
-
-See also:
-- validation field: Similar to an `assert` field, however no parsing is done, and instead simply a condition is checked.
-- optional field: `optional` fields are aware of the types of parser errors produced by `assert` and `validation` fields
-
-==== checksum Field
-
-A checksum field can only operate on simple types.
-
-    [checksum {bit|byte}           {name} '{checksum-expression}']
-
-    [checksum {simple-type} {size} {name} '{checksum-expression}']
-
-When parsing a given simple type is parsed and then the result is compared to the value the `checksum-expression` provides.
-If they don't match an exception is thrown.
-
-When serializing, the `checksum-expression` is evaluated and the result is then output.
-
-Note: As quite often a checksum is calculated based on the byte data of a message read up to the checksum, an artificial variable is available in expressions called `checksumRawData` of type `byte[]` which contains an array of all the byte data read in the current message element and it's sub types in case of a discriminated type.
-
-This field doesn't keep any data in memory.
-
-See also:
-- implicit field: A checksum field is similar to an implicit field, however the `checksum-expression` is evaluated are parsing time and throws an exception if the values don't match.
-
-==== const Field
-
-A const field simply reads a given simple type and compares to a given reference value.
-
-    [const {bit|byte}           {name} {reference}]
-
-    [const {simple-type} {size} {name} {reference}]
-
-When parsing it makes the parser throws an Exception if the parsed value does not match the expected one.
-
-When serializing is simply outputs the expected constant.
-
-This field doesn't keep any data in memory.
-
-See also:
-- implicit field: A const field is similar to an implicit field, however it compares the parsed input to the reference value and throws an exception if the values don't match.
-
-==== discriminator Field
-
-Discriminator fields are only used in `discriminatedType`s.
-
-    [discriminator {simple-type} {size} {name}]
-
-They are used, in cases where the value of a field determines the concrete type of a discriminated type.
-In this case we don't have to waste memory on storing the discriminator value and this can be statically assigned to the type.
-
-When parsing a discriminator fields result just in being a locally available variable.
-
-When serializing is accesses the discriminated types constants and uses these as output.
-
-See also:
-- implicit field: A discriminator field is similar to an implicit field, however doesn't provide a serialization expression as it uses the discrimination constants of the type it is.
-- discriminated types
-
-==== implicit Field
-
-Implicit types are fields that get their value implicitly from the data they contain.
-
-    [implicit {bit|byte}           {name} '{serialization-expression}']
-
-    [implicit {simple-type} {size} {name} '{serialization-expression}']
-
-When parsing an implicit type is available as a local variable and can be used by other expressions.
-
-When serializing the serialization-expression is executed and the resulting value is output.
-
-This type of field is generally used for fields that handle numbers of elements or length values as these can be implicitly calculated at serialization time.
-
-This field doesn't keep any data in memory.
-
-==== manualArray Field
-
-    [manualArray {bit|byte}           {name} {count|length|terminated} '{loop-expression}' '{serialization-expression}' '{deserialization-expression}' '{length-expression}']
-
-    [manualArray {simple-type} {size} {name} {count|length|terminated} '{loop-expression}' '{serialization-expression}' '{deserialization-expression}' '{length-expression}']
-
-    [manualArray {complex-type}       {name} {count|length|terminated} '{loop-expression}' '{serialization-expression}' '{deserialization-expression}' '{length-expression}']
-
-==== manual Field
-
-    [manual {bit|byte}           {name} '{serialization-expression}' '{deserialization-expression}' '{length-expression}']
-
-    [manual {simple-type} {size} {name} '{serialization-expression}' '{deserialization-expression}' '{length-expression}']
-
-    [manual {complex-type}       {name} '{serialization-expression}' '{deserialization-expression}' '{length-expression}']
-
-==== optional Field
-
-An optional field is a type of field that can also be `null`.
-
-    [optional {bit|byte}           {name} ('{optional-expression}')?]
-
-    [optional {simple-type} {size} {name} ('{optional-expression}')?]
-
-    [optional {complex-type}       {name} ('{optional-expression}')?]
-
-The `optional-expression` attribute is optional. If it is provided the `optional-expression` is evaluated.
-If this results in`false` nothing is parsed, if it evaluates to `true` it is parsed.
-
-In any case, if when parsing the content of an `optional` field a `assert` or `validation` field fails, the parser is rewound to the position before starting to parse the `optional` field, the optional field is then skipped and the parser continues with the next field.
-
-When serializing, if the field is `null` nothing is output, if it is not `null` it is serialized normally.
-
-See also:
-- simple field: In general `optional` fields are identical to `simple` fields except the ability to be `null` or be skipped.
-- `assert`: Assert fields are similar to `const` fields, but can abort parsing of an `optional` filed.
-- `validation`: If a validation field in any of the subtypes fails, this aborts parsing of the `optional` field.
-
-==== padding Field
-
-A padding field allows aligning of data blocks.
-It outputs additional padding data, given amount of times specified by padding expression.
-Padding is added only when result of expression is bigger than zero.
-
-    [padding {bit|byte}            {name} '{pading-value}' '{times-padding}']
-
-    [padding {simple-type} {size}  {name} '{pading-value}' '{times-padding}']
-
-When parsing a `padding` field is being parsed, the `times-padding` expressions determines how often the `padding-value` should be read. So it doesn't really check if the read values match the `padding-value`, it just ensures the same amount of bits are being read. The read values are simply discarded.
-
-When serializing, the `times-padding` defines how often the `padding-value` should be written.
-
-This field doesn't keep any data in memory.
-
-===== peek Field
-
-// TODO: Implement
-
-==== reserved Field
-
-Reserved fields are very similar to `const` fields, however they don't throw exceptions, but instead log messages if the values don't match.
-
-The reason for this is that in general reserved fields have the given value until they start being used.
-
-If the field starts to be used this shouldn't break existing applications, but it should raise a flag as it might make sense to update the drivers.
-
-    [reserved {bit|byte}           {name} '{reference}']
-
-    [reserved {simple-type} {size} {name} '{reference}']
-
-When parsing the values a `reserved` field is parsed and the result is compared to the reference value and then discarded.
-
-If the values don't match, a log message is written.
-
-This field doesn't keep any data in memory.
-
-See also:
-- `const` field
-
-==== simple Field
-
-Simple fields are the most common types of fields.
-
-A `simple` field directly mapped to a normally typed field of a message type.
-
-    [simple {bit|byte}           {name}]
-
-    [simple {simple-type} {size} {name}]
-
-    [simple {complex-type}       {name}]
-
-When parsing, the given type is parsed (can't be `null`) and saved in the corresponding model instance's property field.
-
-When serializing it is serialized normally using either a simple type serializer or by delegating serialization to a complex type.
-
-==== typeSwitch Field
-
-// TODO: Finish this ...
-
-These types of fields can only occur in discriminated types.
-
-A `discriminatedType` must contain *exactly one* `typeSwitch` field, as it defines the sub-types.
-
-    [typeSwitch {field-or-attribute-1}(,{field-or-attribute-2}, ...)
-        ['{field-1-value-1}' {subtype-1-name}
-            ... Fields ...
-        ]
-        ['{field-1-value-2}', '{field-2-value-1}' {subtype-2-name}
-            ... Fields ...
-        ]
-        ['{field-1-value-3}', '{field-2-value-2}' {subtype-2-name} [uint 8 'existing-attribute-1', uint 16 'existing-attribute-2']
-            ... Fields ...
-        ]
-
-A type switch element must contain a list of at least one argument expression.
-Only the last option can stay empty, which results in a default type.
-
-Each subtype declares a comma-separated list of concrete values.
-
-It must contain at most as many elements as arguments are declared for the type switch.
-
-The matching type is found during parsing by starting with the first argument.
-
-If it matches and there are no more values, the type is found, if more values are provided, they are compared to the other argument values.
-
-If no type is found, an exception is thrown.
-
-Inside each subtype can declare fields using a subset of the types (`discriminator` and `typeSwitch` can't be used here)
-
-The third case in above code-snippet also passes a named attribute to the subtype.
-The name must be identical to any argument or named field parsed before the switchType.
-These arguments are then available for expressions or passing on in the subtypes.
-
-// TODO: Wildcard names
-
-See also:
-- `discriminatedType`
-
-===== unknown Field
-
-// TODO: Finish this ...
-
-This type of field is mainly used when working on reverse-engineering a new protocol.
-It allows parsing any type of information, storing and using it and serializing it back.
-
-In general, it's something similar to a `simple` field, just explicitly states, that we don't yet quite know how to handle the content.
-
-===== validation Field
-
-As mentioned before, a `validation` field is not really a field, it's a check that is added to the type parser.
-
-// TODO: Finish this ...
-
-If the expression provided in the `validation` field fails, the parser aborts parsing and goes up the stack, till it finds the first `optional` field.
-If it finds one, it rewinds the parser to the position just before starting to parse the `optional` field, then skips the `optional` fields and continues with the next field.
-
-If there is no `optional` field up the stack, then parsing fails.
-
-
-==== virtual Field
-
-Virtual fields have no impact on the input or output.
-They simply result in creating artificial get-methods in the generated model classes.
-
-    [virtual {bit|byte}           {name} '{value-expression}']
-
-    [virtual {simple-type} {size} {name} '{value-expression}']
-
-    [virtual {complex-type}       {name} '{value-expression}']
-
-Instead of being bound to a property, the return value of a `virtual` property is created by evaluating the `value-expression`.
-
-==== Parameters
-
-Sometimes it is necessary to pass along additional parameters.
-
-If a complex type requires parameters, these are declared in the header of that type.
-
-....
-[discriminatedType S7Payload(uint 8 'messageType', S7Parameter 'parameter')
-    [typeSwitch 'parameter.discriminatorValues[0]', 'messageType'
-        ['0xF0' S7PayloadSetupCommunication]
-        ['0x04','0x01' S7PayloadReadVarRequest]
-        ['0x04','0x03' S7PayloadReadVarResponse
-            [arrayField S7VarPayloadDataItem 'items' count 'CAST(parameter, S7ParameterReadVarResponse).numItems']
-        ]
-        ['0x05','0x01' S7PayloadWriteVarRequest
-            [arrayField S7VarPayloadDataItem 'items' count 'COUNT(CAST(parameter, S7ParameterWriteVarRequest).items)']
-        ]
-        ['0x05','0x03' S7PayloadWriteVarResponse
-            [arrayField S7VarPayloadStatusItem 'items' count 'CAST(parameter, S7ParameterWriteVarResponse).numItems']
-        ]
-        ['0x00','0x07' S7PayloadUserData
-        ]
-    ]
-]
-....
-
-Therefore, wherever a complex type is referenced an additional list of parameters can be passed to the next type.
-
-Here comes an example of this in above snippet:
-
-    [field S7Payload   'payload'   ['messageType', 'parameter']]
-
-==== Serializer and Parser-Arguments
-
-Arguments influence the way the parser or serializer operates.
-
-Wherever an parser-argument is used, this should also be valid in all subtypes the parser processes.
-
-===== byteOrder
-
-A `byteOrder` argument can set or change the byte-order used by the parser.
-
-We currently support two variants:
-
-- BIG_ENDIAN
-- LITTLE_ENDIAN
-
-===== encoding
-
-Each simple type has a default encoding, which is ok for a very high percentage of cases.
-
-Unsigned integers for example use 2s-complement notation, floating point values are encoded in IEEE 754 single- or double precision encoding. Strings are encoded as UTF-8 per default.
-
-However, in some cases an alternate encoding needs to be used. Especially when dealing with Strings, different encodings, such as ASCII, UTF-16 and many more, can be used. But also for numeric values, different encodings might be used. For example does KNX use a 16bit floating point encoding, which is not standard or in S7 drivers a special encoding was used to encode numeric values so they represent the number in hex format.
-
-An `encoding` attribute can be used to select a non-default encoding.
\ No newline at end of file
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/conferences.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/conferences.adoc
deleted file mode 100644
index cde6fe0..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/conferences.adoc
+++ /dev/null
@@ -1,49 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-
-== Conferences & Events
-
-On this page we are listing options to attend talks and events around PLC4X.
-
-[width="100%",cols="2,^2,2,^2,^3",options="header"]
-|=========================================================
-|Date |Location |Type |Event | Title
-|18th June 2019 |Erfurt (GER) |Meetup |https://www.meetup.com/de-DE/iothde/events/260140057/[IoT Thüringen] |Industrie & IoT: Die perfekte Verbindung mit Flexibus & Apache PLC4X
-|24th May 2019  |Frankfurt (GER) |Meetup |https://www.meetup.com/de-DE/IoT-Hessen/events/261422034/[IoT Hessen] |Industrial IoT goes Open Source: Apache PLC4X Talks & Party
-|3th April 2019 |Cologne (GER) |Conference |https://www.buildingiot.de[Building IoT] |Apache PLC4X: Industry 4.0 done our way
-|8th March 2019 |Solingen (GER) |Conference |https://www.codecentric.de/2019/02/05/industrial-iot-day-solingen[Industrial IoT Day] |Apache PLC4X: Industry 4.0 done our way
-|21th February 2019 |Aachen (GER) |Meetup | http://www.euregjug.eu/2019/01/29/episode-iv-a-new-hope-industry-40-done-our-way[EURegJUG Maas-Rhine] |Episode IV - A New Hope: Industry 4.0 Done Our Way
-|15th February 2019 |Nürtingen (GER) |Meetup | PLC4X Meetup |Special Hackathon looking deeper into some new Protocols
-|15th November 2018 |Düsseldorf (GER) |Meetup |RheinJUG |http://www.rheinjug.de/rheinjug/event/2018/11/15/wie-wir-mit-apache-plc4x-die-silos-in-der-automatisierungsindustrie-aufbrechen.html[Wie wir mit Apache PLC4X die Silos in der Automatisierungsindustrie aufbrechen]
-|12th-13th November 2018 |Berlin (GER) |Conference |https://www.sv-veranstaltungen.de/fachbereiche/big-data-3/[3. Fachkonferenz: Industrial Analytics & Big Data in der Industrie] |Kommunikation mit Industrieanlagen ohne Umbau- und Lizenzkosten
-|22th-24th October 2018 |Edinburgh (GB) |Conference |https://events.linuxfoundation.org/events/open-source-summit-europe-2018/[Open-Source Summit Europe] |Revolutionizing the production industry with Apache PLC4X
-|24th-19th September 2018 |Montreal (CAN) |Conference |http://apachecon.com/acna18/?ref=apachecon.com[ApacheCon NA 2018] |https://apachecon.dukecon.org/acna/2018/#/scheduledEvent/51feeb6f55f250c39[Revolutionizing the Production Industry with Apache PLC4X (incubating)]
-|20th September 2018 |Nürtingen (GER) |Meetup |PLC4X Meetup |First general committer meetup
-|13th-14th June 2018 |Berlin (GER) |Conference |http://www.apachecon.com/euroadshow18/#[Apache EU Roadshow] |https://foss-backstage.de/session/revolutionizing-production-industry-apache-plc4x[Revolutionizing the production industry with Apache PLC4X]
-|4th June 2018 |Cologne (GER) |Conference |https://www.buildingiot.de/[Building IoT] |https://www.buildingiot.de/veranstaltung-6815-industrial-iot-und-edge-computing-mit-apache-plc4x-und-apache-edgent-%5Bsponsored-talk%5D.html?id=6815[Industrial IoT und Edge Computing mit Apache PLC4X und Apache Edgent]
-|5th April 2018 |Hamburg (GER) |Conference |https://techcamp.hamburg/[TechCamp Hamburg] |https://techcamp.hamburg/events/revolutionizing-industrial-iot-with-apache-plc4x/[Revolutionizing Industrial IoT with Apache PLC4X]
-|21th January 2018 |Hamburg (GER) |Conference |https://www.nortec-hamburg.de/[Nortec] |Mehr für Weniger? Aber Sicher!
-|4th-5th May 2019 |Brussels (BE) |Hackathon |https://eufossahackathon.bemyapp.com[EU FOSSA Apache Hackathon] | Co-creating the future of open source
-|=========================================================
-
-Looking forward to meeting you.
-
-If you've got or found any events or talks we might be missing, please inform us on dev@plc4x.apache.org.
-
-== Additional Material
-
-link:/images/PLC4X_rollup_83x237cm-final.pdf[PLC4X Banner]
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/contributing.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/contributing.adoc
deleted file mode 100644
index 09fc6a6..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/contributing.adoc
+++ /dev/null
@@ -1,208 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-:imagesdir: ../images/
-
-== Contributing
-
-=== Forms of contribution
-
-There are multiple forms in which you can become involved with the PLC4X project.
-
-These usually are, but are not limited to:
-
-- Submitting Pull Requests
-- Filing Bug-Reports
-- Active communication on our mailing lists
-- Promoting the project (articles, blog posts, talks at conferences)
-- Documentation
-
-We are a very friendly bunch and don't be afraid to step forward.
-
-=== Commits
-
-We make use of https://www.conventionalcommits.org/en/v1.0.0/[conventional commits].
-As plc4x is a monolithic polyglot repository we usually define the scope as `...(plc4[language shortcut here]/subcomponent)`
-(e.g. a new feature in Bacnet in the Golang part would have a message of `feat(plc4go/bacnet): cool new feature for...`).
-
-=== Pull-Requests
-
-The simplest way to submit code changes, is via a GitHub pull-request.
-
-In order to do this first create a GitHub account and sign into you account.
-
-After that's done, please to to our https://github.com/apache/plc4x[GitHub site] and create a so-called `Fork`.
-
-image::contributing-github-fork.png[]
-
-What happens now, is that GitHub creates a full copy of the PLC4X repo in your account. Only you can commit to this.
-
-Now ideally you check-out your cloned repository:
-
-    git clone https://github.com/{your-user-id}/plc4x.git
-
-Now you have a copy of PLC4X on your computer and you can change whatever you want and as it's your copy, you can even commit these changes without any danger of breaking things.
-
-As soon as you're finished with your changes and want us to have a look, it's time to create a so-called `Pull-Request`.
-
-You do that by going to your forked repository page on GitHub.
-
-Every forked repository has an additional button called "New Pull Request":
-
-image::contributing-github-create-pull-request.png[]
-
-If you click on this, we will receive a notification on your changes and can review them.
-We also can discuss your changes and have you perfect your pull request before we accept and merge it into PLC4X.
-
-==== Keeping your fork up to date
-
-As we are continuously working on PLC4X and you created a copy of our repo, this will become out-of-date pretty soon.
-
-In order get the changes we introduced in the official repo you have to tell git about that.
-
-You do this locally by adding a new so-called `remote`.
-Per default the remote you cloned from is called `origin`.
-
-Usually you will call the second remote `upstream` but in general you can call it whatever you like.
-
-Add the remote on the commandline (or your git gui of choice):
-
-    git remote add upstream https://github.com/apache/plc4x.git
-
-If you list all your remotes, with the following command:
-
-    git remote -v
-
-It should output something like this:
-
-    origin    https://github.com/{your-user-id}/plc4x.git (fetch)
-    origin    https://github.com/{your-user-id}/plc4x.git (push)
-    upstream    https://github.com/apache/plc4x.git (fetch)
-    upstream    https://github.com/apache/plc4x.git (push)
-
-If that's so, you're fine to continue, if not ... well you could ask for assistance on our dev-list.
-
-In order to get all changes of our upstream-repository, just execute the following command:
-
-    git pull upstream
-
-This will get all changed from upstream and merge them locally. In order to update your GitHub version, you have to push things back to `origin`.
-You can do this by executing the following command:
-
-    git push
-
-(If no remote is provided, git will use `origin` per default)
-
-===  Bug Reports
-
-We use https://issues.apache.org/jira/projects/PLC4X[JIRA] as our Bug & Issue Tracker.
-
-Feel free to submit `feature requests`, `bug reports`, `patches`, `comment on issues`, ...
-
-In order to be able to do so, you need to create an account first.
-
-Currently Apache has a separate login system for JIRA and all other services, this might change in the future, but right now it's the way things are.
-
-So if you are considering to contribute more than just a one-time-patch, please choose a username that hasn't been used by an existing http://people.apache.org/committer-index.html[Apache committer] as this will simplify things if we invite you to become part of the team.
-
-If you want to be assigned to an issue because you want to work on it, please request to be added to the JIRA groups on our http://plc4x.apache.org/mailing-lists.html[developers mailing list]
-
-=== Documentation
-
-As our documentation and website are generated as a side-product of our build, contributing to this technically the same as contributing to the code.
-
-All our content is written in Asciidoctor and is located in `src/site/asciidoc` directories.
-For a reference of the Asciidoctor syntax please have a look at the https://asciidoctor.org/docs/user-manual/#introduction-to-asciidoctor[Asciidoctor documentation].
-
-=== Branching model
-
-The PLC4X project uses the following branching model.
-
-The same model is used for a wide variety of other projects, so it should be pretty straight forward.
-
-- `release` contains the latest released state.
-- Development is performed on the `develop` branch.
-- Features are developed in Feature-Branches with a prefix `feature/`
-- Each minor release has a corresponding release branch `rel/{major-version}.{minor-version}`
-- A release branch is spawned from `develop` only
-- Bugfix releases don't have a dedicated release branch, they are just performed on the corresponding minor versions release branch
-
-// Use http://www.webgraphviz.com/ for online editiing this ...
-[graphviz, plc4x-branching-model, png]
-----
-digraph g{
-    rankdir="LR";
-    pad=0.5;
-    nodesep=0.6;
-    ranksep=0.5;
-    forcelabels=true;
-
-    node [fixedsize=true,
-        shape=circle, style=empty, color="#909090", height=0.5
-        fontcolor="deepskyblue", font="Arial bold", fontsize="14pt" ];
-    edge [color="#909090", penwidth=3];
-
-    node  [group="release"];
-    m1    [label="release", width=0.9];
-    m2   [label="0.2.0", width=0.9];
-    m3   [label="0.2.1", width=0.9];
-    m4   [label="", shape=circle, color="#b0b0b0"];
-    m1 -> m2 -> m3
-    m3 -> m4 [color="#b0b0b0", style=dashed];
-
-    node  [group="rel/0.1", Ylabel="hurz"];
-    r11   [label="rel/0.1", width=2, shape=box];
-    r12   [label="0.1.0-SNAPSHOT", width=2, shape=box];
-    r13   [label="0.1.0", width=0.9];
-    r14   [label="0.1.1-SNAPSHOT", width=2, shape=box];
-    r15   [label="", shape=circle, color="#b0b0b0"];
-    r11 -> r12 -> r13 -> r14;
-    r14 -> r15 [color="#b0b0b0", style=dashed];
-    r13 -> m1
-
-    node  [group="rel/0.2", Ylabel="hurz"];
-    r21   [label="rel/0.2", width=2, shape=box];
-    r22   [label="0.2.0-SNAPSHOT", width=2, shape=box];
-    r23   [label="0.2.0", width=0.9];
-    r24   [label="0.2.1-SNAPSHOT", width=2, shape=box];
-    r25   [label="0.2.1", width=0.9];
-    r26   [label="0.2.2-SNAPSHOT", width=2, shape=box];
-    r27   [label="", shape=circle, color="#b0b0b0"];
-    r21 -> r22 -> r23 -> r24 -> r25 -> r26;
-    r26 -> r27 [color="#b0b0b0", style=dashed];
-    r23 -> m2
-    r25 -> m3
-
-    node  [group="develop"];
-    d1    [label="develop", width=2, shape=box];
-    d2    [label="0.1.0-SNAPSHOT", width=2, shape=box];
-    d3    [label="0.1.0-SNAPSHOT", width=2, shape=box];
-    d4    [label="0.2.0-SNAPSHOT", width=2, shape=box];
-    d5    [label="0.2.0-SNAPSHOT", width=2, shape=box];
-    d6    [label="0.2.0-SNAPSHOT", width=2, shape=box];
-    d7    [label="0.3.0-SNAPSHOT", width=2, shape=box];
-    d8    [label="0.3.0-SNAPSHOT", width=2, shape=box];
-    d9    [label="0.3.0-SNAPSHOT", width=2, shape=box];
-    d10    [label="", shape=circle, color="#b0b0b0"];
-    d1 -> d2 -> d3 -> d4 -> d5 -> d6 -> d7 -> d8 -> d9;
-    d9 -> d10 [color="#b0b0b0", style=dashed];
-
-    d3 -> r11
-    d6 -> r21
-}
-----
-
-
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/decisions.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/decisions.adoc
deleted file mode 100644
index 61d181e..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/decisions.adoc
+++ /dev/null
@@ -1,66 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-:imagesdir: ../images/
-
-== Decision Making
-
-=== Introduction
-
-This document describes the roles and responsibilities of the project, who may vote, how voting works, how conflicts are resolved, etc.
-
-The https://www.apache.org/foundation/faq[Apache Foundation FAQ] and http://www.apache.org/foundation/faq.html[How-It-Works] explain the operation and background of the foundation. Terms used are defined in the https://www.apache.org/foundation/glossary[ASF glossary].
-
-Apache has a http://www.apache.org/foundation/policies/conduct.html[code of conduct] that it expects its members to follow.
-
-=== Roles and Responsibilities
-
-Apache projects define a set of https://www.apache.org/foundation/how-it-works.html#roles[roles] with associated rights and responsibilities.
-
-==== Project Management Committee
-
-The http://www.apache.org/dev/pmc.html#what-is-a-pmc[PMC] has many https://www.apache.org/foundation/how-it-works.html#pmc[responsibilities] including complying with http://www.apache.org/dev/pmc.html#policy[ASF policies], https://www.apache.org/foundation/board/reporting[reporting to the board], https://www.apache.org/foundation/voting.html[approving releases] and adding new http://www.apache.org/dev/pmc.html#newcommitter[committers] and http://www.apache.org/dev/pmc.html#newpmc[PMC members].
-
-==== The Chair
-
-The http://www.apache.org/dev/pmc.html#chair[chair] ensures board reports are submitted and that the project's roster is up to date.
-
-=== Decision Making
-
-Different decisions require different forms of approval but community consensus is always the goal. Voting when needed should be open for http://www.apache.org/legal/release-policy.html#release-approval[at least 72 hours].
-
-- https://www.apache.org/foundation/glossary.html#ConsensusApproval[Consensus Approval] – Consensus approval requires 3 https://www.apache.org/foundation/voting.html#binding-votes[binding] +1 votes and no -1 votes (https://www.apache.org/foundation/glossary.html#Veto[vetoes]).
-- https://www.apache.org/foundation/glossary.html#MajorityApproval[Majority Approval] – requires at least 3 https://www.apache.org/foundation/voting.html#binding-votes[binding] +1 votes more +1 votes than -1 votes.
-- https://www.apache.org/foundation/glossary.html#LazyConsensus[Lazy Consensus] – consensus no objections (‘silence gives assent’).
-
-|===
-|Action                     |Who can vote |Approval           |Where to vote             |Board approval required
-|Code change                |Committer    |Lazy Consensus     |public dev or commit list |
-|Release                    |PMC          |Majority Approval  |public dev list           |
-|New committer              |PMC          |Consensus Approval |private list              |
-|New PMC member             |PMC          |Consensus Approval |private list              |Yes 1)
-|Existing committer removal |PMC          |Consensus Approval |private list              |
-|Existing PMC removal       |PMC          |Consensus Approval |private list              |Yes 2)
-|Change chair               |PMC          |Consensus Approval |private list              |Yes 3)
-|===
-
-1. http://www.apache.org/dev/pmc.html#notice_period[Notice] must be given to board.
-2. Except PMC member in question. Only the board can http://www.apache.org/dev/pmc.html#pmc-removal[remove PMC members].
-3. Need to be http://www.apache.org/dev/pmc.html#newchair[approved by the board] at the next board meeting.
-
-
-
-
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/index.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/index.adoc
deleted file mode 100644
index 33aea91..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/index.adoc
+++ /dev/null
@@ -1,59 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-:imagesdir: ../images/
-:icons: font
-
-== Developer Section
-
-This part of the Apache PLC4X dedicated to provide information to people wanting to build PLC4X and hopefully also start contributing to this awesome project.
-
-=== Getting Started
-
-We have tried to make the PLC4X build experience as smooth as possible and have tried to reduce the number of required third party tools to an absolute minimum.
-
-The full PLC4X build however builds not only `Java` libraries, but also `C++`, `Python` and `C#` libraries as well as builds `Docker` images on `Linux`, `Mac` and `Windows`.
-
-As a start, you will basically need a `Java VM` of at least `Java 11`.
-
-Using the `Maven-Wrapper` you don't even need a `Maven` installation. The build will automatically fetch the right version for you.
-
-As part of the build we have an initial build step that will do a `prerequisite check`. Depending on the activated modules, it will check if all preconditions are met and tell you what's missing.
-
-For details please have a look at the link:preparing/index.html[Preparing your Computer] page.
-
-=== Building PLC4X
-
-We have a dedicated page on link:building.html[Building PLC4X].
-
-Please read this page on information about how to build Apache PLC4X.
-
-=== Contributing
-
-If you want to work on Apache PLC4X in order to `fix things`, `add things` and start `contributing` in general, please have a look at our link:contributing.html[Contributing] page. It should contain all the information you need.
-
-=== Getting Help
-
-The primary source for getting help definitely is our project mailing list dev@plc4x.apache.org.
-
-You can search previous content in our link:++https://lists.apache.org/list.html?dev@plc4x.apache.org++[Mail Archive]
-
-In order to post to the list you first need to subscribe. This can be done by sending an empty Email to dev-subscribe@plc4x.apache.org.
-
-
-
-
-
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/infrastructure/ci.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/infrastructure/ci.adoc
deleted file mode 100644
index fcb0558..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/infrastructure/ci.adoc
+++ /dev/null
@@ -1,40 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-:imagesdir: ../images/
-
-== Continuous Integration
-
-We are currently using the following CI systems.
-
-- Apache's Jenkins at: https://ci-builds.apache.org/job/PLC4X/
-- GitHub Actions at: https://github.com/apache/plc4x/actions
-
-The build on Jenkins is generally responsible for building and testing the state of the project on the `development` branch.
-It is currently the only service that is able to build and deploy the `SNAPSHOT` artifacts and is also responsible for building and updating our website.
-
-GitHub Actions on the other side responsible for doing the main part of the testing.
-It not only builds and runs the tests on a matrix of operating systems as well as with a number of java versions.
-It also is configured to run the tests on pull-requests.
-
-=== Structure of the Jenkins Pipeline build
-
-We are using the Jenkins `multi-branch pipeline plugin` to automatically setup build for branches based upon the build definition in the `Jenkinsfile` in the root of the project.
-
-In general, it builds the `develop` branch and all branches starting with the prefix `feature/`.
-However, when building the `develop` branch some additional steps are performed.
-
-When building `develop` the build not only builds the project itself and runs all tests, it also runs the `sonarcloud` analysis, deploys the artifacts built to the `Apache Nexus` as well as generates and deploys the website.
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/infrastructure/index.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/infrastructure/index.adoc
deleted file mode 100644
index 7f48619..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/infrastructure/index.adoc
+++ /dev/null
@@ -1,22 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-:imagesdir: ../../images/
-:icons: font
-
-== Infrastructure
-
-In this section you can find information on the services the Apache PLC4X project makes use of.
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/infrastructure/issues.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/infrastructure/issues.adoc
deleted file mode 100644
index 13b44a1..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/infrastructure/issues.adoc
+++ /dev/null
@@ -1,24 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-
-== Bug & Issue Tracker
-
-Our bug & issue tracker is Github-Issues.
-
-This service is available here:
-
-https://github.com/apache/plc4x/issues
\ No newline at end of file
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/infrastructure/sonar.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/infrastructure/sonar.adoc
deleted file mode 100644
index 663d919..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/infrastructure/sonar.adoc
+++ /dev/null
@@ -1,24 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-
-== Code Analysis
-
-We are using `SonarCloud` as the service for static code analysis.
-
-This is an externally hosted service and is available here:
-
-https://sonarcloud.io/dashboard?id=apache_plc4x
\ No newline at end of file
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/infrastructure/vm.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/infrastructure/vm.adoc
deleted file mode 100644
index a42a8d8..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/infrastructure/vm.adoc
+++ /dev/null
@@ -1,102 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-
-== The PLC4X Project VM
-
-As, especially for the raw socket functionality of PLC4X, our project had higher demands on the infrastructure as other projects.
-Apache Infra kindly provided us with a dedicated VM.
-
-This is included as build agent into Apache's Jenkins with the label `plc4x2` and is marked for exclusive usage by our project.
-
-The host name of this machine is: `plc4x-vm2.apache.org`
-
-On this machine we can even `sudo` to perform operations only available to `root`.
-
-Project members can request access to the machine.
-
-=== Requesting access
-
-In order to be able to log in, users need to add their SSH public key to their Apache ID first.
-
-This is done under the following url: https://id.apache.org/
-
-Here just add the content in the following format to one of the `SSH Key (authorized_keys line)` fields:
-
-    ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQDd10ykYAZLxHJVTER71IrrVVpyR8OBdlJd1aVwb67Ts+ueJjzo8ofQKLASaQw9EQOSfprGZW0sfzhepeJvbX0n1IfsRexoyIGlD8WzyX/UoLiRLPHFv+eSGJVlN90x/l+zps+yo3lq6qfuIqkXQQvB4aJBYsYC/jifpMLvx06zaUBPfdWIaGiBgaWbX/59Q0QsSpX5r8tgdA+XLw/8Zg5AbKazuS2Cm/soJCfQQ7km4bd/WtF5R5xvakVbyILMT8Dk9Hs9OfVL/RFGLYqX4bjy5uCTwPBrwlWqFyq1u7JR39i870XNgn+bIeChaZU098BGyBH/cWMGt7bTJQSKxksF2SZAHjt8Ga2Pl+J6MTW6/EPzIYENgvfOBVSlVaz9SlM26nel1+SHDND9dK/4gRNbujbmzHZLfTjMk7oc4R+WPCBIw99CFeShTKHSxhJKz/3K [...]
-
-(I just had to copy this line from my `~/.ssh/id_rsa.pub` file)
-
-TIP: Note, the Email Address in the end doesn't seem to matter, I simply added it for the sake of completeness. So if this doesn't match your Apache email, this is not a problem.
-
-As soon as that's done, access needs to be requested from Apache Infra.
-
-This is done using the Infra Jira at: https://issues.apache.org/jira
-
-Here make sure to select the Project `Infrastructure (INFRA)`.
-
-As soon as that's handled by the Infra team, you should be ready to log-in on the machine.
-
-=== Login to the machine
-
-Using SSH we should now be able to log in to the VM.
-
-   ssh apacheId@plc4x-vm2.apache.org
-
-Be sure to use the username matching your Apache ID or the login will fail.
-
-If all went well you should now be able to log in to the machine using your apache user.
-
-=== Doing things as `root`
-
-Apache Infra is great at keeping things safe.
-Providing a sudo password directly would increase the danger of having this intercepted, therefore they are using a tool called `opiepasswd`.
-
-Instead of now entering a password, a challenge is displayed:
-
-    myid@plc4x-vm2:~$ sudo apt-get update
-    otp-md5 496 pl8230
-    Password:
-
-If you now enter your normal password, you'll simply get `permission denied` errors.
-
-In order to execute operations as root on the machine, you firstly need to run ortpasswd to generate a new seed.
-
-    ortpasswd
-
-You can then use an opie client on your local machine or online at https://selfserve.apache.org/otp-calculator.html
-
-   otp-md5 496 pl8230
-
-into OPIE client's `challenge` field.
-
-In the `password` field you provide your Apache LDAP password.
-
-When hitting enter or clicking on `Compute` the tool should automatically generate a response.
-
-Now all you need to do is copy & paste that as password into your SSH client session.
-
-TIP: As with the latest version of Mac Catalina the existing clients no longer work and using a public web service is a bad idea, Apache has its own service to calculate it:
-https://selfserve.apache.org/otp-calculator.html
-
-TIP: More help can be found for Apache committers at https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=122916896
-
-=== Required software
-
-For being able to build the charts and graphics as part of the site generation, we need to add some additional packages:
-
-   sudo apt-get install python-seqdiag
-   sudo apt-get install python-nwdiag
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/infrastructure/website.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/infrastructure/website.adoc
deleted file mode 100644
index 5a39068..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/infrastructure/website.adoc
+++ /dev/null
@@ -1,177 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-
-== Generating the Website
-
-We are currently using the normal `Maven` build to not only generate the project artifacts, but also the projects website.
-
-In order to provide content, every module can have a `src/site` directory. This content will be generated to that modules site-part.
-
-The `skin` being used to generate the site is none of the default `Maven` skins, but a more up-to-date looking skin using:
-
-- Bootstrap (For the CSS)
-- JQuery (For the JavaScript magic)
-- Fontawesome (For icons and symbols)
-
-But we don't have to worry about the details, all is configured to be used automatically.
-
-The site content itself is generated from `asciidoc` files (ending `.adoc`) which is a simple yet powerful markup language.
-(See http://asciidoctor.org/docs/asciidoc-syntax-quick-reference/[AsciiDoc Syntax Quick Reference] or https://powerman.name/doc/asciidoc[AsciiDoc cheatsheet] for details)
-
-Beyond the basic goodies, the build is also configured to generate images from ASCII data using the `asciidoctor-diagram` plugin.
-
-This allows us to generate images like the ones on the http://plc4x.apache.org/protocols/s7/index.html[S7 Protocol Description page]
-
-=== Providing new content
-
-Within the `src/site` directory there is a file `site.xml` which generally controls the menu and the look of the site.
-
-Most setting are inherited from the `plc4x-parent` module. That's also why this is more complicated than the others.
-
-The `site.xml` file is optional. Even if this is not available a site will be generated however no additional content will be linked from any of the navigation menus.
-
-So if we wanted to add a new page on some (hopefully non existent) `Wombat PLC Protocol`, we would create a file called:
-
-`index.adoc` in the `src/site/asciidoc/protocols/wombat` directory.
-
-For example with this content:
-
-```
-== Wombat PLC Protocol
-
-If you want to waste your money, brains and time, feel free to use a `Wombat PLC`.
-
-In order to help you waste even more of that, we'll skip documenting anything.
-
-```
-
-Notice the double equals sign? This is the site Title. It seems the level `One` with only one equals sign is only used for ebook output.
-
-So just keep in mind: Two equals signs is the top level title, all lower levels have more equals signs.
-
-In order to generate the content you need to execute the Maven `site` workflow.
-
-This is for example done by executing:
-
-    mvn site
-
-This will not build the artifact itself, but only it's website.
-
-After the build, you would find a file `target/site/protocols/wombat/index.html`
-
-However you can link to this page from any other page, but it is not added ot the navigation menu.
-
-=== Adding links to menus
-
-In order to add links to the menus, you have to create or modify the `site.xml` for the module you want to add content to.
-
-The simplest form would probably be something like this:
-
-```
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!--
-
- Licensed to the Apache Software Foundation (ASF) under one or more
- contributor license agreements.  See the NOTICE file distributed with
- this work for additional information regarding copyright ownership.
- The ASF licenses this file to You under the Apache License, Version 2.0
- (the "License"); you may not use this file except in compliance with
- the License.  You may obtain a copy of the License at
-
- https://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
-
- -->
-<project name="PLC4J">
-
-  <body>
-    <menu name="Wombat">
-      <item name="lalala" href="https://plc4x.apache.org/somemodule/somedocument.html"/>
-    </menu>
-  </body>
-
-</project>
-```
-
-This will generate a `Wombat` menu at the end, and this has one link named `lalala`.
-
-Notice that the link has to have a file ending of `.html` and not `.adoc`.
-
-If you want to insert the menu somewhere else, you will have to re-define the entire menu.
-
-```
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!--
-
- Licensed to the Apache Software Foundation (ASF) under one or more
- contributor license agreements.  See the NOTICE file distributed with
- this work for additional information regarding copyright ownership.
- The ASF licenses this file to You under the Apache License, Version 2.0
- (the "License"); you may not use this file except in compliance with
- the License.  You may obtain a copy of the License at
-
- https://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
-
- -->
-<project name="PLC4J">
-
-  <body>
-
-      <menu ref="reports" inherit="top"/>
-      <menu ref="parent" inherit="top"/>
-
-      <menu name="Wombat">
-        <item name="lalala" href="https://plc4x.apache.org/somemodule/"/>
-      </menu>
-
-      <menu ref="modules" inherit="top"/>
-
-  </body>
-
-</project>
-```
-
-The `menu ref` items hereby reference standard menus provided by the `Maven` build.
-
-=== Deploying the Website
-
-The PLC4X project uses Apache `gitpubsub` system for maintaining the website.
-
-In general all content in a repos `asf-site` branch is copied to the Webservers, if that repo is registered for it.
-
-The content in this branch is generated and maintained during the `Maven` build as part of the `site` generation if the `site-deploy` phase is executed.
-
-The build system needs to check-in content to the `asf-site` branch and usually ASF Jenkins nodes don't have the permissions to do that.
-
-In order to be able to push to the `asf-site` GIT branch, a dedicated build job is configured to build on nodes with the Jenkins label `git-websites`.
-
-Only on these machines are jobs allowed to push changes to a Git repo and here only to a branch named `asf-site`.
-
-See https://ci-builds.apache.org/job/PLC4X/ for details on the PLC4X Jenkins Website build job.
-
-As soon as content is updated in the `asf-site` the `gitpubsub` mechanism will make those changes available at https://plc4x.apache.org
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/infrastructure/wiki.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/infrastructure/wiki.adoc
deleted file mode 100644
index 7c72a1c..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/infrastructure/wiki.adoc
+++ /dev/null
@@ -1,24 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-
-== WIKI
-
-We use Apache's Confluence instance as Wiki, however most information is generally managed on this website.
-
-This service is available here:
-
-https://cwiki.apache.org/confluence/display/PLC4X
\ No newline at end of file
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/jqassistant.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/jqassistant.adoc
deleted file mode 100644
index edd6928..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/jqassistant.adoc
+++ /dev/null
@@ -1,126 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-:imagesdir: ../images/
-
-== Using JQAssistant
-
-In PLC4X we are using a tool called `https://jqassistant.org/[JQAssistant]` for enforcing quality assurance rules.
-
-`JQAssistant` can be thought of as a set of two components:
-
-- A set of scanners that analyse a project and stores the gathered information in for of linked graphs in a Neo4j database.
-- An engine that executes defined rules against the graph created during the scan phase of the build
-
-These rules can produce either reports and tables or they are used to enforce rules.
-
-If a pre-defined rule is violated the failed checks can be marked as `warning` or `error` that breaks the build.
-
-In contrast to using the `maven-enforcer-plugin` doing cross-domain checks is really simple as all information is available in one big graph.
-
-Currently the following scanners are active:
-
-- CDI
-- Common
-- Common Test
-- Core Analysis
-- EJB3
-- GraphML
-- JAX-RS
-- JPA 2
-- JSON
-- JUnit
-- Java
-- Java 9
-- Java EE 6
-- Maven 3
-- OSGi
-- RDBMS
-- TestNG
-- Tycho
-- XML
-- YAML
-
-These rules that are automatically checked during the build are defined in `src/jjqassistant`.
-If defined in a reactor project, the rules apply to all modules of that (sub-)reactor.
-So if they are defined in the root module of the project, it applies to all modules.
-
-=== Defining JQAssistant rules
-
-TODO: Finish this "little detail" ...
-
-=== Using the Web-UI
-
-The scan and analysis is automatically performed during a normal Maven build.
-In order to do ad-hoc queries against the project or develop new rules, the Web-UI is very helpful.
-
-To start the Web-UI, all you need to do, is run the following command (after a build):
-
-   mvn jqassistant:server
-
-This will start a Neo4j server with web console.
-
-   [INFO] --- jqassistant-maven-plugin:1.3.0:server (default-cli) @ plclogger ---
-   [INFO] Connecting to store at 'file:/Users/christofer.dutz/Projects/Apache/PLC4X/target/jqassistant/store/'
-   2018-04-05 19:11:14.369+0200 INFO  [o.n.s.CommunityNeoServer] No SSL certificate found, generating a self-signed certificate..
-   2018-04-05 19:11:14.683+0200 INFO  [o.n.s.CommunityNeoServer] Starting HTTP on port 7474 (8 threads available)
-   2018-04-05 19:11:14.859+0200 INFO  [o.n.s.w.Jetty9WebServer] Mounting static content at /webadmin
-   2018-04-05 19:11:14.892+0200 INFO  [o.n.s.w.Jetty9WebServer] Mounting static content at /browser
-   Apr 05, 2018 7:11:15 PM com.sun.jersey.server.impl.application.WebApplicationImpl _initiate
-   INFORMATION: Initiating Jersey application, version 'Jersey: 1.19 02/11/2015 03:25 AM'
-   Apr 05, 2018 7:11:15 PM com.sun.jersey.server.impl.application.WebApplicationImpl _initiate
-   INFORMATION: Initiating Jersey application, version 'Jersey: 1.19 02/11/2015 03:25 AM'
-   Apr 05, 2018 7:11:15 PM com.sun.jersey.server.impl.application.WebApplicationImpl _initiate
-   INFORMATION: Initiating Jersey application, version 'Jersey: 1.19 02/11/2015 03:25 AM'
-   2018-04-05 19:11:15.396+0200 INFO  [o.n.s.CommunityNeoServer] Remote interface ready and available at http://localhost:7474/
-   [INFO] Running server for module org.apache.plc4x:plc4x-parent:0.0.1-SNAPSHOT
-   [INFO] Press <Enter> to finish.
-
-So when visiting the anounced url with a browser, you can use the pretty useful neo4j web console.
-
-image::neo4j-web-console.png[Neo4j Web Console]
-
-=== Using IntelliJ Idea
-
-IntelliJ comes with some interesting Neo4J support. Unfortunately this only supports `Neo4j 3`.
-
-Unfortunately the process of enabling this toolset is a little less comfortable than the Web-UI version.
-
-Even if JQAssistant uses `Neo4j 2` per default, we can force it to use `Neo4j 3` by providing an additional commandline parameter.
-
-    mvn -Djqassistant.neo4jVersion=3 clean install
-
-JQAssistant uses Neo4j 3 and the resulting data directory is then in Neo4j 3 format.
-
-In this case the server has to be started with the same parameter:
-
-   mvn -Djqassistant.neo4jVersion=3 jqassistant:server
-
-As soon as the server is started, we can connect from the IntelliJ plugin.
-
-Note: The connection settings also contain a username and a password.
-
-image::neo4j-intellij-settings.png[width=800]
-
-It appears that this can simply be left empty of can contain random values.
-
-After creating the connection, the `Graph Neo4j` view should list the new connection.
-
-image::neo4j-intellij-database-connections-view.png[width=300]
-
-You can now use this to perform queries
-
-image::neo4j-intellij-query-results.png[width=800]
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/maturity.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/maturity.adoc
deleted file mode 100644
index dbefed5..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/maturity.adoc
+++ /dev/null
@@ -1,76 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-
-:icons: font
-
-== Apache Maturity Model Assessment for PLC4X
-
-=== Overview
-
-This is an assessment of the PLC4X project's maturity, meant to help inform the decision (of the mentors, community, Incubator PMC and ASF Board of Directors) to graduate it as a top-level Apache project.
-
-It is based on the ASF project maturity model at https://community.apache.org/apache-way/apache-project-maturity-model.html
-
-=== Maturity model assessment
-
-Community members are encouraged to contribute to this page and comment on it, the following table summarizes project’s self-assessment against the Apache Maturity Model.
-
-[width="100%",options="header"]
-|=========================================================
-|ID |Description |Status
-|*Code* 2+|icon:check[role=green]
-|CD10 |The project produces Open Source software, for distribution to the public at no charge. |icon:check[role=green] The project source code is licensed under the Apache License, version 2.0.
-|CD20 |The project's code is easily discoverable and publicly accessible. |icon:check[role=green] Our sourcecode is available at https://gitbox.apache.org/repos/asf/plc4x.git[Apache GitBox] and https://github.com/apache/plc4x[GitHub] and linked to from our https://plc4x.apache.org/scm.html[website]
-|CD30 |The code can be built in a reproducible way using widely available standard tools. |icon:check[role=green] our https://maven.apache.org[Maven] build has been tested on Linux, Mac-OS and Windows and build description is available on our https://plc4x.apache.org/developers/building.html[website]
-|CD40 |The full history of the project's code is available via a source code control system, in a way that allows any released version to be recreated. |icon:check[role=green] The entire commit history is available from the https://gitbox.apache.org/repos/asf?p=plc4x.git;a=commit;h=dd1fcf4649107762e91f7c494a10e55319a18785[beginning].
-|CD50 |The provenance of each line of code is established via the source code control system, in a reliable way based on strong authentication of the committer. When third-party contributions are committed, commit messages provide reliable information about the code provenance. |icon:check[role=green] The project uses the git repository, managed by Apache Infra, ensuring provenance of each line of code to a committer, each line committed before entering incubation was equally configured.
-|*Licenses and Copyright* 2+|icon:check[role=green]
-|LC10 |The code is released under the Apache License, version 2.0. |icon:check[role=green] Both the source distribution as well as the convenience binary artifacts clearly declare that they are licensed under the Apache 2.0 license
-|LC20 |Libraries that are mandatory dependencies of the project's code do not create more restrictions than the Apache License does. |icon:check[role=green] The list of mandatory dependencies have been reviewed to contain approved licenses only.
-|LC30 |The libraries mentioned in LC20 are available as Open Source software. |icon:check[role=green] All mandatory dependencies are available as open source software.
-|LC40 |Committers are bound by an Individual Contributor Agreement (the http://www.apache.org/licenses/icla.txt["Apache iCLA"]) that defines which code they are allowed to commit and how they need to identify code that is not their own. |icon:check[role=green] The project uses a repository managed by Apache Gitbox -- write access requires an Apache account, which requires an ICLA on file.
-|LC50 |The copyright ownership of everything that the project produces is clearly defined and documented. |All files in the source repository have appropriate headers which is enforced by tooling included in the build. ICLAs from all initial committers have been documented. CCLAs from all companies involved have been documented. SGA is on file for the initial contribution.
-|*Releases* 2+|icon:wrench[role=yellow]
-|RE10 |Releases consist of source code, distributed using standard and open archive formats that are expected to stay readable in the long term. |icon:check[role=green] https://dist.apache.org/repos/dist/release/plc4x/[Current source releases] are distributed via dist.apache.org and http://archive.apache.org/dist/incubator/plc4x/[Older source releases] are available from archive.apache.org. Both are linked from the http://plc4x.apache.org/users/download.html[website].
-|RE20 |Releases are approved by the project's PMC (see CS10), in order to make them an act of the Foundation. |icon:check[role=green] All incubating releases have been unanimously approved by the PLC4X community and the Incubator, all with at least 3 (P)PMC votes and more +1 than -1.
-|RE30 |Releases are signed and/or distributed along with digests that can be reliably used to validate the downloaded archives. |icon:check[role=green] All releases are signed, and the https://dist.apache.org/repos/dist/release/plc4x/KEYS[KEYS] file is provided on dist.apache.org
-|RE40 |Convenience binaries can be distributed alongside source code but they are not Apache Releases -- they are just a convenience provided with no guarantee. |icon:wrench[role=yellow] Convenience binaries are distributed via Maven Central Repository only. Currently due to the platform-dependency of C++ libraries, these are not distributed currently.
-|RE50 |The release process is documented and repeatable to the extent that someone new to the project is able to independently generate the complete set of artifacts required for a release. |icon:check[role=green] We have a guide for release managers, that has been tested by multiple release managers available on our http://plc4x.apache.org/developers/release/release.html[website].
-|*Quality* 2+|icon:check[role=green]
-|QU10 |The project is open and honest about the quality of its code. Various levels of quality and maturity for various modules are natural and acceptable as long as they are clearly communicated. |icon:check[role=green] All issues are documented in our https://issues.apache.org/jira/projects/PLC4X[JIRA] instance, which is our primary bug and issue tracker.
-|QU20 |The project puts a very high priority on producing secure software. |icon:check[role=green] even if we haven't received any security issues targeted at PLC4X yet, we proactively monitor our dependencies and if reported would treat them with the highest priority, according to the https://www.apache.org/security/committers.html[CVE/Security Advisory procedure].
-|QU30 |The project provides a well-documented, secure and private channel to report security issues, along with a documented way of responding to them. |icon:check[role=green] We are using Apaches default way to submit security related information, which is described on our http://plc4x.apache.org/users/security.html[website]
-|QU40 |The project puts a high priority on backwards compatibility and aims to document any incompatible changes and provide tools and documentation to help users transition to new features. |icon:check[role=green] We try to keep everything as backward compatible as possible. If we are forced to introduce incompatible changes, these is documented in a `Incompatible changes` section as part of our release notes.
-|QU50 |The project strives to respond to documented bug reports in a timely manner. |icon:check[role=green] Bug reports are treated with priority and are automatically posted to our developer mailing list https://lists.apache.org/list.html?dev@plc4x.apache.org so they are prominently recognised.
-|*Community* 2+|icon:check[role=green]
-|CO10 |The project has a well-known homepage that points to all the information required to operate according to this maturity model. |icon:check[role=green] The project website has a http://plc4x.apache.org/[description of the project] with technical details, http://plc4x.apache.org/developers/contributing.html[how to contribute], http://plc4x.apache.org/developers/team.html[team].
-|CO20 |The community welcomes contributions from anyone who acts in good faith and in a respectful manner and adds value to the project. |icon:check[role=green] So far we have recognized any form of contribution and every contributor with the desire to become part of the team has been invited to join.
-|CO30 |Contributions include not only source code, but also documentation, constructive bug reports, constructive discussions, marketing and generally anything that adds value to the project. |icon:check[role=green] It’s part of the http://plc4x.apache.org/developers/contributing.html[contribution guide] and the current committers are really keen to welcome contributions.
-|CO40 |The community is meritocratic and over time aims to give more rights and responsibilities to contributors who add value to the project. |icon:check[role=green] So far the community has elected 4 committers, all of them also being added to the PPMC.
-|CO50 |The way in which contributors can be granted more rights such as commit access or decision power is clearly documented and is the same for all contributors. |icon:check[role=green] The criteria is documented in the http://plc4x.apache.org/developers/contributing.html[contribution guide].
-|CO60 |The community operates based on consensus of its members (see CS10) who have decision power. Dictators, benevolent or not, are not welcome in Apache projects. |icon:check[role=green] The project works to build consensus. All votes have been unanimous so far.
-|CO70 |The project strives to answer user questions in a timely manner. |icon:check[role=green] Responses to reported issues or asked questions typically are handled by the community withing a matter of a few hours (Responses being faster during typical European time-zone business-hours).
-|*Consensus Building* 2+|icon:times[role=red]
-|CS10 |The project maintains a public list of its contributors who have decision power -- the project's PMC (Project Management Committee) consists of those contributors. |icon:check[role=green] All members of the team have been added on http://plc4x.apache.org/developers/team.html[team page].
-|CS20 |Decisions are made by consensus among PMC members 9 and are documented on the project's main communications channel. Community opinions are taken into account but the PMC has the final word if needed. |icon:check[role=green] All decisions are made on one of our mailing lists. Every decision discussed off-list has been taken back to the list for final discussion and we'll keep on doing that.
-|CS30 |Documented voting rules are used to build consensus when discussion is not sufficient. |icon:check[role=green] We have documented our decision-making rule on our http://plc4x.apache.org/developers/decisions.html[website].
-|CS40 |In Apache projects, vetoes are only valid for code commits and are justified by a technical explanation, as per the Apache voting rules defined in CS30. |icon:times[role=red] This part actively contradicts the voting rules of the Apache Incubator. This project follows the voting rules of the Apache Incubator which we documented on our http://plc4x.apache.org/developers/decisions.html[website].
-|CS50 |All "important" discussions happen asynchronously in written form on the project's main communications channel. Offline, face-to-face or private discussions 11 that affect the project are also documented on that channel. |icon:check[role=green] As mentioned in CS20 it is impossible to prevent off-list discussions when meeting in person. But we have always handled things in a way that we always write up summaries of important discussions and post them to the mailing lists.
-|*Independence* 2+|icon:check[role=green]
-|IN10 |The project is independent of any corporate or organizational influence. |icon:check[role=green] The group of active committers and PPMCs consists of members of more than independent 4 companies.
-|IN20 |Contributors act as themselves as opposed to representatives of a corporation or organization. |icon:check[role=green] While there are several cases where committers and PPMC members utilize corporate infrastructure or these companies, no case has been found where any of these committers and PPMCs have represented corporate interests.
-|=========================================================
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/preparing/index.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/preparing/index.adoc
deleted file mode 100644
index 460f2af..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/preparing/index.adoc
+++ /dev/null
@@ -1,75 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-
-== Preparing your Computer
-
-Building a project like Apache PLC4X on multiple target operating-systems is quite a challenge, but I think we managed to make it as simple as possible.
-
-We usually test the PLC4X build on the following systems:
-
-width=100%]
-|===
-| Operating System | CPU Architecture | Description
-| Linux            | x86_64           | Most computers
-| Linux            | aarch64          | Linux running on Macs with M processors (Paralells)
-| Windows          | x86_64           | Most computers
-| Windows          | aarch64          | Windows running on Macs with M processors (Paralells)
-| Mac              | x86_64           | Older Macs
-| Mac              | aarch64          | Newer Macs with M processors (Paralells)
-|===
-
-However, when building PLC4X there are some requirements the build is expecting you to have provided.
-These greatly depend on which parts you want to build.
-
-If you're just building the `Java` modules, these probably have the least demanding requirements.
-Also, should the `Go` parts generally work without any additional installations as the maven build should automatically pull the required packages.
-
-In order to build all Java parts of `PLC4X` you are required to have at least `Java 11` installed on your machine.
-
-TIP: We have tested the build with Java 11 up to Java 21 (Latest version at the time of writing this document).
-
-If a new version comes out, please give us a little time to verify and handle any related issues.
-We'll probably fix them as soon as possible.
-However, in the past with Oracle's new release strategy, there have been a few bumps on the road.
-
-Also will PLC4X build with any Maven version starting with `Maven 3.6.0`.
-
-[width=100%]
-|===
-| Profile        | Description                                              | Requirements
-|                | Builds Java API, drivers                                a|
-* Git
-* LibPCAP
-| `with-c`       | Builds C API, drivers                                   a|
-| `with-dotnet`  | Builds C# and .Net API, drivers                         a|
-* dotnet
-| `with-python`  | Builds Python API, drivers                              a|
-* python (min 3.7)
-* pyenv
-|===
-
-The following pages will describe how to provide these requirements for your operating system.
-
-* link:linux.html[Linux]
-* link:macos.html[MacOS]
-* link:windows.html[Windows]
-
-== Preparing your IDE
-
-=== IntelliJ
-
-When running Java unit-tests in IntelliJ, you might run into problems where during the test execution complaints arise that JUnit is unable to load `{failsafeArgLine}`. In this case you need to go to `Settings -> Build, Execution, Deployment -> Build Tools -> Maven -> Running Tests` and deselect the option `argLine`.
\ No newline at end of file
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/preparing/linux.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/preparing/linux.adoc
deleted file mode 100644
index 8492571..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/preparing/linux.adoc
+++ /dev/null
@@ -1,155 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-
-== Linux
-
-As tracking down issues which result from missing or outdated third party tools such as compilers are always hard do diagnose, we have extended the build of PLC4X with a `prerequisiteCheck` that automatically checks if required tools are installed and if a required minimum version is available.
-
-If any of the prerequisites are not met, the build fails with an error message that will help finding out what's wrong.
-
-The number of checks is highly dependent on which profiles are enabled.
-So for example the availability and version of the C compiler is only checked if the `with-c` profile is enabled.
-
-If the check is reporting any issues, please feel free to follow the corresponding steps in this guide to install the tools.
-
-=== Git
-
-Checking:
-
- git --version
-
-If you get any successful output, you probably don't need to do anything.
-
-Apt-based systems:
-
- sudo apt install git
-
-Yum based systems:
-
- sudo yum install git
-
-=== Java
-
-Checking:
-
- java --version
-
-If you get successful output indicating at least Java 11, you don't need to do anything.
-
-Apt based systems:
-
- sudo apt install openjdk-21-jdk
-
-=== Optional and other language support
-
-Git an Java should be all you need for building the Java part of PLC4X.
-
-==== LibPCAP (For raw-ethernet support)
-
-Apt-based systems:
-
- sudo apt install libpcap-dev
-
-Yum based systems:
-
- sudo yum install libpcap-devel
-
-Using libpcap usually requires root privileges, however the java process can be granted permission to do so by executing the following command.
-
- sudo setcap cap_net_raw,cap_net_admin=eip /path/to/java
-
-`/path/to/java` however needs to be a real file and not a symlink.
-So on my Ubuntu 22.04 system, where I installed java as described above the command is as follows:
-
- sudo setcap cap_net_raw,cap_net_admin=eip /usr/lib/jvm/java-21-openjdk-arm64/bin/java
-
-Sometimes I had to set the uid to execute the java executable with the permissions of the owner (root) ... however this is quite suboptimal solution.
-
- sudo chmod 4755 /path/to/java
-
-==== gcc (For PLC4C)
-
-NOTE: It seems that when running Linux on `aarch64` (Apple's Silicon Chips), that there are issues ... we're working on that. Feel free to watch https://github.com/apache/plc4x/issues/1582 on updates to this.
-
-Checking:
-
- gcc --version
-
-If you get any successful output, you probably don't need to do anything.
-
-Apt-based systems:
-
- sudo apt install gcc
-
-Yum based systems:
-
- sudo yum install gcc
-
-==== dotnet (For PLC4Net)
-
-Checking:
-
- dotnet --version
-
-If you get any successful output, you probably don't need to do anything.
-
-Microsoft has documented what is needed to install `.Net SDK` https://dotnet.microsoft.com/en-us/download[here]
-
-For Ubuntu this would be:
-
- wget -q https://packages.microsoft.com/config/ubuntu/22.04/packages-microsoft-prod.deb
- sudo dpkg -i packages-microsoft-prod.deb
- sudo apt install apt-transport-https
- sudo apt update
- sudo apt install dotnet-sdk-6.0
-
-For other distributions, please select the distribution in the drop-down menu and follow the instructions there.
-
-If, when checking the version again after installing, you are getting an error:
-
- A fatal error occurred. The folder [/usr/share/dotnet/host/fxr] does not exist
-
-Then please have a look at this Stackoverflow post (the accepted solution) https://stackoverflow.com/questions/73753672/a-fatal-error-occurred-the-folder-usr-share-dotnet-host-fxr-does-not-exist
-
-==== python (For PLC4Py)
-
-Checking:
-
- python3 --version
-
-If you get a version of 3.7 or higher reported, you probably don't need to do anything.
-
-Apt-based systems:
-
- sudo apt install python3
-
-Yum based systems:
-
- yum intall python3
-
-==== Python venv (For PLC4Py)
-
-Checking:
-
- python3 -Im ensurepip
-
-If you are getting anything else than a: `No module named ensurepip`, you're ok.
-It seems that this manually needs to be installed on some systems.
-
-Apt-based systems:
-
- sudo apt install python3-venv
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/preparing/macos.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/preparing/macos.adoc
deleted file mode 100644
index d61bc26..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/preparing/macos.adoc
+++ /dev/null
@@ -1,123 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-
-== Mac OS
-
-As tracking down issues which result from missing or outdated third party tools such as compilers are always hard do diagnose, we have extended the build of PLC4X with a `prerequisiteCheck` that automatically checks if required tools are installed and if a required minimum version is available.
-
-If any of the prerequisites are not met, the build fails with an error message that will help finding out what's wrong.
-
-The number of checks is highly dependent on which profiles are enabled.
-So for example the availability and version of the C compiler is only checked if the `with-c` profile is enabled.
-
-Most libraries on Mac are installed using `Homebrew`.
-
-Make sure `Homebrew` ist installed in order to install most of these.
-
-    /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
-
-=== Git
-
-Checking:
-
- git --version
-
-If you get any successful output, you probably don't need to do anything.
-
-If you are running this command on a really fresh and clean system, it might be that you are asked to finish installing the XCode commandline tools.
-If this happens, just follow the process and re-try after it has finished.
-
-If you get a response that indicates that git needs to be installed, please execute the following command:
-
- brew install git
-
-=== Java
-
-Checking:
-
- java --version
-
-If you get successful output indicating at least Java 11, you don't need to do anything.
-
-Apt based systems:
-
- brew install openjdk
-
-=== Optional and other language support
-
-Git an Java should be all you need for building the Java part of PLC4X.
-
-==== LibPCAP (For raw-ethernet support)
-
-The libpcap version bundled with macOS is currently 1.9.1.
-This version causes exceptions.
-So it's best to update to a newer version using brew:
-
-   brew install libpcap
-
-==== gcc (For PLC4C)
-
-Checking:
-
- gcc --version
-
-If you get any successful output, you probably don't need to do anything.
-
-It seems macOS comes with a version of gcc which is good enough for our use cases.
-
-==== dotnet (For PLC4Net)
-
-Checking:
-
- dotnet --version
-
-If you get any successful output, you probably don't need to do anything.
-
-Microsoft is offering an installer for macOS which is available from https://dotnet.microsoft.com/download/dotnet-core/2.2[here].
-
-Alternatively you can also install it via homebrew:
-
- brew install --cask dotnet-sdk
-
-==== python (For PLC4Py)
-
-Checking:
-
- python --version
-
-If you get a version of 3.0.0 or higher reported, you probably don't need to do anything.
-
-In order to install it, please execute the following command:
-
- brew install pyenv
-
-Then use pyenv to install python:
-
- pyenv install 3.9.13
-
-Then set this as the global python version:
-
- pyenv global 3.9.13
-
-And add pyenv to the PATH:
-
- echo -e 'if command -v pyenv 1>/dev/null 2>&1; then\n  eval "$(pyenv init -)"\nfi' >> ~/.zshrc
- echo -e 'if command -v pyenv 1>/dev/null 2>&1; then\n  eval "$(pyenv init -)"\nfi' >> ~/.bash_profile
-
-After opening a new terminal, `python` should be configured
-
- python --version
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/preparing/windows.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/preparing/windows.adoc
deleted file mode 100644
index f602b1c..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/preparing/windows.adoc
+++ /dev/null
@@ -1,122 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-
-== Windows
-
-As tracking down issues which result from missing or outdated third party tools such as compilers are always hard do diagnose, we have extended the build of PLC4X with a `prerequisiteCheck` that automatically checks if required tools are installed and if a required minimum version is available.
-
-If any of the prerequisites are not met, the build fails with an error message that will help finding out what's wrong.
-
-The number of checks is highly dependent on which profiles are enabled.
-So for example the availability and version of the C compiler is only checked if the `with-c` profile is enabled.
-
-As in the past keeping the documentation up to date has been quite challenging, as the projects providing and packaging some of the needed tools have been born and dying like weed, we'll start using Chocolatey as something similar to Homebrew on Mac or Apt on Linux.
-
-So first be sure to install Chocolatey from here: https://community.chocolatey.org/ and follow the most recent instructions on that page in order to install it.
-
-=== Git
-
-Checking:
-
- git --version
-
-If you get any successful output, you probably don't need to do anything.
-
-If above command is not successful, simply install it via Chocolatey:
-
- choco install git
-
-=== Java
-
-Checking:
-
- java --version
-
-If you get successful output, check that the version reported is at least Java 11.
-If you need to install or update Java, unfortunately this doesn't seem to be available via Chocolatey, but needs to be installed directly from a distribution.
-
-For Oracles OpenJDK 21 this would be from here: https://learn.microsoft.com/de-de/java/openjdk/download
-If you are using a Windows VM on `aarch64` (Apple M1 or M2 virtual machine), the download available from Microsoft build seem to be one of the few options you have. When installing make sure to select the option to configure the "JAVA_HOME" environment variable (deactivated per default).
-
-=== Optional and other language support
-
-Git an Java should be all you need for building the Java part of PLC4X.
-
-==== LibPCAP (For raw-ethernet support)
-
-In order to use the raw ethernet transport capabilities of PLC4X, we need to ensure the NPcap library is installed.
-
-In order to check if NPcap is installed, check the following directories:
-
-64-bit versions:
-
-- C:\Windows\System32\packet.dll
-- C:\Windows\System32\wpcap.dll
-
-32-bit versions:
-
-- C:\Windows\SysWOW64\packet.dll
-- C:\Windows\SysWOW64\wpcap.dll
-
-If none of these can be found, install it by downloading the installer from https://npcap.com/#download
-
-==== gcc (For PLC4C)
-
-Checking:
-
- gcc --version
-
-If you get any successful output, you probably don't need to do anything.
-
-If above command fails, please install MinGW from an Administrative console with the following command:
-
- choco install mingw
-
-https://repo.maven.apache.org/maven2/com/googlecode/cmake-maven-project/cmake-binaries/3.27.7-b1/
-Download:
-https://repo.maven.apache.org/maven2/com/googlecode/cmake-maven-project/cmake-binaries/3.27.7-b1/cmake-binaries-3.27.7-b1-windows-arm_64.jar
-Deploy as:
-https://repo.maven.apache.org/maven2/com/googlecode/cmake-maven-project/cmake-binaries/3.27.7-b1/cmake-binaries-3.27.7-b1-windows-arm64.jar
-
-==== dotnet (For PLC4Net)
-
-Checking:
-
- dotnet --version
-
-If you get any successful output, you probably don't need to do anything.
-
-Usually this is already installed on Windows machines.
-
-Download the installer from https://dotnet.microsoft.com/en-us/download[here]
-
-==== python (For PLC4Py)
-
-Checking:
-
- python --version
-
-If you get any successful output, you probably don't need to do anything.
-
-You can get Python from https://www.python.org/downloads/windows/[here].
-
-Make sure directory containing `python.exe` is added to your systems `PATH`.
-Also make sure you restarted your IDE and or console window after changing the `PATH` settings for the changes to take effect.
-
-https://visualstudio.microsoft.com/de/visual-cpp-build-tools/
-
-PLC4PY Build doesn't work on Aarch64 on Windows
\ No newline at end of file
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/protocols/ads/protocol.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/protocols/ads/protocol.adoc
deleted file mode 100644
index d71aa79..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/protocols/ads/protocol.adoc
+++ /dev/null
@@ -1,198 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-
-== Beckhoff ADS Protocol
-
-// https://plantuml.com/de/activity-diagram-legacy
-// https://deepu.js.org/svg-seq-diagram/Reference_Guide.pdf
-
-[plantuml,ads-statemachine,svg,opts="inline",svg-type="inline"]
-----
-@startuml
-
-(*) --> Connect
-
-partition "Connected" #EEEEEE {
-    ===Connected=== -->[API Browse Request] Browse
-    ===Connected=== -->[API Read Request] Read
-    ===Connected=== -->[API Write Request] Write
-    ===Connected=== -->[API Subscription Request] Subscribe
-    ===Connected=== -->[API Unsubscription Request] Unsubscribe
-}
-
-partition Connect #EEEECC {
-    (*) --> "initializing"
-    if "Using Authentication?" then
-        -->[true] "Send 'Add Or Update AMS Routes'"
-    else
-        -->[false] "Send 'ADS Read Device Info'"
-    endif
-    "Send 'Add Or Update AMS Routes'" ..> "Receive 'Add Or Update AMS Routes'"
-    "Receive 'Add Or Update AMS Routes'" --> "Send 'ADS Read Device Info'"
-    "Send 'ADS Read Device Info'" ..> "Receive 'ADS Read Device Info'"
-    if "Config: Monitor PLC changes?" then
-        -->[true] "Init Read Online and Offline Version"
-    else
-        -->[false] "Reset Symbol and Data-Type Data"
-    endif
-    "Init Read Online and Offline Version" --> "Send 'Read Online-Version (Symbolic)'"
-    "Init Read Online and Offline Version" --> "Send 'Read Offline-Version'"
-    "Send 'Read Online-Version (Symbolic)'" ..> "Receive 'Read Online-Version (Symbolic)'"
-    "Receive 'Read Online-Version (Symbolic)'" --> ===OnlineAndOfflineVersionRead===
-    "Send 'Read Offline-Version'" ..> "Receive 'Read Offline-Version'"
-    "Receive 'Read Offline-Version'" --> ===OnlineAndOfflineVersionRead===
-    ===OnlineAndOfflineVersionRead=== --> "Reset Symbol and Data-Type Data"
-    if "Config: Load Symbol- and Data-Type-Tables?" then
-        -->[true] "Send 'Read Symbol- and Data-Type-Table sizes'"
-    else
-        -->[false] ===FinishedReadingSymbolAndDataTypeTable===
-    endif
-    "Send 'Read Symbol- and Data-Type-Table sizes'" ..> "Receive 'Read Symbol- and Data-Type-Table sizes'"
-    "Receive 'Read Symbol- and Data-Type-Table sizes'" --> "Send 'Read Data-Type-Table'"
-    "Send 'Read Data-Type-Table'" ..> "Receive 'Read Data-Type-Table'"
-    "Receive 'Read Data-Type-Table'" --> ===FinishedReadingSymbolAndDataTypeTable===
-    "Receive 'Read Symbol- and Data-Type-Table sizes'" --> "Send 'Read Symbol-Table'"
-    "Send 'Read Symbol-Table'" ..> "Receive 'Read Symbol-Table'"
-    "Receive 'Read Symbol-Table'" --> ===FinishedReadingSymbolAndDataTypeTable===
-    if "Config: Monitor PLC changes?" then
-        -right->[true] "Subscribe to changes to the Online- and Offline Version"#EECCEE
-    endif
-    "Subscribe to changes to the Online- and Offline Version" ..>[Update the online- or offline version (Depending on wich one changed)] "Reset Symbol and Data-Type Data"
-    ===FinishedReadingSymbolAndDataTypeTable=== --> ===Connected===
-}
-
-partition Browse #CCCCEE {
-    "Browse" --> ===BrowseStart===
-    if "Is symbol- and data-type-table loaded?" then
-        -->[true] ===BrowseFinishedReadingSymbolAndDataTypeTable===
-    else
-        -->[false] "Browse: Send 'Read Symbol- and Data-Type-Table sizes'"
-        "Browse: Send 'Read Symbol- and Data-Type-Table sizes'" ..> "Browse: Receive 'Read Symbol- and Data-Type-Table sizes'"
-        "Browse: Receive 'Read Symbol- and Data-Type-Table sizes'" --> "Browse: Send 'Read Data-Type-Table'"
-        "Browse: Send 'Read Data-Type-Table'" ..> "Browse: Receive 'Read Data-Type-Table'"
-        "Browse: Receive 'Read Data-Type-Table'" --> ===BrowseFinishedReadingSymbolAndDataTypeTable===
-        "Browse: Receive 'Read Symbol- and Data-Type-Table sizes'" --> "Browse: Send 'Read Symbol-Table'"
-        "Browse: Send 'Read Symbol-Table'" ..> "Browse: Receive 'Read Symbol-Table'"
-        "Browse: Receive 'Read Symbol-Table'" --> ===BrowseFinishedReadingSymbolAndDataTypeTable===
-    endif
-    ===BrowseFinishedReadingSymbolAndDataTypeTable=== --> "Return API Browse Result"
-    "Return API Browse Result" --> ===Connected===
-}
-
-partition Read #CCEECC {
-    "Read" --> ===ReadStart===
-    if "Is single item read request?" then
-        -->[false] if "Are all field addresses resolved?" then
-            -->[unresolved] "Read: Send 'Multi Item Address Resolution' for unresolved"
-            "Read: Send 'Multi Item Address Resolution' for unresolved" ..> "Read: Receive 'Multi Item Address Resolution' for unresolved"
-            "Read: Receive 'Multi Item Address Resolution' for unresolved" --> ===ReadAllItemsResolved===
-        else
-            -->[resolved] ===ReadAllItemsResolved===
-        endif
-        ===ReadAllItemsResolved=== --> "Read: Send 'Multi Item Read'"
-        "Read: Send 'Multi Item Read'" ..> "Read: Receive 'Multi Item Read'"
-        "Read: Receive 'Multi Item Read'" --> "Read: Return API Read Result"
-    else
-        -->[true] if "Is the field address resolved?" then
-            -->[false] "Read: Send 'Single Item Address Resolution'"
-            "Read: Send 'Single Item Address Resolution'" ..> "Read: Receive 'Single Item Address Resolution'"
-            "Read: Receive 'Single Item Address Resolution'" --> "Read: Send 'Single Item Read'"
-        else
-            -->[true] "Read: Send 'Single Item Read'"
-        endif
-        "Read: Send 'Single Item Read'" ..> "Read: Receive 'Single Item Read'"
-        "Read: Receive 'Single Item Read'" --> "Read: Return API Read Result"
-    endif
-    "Read: Return API Read Result" --> ===Connected===
-}
-
-partition Write #EECCCC {
-    "Write" --> ===WriteStart===
-    if "Is single item write request?" then
-        -->[false] if "Are all field addresses resolved?" then
-            -->[unresolved] "Write: Send 'Multi Item Address Resolution' for unresolved"
-            "Write: Send 'Multi Item Address Resolution' for unresolved" ..> "Write: Receive 'Multi Item Address Resolution' for unresolved"
-            "Write: Receive 'Multi Item Address Resolution' for unresolved" --> ===WriteAllItemsResolved===
-        else
-            -->[resolved] ===WriteAllItemsResolved===
-        endif
-        ===WriteAllItemsResolved=== --> "Write: Send 'Multi Item Write'"
-        "Write: Send 'Multi Item Write'" ..> "Write: Receive 'Multi Item Write'"
-        "Write: Receive 'Multi Item Write'" --> "Write: Return API Write Result"
-    else
-        -->[true] if "Is the field address resolved?" then
-            -->[false] "Write: Send 'Single Item Address Resolution'"
-            "Write: Send 'Single Item Address Resolution'" ..> "Write: Receive 'Single Item Address Resolution'"
-            "Write: Receive 'Single Item Address Resolution'" --> "Write: Send 'Single Item Write'"
-        else
-            -->[true] "Write: Send 'Single Item Write'"
-        endif
-        "Write: Send 'Single Item Write'" ..> "Write: Receive 'Single Item Write'"
-        "Write: Receive 'Single Item Write'" --> "Write: Return API Write Result"
-    endif
-    "Write: Return API Write Result" --> ===Connected===
-}
-
-partition Subscribe #EECCEE {
-    "Subscribe" --> ===SubscribeStart===
-    if "Is single item subscription request?" then
-        -->[false] if "Are all field addresses resolved?" then
-            -->[unresolved] "Subscribe: Send 'Multi Item Address Resolution' for unresolved"
-            "Subscribe: Send 'Multi Item Address Resolution' for unresolved" ..> "Subscribe: Receive 'Multi Item Address Resolution' for unresolved"
-            "Subscribe: Receive 'Multi Item Address Resolution' for unresolved" --> ===SubscribeAllItemsResolved===
-        else
-            -->[resolved] ===SubscribeAllItemsResolved===
-        endif
-    else
-        -->[true] if "Is the field address resolved?" then
-            -->[false] "Subscribe: Send 'Single Item Address Resolution'"
-            "Subscribe: Send 'Single Item Address Resolution'" ..> "Subscribe: Receive 'Single Item Address Resolution'"
-            "Subscribe: Receive 'Single Item Address Resolution'" --> ===SubscribeAllItemsResolved===
-        else
-            -->[true] ===SubscribeAllItemsResolved===
-        endif
-        ===SubscribeAllItemsResolved=== --> "Subscribe: Send 'Single Item 1 Subscibe'"
-        "Subscribe: Send 'Single Item 1 Subscibe'" ..> "Subscribe: Receive 'Single Item 1 Subscibe'"
-        "Subscribe: Receive 'Single Item 1 Subscibe'" --> ===SubscribeAllItemsSubscribed===
-        ===SubscribeAllItemsResolved=== --> "Subscribe: Send 'Single Item 2 Subscibe'"
-        "Subscribe: Send 'Single Item 2 Subscibe'" ..> "Subscribe: Receive 'Single Item 2 Subscibe'"
-        "Subscribe: Receive 'Single Item 2 Subscibe'" --> ===SubscribeAllItemsSubscribed===
-        ===SubscribeAllItemsResolved=== --> "Subscribe: Send 'Single Item n Subscibe'"
-        "Subscribe: Send 'Single Item n Subscibe'" ..> "Subscribe: Receive 'Single Item n Subscibe'"
-        "Subscribe: Receive 'Single Item n Subscibe'" --> ===SubscribeAllItemsSubscribed===
-        ===SubscribeAllItemsSubscribed=== --> "Subscribe: Return API Write Result"
-    endif
-    "Subscribe: Return API Write Result" --> ===Connected===
-}
-
-partition Unsubscribe #LightSkyBlue {
-    "Unsubscribe" --> ===UnsubscribeStart===
-    ===UnsubscribeStart=== --> "Unsubscribe: Send 'Single Item 1 Unsubscribe'"
-    "Unsubscribe: Send 'Single Item 1 Unsubscribe'" ..> "Unsubscribe: Receive 'Single Item 1 Unsubscribe'"
-    "Unsubscribe: Receive 'Single Item 1 Unsubscribe'" --> ===UnsubscribeAllItemsUnsubscribed===
-    ===UnsubscribeStart=== --> "Unsubscribe: Send 'Single Item 2 Unsubscribe'"
-    "Unsubscribe: Send 'Single Item 2 Unsubscribe'" ..> "Unsubscribe: Receive 'Single Item 2 Unsubscribe'"
-    "Unsubscribe: Receive 'Single Item 2 Unsubscribe'" --> ===UnsubscribeAllItemsUnsubscribed===
-    ===UnsubscribeStart=== --> "Unsubscribe: Send 'Single Item n Unsubscribe'"
-    "Unsubscribe: Send 'Single Item n Unsubscribe'" ..> "Unsubscribe: Receive 'Single Item n Unsubscribe'"
-    "Unsubscribe: Receive 'Single Item n Unsubscribe'" --> ===UnsubscribeAllItemsUnsubscribed===
-    ===UnsubscribeAllItemsUnsubscribed=== --> "Unsubscribe: Return API Unsubscribe Result"
-    "Unsubscribe: Return API Unsubscribe Result" --> ===Connected===
-}
-
-@enduml
-----
\ No newline at end of file
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/protocols/eip/protocol.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/protocols/eip/protocol.adoc
deleted file mode 100644
index 1cf6bbb..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/protocols/eip/protocol.adoc
+++ /dev/null
@@ -1,132 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-
-== EIP Protocol
-
-// https://plantuml.com/de/activity-diagram-legacy
-// https://deepu.js.org/svg-seq-diagram/Reference_Guide.pdf
-
-[plantuml,eip-statemachine,svg,opts="inline",svg-type="inline"]
-----
-@startuml
-
-(*) --> Connect
-
-partition "Connected" #EEEEEE {
-    ===Connected=== -->[API Browse Request] Browse
-    ===Connected=== -->[API Read Request] Read
-    ===Connected=== -->[API Write Request] Write
-    ===Connected=== -->[API Subscription Request] Subscribe
-    ===Connected=== -->[API Unsubscription Request] Unsubscribe
-    ===Connected=== -->[API Disconnect Request] Disconnect
-}
-
-partition Connect #EEEECC {
-    (*) --> "initializing"
-    "initializing" --> "Send ListServices request"
-    "Send ListServices request" ..> "Receive ListServices response"
-    "Receive ListServices response" -->[If successfull, extract 'CIP encapsulation support' setting] "Send EipConnectionRequest request"
-    "Send EipConnectionRequest request" ..> "Receive EipConnectionRequest response"
-    if "Response is an EipConnectionResponse"?
-        -->[true] "Send GetAllAttributes request"
-    else
-        -->[false] "Send OpenConnectionManager request"
-    endif
-    "Send GetAllAttributes request" ..> "Receive GetAllAttributes response"
-    if "Extract setting for 'useMessageRouter' and 'useConnectionManager'. If useConnectionManager"
-        -->[true] "Send OpenConnectionManager request"
-    else
-        -->[false] ===Connected===
-    endif
-    "Send OpenConnectionManager request" ..> "Receive OpenConnectionManager response"
-    "Receive OpenConnectionManager response" --> ===Connected===
-}
-
-partition Disconnect #EECCCC {
-    "Disconnect" --> ===DisconnectStart===
-    if "connectionId != 0"
-        -->[true] "Send ConnectionManagerClose request"
-    else
-        -->[false] "Send Disconnect request"
-    endif
-    "Send ConnectionManagerClose request" ..> "Receive ConnectionManagerClose response"
-    "Receive ConnectionManagerClose response" --> "Send Disconnect request"
-    "Send Disconnect request" ..> "Receive Disconnect response"
-    "Receive Disconnect response" --> ===Disconnected===
-}
-
-partition Browse #CCCCEE {
-    "Browse" --> ===BrowseStart===
-    ===BrowseStart=== --> ===Connected===
-}
-
-partition Read #CCEECC {
-    "Read" --> ===ReadStart===
-    if "useMessageRouter"
-        if "useConnectionManager"
-            -->[true] "readWithConnectionManager"
-        else
-            -->[false] "readWithoutConnectionManager"
-        endif
-    else
-        -->[false] "readWithoutMessageRouter"
-    endif
-    "readWithConnectionManager" --> "Send SendUnitData request"
-    "Send SendUnitData request" ..> "Receive SendUnitData response"
-    "Receive SendUnitData response" --> ===Connected===
-    "readWithoutConnectionManager" --> "Send CipRRData request"
-    "Send CipRRData request" ..> "Receive CipRRData response"
-    "Receive CipRRData response" --> ===Connected===
-    "readWithoutMessageRouter" --> "Send unconnected CipReadRequest request for each tag"
-    "Send unconnected CipReadRequest request for each tag" ..> "Receive unconnected CipReadRequest response"
-    "Receive unconnected CipReadRequest response" --> ===Connected===
-}
-
-partition Write #EECCCC {
-    "Write" --> ===WriteStart===
-    if "useMessageRouter"
-        if "useConnectionManager"
-            -->[true] "writeWithConnectionManager"
-        else
-            -->[false] "writeWithoutConnectionManager"
-        endif
-    else
-        -->[false] "writeWithoutMessageRouter"
-    endif
-    "writeWithConnectionManager" --> "Send SendUnitData request"
-    "Send SendUnitData request" ..> "Receive SendUnitData response"
-    "Receive SendUnitData response" --> ===Connected===
-    "writeWithoutConnectionManager" --> "Send CipRRData request"
-    "Send CipRRData request" ..> "Receive CipRRData response"
-    "Receive CipRRData response" --> ===Connected===
-    "writeWithoutMessageRouter" --> "Send unconnected CipWriteRequest request for each tag"
-    "Send unconnected CipWriteRequest request for each tag" ..> "Receive unconnected CipWriteRequest response"
-    "Receive unconnected CipWriteRequest response" --> ===Connected===
-}
-
-partition Subscribe #EECCEE {
-    "Subscribe" --> ===SubscribeStart===
-    ===SubscribeStart=== --> ===Connected===
-}
-
-partition Unsubscribe #LightSkyBlue {
-    "Unsubscribe" --> ===UnsubscribeStart===
-    ===UnsubscribeStart=== --> ===Connected===
-}
-
-@enduml
-----
\ No newline at end of file
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/protocols/index.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/protocols/index.adoc
deleted file mode 100644
index c3aa351..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/protocols/index.adoc
+++ /dev/null
@@ -1,23 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-
-== Usage of protocols
-
-=== Currently documented are:
-
-- link:ads/protocol.html[Beckhoff/ ADS]
-- link:eip/protocol.html[EIP]
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/release/build-tools.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/release/build-tools.adoc
deleted file mode 100644
index 4375c95..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/release/build-tools.adoc
+++ /dev/null
@@ -1,397 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-:imagesdir: ../../images/
-:icons: font
-
-== Releasing PLC4X Build-Tools
-
-In contrast to the main project, the `plc4x-build-tools` repository contains a loose collection of sub-projects.
-
-The main `pom.xml` in the root directory is mainly for allowing to import all modules into an IDE and shouldn't be used for releases.
-
-If you want to release a part of the build-tools, please execute the following release steps in the parts sub-directory.
-
-In general the preparation steps for releasing a build-tool is equal to those of the main project.
-So please check link:release.html[here] (Chapters: `Preparing your system for being able to release` and `Preparing the codebase for a release`)
-
-The rest of the steps are a lot simpler than those of the main project as there aren't any profiles involved.
-
-=== Creating a release branch (For the code-generation module)
-
-According to SemVer, we have: Major, Minor and Bugfix releases.
-
-For each new Major and Minor release we create a new branch at the beginning of a code-freeze phase.
-
-So if currently the project version in develop is `{code-generation-full-version}-SNAPSHOT`, we create a branch `release/{code-generation-short-version}`.
-
-When creating the branch is exactly the moment in which the version in `develop` is incremented to the next minor version.
-
-This can and should be automated by the `maven-release-plugin`.
-
-Per default the plugin will ask for the working copy version during the build execution.
-This is the version the `develop` branch will be changed to.
-
-   mvn release:branch -DbranchName=releases/code-generation/{minor-version}
-
-Per default the plugin suggests the next bugfix version as working version, however we want it to use the next minor version.
-So in case of preparing the release branch for `{code-generation-full-version}` the command would be the following:
-
-[subs="verbatim,attributes"]
-----
-   mvn release:branch -DbranchName=releases/code-generation/{code-generation-short-version}
-----
-
-The plugin will then aks for the version:
-
-[subs="verbatim,attributes"]
-----
-   What is the new working copy version for "PLC4X Build Tools: Code Generation"? (org.apache.plc4x.plugins:plc4x-code-generation) {code-generation-bugfix-version}-SNAPSHOT: : {code-generation-development-version}-SNAPSHOT
-----
-
-Where the suggested default is manually overridden.
-
-This step now should perform quite quickly as no build and no tests are involved.
-
-However in the end the versions of the `develop` branch are updated and a new `releases/code-generation/{code-generation-short-version}` branch is created.
-
-=== Preparing `develop` for the next iteration
-
-Now is a good time to add a new section to the `RELEASE_NOTES` document for the new `SNAPSHOT` version.
-
-Here comes a template:
-
-[subs="verbatim,attributes"]
-----
-==============================================================
-(Unreleased) Apache PLC4X {code-generation-development-version}-SNAPSHOT
-==============================================================
-
-New Features
-------------
-
-Incompatible changes
---------------------
-
-Bug Fixes
----------
-
-// Rest of the file
-
-----
-
-After that please remove the `(Unreleased)` from the following section, as we are currently working on its release.
-
-Also be sure to do a quick full-text-search to check if the version was updated correctly everywhere.
-
-WARNING: If you find anything here, you will need to pay attention during the release.
-
-=== Release stabilization phase
-
-Now usually comes a phase in which last tests and checks should be performed.
-
-If any problems are found they, have to be fixed in the release branch.
-
-Changes should either be re applied in `develop` or `cherry-picked`, however merging things back can cause a lot of problems, and we no longer have the same versions.
-
-=== Preparing a release
-
-Before you start preparing the release, it is important to manually make the `RELEASE_NOTES` reflect the version we are planning on releasing.
-
-NOTE: Be sure to ensure you have switched to the release branch before continuing.
-
-So be sure to remove the `(Unreleased)` and `SNAPSHOT` from the version.
-
-As especially when switching a lot between different branches, it is recommended to do a clean checkout of the repository.
-Otherwise, a lot of directories can be left over, which would be included in the source-release zip.
-In order to prepare a release-candidate, the first step is switching to the corresponding release-branch.
-
-NOTE: Again, just in case you missed the first warning: Be sure to ensure you have switched to the release branch before continuing.
-
-After that, the following command will to all preparation steps for the release:
-
-   mvn release:prepare
-
-In general the plugin will now ask you 3 questions:
-
-1. The version we want to release as (It will suggest the version you get by omitting the `-SNAPSHOT` suffix, keep it as it is)
-2. The name of the tag the release commit will be tagged with in the SCM (Name it `releases/code-generation/{release-version}` (`releases/code-generation/{code-generation-full-version}` in our case)
-3. The next development version (The version present in the pom after the release) (leave it as it is suggested by the plugin)
-
-Usually for 1 and 3 the defaults are just fine, make sure the tag name is correct as this usually is different.
-
-However, it is important to check that nowhere else SNAPSHOT versions are referenced.
-
-What the plugin now does, is automatically to execute the following operations:
-
-1. Check we aren't referencing any `SNAPSHOT` dependencies.
-2. Update all pom versions to the release version.
-3. Run a build with all tests
-4. Commit the changes (commit message: `[maven-release-plugin] prepare release releases/code-generation/{code-generation-full-version}`)
-5. Push the commit
-6. Tag the commit
-7. Update all poms to the next development version.
-8. Commit the changes (commit message: `[maven-release-plugin] prepare for next development iteration`)
-9. Push the commit
-
-However, this just prepared the git repository for the release, we have to perform the release to produce and stage the release artifacts.
-
-Please verify the git repository at: https://gitbox.apache.org/repos/asf?p=plc4x-build-tools.git
-is in the correct state. Please select the release branch and verify the commit log looks similar to this
-
-image::release-git-history.png[]
-
-It is important that the commit with the message "[maven-release-plugin] prepare release releases/code-generation/{code-generation-full-version}" is tagged with the release tag (in this case releases/code-generation/{code-generation-full-version})
-
-If you check the commit itself, it should mainly consist of version updates like this:
-
-image::release-git-diff-prepare-release.png[]
-
-The root pom has a few more changes, but in general this should be what you are seeing.
-
-After that should come a second commit:
-
-image::release-git-diff-next-development-iteration.png[]
-
-This now updates the versions again, but this time from the release version to the one we selected for the next development iteration (in this case `{code-generation-bugfix-version}-SNAPSHOT`)
-
-NOTE: If the commit history doesn't look like this, something went wrong.
-
-== What if something goes wrong?
-
-If something goes wrong, you can always execute:
-
-   mvn release:rollback
-
-And it will change the versions back and commit and push things.
-
-However, it will not delete the tag in GIT (locally and remotely). So you have to do that manually or use a different tag next time.
-
-=== Performing a release
-
-This is done by executing another goal of the `maven-release-plugin`:
-
-   mvn release:perform
-
-This executes automatically as all information it requires is located in the `release.properties` file the `prepare`-goal prepared.
-
-The first step is that the `perform`-goal checks out the previously tagged revision into the root modules `target/checkout` directory.
-Here it automatically executes a maven build (You don't have to do this, it's just that you know what's happening):
-
-   mvn clean deploy -P apache-release
-
-As the `apache-release` profile is activated, this builds and tests the project as well as creates the JavaDocs, Source packages and signs each of these with your PGP key.
-
-As this time the build is building with release versions, Maven will automatically choose the release url for deploying artifacts.
-
-The way things are set up in the apache parent pom, is that release artifacts are deployed to a so-called `staging repository`.
-
-You can think of a `staging repository` as a dedicated repository created on the fly as soon as the first artifact comes in.
-
-After the build you will have a nice and clean Maven repository at https://repository.apache.org/ that contains only artifacts from the current build.
-
-After the build it is important to log in to `Nexus` at https://repository.apache.org/, select `Staging Repositories` and find the repository with the name: `orgapacheplc4x-{somenumber}`.
-
-Select that and click on the `Close` button.
-
-Now Nexus will do some checks on the artifacts and check the signatures.
-
-As soon as it's finished, we are done on the Maven side and ready to continue with the rest of the release process.
-
-A release build also produces a so-called `source-assembly` zip.
-
-This contains all sources of the project and will be what's actually the release from an Apache point of view and will be the thing we will be voting on.
-
-This file will also be signed and `SHA512` hashes will be created.
-
-=== Staging a release
-
-Each new release and release-candidate has to be staged in the Apache SVN under:
-
-https://dist.apache.org/repos/dist/dev/plc4x/
-
-The directory structure of this directory is as follows:
-
-[subs="verbatim,attributes"]
-----
-   ./KEYS
-   ./build-tools/code-generation/{code-generation-full-version}
-   ./build-tools/code-generation/{code-generation-full-version}/rc1
-   ./build-tools/code-generation/{code-generation-full-version}/rc1/README
-   ./build-tools/code-generation/{code-generation-full-version}/rc1/RELEASE_NOTES
-   ./build-tools/code-generation/{code-generation-full-version}/rc1/apache-plc4x-code-generation-{code-generation-full-version}-source-release.zip
-   ./build-tools/code-generation/{code-generation-full-version}/rc1/apache-plc4x-code-generation-{code-generation-full-version}-source-release.zip.asc
-   ./build-tools/code-generation/{code-generation-full-version}/rc1/apache-plc4x-code-generation-{code-generation-full-version}-source-release.zip.sha512
-----
-
-I usually prepare exactly the same directory structure, starting with the {code-generation-full-version} locally and then just import everything using the following command:
-
-[subs="verbatim,attributes"]
-----
-svn import {code-generation-full-version} https://dist.apache.org/repos/dist/dev/plc4x/build-tools/code-generation/{code-generation-full-version} -m"Staging of rc1 of PLC4X Build-Tools (Code-Generation) {code-generation-full-version}"
-----
-
-The `KEYS` file contains the PGP public key which belongs to the private key used to sign the release artifacts.
-
-If this is your first release be sure to add your key to this file.
-For the format have a look at the file itself.
-It should contain all the information needed.
-
-Be sure to stage exactly the `README` and `RELEASE_NOTES` files contained in the root of your project.
-Ideally you just copy them there from there.
-
-The three `*-source-release.zip*` artifacts should be located in the directory: `code-generation/target/checkout/code-generation/target`
-
-So, after committing these files to SVN, you are ready to start the vote.
-
-=== Starting a vote on the mailing list
-
-After staging the release candidate in the Apache SVN, it is time to actually call out the vote.
-
-For this we usually send two emails.
-The following would be the one used to do our first TLP release:
-
-[subs="verbatim,attributes"]
-----
-   E-Mail Topic:
-   [VOTE] Apache PLC4X Build-Tools Code-Generation {code-generation-full-version} RC1
-
-   Message:
-   Apache PLC4X Build-Tools Code-Generation {code-generation-full-version} has been staged under [2]
-   and it’s time to vote on accepting it for release.
-
-   All Maven artifacts are available under [1]. Voting will be open for 72hr.
-
-   A minimum of 3 binding +1 votes and more binding +1 than binding -1
-   are required to pass.
-
-   Repository: https://gitbox.apache.org/repos/asf/plc4x-build-tools.git
-   Release tag: releases/code-generation/{code-generation-full-version}
-   Hash for the release tag: {replacethiswiththerealgitcommittag}
-
-   Per [3] "Before voting +1 PMC members are required to download
-   the signed source code package, compile it as provided, and test
-   the resulting executable on their own platform, along with also
-   verifying that the package meets the requirements of the ASF policy
-   on releases."
-
-   You can achieve the above by following [4].
-
-   [ ]  +1 accept (indicate what you validated - e.g. performed the non-RM items in [4])
-   [ ]  -1 reject (explanation required)
-
-
-   [1] https://repository.apache.org/content/repositories/orgapacheplc4x-{somefourdigitnumber}
-   [2] https://dist.apache.org/repos/dist/dev/plc4x/build-tools/code-generation/{code-generation-full-version}/rc1/
-   [3] https://www.apache.org/dev/release/validation.html#approving-a-release
-   [4] https://plc4x.apache.org/developers/release/validation.html
-----
-
-As it is sometimes to do the vote counting, if voting and discussions are going on in the same thread, we send a second email:
-
-
-[subs="verbatim,attributes"]
-----
-   E-Mail Topic:
-   [DISCUSS] Apache PLC4X Build-Tools Code-Generation {code-generation-full-version} RC1
-
-   Message:
-   This is the discussion thread for the corresponding VOTE thread.
-
-   Please keep discussions in this thread to simplify the counting of votes.
-
-   If you have to vote -1 please mention a brief description on why and then take the details to this thread.
-----
-
-Now we have to wait 72 hours till we can announce the result of the vote.
-
-This is an Apache policy to make it possible for anyone to participate in the vote, no matter where that person lives and not matter what weekends or public holidays might currently be.
-
-The vote passes, if at least 3 `+1` votes are received and more `+1` are received than `-1`.
-
-After the 72-our minimum wait period is over, and we have fulfilled the requirement of at least 3 +1 votes and more +1 than -1, a final reply is sent to the vote thread with a prefix of `[RESULT]` in the title in which the summary of the vote is presented in an aggregated form.
-
-[subs="verbatim,attributes"]
-----
-    E-Mail Topic:
-    [RESULT] [VOTE] Apache PLC4X Build-Tools Code-Generation {code-generation-full-version} RC1
-
-    Message:
-    So, the vote passes with 3 +1 votes by PMC members and one +1 vote by a non PMC member.
-
-    Chris
-----
-
-=== Releasing after a successful vote
-
-As soon as the votes are finished, and the results were in favor of a release, the staged artifacts can be released.
-This is done by moving them inside the Apache SVN.
-
-[subs="verbatim,attributes"]
-----
-   svn move -m "Release Apache PLC4X {code-generation-full-version}" \
-       https://dist.apache.org/repos/dist/dev/plc4x/build-tools/code-generation/{code-generation-full-version}/rc1 \
-       https://dist.apache.org/repos/dist/release/plc4x/build-tools/code-generation/{code-generation-full-version}
-----
-
-This will make the release artifacts available and will trigger them being copied to mirror sites.
-
-This is also the reason why you should wait at least 24 hours before sending out the release notification emails.
-
-=== Cleaning up older release versions
-
-As a lot of mirrors are serving our releases, it is the Apache policy to clean old releases from the repo if newer versions are released.
-
-This can be done like this:
-
-    svn delete https://dist.apache.org/repos/dist/release/plc4x/0.3.0/ -m"deleted version 0.3.0"
-
-After this, https://dist.apache.org/repos/dist/release/plc4x should only contain the latest release directory.
-
-=== Releasing the Maven artifacts
-
-The probably simplest part is releasing the Maven artifacts.
-
-In order to do this, the release manager logs into Nexus at https://repository.apache.org/, selects the staging repository and clicks on the `Release` button.
-
-This will move all artifacts into the Apache release repository and delete the staging repository after that.
-
-All release artifacts released to the Apache release repo, will automatically be synced to Maven central.
-
-=== Merge back release version to `release` branch
-
-The `release branch should always point to the last released version.
-This has to be done with git
-
-[subs="verbatim,attributes"]
-----
-git checkout release
-git merge releases/code-generation/{code-generation-full-version}
-----
-
-When there are conflicts it could help to use the `theirs` merge strategy, i.e.,
-
-[subs="verbatim,attributes"]
-----
-git merge -X theirs releases/code-generation/{code-generation-full-version}
-----
-
-Possibly a manual conflict resolution has to be done afterwards. After that, changes need to
-be pushed.
-
-In contrast to main releases of PLC4X we won't do any JIRA version updates, updating of the download page or notifying of the world email to announce@apache.org
-
-So now you're done. Congrats!
\ No newline at end of file
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/release/index.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/release/index.adoc
deleted file mode 100644
index 473cddb..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/release/index.adoc
+++ /dev/null
@@ -1,20 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-:imagesdir: ../../images/
-:icons: font
-
-== Releasing and Validating Releases
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/release/release.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/release/release.adoc
deleted file mode 100644
index 4e7ae20..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/release/release.adoc
+++ /dev/null
@@ -1,626 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-:imagesdir: ../../images/
-:icons: font
-
-== Releasing PLC4X
-
-=== TL/DR
-
-IMPORTANT: Please be sure to execute the release with a Java version 11 or the Karaf feature tests will not run.
-
-[%interactive]
-* [ ] Update the `RELEASE_NOTES`
-* [ ] Check year in `NOTICE`
-* [ ] Create release branch:
-[subs="verbatim,attributes"]
-----
-   mvn release:branch -P with-c,with-dotnet,with-go,with-java,with-python,enable-all-checks -DbranchName=rel/{current-short-version}
-----
-[%interactive]
-* [ ] Add a new section to the `RELEASE_NOTES` on `develop`
-* [ ] Prepare the release:
-[subs="verbatim,attributes"]
-----
-   mvn release:prepare -P with-c,with-dotnet,with-go,with-java,with-python,enable-all-checks
-----
-[%interactive]
-* [ ] Perform the release:
-[subs="verbatim,attributes"]
-----
-   mvn clean release:perform
-----
-[%interactive]
-* [ ] Close the staging repo on `Nexus`
-* [ ] Stage the release artifacts in `SVN`
-* [ ] Vote on the mailing list
-* [ ] Move RC to the release section of `SVN`
-* [ ] Remove old releases in `SVN`
-* [ ] Release staging repo on `Nexus`
-* [ ] Add the version to the DOAP file on `develop`
-* [ ] Update Download site
-* [ ] Update Jira
-* [ ] Merge back release version to `release` branch
-* [ ] Send announce email
-
-=== Preparing your system for being able to release
-
-NOTE: Be sure you are using a JDK and not a JRE, or the release will fail because the release can't execute the `javadoc` executable.
-
-As part of the release process, Maven will upload maven release artifacts to a so-called staging repository.
-
-This can be thought of as an ad-hoc Maven repository that contains only the artifacts for one release.
-This helps reviewers to see what's in the convenience maven package and to release that to the public repos with one click.
-
-In order to be allowed to upload artifacts, your account has to be enabled for this, and you have to tell Maven about your credentials.
-
-In order to do this, you should provide these credentials via `.m2/settings.xml`.
-
-So if you don't already have one, you should create a `.m2` directory in your user home and inside that create a `settings.xml` file with at least this content:
-
-   <?xml version="1.0" encoding="UTF-8"?>
-   <settings xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.1.0 http://maven.apache.org/xsd/settings-1.1.0.xsd" xmlns="http://maven.apache.org/SETTINGS/1.1.0"
-       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
-     <servers>
-       <!-- Apache Repo Settings -->
-       <server>
-           <id>apache.snapshots.https</id>
-           <username>{user-id}</username>
-           <password>{user-pass}</password>
-       </server>
-       <server>
-           <id>apache.releases.https</id>
-           <username>{user-id}</username>
-           <password>{user-pass}</password>
-       </server>
-     </servers>
-   </settings>
-
-This tells maven to use above credentials as soon as a repository with the id `apache.snapshots.https` or `apache.releases.https` is being used.
-For a release all you need is the `releases` repo, but it is good to have the other in place as it enables you to also deploy SNAPSHOTs from your system.
-There repos are defined in the `apache` parent pom and is identical for all Apache projects.
-
-Additionally, all artifacts are automatically signed by the release build. In order to be able to do this you need to set up GPG.
-
-The key being used to sign the artifacts will have to be linked to your Apache E-Mail ({apache-id}@apache.org) and verified by at least one fellow Apache committer (Ideally more) that have trusted keys themselves.
-Usually for this you have to get in touch - in real life - with any Apache committer with a trusted key.
-Attending an `ApacheCon` is usually a great way to do this as usually every ApacheCon has a `Key Signing event` in its schedule.
-He can then sign your key and hereby enable you to sign Apache release artifacts.
-
-There's a detailed description https://github.com/apache/incubator-pulsar/wiki/Create-GPG-keys-to-sign-release-artifacts[here].
-
-NOTE: However, in contrast to that documentation, upload your key to the following servers: `pool.sks-keyservers.net` and `keyserver.ubuntu.com` as these are the ones Nexus is checking.
-
-If you happen to have multiple keys, adding the following profile to your `settings.xml` should help:
-
-    <profile>
-      <id>apache-release</id>
-      <properties>
-        <gpg.keyname>5C60D6B9</gpg.keyname><!-- Your GPG Keyname here -->
-        <!-- Use an agent: Prevents being asked for the password during the build -->
-        <gpg.useagent>true</gpg.useagent>
-        <gpg.passphrase>topsecret-password</gpg.passphrase>
-      </properties>
-    </profile>
-
-Currently, there is a Java-Version sweet-spot for being able to release all modules and that is Java 11.
-
-So be sure to set `Java 11` as the java version used to do the release.
-
-Also, at least `Maven 3.6` is required for CMake.
-
-Ideally use the Maven-Wrapper to ensure the Maven version fits the build.
-
-NOTE: On some systems (mainly Mac) gpg signing can result in errors like:
-    ```[INFO] --- maven-gpg-plugin:3.0.1:sign (sign-release-artifacts) @ plc4x-parent ---
-    gpg: signing failed: Inappropriate ioctl for device```
-    In this case adding the following helps: `export GPG_TTY=$(tty)`
-
-=== Preparing the codebase for a release
-
-Usually you will have to update the RELEASE_NOTES document to the new version.
-I would suggest doing this prior to the branch as otherwise you will definitely have to port it back to `develop`.
-So remove the `SNAPSHOT` and `(Unreleased)` markers from the file and add missing parts.
-
-Also, if you are doing the first release in a new year, it is advisable to search for the old year and check if any occurrences are ok the way they are.
-Usually the `NOTICE` file has to be adjusted.
-
-=== Creating a release branch
-
-According to SemVer, we have: Major, Minor and Bugfix releases.
-
-For each new Major and Minor release we create a new branch at the beginning of a code-freeze phase.
-
-So if currently the project version in develop is `{current-full-version}-SNAPSHOT`, we create a branch `rel/{current-short-version}`.
-
-When creating the branch is exactly the moment in which the version in `develop` is incremented to the next minor version.
-
-This can and should be automated by the `maven-release-plugin`.
-
-Per default the plugin will ask for the working copy version during the build execution.
-This is the version the `develop` branch will be changed to.
-
-In contrast to normal builds, it is important to enable all profiles when creating the branch as only this way will all modules versions be updated.
-Otherwise, the non-default modules on develop will reference the old version which will cause problems when building.
-
-   mvn release:branch -P with-c,with-dotnet,with-go,with-java,with-python,enable-all-checks -DbranchName=rel/{minor-version}
-
-Per default the plugin suggests the next bugfix version as working version, however we want it to use the next minor version.
-So in case of preparing the release branch for `{current-full-version}-SNAPSHOT` the command would be the following:
-
-[subs="verbatim,attributes"]
-----
-   mvn release:branch -P with-c,with-dotnet,with-go,with-java,with-python,enable-all-checks -DbranchName=rel/{current-short-version}
-----
-
-The plugin will then aks for the version:
-
-[subs="verbatim,attributes"]
-----
-   What is the new working copy version for "PLC4X"? (org.apache.plc4x:plc4x-parent) {current-next-incremental-version}-SNAPSHOT: : {current-next-minor-version}-SNAPSHOT
-----
-
-Here the suggested default has to be manually overridden.
-
-This step now should perform quite quickly as no build and no tests are involved.
-
-However, in the end the versions of the `develop` branch are updated and a new `rel/{current-short-version}` branch is created.
-
-=== Preparing `develop` for the next iteration
-
-Now is a good time to add a new section to the `RELEASE_NOTES` document for the new `SNAPSHOT` version.
-
-Here comes a template:
-
-[subs="verbatim,attributes"]
-----
-==============================================================
-(Unreleased) Apache PLC4X {current-next-minor-version}-SNAPSHOT
-==============================================================
-
-New Features
-------------
-
-Incompatible changes
---------------------
-
-Bug Fixes
----------
-
-// Rest of the file
-
-----
-
-Also be sure to do a quick full-text-search to check if the version was updated correctly everywhere.
-
-WARNING: If you find anything here, you will need to pay attention during the release.
-
-=== Release stabilization phase
-
-Now usually comes a phase in which last tests and checks should be performed.
-
-If any problems are found, they have to be fixed in the release branch.
-
-Changes should either be re applied in `develop` or `cherry-picked`, however merging things back can cause a lot of problems, and we no longer have the same versions.
-
-=== Preparing a release
-
-Same as with creating the branch it is important to enable all profiles when creating the branch as only this way will all modules versions be updated.
-Otherwise, the non-default modules on develop will reference the old version which will cause problems when building.
-For people building with some additional profiles from the source release will be impossible.
-
-As especially when switching a lot between different branches, it is recommended to do a clean checkout of the repository.
-Otherwise, a lot of directories can be left over, which would be included in the source-release zip.
-In order to prepare a release-candidate, the first step is switching to the corresponding release-branch.
-
-After that, the following command will to all preparation steps for the release:
-
-   mvn release:prepare -P with-c,with-dotnet,with-go,with-java,with-python,enable-all-checks
-
-(The `-P with-c,with-dotnet,with-go,with-java,with-python,enable-all-checks` tells maven to activate the all profiles that partition the build and makes sure the versions of all modules are updated as part of the release)
-In general the plugin will now ask you 3 questions:
-
-1. The version we want to release as (It will suggest the version you get by omitting the `-SNAPSHOT` suffix)
-2. The name of the tag the release commit will be tagged with in the SCM (Name it `v{release-version}` (`v{current-full-version}` in our case)
-3. The next development version (The version present in the pom after the release) (`{current-next-bugfix-version}` in our case)
-
-Usually for 1 and 3 the defaults are just fine, make sure the tag name is correct as this usually is different.
-
-What the plugin now does, is automatically execute the following operations:
-
-1. Check we aren't referencing any `SNAPSHOT` dependencies.
-2. Update all pom versions to the release version.
-3. Run a build with all tests
-4. Commit the changes (commit message: `[maven-release-plugin] prepare release v{current-full-version}`)
-5. Push the commit
-6. Tag the commit
-7. Update all poms to the next development version.
-8. Commit the changes (commit message: `[maven-release-plugin] prepare for next development iteration`)
-9. Push the commit
-
-However, this just prepared the git repository for the release, we have to perform the release to produce and stage the release artifacts.
-
-Please verify the git repository at: https://gitbox.apache.org/repos/asf?p=plc4x.git
-is in the correct state. Please select the release branch and verify the commit log looks similar to this
-
-image::release-git-history.png[]
-
-It is important that the commit with the message "[maven-release-plugin] prepare release v{release-version}" is tagged with the release tag (in this case v{current-full-version})
-
-If you check the commit itself, it should mainly consist of version updates like this:
-
-image::release-git-diff-prepare-release.png[]
-
-The root pom has a few more changes, but in general this should be what you are seeing.
-
-After that should come a second commit:
-
-image::release-git-diff-next-development-iteration.png[]
-
-This now updates the versions again, but this time from the release version to the one we selected for the next development iteration (in this case 0.3.1-SNAPSHOT)
-
-NOTE: If the commit history doesn't look like this, something went wrong.
-
-== What if something goes wrong?
-
-If something goes wrong, you can always execute:
-
-   mvn release:rollback -P with-c,with-dotnet,with-go,with-java,with-python,enable-all-checks
-
-It will change the versions back and commit and push things.
-
-Also, should you check if you have any uncommitted changes (as our code-generation can make git think they are "dirty")
-
-However, it will not delete the tag in GIT (locally and remotely). So you have to do that manually or use a different tag next time.
-
-=== Performing a release
-
-This is done by executing another goal of the `maven-release-plugin`:
-
-   mvn clean release:perform
-
-NOTE: The clean is only for making sure there is no artifacts in `target` directly, but only in `target/checkout/target`.
-
-This executes automatically as all information it requires is located in the `release.properties` file the `prepare`-goal prepared.
-
-The first step is that the `perform`-goal checks out the previously tagged revision into the root modules `target/checkout` directory.
-Here it automatically executes a maven build (You don't have to do this, it's just that you know what's happening):
-
-   mvn deploy -P apache-release
-
-As the `apache-release` profile is also activated, this builds and tests the project as well as creates the JavaDocs, Source packages and signs each of these with your PGP key.
-
-We are intentionally not adding the other profiles, as these either produce binary artifacts that usually only work on the system they were compiled on (C++, .Net) or we haven't found a good way to distribute them via Maven yet (Python).
-
-As this time the build is building with release versions, Maven will automatically choose the release url for deploying artifacts.
-
-The way things are set up in the apache parent pom, is that release artifacts are deployed to a so-called `staging repository`.
-
-You can think of a `staging repository` as a dedicated repository created on the fly as soon as the first artifact comes in.
-
-After the build you will have a nice and clean Maven repository at https://repository.apache.org/ that contains only artifacts from the current build.
-
-After the build it is important to log in to `Nexus` at https://repository.apache.org/, select `Staging Repositories` and find the repository with the name: `orgapacheplc4x-{somenumber}`.
-
-Select that and click on the `Close` button.
-
-Now Nexus will do some checks on the artifacts and check the signatures.
-
-As soon as it's finished, we are done on the Maven side and ready to continue with the rest of the release process.
-
-A release build also produces a so-called `source-assembly` zip.
-
-This contains all sources of the project and will be what's actually the release from an Apache point of view and will be the thing we will be voting on.
-
-This file will also be signed and `SHA512` hashes will be created.
-
-=== Staging a release
-
-Each new release and release-candidate has to be staged in the Apache SVN under:
-
-https://dist.apache.org/repos/dist/dev/plc4x/
-
-The directory structure of this directory is as follows:
-
-[subs="verbatim,attributes"]
-----
-   ./KEYS
-   ./{current-full-version}/
-   ./{current-full-version}/rc1
-   ./{current-full-version}/rc1/README
-   ./{current-full-version}/rc1/RELEASE_NOTES
-   ./{current-full-version}/rc1/apache-plc4x-{current-full-version}-source-release.zip
-   ./{current-full-version}/rc1/apache-plc4x-{current-full-version}-source-release.zip.asc
-   ./{current-full-version}/rc1/apache-plc4x-{current-full-version}-source-release.zip.sha512
-----
-
-You can generally import the stuff, by preparing a directory structure like above locally and then using `svn import` to do the importing:
-
-----
-cd ./{current-full-version}
-svn import rc1 https://dist.apache.org/repos/dist/dev/plc4x/{current-full-version}/rc1 -m"Staging of rc1 of PLC4X {current-full-version}"
-----
-
-The `KEYS` file contains the PGP public key which belongs to the private key used to sign the release artifacts.
-
-If this is your first release be sure to add your key to this file.
-For the format have a look at the file itself.
-It should contain all the information needed.
-
-Be sure to stage exactly the `README` and `RELEASE_NOTES` files contained in the root of your project.
-Ideally you just copy them there from there.
-
-All three `*-source-relese.zip*` artifacts should be located in the directory: `target/checkout/target`
-
-After committing these files to SVN you are ready to start the vote.
-
-=== Starting a vote on the mailing list
-
-After staging the release candidate in the Apache SVN, it is time to actually call out the vote.
-
-For this we usually send two emails.
-The following would be the one used to do our first TLP release:
-
-[subs="verbatim,attributes"]
-----
-E-Mail Topic:
-[VOTE] Apache PLC4X {current-full-version} RC1
-
-Message:
-Apache PLC4X {current-full-version} has been staged under [2] and it’s time to vote
-on accepting it for release. All Maven artifacts are available under [1].
-Voting will be open for 72hr.
-
-A minimum of 3 binding +1 votes and more binding +1 than binding -1
-are required to pass.
-
-Release tag: v{current-full-version}
-Hash for the release tag: {replacethiswiththerealgitcommittag}
-
-Per [3] "Before voting +1 PMC members are required to download
-the signed source code package, compile it as provided, and test
-the resulting executable on their own platform, along with also
-verifying that the package meets the requirements of the ASF policy
-on releases."
-
-You can achieve the above by following [4].
-
-[ ]  +1 accept (indicate what you validated - e.g. performed the non-RM items in [4])
-[ ]  -1 reject (explanation required)
-
-
-[1] https://repository.apache.org/content/repositories/orgapacheplc4x-{somefourdigitnumber}
-[2] https://dist.apache.org/repos/dist/dev/plc4x/{current-full-version}/rc1
-[3] https://www.apache.org/dev/release.html#approving-a-release
-[4] https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release
-----
-
-As it is sometimes to do the vote counting, if voting and discussions are going on in the same thread, we send a second email:
-
-
-[subs="verbatim,attributes"]
-----
-E-Mail Topic:
-[DISCUSS] Apache PLC4X {current-full-version} RC1
-
-Message:
-This is the discussion thread for the corresponding VOTE thread.
-
-Please keep discussions in this thread to simplify the counting of votes.
-
-If you have to vote -1 please mention a brief description on why and then take the details to this thread.
-----
-
-Now we have to wait 72 hours till we can announce the result of the vote.
-
-This is an Apache policy to make it possible for anyone to participate in the vote, no matter where that person lives and not matter what weekends or public holidays might currently be.
-
-The vote passes, if at least 3 `+1` votes are received and more `+1` are received than `-1`.
-
-After the 72-hour minimum wait period is over and we have fulfilled the requirement of at least 3 +1 votes and more +1 than -1, a final reply is sent to the vote thread with a prefix of `[RESULT]` in the title in which the summary of the vote is presented in an aggregated form.
-
-[subs="verbatim,attributes"]
-----
-E-Mail Topic:
-[RESULT] [VOTE] Apache PLC4X {current-full-version} RC1
-
-Message:
-So, the vote passes with {number of +1 votes} +1 votes by PMC members {number of +1 votes from non-pmc members} +1 vote by a non PMC member.
-----
-
-=== Releasing after a successful vote
-
-As soon as the votes are finished, and the results were in favor of a release, the staged artifacts can be released.
-This is done by moving them inside the Apache SVN.
-
-[subs="verbatim,attributes"]
-----
-   svn move -m "Release Apache PLC4X {current-full-version}" \
-       https://dist.apache.org/repos/dist/dev/plc4x/{current-full-version}/rc1 \
-       https://dist.apache.org/repos/dist/release/plc4x/{current-full-version}
-----
-
-This will make the release artifacts available and will trigger them being copied to mirror sites.
-
-This is also the reason why you should wait at least 24 hours before sending out the release notification emails.
-
-=== Going back for a new release candidate
-
-If however for some reason it is needed to prepare a new RC for the release. Please follow these steps:
-
-- Set the versions of the release branch to the previous version by using the `versions:set` plugin:
-
-    mvn versions:set -DprocessAllModules=true -P with-c,with-dotnet,with-go,with-java,with-python,enable-all-checks
-
-- Delete the tag locally:
-
-    git tag -d v{current-full-version}
-
-- Delete the tag remotely:
-
-    git push --delete origin v{current-full-version}
-
-- Commit all changes
-
-- Drop the staging repo at https://repository.apache.org
-
-- Delete the previous RC in SVN
-
-   svn rm https://dist.apache.org/repos/dist/dev/plc4x/0.9.0/rc1 -m"Removed rc1 of PLC4x 0.9.0"
-
-- Reply to the `VOTE` and the `DISCUSS` announcing the vote has been cancelled and explain why and that you're going to start a new RC soon. Ideally prefix the title of the Emails with `[CANCELLED]`
-
-After this you should be ready to start a new RC.
-
-=== Cleaning up older release versions
-
-As a lot of mirrors are serving our releases, it is the Apache policy to clean old releases from the repo if newer versions are released.
-
-This can be done like this:
-
-    svn delete https://dist.apache.org/repos/dist/release/plc4x/{current-full-version}/ -m"deleted version {current-full-version}"
-
-After this https://dist.apache.org/repos/dist/release/plc4x should only contain the latest release directory.
-
-=== Releasing the Maven artifacts
-
-Probably the simplest part is releasing the Maven artifacts.
-
-In order to do this, the release manager logs into Nexus at https://repository.apache.org/, selects the staging repository and clicks on the `Release` button.
-
-This will move all artifacts into the Apache release repository and delete the staging repository after that.
-
-All release artifacts released to the Apache release repo, will automatically be synced to Maven central.
-
-=== Add the version to the DOAP file
-
-Now that the release is out, in the `develop` branch, update the `DOAP` file for plc4x.
-
-This is found at:
-
-    src/site/resources-filtered/plc4x-doap.rdf
-
-Please add the just released version to the top of the versions.
-
-This file is needed for Apache's tooling to automatically keep track of project release activity, and we use this internally too to automatically update the documentation to always reference the latest released version automatically.
-
-=== Merge back release version to `release` branch
-
-The `release` branch should always point to the last released version.
-This has to be done with git
-
-[subs="verbatim,attributes"]
-----
-git checkout release
-git merge v{current-full-version}
-----
-
-When there are conflicts it could help to use the `theirs` merge strategy, i.e.,
-
-[subs="verbatim,attributes"]
-----
-git merge -X theirs v{current-full-version}
-----
-
-Possibly a manual conflict resolution has to be done afterwards. After that, changes need to
-be pushed.
-
-=== Updating Jira
-
-1. Set the released version to "released" and set the "release-date"
-2. Add the next version to the versions.
-
-=== Update the download site
-
-The URL http://plc4x.apache.org/users/download.html has to be changed, and the current release has to be listed there.
-This is done by changing the `download.adoc` under `src/site/users/` (**in the develop branch, as this is where the site is generated from!**)
-
-1. Copy the last release down to _Previous Releases_
-2. Point the download links of the last release to archive, e.g. `http://archive.apache.org/dist/plc4x/{current-full-version}/apache-plc4x-{current-full-version}-source-release.zip`
-3. Add the new Release under _Current Releases_ and change all links.
-_Note: Please add an anchor for the toc_
-4. Update the sections for the changes according to the _RELEASE_NOTES_ from the release
-_Note: Transfer all to ascii-doc notation to ensure correct rendering of the site_
-_Also remove the JIRA TICKET ids in Front_
-
-=== Notifying the world
-
-Make sure you have given the Apache mirrors time to fetch the release files by waiting at least 24 hours after moving the release candidate to the release part of the SVN.
-
-After that it is time to announce your release to the world:
-
-[subs="verbatim,attributes"]
-----
-From:
-your apache email address
-To:
-announce@apache.org
-
-CC:
-dev@plc4x.apache.org
-
-E-Mail Topic:
-[ANNOUNCE] Apache PLC4X {current-full-version} released
-
-Message:
-The Apache PLC4X team is pleased to announce the release of Apache PLC4X {current-full-version}
-
-PLC4X is a set of libraries for communicating with industrial programmable
-logic controllers (PLCs) using a variety of protocols but with a shared API.
-
-The current release contains drivers able to communicate with industrial PLCs using one of the following protocols:
-
-  *   AB-ETH
-  *   Beckhoff ADS
-  *   CanOpen
-  *   EtherNet/IP / EIP
-  *   Firmata
-  *   KNXNet/IP
-  *   Modbus
-  *   OPC UA
-  *   Siemens S7 (0x32)
-
-Beyond that we also provide integration modules for the following Apache projects and frameworks:
-
-  *   Apache Calcite
-  *   Apache Camel
-  *   Apache Edgent (Incubating / Retired)
-  *   Apache Kafka (Kafka Connect)
-  *   Apache NiFi
-  *   Logstash
-
-It also provides an `OPC UA Server` which can act as a bridge between legacy systems and OPC UA.
-
-Visit the Apache PLC4X website [1] for general information or
-the downloads page [2] for release notes and download information.
-
-Regards,
-The Apache PLC4X team
-
-[1] http://plc4x.apache.org
-[2] http://plc4x.apache.org/users/download.html
-----
-
-It is important to note that you have to send this email from your apache email address, or it will be rejected.
-This wasn't very simple for me to set up.
-A general description can be found here:
-https://reference.apache.org/committer/email
-Here's what I did in Google Mail to allow sending of emails:
-https://gmail.googleblog.com/2009/07/send-mail-from-another-address-without.html
-Note ... you will be able to select the alternate sending address if you click into the recipients line of a new email (Not very intuitive).
-
-After that email is out the door, you're done. Congrats!
\ No newline at end of file
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/release/validation.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/release/validation.adoc
deleted file mode 100644
index e5f572b..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/release/validation.adoc
+++ /dev/null
@@ -1,130 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-:imagesdir: ../images/
-:icons: font
-
-== Validating a staged release
-
-TIP: On MacOS and Linux the first 4 steps can be automated. For details please read the section about tooling after this chapter.
-
-[%interactive]
-* [ ] Download all staged artifacts under the url specified in the release vote email into a directory we'll now call `download-dir`.
-* [ ] Verify the signature is correct:
-Additional Apache tutorial on how to verify downloads can be found http://www.apache.org/info/verification.html[here].
-[subs="attributes"]
-----
-gpg --verify apache-plc4x-{current-full-version}-source-release.zip.asc apache-plc4x-#{current-full-version}-source-release.zip
-----
-[%interactive]
-* [ ] Check if the check is successful.
-* [ ] Check if the signature references an Apache email address.
-* [ ] Verify the SHA512 hashes:
-[subs="attributes"]
-----
-Mac/Linux: shasum -a512 apache-plc4x-{current-full-version}-source-release.zip
-
-Windows (PowerShell): Get-FileHash -Algorithm SHA512 .\apache-plc4x-code-generation-{current-full-version}-source-release.zip | Format-List
-----
-[%interactive]
-* [ ] Unzip the archive:
-[subs="attributes"]
-----
-unzip apache-plc4x-{current-full-version}-source-release.zip
-----
-[%interactive]
-* [ ] Verify the existence of `LICENSE`, `NOTICE`, `README`, `RELEASE_NOTES` files in the extracted source bundle.
-* [ ] Verify the content of `LICENSE`, `NOTICE`, `README`, `RELEASE_NOTES` files in the extracted source bundle.
-
-TIP: (Especially pay attention to the year in the `NOTICE` file if this is the first release of the year)
-
-[%interactive]
-* [ ] [RM] Verify the staged source README, RELEASE_NOTE files correspond to those in the extracted source bundle.
-* [ ] [RM] Run RAT externally to ensure there are no surprises.
-[subs="attributes"]
-----
-java -jar apache-rat-0.13.jar apache-plc4x-{current-full-version}-source-release.zip > rat.log
-----
-[%interactive]
-* [ ] Search for `SNAPSHOT` references:
-[subs="attributes"]
-----
-find . -type f -name 'pom.xml' -exec grep -l "SNAPSHOT" {} \;
-----
-[%interactive]
-* [ ] Search for `Copyright` references, and if they are in headers, make sure these files containing them are mentioned in the LICENSE file.
-* [ ] Build the project according to the information in the README.md file.
-* [ ] [RM] Build the project with all `with-xyz` profiles and tests enabled and an empty maven local repo: by appending `-Dmaven.repo.local=../.m2` (On windows use `-D"maven.repo.local"="../.m2"`).
-
-=== Using RAT
-
-Even if we are using RAT to ensure sources have headers in place, still the project can contain exclusions that hide things from the check.
-
-The only way to avoid missing important files is by running `RAT` externally.
-
-If you haven't got it, yet please download it form https://creadur.apache.org/rat/download_rat.cgi[here].
-
-Also do I like to run RAT against the zip archive containing the source release as this way you avoid the problem of eventually scanning the binaries produced by the build (If you run RAT after building, it will complain about every jar and ever class file).
-
-[subs="attributes"]
-----
-java -jar apache-rat-0.13.jar apache-plc4x-{current-full-version}-source-release.zip > rat.log
-----
-
-By piping the result into a text file gives you the chance to investigate the content more easily.
-
-=== Release Tooling
-
-In the `tools` directory we have a little script that can help with downloading and checking the hashes and signatures automatically.
-
-In order to execute this, please change directories into the projects base directory and execute the following command:
-
-[subs="attributes"]
-----
-tools/download_staged_release.sh {current-full-version} 1
-----
-
-This will download all the files into a directory: `downloaded-plc4x-{current-full-version}1`.
-
-After that it will calculate the SHA512 hash and compare it with the staged hash.
-
-Last not least it will validate the PGP key and print out some information on it.
-
-=== Template for the email for voting
-
-----
-+1/-1 (binding)
-
-Name
-
-[] Download all staged artifacts under the url specified in the release vote email.
-[] Verify the signature is correct.
-[] Check if the signature references an Apache email address.
-[] Verify the SHA512 hashes.
-[] Unzip the archive.
-[] Verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle.
-[] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle.
-[] [RM] Verify the staged source README, RELEASE_NOTE files correspond to those in the extracted source bundle.
-[] [RM] Run RAT externally to ensure there are no surprises.
-[] Search for SNAPSHOT references
-[] Search for Copyright references, and if they are in headers, make sure these files containing them are mentioned in the LICENSE file.
-[] Build the project according to the information in the README.md file.
-[] [RM] Build the project with all with-xyz profiles and tests enabled and an empty maven local repo.
-----
-
-If everything is ok, I put "OK" int the square brackets.
-If there are minor issues, I put "MINOR" in there and, if it's a short reason, I put an explanation at the end of the line. If it's longer I put a longer section after the checklist.
-If there are major issues, I put "FAIL" in there and comment the same way as with minor issues.
\ No newline at end of file
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/team.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/team.adoc
deleted file mode 100644
index 787754f..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/team.adoc
+++ /dev/null
@@ -1,90 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-:imagesdir: ../images/
-:icons: font
-
-== Team
-
-Sorted by first name:
-
-[width="100%",cols="2,4,1,1",options="header"]
-|=========================================================
-|Name |Bio | |
-| *Ben Hutcheson*
-
-Software Developer, Control Systems Engineer
-
-Isar Aerospace
-
-Altötting, Germany |Experienced as an Electrical Engineer, Control Systems Engineer and Software Developer. Enjoys developing systems which overlap in all three of these fields. | a| image::team/hutcheb.png[hutcheb, 240, 320]
-| *César García*
-
-CEOS Automatización, C.A.
-
-Pto. La Cruz, Anzoátegui, Venezuela |Electrical engineer, dedicated to process automation and control. Specialized in Siemens S5, S7, PCS7 architecture for the Oil&Gas industry and Braumat for the food and beverage industry. Applying open source technologies to create added value for users, such as Kannel, Apache Http Server, Apache Karaf, Apache Hop, Apache IoTDB and the meeting point of all of them Apache PLC4X where I have been able to collaborate as a PMC. | a| image::team/glcj.jpg[g [...]
-| *Christofer Dutz*
-
-IoT Consultant
-
-Timecho Europe GmbH
-
-Frankfurt |Likes to swim outside the mainstream. He is really passionate about walking new paths. His first email to an Apache list on file was to the Cocoon project back in the year 2000. His direct involvement started in 2012 when he was elected to become an Apache Flex committer. Since then he became involved with a lot of Apache-internal groups and committees and was elected to become a Member of the Apache Software Foundation in 2015 and recently has taken up the role of mentoring s [...]
-| *Julian Feinauer*
-
-Founder / CEO
-
-pragmatic minds GmbH /
-pragmatic industries GmbH
-
-Kirchheim unter Teck |Has studied mathematics in Stuttgart. Besides his interest in open source software and big data, he focuses on the analysis of time series and traces from testing or manufacturing. PLC4X was the first project where he was offered a position as (P)PMC but he is also engaged in other Apache projects like Edgent and IotDB. | a|image::team/jfeinauer.jpg[jfeinauer, 240, 320]
-| *Łukasz Dywicki*
-
-Coding CEO / Consultant
-
-ConnectorIO sp. z o.o. /
-Code-House (self employed)
-
-Warsaw | He started working with Apache Software Foundation projects in 2007 - at the time when the first incubation version of Apache CXF was out. Since then he took active part and contributed to Apache projects related to software integration such as Apache Karaf, Apache ActiveMQ and Apache Camel. He is an Open Source and OSGi enthusiast, passionate about connecting things, physical ones too. | a|image::team/ldywicki.jpg[ldywicki, 240, 304]
-| *Lukas Ott*
-
-Domain Architect
-
-Pharmaceutical Industry
-
-Copenhagen | He started working with Apache Software Foundation projects in 2013 - at that time in the context of Semantic Technologies with an archived project called Apache Stanbol. Since then he took an interested in several different Apache projects like Apache ActiveMQ, Apache Spark, Apache Storm, Apache Cassandra. He is an Open Source and Pythonista, passionate about connecting people, processes and machines. Main focus is community over code and linking different communities toget [...]
-| *Matthias Milan Strljic*
-
-Research assistant
-
-ISW;
-University of Stuttgart
-
-Stuttgart |Research assistant and software engineer at the Institute for control engineering of machine tools and manufacturing units (ISW) of the university of stuttgart, research in the fields of automation technology + smart services + cloud manufacturing, my favourites are woodwork + knife sharpening + cigars, member of the PMC of PLC4X| a| image::team/mstrljic.jpg[mstrljic, 150, 150]
-| *Sebastian Rühl*
-
-Software Developer
-
-Mapped
-
-Frankfurt |Software engineer, member of the PMC of PLC4X| a| image::team/sruehl.jpg[sruehl, 240, 320]
-| *Tim Mitsch*
-
-Engineer
-
-pragmatic industries GmbH
-
-Nürtingen |Electrical engineer (HW, SW and interface-stuff) from passion and very new to Apache projects. The more he is involved in open-source the more he likes it, focusing on PLC4X at first. | a|image::team/tmitsch.png[tmitsch, 240, 263]
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/tools.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/tools.adoc
deleted file mode 100644
index 825229d..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/tools.adoc
+++ /dev/null
@@ -1,32 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-:imagesdir: ../images/
-:icons: font
-
-== Tools
-
-In order to be able to work on PLC4X some tools have kindly been made available to Apache PLC4X committers.
-
-Jetbrains offers Licenses to IntelliJ to Apache Committers for free
-
-EJ-Technologies have also kindly provided us with JProfiler licenses in order to track down some concurrency and memory usage problems.
-
-[link=https://www.ej-technologies.com/products/jprofiler/overview.html]
-image::https://www.ej-technologies.com/images/product_banners/jprofiler_large.png[JProfiler^,opts=nofollow]
-
-Thank you to all.
-
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/tutorials/index.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/tutorials/index.adoc
deleted file mode 100644
index 21ded0e..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/tutorials/index.adoc
+++ /dev/null
@@ -1,20 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-:imagesdir: ../../images/
-:icons: font
-
-== Tutorials
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/tutorials/testing-serializers-and-parsers.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/tutorials/testing-serializers-and-parsers.adoc
deleted file mode 100644
index 5b55e17..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/tutorials/testing-serializers-and-parsers.adoc
+++ /dev/null
@@ -1,146 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-:imagesdir: ../../images/
-
-= Testing Serializers and Parsers
-
-Currently the build generates the serializers and parsers from a provided `mspec` specification.
-
-A typical full round-trip test for the model, parsers and serializers would look as follows:
-
-* Starting from a byte array
-* The parser is used to parse the byte array
-* The parsed model instance is compared with an expected model
-* If the expected model matched the expected one the model is serialized back to a byte array
-* The resulting byte array is compared to the original byte array
-* If the byte arrays are identical, the round-trip is regarded ok
-
-Doing this manually would require a lot of manual object construction and validation, so we created a framework for creating such tests.
-
-As XML, no matter what you think about it, allows simple and easy readable descriptions these tests are provided as `XML files`.
-
-All generated model classes allow parsing and serializing to XML via `Jackson`.
-
-== Structure of a test
-
-A typical test looks like this:
-
-----
-  <testcase>
-    <name>Read Input Registers Request</name>
-    <raw>000000000006ff0408d20002</raw>
-    <root-type>ModbusTcpADU</root-type>
-    <parser-arguments>
-      <response>false</response>
-    </parser-arguments>
-    <xml>
-      <ModbusTcpADU className="org.apache.plc4x.java.modbus.readwrite.ModbusTcpADU">
-        <transactionIdentifier>0</transactionIdentifier>
-        <unitIdentifier>255</unitIdentifier>
-        <pdu className="org.apache.plc4x.java.modbus.readwrite.ModbusPDUReadInputRegistersRequest">
-          <startingAddress>2258</startingAddress>
-          <quantity>2</quantity>
-        </pdu>
-      </ModbusTcpADU>
-    </xml>
-  </testcase>
-----
-
-As you can see, the `name` provides a simple human readable name for the test which is used for reporting success and failure.
-
-The `raw` element contains the `hex-representation` of the `binary input`.
-
-After that the `root-type` specifies the base type used for parsing this data. In above example the test will use the `ModbusTcpADUIO.serialize` and `ModbusTcpADUIO.parse` methods for serializing and parsing.
-
-Some parsers require additional parameters for parsing. In above example the Modbus protocol can't decide if something is a request or response from the data itself, so we have to pass that information in using a `parser-arguments` argument.
-
-The final element is the `xml` element, which contains the XML representation of the parsed object.
-
-Each test implements exactly the test-strategy sketched above, however for comparing the parsed and the expected model, we use `XMLUint` to serialize the parsed model to XML and compare that to the given XML in the test-case declaration.
-
-== Structure of a testsuite
-
-Multiple tests are usually wrapped into a testsuite document.
-
-In general this is just a container with a given testsuite `name` and a number of `testcase` elements.
-
-One important setting however controls the endianness of the protocol in general.
-
-This is controlled with a `bigEndian` attribute in the testsuite root element.
-
-An example testsuite document looks as follows:
-
-----
-<?xml version="1.0" encoding="UTF-8"?>
-<test:testsuite xmlns:test="https://plc4x.apache.org/schemas/parser-serializer-testsuite.xsd"
-                bigEndian="true">
-
-  <name>Allen-Bradley DF1</name>
-
-  <testcase>
-    ...
-  </testcase>
-
-  <testcase>
-    ...
-  </testcase>
-
-  <testcase>
-    ...
-  </testcase>
-
-  <testcase>
-    ...
-  </testcase>
-
-</test:testsuite>
-----
-
-== The Junit runner
-
-All logic is implemented in the `plc4j-utils-test-utils` module, so make sure to add the following test-dependency:
-
-----
-    <dependency>
-      <groupId>org.apache.plc4x</groupId>
-      <artifactId>plc4j-utils-test-utils</artifactId>
-      <version>{project.version}</version>
-      <scope>test</scope>
-    </dependency>
-----
-
-In order to run these tests as part of the build, as a last step we need to create a test-runner class.
-
-This is generally just a hand-full of boilerplate code, telling the test which document to use for testing.
-
-Following code snippet sort of looks the same for every testsuite:
-
-----
-package org.apache.plc4x.java.modbus;
-
-import org.apache.plc4x.test.parserserializer.ParserSerializerTestsuiteRunner;
-
-public class ModbusIOTest extends ParserSerializerTestsuiteRunner {
-
-    public ModbusIOTest() {
-        super("/testsuite/ModbusTestsuite.xml");
-    }
-
-}
-----
-
-Here the document `ModbusTestsuite.xml` is located in the directory: `src/test/resources/testsuite/`.
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/tutorials/writing-driver.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/tutorials/writing-driver.adoc
deleted file mode 100644
index dcf5727..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/developers/tutorials/writing-driver.adoc
+++ /dev/null
@@ -1,57 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-:imagesdir: ../../images/
-
-== Basic Building Blocs of a Driver / Protocol
-
-The general pipeline for a Protocol looks like the following:
-
-[ditaa,driver-anatomy]
-....
-+-------------------------------------+
-|  Upstream (e.g. PLC4X API           :
-+-------------------------------------+
-                  |
-                  :
-                  v
-+-------------------------------------+
-|  PLC4X Optimizer                    :
-|  Possibly collapse requests         |
-+-------------------------------------+
-                  |
-                  :
-                  v
-+-------------------------------------+
-|  Protocol L1                        |
-|  Req. to (generated) Message Objects|
-+-------------------------------------+
-                  |
-                  |
-                  v
-+-------------------------------------+
-|  Protocol L2                        |
-|  Generated Objects to bytes         |
-+-------------------------------------+
-                  |
-                  |
-                  v
-+-------------------------------------+
-|  Downstream (e.g. Socket for I/O)   :
-+-------------------------------------+
-....
-
-A driver has the task to assemble the pipeline for the protocol(s).
\ No newline at end of file
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/index.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/index.adoc
deleted file mode 100644
index e3ad303..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/index.adoc
+++ /dev/null
@@ -1,242 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-:imagesdir: images/
-:icons: font
-
-++++
-<div class="jumbotron jumbotron-fluid teaser-img">
-    <div class="row" style="align-items:center;z-index:2;position:relative;">
-        <div class="col-12 col-lg-2"></div>
-    <div class="col-12 col-lg-8" style="display:flex;justify-content: center">
-        <div class="teaser-box">
-            <div class="row margin-rl-0">
-                <div class="col-md-12">
-                    <div class="margin-rl-auto">
-                        <img src="images/apache_plc4x_logo.png"  alt="Apache PLC4X" class="plc4x-logo center"/>
-                    </div>
-                    <h3 style="text-align:center;">
-                        <div class="plc4x-headline" style="text-align:center;">The universal
-                            protocol adapter for
-                            Industrial IoT
-                         </div>
-                     </h3>
-                    <div class="apache-teaser center text-center">PLC4X is a set of libraries
-                        for
-                        communicating with
-                        industrial
-                        programmable logic controllers (PLCs) using a variety of protocols but with a shared API.</div>
-                    <div class="center text-center">
-                    <a href="users/getting-started/plc4j.html"
-                       class="plc4x-button plc4x-button-large plc4x-button-primary text-center"><i
-                            class="fas fa-rocket"></i> Get started
-                    </a>
-                    </div>
-                </div>
-            </div>
-        </div>
-    </div>
-        <div class="col-12 col-lg-2"></div>
-    </div>
-</div>
-
-       <section id="no-retrofit" class="section-highlight section-highlight-primary">
-           <div class="container text-center">
-               <div class="row">
-                   <div class="col-lg-12 mx-auto">
-                       <i class="fas fa-plug fa-7x highlight-icon highlight-icon-primary"></i>
-                       <h2 class="section-highlight-text-primary">Connect your shopfloor assets without retrofit.</h2>
-                       <p class="lead c-white">In contrast to other approaches, Apache PLC4X lets you connect your
-                       industrial assets without needing to modify them.</p>
-                   </div>
-               </div>
-           </div>
-       </section>
-       <section id="no-retrofit" class="section-highlight section-highlight-secondary mb-5">
-           <div class="container text-center">
-               <div class="row">
-                   <div class="col-lg-12 mx-auto">
-                       <h2 class="section-highlight-text-secondary">Integrations.</h2>
-                       <p class="lead">PLC4X comes with many built-in integrations to further process your asset data. </p>
-                       <div id="integrationCarousel" class="carousel slide" data-ride="carousel">
-                           <div class="carousel-inner">
-                               <div class="carousel-item active">
-                                   <div class="col-md-12 col-lg-4">
-                                       <div class="card h-100 p-5 justify-content-center"
-                                            onclick="window.open('https://calcite.apache.org','_blank');" style="cursor:pointer;">
-                                           <div class="d-flex align-items-center justify-content-center h-100">
-                                               <img src="images/integrations/apache_calcite_logo.svg" alt="Card image cap">
-                                           </div>
-                                           <div class="card-body">
-                                               <h5 class="card-title"><b>Apache Calcite</b></h5>
-                                           </div>
-                                       </div>
-                                   </div>
-                               </div>
-                               <div class="carousel-item">
-                                   <div class="col-md-12 col-lg-4">
-                                       <div class="card h-100 p-5 justify-content-center"
-                                            onclick="window.open('https://camel.apache.org','_blank');" style="cursor:pointer;">
-                                           <div class="d-flex align-items-center justify-content-center h-100">
-                                               <img src="images/integrations/apache_camel_logo.png" alt="Card image cap">
-                                           </div>
-                                           <div class="card-body">
-                                               <h5 class="card-title"><b>Apache Camel</b></h5>
-                                           </div>
-                                       </div>
-                                   </div>
-                               </div>
-                               <div class="carousel-item">
-                                   <div class="col-md-12 col-lg-4">
-                                       <div class="card h-100 p-5 justify-content-center"
-                                            onclick="window.open('https://iotdb.apache.org','_blank');" style="cursor:pointer;">
-                                           <div class="d-flex align-items-center justify-content-center h-100">
-                                               <img src="images/integrations/apache_iotdb_logo.png" alt="Card image cap">
-                                           </div>
-                                           <div class="card-body">
-                                               <h5 class="card-title"><b>Apache IoTDB</b></h5>
-                                           </div>
-                                       </div>
-                                   </div>
-                               </div>
-                               <div class="carousel-item">
-                                   <div class="col-md-12 col-lg-4">
-                                       <div class="card h-100 p-5 justify-content-center"
-                                            onclick="window.open('https://kafka.apache.org','_blank');" style="cursor:pointer;">
-                                           <div class="d-flex align-items-center justify-content-center h-100">
-                                               <img src="images/integrations/apache_kafka_logo.png" alt="Card image cap">
-                                           </div>
-                                           <div class="card-body">
-                                               <h5 class="card-title"><b>Apache Kafka</b></h5>
-                                           </div>
-                                       </div>
-                                   </div>
-                               </div>
-                               <div class="carousel-item">
-                                   <div class="col-md-12 col-lg-4">
-                                       <div class="card h-100 p-5 justify-content-center"
-                                            onclick="window.open('https://nifi.apache.org','_blank');" style="cursor:pointer;">
-                                           <div class="d-flex align-items-center justify-content-center h-100">
-                                               <img src="images/integrations/apache_nifi_logo.svg" alt="Card image cap">
-                                           </div>
-                                           <div class="card-body">
-                                               <h5 class="card-title"><b>Apache Nifi</b></h5>
-                                           </div>
-                                       </div>
-                                   </div>
-                               </div>
-                               <div class="carousel-item">
-                                   <div class="col-md-12 col-lg-4">
-                                       <div class="card h-100 p-5 justify-content-center"
-                                            onclick="window.open('https://streampipes.apache.org','_blank');"
-                                            style="cursor:pointer;">
-                                           <div class="d-flex align-items-center justify-content-center h-100">
-                                               <img src="images/integrations/apache_streampipes_logo.png" alt="Card image cap">
-                                           </div>
-                                           <div class="card-body">
-                                               <h5 class="card-title"><b>Apache StreamPipes</b></h5>
-                                           </div>
-                                       </div>
-                                   </div>
-                               </div>
-                               <div class="carousel-item">
-                                   <div class="col-md-12 col-lg-4">
-                                       <div class="card h-100 p-5 justify-content-center"
-                                            onclick="window.open('https://hop.apache.org','_blank');"
-                                            style="cursor:pointer;">
-                                           <div class="d-flex align-items-center justify-content-center h-100">
-                                               <img src="images/integrations/apache_hop_logo.png" alt="Card image cap">
-                                           </div>
-                                           <div class="card-body">
-                                               <h5 class="card-title"><b>Apache Hop</b></h5>
-                                           </div>
-                                       </div>
-                                   </div>
-                               </div>                               
-                               <div class="carousel-item">
-                                   <div class="col-md-12 col-lg-4">
-                                       <div class="card h-100 p-5 justify-content-center"
-                                            onclick="window.open('https://www.eclipse.org/ditto/','_blank');"
-                                            style="cursor:pointer;">
-                                           <div class="d-flex align-items-center justify-content-center h-100">
-                                               <img src="images/integrations/eclipse_ditto_logo.png" alt="Card image cap">
-                                           </div>
-                                           <div class="card-body">
-                                               <h5 class="card-title"><b>Eclipse Ditto</b></h5>
-                                           </div>
-                                       </div>
-                                   </div>
-                               </div>
-                           </div>
-                           <a class="carousel-control-prev" href="#integrationCarousel" role="button" data-slide="prev">
-                               <span class="carousel-control-prev-icon" aria-hidden="true"></span>
-                               <span class="sr-only">Previous</span>
-                           </a>
-                           <a class="carousel-control-next" href="#integrationCarousel" role="button" data-slide="next">
-                               <span class="carousel-control-next-icon" aria-hidden="true"></span>
-                               <span class="sr-only">Next</span>
-                           </a>
-                       </div>
-                   </div>
-               </div>
-           </div>
-       </section>
-       <section id="secure" class="section-highlight section-highlight-primary">
-           <div class="container text-center">
-               <div class="row">
-                   <div class="col-lg-12 mx-auto">
-                       <i class="fas fa-lock fa-7x highlight-icon highlight-icon-primary"></i>
-                       <h2 class="section-highlight-text-primary">Secure by design.</h2>
-                       <p class="lead c-white">Not only are PLC4X drivers implemented with security in mind, also our <b>passive-mode drivers</b> bring to you guaranteed side-effect-freeness without the need to pay for validated software.</p>
-                   </div>
-               </div>
-           </div>
-       </section>
-       <section id="performant" class="section-highlight section-highlight-secondary">
-           <div class="container text-center">
-               <div class="row">
-                   <div class="col-lg-12 mx-auto">
-                       <i class="fas fa-tachometer-alt fa-7x highlight-icon highlight-icon-secondary"></i>
-                       <h2 class="section-highlight-text-secondary">Get the performance you need.</h2>
-                       <p class="lead">Most approaches like OPC-UA currently don't deliver the performance needed for machine learning, deep learning and AI. PLC4X allows you to get the data volumes in the resolutions needed, without stressing out your industrial hardware.</p>
-                   </div>
-               </div>
-           </div>
-       </section>
-       <section id="costs" class="section-highlight section-highlight-primary">
-           <div class="container text-center">
-               <div class="row">
-                   <div class="col-lg-12 mx-auto">
-                       <i class="fas fa-smile fa-7x highlight-icon highlight-icon-primary"></i>
-                       <h2 class="section-highlight-text-primary">No license costs, no restrictive licenses.</h2>
-                       <p class="lead c-white">Being open source, PLC4X is <b>free of charge</b>. Start experimenting
-                       without worrying about license costs or shady license agreements. The Apache 2.0 is one of the worlds <b>most trusted and adopted</b> open source licenses out there.</p>
-                   </div>
-               </div>
-           </div>
-       </section>
-       <section id="with-support" class="section-highlight section-highlight-secondary">
-           <div class="container text-center">
-               <div class="row">
-                   <div class="col-lg-12 mx-auto">
-                       <i class="fas fa-info-circle fa-7x highlight-icon highlight-icon-secondary"></i>
-                       <h2 class="section-highlight-text-secondary">Get the <a href="users/commercial-support.html">commercial support</a> you need.</h2>
-                       <p class="lead">Just because you can download and use PLC4X for free doesn't mean that you're left on your own. Some of our community member's companies can also provide you with the <b><a href="users/commercial-support.html">commercial support</a></b> you need.</p>
-                   </div>
-               </div>
-           </div>
-       </section>
-++++
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/ab-eth/index.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/ab-eth/index.adoc
deleted file mode 100644
index 759a709..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/ab-eth/index.adoc
+++ /dev/null
@@ -1,33 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-
-== Allen-Bradley Ethernet
-
-The Allen-Bradley Ethernet protocol encapsulates a DF1 protocol body to transfer data. The PLC4X driver currently only
-supports the protected typed logical read with a limited number of data types.
-
-=== Connection
-
-The connection string looks as follows: `ab-eth://<ip-address>/<station>`
-
-The field address: `N<file>:<offset></bitnumber>:<datatype>[<numberofbytes>]`. The following data types are available
-at the moment: SINBLEBIT (requires bitnumber to be set), WORD (2 byte integer), DWORD (4 byte integer), INTEGER (returns
-the number of bytes requested as an array, for other data types <numberofbytes> will be ignored).
-
-Example of a SINGLEBIT read: `N10:22/5:SINGLEBIT` (file 10, offset 22, bitnumber 5)
-
-Example of a WORD read: `N10:84:WORD` (file 10, offset 84, 2 byte integer)
\ No newline at end of file
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/ads/index.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/ads/index.adoc
deleted file mode 100644
index f586586..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/ads/index.adoc
+++ /dev/null
@@ -1,25 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-
-== Beckhoff ADS
-
-Introduction
-
-=== Links
-
-
-
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/canopen/index.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/canopen/index.adoc
deleted file mode 100644
index 7d9d2b2..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/canopen/index.adoc
+++ /dev/null
@@ -1,39 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-
-== CANopen
-
-CANopen is communication protocol built on top of CAN.
-CAN is a popular link layer standard which allows exchanging data between nodes and build multi-node applications.
-All nodes can broadcast their information to the buss allowing fast data exchanges without necessity to coordinate over a single "master" node.
-CANopen is a specific protocol built on top of CAN bus.
-
-The CAN in Automation (CiA) organization is responsible for releasing CANopen specification.
-It has built number of application layer protocols on top of CAN, CANopen is one of them.
-
-It is possible to obtain a copy of specification from CiA website.
-Please refer the official materials for more details on protocol and its constructs.
-
-Apache PLC4X is open source project.
-It is not a certified product.
-
-=== Links
-
-- https://www.can-cia.org/canopen[CAN in Automation] organization managing specification.
-- Public materials published by CAN in Automation: https://www.can-cia.org/en/download/
-- CAN in Automation membership: https://www.can-cia.org/about-us/member-benefits/
-- Further device profiles built on top of CANopen: https://cia-productguides.org/canopen/profiles/
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/delta-v/index.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/delta-v/index.adoc
deleted file mode 100644
index 791ece1..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/delta-v/index.adoc
+++ /dev/null
@@ -1,197 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-:imagesdir: ../../images/
-
-== DeltaV Industrial Ethernet Communication
-
-The DeltaV protocol is used in the Emerson DeltaV system.
-In contrast to most other systems, this is a combination of PLC and Control System.
-As Emerson seems to insist on the devices not being PLCs, but controllers, well call them this way in this document.
-Same with the Control System, these seem to be called OS (Operator System).
-
-=== Disclaimer
-
-As we had absolutely no information on the details of the protocol, we started by taking an existing DeltaV training system and replaced the network switch with a hub and used this to take network captures of the entire network traffic of the DeltaV network.
-
-These network captures and some knowledge of the normal system operation were all we had.
-
-All information we got, we got by inspecting these captures, building hypothesis and implementing tooling to verify these assumptions.
-
-Definitely we will not have interpreted everything correct and we'll probably do a lot of updating of this page.
-
-Due to this uncertainty we are only implementing a `promiscuous mode` driver, which will be able to read ongoing traffic without the ability to actively interact with the system.
-
-Read link:reverse-engineering.html[here] for a document on how we proceeded with reverse engineering this protocol.
-
-=== The Wrapper Protocol
-
-All communication seems to be done using the `UDP` protocol on port `18507`.
-
-When working with the dumps it seems that this version of the DeltaV protocol was implemented by wrapping another protocol within a thin wrapper protocol.
-We have seen this for almost all other industrial controller types.
-We are hereby assuming that the inner protocol is the version of the DeltaV protocol, which is used for serial communication.
-
-The general structure of such a wrapper packet seems to look like this:
-
-[packetdiag,deltav-wrapper-packet,svg]
-....
-{
-    colwidth = 32
-
-    * Header\n(Constant = 0xFACE) [len = 16]
-    * Payload Length [len = 16]
-    * Type [len = 16]
-    * Message Id [len = 16]
-    * Sender Id [len = 16]
-    * Timestamp [len = 24]
-    * 0x80/0x00 [len = 8]
-    * 0x04 [len = 8]
-    * 0x00 [len = 8]
-    * Payload [len = 64]
-    * Checksum [len = 16]
-}
-....
-
-After the fixed header of `0xFACE` comes a short value providing the `Payload Length`.
-
-After the payload probably comes the message type.
-Here we have observed the internal structure of packets with the same type to be very similar, so we're quite sure this is a type.
-
-The `Message Id` seems to be a counter existing for every communication between two partners, which is incremented for every packet sent to the other partner.
-
-We have observed every unit to have a unique `Sender Id`, however a controller has been seen to have a differing id when communicating with a different operator system.
-What we did notice however, was that controllers usually had numerical ids while the OSes had hexadecimal letters.
-So an id of `0x0002` would probably imply a controller and an id of `0x000d` would imply an operator system.
-But we could be wrong with this assumption and this just being a result of convention.
-
-The 3 bytes after the id seem to relate to a timestamp.
-Inspecting the packets and correlating this to the timestamps in our packet captures, lead us to the assumption that this timestamp uses the first 14 bits for encoding seconds and the last 10 bits for encoding the sub-second fraction.
-While a 3 byte timestamp is only able to measure a 10 minute time-slot and is probably not usable for absolute time measuring, it might be useful to measure transfer times.
-For this a 4 byte value would have been a waste of network capacity and a 2 byte value wouldn't be able to measure more than 60 seconds, which might be too short when taking into account packet resending and network timeouts.
-So for now we are assuming this format is used.
-
-The following 3 bytes seem to have a constant value of `0x800400` for most packets, except the ones with a type of `0x03` and `0x04`.
-For these two types the value seems to be `0x004400`. Here we currently can't make an assumption on the meaning of these fields.
-However as the `0x003` and `0x004` seem to be the first packets used for establishing the connection between the OS and the controller, these could somehow relate to the connection state.
-
-After these mysterious 3 bytes comes the actual payload of the packet.
-The details of these will be discussed later in this document.
-
-At the end comes a short value that seems to be a completely different value for every packet.
-As the message id and timestamp are different for every message, we are assuming this is a simple checksum.
-However we currently have no idea on how this is calculated and we haven't invested any time in finding this out.
-
-UDP being connectionless the DeltaV network protocol seems to require acknowledging.
-This is done by sending a packet back to the originator, but with a length of `0x0000` and the same `type` and mesasge-id` as the packet that is acknowledged.
-
-=== High Level View of the Protocol
-
-In this section we'll describe the general structure of how the communication looks like - which message types are sent when and in which sequence.
-
-==== Connecting an OS to a Controller
-
-[seqdiag,deltav-connect]
-....
-{
-    Controller; OS;
-
-    edge_length = 400;
-    span_height = 18;
-    default_fontsize = 12;
-    activation = none;
-
-    OS ->  Controller [label = "Type 0x0003 (Connection Request)"];
-    OS <-  Controller [label = "Type 0x0004 (Connection Response)"];
-
-    OS ->  Controller [label = "Type 0x0002 Subtype 0x0501 (Version Information)"];
-    OS <-- Controller [label = "Ack"];
-
-    OS <- Controller [label = "Type 0x0002 Subtype 0x0502 (Version Information)"];
-    OS --> Controller [label = "Ack"];
-}
-....
-
-==== Regular sync
-
-It seems that every 15 seconds two packets are exchanged.
-
-The type of these is always `0x0006`.
-
-One thing that is quite obvious, is that these are the only messages, for which the message id doesn't seem to be incremented.
-So these messages have the exact same id as the following request being sent out.
-
-We are assuming that these are sort of heartbeat messages and additionally sync the message ids so the remote could see if it lost messages in the last 15 seconds.
-
-But that is just an assumption.
-
-[seqdiag,deltav-sync]
-....
-{
-    Controller; OS;
-
-    edge_length = 400;
-    span_height = 18;
-    default_fontsize = 12;
-    activation = none;
-
-    OS -> Controller [label = "Type 0x0006 (Sync)"];
-    OS <-- Controller [label = "Type 0x0006 (Sync)"];
-}
-....
-
-==== Data changes in the Controller
-
-In general it seems as if all sub-types regarding normal data changes start with `0x04`.
-
-If the value of a subscribed value changes in the controller, a message type `0x0002` with sub-type `0x0403` is sent.
-
-[seqdiag,deltav-data]
-....
-{
-    Controller; OS;
-
-    edge_length = 400;
-    span_height = 18;
-    default_fontsize = 12;
-    activation = none;
-
-    OS <- Controller [label = "Type 0x0002 Subtype 0x0403 (...)"];
-    OS --> Controller [label = "Ack"];
-}
-....
-
-==== Alarms in the Controller
-
-In general it seems as if all sub-types regarding events and alarms start with `0x03`.
-
-[seqdiag,deltav-alarm]
-....
-{
-    Controller; OS;
-
-    edge_length = 400;
-    span_height = 18;
-    default_fontsize = 12;
-    activation = none;
-
-    OS <- Controller [label = "Type 0x0002 Subtype 0x030? (...)"];
-    OS --> Controller [label = "Ack"];
-}
-....
-
-
-
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/delta-v/read-data.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/delta-v/read-data.adoc
deleted file mode 100644
index 7793bad..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/delta-v/read-data.adoc
+++ /dev/null
@@ -1,1655 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-:imagesdir: ../../images/
-
-== 0x0403 (before registration)
-
-Before a subscription is done, regularly (about once a minute) the following packets come in.
-
-```
-fa ce 00 32 00 02 33 46 00 0b 63 b8 54 80 04 00
-
-04 03 00 00 00 00 00 52 00 00 00 00 00 00 00 00
-00 04 00 00 00 08 00 01 00 00 00 00 04
-- 04 8f 17 b8 00 2f 01 36 04 8f 17 b8
-01 00 00 00 00 00 00
-00 00
-
-94 17
-```
-
-== 0x1B01
-
-The following packets are all reformatted to group parts that belong together into one line.
-Additionally above each line - in comments - the human readable interpretation of the block below.
-
-The general purpose of a `0xB101` packet seems to be to subscribe to individual variables on the controllers.
-A `0cB101` request is always responded to by a `0xB102` reply, which contains the current value of all requested variables.
-
-After this it is noticeable, that `0x0403` packets start coming in, which seem to contain updates to the variables.
-
-The structure of each 0x1B1 is identical:
-
-* First comes a fixed size header that seems to contain mostly `0x00` values.
-* The content starts with a `set context block`, which is terminated by a block of `0xFFFF`.
-* This context block seems to have the following structure:
-** Some sort of type indicator (Haven't seen anything besides `0x04` for `0xB101` packets)
-**
-* Inside a context block come a variable number of entries, each of them with the same format:
-** First comes a short counter value starting with `0x0000`, this will be replicated in the response.
-** The second short value is the length of the string that is to follow
-** For each character of the String two bytes have to be read (Decoding these as UTL-16 worked fine)
-** After the last character comes a constant `0x0000` block
-* After the last context block just comes a single `0x04` byte
-
-```
-fa ce 05 7d 00 02 af 09 00 01 15 e0 54 80 04 00
-
-1b 01 00 00 00 00 00 07 03 6c 01 96 00 04 05 04
-00 08 00 00 00 08 01 ae 00 08 03 5c 00 08 04 82
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00
-- 04 90 17 b9 00 32 01 39 00 00 03 e8
-// BESCH3
-00 00 00 06 00 42 00 45 00 53 00 43 00 48 00 33 00 00
-// SKAL1
-00 01 00 05 00 53 00 4b 00 41 00 4c 00 31 00 00
-// DYN_BESCH1
-00 02 00 0a 00 44 00 59 00 4e 00 5f 00 42 00 45 00 53 00 43 00 48 00 31 00 00
-// ISTWERT3
-00 03 00 08 00 49 00 53 00 54 00 57 00 45 00 52 00 54 00 33 00 00
-// GF_STATUS
-00 04 00 09 00 47 00 46 00 5f 00 53 00 54 00 41 00 54 00 55 00 53 00 00
-// ALARMS
-00 05 00 06 00 41 00 4c 00 41 00 52 00 4d 00 53 00 00
-// DYN_BESCH3
-00 06 00 0a 00 44 00 59 00 4e 00 5f 00 42 00 45 00 53 00 43 00 48 00 33 00 00
-// A/BA
-00 07 00 04 00 41 00 2f 00 42 00 41 00 00
-// A/BA_GFES_AUTO
-00 08 00 0e 00 41 00 2f 00 42 00 41 00 5f 00 47 00 46 00 45 00 53 00 5f 00 41 00 55 00 54 00 4f 00 00
-// DYN_BESCH2
-00 09 00 0a 00 44 00 59 00 4e 00 5f 00 42 00 45 00 53 00 43 00 48 00 32 00 00
-// SKAL2
-00 0a 00 05 00 53 00 4b 00 41 00 4c 00 32 00 00
-// A/GFE_ALARM
-00 0b 00 0b 00 41 00 2f 00 47 00 46 00 45 00 5f 00 41 00 4c 00 41 00 52 00 4d 00 00
-// GF_NAME
-00 0c 00 07 00 47 00 46 00 5f 00 4e 00 41 00 4d 00 45 00 00
-// ISTWERT1
-00 0d 00 08 00 49 00 53 00 54 00 57 00 45 00 52 00 54 00 31 00 00
-// A/IST_FW_KURZ
-00 0e 00 0d 00 41 00 2f 00 49 00 53 00 54 00 5f 00 46 00 57 00 5f 00 4b 00 55 00 52 00 5a 00 00
-// ISTWERT2
-00 0f 00 08 00 49 00 53 00 54 00 57 00 45 00 52 00 54 00 32 00 00
-// BESCH1
-00 10 00 06 00 42 00 45 00 53 00 43 00 48 00 31 00 00
-// SKAL3
-00 11 00 05 00 53 00 4b 00 41 00 4c 00 33 00 00
-// BESCH2
-00 12 00 06 00 42 00 45 00 53 00 43 00 48 00 32 00 00
-ff ff
-- 04 91 17 ba 00 33 01 3a 00 00 03 e8
-// A/IST_FW_KURZ
-00 00 00 0d 00 41 00 2f 00 49 00 53 00 54 00 5f 00 46 00 57 00 5f 00 4b 00 55 00 52 00 5a 00 00
-// GF_STATUS
-00 01 00 09 00 47 00 46 00 5f 00 53 00 54 00 41 00 54 00 55 00 53 00 00
-// ISTWERT1
-00 02 00 08 00 49 00 53 00 54 00 57 00 45 00 52 00 54 00 31 00 00
-// DYN_BESCH3
-00 03 00 0a 00 44 00 59 00 4e 00 5f 00 42 00 45 00 53 00 43 00 48 00 33 00 00
-// ALARMS
-00 04 00 06 00 41 00 4c 00 41 00 52 00 4d 00 53 00 00
-// SKAL2
-00 05 00 05 00 53 00 4b 00 41 00 4c 00 32 00 00
-// DYN_BESCH1
-00 06 00 0a 00 44 00 59 00 4e 00 5f 00 42 00 45 00 53 00 43 00 48 00 31 00 00
-// BESCH3
-00 07 00 06 00 42 00 45 00 53 00 43 00 48 00 33 00 00
-// SKAL3
-00 08 00 05 00 53 00 4b 00 41 00 4c 00 33 00 00
-// SKAL1
-00 09 00 05 00 53 00 4b 00 41 00 4c 00 31 00 00
-// ISTWERT2
-00 0a 00 08 00 49 00 53 00 54 00 57 00 45 00 52 00 54 00 32 00 00
-// GF_NAME
-00 0b 00 07 00 47 00 46 00 5f 00 4e 00 41 00 4d 00 45 00 00
-// ISTWERT3
-00 0c 00 08 00 49 00 53 00 54 00 57 00 45 00 52 00 54 00 33 00 00
-// A/BA
-00 0d 00 04 00 41 00 2f 00 42 00 41 00 00
-// BESCH1
-00 0e 00 06 00 42 00 45 00 53 00 43 00 48 00 31 00 00
-// DYN_BESCH2
-00 0f 00 0a 00 44 00 59 00 4e 00 5f 00 42 00 45 00 53 00 43 00 48 00 32 00 00
-// A/BA_GFES_AUTO
-00 10 00 0e 00 41 00 2f 00 42 00 41 00 5f 00 47 00 46 00 45 00 53 00 5f 00 41 00 55 00 54 00 4f 00 00
-// A/GFE_ALARM
-00 11 00 0b 00 41 00 2f 00 47 00 46 00 45 00 5f 00 41 00 4c 00 41 00 52 00 4d 00 00
-// BESCH2
-00 12 00 06 00 42 00 45 00 53 00 43 00 48 00 32 00 00
-ff ff
-- 04 92 17 bb 00 34 01 3b 00 00 03 e8
-// ISTWERT1
-00 00 00 08 00 49 00 53 00 54 00 57 00 45 00 52 00 54 00 31 00 00
-// A/GFE_ALARM
-00 01 00 0b 00 41 00 2f 00 47 00 46 00 45 00 5f 00 41 00 4c 00 41 00 52 00 4d 00 00
-// A/IST_FW_KURZ
-00 02 00 0d 00 41 00 2f 00 49 00 53 00 54 00 5f 00 46 00 57 00 5f 00 4b 00 55 00 52 00 5a 00 00
-// SKAL1
-00 03 00 05 00 53 00 4b 00 41 00 4c 00 31 00 00
-// ALARMS
-00 04 00 06 00 41 00 4c 00 41 00 52 00 4d 00 53 00 00
-// GF_STATUS
-00 05 00 09 00 47 00 46 00 5f 00 53 00 54 00 41 00 54 00 55 00 53 00 00
-// GF_NAME
-00 06 00 07 00 47 00 46 00 5f 00 4e 00 41 00 4d 00 45 00 00
-// DYN_BESCH1
-00 07 00 0a 00 44 00 59 00 4e 00 5f 00 42 00 45 00 53 00 43 00 48 00 31 00 00
-// A/BA
-00 08 00 04 00 41 00 2f 00 42 00 41 00 00
-// A/A3
-00 09 00 04 00 41 00 2f 00 41 00 33 00 00
-// BESCH1
-00 0a 00 06 00 42 00 45 00 53 00 43 00 48 00 31 00 00
-// A/A2
-00 0b 00 04 00 41 00 2f 00 41 00 32 00 00
-// A/BA_GFES_AUTO
-00 0c 00 0e 00 41 00 2f 00 42 00 41 00 5f 00 47 00 46 00 45 00 53 00 5f 00 41 00 55 00 54 00 4f 00 00
-ff ff
-- 04 93 17 bc 00 35 01 3c 00 00 03 e8
-// ALARMS
-00 00 00 06 00 41 00 4c 00 41 00 52 00 4d 00 53 00 00
-// A/IST_FW_KURZ
-00 01 00 0d 00 41 00 2f 00 49 00 53 00 54 00 5f 00 46 00 57 00 5f 00 4b 00 55 00 52 00 5a 00 00
-// A/BA
-00 02 00 04 00 41 00 2f 00 42 00 41 00 00
-// A/A2
-00 03 00 04 00 41 00 2f 00 41 00 32 00 00
-// GF_STATUS
-00 04 00 09 00 47 00 46 00 5f 00 53 00 54 00 41 00 54 00 55 00 53 00 00
-// A/A1
-00 05 00 04 00 41 00 2f 00 41 00 31 00 00
-ff ff
-- 04
-
-76 37
-```
-
-== 0xB102
-
-```
-fa ce 04 f4 00 02 33 48 00 0b 63 ba 54 80 04 00
-
-1b 02 00 00 00 00 00 07 03 6c 01 96 00 04 00 00
-00 06 00
-01 00 06 01 61 00 06 02 b6 00 06 03 c4
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00
-- 04 00 00 00 00 00 32 01 39 04 90 17 b9
-// ID: 0x0000, Name: BESCH3, 47=Type: Label, Code: 0x000b, Length: 2, Text: DT
-02 00 00 47 00 0b 00 02 00 44 00 54 00 00
-// ID: 0x0001, Name: SKAL1, Type: 24=Skale, 934728, 49696, 1001, 01 (Probably 3 32bit Integers, followed by a flag byte)
-02 00 01 24 00 0e 43 48 00 00 c2 20 00 00 03 e9 01
-// ID: 0x0002, Name: DYN_BESCH1, Type: 47=Label, Code: 0x000b, Length: 2, Text: VL
-02 00 02 47 00 0b 00 02 00 56 00 4c 00 00
-// ID: 0x0003, Name: ISTWERT3, Type: 08=Float (32 bit), Value: 0.0
-02 00 03 08 00 00 00 00
-// ID: 0x0004, Name: GF_STATUS, Type: 63=(Unknown)
-02 00 04 63 02 00 19 c4 2f
-// ID: 0x0005, Name: ALARMS, Type: 76=Alarms (Contains Data-Structure directly related to alarms)
-02 00 05 76 00 6a 05 01 01 00 00 00 08 00 53 00 54 00 4f 00 45 00 52 00 55 00 4e 00 47 00 00 00 39 00 39 00 0f 00 00 2a f1 c6 c4 75 63 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00
-// ID: 0x0006, Name: DYN_BESCH3, Type: 47=Label, Code: 0x0009, Length: 1, Text: T
-02 00 06 47 00 09 00 01 00 54 00 00
-// ID: 0x0007, Name: A/BA, Type: 05=(Boolean?), Value: False
-02 00 07 05 00
-// ID: 0x0008, Name: A/BA_GFES_AUTO, Type: 01=(Boolean?), Value: True
-02 00 08 01 01
-// ID: 0x0009, Name: DYN_BESCH2, Type: Label, Code: 0x0009, Length: 1, Text: T
-02 00 09 47 00 0b 00 02 00 49 00 54 00 00
-// ID: 0x000A, Name: SKAL2, Type: 24=Skale, 934728, 49696, 1001, 01 (Probably 3 32bit Integers, followed by a flag byte)
-02 00 0a 24 00 0e 43 48 00 00 c2 20 00 00 03 e9 01
-// ID: 0x000B, Name: A/GFE_ALARM, Type: 05=(Boolean?), Value: True
-02 00 0b 05 01
-// ID: 0x000C, Name: GF_NAME, Type: 47=Label, Code: 0x0019, Length: 9, Text: PT09ALAC1
-02 00 0c 47 00 19 00 09 00 50 00 54 00 30 00 39 00 41 00 4c 00 41 00 43 00 31 00 00
-// ID: 0x000D, Name: ISTWERT1, Type: 08=Float, Value: 50.416664
-02 00 0d 08 42 49 aa aa
-// ID: 0x000E, Name: A/IST_FW_KURZ, Type: 47=Label, Code: 0x0015, Length: 7, Text: VORLAUF
-02 00 0e 47 00 15 00 07 00 56 00 4f 00 52 00 4c 00 41 00 55 00 46 00 00
-// ID: 0x000F, Name: ISTWERT2, Type: 21=Parametrized Float, Param: 0x80, Value: 50.416664
-02 00 0f 21 80 42 49 aa aa
-// ID: 0x0010, Name: BESCH1, Type: 47=Label, Code: 0x0009, Length: 1, Text: T
-02 00 10 47 00 09 00 01 00 54 00 00
-// ID: 0x0011, Name: SKAL3, Type: 24=Skale, 934560, 0, 1000, 0x01
-02 00 11 24 00 0e 42 a0 00 00 00 00 00 00 03 e8 01
-// ID: 0x0012, Name: BESCH2, Type: 47=Label, Code; 0x0009, Length: 1, Text: T
-02 00 12 47 00 09 00 01 00 54 00 00
-- 01 00 00 00 00 00 33 01 3a 04 91 17 ba
-// ID: 0x0000, Name: A/IST_FW_KURZ, Type: 47=Label, Code: 0x0017, Length: 8, Text: Keine FW
-02 00 00 47 00 17 00 08 00 4b 00 65 00 69 00 6e 00 65 00 20 00 46 00 57 00 00
-// ID: 0x0001, Name: GF_STATUS, Type: 63=(Unknown: Messstellen Status)
-02 00 01 63 00 00 19 c4 2f
-// ID: 0x0002, Name: ISTWERT1, Type: 08=Float (32 bit), Value: 8.923611
-02 00 02 08 41 0e c7 1c
-// ID: 0x0003, Name: DYN_BESCH3, Type: 47=Label, Code: 0x000D, Length: 3, Text: FLU
-02 00 03 47 00 0d 00 03 00 46 00 4c 00 55 00 00
-// ID: 0x0004, Name: ALARMS, Type: 76=Alarms (Contains Data-Structure directly related to alarms)
-02 00 04 76 00 58 05 01 01 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00
-// ID: 0x0005, Name: SKAL2, Type: 24=Skale, 934600, 0, 1088, 00 (Probably 3 32bit Integers, followed by a flag byte)
-02 00 05 24 00 0e 42 c8 00 00 00 00 00 00 04 40 00
-// ID: 0x0006, Name: DYN_BESCH1, Type: 47=Label, Code: 0x000D, Length: 3, Text: F01
-02 00 06 47 00 0d 00 03 00 46 00 30 00 31 00 00
-// ID: 0x0007, Name: BESCH3, Type: 47=Label, Code: 0x0009, Length: 1, Text: W
-02 00 07 47 00 09 00 01 00 57 00 00
-// ID: 0x0008, Name: SKAL3, Type: 24=Skale, 934600, 0, 1088, 00 (Probably 3 32bit Integers, followed by a flag byte)
-02 00 08 24 00 0e 42 c8 00 00 00 00 00 00 04 40 00
-// ID: 0x0009, Name: SKAL1, Type: 24=Skale, 934176, 0, 1349, 01 (Probably 3 32bit Integers, followed by a flag byte)
-02 00 09 24 00 0e 41 20 00 00 00 00 00 00 05 45 01
-// ID: 0x000A, Name: ISTWERT2, Type: 08=Float, Value: -0.000762939453125 (Sort of 0)
-02 00 0a 08 ba 48 00 00
-// ID: 0x000B, Name: GF_NAME, Type: 47=Label, Code: 0x0019, Length: 9, Text: PT09AAHR1
-02 00 0b 47 00 19 00 09 00 50 00 54 00 30 00 39 00 41 00 41 00 48 00 52 00 31 00 00
-// ID: 0x000C, Name: ISTWERT3, Type: 08=Float, Value: 0.0
-02 00 0c 08 00 00 00 00
-// ID: 0x000D, Name: A/BA, Type: 05=(Boolean?), Value: False
-02 00 0d 05 00
-// ID: 0x000E, Name: BESCH1, Type: 47=Label, Code: 0x0009, Length: 1, Text: F
-02 00 0e 47 00 09 00 01 00 46 00 00
-// ID: 0x000F, Name: DYN_BESCH2, Type: 47=Label, Code: 0x000D, Length: 3, Text: FST
-02 00 0f 47 00 0d 00 03 00 46 00 53 00 54 00 00
-// ID: 0x0010, Name: A/BA_GFES_AUTO, Type: 01=(Boolean?), Value: False
-02 00 10 01 00
-// ID: 0x0011, Name: A/GFE_ALARM, Type: 05=(Boolean?), Value: True
-02 00 11 05 01
-// ID: 0x0012, Name: BESCH2, Type: 47=Label, Code: 0x0009, Length: 1, Text: W
-02 00 12 47 00 09 00 01 00 57 00 00
-- 01 00 00 00 00 00 34 01 3b 04 92 17 bb
-// ID: 0x0000, Name: ISTWERT1, Type: 21=Parametrized Float, Param: 0x88, Value: 0.0025000572
-02 00 00 21 88 3b 23 d8 00
-// ID: 0x0001, Name: A/GFE_ALARM, Type: 05=(Boolean?), Value: True
-02 00 01 05 01
-// ID: 0x0002, Name: A/IST_FW_KURZ, Type: 47=Label, Code: 0x0017, Length: 8, Text: Keine FW
-02 00 02 47 00 17 00 08 00 4b 00 65 00 69 00 6e 00 65 00 20 00 46 00 57 00 00
-// ID: 0x0003, Name: SKAL1, Type: 24=Skale, 933760, 49024, 33503, 03 (Probably 3 32bit Integers, followed by a flag byte)
-02 00 03 24 00 0e 3f 80 00 00 bf 80 00 00 82 df 03
-// ID: 0x0004, Name: ALARMS, Type: 76=Alarms (Contains Data-Structure directly related to alarms)
-02 00 04 76 00 76 05 01 01 00 00 00 0e 00 47 00 46 00 45 00 5f 00 56 00 45 00 52 00 52 00 49 00 45 00 47 00 45 00 4c 00 54 00 00 00 54 00 54 01 07 00 00 2a f1 ca d4 71 f6 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00
-// ID: 0x0005, Name: GF_STATUS, Type: 63=(Unknown: Messstellen Status)
-02 00 05 63 00 00 19 c4 2f
-// ID: 0x0006, Name: GF_NAME, Type: 47=Label, Code: 0x0019, Length: 9, Text: PT09AMBM1
-02 00 06 47 00 19 00 09 00 50 00 54 00 30 00 39 00 41 00 4d 00 42 00 4d 00 31 00 00
-// ID: 0x0007, Name: DYN_BESCH1, Type: 47=Label, Code: 0x0007, Length: 0, Text:
-02 00 07 47 00 07 00 00 00 00
-// ID: 0x0008, Name: A/BA, Type: 05=(Boolean?), Value: False
-02 00 08 05 00
-// ID: 0x0009, Name: A/A3, Type: 05=(Boolean?), Value: True
-02 00 09 05 01
-// ID: 0x000a, Name: BESCH1, Type: 47=Label, Code: 0x0009, Length: 1, Text: P
-02 00 0a 47 00 09 00 01 00 50 00 00
-// ID: 0x000b, Name: A/A2, Type: 05=(Boolean?), Value: True
-02 00 0b 05 01
-// ID: 0x000c, Name: A/BA_GFES_AUTO, Type: 01=(Boolean?), Value: False
-02 00 0c 01 00
-- 01 00 00 00 00 00 35 01 3c 04 93 17 bc
-// ID: 0x0000, Name: ALARMS, Type: 76=Alarms (Contains Data-Structure directly related to alarms)
-02 00 00 76 00 76 05 01 01 00 00 00 0e 00 47 00 46 00 45 00 5f 00 56 00 45 00 52 00 52 00 49 00 45 00 47 00 45 00 4c 00 54 00 00 00 54 00 54 00 07 00 00 2a f1 c6 c5 46 ef ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00
-// ID: 0x0001, Name: A/IST_FW_KURZ, Type: 47=Label, Code: 0x0017, Length: 8, Text: Keine FW
-02 00 01 47 00 17 00 08 00 4b 00 65 00 69 00 6e 00 65 00 20 00 46 00 57 00 00
-// ID: 0x0002, Name: A/BA, Type: 05=(Boolean?), Value: False
-02 00 02 05 00
-// ID: 0x0003, Name: A/A2, Type: 05=(Boolean?), Value: False
-02 00 03 05 00
-// ID: 0x0004, Name: GF_STATUS, Type: 63=(Unknown: Messstellen Status)
-02 00 04 63 00 00 19 c4 2f
-// ID: 0x0005, Name: A/A1, Type: 05=(Boolean?), Value: False
-02 00 05 05 00
-- 01
-
-49 ad
-```
-
-== 0x1B01
-
-```
-fa ce 05 7d 00 02 af 0a 00 01 15 e1 54 80 04 00
-
-1b 01 00 00 00 00 00 07 03 6d 01 97 00 04 05 04
-00 08 00 00 00 08 01 78 00 08 02 90 00 08 03 fa
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00
-- 04 96 17 bf 00 38 01 3f 00 00 03 e8
-// A/IST_FW_KURZ
-00 00 00 0d 00 41 00 2f 00 49 00 53 00 54 00 5f 00 46 00 57 00 5f 00 4b 00 55 00 52 00 5a 00 00
-// SKAL1
-00 01 00 05 00 53 00 4b 00 41 00 4c 00 31 00 00
-// ALARMS
-00 02 00 06 00 41 00 4c 00 41 00 52 00 4d 00 53 00 00
-// SKAL2
-00 03 00 05 00 53 00 4b 00 41 00 4c 00 32 00 00
-// DYN_BESCH2
-00 04 00 0a 00 44 00 59 00 4e 00 5f 00 42 00 45 00 53 00 43 00 48 00 32 00 00
-// AKT_SCHRITT
-00 05 00 0b 00 41 00 4b 00 54 00 5f 00 53 00 43 00 48 00 52 00 49 00 54 00 54 00 00
-// A/BA_GFES_AUTO
-00 06 00 0e 00 41 00 2f 00 42 00 41 00 5f 00 47 00 46 00 45 00 53 00 5f 00 41 00 55 00 54 00 4f 00 00
-// A/BA
-00 07 00 04 00 41 00 2f 00 42 00 41 00 00
-// GF_STATUS
-00 08 00 09 00 47 00 46 00 5f 00 53 00 54 00 41 00 54 00 55 00 53 00 00
-// ISTWERT2
-00 09 00 08 00 49 00 53 00 54 00 57 00 45 00 52 00 54 00 32 00 00
-// GF_NAME
-00 0a 00 07 00 47 00 46 00 5f 00 4e 00 41 00 4d 00 45 00 00
-// BESCH1
-00 0b 00 06 00 42 00 45 00 53 00 43 00 48 00 31 00 00
-// DYN_BESCH1
-00 0c 00 0a 00 44 00 59 00 4e 00 5f 00 42 00 45 00 53 00 43 00 48 00 31 00 00
-// BESCH2
-00 0d 00 06 00 42 00 45 00 53 00 43 00 48 00 32 00 00
-// A/GFE_ALARM
-00 0e 00 0b 00 41 00 2f 00 47 00 46 00 45 00 5f 00 41 00 4c 00 41 00 52 00 4d 00 00
-// ISTWERT1
-00 0f 00 08 00 49 00 53 00 54 00 57 00 45 00 52 00 54 00 31 00 00
-ff ff
-- 04 97 17 c0 00 39 01 40 00 00 03 e8
-// ALARMS
-00 00 00 06 00 41 00 4c 00 41 00 52 00 4d 00 53 00 00
-// SKAL1
-00 01 00 05 00 53 00 4b 00 41 00 4c 00 31 00 00
-// GF_STATUS
-00 02 00 09 00 47 00 46 00 5f 00 53 00 54 00 41 00 54 00 55 00 53 00 00
-// BESCH1
-00 03 00 06 00 42 00 45 00 53 00 43 00 48 00 31 00 00
-// A/A1
-00 04 00 04 00 41 00 2f 00 41 00 31 00 00
-// A/IST_FW_KURZ
-00 05 00 0d 00 41 00 2f 00 49 00 53 00 54 00 5f 00 46 00 57 00 5f 00 4b 00 55 00 52 00 5a 00 00
-// DYN_BESCH1
-00 06 00 0a 00 44 00 59 00 4e 00 5f 00 42 00 45 00 53 00 43 00 48 00 31 00 00
-// GF_NAME
-00 07 00 07 00 47 00 46 00 5f 00 4e 00 41 00 4d 00 45 00 00
-// A/BA
-00 08 00 04 00 41 00 2f 00 42 00 41 00 00
-// A/GFE_ALARM
-00 09 00 0b 00 41 00 2f 00 47 00 46 00 45 00 5f 00 41 00 4c 00 41 00 52 00 4d 00 00
-// A/BA_GFES_AUTO
-00 0a 00 0e 00 41 00 2f 00 42 00 41 00 5f 00 47 00 46 00 45 00 53 00 5f 00 41 00 55 00 54 00 4f 00 00
-// ISTWERT1
-00 0b 00 08 00 49 00 53 00 54 00 57 00 45 00 52 00 54 00 31 00 00
-ff ff
-- 04 98 17 c1 00 3a 01 41 00 00 03 e8
-// SKAL2
-00 00 00 05 00 53 00 4b 00 41 00 4c 00 32 00 00
-// ISTWERT1
-00 01 00 08 00 49 00 53 00 54 00 57 00 45 00 52 00 54 00 31 00 00
-// GF_STATUS
-00 02 00 09 00 47 00 46 00 5f 00 53 00 54 00 41 00 54 00 55 00 53 00 00
-// SKAL1
-00 03 00 05 00 53 00 4b 00 41 00 4c 00 31 00 00
-// A/A1
-00 04 00 04 00 41 00 2f 00 41 00 31 00 00
-// ALARMS
-00 05 00 06 00 41 00 4c 00 41 00 52 00 4d 00 53 00 00
-// A/GFE_ALARM
-00 06 00 0b 00 41 00 2f 00 47 00 46 00 45 00 5f 00 41 00 4c 00 41 00 52 00 4d 00 00
-// GF_NAME
-00 07 00 07 00 47 00 46 00 5f 00 4e 00 41 00 4d 00 45 00 00
-// A/BA
-00 08 00 04 00 41 00 2f 00 42 00 41 00 00
-// DYN_BESCH2
-00 09 00 0a 00 44 00 59 00 4e 00 5f 00 42 00 45 00 53 00 43 00 48 00 32 00 00
-// BESCH2
-00 0a 00 06 00 42 00 45 00 53 00 43 00 48 00 32 00 00
-// BESCH1
-00 0b 00 06 00 42 00 45 00 53 00 43 00 48 00 31 00 00
-// ISTWERT2
-00 0c 00 08 00 49 00 53 00 54 00 57 00 45 00 52 00 54 00 32 00 00
-// A/BA_GFES_AUTO
-00 0d 00 0e 00 41 00 2f 00 42 00 41 00 5f 00 47 00 46 00 45 00 53 00 5f 00 41 00 55 00 54 00 4f 00 00
-// DYN_BESCH1
-00 0e 00 0a 00 44 00 59 00 4e 00 5f 00 42 00 45 00 53 00 43 00 48 00 31 00 00
-// A/IST_FW_KURZ
-00 0f 00 0d 00 41 00 2f 00 49 00 53 00 54 00 5f 00 46 00 57 00 5f 00 4b 00 55 00 52 00 5a 00 00
-ff ff
-- 04 99 17 c2 00 3b 01 42 00 00 03 e8
-// BESCH1
-00 00 00 06 00 42 00 45 00 53 00 43 00 48 00 31 00 00
-// SKAL1
-00 01 00 05 00 53 00 4b 00 41 00 4c 00 31 00 00
-// A/BA_GFES_AUTO
-00 02 00 0e 00 41 00 2f 00 42 00 41 00 5f 00 47 00 46 00 45 00 53 00 5f 00 41 00 55 00 54 00 4f 00 00
-// GF_NAME
-00 03 00 07 00 47 00 46 00 5f 00 4e 00 41 00 4d 00 45 00 00
-// A/GFE_ALARM
-00 04 00 0b 00 41 00 2f 00 47 00 46 00 45 00 5f 00 41 00 4c 00 41 00 52 00 4d 00 00
-// A/IST_FW_KURZ
-00 05 00 0d 00 41 00 2f 00 49 00 53 00 54 00 5f 00 46 00 57 00 5f 00 4b 00 55 00 52 00 5a 00 00
-// ALARMS
-00 06 00 06 00 41 00 4c 00 41 00 52 00 4d 00 53 00 00
-// A/BA
-00 07 00 04 00 41 00 2f 00 42 00 41 00 00
-// GF_STATUS
-00 08 00 09 00 47 00 46 00 5f 00 53 00 54 00 41 00 54 00 55 00 53 00 00
-// DYN_BESCH1
-00 09 00 0a 00 44 00 59 00 4e 00 5f 00 42 00 45 00 53 00 43 00 48 00 31 00 00
-// ISTWERT1
-00 0a 00 08 00 49 00 53 00 54 00 57 00 45 00 52 00 54 00 31 00 00
-ff ff
-- 04
-
-b2 c7
-```
-
-== 0xB102
-
-```
-fa ce 04 b6 00 02 33 49 00 0b 63 bb 54 80 04 00
-
-1b 02 00 00 00 00 00 07 03 6d 01 97 00 04 00 00
-00 06 00
-01 00 06 01 51 00 06 02 3c 00 06 03 59
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00
-- 04 00 00 00 00 00 38 01 3f 04 96 17 bf
-02 00 00 47 00 17 00 08 00 4b 00 65 00 69 00 6e 00 65 00 20 00 46 00 57 00 00
-02 00 01 24 00 0e 43 48 00 00 c2 20 00 00 03 e9 01
-02 00 02 76 00 76 05 01 01 00 00 00 0e 00 47 00 46 00 45 00 5f 00 56 00 45 00 52 00 52 00 49 00 45 00 47 00 45 00 4c 00 54 00 00 00 54 00 54 01 07 00 00 2a f1 c7 82 e4 d8 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00
-02 00 03 24 00 0e 40 20 00 00 00 00 00 00 80 16 03
-02 00 04 47 00 11 00 05 00 4d 00 43 00 50 00 30 00 31 00 00
-02 00 05 47 00 07 00 00 00 00
-02 00 06 01 00
-02 00 07 05 00
-02 00 08 63 00 00 19 c4 2f
-02 00 09 08 3f 89 68 4c
-02 00 0a 47 00 19 00 09 00 50 00 54 00 30 00 39 00 41 00 4e 00 41 00 44 00 31 00 00
-02 00 0b 47 00 09 00 01 00 54 00 00
-02 00 0c 47 00 11 00 05 00 4d 00 43 00 54 00 30 00 31 00 00
-02 00 0d 47 00 09 00 01 00 50 00 00
-02 00 0e 05 01
-02 00 0f 08 42 49 aa aa
-- 01 00 00 00 00 00 39 01 40 04 97 17 c0
-02 00 00 76 00 58 05 01 01 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00
-02 00 01 24 00 0e 41 28 00 00 00 00 00 00 05 45 01
-02 00 02 63 00 00 19 c4 2f
-02 00 03 47 00 09 00 01 00 46 00 00
-02 00 04 05 01
-02 00 05 47 00 17 00 08 00 4b 00 65 00 69 00 6e 00 65 00 20 00 46 00 57 00 00
-02 00 06 47 00 07 00 00 00 00
-02 00 07 47 00 19 00 09 00 50 00 54 00 30 00 39 00 41 00 44 00 42 00 51 00 31 00 00
-02 00 08 05 00
-02 00 09 05 01
-02 00 0a 01 00
-02 00 0b 21 80 00 00 00 00
-- 01 00 00 00 00 00 3a 01 41 04 98 17 c1
-02 00 00 24 00 0e 42 c8 00 00 00 00 00 00 06 34 00
-02 00 01 08 3f 7f ff ff
-02 00 02 63 00 00 19 c4 2f
-02 00 03 24 00 0e 3f 99 99 9a 00 00 00 00 80 16 03
-02 00 04 05 01
-02 00 05 76 00 58 05 01 01 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00
-02 00 06 05 00
-02 00 07 47 00 19 00 09 00 50 00 54 00 30 00 39 00 41 00 44 00 48 00 4f 00 31 00 00
-02 00 08 05 00
-02 00 09 47 00 07 00 00 00 00
-02 00 0a 47 00 07 00 00 00 00
-02 00 0b 47 00 09 00 01 00 50 00 00
-02 00 0c 08 00 00 00 00
-02 00 0d 01 01
-02 00 0e 47 00 0d 00 03 00 56 00 41 00 4b 00 00
-02 00 0f 47 00 17 00 08 00 4b 00 65 00 69 00 6e 00 65 00 20 00 46 00 57 00 00
-- 01 00 00 00 00 00 3b 01 42 04 99 17 c2
-02 00 00 47 00 09 00 01 00 46 00 00
-02 00 01 24 00 0e 41 20 00 00 00 00 00 00 05 45 01
-02 00 02 01 00
-02 00 03 47 00 19 00 09 00 50 00 54 00 30 00 39 00 41 00 41 00 4e 00 4b 00 31 00 00
-02 00 04 05 01
-02 00 05 47 00 17 00 08 00 4b 00 65 00 69 00 6e 00 65 00 20 00 46 00 57 00 00
-02 00 06 76 00 58 05 01 01 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00
-02 00 07 05 00
-02 00 08 63 00 00 19 c4 2f
-02 00 09 47 00 07 00 00 00 00
-02 00 0a 08 00 00 00 00
-- 01
-
-b0 25
-```
-
-== 0xB101
-
-```
-fa ce 05 89 00 02 af 0c 00 01 15 e3 54 80 04 00
-
-1b 01 00 00 00 00 00 07 03 6e 01 98 00 04 05 10
-00 08 00 00 00 08 00 5a 00 08 01 e0 00 08 04 d8
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00
-- 04 93 17 bc 00 35 01 3c 00 00 03 e8
-// A/BA_GFES_AUTO
-00 06 00 0e 00 41 00 2f 00 42 00 41 00 5f 00 47 00 46 00 45 00 53 00 5f 00 41 00 55 00 54 00 4f 00 00
-// A/GFE_ALARM
-00 07 00 0b 00 41 00 2f 00 47 00 46 00 45 00 5f 00 41 00 4c 00 41 00 52 00 4d 00 00
-// A/A3
-00 08 00 04 00 41 00 2f 00 41 00 33 00 00
-ff ff
-- 04 94 17 bd 00 36 01 3d 00 00 03 e8
-// BESCH2
-00 00 00 06 00 42 00 45 00 53 00 43 00 48 00 32 00 00
-// SKAL1
-00 01 00 05 00 53 00 4b 00 41 00 4c 00 31 00 00
-// ALARMS
-00 02 00 06 00 41 00 4c 00 41 00 52 00 4d 00 53 00 00
-// A/BA_GFES_AUTO
-00 03 00 0e 00 41 00 2f 00 42 00 41 00 5f 00 47 00 46 00 45 00 53 00 5f 00 41 00 55 00 54 00 4f 00 00
-00 04 00 09 00 47 00 46 00 5f 00 53 00 54 00 41 00 54 00 55 00 53 00 00
-// SKAL2
-00 05 00 05 00 53 00 4b 00 41 00 4c 00 32 00 00
-// DYN_BESCH1
-00 06 00 0a 00 44 00 59 00 4e 00 5f 00 42 00 45 00 53 00 43 00 48 00 31 00 00
-// A/GFE_ALARM
-00 07 00 0b 00 41 00 2f 00 47 00 46 00 45 00 5f 00 41 00 4c 00 41 00 52 00 4d 00 00
-// DYN_BESCH2
-00 08 00 0a 00 44 00 59 00 4e 00 5f 00 42 00 45 00 53 00 43 00 48 00 32 00 00
-// ISTWERT2
-00 09 00 08 00 49 00 53 00 54 00 57 00 45 00 52 00 54 00 32 00 00
-// A/A1
-00 0a 00 04 00 41 00 2f 00 41 00 31 00 00
-// BESCH1
-00 0b 00 06 00 42 00 45 00 53 00 43 00 48 00 31 00 00
-// GF_NAME
-00 0c 00 07 00 47 00 46 00 5f 00 4e 00 41 00 4d 00 45 00 00
-// A/BA
-00 0d 00 04 00 41 00 2f 00 42 00 41 00 00
-// A/IST_FW_KURZ
-00 0e 00 0d 00 41 00 2f 00 49 00 53 00 54 00 5f 00 46 00 57 00 5f 00 4b 00 55 00 52 00 5a 00 00
-// AKT_SCHRITT
-00 0f 00 0b 00 41 00 4b 00 54 00 5f 00 53 00 43 00 48 00 52 00 49 00 54 00 54 00 00
-// ISTWERT1
-00 10 00 08 00 49 00 53 00 54 00 57 00 45 00 52 00 54 00 31 00 00
-ff ff
-- 04 95 17 be 00 37 01 3e 00 00 03 e8
-// DYN_ISTWERTE/OUT_FARBE1
-00 00 00 17 00 44 00 59 00 4e 00 5f 00 49 00 53 00 54 00 57 00 45 00 52 00 54 00 45 00 2f 00 4f 00 55 00 54 00 5f 00 46 00 41 00 52 00 42 00 45 00 31 00 00
-// DYN_ISTWERTE/OUT_ENABLED2
-00 01 00 19 00 44 00 59 00 4e 00 5f 00 49 00 53 00 54 00 57 00 45 00 52 00 54 00 45 00 2f 00 4f 00 55 00 54 00 5f 00 45 00 4e 00 41 00 42 00 4c 00 45 00 44 00 32 00 00
-// GFE_ALARM
-00 02 00 09 00 47 00 46 00 45 00 5f 00 41 00 4c 00 41 00 52 00 4d 00 00
-// DYN_ISTWERTE/BESCH1
-00 03 00 13 00 44 00 59 00 4e 00 5f 00 49 00 53 00 54 00 57 00 45 00 52 00 54 00 45 00 2f 00 42 00 45 00 53 00 43 00 48 00 31 00 00
-// GF_STATUS
-00 04 00 09 00 47 00 46 00 5f 00 53 00 54 00 41 00 54 00 55 00 53 00 00
-// DYN_ISTWERTE/BESCH2
-00 05 00 13 00 44 00 59 00 4e 00 5f 00 49 00 53 00 54 00 57 00 45 00 52 00 54 00 45 00 2f 00 42 00 45 00 53 00 43 00 48 00 32 00 00
-// IST_FW_KURZ
-00 06 00 0b 00 49 00 53 00 54 00 5f 00 46 00 57 00 5f 00 4b 00 55 00 52 00 5a 00 00
-// ALARMS
-00 07 00 06 00 41 00 4c 00 41 00 52 00 4d 00 53 00 00
-// DYN_ISTWERTE/DYN_BESCH2
-00 08 00 17 00 44 00 59 00 4e 00 5f 00 49 00 53 00 54 00 57 00 45 00 52 00 54 00 45 00 2f 00 44 00 59 00 4e 00 5f 00 42 00 45 00 53 00 43 00 48 00 32 00 00
-// DYN_ISTWERTE/OUT_FARBE2
-00 09 00 17 00 44 00 59 00 4e 00 5f 00 49 00 53 00 54 00 57 00 45 00 52 00 54 00 45 00 2f 00 4f 00 55 00 54 00 5f 00 46 00 41 00 52 00 42 00 45 00 32 00 00
-// DYN_ISTWERTE/OUT_SCALE1
-00 0a 00 17 00 44 00 59 00 4e 00 5f 00 49 00 53 00 54 00 57 00 45 00 52 00 54 00 45 00 2f 00 4f 00 55 00 54 00 5f 00 53 00 43 00 41 00 4c 00 45 00 31 00 00
-// BA_GFES_AUTO
-00 0b 00 0c 00 42 00 41 00 5f 00 47 00 46 00 45 00 53 00 5f 00 41 00 55 00 54 00 4f 00 00
-// BA
-00 0c 00 02 00 42 00 41 00 00
-// DYN_ISTWERTE/OUT2
-00 0d 00 11 00 44 00 59 00 4e 00 5f 00 49 00 53 00 54 00 57 00 45 00 52 00 54 00 45 00 2f 00 4f 00 55 00 54 00 32 00 00
-// DYN_ISTWERTE/OUT_SCALE2
-00 0e 00 17 00 44 00 59 00 4e 00 5f 00 49 00 53 00 54 00 57 00 45 00 52 00 54 00 45 00 2f 00 4f 00 55 00 54 00 5f 00 53 00 43 00 41 00 4c 00 45 00 32 00 00
-// DYN_ISTWERTE/OUT_ENABLED1
-00 0f 00 19 00 44 00 59 00 4e 00 5f 00 49 00 53 00 54 00 57 00 45 00 52 00 54 00 45 00 2f 00 4f 00 55 00 54 00 5f 00 45 00 4e 00 41 00 42 00 4c 00 45 00 44 00 31 00 00
-// DYN_BEZ
-00 10 00 07 00 44 00 59 00 4e 00 5f 00 42 00 45 00 5a 00 00
-// DYN_ISTWERTE/OUT1
-00 11 00 17 00 44 00 59 00 4e 00 5f 00 49 00 53 00 54 00 57 00 45 00 52 00 54 00 45 00 2f 00 44 00 59 00 4e 00 5f 00 42 00 45 00 53 00 43 00 48 00 31 00 00
-// DYN_ISTWERTE/OUT1
-00 12 00 11 00 44 00 59 00 4e 00 5f 00 49 00 53 00 54 00 57 00 45 00 52 00 54 00 45 00 2f 00 4f 00 55 00 54 00 31 00 00
-ff ff
-- 04 9a 17 c3 00 3c 01 43 00 00 03 e8
-// ALARMS
-00 00 00 06 00 41 00 4c 00 41 00 52 00 4d 00 53 00 00
-// GF_STATUS
-00 01 00 09 00 47 00 46 00 5f 00 53 00 54 00 41 00 54 00 55 00 53 00 00
-ff ff
-- 04
-
-ea 72
-```
-
-== 0xB102
-
-```
-fa ce 03 6c 00 02 33 4b 00 0b 63 bd 54 80 04 00
-1b 02 00 00 00 01 00 07 03 6e 01 98 00 04 00 00
-00 06 00 01 00 06 00 1d 00 06 01 52 00 06 02 83
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00
-- 04 00 00 00 00 00 35 01 3c 04 93 17 bc
-02 00 06 01 00
-02 00 07 05 01
-02 00 08 05 01
-- 01 00 00 00 00 00 36 01 3d 04 94 17 bd
-02 00 00 47 00 09 00 01 00 50 00 00
-02 00 01 24 00 0e 45 35 40 00 00 00 00 00 82 dc 00
-02 00 02 76 00 58 05 01 01 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00
-02 00 03 01 01
-02 00 04 63 00 00 19 c4 2f
-02 00 05 24 00 0e 43 c8 00 00 c2 c8 00 00 82 dd 01
-02 00 06 47 00 07 00 00 00 00
-02 00 07 05 01
-02 00 08 47 00 11 00 05 00 44 00 52 00 55 00 43 00 4b 00 00
-02 00 09 21 88 c2 20 00 00
-02 00 0a 05 01
-02 00 0b 47 00 09 00 01 00 53 00 00
-02 00 0c 47 00 19 00 09 00 50 00 54 00 30 00 39 00 41 00 44 00 47 00 4f 00 31 00 00
-02 00 0d 05 00
-02 00 0e 47 00 17 00 08 00 4b 00 65 00 69 00 6e 00 65 00 20 00 46 00 57 00 00
-02 00 0f 47 00 0d 00 03 00 41 00 75 00 73 00 00
-02 00 10 21 80 00 00 00 00
-- 01 00 00 00 00 00 37 01 3e 04 95 17 be
-02 00 00 05 00
-02 00 01 01 01
-02 00 02 05 00
-02 00 03 47 00 09 00 01 00 54 00 00
-02 00 04 63 00 00 19 c4 2f
-02 00 05 47 00 09 00 01 00 54 00 00
-02 00 06 63 64 00 19 b9 88
-02 00 07 76 00 6a 05 01 01 00 00 00 08 00 53 00 54 00 4f 00 45 00 52 00 55 00 4e 00 47 00 00 00 39 00 39 00 0f 00 00 2a f1 c6 c4 7a 4f ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00
-02 00 08 47 00 0b 00 02 00 52 00 4c 00 00
-02 00 09 05 00
-02 00 0a 24 00 0e 43 48 00 00 c2 20 00 00 03 e9 01
-02 00 0b 01 00
-02 00 0c 05 00
-02 00 0d 08 41 a0 8e 39
-02 00 0e 24 00 0e 43 48 00 00 c2 20 00 00 03 e9 01
-02 00 0f 01 01
-02 00 10 47 00 19 00 09 00 50 00 54 00 30 00 39 00 41 00 4c 00 42 00 43 00 31 00 00
-02 00 11 47 00 0b 00 02 00 56 00 4c 00 00
-02 00 12 08 41 a0 8e 39 01 00 00 00 00 00 3c 01 43 04 9a 17 c3 02 00 00 76 00 58 05 01 01 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 02 00 01 63 00 00 19 c4 2f
-- 01
-
-16 0b
-```
-
-== 0xB101
-
-```
-fa ce 02 a1 00 02 af 0e 00 01 15 e5 54 80 04 00
-
-1b 01 00 00 00 00 00 07 03 6f 01 99 00 04 02 28
-00 08 00 00 00 08 00 7a 00 08 01 84 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00
-- 04 9a 17 c3 00 3c 01 43 00 00 03 e8
-// A/IST_FW_KURZ
-00 02 00 0d 00 41 00 2f 00 49 00 53 00 54 00 5f 00 46 00 57 00 5f 00 4b 00 55 00 52 00 5a 00 00
-// A/BA
-00 03 00 04 00 41 00 2f 00 42 00 41 00 00
-// A/BA_GFES_AUTO
-00 04 00 0e 00 41 00 2f 00 42 00 41 00 5f 00 47 00 46 00 45 00 53 00 5f 00 41 00 55 00 54 00 4f 00 00
-// A/GFE_ALARM
-00 05 00 0b 00 41 00 2f 00 47 00 46 00 45 00 5f 00 41 00 4c 00 41 00 52 00 4d 00 00
-ff ff
-- 04 9b 17 c4 00 3d 01 44 00 00 03 e8
-// GF_STATUS
-00 00 00 09 00 47 00 46 00 5f 00 53 00 54 00 41 00 54 00 55 00 53 00 00
-// ALARMS
-00 01 00 06 00 41 00 4c 00 41 00 52 00 4d 00 53 00 00
-// BESCH1
-00 02 00 06 00 42 00 45 00 53 00 43 00 48 00 31 00 00
-// SKAL1
-00 03 00 05 00 53 00 4b 00 41 00 4c 00 31 00 00
-// DYN_BESCH1
-00 04 00 0a 00 44 00 59 00 4e 00 5f 00 42 00 45 00 53 00 43 00 48 00 31 00 00
-// A/BA_GFES_AUTO
-00 05 00 0e 00 41 00 2f 00 42 00 41 00 5f 00 47 00 46 00 45 00 53 00 5f 00 41 00 55 00 54 00 4f 00 00
-// A/IST_FW_KURZ
-00 06 00 0d 00 41 00 2f 00 49 00 53 00 54 00 5f 00 46 00 57 00 5f 00 4b 00 55 00 52 00 5a 00 00
-// ISTWERT1
-00 07 00 08 00 49 00 53 00 54 00 57 00 45 00 52 00 54 00 31 00 00
-// A/BA
-00 08 00 04 00 41 00 2f 00 42 00 41 00 00
-// GF_NAME
-00 09 00 07 00 47 00 46 00 5f 00 4e 00 41 00 4d 00 45 00 00
-// A/GFE_ALARM
-00 0a 00 0b 00 41 00 2f 00 47 00 46 00 45 00 5f 00 41 00 4c 00 41 00 52 00 4d 00 00
-ff ff
-- 04 9c 17 c5 00 3e 01 45 00 00 03 e8
-// A/BA_GFES_AUTO
-00 00 00 0e 00 41 00 2f 00 42 00 41 00 5f 00 47 00 46 00 45 00 53 00 5f 00 41 00 55 00 54 00 4f 00 00
-// GF_STATUS
-00 01 00 09 00 47 00 46 00 5f 00 53 00 54 00 41 00 54 00 55 00 53 00 00
-// A/BA
-00 02 00 04 00 41 00 2f 00 42 00 41 00 00
-// ALARMS
-00 03 00 06 00 41 00 4c 00 41 00 52 00 4d 00 53 00 00
-// A/IST_FW_KURZ
-00 04 00 0d 00 41 00 2f 00 49 00 53 00 54 00 5f 00 46 00 57 00 5f 00 4b 00 55 00 52 00 5a 00 00
-// A/GFE_ALARM
-00 05 00 0b 00 41 00 2f 00 47 00 46 00 45 00 5f 00 41 00 4c 00 41 00 52 00 4d 00 00
-ff ff
-- 03
-
-7d 1c
-```
-
-== 0xB102
-
-```
-fa ce 02 4d 00 02 33 4e 00 0b 63 c0 54 80 04 00
-
-1b 02 00 00 00 00 00 07 03 6f 01 99 00 04 00 00
-00 06 00 01 00 06 00 37 00 06 01 3b 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00
-- 03 00 00 00 00 00 3c 01 43 04 9a 17 c3
-02 00 02 47 00 17 00 08 00 4b 00
-65 00 69 00 6e 00 65 00 20 00 46 00 57 00 00
-02 00 03 05 00
-02 00 04 01 00
-02 00 05 05 01
-- 01 00 00 00 00 00 3d 01 44 04 9b 17 c4
-02 00 00 63 00 00 19 c4 2f
-02 00 01 76 00 76 05 01 01 00 00 00 0e 00 47 00 46 00 45 00 5f 00 56 00 45 00 52 00 52 00 49 00 45 00 47 00 45 00 4c 00 54 00 00 00 54 00 54 00 07 00 00 2a f1 c6 c4 e1 1f ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00
-02 00 02 47 00 09 00 01 00 53 00 00
-02 00 03 24 00 0e 41 20 00 00 00 00 00 00 82 dc 02
-02 00 04 47 00 07 00 00 00 00
-02 00 05 01 00
-02 00 06 47 00 17 00 08 00 4b 00 65 00 69 00 6e 00 65 00 20 00 46 00 57 00 00
-02 00 07 21 80 00 00 00 00
-02 00 08 05 00
-02 00 09 47 00 19 00 09 00 50 00 54 00 30 00 39 00 41 00 48 00 45 00 44 00 31 00 00
-02 00 0a 05 01
-- 01 00 00 00 00 00 3e 01 45 04 9c 17 c5
-02 00 00 01 00
-02 00 01 63 00 00 19 c4 2f
-02 00 02 05 00
-02 00 03 76 00 58 05 01 01 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00
-02 00 04 47 00 17 00 08 00 4b 00 65 00 69 00 6e 00 65 00 20 00 46 00 57 00 00
-02 00 05 05 01
-- 01
-
-6d cc
-```
-
-== 0x0403 (after registration)
-
-```
-fa ce 02 a5 00 02 33 50 00 0b 63 cb 54 80 04 00
-
-04 03 00 00 00 01 00 52 00 00 00 00 00 00 00 00
-00 04 00 00 00 08 00 01 00 00 00 00
-- 05 04 8f 17 b8 00 32 01 39 04 90 17 b9
-02 00 01 24 00 0e 43 48 00 00 c2 20 00 00 03 e9 01
-02 00 03 08 00 00 00 00
-02 00 0a 24 00 0e 43 48 00 00 c2 20 00 00 03 e9 01
-02 00 0d 08 42 49 aa aa
-02 00 0f 21 80 42 49 aa aa
-02 00 11 24 00 0e 42 a0 00 00 00 00 00 00 03 e8 01
-- 01 00 33 01 3a 04 91 17 ba
-02 00 02 08 41 0e c7 1c
-02 00 05 24 00 0e 42 c8 00 00 00 00 00 00 04 40 00
-02 00 08 24 00 0e 42 c8 00 00 00 00 00 00 04 40 00
-02 00 09 24 00 0e 41 20 00 00 00 00 00 00 05 45 01
-02 00 0a 08 ba 48 00 00
-02 00 0c 08 00 00 00 00
-- 01 00 34 01 3b 04 92 17 bb
-02 00 00 21 88 3b 23 d8 00
-02 00 03 24 00 0e 3f 80 00 00 bf 80 00 00 82 df 03
-- 01 00 38 01 3f 04 96 17 bf
-02 00 01 24 00 0e 43 48 00 00 c2 20 00 00 03 e9 01
-02 00 02 76 00 76 05 01 01 00 00 00 0e 00 47 00 46 00 45 00 5f 00 56 00 45 00 52 00 52 00 49 00 45 00 47 00 45 00 4c 00 54 00 00 00 54 00 54 01 07 00 00 2a f1 c7 82 e4 d8 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00
-02 00 03 24 00 0e 40 20 00 00 00 00 00 00 80 16 03
-02 00 09 08 3f 89 68 4c
-02 00 0f 08 42 49 aa aa
-- 01 00 39 01 40 04 97 17 c0
-02 00 01 24 00 0e 41 28 00 00 00 00 00 00 05 45 01
-02 00 0b 21 80 00 00 00 00
-- 01 00 3a 01 41 04 98 17 c1
-02 00 00 24 00 0e 42 c8 00 00 00 00 00 00 06 34 00
-02 00 01 08 3f 7f ff ff
-02 00 03 24 00 0e 3f 99 99 9a 00 00 00 00 80 16 03
-02 00 0c 08 00 00 00 00
-- 01 00 3b 01 42 04 99 17 c2
-02 00 01 24 00 0e 41 20 00 00 00 00 00 00 05 45 01
-02 00 0a 08 00 00 00 00
-- 01 00 36 01 3d 04 94 17 bd
-02 00 01 24 00 0e 45 35 40 00 00 00 00 00 82 dc 00
-02 00 05 24 00 0e 43 c8 00 00 c2 c8 00 00 82 dd 01
-02 00 07 05 01
-02 00 09 21 88 c2 20 00 00
-02 00 10 21 80 00 00 00 00
-- 01 00 37 01 3e 04 95 17 be
-02 00 06 63 64 00 19 b9 88
-02 00 0c 05 00
-- 01 00 3d 01 44 04 9b 17 c4
-02 00 03 24 00 0e 41 20 00 00 00 00 00 00 82 dc 02
-02 00 07 21 80 00 00 00 00
-- 01 00 00 00 00 00 00 00 00
-
-be ff
-```
-
-```
-fa ce 02 27 00 02 33 55 00 0b 63 df 54 80 04 00
-
-04 03 00 00 00 00 00 52 00 00 00 00 00 00 00 00
-00 04 00 00 00 08 00 01 00 00 00 00
-- 06 04 8f 17 b8 00 32 01 39 04 90 17 b9
-02 00 01 24 00 0e 43 48 00 00 c2 20 00 00 03 e9 01
-02 00 03 08 00 00 00 00
-02 00 0a 24 00 0e 43 48 00 00 c2 20 00 00 03 e9 01
-02 00 0d 08 42 49 aa aa
-02 00 0f 21 80 42 49 aa aa
-02 00 11 24 00 0e 42 a0 00 00 00 00 00 00 03 e8 01
-- 01 00 33 01 3a 04 91 17 ba
-02 00 02 08 41 0e c7 1c
-02 00 05 24 00 0e 42 c8 00 00 00 00 00 00 04 40 00
-02 00 08 24 00 0e 42 c8 00 00 00 00 00 00 04 40 00
-02 00 09 24 00 0e 41 20 00 00 00 00 00 00 05 45 01
-02 00 0a 08 ba 48 00 00
-02 00 0c 08 00 00 00 00
-- 01 00 34 01 3b 04 92 17 bb
-02 00 00 21 88 3b 23 d8 00
-02 00 03 24 00 0e 3f 80 00 00 bf 80 00 00 82 df 03
-- 01 00 38 01 3f 04 96 17 bf
-02 00 01 24 00 0e 43 48 00 00 c2 20 00 00 03 e9 01
-02 00 03 24 00 0e 40 20 00 00 00 00 00 00 80 16 03
-02 00 09 08 3f 89 68 4c
-02 00 0f 08 42 49 aa aa
-- 01 00 39 01 40 04 97 17 c0
-02 00 01 24 00 0e 41 28 00 00 00 00 00 00 05 45 01
-02 00 0b 21 80 00 00 00 00 01 00 3a 01 41 04 98 17 c1
-02 00 00 24 00 0e 42 c8 00 00 00 00 00 00 06 34 00
-02 00 01 08 3f 7f ff ff
-02 00 03 24 00 0e 3f 99 99 9a 00 00 00 00 80 16 03
-02 00 0c 08 00 00 00 00
-- 01 00 3b 01 42 04 99 17 c2
-02 00 01 24 00 0e 41 20 00 00 00 00 00 00 05 45 01
-02 00 0a 08 00 00 00 00 01 00 36 01 3d 04 94 17 bd
-02 00 01 24 00 0e 45 35 40 00 00 00 00 00 82 dc 00
-02 00 05 24 00 0e 43 c8 00 00 c2 c8 00 00 82 dd 01
-02 00 09 21 88 c2 20 00 00
-02 00 10 21 80 00 00 00 00
-- 01 00 37 01 3e 04 95 17 be
-02 00 06 63 64 00 19 b9 88
-02 00 0c 05 00 01 00 3d 01 44 04 9b 17 c4
-02 00 03 24 00 0e 41 20 00 00 00 00 00 00 82 dc 02
-02 00 07 21 80 00 00 00 00
-- 01 00 00 00 00 00 00 00 00
-
-51 1a
-```
-
-```
-fa ce 02 27 00 02 33 5e 00 0b 63 f3 54 80 04 00
-04 03 00 00 00 00 00 52 00 00 00 00 00 00 00 00
-00 04 00 00 00 08 00 01 00 00 00 00 07 04 8f 17
-b8 00 32 01 39 04 90 17 b9 02 00 01 24 00 0e 43
-48 00 00 c2 20 00 00 03 e9 01 02 00 03 08 bd 8e
-38 00 02 00 0a 24 00 0e 43 48 00 00 c2 20 00 00
-03 e9 01 02 00 0d 08 42 49 63 8e 02 00 0f 21 80
-42 49 aa aa 02 00 11 24 00 0e 42 a0 00 00 00 00
-00 00 03 e8 01 01 00 33 01 3a 04 91 17 ba 02 00
-02 08 41 0e c7 1c 02 00 05 24 00 0e 42 c8 00 00
-00 00 00 00 04 40 00 02 00 08 24 00 0e 42 c8 00
-00 00 00 00 00 04 40 00 02 00 09 24 00 0e 41 20
-00 00 00 00 00 00 05 45 01 02 00 0a 08 ba 48 00
-00 02 00 0c 08 00 00 00 00 01 00 34 01 3b 04 92
-17 bb 02 00 00 21 88 3b 23 d8 00 02 00 03 24 00
-0e 3f 80 00 00 bf 80 00 00 82 df 03 01 00 38 01
-3f 04 96 17 bf 02 00 01 24 00 0e 43 48 00 00 c2
-20 00 00 03 e9 01 02 00 03 24 00 0e 40 20 00 00
-00 00 00 00 80 16 03 02 00 09 08 3f 89 68 4c 02
-00 0f 08 42 49 aa aa 01 00 39 01 40 04 97 17 c0
-02 00 01 24 00 0e 41 28 00 00 00 00 00 00 05 45
-01 02 00 0b 21 80 00 00 00 00 01 00 3a 01 41 04
-98 17 c1 02 00 00 24 00 0e 42 c8 00 00 00 00 00
-00 06 34 00 02 00 01 08 3f 7f ff ff 02 00 03 24
-00 0e 3f 99 99 9a 00 00 00 00 80 16 03 02 00 0c
-08 00 00 00 00 01 00 3b 01 42 04 99 17 c2 02 00
-01 24 00 0e 41 20 00 00 00 00 00 00 05 45 01 02
-00 0a 08 00 00 00 00 01 00 36 01 3d 04 94 17 bd
-02 00 01 24 00 0e 45 35 40 00 00 00 00 00 82 dc
-00 02 00 05 24 00 0e 43 c8 00 00 c2 c8 00 00 82
-dd 01 02 00 09 21 88 c2 20 00 00 02 00 10 21 80
-00 00 00 00 01 00 37 01 3e 04 95 17 be 02 00 06
-63 64 00 19 b9 88 02 00 0c 05 00 01 00 3d 01 44
-04 9b 17 c4 02 00 03 24 00 0e 41 20 00 00 00 00
-00 00 82 dc 02 02 00 07 21 80 00 00 00 00 01 00
-00 00 00 00 00 00 00 39 bd
-```
-
-
-== After opening a detail dialog
-
-== 0xB101
-
-```
-fa ce 01 3f 00 02 af b9 00 01 18 62 54 80 04 00
-
-1b 01 00 00 00 00 00 07 03 ac 01 d6 00 04 00 c6
-00 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00
-- 04 90 17 b9 00 32 01 39 00 00 03 e8
-// A/ALA_T9002_Y/SCHRITTTEXT_ALT
-00 13 00 1d 00 41 00 2f 00 41 00 4c 00 41 00 5f 00 54 00 39 00 30 00 30 00 32 00 5f 00 59 00 2f 00 53 00 43 00 48 00 52 00 49 00 54 00 54 00 54 00 45 00 58 00 54 00 5f 00 41 00 4c 00 54 00 00
-// DESC
-00 14 00 04 00 44 00 45 00 53 00 43 00 00
-// A/ALA_T9002_Y/RESTZEIT
-00 15 00 16 00 41 00 2f 00 41 00 4c 00 41 00 5f 00 54 00 39 00 30 00 30 00 32 00 5f 00 59 00 2f 00 52 00 45 00 53 00 54 00 5a 00 45 00 49 00 54 00 00
-// A/ALA_T9002_Y/SCHRITTTEXT
-00 16 00 19 00 41 00 2f 00 41 00 4c 00 41 00 5f 00 54 00 39 00 30 00 30 00 32 00 5f 00 59 00 2f 00 53 00 43 00 48 00 52 00 49 00 54 00 54 00 54 00 45 00 58 00 54 00 00
-ff ff
-- 01
-d8 bf
-```
-
-== 0xB102
-
-```
-fa ce 01 01 00 02 34 ae 00 0b 66 db 54 80 04 00
-
-1b 02 00 00 00 00 00 07 03 ac 01 d6 00 04 00 00
-00 06 00 01 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00
-- 01 00 00 00 00 00 32 01 39 04 90 17 b9
-02 00 13 47 00 4b 00 22 00 49 00 6e 00 69 00 74 00 69 00 61 00 6c 00 69 00 73 00 69 00 65 00 72 00 75 00 6e 00 67 00 20 00 2e 00 2e 00 2e 00 2e 00 2e 00 20 00 62 00 69 00 74 00 74 00 65 00 20 00 77 00 61 00 72 00 74 00 65 00 6e 00 00
-03 00 14 00 00 00 1f
-02 00 15 03 00 00
-02 00 16 47 00 1d 00 0b 00 57 00 41 00 52 00 54 00 45 00 4e 00 20 00 2e 00 2e 00 2e 00 20 00 00
-- 01
-
-e0 99
-```
-
-== 0xB101
-
-```
-fa ce 05 7d 00 02 af bb 00 01 18 66 54 80 04 00
-
-1b 01 00 00 00 00 00 07 03 ad 01 d7 00 04 05 04
-00 08 00 00 00 08 00 8c 00 08 01 38 00 08 01 e4
-00 08 03 64 00 08 04 10 00 08 04 b8 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00
-- 04 9d 17 c6 00 3f 01 46 00 00 03 e8
-// ALARMS
-00 00 00 06 00 41 00 4c 00 41 00 52 00 4d 00 53 00 00
-// C/DC1/PV_D
-00 01 00 0a 00 43 00 2f 00 44 00 43 00 31 00 2f 00 50 00 56 00 5f 00 44 00 00
-// SIM_AKT
-00 02 00 07 00 53 00 49 00 4d 00 5f 00 41 00 4b 00 54 00 00
-// C/BA
-00 03 00 04 00 43 00 2f 00 42 00 41 00 00
-// FREIGABE
-00 04 00 08 00 46 00 52 00 45 00 49 00 47 00 41 00 42 00 45 00 00
-// BAD_ACTIVE
-00 05 00 0a 00 42 00 4100 44 00 5f 00 41 00 43 00 54 00 49 00 56 00 45 00 00
-ff ff
-- 04 9e 17 c7 00 40 01 47 00 00 03 e8
-// C/IST
-00 00 00 05 00 43 00 2f 00 49 00 53 00 54 00 00
-// X_SCALE
-00 01 00 07 00 58 00 5f 00 53 00 43 00 41 00 4c 00 45 00 00
-// SIM_AKT
-00 02 00 07 00 53 00 49 00 4d 00 5f 00 41 00 4b 00 54 00 00
-// ALARMS
-00 03 00 06 00 41 00 4c 00 41 00 52 00 4d 00 53 00 00
-// BILD_TXT
-00 04 00 08 00 42 00 49 00 4c 00 44 00 5f 00 54 00 58 00 54 00 00
-// C/BA
-00 05 00 04 00 43 00 2f 00 42 00 41 00 00
-// BAD_ACTIVE
-00 06 00 0a 00 42 00 41 00 44 00 5f 00 41 00 43 00 54 00 49 00 56 00 45 00 00
-// C/PV_DYN
-00 07 00 08 00 43 00 2f 00 50 00 56 00 5f 00 44 00 59 00 4e 00 00
-ff ff
-- 04 9f 17 c8 00 41 01 48 00 00 03 e8
-// BAD_ACTIVE
-00 00 00 0a 00 42 00 41 00 44 00 5f 00 41 00 43 00 54 00 49 00 56 00 45 00 00
-// C/PV_DYN
-00 01 00 08 00 43 00 2f 00 50 00 56 00 5f 00 44 00 59 00 4e 00 00
-// C/IST
-00 02 00 05 00 43 00 2f 00 49 00 53 00 54 00 00
-// X_SCALE
-00 03 00 07 00 58 00 5f 00 53 00 43 00 41 00 4c 00 45 00 00
-// ALARMS
-00 04 00 06 00 41 00 4c 00 41 00 52 00 4d 00 53 00 00
-// SIM_AKT
-00 05 00 07 00 53 00 49 00 4d 00 5f 00 41 00 4b 00 54 00 00
-// BILD_TXT
-00 06 00 08 00 42 00 49 00 4c 00 44 00 5f 00 54 00 58 00 54 00 00
-// C/BA
-00 07 00 04 00 43 00 2f 00 42 00 41 00 00
-ff ff
-- 04 a0 17 c9 00 42 01 49 00 00 03 e8
-// ALARMS
-00 00 00 06 00 41 00 4c 00 41 00 52 00 4d 00 53 00 00
-// YAW_MAX
-00 01 00 07 00 59 00 41 00 57 00 5f 00 4d 00 41 00 58 00 00
-// C/AUT_MODUS
-00 02 00 0b 00 43 00 2f 00 41 00 55 00 54 00 5f 00 4d 00 4f 00 44 00 55 00 53 00 00
-// C/FREIGABE
-00 03 00 0a 00 43 00 2f 00 46 00 52 00 45 00 49 00 47 00 41 00 42 00 45 00 00
-// C/PV_DYN
-00 04 00 08 00 43 00 2f 00 50 00 56 00 5f 00 44 00 59 00 4e 00 00
-// X
-00 05 00 01 00 58 00 00
-// SIM_AKT
-00 06 00 07 00 53 00 49 00 4d 00 5f 00 41 00 4b 00 54 00 00
-// C/PI/PV_SCALE
-00 07 00 0d 00 43 00 2f 00 50 00 49 00 2f 00 50 00 56 00 5f 00 53 00 43 00 41 00 4c 00 45 00 00
-// BILD_TXT
-00 08 00 08 00 42 00 49 00 4c 00 44 00 5f 00 54 00 58 00 54 00 00
-// YAW_MIN
-00 09 00 07 00 59 00 41 00 57 00 5f 00 4d 00 49 00 4e 00 00
-// C/KASKMOD
-00 0a 00 09 00 43 00 2f 00 4b 00 41 00 53 00 4b 00 4d 00 4f 00 44 00 00
-// C/W_WORK
-00 0b 00 08 00 43 00 2f 00 57 00 5f 00 57 00 4f 00 52 00 4b 00 00
-// X_SCALE
-00 0c 00 07 00 58 00 5f 00 53 00 43 00 41 00 4c 00 45 00 00
-// C/PI/OUT
-00 0d 00 08 00 43 00 2f 00 50 00 49 00 2f 00 4f 00 55 00 54 00 00
-// C/OP_MODUS
-00 0e 00 0a 00 43 00 2f 00 4f 00 50 00 5f 00 4d 00 4f 00 44 00 55 00 53 00 00
-// BAD_ACTIVE
-00 0f 00 0a 00 42 00 41 00 44 00 5f 00 41 00 43 00 54 00 49 00 56 00 45 00 00
-// C/BA
-00 10 00 04 00 43 00 2f 00 42 00 41 00 00
-ff ff
-- 04 a1 17 ca 00 43 01 4a 00 00 03 e8
-// C/BA
-00 00 00 04 00 43 00 2f 00 42 00 41 00 00
-// ALARMS
-00 01 00 06 00 41 00 4c 00 41 00 52 00 4d 00 53 00 00
-// BAD_ACTIVE
-00 02 00 0a 00 42 00 41 00 44 00 5f 00 41 00 43 00 54 00 49 00 56 00 45 00 00
-// C/PV_DYN
-00 03 00 08 00 43 00 2f 00 50 00 56 00 5f 00 44 00 59 00 4e 00 00
-// C/PV_DYN
-00 04 00 05 00 43 00 2f 00 49 00 53 00 54 00 00
-// X_SCALE
-00 05 00 07 00 58 00 5f 00 53 00 43 00 41 00 4c 00 45 00 00
-// SIM_AKT
-00 06 00 07 00 53 00 49 00 4d 00 5f 00 41 00 4b 00 54 00 00
-// BILD_TXT
-00 07 00 08 00 42 00 49 00 4c 00 44 00 5f 00 54 00 58 00 54 00 00
-ff ff
-- 04 a2 17 cb 00 44 01 4b 00 00 03 e8
-// ALARMS
-00 00 00 06 00 41 00 4c 00 41 00 52 00 4d 00 53 00 00
-// C/RC_AUF
-00 01 00 08 00 43 00 2f 00 52 00 43 00 5f 00 41 00 55 00 46 00 00
-// Y
-00 02 00 01 00 59 00 00
-// BAD_ACTIVE
-00 03 00 0a 00 42 00 41 00 44 00 5f 00 41 00 43 00 54 00 49 00 56 00 45 00 00
-// C/BA
-00 04 00 04 00 43 00 2f 00 42 00 41 00 00
-// C/FREIGABE
-00 05 00 0a 00 43 00 2f 00 46 00 52 00 45 00 49 00 47 00 41 00 42 00 45 00 00
-// C/RC_ZU
-00 06 00 07 00 43 00 2f 00 52 00 43 00 5f 00 5a 00 55 00 00
-// SIM_AKT
-00 07 00 07 00 53 00 49 00 4d 00 5f 00 41 00 4b 00 54 00 00
-ff ff
-- 04 a3 17 cc 00 45 01 4c 00 00 03 e8
-// C/RC_AUF
-00 00 00 08 00 43 00 2f 00 52 00 43 00 5f 00 41 00 55 00 46 00 00
-// BAD_ACTIVE
-00 01 00 0a 00 42 00 41 00 44 00 5f 00 41 00 43 00 54 00 49 00 56 00 45 00 00
-// C/BA
-00 02 00 04 00 43 00 2f 00 42 00 41 00 00
-ff ff
-- 07
-
-22 05
-```
-
-== 0xB102
-
-```
-fa ce 04 e1 00 02 34 b0 00 0b 66 df 54 80 04 00
-1b 02 00 00 00 00 00 07 03 ad 01 d7 00 04 00 00
-00 06 00 01 00 06 00 94 00 06 01 37 00 06 02 00
-00 06 02 f5 00 06 03 98 00 06 04 4d 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 07 00 00 00 00 00 3f 01
-46 04 9d 17 c6 02 00 00 76 00 66 05 01 01 00 00
-00 06 00 46 00 45 00 48 00 4c 00 45 00 52 00 00
-00 3b 00 3b 01 0d 00 00 2a f2 70 c7 be 79 ff ff
-00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff
-00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff
-00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff
-00 00 00 00 00 ff 00 00 00 00 00 00 00 00 02 00
-01 63 00 7c 0d a6 a2 02 00 02 01 00 02 00 03 05
-01 02 00 04 01 01 02 00 05 01 00 01 00 00 00 00
-00 40 01 47 04 9e 17 c7 02 00 00 08 42 48 d5 53
-02 00 01 24 00 0e 43 48 00 00 c2 20 00 00 03 e9
-01 02 00 02 01 00 02 00 03 76 00 58 05 01 01 00
-00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00
-00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00
-00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00
-00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00
-00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00
-00 02 00 04 47 00 0b 00 02 00 54 00 49 00 00 02
-00 05 05 01 02 00 06 01 00 02 00 07 01 00 01 00
-00 00 00 00 41 01 48 04 9f 17 c8 02 00 00 01 00
-02 00 01 01 01 02 00 02 08 00 00 00 00 02 00 03
-24 00 0e 41 a0 00 00 00 00 00 00 05 45 01 02 00
-04 76 00 7e 05 01 01 00 00 00 07 00 4d 00 49 00
-4e 00 5f 00 41 00 4c 00 4d 00 00 00 32 00 32 01
-0d 00 00 2a f2 70 c7 21 f3 00 0a 00 4d 00 49 00
-4e 00 5f 00 53 00 43 00 48 00 41 00 4c 00 54 00
-00 00 36 00 36 00 03 00 00 2a f2 70 c7 21 f6 ff
-ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff
-ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff
-ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 02
-00 05 01 00 02 00 06 47 00 0b 00 02 00 46 00 49
-00 00 02 00 07 05 01 01 00 00 00 00 00 42 01 49
-04 a0 17 c9 02 00 00 76 00 58 05 01 01 00 00 ff
-ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff
-ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff
-ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff
-ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff
-ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 02
-00 01 08 42 c8 00 00 02 00 02 63 00 00 19 c9 9c
-02 00 03 48 80 01 02 00 04 01 00 02 00 05 21 80
-42 49 1c 72 02 00 06 01 00 02 00 07 24 00 0e 43
-48 00 00 c2 20 00 00 03 e9 01 02 00 08 47 00 0d
-00 03 00 54 00 49 00 43 00 00 02 00 09 08 00 00
-00 00 02 00 0a 01 00 02 00 0b 08 42 49 1c 72 02
-00 0c 24 00 0e 43 48 00 00 c2 20 00 00 03 e9 01
-02 00 0d 21 c3 42 17 aa ab 02 00 0e 63 00 00 19
-9c 7b 02 00 0f 01 00 02 00 10 05 01 01 00 00 00
-00 00 43 01 4a 04 a1 17 ca 02 00 00 05 01 02 00
-01 76 00 58 05 01 01 00 00 ff ff 00 00 00 00 00
-ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00
-ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00
-ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00
-ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00
-ff 00 00 00 00 00 00 00 00 02 00 02 01 00 02 00
-03 01 00 02 00 04 08 42 49 1c 72 02 00 05 24 00
-0e 43 48 00 00 c2 20 00 00 03 e9 01 02 00 06 01
-00 02 00 07 47 00 0b 00 02 00 54 00 49 00 00 01
-00 00 00 00 00 44 01 4b 04 a2 17 cb 02 00 00 76
-00 7e 05 01 01 00 00 00 0a 00 4d 00 41 00 58 00
-5f 00 53 00 43 00 48 00 41 00 4c 00 54 00 00 00
-2e 00 2e 00 03 00 00 2a f2 71 9b 0f 2c 00 07 00
-4d 00 41 00 58 00 5f 00 41 00 4c 00 4d 00 00 00
-29 00 29 00 03 00 00 2a f2 71 9b 0f 2b ff ff 00
-00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00
-00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00
-00 00 00 00 ff 00 00 00 00 00 00 00 00 02 00 01
-01 00 02 00 02 21 80 3c ce e0 00 02 00 03 01 00
-02 00 04 05 01 02 00 05 01 01 02 00 06 01 01 02
-00 07 01 00 01 00 00 00 00 00 45 01 4c 04 a3 17
-cc 02 00 00 01 00 02 00 01 01 00 02 00 02 05 01
-01 42 c5
-```
-
-== 0xB101
-
-```
-fa ce 01 bb 00 02 af bc 00 01 18 67 54 80 04 00
-1b 01 00 00 00 00 00 07 03 ae 01 d8 00 04 01 42
-00 08 00 00 00 08 00 a8 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 04 a9 17 d2 00 4b 01 52
-00 00 03 e8 00 00 00 07 00 53 00 49 00 4d 00 5f
-00 41 00 4b 00 54 00 00 00 01 00 06 00 41 00 4c
-00 41 00 52 00 4d 00 53 00 00 00 02 00 08 00 43
-00 2f 00 52 00 43 00 5f 00 41 00 55 00 46 00 00
-00 03 00 0a 00 42 00 41 00 44 00 5f 00 41 00 43
-00 54 00 49 00 56 00 45 00 00 00 04 00 01 00 59
-00 00 00 05 00 04 00 43 00 2f 00 42 00 41 00 00
-00 06 00 0a 00 43 00 2f 00 46 00 52 00 45 00 49
-00 47 00 41 00 42 00 45 00 00 00 07 00 07 00 43
-00 2f 00 52 00 43 00 5f 00 5a 00 55 00 00 ff ff
-04 aa 17 d3 00 4c 01 53 00 00 03 e8 00 00 00 09
-00 47 00 5f 00 5a 00 55 00 53 00 54 00 41 00 4e
-00 44 00 00 00 01 00 04 00 43 00 2f 00 42 00 41
-00 00 00 02 00 06 00 41 00 4c 00 41 00 52 00 4d
-00 53 00 00 00 03 00 08 00 46 00 52 00 45 00 49
-00 47 00 41 00 42 00 45 00 00 00 04 00 08 00 43
-00 2f 00 52 00 43 00 5f 00 41 00 55 00 46 00 00
-00 05 00 07 00 53 00 49 00 4d 00 5f 00 41 00 4b
-00 54 00 00 00 06 00 07 00 43 00 2f 00 52 00 43
-00 5f 00 5a 00 55 00 00 ff ff 02 e7 95
-```
-
-== 0xB102
-
-```
-fa ce 01 bf 00 02 34 b2 00 0b 66 e0 54 80 04 00
-1b 02 00 00 00 00 00 07 03 ae 01 d8 00 04 00 00
-00 06 00 01 00 06 00 be 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 02 00 00 00 00 00 4b 01
-52 04 a9 17 d2 02 00 00 01 00 02 00 01 76 00 86
-05 01 01 00 00 00 0a 00 56 00 45 00 52 00 52 00
-49 00 45 00 47 00 45 00 4c 00 54 00 00 00 54 00
-54 00 04 00 00 2a f2 71 97 40 42 00 0b 00 4d 00
-49 00 4e 00 5f 00 41 00 5f 00 41 00 4c 00 4d 00
-5f 00 59 00 00 00 35 00 35 00 03 00 00 2a f2 71
-96 46 47 ff ff 00 00 00 00 00 ff 00 00 00 00 00
-00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00
-00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00
-00 00 00 02 00 02 01 00 02 00 03 01 00 02 00 04
-21 80 00 00 00 00 02 00 05 05 01 02 00 06 01 00
-02 00 07 01 01 01 00 00 00 00 00 4c 01 53 04 aa
-17 d3 02 00 00 07 00 00 00 00 02 00 01 05 01 02
-00 02 76 00 58 05 01 01 00 00 ff ff 00 00 00 00
-00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00
-00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00
-00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00
-00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00 00
-00 ff 00 00 00 00 00 00 00 00 02 00 03 01 01 02
-00 04 01 01 02 00 05 01 00 02 00 06 01 00 01 b2
-29
-```
-
-== 0xB101
-
-```
-fa ce 04 a9 00 02 af bd 00 01 18 68 54 80 04 00
-1b 01 00 00 00 00 00 07 03 af 01 d9 00 04 04 30
-00 08 00 00 00 08 00 6a 00 08 00 f0 00 08 02 7a
-00 08 03 00 00 08 03 86 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 04 a3 17 cc 00 45 01 4c
-00 00 03 e8 00 03 00 06 00 41 00 4c 00 41 00 52
-00 4d 00 53 00 00 00 04 00 0a 00 43 00 2f 00 46
-00 52 00 45 00 49 00 47 00 41 00 42 00 45 00 00
-00 05 00 07 00 43 00 2f 00 52 00 43 00 5f 00 5a
-00 55 00 00 00 06 00 01 00 59 00 00 00 07 00 07
-00 53 00 49 00 4d 00 5f 00 41 00 4b 00 54 00 00
-ff ff 04 a4 17 cd 00 46 01 4d 00 00 03 e8 00 00
-00 07 00 49 00 53 00 54 00 57 00 45 00 52 00 54
-00 00 00 01 00 0a 00 42 00 41 00 44 00 5f 00 41
-00 43 00 54 00 49 00 56 00 45 00 00 00 02 00 04
-00 43 00 2f 00 42 00 41 00 00 00 03 00 06 00 41
-00 4c 00 41 00 52 00 4d 00 53 00 00 00 04 00 08
-00 46 00 52 00 45 00 49 00 47 00 41 00 42 00 45
-00 00 00 05 00 07 00 53 00 49 00 4d 00 5f 00 41
-00 4b 00 54 00 00 ff ff 04 a5 17 ce 00 47 01 4e
-00 00 03 e8 00 00 00 07 00 53 00 49 00 4d 00 5f
-00 41 00 4b 00 54 00 00 00 01 00 08 00 42 00 49
-00 4c 00 44 00 5f 00 54 00 58 00 54 00 00 00 02
-00 06 00 41 00 4c 00 41 00 52 00 4d 00 53 00 00
-00 03 00 09 00 43 00 2f 00 4b 00 41 00 53 00 4b
-00 4d 00 4f 00 44 00 00 00 04 00 0b 00 43 00 2f
-00 41 00 55 00 54 00 5f 00 4d 00 4f 00 44 00 55
-00 53 00 00 00 05 00 08 00 43 00 2f 00 57 00 5f
-00 57 00 4f 00 52 00 4b 00 00 00 06 00 07 00 58
-00 5f 00 53 00 43 00 41 00 4c 00 45 00 00 00 07
-00 08 00 43 00 2f 00 50 00 49 00 2f 00 4f 00 55
-00 54 00 00 00 08 00 06 00 59 00 2d 00 48 00 45
-00 4c 00 50 00 00 00 09 00 0a 00 42 00 41 00 44
-00 5f 00 41 00 43 00 54 00 49 00 56 00 45 00 00
-00 0a 00 04 00 43 00 2f 00 42 00 41 00 00 00 0b
-00 0a 00 43 00 2f 00 46 00 52 00 45 00 49 00 47
-00 41 00 42 00 45 00 00 00 0c 00 0a 00 43 00 2f
-00 4f 00 50 00 5f 00 4d 00 4f 00 44 00 55 00 53
-00 00 00 0d 00 08 00 43 00 2f 00 50 00 56 00 5f
-00 44 00 59 00 4e 00 00 00 0e 00 01 00 58 00 00
-00 0f 00 09 00 45 00 58 00 54 00 5f 00 54 00 52
-00 41 00 43 00 4b 00 00 00 10 00 0d 00 43 00 2f
-00 50 00 49 00 2f 00 50 00 56 00 5f 00 53 00 43
-00 41 00 4c 00 45 00 00 00 11 00 01 00 59 00 00
-ff ff 04 a6 17 cf 00 48 01 4f 00 00 03 e8 00 00
-00 0a 00 42 00 41 00 44 00 5f 00 41 00 43 00 54
-00 49 00 56 00 45 00 00 00 01 00 04 00 43 00 2f
-00 42 00 41 00 00 00 02 00 06 00 41 00 4c 00 41
-00 52 00 4d 00 53 00 00 00 03 00 08 00 46 00 52
-00 45 00 49 00 47 00 41 00 42 00 45 00 00 00 04
-00 07 00 53 00 49 00 4d 00 5f 00 41 00 4b 00 54
-00 00 00 05 00 07 00 49 00 53 00 54 00 57 00 45
-00 52 00 54 00 00 ff ff 04 a7 17 d0 00 49 01 50
-00 00 03 e8 00 00 00 07 00 53 00 49 00 4d 00 5f
-00 41 00 4b 00 54 00 00 00 01 00 06 00 41 00 4c
-00 41 00 52 00 4d 00 53 00 00 00 02 00 08 00 46
-00 52 00 45 00 49 00 47 00 41 00 42 00 45 00 00
-00 03 00 0a 00 42 00 41 00 44 00 5f 00 41 00 43
-00 54 00 49 00 56 00 45 00 00 00 04 00 04 00 43
-00 2f 00 42 00 41 00 00 00 05 00 07 00 49 00 53
-00 54 00 57 00 45 00 52 00 54 00 00 ff ff 04 a8
-17 d1 00 4a 01 51 00 00 03 e8 00 00 00 07 00 53
-00 49 00 4d 00 5f 00 41 00 4b 00 54 00 00 00 01
-00 07 00 58 00 5f 00 53 00 43 00 41 00 4c 00 45
-00 00 00 02 00 08 00 42 00 49 00 4c 00 44 00 5f
-00 54 00 58 00 54 00 00 00 03 00 04 00 43 00 2f
-00 42 00 41 00 00 00 04 00 06 00 41 00 4c 00 41
-00 52 00 4d 00 53 00 00 00 05 00 09 00 47 00 5f
-00 5a 00 55 00 53 00 54 00 41 00 4e 00 44 00 00
-00 06 00 08 00 43 00 2f 00 50 00 56 00 5f 00 44
-00 59 00 4e 00 00 00 07 00 05 00 43 00 2f 00 49
-00 53 00 54 00 00 ff ff 06 c1 f7
-```
-
-== 0xB102
-
-```
-fa ce 04 82 00 02 34 b3 00 0b 66 e2 54 80 04 00
-1b 02 00 00 00 00 00 07 03 af 01 d9 00 04 00 00
-00 06 00 01 00 06 00 af 00 06 01 42 00 06 02 3d
-00 06 02 d0 00 06 03 63 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 06 00 00 00 00 00 45 01
-4c 04 a3 17 cc 02 00 03 76 00 86 05 01 01 00 00
-00 0a 00 56 00 45 00 52 00 52 00 49 00 45 00 47
-00 45 00 4c 00 54 00 00 00 54 00 54 00 04 00 00
-2a f2 70 d0 7b d3 00 0b 00 4d 00 49 00 4e 00 5f
-00 41 00 5f 00 41 00 4c 00 4d 00 5f 00 59 00 00
-00 35 00 35 00 03 00 00 2a f1 c7 5e 3e a7 ff ff
-00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff
-00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff
-00 00 00 00 00 ff 00 00 00 00 00 00 00 00 02 00
-04 01 00 02 00 05 01 01 02 00 06 21 80 00 00 00
-00 02 00 07 01 00 01 00 00 00 00 00 46 01 4d 04
-a4 17 cd 02 00 00 63 01 7c 0d a6 d7 02 00 01 01
-00 02 00 02 05 01 02 00 03 76 00 66 05 01 01 00
-00 00 06 00 46 00 45 00 48 00 4c 00 45 00 52 00
-00 00 52 00 52 01 0d 00 00 2a f1 c7 f0 48 88 ff
-ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff
-ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff
-ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff
-ff 00 00 00 00 00 ff 00 00 00 00 00 00 00 00 02
-00 04 01 01 02 00 05 01 00 01 00 00 00 00 00 47
-01 4e 04 a5 17 ce 02 00 00 01 00 02 00 01 47 00
-0d 00 03 00 54 00 49 00 43 00 00 02 00 02 76 00
-58 05 01 01 00 00 ff ff 00 00 00 00 00 ff 00 00
-00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00
-00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00
-00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00
-00 00 00 00 00 00 ff ff 00 00 00 00 00 ff 00 00
-00 00 00 00 00 00 02 00 03 01 00 02 00 04 63 01
-00 19 c9 9c 02 00 05 08 42 4c 00 00 02 00 06 24
-00 0e 43 48 00 00 c2 20 00 00 03 e9 01 02 00 07
-21 c0 42 95 fe c7 02 00 08 08 42 48 00 00 02 00
-09 01 00 02 00 0a 05 01 02 00 0b 48 80 01 02 00
-0c 63 01 00 19 9c 7b 02 00 0d 01 00 02 00 0e 21
-80 42 49 1c 72 02 00 0f 01 00 02 00 10 24 00 0e
-43 48 00 00 c2 20 00 00 03 e9 01 02 00 11 21 80
-42 95 fe c7 01 00 00 00 00 00 48 01 4f 04 a6 17
-cf 02 00 00 01 00 02 00 01 05 01 02 00 02 76 00
-66 05 01 01 00 00 00 06 00 46 00 45 00 48 00 4c
-00 45 00 52 00 00 00 52 00 52 01 0d 00 00 2a f2
-70 c7 30 06 ff ff 00 00 00 00 00 ff 00 00 00 00
-00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00
-00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00
-00 00 00 00 ff ff 00 00 00 00 00 ff 00 00 00 00
-00 00 00 00 02 00 03 01 00 02 00 04 01 00 02 00
-05 63 00 7c 0d a6 d7 01 00 00 00 00 00 49 01 50
-04 a7 17 d0 02 00 00 01 00 02 00 01 76 00 66 05
-01 01 00 00 00 06 00 46 00 45 00 48 00 4c 00 45
-00 52 00 00 00 52 00 52 01 0d 00 00 2a f1 c8 bc
-f6 68 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00
-00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00
-00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00
-00 00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00
-00 00 02 00 02 01 00 02 00 03 01 00 02 00 04 05
-01 02 00 05 63 00 7c 0d a6 d7 01 00 00 00 00 00
-4a 01 51 04 a8 17 d1 02 00 00 01 00 02 00 01 24
-00 0e 43 48 00 00 c2 20 00 00 03 e9 01 02 00 02
-47 00 0b 00 02 00 54 00 49 00 00 02 00 03 05 01
-02 00 04 76 00 58 05 01 01 00 00 ff ff 00 00 00
-00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00
-00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00
-00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00
-00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00
-00 00 ff 00 00 00 00 00 00 00 00 02 00 05 07 00
-00 00 00 02 00 06 01 00 02 00 07 21 80 42 48 00
-00 01 42 28
-```
-
-== After quite some time ...
-
-== 0xB101
-
-```
-fa ce 00 97 00 02 b0 5f 00 01 1a cd 54 80 04 00
-1b 01 00 00 00 00 00 07 01 ed 00 16 00 04 00 1e
-00 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 04 9e 17 c7 00 40 01 47
-00 00 03 e8 00 08 00 05 00 49 00 44 00 49 00 53
-00 50 00 00 ff ff 01 99 70
-```
-
-== 0xB102
-
-```
-fa ce 00 8d 00 02 36 02 00 0b 69 df 54 80 04 00
-1b 02 00 00 00 00 00 07 01 ed 00 16 00 04 00 00
-00 06 00 01 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 01 00 00 00 00 00 40 01
-47 04 9e 17 c7 03 00 08 00 00 00 1f 01 4a 60
-```
-
-== 0xB101
-
-```
-fa ce 00 a9 00 02 b0 66 00 01 1a e1 54 80 04 00
-1b 01 00 00 00 00 00 07 01 ee 00 17 00 04 00 30
-00 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 04 9e 17 c7 00 40 01 47
-00 00 03 e8 00 09 00 0e 00 43 00 2f 00 53 00 57
-00 5f 00 4d 00 41 00 58 00 5f 00 53 00 43 00 41
-00 4c 00 45 00 00 ff ff 01 cf 34
-```
-
-== 0xB102
-
-```
-fa ce 00 97 00 02 36 10 00 0b 69 f8 54 80 04 00
-1b 02 00 00 00 00 00 07 01 ee 00 17 00 04 00 00
-00 06 00 01 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 01 00 00 00 00 00 40 01
-47 04 9e 17 c7 02 00 09 24 00 0e 43 48 00 00 c2
-20 00 00 03 e9 01 01 74 11
-```
-
-
-
-
-
-
-
-```
-fa ce 05 14 00 02 9a 21 00 01 c8 96 54 80 04 00
-
-1b 02 00 00 00 00 00 07 03 bf 01 1b 00 04 00 00
-00 06 00 01 00 06 01 81 00 06 02 d6 00 06 03 e4
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
-00 00 00 00 00 00 00 00
-04 00 00 00 00 00 35 01 4b 08 ea 1c 13
-02 00 00 47 00 0b 00 02 00 44 00 54 00 00
-02 00 01 24 00 0e 43 48 00 00 c2 20 00 00 03 e9 01
-02 00 02 47 00 0b 00 02 00 56 00 4c 00 00
-02 00 03 08 00 00 00 00
-02 00 04 63 00 00 19 c4 2f
-02 00 05 76 00 88 05 01 01 00 00 00 0e
-00 47 00 46 00 45 00 5f 00 56 00 45 00 52 00 52
-00 49 00 45 00 47 00 45 00 4c 00 54 00 00 00 54
-00 00 01 07 00 00 2a f5 b7 5d f8 ed 00 08 00 53
-00 54 00 4f 00 45 00 52 00 55 00 4e 00 47 00 00
-00 39 00 39 00 0f 00 00 2a f4 8e c3 64 22 ff ff
-00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff
-00 00 00 00 00 ff 00 00 00 00 00 00 00 00 ff ff
-00 00 00 00 00 ff 00 00 00 00 00 00 00 00
-02 00
-06 47 00 09 00 01 00 54 00 00
-02 00 07 05 00
-02 00 08 01 01
-02 00 09 47 00 0b 00 02 00 49 00 54 00 00
-02 00 0a 24 00 0e 43 48 00 00 c2 20 00 00 03 e9 01
-02 00 0b 05 01
-02 00 0c 47 00 19 00 09 00 50 00 54 00 30 00 39 00 41 00 4c 00 41 00 43 00 31 00 00
-02 00 0d 08 c2 20 00 00
-02 00 0e 47 00 17 00 08 00 4b 00 65 00 69 00 6e 00 65 00 20 00 46 00 57 00 00
-02 00 0f 21 80 c2 20 00 00 02 00 10 47 00 09 00 01 00 54 00 00
-02 00 11 24 00 0e 42 a0 00 00 00 00 00 00 03 e8 01
-02 00 12 47 00 09 00 01 00 54 00 00
-- 01 00 00 00 00 00 36 01 4c 08 eb 1c 14
-02 00 00 47 00 17 00 08 00 4b 00 65 00 69 00 6e 00 65 00 20 00 46 00 57 00 00
-02 00 01 63 00 00 19 c4 2f
-02 00 02 08 41 0e c7 1c
-02 00 03 47 00 0d 00 03 00 46 00 4c 00 55 00 00
-02 00 04 76 00 58 05 01 01 00 00 ff ff 00 00 00
-00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00
-00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00
-00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00
-00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00 00
-00 00 ff 00 00 00 00 00 00 00 00
-02 00 05 24 00
-0e 42 c8 00 00 00 00 00 00 04 40 00 02 00 06 47
-00 0d 00 03 00 46 00 30 00 31 00 00 02 00 07 47
-00 09 00 01 00 57 00 00 02 00 08 24 00 0e 42 c8
-00 00 00 00 00 00 04 40 00 02 00 09 24 00 0e 41
-20 00 00 00 00 00 00 05 45 01 02 00 0a 08 ba 48
-00 00 02 00 0b 47 00 19 00 09 00 50 00 54 00 30
-00 39 00 41 00 41 00 48 00 52 00 31 00 00 02 00
-0c 08 00 00 00 00 02 00 0d 05 00 02 00 0e 47 00
-09 00 01 00 46 00 00 02 00 0f 47 00 0d 00 03 00
-46 00 53 00 54 00 00 02 00 10 01 00 02 00 11 05
-01 02 00 12 47 00 09 00 01 00 57 00 00 01 00 00
-00 00 00 37 01 4d 08 ec 1c 15 02 00 00 21 88 3b
-23 d8 00 02 00 01 05 01 02 00 02 47 00 17 00 08
-00 4b 00 65 00 69 00 6e 00 65 00 20 00 46 00 57
-00 00 02 00 03 24 00 0e 3f 80 00 00 bf 80 00 00
-82 df 03 02 00 04 76 00 76 05 01 01 00 00 00 0e
-00 47 00 46 00 45 00 5f 00 56 00 45 00 52 00 52
-00 49 00 45 00 47 00 45 00 4c 00 54 00 00 00 54
-00 54 01 07 00 00 2a f4 92 c2 4a 74 ff ff 00 00
-00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00
-00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00
-00 00 00 ff 00 00 00 00 00 00 00 00 ff ff 00 00
-00 00 00 ff 00 00 00 00 00 00 00 00 02 00 05 63
-00 00 19 c4 2f 02 00 06 47 00 19 00 09 00 50 00
-54 00 30 00 39 00 41 00 4d 00 42 00 4d 00 31 00
-00 02 00 07 47 00 07 00 00 00 00 02 00 08 05 00
-02 00 09 05 01 02 00 0a 47 00 09 00 01 00 50 00
-00 02 00 0b 05 01 02 00 0c 01 00 01 00 00 00 00
-00 38 01 4e 08 ed 1c 16 02 00 00 76 00 76 05 01
-01 00 00 00 0e 00 47 00 46 00 45 00 5f 00 56 00
-45 00 52 00 52 00 49 00 45 00 47 00 45 00 4c 00
-54 00 00 00 54 00 54 00 07 00 00 2a f4 8e c4 35
-ef ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00
-00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00
-00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00
-00 ff ff 00 00 00 00 00 ff 00 00 00 00 00 00 00
-00 02 00 01 47 00 17 00 08 00 4b 00 65 00 69 00
-6e 00 65 00 20 00 46 00 57 00 00 02 00 02 05 00
-02 00 03 05 00 02 00 04 63 00 00 19 c4 2f 02 00
-05 05 00
-01
-
-fa f9
-```
-
-
-
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/delta-v/reverse-engineering.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/delta-v/reverse-engineering.adoc
deleted file mode 100644
index 271c31b..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/delta-v/reverse-engineering.adoc
+++ /dev/null
@@ -1,252 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-:imagesdir: ../../images/
-
-== Reverse Engineering the DeltaV protocol
-
-This document should describe what we did in order to reverse-engineer the DeltaV protocol.
-
-The sole purpose of this document, is to write document our path in order to eventually protect ourselves against accusation of using illegal measures in gaining the information we got.
-
-=== Starting point
-
-We kindly were provided with access to a DeltaV system used for training.
-
-Therefore we were able to change a few things without fearing to break anything important.
-
-This system consisted of three DeltaV controllers, two Operator-System instances
-So in general there were three types of systems involved:
-
-1. DeltaV Controller
-2. DeltaV Operator-System
-3. Laptop running WireShark
-
-The first change here, was to replace the network switch with a network hub, so we could capture the entire network traffic.
-(By the way ... if you happen to still have a working Hub, don't give that away. It turns out it's really hard to get you hands on hubs these days)
-
-With this we let the system run and did a pretty long network capture.
-
-This 29MB WireShark capture was what we started working with.
-
-=== Identifying the protocol
-
-As WireShark didn't have a DeltaV disector, we had to trace it down ourselves.
-
-When looking at the capture, we very quickly filtered out the usual network protocols and the Windows communication and found a lot of binary `UDP` traffic running on port `18507`.
-
-Special with all of these was that they all started with a payload of `0xFACE`.
-
-=== First steps in understanding the protocol
-
-Here it appeared that `UDP` packets are sent with some sort of payload, which are obviously responded to by packets with a fixed and very small size (64 bytes).
-
-So we are assuming these short messages, that seem to partially repeat some of the information of the first packet (but not all), are probably acknowledge packets.
-
-From looking at the nature of the traffic and knowing the IP addresses of the DeltaV controllers (PLC) and the Operator Systems (Controll-Software), we could see that this communication is probably subscription based as we could see a lot of the Controller sending packets to the OS, which the OS then acknowleges in regular intervals.
-
-When filtering only the `UDP` packets on port `18507` we could scroll though the byte representation, we could quickly identify some things.
-
-1. Directly after the `0xFACE` head, came two bytes (short) which was identical for similar packet content, so we at first thought it somehow correlates to a type.
-2. After this came another short value which also seemed identical for similar packets. However as there were differences, we assumed this was some sort of sub-type.
-3. This was followed by one byte that seemed identical for all messages sent from one node to another, but we did find up to 3 different values in the dumps. So we at first thought this was some sort of connection id
-4. The most obvious thing about the byte after that was, that it seemed to increment by one for messages with the same "connection id", so we assumed this was a message-id.
-5. There were 3 bytes between the message-id and an obviously constant sequence of 3 bytes which, at first we had no idea what they might be used for.
-
-In order to prove any assumption we made, we used little programs that used Pcap4J to programmatically check assumptions.
-
-=== Decoding the wrapper packet header
-
-As mentioned before, it appeared obvious that for almost identical packets the first two short values were very similar too, which led us to the assumption that these are `type` and `sub-type'.
-So we wrote a little program, that scanned all the packets and counted how many types we had.
-This was a very large number. Also did we output some additional information about packets on the console ... one of these pieces of information was the length of the packet.
-
-When outputting a sorted list of the type values (maybe it's strange, but I like data sorted) it seemed quite obvious, that for a larger presumed `type` value, also the length of the packet was larger.
-Especially when comparing the difference of these values also showed that of a `type` had a value that is larger than another packet, that also the length was exactly this number of bytes larger.
-
-So in the end it turned out that the first short value is not the `type`, but a packet length-related value.
-It even turned out that the number encoded here was constantly 2 bytes short the number of bytes after the 3 constant bytes of `0x800400`, ending leaving two bytes at the end.
-
-These two bytes seemed to be extremely jumpy.
-Here we could see that for every packet this value seemed to change quite dramatically, even if the payload was almost identical.
-We did see values repeated, but couldn't see any correlation between the content of the colliding packets.
-So in the end we assume this is some sort of checksum value.
-
-With this assumption, we now think that the first short value is the `payload-length` value.
-
-Knowing the first short value no longer is the type, upgraded the second short value to being a new candidate for being a full type.
-
-Scanning the communication, it pretty quickly became obvious that here most communication packets have a value of `0x0002` and some have `0x0006`.
-Only when starting a new OS instance while capturing, made some others pop up: `0x0003` and `0x0004`.
-
-So we are assuming the `0x0003` and `0x0004` packets are related to establishing a connection.
-Also we could see the node initiating a connection sends a `0x0003` packet, which is then replied to by a `0x0004` packet.
-
-Then most information is sent via `0x0002` packets.
-However every now and then there comes a pair of `0x0006` packets, who's length seems to prevent being used to transfer any data.
-We are therefore assuming these packets are used for syncing.
-
-As mentioned before we did a lot of automatically splitting up PCAPNG files into separate ones depending on different conditions, because this allowed to browse through similar packets using simple human pattern recognition for decoding.
-
-Pretty soon after starting to splitting up the streams, so the communication between two nodes was separated into one separate file, we did notice what we assumed to be a `connection-id` and a `mesasage-counter` instantly following the type.
-
-However when doing the statistical counting and listing of these values, we noticed that after the message-id `0xFF` came the `0x00`, as we would have expected, but the assumed connection-id was also incremented by one.
-So it turned out that the similarity of the first byte were not due to a connection-id, but rather the counter of just having the same first byte.
-After the `type` byte seems to come a `message-id` counter.
-It seems as if this initialized to some random value during the connection establishment and is then incremented with every message.
-
-However our little check did reveal, that this id is identical for a packet following a `0x0006` packet.
-Therefore we are assuming the `0x0006` packets are used to sync the connection between two nodes.
-
-The short value (or a byte value following a 0x00 byte), after this message id seems to be constant for every message sent from ine node to another, but we think to have seen one node use different values for communicating with different nodes.
-Also it seems that all Controllers seem to have values from `0x0000` to `0x0009` and OSes seem to have values from `0x000A` to `0x000F`.
-We are assuming this is some sort of `sender-id` value.
-
-The following 3 bytes were quite a mystery to us.
-We could see that it seems to be an ever increasing number stored here, however the increment was not linear.
-However when interpreting these 3 bytes as a number and filtering only packets initiated by the controller to one particular OS, filtering out Ack messages by accident, we did notice a certain pattern.
-When correlating that to the capture file, we could see that the pattern correlated to the pattern in the communication.
-We were told, that the OS is configured to update the values once a second and could see that pattern in the capture.
-Here was when we noticed that the numeric value in the 3 bytes followed this pattern.
-In the end it turns out that if we interpret this 3 byte number where the first 14 bits encoding seconds and the following 10 bits the sub-second part, the values in the timestamp matched the timestamps of the pacet capture.
-
-We have to admit that we were a little surprised about this.
-Currently we are assuming that this timestamp is used for tracking transmission times.
-4 bytes would allow quite a time-range, but would come at a cost of one additional byte per packet, that wouldn't be needed for simple run-time checking.
-Two bytes however only would allow to encode only about 63 seconds, which is probably too little when thinking about packet-losses and re-transmissions.
-So in the end we assume these 3 bytes are a simple timestamp.
-
-As mentioned before, the following byte is usually `0x80` except for the first packet every party exchanges with the other side.
-In this case the value is `0x00`.
-So we'll just keep that in mind an not worry about interpreting a meaning into this.
-The last two bytes of the wrapper packet header are simply constantly `0x8000` in every packet.
-Here too, we'll just live with knowing that and not wondering what it could mean.
-
-=== Decoding the internal packet
-
-After having decoded what we think is the wrapper-protocol packet structure, we knew decoding the internal protocol would be a bigger challenge.
-
-Therefore the test-setup was changed a little.
-
-The number of controllers and operator-systems were reduced to one each.
-The OS was changed to display only one single value of the controller.
-A simulator was introduced, which was connected to the controller and communicated to this via ProfiNet protocol.
-This simulator allowed us to provide values to the controller via the backend ProfiNet connection.
-
-With this setup we started working on the payload decoding.
-
-The first two bytes of the payload seem again to relate to a type as similar packets usually had identical values here.
-
-Especially we did a lot of separate captures for all sorts of different operations.
-During this we managed to reverse engineer the connection on the wrapper-protocol layer as well how the communication looks inside the internal protocol.
-
-==== Connecting
-
-When an OS is booted, the following communication could be observed:
-
-1. The OS sends a wrapper-protocol type `0x0003` to the controller.
-2. The controller responds with a `0x0004` message back to the controller.
-3. After receiving the `0x0004` message, the OS sends a type `0x0002` message with a wrapped type `0x0501`
-4. This packet is acknowledged by the controller
-5. The controller sends a very similar packet as the `0x0501` packet back to the OS
-6. The OS acknowledges this packet back to the controller
-
-From looking at the packet in WireShark's byte and ASCII view, we could see ASCII characters that seem to relate to test strings.
-A quick consultation of the guy in charge of these systems made us realize that these strings refer to parts of the controllers software.
-Digging even deeper made us realize that the 4 byte values relate to unix timestamps - at least we could decode the byte values to absolutely sensible dates.
-So it seems that In these packets each participant compares it's software state in order to know all are using compatible versions.
-
-This does make sense.
-When connecting to a remote system, checking the version compatibility is surely an important thing to do.
-
-==== Normal operation
-
-When just starting the system and not changing anything, we did notice those previously mentioned `0x0006` type messages we think are responsible for keeping the connections in sync.
-
-What is also noticeable when just starting a System and not logging in to Windows yet, is that the DeltaV Operator System seems to connect before a user logs in to Windows.
-After the connection is established, the Controller almost immediately starts sending alarm telegrams (0x03XX types), but no value telegrams (0x04xx).
-
-It also appears that there is some upper bound for the size of packets.
-As when seeing a lot of alarms being sent in 0x0304 messages, sometimes these are split up into multiple messages sent in very short intervals.
-The last of these usually being smaller than the rest.
-
-==== Changing values
-
-So now we started changing values.
-First we started changing valid values into other valid values.
-
-So whenever we changed a value immediately a packet with wrapper-type `0x0002` was written from the controller to the os with a payload-type `0x0403`.
-
-Whenever we changed values to values that raise alarms, we could see the same `0x0403` messages being sent, but the payload of these being a lot larger, but additionally packets with payload-types starting with `0x03` being sent.
-
-So after increasing a value to a value that raises alarms, we got a payload-type `0x0304` message containing a string-like representation of the Name of the alarm raised as well as probably a name of a user or role.
-Also did we notice the `0x0403` packets seem to contain String constants that relate exactly to the text displayed at the bottom of each screen window.
-
-We assume payload-types starting with `0x04` relate to normal data exchange and ones with `0x03` relating to events and alarms.
-
-==== Decoding value changes
-
-After coming to the conclusion that wrapper-type `0x0002` messages with a payload-type `0x0403` seem to relate to value changes, we started filtering for exactly these packages.
-
-Next we created some captures that contain all sorts of documented value changes.
-So we started with the value 0 and incremented that in steps of 1 till 20 and then in steps of 10 up to 200, going back to 0 and then down to the minimum value of -40.
-
-And we could see that there were certain parts of the packet that seem to change when changing values, most of the packet remaining constant.
-When changing a value back to the original value, the packets payload was identical in this part.
-As the packets didn't all have the same content and some times blocks were added and left away in regular intervals, lead us to the impression, that these packets too consist of a fixed packet header followed by blocks.
-In our case the changing blocks all had two indicator bytes `0x0b08` with the 4 bytes after that changing according to the input.
-Sometimes a block of bytes was added before this block, then the entire content was just pushed back.
-
-The last of such blocks would always be a sequence of 9 bytes: `0x01000000000000000000`, so we assume this is sort of the `terminating block` of such a packet.
-
-One thing quite obvious is that the header does again seem to contain a counter of one byte which is incremented for every `0x0403` packet.
-
-As we currently wanted to understand how the data is encoded we decided to ignore all other parts and concentrate on the block we identified as containing the information we were looking for.
-
-Now how should we interpret this information. At first I was told we were working with an unsigned 16 bit integer.
-Unfortunately we could see 4 bytes changing.
-It took us quite a while.
-As mentioned before we created a table containing the value we input and what we could see in the packet.
-Unfortunately we started seeing patterns, but couldn't quite get the meaning, however we did notice the "end" of the hex-values alternating around `0x00001` and `0xFFFFF`.
-This didn't help much, so we converted these 4 bytes into a numeric value.
-And we did notice the numbers being a lot bigger for negative values, which made us think, maybe the first bit is used for the sign.
-We could confirm that a value of +20 and -20 did produce a value that was equal, except for the first bit.
-Unfortunately still we didn't quite understand how to interpet the other 31 bits.
-So we converted the payload to it's binary representation and this is when we finally found out what it meant.
-So in reality this value was not a 16 bit integer, but a `IEEE-754 Floating Point` value.
-Here the first bit is interpreted as sign, the following an 8 bit exponent and a 23 bit mantisse.
-This explained the end of the value alternating around 0.
-
-With this we were able to write a simple console application that was able to instantly display value changes.
-
-However when using what we learnt on the old captures we did, it turned out that unfortunately we could no longer find these `0x0b08` sequences, however we did find a lot of `0x08` followed by a 32 bit floating point value.
-So it seems that `0x08` indicates the type of an `signed 32 bit IEE 754 floating point value`.
-Perhaps the `0x0b` part referred to some sort subscription-id.
-
-As we seem to be doing a subscription based communication, the OS has to tell the controller what information it is interested in.
-
-Right now we are assuming that in one of the other `0x04` packets a subscription is initiated and assigned with some sort of id and this id is used to identify which value is actually changed.
-
-We will hopefully be able to decode this addressing problem in one of our next reverse-engineering sessions.
-
-==== Decoding Strings
-
-As we mentioned before, that we could see content in the packages that were sometimes readable from just looking at the payload, we decided to have another look at these.
-
-After some time, we did notice, that it seems that Strings have a type of `0x00` and are followed by one byte or are a short value containing the length of the string value.
-This is then followed by each character being output using two bytes.
-We assume this is in order to allow transferring `UTF-16` (two byte) big characters, but never found any.
-Right now the first byte of every block is simply `0x00` followed by the `UTF-8` character value.
\ No newline at end of file
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/ehtercat/index.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/ehtercat/index.adoc
deleted file mode 100644
index 8fecaa9..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/ehtercat/index.adoc
+++ /dev/null
@@ -1,28 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-
-== EtherCAT
-
-Introduction
-
-=== Links
-
-https://www.ethercat.org/default.htm
-https://www.ethercat.org/download/documents/EtherCAT_EAP_EN.pdf
-https://www.ethercat.org/pdf/english/EtherCAT_Introduction_0905.pdf
-https://download.beckhoff.com/download/document/io/ethercat-terminals/ethercatsystem_en.pdf
-https://www.megatech.ro/doc/699/FZM1%20EtherCAT%20Communications%20Manual%20EN.pdf
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/ethernet-ip/index.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/ethernet-ip/index.adoc
deleted file mode 100644
index f0c705b..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/ethernet-ip/index.adoc
+++ /dev/null
@@ -1,30 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-
-== EtherNet/IP
-
-Introduction
-
-=== Links
-
-As of November 2008, The EtherNet/IP Specification consists of three parts: The Common Industrial
-Protocol (Volume 1 of the CIP Networks Library), the EtherNet/IP Adaptation of CIP (Volume 2), and the
-Integration of Modbus® Devices into a CIP Architecture (Volume 7).
-
-Order Form for the SPEC ($1000) https://www.odva.org/spec-vid-ctsoftware-order-form/
-
-
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/features.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/features.adoc
deleted file mode 100644
index 2c20eaf..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/features.adoc
+++ /dev/null
@@ -1,87 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-
-== Features
-:icons: font
-
-The following table contains a list of operations and the protocols that support them:
-
-|===
-|Protocol |Read Single Address Value |Read Multiple Address Values |Write Single Address Value |Write Multiple Address Value|Subscribe to Value changes |Subscribe to PLC Events/Alarms
-
-|AB-Ethernet
-|icon:check[role="green"]
-|icon:check[role="red"]
-|icon:check[role="red"]
-|icon:check[role="red"]
-|icon:check[role="red"]
-|icon:question[role="red"]
-
-|ADS
-|icon:check[role="green"]
-|icon:check[role="green"]
-|icon:check[role="green"]
-|icon:check[role="green"]
-|icon:check[role="green"]
-|icon:question[role="red"]
-
-|DeltaV
-|icon:question[role="red"]
-|icon:question[role="red"]
-|icon:question[role="red"]
-|icon:question[role="red"]
-|icon:question[role="red"]
-|icon:question[role="red"]
-
-|EtherNet/IP
-|icon:question[role="red"]
-|icon:question[role="red"]
-|icon:question[role="red"]
-|icon:question[role="red"]
-|icon:question[role="red"]
-|icon:question[role="red"]
-
-|Modbus
-|icon:question[role="red"]
-|icon:question[role="red"]
-|icon:question[role="red"]
-|icon:question[role="red"]
-|icon:question[role="red"]
-|icon:question[role="red"]
-
-|OPC-UA
-|icon:question[role="red"]
-|icon:question[role="red"]
-|icon:question[role="red"]
-|icon:question[role="red"]
-|icon:question[role="red"]
-|icon:question[role="red"]
-
-|S7
-|icon:check[role="green"]
-|icon:check[role="green"]
-|icon:check[role="green"]
-|icon:exclamation[role="yellow"]
-|icon:question[role="red"]
-|icon:question[role="red"]
-|===
-
-Legend:
-
-- icon:check[role="green"] Implemented and fully supported
-- icon:exclamation[role="yellow"] Implemented and supported by simulation
-- icon:question[role="red"] Not implemented yet
\ No newline at end of file
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/index.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/index.adoc
deleted file mode 100644
index da8c530..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/index.adoc
+++ /dev/null
@@ -1,51 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-
-== Protocols
-
-- link:ab-eth/index.html[AB-Ethernet]
-- link:ads/index.html[DeltaV]
-- link:canopen/index.html[CANopen]
-- link:delta-v/index.html[DeltaV]
-- link:ethernet-ip/index.html[EtherNet/IP]
-- link:modbus/index.html[Modbus]
-- link:opc-ua/index.html[OPC-UA]
-- link:s7/index.html[S7]
-
-=== Links
-
-Apache 2.0 licensed JNI library for accessing raw IPv4 and IPv6 sockets. Might be the ideal starting point for implementing protocols below TCP & UDP.
-https://www.savarese.org/software/rocksaw/
-
-Links to different WireShark captures: https://github.com/automayt/ICS-pcap
-
-==== BACNet
-
-Used in the building automation sector.
-http://www.bacnet.org/Addenda/Add-135-2008t.pdf
-
-AKA: ISO 16484-5:
-The official specification can be purchased here: https://www.iso.org/standard/71935.html
-
-==== IEC 61850
-
-Used by the IDS SAS (station automation system)
-
-https://de.wikipedia.org/wiki/IEC_60870
-
-German norm: DIN EN 60870
-The official specification can be purchased here: https://www.beuth.de/de/norm/din-en-60870-5-104/100426613
\ No newline at end of file
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/modbus/index.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/modbus/index.adoc
deleted file mode 100644
index 7a1092e..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/modbus/index.adoc
+++ /dev/null
@@ -1,26 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-
-== Modbus
-
-Introduction
-
-=== Links
-
-- Main Landing Page: http://www.modbus.org/tech.php
-- Modbus Protocol Spec: http://www.modbus.org/docs/Modbus_Application_Protocol_V1_1b3.pdf
-- Modbus TCP Protocol Spec: http://www.modbus.org/docs/Modbus_Messaging_Implementation_Guide_V1_0b.pdf
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/opc-ua/index.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/opc-ua/index.adoc
deleted file mode 100644
index 82973c0..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/opc-ua/index.adoc
+++ /dev/null
@@ -1,28 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-
-== OPC-UA
-
-Introduction
-
-=== Links
-
-https://opcfoundation.org/developer-tools/specifications-unified-architecture/part-1-overview-and-concepts
-
-https://opcfoundation.org/developer-tools/certification-specifications (Seems you have to become a OPC foundation member to access the Spec details)
-
-OPC-UA Membership: https://opcfoundation.org/membership/benefits/
diff --git a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/s7/index.adoc b/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/s7/index.adoc
deleted file mode 100644
index bb17ec7..0000000
--- a/plc4x-site-skin/src/it/plc4x-website/src/site/asciidoc/protocols/s7/index.adoc
+++ /dev/null
@@ -1,289 +0,0 @@
-//
-//  Licensed to the Apache Software Foundation (ASF) under one or more
-//  contributor license agreements.  See the NOTICE file distributed with
-//  this work for additional information regarding copyright ownership.
-//  The ASF licenses this file to You under the Apache License, Version 2.0
-//  (the "License"); you may not use this file except in compliance with
-//  the License.  You may obtain a copy of the License at
-//
-//      https://www.apache.org/licenses/LICENSE-2.0
-//
-//  Unless required by applicable law or agreed to in writing, software
-//  distributed under the License is distributed on an "AS IS" BASIS,
-//  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-//  See the License for the specific language governing permissions and
-//  limitations under the License.
-//
-:imagesdir: ../../images/
-
-== S7 Communication
-
-When communicating with S7 Devices there is a whole family of protocols, that can be used.
-In general you can divide them into `Profinet` protocols and `S7 Comm` protocols.
-The later are far simpler in structure, but also far less documented.
-The `S7 Comm` protocols are generally split up into two flavours: The classic `S7 Comm` and a newer version unofficially called `S7 Comm Plus`.
-
-=== Overview of the Protocols
-
-[ditaa,protocols-s7-osi]
-....
-                    :                                                       :             : implemented               :
-                    :                                                       :             :      |                    :
-                    :                       Profinet                        :             :      | S7 Protocol        :
-                    :                                                       :             :      V                    :
-- - - - - - - - - - +-------------+-------------+-------------+-------------+-------------+-------------+-------------+ - -
-                    |c0B0         |c0B0         |c0B0         |c0B0         |c05A         |c0BA         |c0BA         |
- Application        |             |             |             |             |             |             |             |
- Layer              |             |             |             |             |             |             |             |
-                    |             |             |             |             |             |             |             |
-                    | Profinet IO | Profinet IO | Profinet CBA| Profinet CBA|             |             |             |
-- - - - - - - - - - |   RT / IRT  |             |             |      RT     |             |             |             | - -
-                    |             |             |             |             |             |             |             |
- Presentation       |             |             |             |             |             |             |             |
- Layer              |             |             |             |             |     S7      |     S7      |     S7      |
-                    |             |             |             |             |    Comm     |    Comm     |    Comm     |
-                    |             |             |             |             |    Plus     |             |             |
-- - - - - - - - - - |             +-------------+-------------+             |             |             |             | - -
-                    |             |cAAA         |cAAA         |             |             |             |             |
- Session            |             |             |             |             |             |             |             |
- Layer              |             |     RPC     |    DCOM     |             |             |             |             |
-                    |             |             |             |             |             |             |             |
-                    |             |             |             |             |             |             |             |
-- - - - - - - - - - |             +-------------+-------------+             +-------------+-------------+-------------+ - -
-                    |             |cAAA         |cAAA         |             |cF6F                                     |
-                    |             |             |             |             |         ISO Transport Protocol          |
-                    |             |             |             |             |                 RFC 905                 |
-                    |             |             |             |             | (Class 0)                               |
-                    |             |             |             |             +---------------------------+             |
-                    |             |             |             |             |cFF6                       |             |
- Transport          |             |             |             |             | ISO on TCP                |             |
- Layer              |             |     UDP     |     TCP     |             |  RFC 1006                 |             |
-                    |             |             |             |             +---------------------------+             |
... 13376 lines suppressed ...