You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@plc4x.apache.org by ot...@apache.org on 2021/02/06 10:13:10 UTC
[plc4x] branch develop updated: updating webpage
This is an automated email from the ASF dual-hosted git repository.
otluk pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/plc4x.git
The following commit(s) were added to refs/heads/develop by this push:
new c1cd2c4 updating webpage
c1cd2c4 is described below
commit c1cd2c4ff7c39a724dc8a0cbb9bf7c4d95362780
Author: ottlukas <ot...@gmail.com>
AuthorDate: Sat Feb 6 11:12:20 2021 +0100
updating webpage
https://issues.apache.org/jira/browse/PLC4X-282
https://issues.apache.org/jira/browse/PLC4X-281
---
.gitignore | 1 +
src/site/asciidoc/index.adoc | 4 ++--
src/site/asciidoc/users/industry40.adoc | 32 ++++++++++++++++----------------
src/site/site.xml | 1 +
4 files changed, 20 insertions(+), 18 deletions(-)
diff --git a/.gitignore b/.gitignore
index 037c604..fcf9cb6 100644
--- a/.gitignore
+++ b/.gitignore
@@ -180,3 +180,4 @@ build-iPhoneSimulator/
# Temp stuff ...
/sandbox/plc4go/temp/
/plc4go/.idea/
+plc4j/examples/hello-storage-elasticsearch/.factorypath
diff --git a/src/site/asciidoc/index.adoc b/src/site/asciidoc/index.adoc
index 6ab9b28..8719ca9 100644
--- a/src/site/asciidoc/index.adoc
+++ b/src/site/asciidoc/index.adoc
@@ -235,8 +235,8 @@
<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>
+ <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>
diff --git a/src/site/asciidoc/users/industry40.adoc b/src/site/asciidoc/users/industry40.adoc
index e4cbecb..cfdea5b 100644
--- a/src/site/asciidoc/users/industry40.adoc
+++ b/src/site/asciidoc/users/industry40.adoc
@@ -26,21 +26,21 @@ Usually however in order to do this, a company needed to use the control system
This has tied companies to stick to the company they decided to use the PLCs of.
Making it almost impossible to switch to another vendor.
-In the last 20 years in the IT industry, the concept of Open-Source has come up and has more and more proven to be the engine of great innovation.
+In the last 20 years in the IT industry, the concept of open source has come up and has more and more proven to be the engine of great innovation.
Most of the biggest changes in how we create modern IT systems is a result of this.
Unfortunately the production industry has been missing a lot of this innovation.
-Only a small number of companies today use Open-Source software in their production systems.
+Only a small number of companies today use open source software in their production systems.
-=== Benefits of using Open-Source
+=== Benefits of using open source
-The benefit of using Open-Source could be huge:
+The benefit of using open source could be huge:
* Increased Flexibility
* Increased Stability
* Increased Extendability
* Improved Security
-* Great Cost-Reduction
+* Great Cost reduction
==== Increased Flexibility
@@ -68,17 +68,17 @@ If the company decided to utilize a public cloud provider, it makes things even
==== Improved Security
This is probably one of the most concerning aspects of modern production control systems.
-Right now, in order to run these systems, a lot of the most popular solutions require companies to run not up-to-date systems.
+Right now, in order to run these systems, a lot of the most popular solutions require companies to run not up to date systems.
If applying all updates, the company is risking either loss of commercial support or even loss of functionality.
-Therefore an attacker can probably be certain to be able to exploit certain vulnerabilities just by knowing the type and version of the used control-system.
+Therefore an attacker can probably be certain to be able to exploit certain vulnerabilities just by knowing the type and version of the used control system.
-==== Cost-Reduction
+==== Cost Reduction
-Well the probably biggest and most obvious cost-reduction factor is definitely, that if the software you are using is fee, you will not have to pay for it.
+Well the probably biggest and most obvious cost reduction factor is definitely, that if the software you are using is free, you will not have to pay for it.
Additionally, the ability to get the computing power of one insanely expensive system by using a cluster of cheap commodity systems, helps saving a lot of money.
-Being freed of the requirement to stick to the products of one vendor alonw anf to be able to choose the technology and the vendor of used systems freely will definitely also reduce costs.
+Being freed of the requirement to stick to the products of one vendor alone and to be able to choose the technology and the vendor of used systems freely will definitely also reduce costs.
=== Options to communicating with PLCs
@@ -89,7 +89,7 @@ In general there are two options for communicating with industrial PLCs:
** Software protocol converter
* Using a driver for direct communication
** Commercial drivers
-** Open-Source drivers
+** Open source drivers
Well protocol converters are all software in the end, but while a "hardware converter" is usually a closed hardware box that runs some sort of software, a "software converter" is usually an installable service or program that runs on a host system.
@@ -103,7 +103,7 @@ Another disadvantage is a slightly increased latency when making information ava
This is due to the fact that the protocol converter has to send a request to the PLC to get information and as soon as this information is returned to the converter this new information can only be passed on in the other protocol in the next request.
The usage of a protocol converter is probably the ideal solution, if all a company wants to do, is integrate PLCs communicating in one protocol into an existing system using a different protocol.
-In case of integrating open-source software, this usually is a protocol converter that converts into one of the well established open source protocols.
+In case of integrating open source software, this usually is a protocol converter that converts into one of the well established open source protocols.
The most widely used protocol here currently will probably be `MQTT`.
The option that provides the most possibilities is directly communicating with the PLCs.
@@ -112,13 +112,13 @@ Here the system can always directly access only the exact information required a
There is a wide variety of drivers available, that generally would allow writing software that directly accesses PLCs.
Unfortunately most of these are commercial drivers.
-While there is a number of open-source drivers, most of these have licenses that render them useless for commercial applications.
-Either they are licensed with restrictive licenses such as GPL or they are dual licensed with a restriction to non-commercial usage for the open-source version and the requirement to purchase a commercial license for commercial use-cases.
+While there is a number of open source drivers, most of these have licenses that render them useless for commercial applications.
+Either they are licensed with restrictive licenses such as GPL or they are dual licensed with a restriction to non-commercial usage for the open source version and the requirement to purchase a commercial license for commercial use cases.
The APIs of all drivers usually differs quite greatly from each one another. This makes it extremely difficult to create solutions that work with a variety of PLCs and protocols.
This is where `Apache PLC4X` comes in. It is the goal of `PLC4X` to provide a suite of drivers for communicating with industrial PLCs using a variety of protocols, but with a shared API and a license model, that is suitable for creating commercial applications.
-Hereby `PLC4X` forms the missing link between the automation and the open-source world.
-Making it possible to use the entire stack of open-source technologies to create a new generation of open industrial control systems.
+Hereby `PLC4X` forms the missing link between the automation and the open source world.
+Making it possible to use the entire stack of open source technologies to create a new generation of open industrial control systems.
diff --git a/src/site/site.xml b/src/site/site.xml
index 6291a62..1b593ed 100644
--- a/src/site/site.xml
+++ b/src/site/site.xml
@@ -50,6 +50,7 @@
<item name="Section Home" href="users/index.html"/>
<item name="Download" href="users/download.html"/>
<item name="Adopters" href="users/adopters.html"/>
+ <item name="Bug & Issue Tracker" href="developers/infrastructure/issues.html"/>
<item name="Commercial support" href="users/commercial-support.html"/>
<item name="Getting Started" href="users/gettingstarted.html">
<item name="Go" href="users/getting-started/plc4go.html"/>