Google Git
Sign in
apache / plc4x / facb33c3937f3785295a8d2155139be913db84a6
commitfacb33c3937f3785295a8d2155139be913db84a6[log] [tgz]
authorCésar García <cesar.garcia@ceos.com.ve>Sat May 06 01:11:37 2023 -0400
committerCésar García <cesar.garcia@ceos.com.ve>Sat May 06 01:11:37 2023 -0400
treee158505d23c5256fe81e8797e80296ef16416d30
parent000455b3cd54fd428a25a0ef98aa7a27cd7c6538 [diff]
Verifying the execution sequence for a multi-instance system.
19 files changed
tree: e158505d23c5256fe81e8797e80296ef16416d30
  1. .github/
  2. .idea/
  3. .mvn/
  4. code-generation/
  5. images/
  6. licenses/
  7. media/
  8. plc4c/
  9. plc4go/
  10. plc4j/
  11. plc4net/
  12. protocols/
  13. reactors/
  14. sandbox/
  15. src/
  16. tools/
  17. .asf.yaml
  18. .dockerignore
  19. .editorconfig
  20. .gitignore
  21. build-reproducible.sh
  22. CHANGELOG.md
  23. compare-reproducible.sh
  24. CONTRIBUTING.md
  25. DEVELOPMENT.md
  26. Dockerfile
  27. jenkins.pom
  28. Jenkinsfile
  29. LICENSE
  30. mvnw
  31. mvnw.cmd
  32. NOTICE
  33. pom.xml
  34. README.md
  35. RELEASE_NOTES
README.md

Maven central License Jenkins Build Status Last commit Twitter Java Platform compatibility Go Platform compatibility C Platform compatibility Python Platform Compatibility

Table of contents

About Apache PLC4X

Apache PLC4X is an effort to create a set of libraries for communicating with industrial grade programmable logic controllers (PLCs) in a uniform way. We are planning on shipping libraries for usage in:

  1. Java
  2. Go
  3. C (not ready for usage)
  4. Python (not ready for usage)
  5. C# (.Net) (not ready for usage - abandoned)

PLC4X also integrates with other Apache projects, such as:

And brings stand-alone (Java) utils like:

  • OPC-UA Server: Enables you to communicate with legacy devices using PLC4X with OPC-UA.
  • PLC4X Server: Enables you to communicate with a central PLC4X Server which then communicates with devices via PLC4X.

It also provides (Java) tools for usage inside an application:

  • Connection Cache: New implementation of our framework for re-using and sharing PLC-connections
  • Connection Pool: Old implementation of our framework for re-using and sharing PLC-connections
  • OPM: Object-Plc-Mapping: Allows binding PLC fields to properties in java POJOs similar to JPA
  • Scraper: Utility to do scheduled and repeated data collection.

Getting started

Depending on the programming language, the usage will differ, therefore please go to the Getting Started on the PLC4X website to look up the language of choice.

Java

NOTE: Currently the Java version which supports building of all parts of Apache PLC4X is at least Java 11 (Currently with Java 19 the Apache Kafka integration module is excluded from the build as the plugins it requires are incompatible with this version)

See the PLC4J user guide on the website to start using PLC4X in your Java application: https://plc4x.apache.org/users/getting-started/plc4j.html

Developers

Environment

Currently, the project is configured to require the following software:

  1. Java 11 JDK: For running Maven in general as well as compiling the Java and Scala modules JAVA_HOME configured to point to that.
  2. Git (even when working on the source distribution)
  3. (Optional, for running all tests) libpcap/Npcap for raw socket tests in Java or use of passive-mode drivers
  4. (Optional, for building the website) Graphviz : For generating the graphs in the documentation

WARNING: The code generation uses a utility which requires some additional VM settings. When running a build from the root, the settings in the .mvn/jvm.config are automatically applied. When building only a sub-module, it is important to set the vm args: --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. In Intellij for example set these in the IDE settings under: Preferences | Build, Execution, Deployment | Build Tools | Maven | Runner: JVM Options.

A more detailed description is available on our website:

https://plc4x.apache.org/developers/preparing/index.html

For building PLC4C we also need:

All requirements are retrieved by the build itself

For building PLC4Go we also need:

All requirements are retrieved by the build itself

For building PLC4Py we also need:

  1. Python 3.7 or higher
  2. Python pyenv

For building PLC4Net we also need:

  1. DotNet SDK 6.0

With this setup you will be able to build the Java part of PLC4X.

The when doing a full build, we automatically run a prerequisite check and fail the build with an explanation, if not all requirements are meet.

Building with Docker

If you don't want to bother setting up the environment on your normal system and you have Docker installed, you can also build everything in a Docker container:

   docker build -t plc4x .

Getting Started

You must have at least Java 11 installed on your system and connectivity to Maven Central (for downloading external third party dependencies). Maven 3.6 is required to build, so be sure it's installed and available on your system.

NOTE: When using Java 19 currently the Apache Kafka integration module is excluded from the build as one of the plugins it requires has proven to be incompatible with this version.

NOTE: There is a convenience Maven-Wrapper installed in the repo, when used, this automatically downloads and installs Maven. If you want to use this, please use ./mvnw or mvnw instead of the normal mvn command.

NOTE: When running from sources-zip, the mvnw might not be executable on Mac or Linux. This can easily be fixed by running the following command in the directory.

$ chmod +x mvnw

NOTE: If you are working on a Windows system, please use mvnw.cmd instead of ./mvnw in the following build commands.

Build PLC4X Java jars and install them in your local maven repository

./mvnw install

You can now construct Java applications that use PLC4X. The PLC4X examples are a good place to start and are available inside the plc4j/examples directory.

The Go drivers can be built by enabling the with-go profile:

./mvnw -P with-go install

The C# / .Net implementation is currently in a work in progress state. In order to be able to build the C# / .Net module, you currently need to activate the: with-dotnet profiles.

./mvnw -P with-dotnet install

The Python implementation is currently in a somewhat unclean state and still needs refactoring. In order to be able to build the Python module, you currently need to activate the: with-sandbox and with-python profiles.

./mvnw -P with-sandbox,with-python install

In order to build everything the following command should work:

./mvnw -P with-c,with-go,with-python,with-sandbox install

Community

Join the PLC4X community by using one of the following channels. We'll be glad to help!

Mailing Lists

Subscribe to the following mailing lists:

See also: https://plc4x.apache.org/mailing-lists.html

Twitter

Get the latest PLC4X news on Twitter: https://twitter.com/ApachePlc4x

Contributing

There are multiple forms in which you can become involved with the PLC4X project.

These are, but are not limited to:

  • Providing information and insights
  • Testing PLC4X and providing feedback
  • 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 so don’t be afraid to step forward. If you'd like to contribute to PLC4X, have a look at our contribution guide!

Licensing

Apache PLC4X is released under the Apache License Version 2.0.