Re: [VOTE] Create plc4x-extras repository

[Lukas Ott]

+1

Am Sa., 23. März 2024 um 20:03 Uhr schrieb Björn Haverland <
bjo...@coding-nexus.com>:

> +1
>
> Gesendet von Outlook für Android
> 
> From: Christofer Dutz 
> Sent: Saturday, March 23, 2024 4:49:17 PM
> To: dev@plc4x.apache.org 
> Subject: AW: [VOTE] Create plc4x-extras repository
>
> +1 (binding)
>
> cdutz
>
>
>
> Von: Christofer Dutz 
> Datum: Samstag, 23. März 2024 um 17:48
> An: dev@plc4x.apache.org 
> Betreff: [VOTE] Create plc4x-extras repository
> We would like to create a new git-repository “plc4x-extras” that will
> contain the integration modules as well as the examples.
>
> Please vote +1 if you are in favor of creating this repository and moving
> things from the main repository.
>
> Chris
>

Re: [DISCUSS] What do we want to look into/talk about on the Meetup/Workshop?

[Lukas Ott]

Mine are much simpler:
- Merge my pull request
* https://github.com/apache/plc4x/pull/1419 should be 5-10 minutes with
Sebastian.
- Go through PLC4PY with Ben and get things running on my side
  * Add Pip Package to https://pypi.org/ including release integration etc.
  * What is missing for PLC4Py to get out of the sandbox?
  * Find little tasks where I can start and not overwhelmed as one of
the rare-non developers in that project.
- Look into what you (Chris) did with ReactJS on the UI branch and get that
running

For the rest I am giving a +1 for your points.

Lukas

Am Mo., 18. März 2024 um 11:17 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Here some things I have on my mind:
>
>
>   *   Road to 1.0.0 (What’s still missing?)
>   *   Generating larger portions of the code (Mesasages & Request+Response)
>   *   Missing features:
>  *   Optimizer Framework (Optimize requests, by rewriting them)
>  *   Subscription Emulation (General purpose component, that uses the
> READ api to simulare subscriptions)
>  *   New/Advanced Scraper (Rewrite of the Scraper, that allows things
> like “read, triggered by subscription”)
>   *   How can we distribute the workload a bit better?
>   *   How can we grow the community?
>
> Chris
>

Re: So when do we want to meet on Saturday?

[Lukas Ott]

Hi all,

according to my travel plans.
My train arrives in Frankfurt Main Station at 14:00.
Connection on Sat. 23.03.2024
- from Oerestad st, departure 00:46 Gl. 2 with IC 1401
- to Frankfurt(Main)Hbf, arrival 14:00 Gl. 6 with ICE 75
Verbindung ansehen:
https://www.bahn.de/buchung/start?vbid=c10e14c7-cd2b-4691-90f9-82e504366818

So I can not join earlier.

Lukas


Am Mo., 18. März 2024 um 08:59 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Hi all,
>
> So, when do we want to meet on Saturday?
>
> I would propose something round 13:00 (could also do even earlier)
>
> Chris
>
>

Re: [VOTE] Apache PLC4X 0.12.0 RC2

[Lukas Ott]

+1 (binding)

Lukas - otluk

[x] Download all staged artifacts under the url specified in the release
vote email.
[x] Verify the signature is correct.
[x] Check if the signature references an Apache email address.
[x] Verify the SHA512 hashes.
[x] Unzip the archive.
[x] Verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES files in
the extracted source bundle.
[x] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in
the extracted source bundle.
[x] [RM] Verify the staged source README, RELEASE_NOTE files correspond to
those in the extracted source bundle.
[x] [RM] Run RAT externally to ensure there are no surprises.
[x] Search for SNAPSHOT references
[x] Build the project according to the information in the README.md file.

Built with: ./mvnw -P
with-c,with-dotnet,with-java,with-python,with-sandbox,enable-all-checks,update-generated-code
install -X

OS: Linux Mint 21.3 x86_64
Kernel: 6.5.0-18-generic
openjdk version "11.0.21" 2023-10-17
OpenJDK Runtime Environment (build 11.0.21+9-post-Ubuntu-0ubuntu122.04)
OpenJDK 64-Bit Server VM (build 11.0.21+9-post-Ubuntu-0ubuntu122.04, mixed
mode, sharing)
.NET - SDK-Version: 8.0.102
Python 3.10.12

Am Fr., 16. Feb. 2024 um 18:09 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Apache PLC4X 0.13.0 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: v0.12.0
> Hash for the release tag: 47af22589818dc83c274dd6299449ec1a36f8fae
>
> 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-1054
> [2] https://dist.apache.org/repos/dist/dev/plc4x/0.12.0/rc2
> [3] https://www.apache.org/dev/release.html#approving-a-release
> [4]
> https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release
>
>

Re: [CANCELED][VOTE] Apache PLC4X 0.12.0 RC1

[Lukas Ott]

-1 (binding)

Found the mentioned issue and can confirm that I can not build from source.

Lukas

[OK] Download all staged artifacts under the url specified in the release
vote email.
[OK] Verify the signature is correct.
[OK] Check if the signature references an Apache email address.
[OK] Verify the SHA512 hashes.
[OK] Unzip the archive.
[OK] Verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES files
in the extracted source bundle.
[MINOR] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files
in the extracted source bundle.

  *   It turns out the “build with everything” statement needs an
additional “update-generated-code” profile to really build everything.

Am Fr., 16. Feb. 2024 um 14:56 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Found an issue … will fix it and stage an RC2
>
> Chris
>
> Von: Christofer Dutz 
> Datum: Freitag, 16. Februar 2024 um 14:54
> An: dev@plc4x.apache.org 
> Betreff: AW: [VOTE] Apache PLC4X 0.12.0 RC1
> -1 (binding)
>
> Chris
>
> [OK] Download all staged artifacts under the url specified in the release
> vote email.
> [OK] Verify the signature is correct.
> [OK] Check if the signature references an Apache email address.
> [OK] Verify the SHA512 hashes.
> [OK] Unzip the archive.
> [OK] Verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES files
> in the extracted source bundle.
> [MINOR] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files
> in the extracted source bundle.
>
>   *   It turns out the “build with everything” statement needs an
> additional “update-generated-code” profile to really build everything.
> [OK] [RM] Verify the staged source README, RELEASE_NOTE files correspond
> to those in the extracted source bundle.
> [OK] [RM] Run RAT externally to ensure there are no surprises.
> [FAIL] Search for SNAPSHOT references
>
>   *   It seems the code-generation tests were not run during the release
> and therefore the artifacts there were not updated :-/
> [OK] 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.
>
>
> Von: Christofer Dutz 
> Datum: Freitag, 16. Februar 2024 um 13:58
> An: dev@plc4x.apache.org 
> Betreff: [VOTE] Apache PLC4X 0.12.0 RC1
> Apache PLC4X 0.12.0 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: v0.12.0
> Hash for the release tag: 90fc8c00de051abcad2789d7622c8d497209def4
>
> 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-1052
> [2] https://dist.apache.org/repos/dist/dev/plc4x/0.12.0/rc1
> [3] https://www.apache.org/dev/release.html#approving-a-release
> [4]
> https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release
>

Re: [DISCUSS] How about releasing 0.12.0?

[Lukas Ott]

+1 for releasing as we have closed so many issues. and we have now a proper
Linkedin Page to announce ;-)

Am Mi., 14. Feb. 2024 um 20:53 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Hi all,
>
> so in the past few weeks we managed to cut the number of open issues by
> half and merge in all the big running initiatives.
>
> I would really love to have a new version available at Building IoT next
> week.
>
> What do you think? Should we do a new release?
>
> I would also really love to test the scripts for releasing reproducible
> builds with docker that I whipped up over the last months.
>
> Chris
>
>

Re: [DISCUSS] How about registering a profile for ApachePLC4X on LinkedIn?

[Lukas Ott]

+1

As we would mainly follow other Apache projects like:
- https://www.linkedin.com/company/apache-streampipes/
- https://www.linkedin.com/company/apachespark/
- https://www.linkedin.com/company/apache-beam/
- https://www.linkedin.com/company/apache-airflow/
- https://www.linkedin.com/company/apache-hudi/
- https://www.linkedin.com/company/apache-nifi/
- https://www.linkedin.com/company/apache-cassandra/
- https://www.linkedin.com/company/apachehop/
- https://www.linkedin.com/showcase/apache-ignite/
- https://www.linkedin.com/company/apache-couchdb/
- https://www.linkedin.com/company/apache-apisix/
- https://www.linkedin.com/company/tinkerpop

Am So., 4. Feb. 2024 um 11:00 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Hi all,
>
> it seems that LinkedIn have dropped the hashtags … so people interested in
> ApachePLC4X can no longer follow the hashtag.
> What do you folks think? Should I register an account (setting our private
> list as email address)?
>
> I would say: Yes.
>
>
> Chris
>

Re: [DRAFT] December board report

[Lukas Ott]

Thank you Chris!

Christofer Dutz  schrieb am Do., 14. Dez. 2023,
08:35:

> Ok … report is published,
>
> I added a point about Lukas’ work on the OPC-UA secure-connection part.
>
> Chris
>
> Von: Christofer Dutz 
> Datum: Dienstag, 12. Dezember 2023 um 09:10
> An: dev@plc4x.apache.org 
> Betreff: [DRAFT] December board report
> Hi all,
>
> it’s reporting time again … I went through our commit history and tried to
> compile a list of the most noticeable changes.
> Could you please have a look if anything is missing?
>
> I’ll post it tomorrow.
>
> Chris
>
> ---
>
>
> # Description:
> The mission of the Apache PLC4X project is creating a set of libraries for
> communicating with industrial programmable logic controllers (PLCs) using a
> variety of protocols but with a shared API.
>
> ## Project Status:
> Current project status: ongoing with moderate activity
> Issues for the board: none
>
> ## Membership Data:
> Apache PLC4X was founded 2019-04-17 (5 years ago)
> There are currently 21 committers and 13 PMC members in this project.
> The Committer-to-PMC ratio is roughly 3:2.
>
> Community changes, past quarter:
> - No new PMC members. Last addition was César García on 2021-10-01.
> - No new committers. Last addition was Jinlin Hong on 2022-11-02.
>
> ## Project Activity:
> The most noteworthy points for the last 3 months were definitely:
> - Our last release after exactly one year (didn't copy+paste that)
> - Work on the Profinet Driver
> - Initiation of a new Web-Based UI tool
> - Major updates in the S7 driver (datatype-handling)
> - Work on PLC4PY which now has a first working Modbus driver
> - Refactored the way transports are configured
> - Prepared the build for reproducible builds
> - Multiple Bugfixes
>
> Recent releases:
> 0.11.0 was released on 2023-10-06.
> 0.10.0 was released on 2022-10-06.
> 0.9.1 was released on 2021-09-21.
>
> ## Community Health:
> While I was a bit worried about activity inside the project in my last
> reports, things are looking a bit different now. There's currently plenty
> activity on various initiatives.
>
> Following the last release we received a number of new bug-reports and
> fixes
> by new folks. We're definitely not going to wait another year for a new
> release.
>

Re: [VOTE] Drop Java 1.8 Support

[Lukas Ott]

+1

Otto Fowler  schrieb am Mo., 11. Dez. 2023, 04:26:

>  +1 binding
>
> On December 8, 2023 at 9:16:19 AM, Christofer Dutz (
> christofer.d...@c-ware.de) wrote:
>
> Hi all,
>
> in the past we have settled with requiring Java 11 for building plc4x and
> making sure the libraries we build are compatible with Java 1.8.
> Now it looks as if some of our libraries are no longer runnable on Java 1.8
> and we would need one of the following two options:
>
>
> 1. Re-Enable the animal-sniffer-plugin to ensure binary compatability with
> Java 1.8 and fix the location in the code
> 2. We officially drop Java 1.8 support
>
> As we like to vote with “+1” and “-1”, I therefore start this vote as:
>
> Do we want to officially drop Java 11 support?
>
> Chris
>

Re: Convert the Milo-based test suite into one using our integration-test framework?

[Lukas Ott]

+1 for disabling Milo, we should be able to build with docker compose up
without running into these issues.

If someone needs Milo test then actively enabling them seems like a
reasonable plan.

Lukad

Christofer Dutz  schrieb am Mo., 25. Sept. 2023,
10:59:

> Hi Lukasz,
>
> Well … we need a test-suite that runs reliably … in the past I usually ran
> into issues with Milo not running on various configurations.
> Admittedly I’m just no longer willing to invest the little time into
> fixing issues with this bit of software.
>
> For example, running “docker compose up” currently fails because in docker
> something seems to fail to startup, which doesn’t fail when running on the
> hardware directly.
>
> I’m happy for a profile “option-with-milo-tests” that actively enables
> Milo-based tests.
> (I would insist on actively enabling it instead of actively disabling it
> as otherwise people will continuously report problems with it)
>
> Chris
>
>
>
> Von: Łukasz Dywicki 
> Datum: Montag, 25. September 2023 um 10:49
> An: dev@plc4x.apache.org 
> Cc: Patryk Gała 
> Betreff: Re: Convert the Milo-based test suite into one using our
> integration-test framework?
> Milo is a bit painful, but it does more than we currently can do in our
> opcua implementation. Also, from basic look I had into why some of tests
> fail, it looks primarily like resource lookup issue. For example I
> spotted a swallowed null pointer exception which comes from our code,
> not Milo.
>
> We will have difficult times making test framework for testing security
> with certificates and Java crypto apis. Please hold on with major
> changes in this area, as we intend using it to automate testing of UA
> security policies (sign, sing) using various modes (basic rsa,
> basic aes etc.).
> Back then Patryk had an idea of making a "test container" for Milo which
> would separate it into its own process. Obviously it will need a bit of
> work and will become a prerequisite to eventual test refactoring,
> however it will make it (fail) same way for everyone. ;)
>
> Best,
> Łukasz
>
> On 25.09.2023 10:38, Christofer Dutz wrote:
> > Hi all,
> >
> > I know that I have spent many days tracking down oddness of problem with
> OPC-UA tests, that all tracked down to Milo behaving oddly on various
> platforms (Doesn#t start in Parallells VMs, has issues being run in docker,
> …).
> > When building PLC4X I put a lot of effort into our integration-test
> framework, which should allow testing our drivers on various platforms and
> languages without needing a real (or simulated) device.
> >
> > I think we should translate the Milo based tests into ones using our
> DriverTestsuite framework, as admittedly I’m fedup with Milo …
> >
> >
> > Chris
> >
> >
>

Re: [VOTE] Apache PLC4X Build-Tools Code-Generation 1.7.0 RC1

[Lukas Ott]

+1 (binding)

Built on Linuxmint - LMDE 6 using openjdk 17.0.8 2023-07-18
OpenJDK Runtime Environment (build 17.0.8+7-Debian-1deb12u1)
OpenJDK 64-Bit Server VM (build 17.0.8+7-Debian-1deb12u1, mixed mode,
sharing)


Lukas

[OK] Download all staged artifacts under the url specified in the release
vote email.
[OK] Verify the signature is correct.
[OK] Check if the signature references an Apache email address.
[OK] Verify the SHA512 hashes.
[OK] Unzip the archive.
[OK] Verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES files
in the extracted source bundle.
[OK] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in
the extracted source bundle.
[OK] [RM] Verify the staged source README, RELEASE_NOTE files correspond to
those in the extracted source bundle.
[OK] [RM] Run RAT externally to ensure there are no surprises.
[OK] Search for SNAPSHOT references
[OK] Search for Copyright references, and if they are in headers, make sure
these files containing them are mentioned in the LICENSE file.
[OK] Build the project according to the information in the README.md file.

Am Fr., 22. Sept. 2023 um 13:32 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> +1 (binding)
>
> Built on Mac OS 13.5.2 with Apple M2 Max using Java 11.0.20 (Amazon
> Coretto Build)
>
> Chris
>
> [OK] Download all staged artifacts under the url specified in the release
> vote email.
> [OK] Verify the signature is correct.
> [OK] Check if the signature references an Apache email address.
> [OK] Verify the SHA512 hashes.
> [OK] Unzip the archive.
> [OK] Verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES files
> in the extracted source bundle.
> [OK] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in
> the extracted source bundle.
> [OK] [RM] Verify the staged source README, RELEASE_NOTE files correspond
> to those in the extracted source bundle.
> [OK] [RM] Run RAT externally to ensure there are no surprises.
> [OK] Search for SNAPSHOT references
> [OK] Search for Copyright references, and if they are in headers, make
> sure these files containing them are mentioned in the LICENSE file.
> [OK] Build the project according to the information in the README.md file.
> [OK] [RM] Build the project with all with-xyz profiles and tests enabled
> and an empty maven local repo.
>
>
> Von: Christofer Dutz 
> Datum: Freitag, 22. September 2023 um 13:20
> An: dev@plc4x.apache.org 
> Betreff: [VOTE] Apache PLC4X Build-Tools Code-Generation 1.7.0 RC1
> Apache PLC4X Build-Tools Code-Generation 1.7.0 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/1.7.0
>Hash for the release tag: 43b93a139c9580325c26082e7272fc224238355f
>
>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-1049
>[2]
> https://dist.apache.org/repos/dist/dev/plc4x/build-tools/code-generation/1.7.0/rc1/
>[3]
> https://www.apache.org/dev/release/validation.html#approving-a-release
>[4] https://plc4x.apache.org/developers/release/validation.html
>

Re: Connection Issue with Siemens PLC via OPC UA

[Lukas Ott]

Hi Antonio,

Welcome to the PLC4X Community.

Can you add some more details how you are using the library.

You can also add more details as GitHub Issue.

So we need the connection string you are using and potentially the actual
error messages you are receiving.

For instance are you sure you are using OPC UA and not S7?

Thank you!

Best Regards,
Lukas

FARIELLO, ANTONIO  schrieb am Do.,
29. Juni 2023, 11:17:

> Dear PLC4x Team,
>
>
>
> I'm writing to you to document a problem we encountered when trying to
> connect to a Siemens PLC via OPC UA using a Java client.
>
>
>
> We programmed a Java client to establish a connection to the Siemens PLC,
> following the recommended methods and procedures.
>
> However, we were unable to get a working connection. During our tests, we
> were connected to a switch via network cable, and the same switch was in
> turn connected to the PLC.
>
>
>
> Running the test several times (without any changes to the code) we
> obtained 3 different results:
>
>
>
> 1) Error: "Connection terminated by remote"
>
>
>
> 2) Error: "An established connection was aborted by the software in your
> host machine"
>
>
>
> 3) Connection established successfully (very rarely).
>
>
>
>
>
> I would like to point out that we have tested the functionality of other
> tools such as Apache Milo and UA Expert, which successfully connected to
> Siemens PLC using the same network environment. These tools established a
> connection without problems, proving that the PLC and its configuration are
> correct.
>
>
>
> Therefore, we are interested in understanding what could be the cause of
> the problem we are having with the Java client that we have developed using
> PLC4x. We can rule out a malfunction of the PLC or its configuration, as
> other tools work fine.
>
>
>
> Thank you for the attention dedicated to our request and I look forward to
> your response to resolve this issue.
>
>
>
> Best regards,
>
> Antonio.
>
>
>
>
>
> *Antonio Fariello*
>
> Professional | Industrial Operations Engineer
>
>
>
> Capgemini Italia | Italy
>
>
>
> antoniofarie...@capgemini.com
>
> www.capgemini.com
>
> 
> 
>
>
>
> [image: twitter]  [image: linkedin]
>  [image: facebook]
>  [image: youtube]
>  [image: soundcloud]
>  [image: Résultat de recherche
> d'images pour "instagram logo rond"] 
>   
> 
>
> 7  Switch off  |qRecycle | P Print only if necessary
>
>
> This message contains information that may be privileged or confidential
> and is the property of the Capgemini Group. It is intended only for the
> person to whom it is addressed. If you are not the intended recipient, you
> are not authorized to read, print, retain, copy, disseminate, distribute,
> or use this message or any part thereof. If you receive this message in
> error, please notify the sender immediately and delete all copies of this
> message.
>

Re: Update the S7 driver to only say "subscriptions supported" for S7 devices that actually support it?

[Lukas Ott]

+1 , yes indeed it seems obviously misleading.

Am Mi., 14. Juni 2023 um 08:07 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Hi,
>
> Again, a user seems to have been mis-led by
> “plcConnection.getMetadata().canSubscribe()”.
> I think we need to return a different value here based on the detected S7
> version (Or the one the user provided).
>
> Chris
>

Re: [DISCUSS] Adding a Publish-API?

[Lukas Ott]

+1 to add a Publish API. I think so too that we really have a need for an
API like that to support Pub-Sub Protocols like MQTT and AMQP in a more
natural way.

Lukas

Am Mi., 31. Mai 2023 um 14:32 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Hi all,
>
> I’m currently contining to work on Ben’s PROFINET work, hopefully pushing
> the PN driver to a really useable form in this month.
>
> However, we did come across something that we haven’t had before, but I
> think we will more and more come across the more Fieldbus protocols we will
> be supporting.
>
> We currently have the Read and the Write API for Async reading and writing
> and we have the Subscription API for subscribing events from the PLC.
> You might have noticed what’s generally missing here? … Profinet allows us
> to setup not only a subscription where we’ll be cyclically receive values,
> it also allows us to publish values to the PN devices.
>
> The problem with this is, that it needs to be setup and all published
> values need to be published in every cycle.
>
> It would be quite problematic to use our Write API for this … but it’s
> actually a lot more like our Subscription API … just like with the async
> variants, the write direction is simply the read-direction plus a value.
>
> So my proposal would be to add a Publish API, where the user sets up which
> tags he intends to write with which initial values and the driver would
> start sending that data on every cycle … now the API could receive
> Update-Events from the Application and simply update the local values and
> have the updated values posted on the next cycle.
>
> I am pretty sure we’ll need something like that for EtherCAT and IOLink
> etc. … and it sort of feels like it’s actually a missing main component of
> the API.
>
> We might even be able to use this to support stuff like MQTT?
>
>
> What do you folks think?
>
> Chris
>

Re: [DISCUSS] Add GitHub Discussions?

[Lukas Ott]

Hi,

I personally started using GitHub Discussions and I am really a fan of it
as it seamlessly integrates with our code repository.

Especially as Confluence is not so visible and the linking and switching
from an article to an issue and vice versa.

So I am in favor as well. Plus we would have really everything in one place.

Lukas

Am Mo., 15. Mai 2023 um 16:39 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Hi all,
>
> So, my PR for infra just got merged and we can now customize the
> auto-generated emails sent for GitHub Discussions … so now I would like to
> hear your thoughts on if we want to enable GitHub Discussions for PLC4X
>
> I would be in favor for it.
>
>
> Chris
>

Re: [DISCUSS] Have some sort of multi-connection?

[Lukas Ott]

+1 for building a more generic solution for multi-connections as it helps
for PROFINET and ADS as well

Am Fr., 5. Mai 2023 um 15:17 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Hi all,
>
> while going through Cesar’s changes I noticed that he actually addressed
> something I keept on avoiding ;-) ... Multi-Connections. I know I needed
> them for PROFINET (Raw base transport and UDP config) as well as ADS (TCP
> base transport and UDP config) ... I solved the problem by implementing the
> UDP stuff manually, completely avoiding Netty .. but I think it would be
> more in the spirit of PLC4X to do it in a cleaner way ... as Cesar did it.
>
> However, Cesars version is hard-coded for S7 and S7HA. I would suggest to
> build a more generic solution ... what do you folks think?
>
> Chris
>

Re: Need help to figure Dependency and Project work flow-regards

[Lukas Ott]

Hi Laveenkumar,

Welcome to the PLC4X Project.

Sorry I do not understand your question.

First can you tell us which language you are trying to use?
- Java
- Go
or C? (are you trying to deploy PLC4C on an Arduino?)

Second we can not see any links.

Please provide a code example or some more description what you are trying
to do

Thank you!

With regards
Lukas

Am So., 23. Apr. 2023 um 17:52 Uhr schrieb Laveenkumar Sridhar <
lave...@gmail.com>:

> Dear Team,
>
>
> Am Sridhar- India , working on Startup which our own plc Board (esp32,
> arduino base) will connect to Mqtt, and plc4x , kafka . Which helps to work
> Industry 4.0 .. Small scale based industries..
>
> Coming to point!! Our programmer developed PLC LD AND DUMPED into plc board
> !! Also that code sended to Mqtt .
>
> Here plc4x how to connect and to work with plc4x lot of doubts came.
>
> Can you team support us how to sort this out?
>
>
>
> With Regards
> Laveenkumar Sridhar
> Hyderabad
> 9789136125 - Whatsapp
>

Re: [DISCUSS] Should we remove the PLC4X Connector from the Confluent Hub

[Lukas Ott]

As we only see complains from confluent and no support. We should remove
and may ping some of the Confluent guys again to highlight if you want
PLC4X connector then please do at least the maintenance work and patch
security and keep the connector up to date. In my humble opinion.
Lukas

Am Mi., 12. Apr. 2023 um 05:56 Uhr schrieb Ben Hutcheson <
ben.hut...@gmail.com>:

> This is the discussion thread for the vote on removing the PLC4X Kafka
> Connector.
> Please keep all discussions on this thread.
>

Re: [VOTE] Should we remove the PLC4X Connector from the Confluent Hub

[Lukas Ott]

+1

Lukas

Am Mi., 12. Apr. 2023 um 08:19 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> +1
>
> Chris
>
> Gesendet von Outlook für Android
> 
> From: Ben Hutcheson 
> Sent: Wednesday, April 12, 2023 5:50:27 AM
> To: dev@plc4x.apache.org 
> Subject: [VOTE] Should we remove the PLC4X Connector from the Confluent Hub
>
> Hi,
>
> The work expected from Confluent to maintain the PLC4X Kafka Connector in
> the hub, historically hasn't been in line with our release schedule. And
> seeing as though there isn't really anybody that is actively maintaining
> the PLC4X Kafka Connector, I would like to vote on removing the package
> from the Confluent Hub.
> https://www.confluent.io/hub/apache/kafka-connect-plc4x-plc4j
>
> Please vote:
>
> [ ] +1: Remove the package from the Confluent Hub
> [ ] 0: No opinion
> [ ] -1: Keep the package in the Confluent Hub
>
> The vote will remain open for 72 hours, the majority vote will decide.
>
> Kind Regard
>
> Ben
>

Re: Introduction to PLC4X

[Lukas Ott]

Hello Andoni,

Welcome to the PLC4X Community:-)

Glad to see you on the list.

Nice to see someone interested in our framework.

Cheers,
Lukas

Am Do., 16. Feb. 2023 um 14:21 Uhr schrieb Andoni Angulo
:

> Hello everyone,
>
> My name is Andoni Angulo (LaManoServida on GitHub) and I am another member
> from Zylk who is working on Nifi integration.
>
> I am glad to be part of this community and I look forward to contributing
> to PLC4X.
>
> Kind regards,
> Andoni Angulo
>
> I+D en [ https://www.zylk.net/ | ZYLK ] - consultoría open source
> Ribera de Axpe, 11
> Edificio A, módulo 201-203
> 48950 Erandio (Bizkaia)
>

Re: [DISCUSS] Generally move to using "Context" objects inside our generated code?

[Lukas Ott]

+1 yes Otto s comment is correct so it seems to be the next logical step.

Otto Fowler  schrieb am Sa., 4. Feb. 2023, 15:42:

>  Any DSL at some point will consider stack / call / variable contexts.
> This seems reasonable.
>
> From: Christofer Dutz 
> 
> Reply: dev@plc4x.apache.org  
> Date: February 4, 2023 at 05:18:59
> To: dev@plc4x.apache.org  
> Subject:  [DISCUSS] Generally move to using "Context" objects inside our
> generated code?
>
> Hi all,
>
> recently I have been working on supporting dynamic tags like “_itemCount”,
> “_curItem” and “_lastItem” in array elements.
>
> In java I used ThreadLocals for this as it felt like a Java-Native way and
> it wouldn’t blow up the signatures of our Parser, Serializer and
> GetLengthInXYZ methods.
>
> Now when looking for something similar in Go, it seems in such cases
> Contexts are used. These are sort of like a HashMap wrapped with little
> util methods. In this HashMap you pass along values that are “in context” …
> if you change the context, a copy of the old context is created and then
> the updated/added values are updated/added to the HashMap.
>
> So, in an array I add the additional information to the existing one by:
>
> arrayCtx := spiContext.CreateArrayContext(ctx, int(_numItems),
> int(_curItem))
>
>
> and then simply pass in the „arrayContext”. And for accessing it I simply
> for this:
>
> spiContext.GetLastItemFromContext(ctx)
>
>
>
> Admittedly I’m not a big fan of crating copies of the full context every
> time, I would prefer to be able to push to sort of a context stack, but I
> guess that’s the way things work in Go.
>
>
>
> When I wanted to add the functionality of Java and Go to PLC4C I was a bit
> stuck, as neither concept really existed.
>
>
>
> However thinking a bit more about it, adding the concept of Contexts to C
> was actually quite simple.
>
>
>
> Now that got me thinking:
>
> Shouldn’t we implement the same pattern for Java? It should be easy to
> implement.
>
>
>
> And while I was thinking, I even thought: Shouldn’t we extend this idea and
> also get the ReadBuffer, WriteBuffer, the Encoding, the ByteOrder and
> anything we’re currently passing along with “WithXYZOption” var-args, into
> these Contexts and simply pass along one Context object?
>
> I think this would clean up the code quite a bit.
>
>
>
> What do you think?
>
>
>
> Chris
>

Re: [DISCUSS] Send dependant emails to commits@ or a new list (notifications@)?

[Lukas Ott]

+1 for getting rid of them on our developer list. where we should be able
to discuss topics and do releases :-)

Am Do., 19. Jan. 2023 um 18:08 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Hi all,
>
> today I learned, that it’s possible to redirect bot-notifications to
> different lists.
> I would really love to rid us from the dependabot emails.
> I guess nobody pays much attention to them as Sebasitan constantly takes
> care of them.
>
> Having these emails out of our list would be great.
>
>
> https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Specialschemesforbots
>
> What do you think?
>
> Chris
>

Re: [DISCUSS] Removing the Apache Feather from our logos?

[Lukas Ott]

Yeah sure we can remove the feather. We have a lot of other Toddy Logos
with PLC s and so on anyway.

I am just wondering how we could at least incorporate the colors from the
ASF.

Cheers
Luk

Christofer Dutz  schrieb am So., 15. Jan. 2023,
12:21:

> Hi all,
>
> I know that initially I had our designer add the feather to our logo, to
> lay emphasis on the relation to the ASF.
>
> Now over the last few years there have been many rounds of fruitless
> discussions on changing the name of the Apache Software Foundation as it
> would be harming the Native American Cultural Groups.
> Many people are discussing on how we could rename the ASF or which steps
> we could do.
>
> One argument, that even if “Apache Webserver” was derived from “A Patchy
> Webserver” as it initially was a webserver with a lot of patches. Nobody
> can argue against the fact that the feather does refer more to native
> Americans than towards a set of patches.
>
> So, I thought … how about us starting to do a first step and we remove the
> feather from our logo?
>
> What are your thoughts on this?
>
> Chris
>

Re: [DISCUSS] Having a in-person community meetup?

[Lukas Ott]

If I can fit it into my schedule, count me in as well.

Lukas

Am Mi., 11. Jan. 2023 um 11:24 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> So right now, I count 9 people (one of them planning on using TAC), right?
>
>
>   *   Ben Hucheson
>   *   Cesar Garcia (TAC)
>   *   Christofer Dutz
>   *   Dominik Riemer
>
>   *   Julian Feinauer (I guess)
>   *   Lukasz Dywicki
>   *   Niclas Hedhman
>   *   Niclas Merz
>   *   Willem Remie
>
> Anyone else? Or did I list someone in the wrong category?
>
> Chris
>
>
> From: Niklas Merz 
> Date: Wednesday, 11. January 2023 at 08:56
> To: dev@plc4x.apache.org 
> Subject: Re: [DISCUSS] Having a in-person community meetup?
> On 2023-01-10 14:33, Christofer Dutz wrote:
> > So please speak up … who would be interested to come? And who would
> > need assistance and if yes: from where you would be coming.
>
> I would also consider attending on my own cost. Both Frankfurt and
> Stuttgart would be great options for me.
>

Re: [DISCUSS] Having a in-person community meetup?

[Lukas Ott]

cool :-) would be fun so that I can finally ask all my questions in person
;-)

Am Mi., 4. Jan. 2023 um 16:37 Uhr schrieb Ben Hutcheson <
ben.hut...@gmail.com>:

> Sounds like fun.
>
> Ben
>
> On Wed, Jan 4, 2023 at 4:30 PM Christofer Dutz 
> wrote:
>
> > Ok …
> >
> > Uwe from codecentric FFM (the new office) was delighted my me asking if
> > codecentric would be willing to accommodate us during the hackathon.
> > So, that would be one option … I guess Sebastian would like that option
> ;-)
> >
> > Chris
> >
> >
> > From: Christofer Dutz 
> > Date: Wednesday, 4. January 2023 at 16:24
> > To: dev@plc4x.apache.org 
> > Subject: [DISCUSS] Having a in-person community meetup?
> > Hi all,
> >
> > some of you remember the times around our graduation. We had loads of
> > in-presence meetups and that really fuled the drive in the community.
> > Covid sort of was the opposite and it felt like we were sort of losing
> our
> > drive a bit.
> >
> > Now that Ben now also lives in Germany, I wanted to bring up this topic
> > again.
> >
> > What do you folks think of a 2-3-day hackathon on PLC4X (and possibly the
> > Historian)?
> > Probably we would need to sort of do it Friday to Sunday.
> >
> > Also currently probing if we could not get TAC to help finance the
> travels
> > of everyone except me.
> >
> > Even if I would love a week on the Bahamas, probably something in Germany
> > somewhere round Frankfurt or Stuttgart would make sense
> > (from the perspective of people being able to come there via public
> > transport and keeping the connection options simple and cheaper)
> >
> > What do you folks think.
> >
> >
> > Chris
> >
>

Re: Simple modbus application does not terminate

[Lukas Ott]

+1 -> thank you Niels :-)

Am Mo., 2. Jan. 2023 um 15:02 Uhr schrieb Niels Basjes :

> Thanks for clarifying.
> I've added this to the example (+ cleanups):
> https://github.com/apache/plc4x/pull/724
>
> On Mon, Jan 2, 2023 at 2:43 PM Christofer Dutz 
> wrote:
>
> > Hi Niels,
> >
> > If you find the time to have a little bit deeper look and find a solution
> > … we’re super happy about PRs ;-)
> > This behavior is sort of know behavior and we never really got to
> > addressing it. I would assume it’s generally because of some Netty-Crap
> … I
> > would so love to get rid of Netty.
> >
> > Chris
> >
> >
> >
> > From: Niels Basjes 
> > Date: Monday, 2. January 2023 at 14:41
> > To: dev@plc4x.apache.org 
> > Subject: Re: Simple modbus application does not terminate
> > I found a workaround by digging through the example code:
> > End the application with an explicit System.exit(0);
> >
> >
> >
> https://github.com/apache/plc4x/blob/b784dedaa787e52e7907085bf096e8ea2e093f3b/plc4j/examples/hello-world-plc4x-read/src/main/java/org/apache/plc4x/java/examples/helloplc4x/read/HelloPlc4xRead.java#L93
> >
> > Then it does terminate the application.
> >
> > Niels
> >
> >
> > On Mon, Jan 2, 2023 at 12:30 PM Niels Basjes  wrote:
> >
> > > Hi,
> > >
> > > I'm trying out building some stuff using plc4j/modbus and I have some
> > > questions about that.
> > >
> > > I created a very simple test that connects using modbus-tcp and
> retrieves
> > > some registers.
> > > Essentially it is this example (using the latest snapshot) but with
> > modbus
> > > https://plc4x.apache.org/users/getting-started/plc4j.html
> > > So I use this connect string "modbus-tcp:tcp://127.0.0.1:1502" and
> > > request ModbusTag.of("3x1:UINT[100]").
> > >
> > > The problem I have is that after the data has been read and printed
> > (which
> > > works as expected)  the application does not terminate.
> > >
> > >
> > > In the console I see (among other things) at the start:
> > > 12:17:11,811 [INFO ] PlcDriverManager:   48:
> > > Instantiating new PLC Driver Manager with class loader
> > > jdk.internal.loader.ClassLoaders$AppClassLoader@251a69d7
> > > 12:17:11,813 [INFO ] PlcDriverManager:   52:
> > > Registering available drivers...
> > > 12:17:11,818 [INFO ] PlcDriverManager:   59:
> > > Registering driver for Protocol modbus-ascii (Modbus ASCII)
> > > 12:17:11,819 [INFO ] PlcDriverManager:   59:
> > > Registering driver for Protocol modbus-rtu (Modbus RTU)
> > > 12:17:11,820 [INFO ] PlcDriverManager:   59:
> > > Registering driver for Protocol modbus-tcp (Modbus TCP)
> > > 12:17:11,921 [INFO ] TcpChannelFactory   :   60:
> > > Configuring Bootstrap with ModbusTcpConfiguration{requestTimeout=5000,
> > > unitIdentifier=1}
> > >
> > > and after my application finished
> > >
> > > 12:17:18,022 [INFO ] NettyChannelFactory :  150:
> > > Channel is closed, closing worker Group also
> > > 12:17:20,025 [INFO ] NettyChannelFactory :  154:
> > > Worker Group was closed successfully!
> > >
> > > and then it just waits...
> > >
> > > When using the debugger in IntelliJ I press pause and have a look at
> the
> > > threads it seems to me it is stuck in some kind of cleanup I do not
> > > understand.
> > > There is actually a thread called DestroyJavaVM so sounds like outside
> of
> > > my actual application.
> > >
> > > How do I fix this?
> > >
> > > --
> > > Best regards / Met vriendelijke groeten,
> > >
> > > Niels Basjes
> > >
> >
> >
> > --
> > Best regards / Met vriendelijke groeten,
> >
> > Niels Basjes
> >
>
>
> --
> Best regards / Met vriendelijke groeten,
>
> Niels Basjes
>

Re: [DRAFT] December Board Report

[Lukas Ott]

+1
seems to be accurate ;-)

Luk

Am Mi., 14. Dez. 2022 um 10:13 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Hi all,
>
> I just wrote our board report … hope I didn’t miss anything. Please
> provide feedback, If you have something:
>
> 
>
> ## Description:
> The mission of the Apache PLC4X project is creating a set of libraries for
> communicating with industrial programmable logic controllers (PLCs) using a
> variety of protocols but with a shared API.
>
> ## Issues:
> There are currently no issues requiring board attention.
>
> ## Membership Data:
> Apache PLC4X was founded 2019-04-17 (4 years ago)
> There are currently 21 committers and 13 PMC members in this project.
> The Committer-to-PMC ratio is roughly 3:2.
>
> Community changes, past quarter:
> - No new PMC members. Last addition was César García on 2021-10-01.
> - Jinlin Hong was added as committer on 2022-11-02
>
> ## Project Activity:
> We finished our work on some of the refactoring and streamlining of our
> APIs
> and are now sort of going back to a normal more of activity. Also are we
> seeing a broad set of initiatives currently being worked on:
> - Profinet Drivers
> - Major update of the ADS driver
> - The PLC4Rust and PLC4Py initiatives are continuing
> - We're doing some onboarding work for some of the new contributors that
>   showed up over the last few months.
>
> We did notice that our usage of JavaFX in one of our new tools (only
> contained in the 0.10.0 and still in Beta state there) is actually not ok
> since JavaFX was removed from the JDK itself. We'll be replacing this with
> a
> technology which is compatible with the ASF rules as soon as possible or
> we'll
> be removing it if there is no short-term solution for this problem.
>
> Recent releases:
> - 0.10.0 was released on 2022-10-06
> - 0.9.1 was released on 2021-12-17
>
> ## Community Health:
> Since we switched from Jira to GitHub Issues, we are seeing a significant
> uptake on activity coming in from new folks. The project is doing its best
> to
> encourage them to submit pull requests and mentoring them to be able to do
> so.
> At least 3 new contributors have shown up in the last few months.
>
> In parallel, we have started an initiative together with some friends from
> the
> IoTDB project, to do some initial kick-off work for building an open-source
> and Apache Historian solution, which would less be a tool or framework, but
> more a product intended for the automation industry. Hoping on some
> increased
> interest and activity based on that.
>
> So far, we're happy how the project is evolving, and we hope to be able
> to invite more people into comittership soon.
>
>
> 
>
>
> Will submit this in 2 or 3 days.
>
> Chris
>

Re: Building a PLC4X and IoTDB Historian?

[Lukas Ott]

+1 for that . Apache driven Historian would be quite awesome :-)

Am Sa., 26. Nov. 2022 um 16:36 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Hi all,
>
> I am currently thinking, if it wouldn’t be a good idea to build something
> like an open-source Historian based on PLC4X and IoTDB.
>
> For those of you, who don’t know what a Historian is. In the manufacturing
> industry they have these extremely expensive servers (usually you buy them
> as a bundle of hard- and software).
> These servers are nothing else than a really crappy and brutally expensive
> Database for storing Time-Series data.
>
> The thing is most commercial products are currently really having trouble
> to keep up with the increasing amount of Data being sent.
>
> So instead of suggesting building an Historian at each customer’s site, I
> thought: Perhaps a ready-to-use solution based on open-source would be a
> good idea.
> Not 100% sure where I’d locate such an initiative, but I would tend to see
> it more on the Database side.
>
> I think IoTDB would be the perfect storage system, all we seem to need is
> some sort of rest-interface that matches the industry standards for
> querying the information and on the other side something like PLC4X to fill
> the database.
>
> Here some examples:
>
> https://www.ge.com/digital/documentation/historian/version80/c_historian_apis_overview.html
> https://cdn.logic-control.com/docs/aveva/historian/HistorianRetrieval.pdf
>
> What do you folks think?
>
>
> Chris
>

Re: [DISCUSS] Check in generated Java code?

[Lukas Ott]

+1 as this simplifies for users

Am Fr., 25. Nov. 2022 um 11:27 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Hi all,
>
> I know it’s sort of considered bad practice to check in generated code,
> when you’re working with maven.
>
> However, we’ve already started to check-in generated code for all other
> languages.
> Especially today when working on the Time and Date stuff I really have
> learned to appreciate to see what changed, when working on code-generation.
>
> I would like to propose to also start checking in the generated java-code.
>
> But I would like to generate it into a separate directory and use the
> build-helper-plugin in order to keep things separate (This way we can
> simply delete the directory, run the build and we get rid of obsolete types)
>
> I would propose to generate code into a “src/main/generated” directory.
>
> The upside would be: Everyone can simply check out plc4x and use it in any
> IDE without having to build first.
>
> What do you folks think?
>
>
> Chris
>

Re: [DISCUSS] Make the PlcConnection return PlcFieldHandler and PlcValueHandler instances?

[Lukas Ott]

Nice job Sebastian and Christofer! Awesome work! :-)

Am Di., 22. Nov. 2022 um 19:48 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Hi all,
>
> So, thanks to Sebastian’s great work on the Go SPI, making the ADS driver
> use context aware TagHandlers and ValueHandlers, was super easy.
> And regarding my last email … I’ve simply provided two Constructors … one
> that takes a DriverContext and one that doesn’t. It the TagHandler doesn’t
> have the DriverContext, it just does a statical structural check and if
> it’s there if will add all of the cool stuff, we now have at our disposal.
>
> Chris
>
>
> From: Christofer Dutz 
> Date: Tuesday, 22. November 2022 at 19:10
> To: dev@plc4x.apache.org 
> Subject: Re: [DISCUSS] Make the PlcConnection return PlcFieldHandler and
> PlcValueHandler instances?
> Hi all,
>
> I just noticed a “CheckTagAddress” function in PLC4Go’s PlcDriver type.
> So if we provide address checking beyond the normal static checks, we
> can’t really check the dynamic stuff on the PlcDriver level.
>
> Chris
>
>
> From: Christofer Dutz 
> Date: Tuesday, 22. November 2022 at 16:44
> To: dev@plc4x.apache.org 
> Subject: [DISCUSS] Make the PlcConnection return PlcFieldHandler and
> PlcValueHandler instances?
> Hi all,
>
> till now we always created the PlcFieldHandler and PlcValueHandlers in the
> Driver code statically.
>
> Now with the updated ADS driver we have some completely new possibilities:
>
>   *   We can check if a tag exists before executing the query
>   *   We can check the type and structure of values we want to write
> before sending them to the PLC
>   *   We can start using some fancy array notation which we can validate
> the query before sending the request.
>
> The only problem I currently have, it that the FieldHandler and
> ValueHandler are both created detached from the Connection, where the
> information is present.
>
> So, I would like to change that the Connection is responsible of creating
> the PlcValueHandler and PlcValueHandler.
>
>
> With this we could even do crazy stuff like:
>
>   *   In S7 give an error warning if the type of S7 doesn’t support the
> datatype, that the user wanted to use?
>   *   Possibly rewrite fields, if we’re using an incompatible S7 type
> (Like if I’m on a S7-1200 and want to read a LINT, which the 1200 doesn’t
> support), then we could replace this with a 2-element array of DINT and
> still support datatypes the device itself doesn’t.
>   *   We could provide an error if someone wants to use the S7 driver
> subscription API with a PLC, that doesn’t support that.
>   *   … I probably could go on forever ;-)
>
>
> What do you folks think?
>
>
> Chris
>

Re: [PLC4PY] Required setup for building?

[Lukas Ott]

yes leave it at 3.7.

They are currently improving a lot - 3.10 was a major shift and 3.11 has
lot of neat improvements concerning error handling.
See also: Built-in Exceptions — Python 3.11.0 documentation
 and Python 3.11
Preview: Even Better Error Messages – Real Python


So yes when Plc4Py gets actually usable we can bump it to a stable 3.XX
version.




Am Fr., 11. Nov. 2022 um 12:08 Uhr schrieb Ben Hutcheson <
ben.hut...@gmail.com>:

> No, just leave the prerequisite check, 3.7 is still a reasonable starting
> point (Although by the time Plc4Py actually gets useable it probably won't
> be)
>
> On Fri, Nov 11, 2022 at 5:03 AM Christofer Dutz  >
> wrote:
>
> > Oh …
> >
> > if it’s just that, I can simply add that to the prerequisite check.
> > That currently checks, if python is at least 3.7.0, I can bump that to
> > 3.10.0 … however it seems that 3.9 is simpler to setup (As I didn’t
> > explicitly select a version and that one was installed). So if the
> benefit
> > of 3.10+ is not too big, perhaps make it work with 3.9.x.
> >
> > Chris
> >
> >
> > From: Ben Hutcheson 
> > Date: Friday, 11. November 2022 at 11:55
> > To: dev@plc4x.apache.org 
> > Subject: Re: [PLC4PY] Required setup for building?
> > Hi,
> >
> > Yeah it looks like we'll have to work on support for Python version <
> 3.10.
> > It should be an easy fix to use the Union operator for type hints instead
> > of the Pipe symbol.
> >
> > Ben
> >
> > On Fri, Nov 11, 2022 at 4:50 AM Christofer Dutz <
> christofer.d...@c-ware.de
> > >
> > wrote:
> >
> > > [INFO] --- exec-maven-plugin:3.1.0:exec (python-test) @ plc4py ---
> > > = test session starts
> > > ==
> > > platform darwin -- Python 3.9.12, pytest-7.2.0, pluggy-1.0.0 --
> > >
> >
> /Users/christoferdutz/Projects/Apache/PLC4X/plc4x/sandbox/plc4py/venv/bin/python3
> > > cachedir: .pytest_cache
> > > rootdir:
> > /Users/christoferdutz/Projects/Apache/PLC4X/plc4x/sandbox/plc4py,
> > > configfile: setup.cfg
> > > plugins: mock-3.10.0, asyncio-0.20.1
> > > asyncio: mode=auto
> > > collecting ... collected 16 items / 2 errors
> > >
> > >  ERRORS
> > > 
> > >  ERROR collecting tests/test_plc4py.py
> > > _
> > > tests/test_plc4py.py:28: in 
> > > from plc4py.drivers.modbus.ModbusConnection import ModbusConnection
> > > plc4py/drivers/modbus/ModbusConnection.py:30: in 
> > > from plc4py.drivers.modbus.ModbusProtocol import ModbusProtocol
> > > plc4py/drivers/modbus/ModbusProtocol.py:21: in 
> > > from plc4py.spi.Plc4xBaseProtocol import Plc4xBaseProtocol
> > > plc4py/spi/Plc4xBaseProtocol.py:25: in 
> > > class Plc4xBaseProtocol(Protocol):
> > > plc4py/spi/Plc4xBaseProtocol.py:35: in Plc4xBaseProtocol
> > > def connection_lost(self, exc: Exception | None) -> None:
> > > E   TypeError: unsupported operand type(s) for |: 'type' and 'NoneType'
> > > ___ ERROR collecting tests/unit/plc4py/spi/test_protocol.py
> > > 
> > > tests/unit/plc4py/spi/test_protocol.py:26: in 
> > > from plc4py.spi.Plc4xBaseProtocol import Plc4xBaseProtocol
> > > plc4py/spi/Plc4xBaseProtocol.py:25: in 
> > > class Plc4xBaseProtocol(Protocol):
> > > plc4py/spi/Plc4xBaseProtocol.py:35: in Plc4xBaseProtocol
> > > def connection_lost(self, exc: Exception | None) -> None:
> > > E   TypeError: unsupported operand type(s) for |: 'type' and 'NoneType'
> > > === short test summary info
> > > 
> > > ERROR tests/test_plc4py.py - TypeError: unsupported operand type(s) for
> > |:
> > > 't...
> > > ERROR tests/unit/plc4py/spi/test_protocol.py - TypeError: unsupported
> > > operand...
> > > !!! Interrupted: 2 errors during collection
> > > 
> > > == 2 errors in 0.08s
> > > ===
> > > [ERROR] Command execution failed.
> > > org.apache.commons.exec.ExecuteException: Process exited with an
> error: 2
> > > (Exit value: 2)
> > > at org.apache.commons.exec.DefaultExecutor.executeInternal
> > > (DefaultExecutor.java:404)
> > > at org.apache.commons.exec.DefaultExecutor.execute
> > > (DefaultExecutor.java:166)
> > > at org.codehaus.mojo.exec.ExecMojo.executeCommandLine
> > > (ExecMojo.java:1000)
> > > at org.codehaus.mojo.exec.ExecMojo.executeCommandLine
> > > (ExecMojo.java:947)
> > > at org.codehaus.mojo.exec.ExecMojo.execute (ExecMojo.java:471)
> > > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> > > (DefaultBuildPluginManager.java:137)
> > > at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > > (MojoExecutor.java:210)
> > > at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> > > (MojoExecutor.java:156)
> > > at 

Re: [DISCUSS] Enable GitHub issues?

[Lukas Ott]

Hi Dominik,

It was straight foward and easy to use. :-)

KR
Lukas

Am Mi., 9. Nov. 2022 um 11:36 Uhr schrieb Dominik Riemer :

> Hi Lukas,
>
> great work!
> Just out of interest, how was your experience when using the migration
> tool? Are there any pitfalls/things one should be aware of when configuring
> the migration?
>
> Cheers
> Dominik
>
> -----Original Message-
> From: Lukas Ott 
> Sent: Wednesday, November 9, 2022 11:33 AM
> To: dev@plc4x.apache.org
> Subject: Re: [DISCUSS] Enable GitHub issues?
>
> successfully migrated all 70 Jira Issues to Github Issues -> Unfortunately
> it seems i do not have the rights to close down our JIRA:
> "This can be done by turning off the create issue permission for all
> non-admins and adding an announcement in Portal Settings redirecting people
> to GitHub."
>
> Am Mi., 9. Nov. 2022 um 10:25 Uhr schrieb Lukas Ott :
>
> > Updated:
> > - Driver-Profinet -> Profinet
> > - Driver-ADS -> ADS
> > - API -> API
> > - Driver-S7 -> S7
> > - Core -> ???
> > - Util-Pool -> ???
> > - newbie -> good first issue
> > - Code-Generation
> > - Driver-Modbus -> Modbus
> > - Integration-NiFi
> > - feature-request -> new feature
> > - Driver-OPC-UA -> OPC-UA
> > - documentation -> documentation
> > - Scraper -> ???
> > - Driver-Fatek -> Fatek
> > - Testing -> test
> > - Integration-Camel -> we have donated this to Apache Camel
> > - Driver-Ethernet/IP -> Ethernet/IP
> > - beginnerv -> good first issue
> > - feature -> new feature
> > - low-hanging-fruit -> good first issue
> > - easy-fix -> good first issue
> > - PLC4C -> c
> > - documentation-update -> documentation
> > - docker -> ???
> > - Integration-Kafka-Connect
> > - examples -> ??
> > - Build -> release
> > - Driver-CANopen -> CANopen
> > - PLC4J - > java
> >
> > On 2022/11/04 09:55:44 jl hong wrote:
> > > Hello Lukas,
> > >
> > >- Driver-Profinet
> > >- Driver-ADS
> > >- API
> > >- Driver-S7
> > >- Core
> > >- Util-Pool
> > >- newbie
> > >- Code-Generation
> > >- Driver-Modbus
> > >- Integration-NiFi
> > >- feature-request
> > >- Driver-OPC-UA
> > >- documentation
> > >- Scraper
> > >- Driver-Fatek
> > >- Testing
> > >- Integration-Camel
> > >- Driver-Ethernet/IP
> > >- beginner
> > >- feature
> > >- low-hanging-fruit
> > >- easy-fix
> > >- PLC4C
> > >- documentation-update
> > >- docker
> > >- Integration-Kafka-Connect
> > >- examples
> > >- Build
> > >- Driver-CANopen
> > >- PLC4J
> > >
> > > The list which I got by jira-to-issues is current labels in our Jira.
> > > Some of them are not on your list, such as "driver".
> > >
> > > Lukas Ott  於 2022年11月1日 週二 凌晨3:25寫道：
> > >
> > > > I started cleaning up the Issues on JIRA.
> > > > Current status is 84 Issues.
> > > >
> > > > On Github I added a few labels.
> > > > Current list of labels (17):
> > > >
> > > >- test
> > > >- task
> > > >- wish
> > > >- new feature
> > > >- bug
> > > >- dependencies
> > > >- duplicate
> > > >- enhancement
> > > >- go
> > > >- good first issue
> > > >- help wanted
> > > >- invalid
> > > >- java
> > > >- python
> > > >- question
> > > >- wontfix
> > > >- github_actions
> > > >
> > > > Open tasks:
> > > > - Turn off new Jiras
> > > > This can be done by turning off the create issue permission for
> > > > all non-admins and adding an announcement in Portal Settings
> > > > redirecting
> > people
> > > > to GitHub.
> > > > - Migrating Existing Issues
> > > > - Create / Add Issue Template
> > > >
> > > > Am Mo., 31. Okt. 2022 um 19:26 Uhr schrieb Ben Hutcheson <
> > > > ben.hut...@gmail.com>:
> > > >
> > > > > +1
> > > > >
> > > > > This will make the issues more visible, which i

Re: [DISCUSS] Enable GitHub issues?

[Lukas Ott]

successfully migrated all 70 Jira Issues to Github Issues -> Unfortunately
it seems i do not have the rights to close down our JIRA:
"This can be done by turning off the create issue permission for all
non-admins and adding an announcement in Portal Settings redirecting people
to GitHub."

Am Mi., 9. Nov. 2022 um 10:25 Uhr schrieb Lukas Ott :

> Updated:
> - Driver-Profinet -> Profinet
> - Driver-ADS -> ADS
> - API -> API
> - Driver-S7 -> S7
> - Core -> ???
> - Util-Pool -> ???
> - newbie -> good first issue
> - Code-Generation
> - Driver-Modbus -> Modbus
> - Integration-NiFi
> - feature-request -> new feature
> - Driver-OPC-UA -> OPC-UA
> - documentation -> documentation
> - Scraper -> ???
> - Driver-Fatek -> Fatek
> - Testing -> test
> - Integration-Camel -> we have donated this to Apache Camel
> - Driver-Ethernet/IP -> Ethernet/IP
> - beginnerv -> good first issue
> - feature -> new feature
> - low-hanging-fruit -> good first issue
> - easy-fix -> good first issue
> - PLC4C -> c
> - documentation-update -> documentation
> - docker -> ???
> - Integration-Kafka-Connect
> - examples -> ??
> - Build -> release
> - Driver-CANopen -> CANopen
> - PLC4J - > java
>
> On 2022/11/04 09:55:44 jl hong wrote:
> > Hello Lukas,
> >
> >- Driver-Profinet
> >- Driver-ADS
> >- API
> >- Driver-S7
> >- Core
> >- Util-Pool
> >- newbie
> >- Code-Generation
> >- Driver-Modbus
> >- Integration-NiFi
> >- feature-request
> >- Driver-OPC-UA
> >- documentation
> >- Scraper
> >- Driver-Fatek
> >- Testing
> >- Integration-Camel
> >- Driver-Ethernet/IP
> >- beginner
> >- feature
> >- low-hanging-fruit
> >- easy-fix
> >- PLC4C
> >- documentation-update
> >- docker
> >- Integration-Kafka-Connect
> >- examples
> >- Build
> >- Driver-CANopen
> >- PLC4J
> >
> > The list which I got by jira-to-issues is current labels in our Jira.
> > Some of them are not on your list, such as "driver".
> >
> > Lukas Ott  於 2022年11月1日 週二 凌晨3:25寫道：
> >
> > > I started cleaning up the Issues on JIRA.
> > > Current status is 84 Issues.
> > >
> > > On Github I added a few labels.
> > > Current list of labels (17):
> > >
> > >- test
> > >- task
> > >- wish
> > >- new feature
> > >- bug
> > >- dependencies
> > >- duplicate
> > >- enhancement
> > >- go
> > >- good first issue
> > >- help wanted
> > >- invalid
> > >- java
> > >- python
> > >    - question
> > >- wontfix
> > >- github_actions
> > >
> > > Open tasks:
> > > - Turn off new Jiras
> > > This can be done by turning off the create issue permission for all
> > > non-admins and adding an announcement in Portal Settings redirecting
> people
> > > to GitHub.
> > > - Migrating Existing Issues
> > > - Create / Add Issue Template
> > >
> > > Am Mo., 31. Okt. 2022 um 19:26 Uhr schrieb Ben Hutcheson <
> > > ben.hut...@gmail.com>:
> > >
> > > > +1
> > > >
> > > > This will make the issues more visible, which is probably a good
> thing.
> > > >
> > > > On Mon, 31 Oct 2022 at 12:06 pm, Lukas Ott 
> > > wrote:
> > > >
> > > > > Thank you Dominik! This
> > > > >
> > > > > It seems we have less of the Cons they are mentioning :-)
> > > > > -> Google Summer of Code was not yet part of PLC4X
> > > > > -> We only need to migrate around 100 Jira issues
> > > > > -> I am not aware of any Milestones in our project that we track in
> > > Jira.
> > > > >
> > > > > Concerning preparation:
> > > > > - We already have list of labels
> > > > > List to be added:
> > > > >
> > > > > Category
> > > > >
> > > > > Values
> > > > >
> > > > > Priority
> > > > >
> > > > > "P0", "P1", "P2", "P3"
> > > > >
> > > > > Type
> > > > >
> > > > >

Re: [DISCUSS] Enable GitHub issues?

[Lukas Ott]

Updated:
- Driver-Profinet -> Profinet
- Driver-ADS -> ADS
- API -> API
- Driver-S7 -> S7
- Core -> ???
- Util-Pool -> ???
- newbie -> good first issue
- Code-Generation
- Driver-Modbus -> Modbus
- Integration-NiFi
- feature-request -> new feature
- Driver-OPC-UA -> OPC-UA
- documentation -> documentation
- Scraper -> ???
- Driver-Fatek -> Fatek
- Testing -> test
- Integration-Camel -> we have donated this to Apache Camel
- Driver-Ethernet/IP -> Ethernet/IP
- beginnerv -> good first issue
- feature -> new feature
- low-hanging-fruit -> good first issue
- easy-fix -> good first issue
- PLC4C -> c
- documentation-update -> documentation
- docker -> ??? 
- Integration-Kafka-Connect
- examples -> ??
- Build -> release
- Driver-CANopen -> CANopen
- PLC4J - > java

On 2022/11/04 09:55:44 jl hong wrote:
> Hello Lukas,
> 
>- Driver-Profinet
>- Driver-ADS
>- API
>- Driver-S7
>- Core
>- Util-Pool
>- newbie
>- Code-Generation
>- Driver-Modbus
>- Integration-NiFi
>- feature-request
>- Driver-OPC-UA
>- documentation
>- Scraper
>- Driver-Fatek
>- Testing
>- Integration-Camel
>- Driver-Ethernet/IP
>- beginner
>- feature
>- low-hanging-fruit
>- easy-fix
>- PLC4C
>- documentation-update
>- docker
>- Integration-Kafka-Connect
>- examples
>- Build
>    - Driver-CANopen
>- PLC4J
> 
> The list which I got by jira-to-issues is current labels in our Jira.
> Some of them are not on your list, such as "driver".
> 
> Lukas Ott  於 2022年11月1日 週二 凌晨3:25寫道：
> 
> > I started cleaning up the Issues on JIRA.
> > Current status is 84 Issues.
> >
> > On Github I added a few labels.
> > Current list of labels (17):
> >
> >- test
> >- task
> >- wish
> >- new feature
> >- bug
> >- dependencies
> >- duplicate
> >- enhancement
> >- go
> >- good first issue
> >- help wanted
> >- invalid
> >- java
> >- python
> >- question
> >- wontfix
> >- github_actions
> >
> > Open tasks:
> > - Turn off new Jiras
> > This can be done by turning off the create issue permission for all
> > non-admins and adding an announcement in Portal Settings redirecting people
> > to GitHub.
> > - Migrating Existing Issues
> > - Create / Add Issue Template
> >
> > Am Mo., 31. Okt. 2022 um 19:26 Uhr schrieb Ben Hutcheson <
> > ben.hut...@gmail.com>:
> >
> > > +1
> > >
> > > This will make the issues more visible, which is probably a good thing.
> > >
> > > On Mon, 31 Oct 2022 at 12:06 pm, Lukas Ott 
> > wrote:
> > >
> > > > Thank you Dominik! This
> > > >
> > > > It seems we have less of the Cons they are mentioning :-)
> > > > -> Google Summer of Code was not yet part of PLC4X
> > > > -> We only need to migrate around 100 Jira issues
> > > > -> I am not aware of any Milestones in our project that we track in
> > Jira.
> > > >
> > > > Concerning preparation:
> > > > - We already have list of labels
> > > > List to be added:
> > > >
> > > > Category
> > > >
> > > > Values
> > > >
> > > > Priority
> > > >
> > > > "P0", "P1", "P2", "P3"
> > > >
> > > > Type
> > > >
> > > > "Bug", "Improvement", "New Feature", "Task", "Test", "Wish", "Outage"
> > > >
> > > > Component
> > > >
> > > > One label per JIRA component, formatted "Component: "
> > > (e.g.
> > > > "Component: sdk-go")
> > > >
> > > > Status
> > > >
> > > > "Awaiting Triage", "Fixed", "Not a problem", "Duplicate"
> > > >
> > > >
> > > > - Yes we should add a issue template
> > > > This can be done by turning off the create issue permission for all
> > > > non-admins and adding an announcement in Portal Settings redirecting
> > > people
> > > > to GitHub.
> > > > - Update documentation after migration
> > > >
> > > > Next steps
> > > > - Turn on Github Issues Tab
> >

Re: [DISCUSS] Rename Fields -> Tags?

[Lukas Ott]

+1 for "tag" as naming convention

Christofer Dutz  schrieb am So., 6. Nov. 2022,
13:33:

> Hi Lukasz,
>
> even in protocols like ADS and EIP at Rivian everyone is referring to any
> data point as a “Tag”.
> So far, I haven’t come across a single person saying something else on
> LinkedIn.
> https://www.linkedin.com/feed/update/urn:li:activity:6994584721582088192
>
> And keep in mind: PLC4X is meant to be the bridge between IT and OT, and
> we chose a lot of stuff (Like the address patterns, etc.) to match the OT
> expectations. After all, I will most probably be an IT person asking the OT
> person: Please give me the address for Field/Tag XYZ. So, I think naming it
> “Tag” would be better.
>
> I would like to name it to match the most used term: I know that this
> isn’t always a perfect match in all protocols, but I guess that’s the
> difference between providing a “shared API” or building individual drivers
> for each protocol.
>
> And currently we name it “Query” in Go … so you currently say: “AddQuery”
> instead of “AddField”.
>
> Chris
>
>
> From: Łukasz Dywicki 
> Date: Sunday, 6. November 2022 at 11:45
> To: dev@plc4x.apache.org , Christofer Dutz <
> christofer.d...@c-ware.de>
> Subject: Re: [DISCUSS] Rename Fields -> Tags?
> Hey Chris,
> I am not certain if "tag" is standardized or not. Earlier, knowing only
> modbus registers and bacnet objects, I been confused multiple times what
> the tag is. For regular IT tag is rather a marker placed on something to
> categorize elements. Our field currently specifies rather a unique data
> point than a tag.
> If tag meaning comes from IEC standard then I'd opt in for a change. If
> its not standardized then I'd advice staying with a field. Our use is
> mixed IT/OT (with probably still more IT?), if we stick too much to
> automation industry terminology then we will need to bake definition of
> a tag, fight situations where we miss a "common understanding" cause we
> can't beg others for unification of their meaning.
>
> I've seen tag used in context of ethernet/ip (more precisely Rockwell
> PLCs), but haven't done a research of why. Keep in mind we have also
> object oriented protocols such as BACnet (with `device.object.property`)
> and CANopen (with `device.sdo` or `device.tpdo..`) thus in their context
> tag is far less meaningful than field.
>
> Cheers,
> Łukasz
>
> On 5.11.2022 12:23, Christofer Dutz wrote:
> > Hi all,
> >
> > I’m currently working on harmonizing our different API variants a bit
> and hopefully finalizing our Browse API (Which sort of wen’t through
> multiple levels of change between Java and Go, back to Java and now back to
> Go.
> >
> > One thing I learned at Rivian is, that everyone seems to be talking
> about “Tags” on PLCs. So I asked on LinkedIn and it seems pretty obvious
> that “Tag” seems to be the term mostly used in the automation industry.
> >
> > So, I would like to consequently rename “Field” to “Tag”.
> >
> > What do you folks think?
> >
> > Chris
> >
>

Re: Configuring and using plc4x

[Lukas Ott]

Hello Mihai,

First of all welcome to the mailing list. :-)

I hope that you managed to subscribe.

Did you have a look here:
https://plc4x.apache.org/users/blogs-videos-and-slides.html ?
https://youtu.be/SNFKqrLMIZI this hands on should give you a good starting
point on how to get started with our Java Driver talking to S7.

If you have further questions. Please let us know.

The best way is to also have some code running. So that you can show us
where you got stuck.

Helps us improve documentation and hopefully help you further. :-)

Kind regards
otluk

Am Sa., 5. Nov. 2022 um 12:15 Uhr schrieb Mihai Demian <
mihai.dem...@easyea.ro>:

> Hello,
> My name is Mihai Demian, I am from Romania and I own an automation firm
> (with no
> activity yet, unfortunately).
> Looking for ways to make a plc communicate with a pc, I came across plc4x.
> I have an old laptop at home, running as a small home server (the best I
> could, I am very
> new to Linux world), and I downloaded and installed (with ./mvnw install).
> It took me a
> while, the distribution had some bugs in it with missing licences in
> header ( >) and then some wrong references, but I cannot remember the files. I
> managed to correct
> the issues and install it.
> I also have 2 plcs Siemens S7-1200 connected on the same network as the
> server.  From
> my understanding of OPC Server, the server takes care about the
> communication with the
> plc and the client (user's computer) connects to the server and reads and
> writes data
> from/to the plc. At my current employer, OPC Server and a custom app
> developed in-house
> is the default way of doing things.
> Can you help me figuring out how to make them "talk" to each other? I want
> to be able to
> offer this option to companies.
>
> Thank you very much.
> --
> Cu stima, / Best regards,
> Mihai Demian
> Administrator & PLC Programmer
> Easy Engineering and Automation SRL[1]
>
> 
> [1] https://easyea.ro
>

Re: [DISCUSS] Enable GitHub issues?

[Lukas Ott]

Feel free to add them as labels on our Github :-)

Am Fr., 4. Nov. 2022 um 10:56 Uhr schrieb jl hong :

> Hello Lukas,
>
>- Driver-Profinet
>- Driver-ADS
>- API
>- Driver-S7
>- Core
>- Util-Pool
>- newbie
>- Code-Generation
>- Driver-Modbus
>- Integration-NiFi
>- feature-request
>- Driver-OPC-UA
>- documentation
>- Scraper
>- Driver-Fatek
>- Testing
>- Integration-Camel
>- Driver-Ethernet/IP
>- beginner
>- feature
>- low-hanging-fruit
>- easy-fix
>- PLC4C
>- documentation-update
>- docker
>- Integration-Kafka-Connect
>- examples
>- Build
>- Driver-CANopen
>- PLC4J
>
> The list which I got by jira-to-issues is current labels in our Jira.
> Some of them are not on your list, such as "driver".
>
> Lukas Ott  於 2022年11月1日 週二 凌晨3:25寫道：
>
> > I started cleaning up the Issues on JIRA.
> > Current status is 84 Issues.
> >
> > On Github I added a few labels.
> > Current list of labels (17):
> >
> >- test
> >- task
> >- wish
> >- new feature
> >- bug
> >- dependencies
> >- duplicate
> >- enhancement
> >- go
> >- good first issue
> >- help wanted
> >- invalid
> >- java
> >- python
> >- question
> >- wontfix
> >- github_actions
> >
> > Open tasks:
> > - Turn off new Jiras
> > This can be done by turning off the create issue permission for all
> > non-admins and adding an announcement in Portal Settings redirecting
> people
> > to GitHub.
> > - Migrating Existing Issues
> > - Create / Add Issue Template
> >
> > Am Mo., 31. Okt. 2022 um 19:26 Uhr schrieb Ben Hutcheson <
> > ben.hut...@gmail.com>:
> >
> > > +1
> > >
> > > This will make the issues more visible, which is probably a good thing.
> > >
> > > On Mon, 31 Oct 2022 at 12:06 pm, Lukas Ott 
> > wrote:
> > >
> > > > Thank you Dominik! This
> > > >
> > > > It seems we have less of the Cons they are mentioning :-)
> > > > -> Google Summer of Code was not yet part of PLC4X
> > > > -> We only need to migrate around 100 Jira issues
> > > > -> I am not aware of any Milestones in our project that we track in
> > Jira.
> > > >
> > > > Concerning preparation:
> > > > - We already have list of labels
> > > > List to be added:
> > > >
> > > > Category
> > > >
> > > > Values
> > > >
> > > > Priority
> > > >
> > > > "P0", "P1", "P2", "P3"
> > > >
> > > > Type
> > > >
> > > > "Bug", "Improvement", "New Feature", "Task", "Test", "Wish", "Outage"
> > > >
> > > > Component
> > > >
> > > > One label per JIRA component, formatted "Component: "
> > > (e.g.
> > > > "Component: sdk-go")
> > > >
> > > > Status
> > > >
> > > > "Awaiting Triage", "Fixed", "Not a problem", "Duplicate"
> > > >
> > > >
> > > > - Yes we should add a issue template
> > > > This can be done by turning off the create issue permission for all
> > > > non-admins and adding an announcement in Portal Settings redirecting
> > > people
> > > > to GitHub.
> > > > - Update documentation after migration
> > > >
> > > > Next steps
> > > > - Turn on Github Issues Tab
> > > > - Turn off Jira Tickets (How do we do that?)
> > > >
> > > >
> > > >
> > > >
> > > > Am Mo., 31. Okt. 2022 um 18:48 Uhr schrieb Dominik Riemer <
> > rie...@fzi.de
> > > >:
> > > >
> > > > > I've recently looked at other ASF projects which discussed
> migration
> > > from
> > > > > Jira to Github, e.g., here are some discussions from Apache Beam:
> > > > >
> > > > > Feature Comparison:
> > > > >
> > > >
> > >
> >
> https://docs.google.com/document/d/1_n7gboVbSKPs-CVcHzADgg8qpNL9igiHqUPCmiOslf0/edit#heading=h.r8qwrrbs8odn
> > > > > Migration Plan:
> > 

Re: [DISCUSS] Enable GitHub issues?

[Lukas Ott]

I started cleaning up the Issues on JIRA.
Current status is 84 Issues.

On Github I added a few labels.
Current list of labels (17):

   - test
   - task
   - wish
   - new feature
   - bug
   - dependencies
   - duplicate
   - enhancement
   - go
   - good first issue
   - help wanted
   - invalid
   - java
   - python
   - question
   - wontfix
   - github_actions

Open tasks:
- Turn off new Jiras
This can be done by turning off the create issue permission for all
non-admins and adding an announcement in Portal Settings redirecting people
to GitHub.
- Migrating Existing Issues
- Create / Add Issue Template

Am Mo., 31. Okt. 2022 um 19:26 Uhr schrieb Ben Hutcheson <
ben.hut...@gmail.com>:

> +1
>
> This will make the issues more visible, which is probably a good thing.
>
> On Mon, 31 Oct 2022 at 12:06 pm, Lukas Ott  wrote:
>
> > Thank you Dominik! This
> >
> > It seems we have less of the Cons they are mentioning :-)
> > -> Google Summer of Code was not yet part of PLC4X
> > -> We only need to migrate around 100 Jira issues
> > -> I am not aware of any Milestones in our project that we track in Jira.
> >
> > Concerning preparation:
> > - We already have list of labels
> > List to be added:
> >
> > Category
> >
> > Values
> >
> > Priority
> >
> > "P0", "P1", "P2", "P3"
> >
> > Type
> >
> > "Bug", "Improvement", "New Feature", "Task", "Test", "Wish", "Outage"
> >
> > Component
> >
> > One label per JIRA component, formatted "Component: "
> (e.g.
> > "Component: sdk-go")
> >
> > Status
> >
> > "Awaiting Triage", "Fixed", "Not a problem", "Duplicate"
> >
> >
> > - Yes we should add a issue template
> > This can be done by turning off the create issue permission for all
> > non-admins and adding an announcement in Portal Settings redirecting
> people
> > to GitHub.
> > - Update documentation after migration
> >
> > Next steps
> > - Turn on Github Issues Tab
> > - Turn off Jira Tickets (How do we do that?)
> >
> >
> >
> >
> > Am Mo., 31. Okt. 2022 um 18:48 Uhr schrieb Dominik Riemer  >:
> >
> > > I've recently looked at other ASF projects which discussed migration
> from
> > > Jira to Github, e.g., here are some discussions from Apache Beam:
> > >
> > > Feature Comparison:
> > >
> >
> https://docs.google.com/document/d/1_n7gboVbSKPs-CVcHzADgg8qpNL9igiHqUPCmiOslf0/edit#heading=h.r8qwrrbs8odn
> > > Migration Plan:
> > >
> >
> https://docs.google.com/document/d/1powrXGbjMLMYl9ibRzMda5o5HM_p44XvBy5MZu75Q5E/edit#heading=h.wskna8eurvjv
> > >
> > > And Beam also open-sourced the migration tool they used:
> > > https://github.com/google/jira-to-issues
> > >
> > > I've not yet tried it, but looks quite good 
> > >
> > > Cheers
> > > Dominik
> > >
> > >
> > > -Original Message-
> > > From: Lukas Ott 
> > > Sent: Monday, October 31, 2022 6:41 PM
> > > To: dev@plc4x.apache.org
> > > Subject: Re: [DISCUSS] Enable GitHub issues?
> > >
> > > I will look into that.
> > >
> > > Currently we have 103 open jira issues. Oldest one is more than 2 years
> > > ago.
> > >
> > >
> > >
> > > Am Mo., 31. Okt. 2022 um 18:28 Uhr schrieb Christofer Dutz <
> > > christofer.d...@c-ware.de>:
> > >
> > > > I’m also fine with that.
> > > > So anyone willing to work on the migration?
> > > >
> > > > Chris
> > > >
> > > > From: Lukas Ott 
> > > > Date: Monday, 31. October 2022 at 17:50
> > > > To: dev@plc4x.apache.org 
> > > > Subject: Re: [DISCUSS] Enable GitHub issues?
> > > > Hi Chris,
> > > >
> > > > In my humble opinion we should not run parallel.
> > > >
> > > > Our Jira has already a lot of issues that are outdated.
> > > >
> > > > So i opt for enabling GitHub Issues and migrating the few Jira Issues
> > > > that are still worked on.
> > > >
> > > > This helps us also for cleaning up and having one public issue
> > > > tracker, where everyone can easily see what is worked on and what is
> > > open.
> > > >
> > > > Luk
> > > >
> > > > Am Mo., 31. Okt. 2022 um 17:07 Uhr schrieb Christofer Dutz <
> > > > christofer.d...@c-ware.de>:
> > > >
> > > > > Hi all,
> > > > >
> > > > > for those of you that haven’t heard of it, Apache will be disabling
> > > > signup
> > > > > to Apache’s Jira due to excessive Spam problems.
> > > > > So, for people outside of the project, wanting to submit issues,
> > > > > there will be no simple way to do so.
> > > > >
> > > > > How about we turn on GitHub Issues and simply run both in parallel.
> > > > >
> > > > > Chris
> > > > >
> > > >
> > >
> >
>

Re: [DISCUSS] Enable GitHub issues?

[Lukas Ott]

Thank you Dominik! This

It seems we have less of the Cons they are mentioning :-)
-> Google Summer of Code was not yet part of PLC4X
-> We only need to migrate around 100 Jira issues
-> I am not aware of any Milestones in our project that we track in Jira.

Concerning preparation:
- We already have list of labels
List to be added:

Category

Values

Priority

"P0", "P1", "P2", "P3"

Type

"Bug", "Improvement", "New Feature", "Task", "Test", "Wish", "Outage"

Component

One label per JIRA component, formatted "Component: " (e.g.
"Component: sdk-go")

Status

"Awaiting Triage", "Fixed", "Not a problem", "Duplicate"


- Yes we should add a issue template
This can be done by turning off the create issue permission for all
non-admins and adding an announcement in Portal Settings redirecting people
to GitHub.
- Update documentation after migration

Next steps
- Turn on Github Issues Tab
- Turn off Jira Tickets (How do we do that?)




Am Mo., 31. Okt. 2022 um 18:48 Uhr schrieb Dominik Riemer :

> I've recently looked at other ASF projects which discussed migration from
> Jira to Github, e.g., here are some discussions from Apache Beam:
>
> Feature Comparison:
> https://docs.google.com/document/d/1_n7gboVbSKPs-CVcHzADgg8qpNL9igiHqUPCmiOslf0/edit#heading=h.r8qwrrbs8odn
> Migration Plan:
> https://docs.google.com/document/d/1powrXGbjMLMYl9ibRzMda5o5HM_p44XvBy5MZu75Q5E/edit#heading=h.wskna8eurvjv
>
> And Beam also open-sourced the migration tool they used:
> https://github.com/google/jira-to-issues
>
> I've not yet tried it, but looks quite good 
>
> Cheers
> Dominik
>
>
> -Original Message-
> From: Lukas Ott 
> Sent: Monday, October 31, 2022 6:41 PM
> To: dev@plc4x.apache.org
> Subject: Re: [DISCUSS] Enable GitHub issues?
>
> I will look into that.
>
> Currently we have 103 open jira issues. Oldest one is more than 2 years
> ago.
>
>
>
> Am Mo., 31. Okt. 2022 um 18:28 Uhr schrieb Christofer Dutz <
> christofer.d...@c-ware.de>:
>
> > I’m also fine with that.
> > So anyone willing to work on the migration?
> >
> > Chris
> >
> > From: Lukas Ott 
> > Date: Monday, 31. October 2022 at 17:50
> > To: dev@plc4x.apache.org 
> > Subject: Re: [DISCUSS] Enable GitHub issues?
> > Hi Chris,
> >
> > In my humble opinion we should not run parallel.
> >
> > Our Jira has already a lot of issues that are outdated.
> >
> > So i opt for enabling GitHub Issues and migrating the few Jira Issues
> > that are still worked on.
> >
> > This helps us also for cleaning up and having one public issue
> > tracker, where everyone can easily see what is worked on and what is
> open.
> >
> > Luk
> >
> > Am Mo., 31. Okt. 2022 um 17:07 Uhr schrieb Christofer Dutz <
> > christofer.d...@c-ware.de>:
> >
> > > Hi all,
> > >
> > > for those of you that haven’t heard of it, Apache will be disabling
> > signup
> > > to Apache’s Jira due to excessive Spam problems.
> > > So, for people outside of the project, wanting to submit issues,
> > > there will be no simple way to do so.
> > >
> > > How about we turn on GitHub Issues and simply run both in parallel.
> > >
> > > Chris
> > >
> >
>

Re: [DISCUSS] Enable GitHub issues?

[Lukas Ott]

I will look into that.

Currently we have 103 open jira issues. Oldest one is more than 2 years ago.



Am Mo., 31. Okt. 2022 um 18:28 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> I’m also fine with that.
> So anyone willing to work on the migration?
>
> Chris
>
> From: Lukas Ott 
> Date: Monday, 31. October 2022 at 17:50
> To: dev@plc4x.apache.org 
> Subject: Re: [DISCUSS] Enable GitHub issues?
> Hi Chris,
>
> In my humble opinion we should not run parallel.
>
> Our Jira has already a lot of issues that are outdated.
>
> So i opt for enabling GitHub Issues and migrating the few Jira Issues that
> are still worked on.
>
> This helps us also for cleaning up and having one public issue tracker,
> where everyone can easily see what is worked on and what is open.
>
> Luk
>
> Am Mo., 31. Okt. 2022 um 17:07 Uhr schrieb Christofer Dutz <
> christofer.d...@c-ware.de>:
>
> > Hi all,
> >
> > for those of you that haven’t heard of it, Apache will be disabling
> signup
> > to Apache’s Jira due to excessive Spam problems.
> > So, for people outside of the project, wanting to submit issues, there
> > will be no simple way to do so.
> >
> > How about we turn on GitHub Issues and simply run both in parallel.
> >
> > Chris
> >
>

Re: [DISCUSS] Enable GitHub issues?

[Lukas Ott]

Hi Chris,

In my humble opinion we should not run parallel.

Our Jira has already a lot of issues that are outdated.

So i opt for enabling GitHub Issues and migrating the few Jira Issues that
are still worked on.

This helps us also for cleaning up and having one public issue tracker,
where everyone can easily see what is worked on and what is open.

Luk

Am Mo., 31. Okt. 2022 um 17:07 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Hi all,
>
> for those of you that haven’t heard of it, Apache will be disabling signup
> to Apache’s Jira due to excessive Spam problems.
> So, for people outside of the project, wanting to submit issues, there
> will be no simple way to do so.
>
> How about we turn on GitHub Issues and simply run both in parallel.
>
> Chris
>

Re: Change the array-notation in fields?

[Lukas Ott]

The question for me is why not startIndex = 0
Instead of 1.

In general this proposal sound reasonable to me and a I opt +1.
Luk

Am Sa., 29. Okt. 2022 um 17:30 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Hi all
>
> currently in most drivers we support an array notation like:
> XYZ{numElements}]
> In order to support reading arrays.
>
> Now in order to support reading partial arrays, I think it would be good
> to generally change that to:
>
> XYZ[{startIndex}..{endIndex}]
>
> And the ordinary version:
>
> XYZ[{endIndex}]
>
> This would imply starting at the first element.
> However, we should probably start with index “1”, as this seems to be what
> most seem to use.
>
> So:
> XYZ
> Would be the same as:
> XYZ[1]
> Would be the same as:
> XYZ[1..1]
>
> What do you think?
>
> Chris
>

Re: [VOTE] Move the Apache PLC4X Camel adapter to the Apache Camel project

[Lukas Ott]

+1

Am Di., 18. Okt. 2022 um 18:52 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> As discussed before:
>
> I would like to transfer the Apache PLC4X Camel adapter from Apache PLC4X
> into the Apache Camel project.
> I have discussed this with the Apache Camel folks and they would be happy
> to add it.
>
> So, I guess it’s time to make this official on our side.
>
> So please vote.
>
> Chris
>

Re: [DISCUSS] Donate/Move the Apache Camel integration to the Apache Camel project?

[Lukas Ott]

+1

Am Mi., 12. Okt. 2022 um 20:22 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Hi all,
>
> I know we‘ve discussed this on several occasions and as far as I remember
> there never really were any objections. But I’d like to do this one
> (hopefully) last time.
>
> So I had a chat with the Camel folks at ApacheCon and I would like to
> initiate moving our Camel Integration to the Apache Camel project.
>
> The advantages would be:
>
>   *   People that actually know Camel would help keep it in sync with
> future API changes
>   *   The probably biggest advantage would be that the PLC4X would show up
> in their “Marketplace” and be usable out of the box with Apache Camel
> Karavan
>
> I started the discussion on the Camel list, and it seems they’d be happy
> to accept the component.
>
>
> What do you folks think?
>
> Chris
>
>

Re: [VOTE] Apache PLC4X 0.10.0 RC2

[Lukas Ott]

+1 (binding)

Lukas

[x] Download all staged artifacts under the url specified in the
release vote email.
[x] Verify the signature is correct.
[x] Check if the signature references an Apache email address.
[x] Verify the SHA512 hashes.
[x] Unzip the archive.
[x] Verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES
files in the extracted source bundle.
[x] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files
in the extracted source bundle.
[x] [RM] Verify the staged source README, RELEASE_NOTE files
correspond to those in the extracted source bundle.
[x] [RM] Run RAT externally to ensure there are no surprises.
[x] Search for SNAPSHOT references
[x] Search for Copyright references, and if they are in headers, make
sure these files containing them are mentioned in the LICENSE file.
[x] Build the project according to the information in the README.md file.
[x] [RM] Build the project with ./mvnw install

java --version
openjdk 11.0.16 2022-07-19
OpenJDK Runtime Environment (build 11.0.16+8-post-Ubuntu-0ubuntu122.04)
OpenJDK 64-Bit Server VM (build 11.0.16+8-post-Ubuntu-0ubuntu122.04,
mixed mode, sharing)

Distributor ID: Linuxmint
Description:Linux Mint 21
Release:21
Codename:   vanessa


Am Mo., 3. Okt. 2022 um 18:46 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Argh … sorry for the noise … currently running the IoT track in parallel …
> use https://dist.apache.org/repos/dist/dev/plc4x/0.10.0/rc2/
>
> (It should end on RC2)
>
> Chris
>
> From: Christofer Dutz 
> Date: Monday, 3. October 2022 at 11:42
> To: dev@plc4x.apache.org 
> Subject: Re: [VOTE] Apache PLC4X 0.10.0 RC2
> Please use https://dist.apache.org/repos/dist/dev/plc4x/0.10.0/rc1
> instead … forgot to update that link in the vote email
>
>
>
> From: Christofer Dutz 
> Date: Monday, 3. October 2022 at 11:15
> To: dev@plc4x.apache.org 
> Subject: [VOTE] Apache PLC4X 0.10.0 RC2
> Apache PLC4X 0.10.0 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: v0.10.0
> Hash for the release tag: cac8254518540d6353546fcf7619203e2f64e721
>
> 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-1046
> [2] https://dist.apache.org/repos/dist/dev/plc4x/0.10.0/rc1
> [3] https://www.apache.org/dev/release.html#approving-a-release
> [4]
> https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release
>

Re: [DISCUSS] Apache PLC4X 0.10.0 RC1

[Lukas Ott]

Yes so we should go for RC2 and have a working 0.10 Version that can be
built.

Am Fr., 30. Sept. 2022 um 19:56 Uhr schrieb Ben Hutcheson <
ben.hut...@gmail.com>:

> Can confirm there's some SNAPSHOT revisions in the apache-kafka pom.
>
> On Fri, Sep 30, 2022 at 11:47 AM Otto Fowler 
> wrote:
>
> >  wrong, did not fix.  Any ideas?
> >
> > From: Otto Fowler  
> > Reply: Otto Fowler  
> > Date: September 30, 2022 at 13:42:21
> > To: dev@plc4x.apache.org  
> > Subject:  Re: [DISCUSS] Apache PLC4X 0.10.0 RC1
> >
> > ok, cleaning my .m2 seems to resolved, sorry for the noise
> >
> > From: Otto Fowler  
> > Reply: Otto Fowler  
> > Date: September 30, 2022 at 13:38:35
> > To: dev@plc4x.apache.org  
> > Subject:  Re: [DISCUSS] Apache PLC4X 0.10.0 RC1
> >
> > also with 11
> >
> > ✝  0.10.0/rc1/apache-plc4x-0.10.0   develop±  mvn --version
> > Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
> > Maven home: /usr/local/Cellar/maven/3.8.6/libexec
> > Java version: 11.0.2, vendor: Oracle Corporation, runtime:
> > /Library/Java/JavaVirtualMachines/openjdk-11.0.2.jdk/Contents/Home
> > Default locale: en_US, platform encoding: UTF-8
> > OS name: "mac os x", version: "10.16", arch: "x86_64", family: “mac"
> >  ✝  0.10.0/rc1/apache-plc4x-0.10.0   develop±  mvn clean install -U
> > [INFO] Scanning for projects...
> > Downloading from confluent:
> >
> >
> https://packages.confluent.io/maven/org/apache/plc4x/plc4j-integrations/0.10.0-SNAPSHOT/maven-metadata.xml
> > Downloading from confluent:
> >
> >
> https://packages.confluent.io/maven/org/apache/plc4x/plc4j-integrations/0.10.0-SNAPSHOT/plc4j-integrations-0.10.0-SNAPSHOT.pom
> > [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> > [FATAL] Non-resolvable parent POM for
> > org.apache.plc4x:plc4j-apache-kafka:0.10.0-SNAPSHOT: Could not find
> > artifact org.apache.plc4x:plc4j-integrations:pom:0.10.0-SNAPSHOT in
> > confluent (https://packages.confluent.io/maven/) and
> 'parent.relativePath'
> > points at wrong local POM @ line 23, column 11
> >  @
> > [ERROR] The build could not read 1 project -> [Help 1]
> > [ERROR]
> > [ERROR] The project org.apache.plc4x:plc4j-apache-kafka:0.10.0-SNAPSHOT
> >
> >
> (/Users/ottofowler/src/apache/forks/incubator-plc4x/downloaded-plc4x-0.10.0rc1/0.10.0/rc1/apache-plc4x-0.10.0/plc4j/integrations/apache-kafka/pom.xml)
> > has 1 error
> > [ERROR] Non-resolvable parent POM for
> > org.apache.plc4x:plc4j-apache-kafka:0.10.0-SNAPSHOT: Could not find
> > artifact org.apache.plc4x:plc4j-integrations:pom:0.10.0-SNAPSHOT in
> > confluent (https://packages.confluent.io/maven/) and
> 'parent.relativePath'
> > points at wrong local POM @ line 23, column 11 -> [Help 2]
> > [ERROR]
> > [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e
> > switch.
> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> > [ERROR]
> > [ERROR] For more information about the errors and possible solutions,
> > please read the following articles:
> > [ERROR] [Help 1]
> >
> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
> > [ERROR] [Help 2]
> >
> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
> >
> >
> >
> > From: Otto Fowler  
> > Reply: Otto Fowler  
> > Date: September 30, 2022 at 13:26:48
> > To: dev@plc4x.apache.org  
> > Subject:  Re: [DISCUSS] Apache PLC4X 0.10.0 RC1
> >
> > :(
> >
> > mvn --version
> > Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
> > Maven home: /usr/local/Cellar/maven/3.8.6/libexec
> > Java version: 9, vendor: Oracle Corporation, runtime:
> > /Library/Java/JavaVirtualMachines/adoptopenjdk-9.jdk/Contents/Home
> > Default locale: en_US, platform encoding: UTF-8
> > OS name: "mac os x", version: "10.16", arch: "x86_64", family: “mac"
> >
> >
> > ```./mvnw install -U
> > [INFO] Scanning for projects...
> > Downloading from confluent:
> >
> >
> https://packages.confluent.io/maven/org/apache/plc4x/plc4j-integrations/0.10.0-SNAPSHOT/maven-metadata.xml
> > Downloading from confluent:
> >
> >
> https://packages.confluent.io/maven/org/apache/plc4x/plc4j-integrations/0.10.0-SNAPSHOT/plc4j-integrations-0.10.0-SNAPSHOT.pom
> > [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> > [FATAL] Non-resolvable parent POM for
> > org.apache.plc4x:plc4j-apache-kafka:0.10.0-SNAPSHOT: Could not find
> > artifact org.apache.plc4x:plc4j-integrations:pom:0.10.0-SNAPSHOT in
> > confluent (https://packages.confluent.io/maven/) and
> 'parent.relativePath'
> > points at wrong local POM @ line 23, column 11
> >  @
> > [ERROR] The build could not read 1 project -> [Help 1]
> > [ERROR]
> > [ERROR] The project org.apache.plc4x:plc4j-apache-kafka:0.10.0-SNAPSHOT
> >
> >
> (/Users/ottofowler/src/apache/forks/incubator-plc4x/downloaded-plc4x-0.10.0rc1/0.10.0/rc1/apache-plc4x-0.10.0/plc4j/integrations/apache-kafka/pom.xml)
> > has 1 error
> > [ERROR] Non-resolvable parent POM for
> > 

Re: [VOTE] Apache PLC4X 0.10.0 RC1

[Lukas Ott]

+1 (binding)

Lukas

[x] Download all staged artifacts under the url specified in the
release vote email.
[x] Verify the signature is correct.
[x] Check if the signature references an Apache email address.
[x] Verify the SHA512 hashes.
[x] Unzip the archive.
[x] Verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES
files in the extracted source bundle.
[x] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files
in the extracted source bundle.
[x] [RM] Verify the staged source README, RELEASE_NOTE files
correspond to those in the extracted source bundle.
[x] [RM] Run RAT externally to ensure there are no surprises.
[x] Build the project according to the information in the README.md file.

Build with "./mvnw install"

Distributor ID: Ubuntu
Description:Ubuntu 22.04.1 LTS
Release:22.04
Codename:   jammy



Am Do., 29. Sept. 2022 um 19:28 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Apache PLC4X 0.10.0 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: v0.10.0
> Hash for the release tag: 014ee7a82f3d805dfbae518ec9a383e19a695e68
>
> 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-1044
> [2] https://dist.apache.org/repos/dist/dev/plc4x/0.10.0/rc1
> [3] https://www.apache.org/dev/release.html#approving-a-release
> [4]
> https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release
>
>

Re: [NOTICE] Removal of BitString PlcValue types and update to using PlcBYTE etc.

[Lukas Ott]

+1

On Wed, 28 Sep 2022 at 16.31, Christofer Dutz 
wrote:

> Hi all,
>
> while doing the pre-release grooming of our codebase and testing the
> drivers agains the hardware that I have here. I noticed painfully that it
> seems every single diver handled the BYTE, WORD, DWORD and LWORD types
> differently.
> I reached out to colleagues of mine from the Automation department and
> reached out to people on LinkedIn.
>
> Together with previous input on discussions here on the list, I decided to
> remove the BitString types completely and updated all drivers to now use
> the PlcBYTE, PlcWORD, PlcDWORD and PlcLWORD datatypes, which currently seem
> to be clones of the unsigned integer types.
>
> Even if I think it’s a bit of a step back, it doesn’t help if the rest of
> the world sems to be using the datatypes this way. Also does it make
> implementation a lot easier (Actually the main reason I ended up liking
> this option).
> Cause now the users have to deal with stuff like “bit-order” etc. Before
> this switch I was really trying to find a sensible way how we define the
> order of the bits as soon as more than one Byte is involved.
>
> I really hope this cleans up a lot of things in the drivers and makes
> things simpler for our users.
>
> Chris
>

Re: [VOTE] Apache PLC4X Build-Tools Code-Generation 1.6.0 RC1

[Lukas Ott]

+1

Lukas

System:
Distributor ID: Ubuntu
Description: Ubuntu 22.04.1 LTS
Release: 22.04
Codename: jammy

openjdk version "11.0.16" 2022-07-19
OpenJDK Runtime Environment (build 11.0.16+8-post-Ubuntu-0ubuntu122.04)
OpenJDK 64-Bit Server VM (build 11.0.16+8-post-Ubuntu-0ubuntu122.04, mixed
mode)

Executed command: /build-tools/apache-plc4x-code-generation-1.6.0$ mvn
install

Apache Maven 3.6.3
Maven home: /usr/share/maven
Java version: 11.0.16, vendor: Ubuntu, runtime:
/usr/lib/jvm/java-11-openjdk-amd64
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.15.0-48-generic", arch: "amd64", family:
"unix"

Used apache-rat-0.15.jar for license check.

This URL:
https://www.apache.org/dev/release/validation.html#approving-a-release ends
in 404.


[x] Download all staged artifacts under the url specified in the release
vote email.
[x] Verify the signature is correct.
[x] Check if the signature references an Apache email address.
[x] Verify the SHA512 hashes.
[x] Unzip the archive.
[x] Verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES files in
the extracted source bundle.
[x] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in
the extracted source bundle.
[x] [RM] Verify the staged source README, RELEASE_NOTE files correspond to
those in the extracted source bundle.
[x] [RM] Run RAT externally to ensure there are no surprises.
[x] Search for SNAPSHOT references
[x] Search for Copyright references, and if they are in headers, make sure
these files containing them are mentioned in the LICENSE file.
[x] Build the project according to the information in the README.md file.
[x] [RM] Build the project with all with-xyz profiles and tests enabled and
an empty maven local repo.

Am Do., 22. Sept. 2022 um 14:17 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Apache PLC4X Build-Tools Code-Generation 1.6.0 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/1.6.0
> Hash for the release tag: 9e91bf424bc4ee581158a200e67edaf02825097d
>
> 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-1042
> [2]
> https://dist.apache.org/repos/dist/dev/plc4x/build-tools/code-generation/1.6.0/rc1/
> [3] https://www.apache.org/dev/release/validation.html#approving-a-release
> [4] https://plc4x.apache.org/developers/release/validation.html
>
>

Re: [DISCUSS] Apache PLC4X Build-Tools Code-Generation 1.6.0 RC1

[Lukas Ott]

okay sorry had to "sudo apt install openjdk-11-jdk" ;-)

Am Do., 22. Sept. 2022 um 20:33 Uhr schrieb Lukas Ott <
ott.lukas...@gmail.com>:

> Some more details:
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-plugin-plugin:3.6.4:descriptor
> (default-descriptor) on project plc4x-maven-plugin: The API of the mojo
> scanner is not compatible with this plugin version. Please check the plugin
> dependencies configured in the POM and ensure the versions match.: Can't
> load library: /usr/lib/jvm/java-11-openjdk-amd64/lib/libawt_xawt.so ->
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-plugin-plugin:3.6.4:descriptor
> (default-descriptor) on project plc4x-maven-plugin: The API of the mojo
> scanner is not compatible with this plugin version. Please check the plugin
> dependencies configured in the POM and ensure the versions match.
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:215)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native
> Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:566)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
>
> Caused by: org.apache.maven.plugin.MojoExecutionException: The API of the
> mojo scanner is not compatible with this plugin version. Please check the
> plugin dependencies configured in the POM and ensure the versions match.
> at org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute
> (AbstractGeneratorMojo.java:334)
> at org.apache.maven.plugin.plugin.DescriptorGeneratorMojo.execute
> (DescriptorGeneratorMojo.java:94)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native
> Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMetho

Re: [DISCUSS] Apache PLC4X Build-Tools Code-Generation 1.6.0 RC1

[Lukas Ott]

lib/libawt_xawt.so
at java.lang.ClassLoader.loadLibrary (ClassLoader.java:2633)
at java.lang.Runtime.load0 (Runtime.java:768)
at java.lang.System.load (System.java:1837)
at java.lang.ClassLoader$NativeLibrary.load0 (Native Method)
at java.lang.ClassLoader$NativeLibrary.load (ClassLoader.java:2445)
at java.lang.ClassLoader$NativeLibrary.loadLibrary
(ClassLoader.java:2501)
at java.lang.ClassLoader.loadLibrary0 (ClassLoader.java:2700)
at java.lang.ClassLoader.loadLibrary (ClassLoader.java:2651)
at java.lang.Runtime.loadLibrary0 (Runtime.java:830)
at java.lang.System.loadLibrary (System.java:1873)
at java.awt.Toolkit$3.run (Toolkit.java:1399)
at java.awt.Toolkit$3.run (Toolkit.java:1397)
at java.security.AccessController.doPrivileged (Native Method)
at java.awt.Toolkit.loadLibraries (Toolkit.java:1396)
at java.awt.Toolkit. (Toolkit.java:1429)
at sun.awt.AppContext$2.run (AppContext.java:282)
at sun.awt.AppContext$2.run (AppContext.java:271)
at java.security.AccessController.doPrivileged (Native Method)
at sun.awt.AppContext.initMainAppContext (AppContext.java:271)
at sun.awt.AppContext$3.run (AppContext.java:326)
at sun.awt.AppContext$3.run (AppContext.java:309)
at java.security.AccessController.doPrivileged (Native Method)
at sun.awt.AppContext.getAppContext (AppContext.java:308)
at javax.swing.text.html.parser.ParserDelegator.getDefaultDTD
(ParserDelegator.java:59)
at javax.swing.text.html.parser.ParserDelegator.setDefaultDTD
(ParserDelegator.java:55)
at javax.swing.text.html.parser.ParserDelegator.
(ParserDelegator.java:109)
at org.apache.maven.tools.plugin.generator.GeneratorUtils.toText
(GeneratorUtils.java:343)
at org.apache.maven.tools.plugin.generator.GeneratorUtils.element
(GeneratorUtils.java:120)
at
org.apache.maven.tools.plugin.generator.PluginDescriptorGenerator.writeDescriptor
(PluginDescriptorGenerator.java:126)
at
org.apache.maven.tools.plugin.generator.PluginDescriptorGenerator.execute
(PluginDescriptorGenerator.java:83)
at org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute
(AbstractGeneratorMojo.java:320)
at org.apache.maven.plugin.plugin.DescriptorGeneratorMojo.execute
(DescriptorGeneratorMojo.java:94)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:566)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:347)
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR]   mvn  -rf :plc4x-maven-plugin


Am Do., 22. Sept. 2022 um 19:58 Uhr schrieb Lukas Ott <
ott.lukas...@gmail.com>:

> Can not build from source:
> [INFO] PLC4X Build Tools: Code Generation: PLC4X Maven Plugin FAILURE [
>  6.324 s]
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugi

Re: [DISCUSS] Apache PLC4X Build-Tools Code-Generation 1.6.0 RC1

[Lukas Ott]

Can not build from source:
[INFO] PLC4X Build Tools: Code Generation: PLC4X Maven Plugin FAILURE [
 6.324 s]
[INFO]

[INFO] BUILD FAILURE
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-plugin-plugin:3.6.4:descriptor
(default-descriptor) on project plc4x-maven-plugin: The API of the mojo
scanner is not compatible with this plugin version. Please check the plugin
dependencies configured in the POM and ensure the versions match.: Can't
load library: /usr/lib/jvm/java-11-openjdk-amd64/lib/libawt_xawt.so ->
[Help 1]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR]   mvn  -rf :plc4x-maven-plugin

System:
Distributor ID: Ubuntu
Description: Ubuntu 22.04.1 LTS
Release: 22.04
Codename: jammy

openjdk version "11.0.16" 2022-07-19
OpenJDK Runtime Environment (build 11.0.16+8-post-Ubuntu-0ubuntu122.04)
OpenJDK 64-Bit Server VM (build 11.0.16+8-post-Ubuntu-0ubuntu122.04, mixed
mode, sharing)

Executed command: /build-tools/apache-plc4x-code-generation-1.6.0$ mvn
install

Apache Maven 3.6.3
Maven home: /usr/share/maven
Java version: 11.0.16, vendor: Ubuntu, runtime:
/usr/lib/jvm/java-11-openjdk-amd64
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.15.0-47-generic", arch: "amd64", family:
"unix"


Am Do., 22. Sept. 2022 um 14:19 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> 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.
>
>

Re: [API] Added a getArrayDimensions method to the PlcBrowseItems type

[Lukas Ott]

+1  and for those who are interested here the article where it has been
publicly discussed:
https://www.linkedin.com/posts/christofer-dutz_automation-engineering-api-activity-6974392632059781123-d1PN
:-)

Am So., 11. Sept. 2022 um 16:01 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Hi all,
>
> while I’m working on the UI and fine-tuning the API for the Browse API, I
> had to add some Array-Info types that in case of array types.
> And as it turns out, in contrast to usual arrays in “normal” programming
> languages, in PLCs arrays seem to be able to start at any index and have a
> given number of elements.
>
> So, I decided for a notation:
>
> [{from-index} .. {to-index}]
>
> And there can be multi-dimensional arrays, so there could be multiple of
> these array blocks in a chain.
>
> Just wanted to keep you informed.
>
>
> Chris
>

Re: [DRAFT] Board Report

[Lukas Ott]

+1


You do not want to mention our Go based CLI tool or your JavaFX based UI
Proof of Concept?



Christofer Dutz  schrieb am Sa., 10. Sept. 2022,
15:29:

> Hi folks
>
> It’s reporting time again ;-)
>
> I’m planning on posting the following report on Monday, would be cool to
> get some approval or feedback:
>
> Chris
>
>
>
>
>
> ## Description:
> The mission of the Apache PLC4X project is creating a set of libraries for
> communicating with industrial programmable logic controllers (PLCs) using a
> variety of protocols but with a shared API.
>
> ## Issues:
> There are currently no issues requiring board attention
>
> ## Membership Data:
> Apache PLC4X was founded 2019-04-17 (3 years ago)
> There are currently 20 committers and 13 PMC members in this project.
> The Committer-to-PMC ratio is roughly 5:4.
>
> Community changes, past quarter:
> - No new PMC members. Last addition was César García on 2021-10-01.
> - Iñigo Angulo Otegi was added as committer on 2022-08-29
>
> ## Project Activity:
>
> It's been an interesting quarter. The project has seen numerous different
> initiatives. Our BACNet driver has gotten a lot of attention, same with a
> new
> C-Bus driver. Our Beckhoff ADS driver has received a major overhaul. Work
> on
> some drivers (Especially PROFINET) has been taken over by other members of
> the
> community. A lot of progress has been made on the Browse and Discovery API.
> Besides that the community has been working on PLC4PY (PLC4X on Python),
> PLC4RS (PLC4X on Rust).
>
> We haven't had any releases in the last quarter.
>
> Our last releases were:
> 0.8.0 was released on 2021-01-28.
> 0.7.0 was released on 2020-05-25.
> 0.6.0 was released on 2020-03-01.
>
> However, we're currently tying up the last strings in preparation for our
> next
> release of version 0.10.0. Also will there be multiple presentations on
> PLC4X
> at the upcoming ApacheCon NA in New Orleans.
>
> ## Community Health:
> Communication-wise, it's been a pretty quiet quarter. I credit this to the
> fact that most people actively working on some of the features are working
> on
> them on their own, only syncing up every now and then. Nothing to be really
> concerned about. Looking at most of the metrics, most of them have
> increases
> from 70%-136% while the only decrease is on the dev@ and issues@ mailing
> lists
>
>

Re: PLC4X Community Call today 19:00 CET

[Lukas Ott]

+1

Am Di., 6. Sept. 2022 um 13:38 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Hi all,
>
> I just wanted to remind you, that it’s the first Tuesday of the month
> again and therefore it’s time for another community call.
>
> You can join, with this link:
> https://us06web.zoom.us/j/91591629512?pwd=Z3A1WTdNbXRmMnZIZ2c3SVdYaHo3QT09
>
> If you plan to attend, please reply to this email thread.
>
> Chris
>
>

Re: [DISCUSS] Format for specifying "known messages"

[Lukas Ott]

I like that approach really much to leverage our existing XML unit tests
for this kind of code generation.
+1

Am Mi., 24. Aug. 2022 um 13:52 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Hi all,
>
> It’s getting more and more challenging to keep all of the driver types we
> have in all the languages perfectly in-sync.
> So I’m thinking of starting the next step on generating more of the code.
>
> Right now I’d love to generate the construction of well known messages.
> As usually you have some messages that you send in certain situations.
> There usually require you to fill 90% of the fields with constant values
> and only 2-3 of the remaining are actually dynamic.
>
> So I’d love to generate a “message-factory” as a first step.
>
> There we’d have methods/functions like “createCotpConectionRequest” and
> you only pass in the dynamic parts. This method/function would then simply
> return a pre-initialized message that we can simply fire out.
>
> I think our mspec format just isn’t right for this sort of thing. I once
> did a POC using XML and I generally liked it pretty much.
> So in this case we’d use the format like we use in the tests, but with the
> only difference, that for the dynamic parts, we could use placehoderrs like
> “${someVariable}” and this would generate code that initializes the
> data-structures for the given languages.
>
> What do you think? Sticking with XML for this, would make it more
> compatible with our tests … we could simply take xml from our unit and
> integration tests, and simply convert them into message templates.
>
> Chris
>
>

Re: [CALL FOR VOLUNTEERS] Updating the documentation

[Lukas Ott]

Hi Chris,

We can discuss the details next week in our PLC4X community meeting.
I would like to support and update the documentation.

So we may do some examples together during the community meeting and I will
then continue updating other parts (based on the example we created
together) of the documentation.

Luk

Am So., 26. Juni 2022 um 13:17 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Hi all,
>
> I have recently noticed that the documentation of most of our drivers,
> tools and integration modules has grown a bit stale and out-of-date.
> Who would be willing to help with giving the existing documents a review
> and some updates?
> I know that I could definitely do that, but I also know that this could be
> considered low-hanging-fruit for people willing to start contributing and I
> would like to concentrate on starting to work on the documentation of our
> code-generation stuff, which I would not consider low-hanging-fruit.
>
> So? Who wants to become a bit more active again or who want's to get
> started in contributing to our awesome project?
>
> It's actually super simple, as our website is generated as part of the
> build by the CI server and all you need to do, is update the asciidoc
> documents in src/site/asciidoc.
>
> As always ... always happy to help if you need help.
>
> Chris
>

Re: [PROPOSAL] Implement a Java GUI application for browsing PLCs with PLC4X

[Lukas Ott]

What about https://cordova.apache.org/ and creating an Electron App?

https://cordova.apache.org/docs/en/11.x/guide/platforms/electron/index.html

So we can deploy easily to all kinds of platforms?

Example for a very successful Frontend application:
https://github.com/jgraph/drawio

Interesting discussion a few years ago:
https://twitter.com/tuxtor/status/1167454864932319232

-> Electron is de facto the standard for Desktop Applications at least at
the moment.

https://medium.com/the-web-tub/electron-on-cordova-29ede5d6d789

https://www.reddit.com/r/javahelp/comments/lrg2ho/web_app_vs_java_fx_vs_electron_js/

My five cents to this conversation ;-)

Luk

Am Do., 23. Juni 2022 um 16:19 Uhr schrieb Sebastian Rühl :

> I would vote doing it as a terminal application with tcell :D
>
> https://github.com/gdamore/tcell
> https://github.com/gcla/gowid
>
> good example for that is termshark
>
> - Sebastian
>
> On 2022/06/23 13:47:29 Christofer Dutz wrote:
> > Hi all,
> >
> > Great to see this discussion here :-)
> >
> > Well, I agree that going down the lane of basing something on NetBeans,
> Eclipse, IntelliJ, VSCode makes the tool a bit too big and complicated.
> Integrating something based on Eclipse into our build also would add
> Nightmares to that.
> >
> > I probably would have chosen Java/Kotlin with JavaFX ... but I would
> say, those who actually work on it should choose what they are comfortable
> with.
> >
> > So perhaps we could see who's actually interested, willing and able to
> help on the coding and then these people should discuss how to implement
> it. I'll be available as a "Mentor" if any help is needed in integrating
> that into the build or if PLC4X related help is needed.
> >
> > Chris
> >
> >
> > -Original Message-
> > From: Stephen Snow 
> > Sent: Donnerstag, 23. Juni 2022 15:31
> > To: dev@plc4x.apache.org
> > Subject: Re: [PROPOSAL] Implement a Java GUI application for browsing
> PLCs with PLC4X
> >
> > Truly,
> > To scaffold an application that can be rapidly utilized in Java/Kotlin I
> would strongly recommend Quarkus from https://quarkus.io/. It likes to
> use the GraalVM and readily can build out to native or native in container.
> It can be deployed ootb in development mode with ci happening as you
> develop in netbeans say.
> >
> > Just my 2c worth.
> >
> > Regards,
> > Stephen
> > On Thu, 2022-06-23 at 14:59 +0200, Łukasz Dywicki wrote:
> > > I been wrapping head around this as I had a necessity to watch CANopen
> > > traffic decoded by plc4x. I ended up building fairly basic web page
> > > which displayed most recent frames (so I could stay with local
> > > socketcan transport), yet it was far from useful or portable. Recently
> > > I also did struggle a lot with bloody modbus. My usecases are often
> > > focused on making the commissioning to generate further software
> > > configuration.
> > >
> > > My little research in topic of desktop applications ended up at javafx
> > > which allows to make it small and compile to native binary thanks to
> > > graal. My experiences with RCP platforms are rather bad (I did some
> > > small Eclipse RCP projects), even if I have no issues with OSGi.
> > > Problem
> > > I see in RCP platforms is sparse development documentation, I also
> > > perceive both Eclipse RCP and Netbeans as focused mainly on organizing
> > > navigation while strongly depending on UI frameworks (jface/swt or
> > > swing/awt). Effectively you still need to build tables and so on, but
> > > with much more overhead.
> > > Please do not take above too seriously in context of Netbeans, I don't
> > > know much about it and its flexibility. I don't know how to build it
> > > with Maven, hence it feels strange.
> > > For the Kotlin stuff and frameworks there - I can say that any UI
> > > project which Google is pushing is a red flag to me. Looking at GWT,
> > > Angular 1.x (I used both) I simply fear that they can step back from
> > > "experiment" after a year or two leaving everything to the community.
> > > I
> > > looked at kootlin and javafx a while ago and there is not much
> > > happening there. I don't know if is because of maturity, javafx issues
> > > or shift to other UI approaches.
> > >
> > > As I had no time to work on it I just postponed that to a future.
> > > Yet, I
> > > still dream from time to time about proper "fieldbus.app". ;-)
> > >
> > > Cheers,
> > > Łukasz
> > >
> > > On 23.06.2022 14:46, Michal Harakal wrote:
> > > > Hi,
> > > >
> > > > I would be also interested in, having a strong opinion on technology
> > > > stack, but fully open to design and function.
> > > >
> > > > My suggestion is writing a Desktop App with Kotlin Jetpack Compose
> > > > for Desktop:
> > > >
> > > > Props:
> > > > * modern, state of the art, way to write reactive UI (natural way to
> > > > implement unidirectional data flows architectures)
> > > > * JVM target
> > > > * open source, backed by Google And Jetbrains (they use it in their
> > > > critical products)
> > 

Re: Zenoh protocol

[Lukas Ott]

Hi Sudhakar,

Welcome to the list :-)

You can just use PLC4X to talk to the current PLCs and then translate to
Zenoh protocol. As the concept is quite similar to MQTT. See
https://github.com/apache/plc4x/tree/develop/plc4j/examples/hello-connectivity-mqtt

We also support Kafka (
https://github.com/apache/plc4x/blob/d0c9fd63277d4bd7bb628689e9b040b9fd27376b/plc4j/integrations/apache-kafka/README.md)
and also think about including nats.io

Regards,
otluk


Am Mi., 22. Juni 2022 um 22:12 Uhr schrieb Allam, Sudhakara <
sudhakara.al...@weatherford.com>:

> Hi,
>
> I am trying to formalize a new system components and particularly
> interested in using Zenoh for its performance,
> Simplicity and functionality. Could you please let me know if this is one
> of the protocol that you may adopt for PLC4x?
> It is not yet adapted by any PLC manufacturer, however, my main aim is to
> directly poll instruments using this protocol.
> Please let me know.
>
> Regards,
> Sudhakar
> This electronic communication is for the use of the intended recipient(s)
> only, and may contain confidential, privileged or proprietary information.
> If you are not an intended recipient, please reply to the sender and then
> immediately delete and destroy all copies of the communication. See our
> Electronic Communications Terms and Conditions<
> https://www.weatherford.com/en/about-us/policies/terms-and-conditions-for-electronic-communications/>
> for further information
>

Re: [DISCUSS] Is a page like this ok?

[Lukas Ott]

In my humble opinion - yes that is ok - as long as it is aligned with the
Apache policies. And in this case it looks fine to me.

Am Mi., 15. Juni 2022 um 13:43 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Hi all,
>
> I just recently was in need of a good profiler and EJ-Technologies were
> kind enough to send me a site-license for the Apache PLC4X project.
> Usually they require a no "nofollow" link back to JProfiler. I told them
> that we are not allowed to do that due to Apache policies.
> They said in this case it wouldn't be a problem to have a nofollow link.
>
> So, I created a page with all the commercial tools I know we get free
> licenses for (didn't want to have just JProfiler on it)
> It's not yet linked to the menu so you can only reach it, if you know the
> url.
>
> https://plc4x.apache.org/developers/tools.html
>
> Would it be ok to integrate this page into the navigation menu?
>
> Chris
>
>
>
>

Re: [DRAFT] June Board Report

[Lukas Ott]

+1 and we really should aim to have a release soon after all the
re-factoring work done by the awesome Sebastian and Chris.

Am Do., 2. Juni 2022 um 11:48 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> I updated the Project Activity to this:
>
>
> ## Project Activity:
> In the past 3 months the project has been waking up after it's slumber.
> Some
> members of the community have been working on PLC4PY and just recently
> another
> initiative has been workinng on brinigng PLC4X to Rust (PLC4RS). The rest
> has
> been continuously addressing reported bugs and issues and have continuously
> been working on improving things throughout the project.
>
> Last Releases:
> - 0.9.1 (Released on 2021-12-17)
> - 0.9.0 (Released on 2021-09-21)
>
> -Original Message-
> From: Christofer Dutz 
> Sent: Donnerstag, 2. Juni 2022 11:46
> To: dev@plc4x.apache.org
> Subject: RE: [DRAFT] June Board Report
>
> Just noticed it's missing the last release and dates ...
>
> -Original Message-
> From: Christofer Dutz 
> Sent: Donnerstag, 2. Juni 2022 11:45
> To: dev@plc4x.apache.org
> Subject: [DRAFT] June Board Report
>
> Hi all ..
>
> Here the draft of the report I was planning to submit:
>
>
> ## Description:
> The mission of the Apache PLC4X project is creating a set of libraries for
> communicating with industrial programmable logic controllers (PLCs) using a
> variety of protocols but with a shared API.
>
> ## Issues:
> None (anmore)
>
> ## Membership Data:
> Apache PLC4X was founded 2019-04-17 (3 years ago) There are currently 19
> committers and 13 PMC members in this project.
> The Committer-to-PMC ratio is roughly 5:4.
>
> Community changes, past quarter:
> - No new PMC members. Last addition was César García on 2021-10-01.
> - No new committers. Last addition was Thomas Frost on 2021-05-07.
>
> ## Project Activity:
> In the past 3 months the project has been waking up after it's slumber.
> Some members of the community have been working on PLC4PY and just recently
> another initiative has been workinng on brinigng PLC4X to Rust (PLC4RS).
> The rest has been continuously addressing reported bugs and issues and have
> continuously been working on improving things throughout the project.
>
> ## Community Health:
> Most interaction regarding Bugs and PRs is being handled via GitHub. Also
> most of the initiatives seem to be working mostly silently or usig slack
> for coordination. So I'm not worried about the drop of 38% in mailinglist
> communication.
>
> 14 code contributors in the past quarter (no change) 44 PRs opened on
> GitHub, past quarter (-4% change) 43 PRs closed on GitHub, past quarter
> (-2% change)
>

Re: PLC4J EIP String Reads

[Lukas Ott]

Hello Andy,

Can you also provide a PCAP from Wireshark and add it to a ticket in Jira?

Thank you!

BR / otluk

Am Do., 5. Mai 2022 um 23:48 Uhr schrieb Andy Grebe :

> Hello,
>
> I'm working on a project using EIP and need to read string tags from a
> PLC.  When I send the read, I see the string coming back in wireshark, but
> it looks like it is not getting parsed correctly.  I am able to read BOOLs,
> INTs, etc, but I get an error when attempting to read STRINGs.
>
> java.lang.NullPointerException: Cannot invoke
> "org.apache.plc4x.java.api.value.PlcValue.getString()" because the return
> value of
> "org.apache.plc4x.java.api.messages.PlcReadResponse.getPlcValue(String)" is
> null
>
> I can provide code snippets, but it's written the same for all of the
> fields.
>
> Thanks,
> Andy
>

Re: [DISCUSS] Should we ask ComDev to setup PLC4X on redbubble so people could by PLC4X caps, hoodies, etc.?

[Lukas Ott]

+1 for Toddy-Hoodie

Am Mi., 4. Mai 2022 um 09:35 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> I guess the title says it all.
>
> Right now, you can only purchase stickers:
> https://www.redbubble.com/de/shop/?query=PLC4X=search_box
>
> Which is cool, but I'd love a Toddy-Hoodie ;-)
>
> Chris
>

Re: [DISCUSS] Start release process for 0.10.0?

[Lukas Ott]

+1 and 0.11.0 we release in October for ApacheCon :-)

Am Fr., 29. Apr. 2022 um 12:43 Uhr schrieb Sebastian Rühl :

> Sure, sounds like fun
>
> - Sebastian
>
> On 2022/04/29 09:25:28 Christofer Dutz wrote:
> > Hi all,
> >
> > we have again implemented a lot of new features and fixed issues ... but
> mainly we've changed some driver names (Modbus) which are no longer in-line
> with our website.
> > I think we should start the process for a new release.
> >
> > What do you think?
> >
> > Chris
> >
> >
>

Re: PLC4Py - Change of Build System - Poetry is for the time beeing not suitable anymore

[Lukas Ott]

I mean it is supported by jazzband :-) :
https://github.com/jazzband/pip-tools

https://pip-tools.readthedocs.io/en/latest/

Am Mi., 20. Apr. 2022 um 10:41 Uhr schrieb Sebastian Rühl :

> pip-tools SGTM
>
> - Sebastian
>
> On 2022/04/19 19:52:03 Lukas Ott wrote:
> > Hello PLC4X Developers,
> >
> > As shown here: https://github.com/apache/plc4x/pull/348
> >
> > We started the discussion to change our build system.
> >
> > Poetry has at the moment an increasing amount of issues:
> > https://github.com/python-poetry/poetry/issues
> >
> > Which are not fixed soon. Even that Poetry is a good solution and was the
> > right decision to begin with. We need a solution that works for our
> > purposes.
> >
> > Therefore here are some links comparing different possibilities:
> > https://remastr.com/blog/pip-pipenv-poetry-comparison
> >
> >
> https://www.reddit.com/r/Python/comments/limd9t/poetry_vs_pipenv_vs_piptools_what_do_you_use/
> >
> > My suggestion would be to go with https://pypi.org/project/pip-tools/
> It is
> > more low-level but also more stable / reliable.
> >
> > What are your thoughts?
> >
> > Thank you Ben! It is really fun to read / see your work in the Pull
> request
> > :-)
> >
> > Cheers,
> > Lukas
> >
>

PLC4Py - Change of Build System - Poetry is for the time beeing not suitable anymore

[Lukas Ott]

Hello PLC4X Developers,

As shown here: https://github.com/apache/plc4x/pull/348

We started the discussion to change our build system.

Poetry has at the moment an increasing amount of issues:
https://github.com/python-poetry/poetry/issues

Which are not fixed soon. Even that Poetry is a good solution and was the
right decision to begin with. We need a solution that works for our
purposes.

Therefore here are some links comparing different possibilities:
https://remastr.com/blog/pip-pipenv-poetry-comparison

https://www.reddit.com/r/Python/comments/limd9t/poetry_vs_pipenv_vs_piptools_what_do_you_use/

My suggestion would be to go with https://pypi.org/project/pip-tools/ It is
more low-level but also more stable / reliable.

What are your thoughts?

Thank you Ben! It is really fun to read / see your work in the Pull request
:-)

Cheers,
Lukas

Re: [DISCUSS] Long running branches

[Lukas Ott]

+1
I think it is about time to clean up and bringing most of the things to
develop branch . Therefore we have the sandbox . Of course if there is
something breaking the existing stuff in Java, Go or C we may open a
branch. but most of the branches seem to be not in use anymore and it es
getting really hard to getting the old branches back to "develop" branch.

Am Do., 7. Apr. 2022 um 13:34 Uhr schrieb Sebastian Rühl :

> I agree. It's fine developing new features on develop as long as they are
> not breaking the build or have a regression. So in case of plc4py this is
> completely fine as this is a T-0 implementation.
>
> - Sebastian
>
> On 2022/04/07 11:08:36 Christofer Dutz wrote:
> > Hi all,
> >
> > We have an always growing number of branches where things have been
> begun, but never finished (Or at least never been taken back to develop)
> > Now some of the branches are so old, that rebasing them is not really
> possible anymore.
> >
> > Could you please have a look at the branches you created, if they are
> still valid, please update/rebase them. If they are obsolete, delete them.
> If they contain things develop needs, please port them to develop.
> >
> > Especially for the PLC4Py work, I would feel more comfortable with this
> development being done on "develop" (Similar to PLC4Net) ... only this way
> do we have it on our radar when working on things. I don't want to waste
> your time and effort. I do think that people understand that the different
> parts of PLC4X have different maturities and having a not yet fully
> functional PLC4Py is nothing to be ashamed of.
> >
> > What do you folks think?
> >
> > Chris
> >
>

Re: PLC4X Error

[Lukas Ott]

Hi Zap,

Welcome to our mailing list :-)

Can you give us a little bit more details.
What version of PLC4X are you running and is this a Kafka related error or
does the error occur from the modbus driver and then which Modbus driver.
(Does the error also occur when connecting to the Modbus Device without
Kafka)

Thank you!

Best regards,
otluk

Am Fr., 1. Apr. 2022 um 09:27 Uhr schrieb Zap Tashkilot :

>
> Hi
>
> I want to implement PLC4X and Kafka in some of our projects but it seems
> to be some errors that I can't get rid of, I hope you can help with that.
>
> ERROR [plc-modbus-source|task-0] WorkerSourceTask{id=plc-modbus-source-0}
> Task threw an uncaught and unrecoverable exception. Task is being killed
> and will not recover until manually restarted
> (org.apache.kafka.connect.runtime.WorkerTask:195)
> java.lang.NoClassDefFoundError:
> com/fasterxml/jackson/dataformat/yaml/YAMLFactory
>
> thanks in advanced
>
>
> Best Regards/Med venlig hilsen
> Zap Tashkilot
> Project Engineer/Projektingeniør
>
> +45 61812840
> Kontakt mig på Teams<
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fteams.microsoft.com%2Fl%2Fchat%2F0%2F0%3Fusers%3DZap.Tashkilot%40Logimatic.dk=04%7C01%7Czap%40logimatic.dk%7C4498ba7211824a56b08408d9c54fde26%7C42712bb734fd467d9467b16fff25db5d%7C1%7C0%7C637757769284141272%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0=Aq1VsyZjSQ8iPyuyLzztLLSYO%2B1xP%2FrlpVq0BAjj6Vo%3D=0
> >
>
> LOGIMATIC Find Logimatic på LinkedIn<
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.linkedin.com%2Fcompany%2Flogimatic=04%7C01%7Czap%40logimatic.dk%7C4498ba7211824a56b08408d9c54fde26%7C42712bb734fd467d9467b16fff25db5d%7C1%7C0%7C637757769284141272%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0=wxvosODhPe2n%2F5gOVcq%2FDi%2Bxirm2Spl9xJzqC061hpc%3D=0>
> eller Facebook<
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.facebook.com%2FLogimatic.dk=04%7C01%7Czap%40logimatic.dk%7C4498ba7211824a56b08408d9c54fde26%7C42712bb734fd467d9467b16fff25db5d%7C1%7C0%7C637757769284151273%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0=iuT9LFAuq6kZ7j4DZuu03bAd1ycI9KduoX8WIOEkF%2B4%3D=0
> >
> Besøg logimatic.dk<
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.logimatic.dk%2F=04%7C01%7Czap%40logimatic.dk%7C4498ba7211824a56b08408d9c54fde26%7C42712bb734fd467d9467b16fff25db5d%7C1%7C0%7C637757769284151273%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0=QYrA80IgHTQxkT%2BqHFcqEh7a1i9EMRD64HE38E29GHY%3D=0
> >
>
>

Re: [DISCUSS] Rename "modbus" to "modbus-tcp"?

[Lukas Ott]

Exactly this is why I gave a +1 and confirmed the three suggested naming
conventions.
Just listed additionally all publicly known Modbus related protocols so
that everyone in the community is on the same page :-)

Am Mi., 9. März 2022 um 17:07 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Hi Lukas,
>
> I think that Modbus+ is a completely different thing. Seems to be related
> to routing of Modbus traffic ... haven't looked too deep at it.
>
> From the Spec side there are 3 variants:
> - Modbus TCP
> - Modbus RTU
> - Modbus ASCII
>
> In general Modbus RTU and ASCII are sort of the same (Serial) ... the main
> difference is the encoding of the payload and the termination of frames.
> That's why I'll leave the ModbusSerialAdu as topmost packet in both Modbus
> RTU and ASCII, as the difference is handled on the level between the
> transport and the driver.
>
> Please correct me if I'm wrong,
>
> Chris
>
> -Original Message-
> From: Lukas Ott 
> Sent: Mittwoch, 9. März 2022 16:48
> To: dev@plc4x.apache.org
> Subject: Re: [DISCUSS] Rename "modbus" to "modbus-tcp"?
>
> +1
>
> I would follow the most common naming convention and call the drivers the
> following:
> - Modbus ASCII
>   - Supported Devices: Any Device Supporting Modbus ASII, Any Modbus
> ASCII Comliant PLC, Flow Computers
> - Modbus TCP/ IP (What is Modbus TCP/IP ? | Modbus Tcp/ip vs Ethernet ip -
> The Automization <https://theautomization.com/what-is-modbus-tcp-ip/>)
> - Supported Devices: Applicom: Generic Modbus, TSX Premium, TSX
> Quantum, Fluenta FGM, Instromet, Mailbox, Modbus Ethernet, Roxar RFM
> - Modbus Plus (Difference between Modbus & Modbus Plus | Instrumentation
> and Control Engineering (automationforum.co) <
> https://automationforum.co/difference-between-modbus-modbus-plus/> )
>   - Supported Devices: AT-984 Programmable Controller Board, Hilscher
> CIF Card, Modbus Plus ISA PC Adapter Card, Modbus Plus PCI PC Adapter Card,
> Modbus Plus Type II PCMCIA Card, Modbus Plus Type III PCMCIA Card, Modbus
> Plus Type III PnP PCMCIA Card, SA85 (-002 and -001) PC Interface Cards,
> SA85-PCI
> - Modbus Serial
> - Supported Devices: Daniel S500 Flow Computer, Dynamic Fluid Meter,
> Elliot Flow Computer, Magnetek GPD 515 Drive, Modbus Compatible Devices,
> Omni Flow Computer (Enron Modbus), TSXCUSBMBP USB Adapter
> - Modbus RTU Server Serial
> - Any Modbus compatible devices
>
> Modbus ASCII vs Modbus RTU vs Modbus TCP/IP - The Automization <
> https://theautomization.com/modbus-ascii-vs-modbus-rtu-vs-modbus-tcpip/>
>
> To sum up, basically following your suggestion: modbus-tcp, modbus-rtu and
> modbus-ascii sounds like a good approach.
>
> Cheers,
> otluk
>
>
>
> Am Mi., 9. März 2022 um 15:19 Uhr schrieb Christofer Dutz <
> christofer.d...@c-ware.de>:
>
> > Hi all,
> >
> > I'm currently working on the modbus RTU stuff ... as in general the
> > protocols are referred to modbus-tcp, modbus-rtu und modbus-ascii, I
> > would like to rename the "modbus" to "modbus-tcp" ... While modbus-tcp
> > will not be many variants, will the modbus-rtu and ascii also be
> > available as "modbus-rtu:tcp" if a tcp tunnel is used.
> >
> > What do you think?
> >
> > Chris
> >
>

Re: [DISCUSS] Rename "modbus" to "modbus-tcp"?

[Lukas Ott]

+1

I would follow the most common naming convention and call the drivers the
following:
- Modbus ASCII
  - Supported Devices: Any Device Supporting Modbus ASII, Any Modbus
ASCII Comliant PLC, Flow Computers
- Modbus TCP/ IP (What is Modbus TCP/IP ? | Modbus Tcp/ip vs Ethernet ip -
The Automization )
- Supported Devices: Applicom: Generic Modbus, TSX Premium, TSX
Quantum, Fluenta FGM, Instromet, Mailbox, Modbus Ethernet, Roxar RFM
- Modbus Plus (Difference between Modbus & Modbus Plus | Instrumentation
and Control Engineering (automationforum.co)
 )
  - Supported Devices: AT-984 Programmable Controller Board, Hilscher
CIF Card, Modbus Plus ISA PC Adapter Card, Modbus Plus PCI PC Adapter Card,
Modbus Plus Type II PCMCIA Card, Modbus Plus Type III PCMCIA Card, Modbus
Plus Type III PnP PCMCIA Card, SA85 (-002 and -001) PC Interface Cards,
SA85-PCI
- Modbus Serial
- Supported Devices: Daniel S500 Flow Computer, Dynamic Fluid Meter,
Elliot Flow Computer, Magnetek GPD 515 Drive, Modbus Compatible Devices,
Omni Flow Computer (Enron Modbus), TSXCUSBMBP USB Adapter
- Modbus RTU Server Serial
- Any Modbus compatible devices

Modbus ASCII vs Modbus RTU vs Modbus TCP/IP - The Automization


To sum up, basically following your suggestion: modbus-tcp, modbus-rtu and
modbus-ascii sounds like a good approach.

Cheers,
otluk



Am Mi., 9. März 2022 um 15:19 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Hi all,
>
> I'm currently working on the modbus RTU stuff ... as in general the
> protocols are referred to modbus-tcp, modbus-rtu und modbus-ascii, I would
> like to rename the "modbus" to "modbus-tcp" ... While modbus-tcp will not
> be many variants, will the modbus-rtu and ascii also be available as
> "modbus-rtu:tcp" if a tcp tunnel is used.
>
> What do you think?
>
> Chris
>

Re: Update to my role at Apache

[Lukas Ott]

I do not think it is necessary as it is just the report and is not related
to our decision making process. So i am fine.

Christofer Dutz  schrieb am Sa., 5. März 2022,
11:42:

> Hi all,
>
> I am not sure everyone on the project heard it, but last Thursday I was
> elected as one of the members of the Board of Directors of the ASF.
>
> I am more than happy to continue my role as VP of Apache PLC4X (Currently
> it's writing the board report), but I just wanted to hear your opinions.
> I am also happy to step back, if you think this is necessary.
>
> What do you folks think?
>
> Chris
>
>
>

Re: [DRAFT] March PLC4X board report

[Lukas Ott]

+1

Am Do., 3. März 2022 um 11:11 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Had to hand write this one ... seems the report generator is currently
> defective, but as we reduced the numbers in the report anyway, it wasn't
> too much additional work ;-)
>
>
>
> I did ad a bit mor personal part to the Community health part as I think
> the board should be aware of it.
>
>
>
> If I don't see any objections, I'll submit this in a few days.
>
>
>
>
>
>
>
>
>
> ## Description:
>
> The mission of the Apache PLC4X project is creating a set of libraries for
> communicating with industrial programmable logic controllers (PLCs) using a
> variety of protocols but with a shared API.
>
>
>
> ## Issues:
>
> There are currently no issues requiring board attention. The previously
> reported absence of PMC activity seems to have disappeared. I am no longer
> concerned about this.
>
>
>
> ## Membership Data:
>
> Apache PLC4X was founded 2019-04-17 (almost 4 years ago) There are
> currently 19 committers and 13 PMC members in this project.
>
> The Committer-to-PMC ratio is roughly 5:4.
>
>
>
> Community changes, past quarter:
>
> - César García was added to the PMC on 2021-10-01
>
> - No new committers. Last addition was Thomas Frost on 2021-05-07.
>
>
>
> ## Project Activity:
>
> The project has continuously been working on adding new features, fixing
> bugs, and improving existing code. Probably the most significant block of
> work has been the complete re-write of our code-generation core. In
> anticipation of more programming-languages coming to the project, we
> refactored and rewrote most of the code-generation to make it simpler to
> develop new code-generation templates. In the end all of this didn't change
> a single driver, but the overall usability of our tooling has improved as
> well as we lowered the entry-bar for folks coming into the project.
>
>
>
> ## Community Health:
>
> Project activity was low in December. In the beginning of January, I
> (Chris) posted a blog post [1], where I announced that I personally would
> be stopping to provide free community support for companies. This blogpost
> unexpectedly went viral. Online and offline news picked it up all over the
> world and reported about it in the context of the whole "sustainability of
> open-source" discussion. I did see one occasion where false news was spread
> (HackerNews reported Apache PLC4X was giving up free community support),
> but I think I managed to correct that. Besides that, it generally brought a
> lot of attention to the topic of open-source sustainability, but also to
> our project. Since then, we have seen a significant increase in page views
> to our website, to the github repository and we even got several new
> contributors sending pull-requests, bug reports, etc. There are also
> several companies willing to invest in PLC4X development. Admittedly now, I
> am really happy with the activity in the project. (I would have loved to
> provide numbers, but currently the board report tool seems defective)
>
> My general takeaway is, that it looks as if me stepping back a bit might
> even have been good for the project. I am not giving up on the project, I
> just switched to not instantly fix everything and rather help people
> reporting bugs into fixing them themselves and contributing this back.
>
>
>
> Perhaps projects in which one or a few individuals are excessively trying
> to keep all balls in flight is counter-productive with respect to
> developing a healthy community.
>
> [1]
> https://github.com/chrisdutz/blog/blob/main/plc4x/free-trial-expired.adoc
>

Re: [CODE GENERATION] Updates from today

[Lukas Ott]

+1 awesome job Chris and Sebastian ! #teamToddy

Am Di., 22. Feb. 2022 um 21:24 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Hi all,
>
> the last few days I was working hard on creating a new C template module
> based on our latest refactorings. There I noticed I need not only a target
> type (The type of the expression output) but also the current type when
> working with expressions. Sebastian stumbled over the same problem in Java.
> At first, I wanted to pass along the current type but Sebastian convinced
> me to do it in the mspec parser.
>
> So today we enabled the mspec parser to assign a type to each literal of
> an expression. This is particularly interesting for variable expressions.
>
> Now in the code-generation we can simply access the type of a variable at
> every step of the generation process. This will allow simplifying the
> templates quite a bit.
>
> But the super-awesome side-effect is, that now the parser ensures
> expressions are valid and you're not referencing properties that don't
> exist. This will help with developing syntactically and semantically
> correct protocol specs.
>
> We even thought, that now it would make sense to have a test in every
> protocol module, which simply tries to parse the mspec and to report errors
> early.
>
> So much for the update .. I bet 99,99% of our users will not even notice
> any change ;-)
>
> Chris
>

Re: [DISCUSS] Participate in the Outreachy programm?

[Lukas Ott]

Yes raising the hand in a sense of support for organisational things yes.

Am Di., 15. Feb. 2022 um 10:15 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> I totally agree,
>
> perhaps PLC4Py would actually make a good candidate for such a thing.
> I would be willing to mentor any candidates, but I would expect some of
> the work to come from the community too.
> So, do I understand you correctly? You are raising your hand? (And please
> ... if you raise your hand, only do it if you really are willing to help
> and are able to help)
>
> Chris
>
> -----Original Message-
> From: Lukas Ott 
> Sent: Dienstag, 15. Februar 2022 10:10
> To: dev@plc4x.apache.org
> Subject: Re: [DISCUSS] Participate in the Outreachy programm?
>
> Hi,
>
> +1 for participating. I still want to drive our native Python support. I
> would also be willing to mentor in the sense of organization.
>
> We had some students from Julians team once and I still think we should at
> least not stop trying to increase our diversity.
>
> Lukas
>
> Am Di., 15. Feb. 2022 um 09:54 Uhr schrieb Christofer Dutz <
> christofer.d...@c-ware.de>:
>
> > Hi all,
> >
> > the plc4x community, even being a super-awesome one, we still are a
> > pretty homogeneous bunch.
> >
> > The Outreachy program has stipends to offer for people from groups
> > under-represented in a community.
> > Chosen people get paid for working on these projects and herby get a
> > chance to enrich the communities they work for.
> >
> > Do we want to participate? If yes: Which would be tasks or task
> > bundles, that we could be handing out? Who would be willing to act as a
> mentor?
> >
> > Chris
> >
>

Re: [DISCUSS] Participate in the Outreachy programm?

[Lukas Ott]

Hi,

+1 for participating. I still want to drive our native Python support. I
would also be willing to mentor in the sense of organization.

We had some students from Julians team once and I still think we should at
least not stop trying to increase our diversity.

Lukas

Am Di., 15. Feb. 2022 um 09:54 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Hi all,
>
> the plc4x community, even being a super-awesome one, we still are a pretty
> homogeneous bunch.
>
> The Outreachy program has stipends to offer for people from groups
> under-represented in a community.
> Chosen people get paid for working on these projects and herby get a
> chance to enrich the communities they work for.
>
> Do we want to participate? If yes: Which would be tasks or task bundles,
> that we could be handing out? Who would be willing to act as a mentor?
>
> Chris
>

Re: [DISCUSS] Behaviour of a ConnectionPool?

[Lukas Ott]

+1 for sequential failing

Am Mi., 19. Jan. 2022 um 10:50 Uhr schrieb Julian Feinauer <
j.feina...@pragmaticminds.de>:

> Hi Chris,
>
> excellent question (and worth discussing).
> In the java pool there currently is NO automatic reconnection (lazy
> connection).
> I have no backup strategy there (but makes sense to have one although this
> may depend on specific situations).
>
> I currently fail one connection at a time after their specific timeout.
>
> If e.g. you set the timeout for the connection request to 1 second then
> you could easily have one connection failing but the next attempt working.
>
> So I personally would go for sequential failing when their limit is due
> but I think the other alternative is fine as well.
>
> Julian
>
> Von: Christofer Dutz 
> Datum: Mittwoch, 19. Januar 2022 um 10:21
> An: dev@plc4x.apache.org 
> Betreff: [DISCUSS] Behaviour of a ConnectionPool?
> Hi all,
>
> I'm currently working on the go connection-pool. Now while in general I
> would assume the functionality of a connection pool to be quite clearly
> defined, there still are some special cases where I want to make sure we
> consistently implement them.
>
> Right now, I'm implementing it so there is only one connection for one
> given connection string ... we can later adjust this. Reasoning here is
> that in general connections to plcs can be considered highly limited so we
> won't be going much over 2 or 3 anyway.
>
> The thing that I'm currently working on are the edge-cases. So, what
> happens if:
>
>
>   *   The connection itself fails.
>  *   Should the pool try automatically reconnecting?
>  *   If yes, should it do it as fast as possible?
>  *   Should there be an increasing back-off delay between attempts?
>  *   Should there be a maximum number of retries?
>  *   What happens to other waiting clients in case of a connection
> failure?
> *   Do all instantly get a "connection-error"?
> *   Does the connection get retried for each client in the queue
> independently?
>
> Right now, I would opt for a delay between attempts of 1s at first, the
> number doubling between each attempt and giving up after 3 times and then
> failing all waiting clients simultaneously. But I would make the limits
> configurable in the pool (reconnectInitialDelay, reconnectMaxAttempts,
> reconnectBackoffStrategy, reconnectFailureStrategy).
>
> I think if I run into any other situations where I'm unsure, I'll continue
> this thread.
>
> Chris
>

Re: [DISCUSS] Permanently move our monthly video call?

[Lukas Ott]

+1

Am Mo., 20. Dez. 2021 um 09:08 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Hi all,
>
> I would like to move our monthly call to the first Tuesday of the month
> (same time)
>
> If we leave it, I will not be participating on events that happen to be on
> even week numbers.
>
>
> Chris
>
>
> Holen Sie sich Outlook für Android
>

Re: [LAZY-CONSENSUS] Clean up in our branches?

[Lukas Ott]

+1 for cleaning up the old branches

Am Mi., 15. Dez. 2021 um 10:23 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Hi all,
>
> I have just tried to revive a not so old branch (feature/plc4net) and that
> is a LOT of work.
>
> Considering how many super-old branches we have; I would like to propose
> to clean up all branches that haven't been touched for at least a year.
> (I know one or two I stripped from this list, because they were mine and I
> want to update them or they are release branches, which I think we should
> keep)
>
> Right now, we have 48 branches.
>
> The ones I would delete are:
>
> Stale for longer than 12 months:
> feature/code-gen-julian<
> https://github.com/apache/plc4x/tree/feature/code-gen-julian> (3 years)
> too-many-open-files<
> https://github.com/apache/plc4x/tree/too-many-open-files> (2 years)
> fix-netty-usage (2
> years)
> fix-bytebuff-leaks
> (2 years)
> feature/big_integer_support_on_driver_base<
> https://github.com/apache/plc4x/tree/feature/big_integer_support_on_driver_base>
> (2 years)
> feature/optimizer-for-next-gen<
> https://github.com/apache/plc4x/tree/feature/optimizer-for-next-gen> (2
> years)
> develop-test (2 years)
> feature/link-layer-discovery-protocol<
> https://github.com/apache/plc4x/tree/feature/link-layer-discovery-protocol>
> (2 years)
> feature/profinet
> (2 years)
> feature/plc-simulator<
> https://github.com/apache/plc4x/tree/feature/plc-simulator> (2 years)
> feature/bacnet-active<
> https://github.com/apache/plc4x/tree/feature/bacnet-active> (2 years)
> bugfix/close-eventloop-after-channel<
> https://github.com/apache/plc4x/tree/bugfix/close-eventloop-after-channel>
> (16 months)
> feature/parser-tracing<
> https://github.com/apache/plc4x/tree/feature/parser-tracing> (16 months)
> issue/PLC4X-258 (13
> months)
> feature/grpc-proxy
> (13 months)
> issue/PLC4X-252 (14
> months)
>
> Newer branches, that I think might be obsolete or forgotten to be deleted
> ...
> feature/sparkplug-gateway<
> https://github.com/apache/plc4x/tree/feature/sparkplug-gateway> (9 months)
> fix/modbus_string
> (is this obsolete? What's the status on this?)
> feature/profinet2
> (I think this is merged, right?)
> feature/updated-mspec-string<
> https://github.com/apache/plc4x/tree/feature/updated-mspec-string> (I
> think this is obsolete, right?)
> issue/PLC4X-304 (I
> think this is merged, right?)
> issue/PLC4X-311 (I
> think this is merged, right?)
> s7event (I think this is
> merged, right?)
>
> So, anyone wanting to keep one of these branches ... please reply in let's
> say the next 7 days and if I don't hear back from you, I'll delete the
> listed branches.
>
> Chris
>
>

Re: [DRAFT] December PLC4X board report

[Lukas Ott]

+1

Am Do., 2. Dez. 2021 um 16:07 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> ## Description:
> The mission of the Apache PLC4X project is creating a set of libraries for
> communicating with industrial programmable logic controllers (PLCs) using a
> variety of protocols but with a shared API.
>
> ## Issues:
> There are currently no issues requiring board attention. I do see a bit of
> an
> absence of PMC coverage however regarding things cominig up on the
> mailinglists (dev and private)
>
> ## Description:
> The mission of the Apache PLC4X project is creating a set of libraries for
> communicating with industrial programmable logic controllers (PLCs) using a
> variety of protocols but with a shared API.
>
> ## Issues:
> There are currently no issues requiring board attention. I do see a bit of
> an
> absence of PMC coverage however regarding things cominig up on the
> mailinglists (dev and private)
>
> ## Membership Data:
> Apache PLC4X was founded 2019-04-17 (3 years ago)
> There are currently 19 committers and 13 PMC members in this project.
> The Committer-to-PMC ratio is roughly 5:4.
>
> Community changes, past quarter:
> - César García was added to the PMC on 2021-10-01
> - No new committers. Last addition was Thomas Frost on 2021-05-07.
>
> ## Project Activity:
> After finishing the work for the next release some members of the community
> have invested a lot of time into a complete refactoring of our codebase for
> the code-generation. This was needed in order to be able to support more
> situations needed for new drivers, but also for cleaning up stuff to make
> it
> more easily understandable for others. Others have been working on adding
> very
> cool new features to the S7 driver as well as working on the CAN-drivers.
>
> We had talks at 4 conferences:
> - ApacheCon @Home (2 Talks)
> - LF OSS-Summit (1 Talk)
> - Eclipse Con (1 Talk)
> - IoT Conference (1 Talk)
>
> ## Community Health:
> We are getting more and more reports of people using plc4x and getting bug
> reports. That's great. However contributions have been coming in from 11%
> less
> individuals compared to the previous quarter. Hopefully, in 2022 we will be
> able to do in-person events again, to strengthen the sense of community
> again.
> I am feeling as we are loosing grip of each other after 2 years of
> absolutely
> no in-person events. In the past especially these events have been helping
> with building the commnunity.
>

Re: [DISCUSS] Bring the Camel connector into the Apache Camel project?

[Lukas Ott]

+1 yes lets ask on their mailing list if they are interested.

Am Di., 28. Sept. 2021 um 18:32 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Hi all,
>
> at this year's ApacheCOn@Home I attended a talk on Apache Camel and was
> pretty impressed by their component library and Kamelet catalog.
> However PLC4X is not listed in these as the PLC4X Camel connector is not
> part of the Apache Camel project.
>
> What do you folks think about bringing the existing connector to Camel and
> then helping out over there to keep it up to date regarding PLC4X?
>
>
> Chris
>

Re: [VOTE] Apache PLC4X 0.9.0 RC2

[Lukas Ott]

+1 binding

Actions performed:
Downloaded all staged artifacts under the url specified in the release vote
email into a directory we’ll now call download-dir.
Verified the signature is correct
gpg: Korrekte Signatur von "Christofer Dutz (Apache Comitter) <
cd...@apache.org>"
Verified  the SHA512 hashes
Verified  the existence of LICENSE, NOTICE, README, RELEASE_NOTES files in
the extracted source bundle.
Verified  the content of LICENSE, NOTICE, README, RELEASE_NOTES files in
the extracted source bundle.
Run RAT externally with no surprises (log to be expected):
9 Unknown Licenses

*

Files with unapproved licenses:


apache-plc4x-0.9.0/code-generation/protocol-base-mspec/src/main/antlr4/org/apache/plc4x/plugins/codegenerator/language/mspec/expression/Expression.g4

apache-plc4x-0.9.0/code-generation/protocol-base-mspec/src/remote-resources/UNLICENSE
  apache-plc4x-0.9.0/licenses/UNLICENSE
  apache-plc4x-0.9.0/plc4go/go.sum
  apache-plc4x-0.9.0/plc4j/examples/hello-webapp/client/asconfig.json

apache-plc4x-0.9.0/plc4j/integrations/apache-calcite/src/test/resources/model.json
  apache-plc4x-0.9.0/plc4j/tools/scraper/src/test/resources/config.json
  apache-plc4x-0.9.0/sandbox/code-gen/src/main/resources/example.json
  apache-plc4x-0.9.0/sandbox/code-gen/src/main/resources/example2.json

*
Successfully built with Ubuntu 20.04
mvn -P with-go install
openjdk 11.0.11 2021-04-20
OpenJDK Runtime Environment (build 11.0.11+9-Ubuntu-0ubuntu2.20.04)

Am Sa., 18. Sept. 2021 um 18:15 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Apache PLC4X 0.9.0 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: v0.9.0
>
> Hash for the release tag: e9e9a58b057d7df827463f1262ded3a34015666a
>
>
>
> 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-1038
>
> [2] https://dist.apache.org/repos/dist/dev/plc4x/0.9.0/rc2
>
> [3] https://www.apache.org/dev/release.html#approving-a-release
>
> [4]
> https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release
>
>

Re: [VOTE] Apache PLC4X Build-Tools Site-Skin 1.1.0 RC1

[Lukas Ott]

+1 (binding)

Actions performed:
Downloaded all staged artifacts under the url specified in the release vote
email into a directory we’ll now call download-dir.
Verified the signature is correct
gpg: Korrekte Signatur von "Christofer Dutz (Apache Comitter) <
cd...@apache.org>"
Verified  the SHA512 hashes
Verified  the existence of LICENSE, NOTICE, README, RELEASE_NOTES files in
the extracted source bundle.
Verified  the content of LICENSE, NOTICE, README, RELEASE_NOTES files in
the extracted source bundle.
Run RAT externally with no surprises
Successfully built with Ubuntu 20.04 and
openjdk 11.0.11 2021-04-20
OpenJDK Runtime Environment (build 11.0.11+9-Ubuntu-0ubuntu2.20.04)

Am Mi., 8. Sept. 2021 um 20:41 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Apache PLC4X Build-Tools Site-Skink 1.1.0 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: site-skin/v1.1.0
> Hash for the release tag: be516d634bcff0c09c714e948fd5958915f47771
>
> 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-1035
> [2]
> https://dist.apache.org/repos/dist/dev/plc4x/build-tools/plc4x-site-skin/1.1.0/rc1/
> [3] https://www.apache.org/dev/release/validation.html#approving-a-release
> [4] https://plc4x.apache.org/developers/release/validation.html
>

Re: [VOTE] Apache PLC4X Build-Tools Code-Generation 1.5.0 RC1

[Lukas Ott]

+1 (binding)

Actions performed:
Downloaded all staged artifacts under the url specified in the release vote
email into a directory we’ll now call download-dir.
Verified the signature is correct
gpg: Korrekte Signatur von "Christofer Dutz (Apache Comitter) <
cd...@apache.org>"
Verified  the SHA512 hashes
Verified  the existence of LICENSE, NOTICE, README, RELEASE_NOTES files in
the extracted source bundle.
Verified  the content of LICENSE, NOTICE, README, RELEASE_NOTES files in
the extracted source bundle.
Run RAT externally with no surprises
Successfully built with Ubuntu 20.04 and
openjdk 11.0.11 2021-04-20
OpenJDK Runtime Environment (build 11.0.11+9-Ubuntu-0ubuntu2.20.04)

Am Mi., 8. Sept. 2021 um 20:17 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

>Apache PLC4X Build-Tools Code-Generation 1.5.0 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/1.5.0
>Hash for the release tag: e0f1569f74ad00af15e4a984efa0cc8ffbae85d1
>
>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-1034
>[2]
> https://dist.apache.org/repos/dist/dev/plc4x/build-tools/code-generation/1.5.0/rc1/
>[3]
> https://www.apache.org/dev/release/validation.html#approving-a-release
>[4] https://plc4x.apache.org/developers/release/validation.html
>

Re: Modbus and Plc4x

[Lukas Ott]

Hi Jayons,

Welcome to the PLC4X community mailing list. :-)

you should check-out the re-written Nifi Integration in this Pull Request:
https://github.com/apache/plc4x/pull/257

We will merge it soon into development and afterwards start a new PLC4X
release.

Regards,
otluk

Am Mi., 8. Sept. 2021 um 20:50 Uhr schrieb Jayson Hurst :

> I am new to both plc’s in general as well as Modbus. I am hoping to find
> some help on how to write to a Modbus device. I am using Apaches Nifi and
> using the Plc4xSourceProssor I have been able to read from Modbus
> registers. I have not figure out a way to write back to another device.
>
> All and any help would be greatly appreciate.
>
> Thanks
>
>

Re: [Reminder] Apache PLC4X community call August 4th 2021

[Lukas Ott]

Yeah Rainy and Cold day here in the middle of Germany - so I more for hot
tea or mulled wine , too

Am Mi., 4. Aug. 2021 um 11:37 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> (Sending again as it seems outlook decided to send personal emails)
>
> Hi Cesar,
>
> here comes:
> https://us06web.zoom.us/j/91591629512?pwd=Z3A1WTdNbXRmMnZIZ2c3SVdYaHo3QT09
>
> And @Lukas Ott<mailto:lo...@csc.com> … you mean Summer 2021 drinks, such
> as mulled wine?  ;-)
>
> Chris
>
>
> Von: Cesar Garcia 
> Gesendet: Dienstag, 3. August 2021 22:49
> An: Apache PLC4X 
> Cc: Christofer Dutz 
> Betreff: Re: [Reminder] Apache PLC4X community call August 4th 2021
>
> Hi,
>
> Please send the Zoom invitation.
>
> Bestregards
>
> El mar, 3 ago 2021 a las 16:32, Łukasz Dywicki ( <mailto:l...@code-house.org>>) escribió:
> May the August be with you,
> This message is a reminder that closest Wednesday 4th August 2021 is a
> first Wednesday of the month. This means that we have our community call
> hosted at zoom.
> Given that, next event will be held in September this is last chance to get
> summer drinks with the team!
>
> Kind regards,
> Łukasz
>
>
> --
> CEOS Automatización, C.A.
> GALPON SERVICIO INDUSTRIALES Y NAVALES FA, C.A.,
> PISO 1, OFICINA 2, AV. RAUL LEONI, SECTOR GUAMACHITO,
> FRENTE A LA ASOCIACION DE GANADEROS,BARCELONA,EDO. ANZOATEGUI
> Ing. César García
> Cel: +58 414-760.98.95
> Hotline Técnica SIEMENS: 0800 1005080
> Email: support.aan.automat...@siemens.com support.aan.automat...@siemens.com>
>
>

Re: Account Request PLC4X IoT Lab

[Lukas Ott]

Hey Yannick,

Welcome to the PLC4X Developer list.

Please first of all introduce yourself and what you are aiming for.
What are your actual needs, because most of the things do not require
access to actual hardware.
 As we can do most of the things also with our virtual drivers and then
just change the settings when actual hardware is available.

For me personally this request from Fraunhofer is kind of strange as I know
for a fact that at least 2 institutes have their own PLC hardware setup.
So you may just ping Frank Schnicke (Kaiserslautern, Fraunhofer IESE) for
instance as the BaSys Project is already collaborating with us, the Apache
PLC4X project.

Best regards,

otluk



Am Do., 15. Juli 2021 um 00:59 Uhr schrieb Mayer, Yannick <
yannick.ma...@ipa.fraunhofer.de>:

> Dear Developers,
>
> I would like to request an account for access to the PLC Hardware via the
> VPN Gateway.
>
> Thank you in advance
>
> Best regards,
>
> Yannick Mayer
>

Re: [DISCUSS] Extend our Jira Issue format to allow selection of "component" and "language"?

[Lukas Ott]

+1

Am Mi., 30. Juni 2021 um 11:25 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Hi all,
>
> as we are more and more polyglot, the question of "What language does
> this apply to?" comes up more frequently. So how about adding this as a
> mandatory field in issues?
>
> Chris
>

Re: Hi

[Lukas Ott]

Hi Purus,

Welcome to the club.

If you need help just let us know.

We will have a Virtual Meeting on 9th of June 2021, starting 7 PM Central
European Time.

Regards,
otluk

Am Fr., 4. Juni 2021 um 11:43 Uhr schrieb Purushotham Y :

> Hi,
>I would like to be part of the development activity for plc4x.
> Regards,
> Purushotham
>

Re: [DRAFT] June Board Report

[Lukas Ott]

.+1 yes let s try to keep it short and see if there is feedback fro m the
board

Christofer Dutz  schrieb am Fr., 4. Juni 2021,
10:13:

> Hi all,
>
> this time I tried keeping the details of the report as short as
> possible. Even if I liked to point out our achievements and such, I
> started thinking what I would like to know, if I was a board member and
> had to chew through the reports of 1/3 of the foundation's reports every
> month.
>
> Let's see if this form of report is appreciated ... if not we'll provide
> more details next time.
>
> Chris
>
> ---
>
>
> ## Description:
> The mission of the Apache PLC4X project is creating a set of libraries for
> communicating with industrial programmable logic controllers (PLCs) using a
> variety of protocols but with a shared API.
>
> ## Issues:
> There are no issues requiring board attention.
>
> ## Membership Data:
> Apache PLC4X was founded 2019-04-17 (2 years ago)
> There are currently 19 committers and 12 PMC members in this project.
> The Committer-to-PMC ratio is roughly 5:3.
>
> Community changes, past quarter:
> - No new PMC members. Last addition was Ben Hutcheson on 2020-11-08.
> - Thomas Frost was added as committer on 2021-05-07
>
> ## Project Activity:
> The project is currently working hard on finishing a number of new
> features and improvements that are currently being worked on in
> parallel. As soon as these are brought to an end, we're planning on
> starting the next release.
>
> ## Community Health:
> Overall activity hast increased since the last report and more and more
> folks seem to be showing up which we are helping in doing their first
> contributions. I would consider the overall health of the project very
> good.
>
> The list activity increased by 35%, number of commits went up by 25%,
> number of contributors increased by 15%
>

Re: Cleanup in our repo (and Sandbox)?

[Lukas Ott]

+1

Am Mi., 12. Mai 2021 um 13:22 Uhr schrieb Googlemail OS
:

> +1
>
> > Am 12.05.2021 um 13:20 schrieb Otto Fowler :
> >
> > +1
> >
> >> On May 12, 2021, at 04:19, Christofer Dutz 
> wrote:
> >>
> >> Hi all,
> >>
> >> I recently had a look at our Sandbox, and I'd like to clean it up a
> bit.
> >> There's quite some stuff in there, that will probably not be updated
> >> anymore.
> >>
> >> I would like to remove the StreamPipes stuff as the StreamPipes folks
> >> are releasing PLC4X connectors. No need for us to do the same. And
> >> beyond that I bet our versions are extremely outdated anyway.
> >>
> >> I would like to move the plc4c stuff out of the Sandbox and make it a
> >> top-level thing, just like plc4j and plc4go.
> >>
> >> @Julain ... what's the status of your "code-gen"? Will you ever use
> that
> >> or will you ever make id do anything?
> >>
> >> The "hello-influx-data-collection ... could that move to the PLC4j
> examples?
> >>
> >> And as the elastic license is now X-Rated we coudldn't update our
> >> Logstash integration (outside of the sandbox). I would like to remove
> >> that completely.
> >>
> >> Last not least I would like to rename the "build-utils" as it's too
> >> closely related to the build-tools and it's difficult to distinguish
> >> what you're talking about. I would like to rename the "build-utils" to
> >> "code-generation".
> >>
> >>
> >> What do you think?
> >>
> >>
> >> Chris
> >
>

Re: change Lebbing company name at adopters

[Lukas Ott]

Hello Marcus,

done (updated in the source code -> after rebuild an crtl+f5 also on the
website)

Best regards

Am Mo., 26. Apr. 2021 um 08:22 Uhr schrieb Marcus Gotthardt - Lebbing
automation & drives GmbH :

> Hello,
>
>
>
> please change the company name from
>
> Lebbing engineering & consulting GmbH
>
> to
>
> Lebbing automation & drives GmbH
>
>
>
> Please also change the company image, see attached.
>
>
>
> Mit freundlichen Grüßen · Best regards
>
> *MARCUS GOTTHARDT M.Sc.*
> In2Lutions - Team Leader
>
>
>
> Phone +49 2871 / 2412 - 364
> Mobile +49 173 6840101
> Mail marcus.gottha...@lebbing.com
>
> *Lebbing automation & drives GmbH*
> Konrad-Zuse-Straße 16 · 46397 Bocholt · Germany
> www.lebbing.com · i...@lebbing.com
> --
>
>
> * SERVICE-HOTLINE*
> E-Mail: serv...@lebbing.com
> Phone +49 2871 / 2412 - 222
>
> 
>
> Lebbing automation & drives GmbH is a German corporation, which provides
> engineering consulting services around the world. Lebbing automation &
> drives GmbH employees may travel to meet with clients or potential clients
> to negotiate contracts, gather data in order to perform consulting
> services, and/or install, service, or repair commercial or industrial
> equipment or machinery purchased from a foreign company or to train workers
> to perform such services. While at a client site, Lebbing automation &
> drives GmbH employees remain under the direction and control of Lebbing
> automation & drives GmbH, remain on the Lebbing automation & drives GmbH
> payroll, and receive no remuneration from a client. Contracts to provide
> such services do not create an employer-employee relationship between the
> client and the Lebbing automation & drives GmbH employee providing the
> service.
>
> Sitz der Gesellschaft · Registered Office: Bocholt
> Registergericht · Register Court: Coesfeld HRB 8670
> Geschäftsführer · CEO: Thomas Lebbing & Dipl.-Ing. Guido Lebbing
>

Re: PLC4x integration for Profinet

[Lukas Ott]

+1 Lukasz you are awesome!

Am Mo., 19. Apr. 2021 um 19:33 Uhr schrieb Łukasz Dywicki <
l...@code-house.org>:

> I've pushed few additional changes to features/profinet2 branch.
>
> Now it is possible to interact through PLC4X api. At least for
> identification calls.
> Sample client code:
> https://gist.github.com/splatch/f1554f0775b2b20df072f51a98ad280b
>
> Best,
> Łukasz
>
> On 19.04.2021 11:34, Łukasz Dywicki wrote:
> > Hey Mehta,
> > Our progress on profinet so far is limited just to one section - namely
> DCP.
> > Adrian Lazar (in CC) and I work together in two places:
> > https://github.com/Adito5393/plc4x/tree/feature/profinet2-setConfigs/
> > https://github.com/apache/plc4x/tree/feature/profinet2
> >
> > So far we been able to cover tagged/untaged frames, DCP broadcasts, DCP
> > answers. Next things include implementation of actual protocol
> > logic/structure mapping and attempt to interact with DCP GET/SET calls.
> > I plan to work on first parts of logic this week.
> > Please be aware that profinet protocol currently java only and rely on
> > pcap4j transport which is quite slow. It is listening at very top of
> > operating system network stack hence its not intended for control
> > scenarios. Libpcap is also known of having some issues with Windows
> > which Adrian tried to address.
> >
> > Feel free to attach your sample PCAPs/GSDML here:
> > https://issues.apache.org/jira/browse/PLC4X-8
> > We won't be able to build full profinet stack anytime soon but we'll
> > definitely be able to do data acquisition. Any help is welcome.
> >
> > Kind regards,
> > Łukasz
> >
> >
> > On 19.04.2021 10:18, Mehta Vineet wrote:
> >>
> >> I came across Apache PLC4x while researching for a way to read sensor
> data over Profinet. How far along is the integration? Any idea when it will
> be made available?
> >>
> >> Mit freundlichen Grüßen / With best regards
> >>
> >> Vineet Mehta
> >> Praktikant
> >>
> >> ruhlamat GmbH
> >> Sonnenacker 2, 99834 Gerstungen OT Marksuhl
> >> phone:
> >>
> >> +49 (0)36925 929-
> >>
> >> v.me...@ruhlamat.de
> >>
> >> fax:
> >>
> >> +49 (0)36925 929-501
> >>
> >> http://www.ruhlamat.de
> >>
> >>
> >> [https://www.ruhlamat.com/sites/all/themes/ruhlamat/logo1.png]
> >>
> >> [GF/Management: Thomas Mack, Karl Mack] - [Amtsgericht Jena/Local Court
> Jena: HRB 401145]
> >> [Firmensitz/Registered Office: Marksuhl] - [Ust-ID Nr.: DE 150382006]
> >>
> >>
> >>
>

Re: [DISCUSS] Refactor our "integration" to use a centralized "Backend" tool?

[Lukas Ott]

+1 sounds like a good way forward

Am Mi., 24. März 2021 um 16:35 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Hi all,
>
> inspired by the Sparkplug tool at Building IoT, I started working on a
> Sparkplug Edge Gateway to use legacy hardware in a Sparkplug system.
>
> While at it I noticed that probably most code needed would be the same as
> in the OPC-UA server.
>
> But I also noticed that generally it would also be like the Logstash,
> Kafka Connect,  integrations.
>
> So, I thought: How about us refactoring all of these to use a shared
> backend?
>
> With this we could keep the configuration of all our tools aligned, we
> could solve problems only once and profit in all integrations from it.
>
> What do you think?
>
> Chris
>
>

Re: PROFIBUS driver?

[Lukas Ott]

Yes, the whole idea of PLC4X is to support as much as possible.

 The limitation are ressources:
- Budget so that the developer gets paid
- Time so if you or someone else wants to develop a driver do not hesitate
to ask and just do it
- Access to devices and / or manuals for the specific protocol is missing
(so it makes it difficult for the developer to build and test a driver)

Cheers,
otluk

Am Di., 16. März 2021 um 06:57 Uhr schrieb Andreas Vogler
:

> Hi,
> Is it planned to implement a PROFIBUS driver?
> Regards,
> Andreas
>

Re: add lebbing to adopters section

[Lukas Ott]

Hello Marcus,

sure - thank you and welcome to the PLC4X community.

As soon as the build server build our website - your company will be added
to the list.

Best regards
Lukas

Am Do., 11. März 2021 um 08:56 Uhr schrieb Marcus Gotthardt - Lebbing
engineering & consulting GmbH :

> Hello,
>
>
>
> please can you add our company to the adopters section?
>
>
>
> *Name*:
>
> Lebbing engineering & consulting GmbH
>
>
>
> *URL*:
>
> https://www.lebbing.com/
>
> https://in2lutions.com/
>
>
>
> The second link represents the department/team of lebbing, which is using
> plc4x
>
>
>
> *Market*:
>
> Automation / Drives / Industry 4.0
>
>
>
> *Description*:
>
> We used PLC4X to developed a solution to synchronize data between PLCs and
> customers systems. Our Solution is used for new products as well as for
> industry 4.0 upgrades to older machines.
>
> ---
>
>
>
> Mit freundlichen Grüßen / With best regards
>
>
> *i. A. M.Sc. MARCUS GOTTHARDT *In2Lutions - Team Leader
>
> *Lebbing engineering & consulting GmbH*
> Jagenberg Group
>
> Konrad-Zuse-Strasse 16
> 46397 Bocholt, Germany
>
> Tel.: +49 2871 / 2412 - 364
> Fax: +49 2871 / 2412 - 100
> Mobil: +49 173 6840101
> E-Mail: marcus.gottha...@lebbing.com
> Web: www.lebbing.com
> --
>
>
> *SERVICE-HOTLINE *
> E-Mail: serv...@lebbing.com
> Tel.: +49 2871 / 2412 - 222
>
>
>
>
>
>
> Lebbing Engineering & Consulting GmbH ("LEC") is a German corporation,
> which provides engineering consulting services around the world. LEC
> employees may travel to meet with clients or potential clients to negotiate
> contracts, gather data in order to perform consulting services, and/or
> install, service, or repair commercial or industrial equipment or machinery
> purchased from a foreign company or to train workers to perform such
> services. While at a client site, LEC employees remain under the direction
> and control of LEC, remain on the LEC payroll, and receive no
> remuneration from a client. Contracts to provide such services do not
> create an employer-employee relationship between the client and the LEC
> employee providing the service.
>
> Lebbing engineering & consulting GmbH - Geschäftsführer / CEO: Thomas
> Lebbing & Dipl.-Ing. Guido Lebbing - Registergericht / Register Court:
> Coesfeld - HRB 8670 - USt-ID. DE812549901
>
>

Re: AW: Source Time of PLC Value?

[Lukas Ott]

+1 to Lukasz

Am Mo., 8. März 2021 um 14:09 Uhr schrieb Łukasz Dywicki <
l...@code-house.org>:

> Hold on for a second.
>
> Making options pushed over connection string is a long term recipe for
> disaster. Apache Camel is a prime example of what could happen if you
> starting with configuration with URIs and dynamic parameters. Most of
> components distinguish producer (writer) and consumer (receiver)
> options, most complicated components ended up with 40+ options settable
> via URI. Having a mix of PlcValues which are timestamped and 'qualified'
> and not will complicate encoding logic (how we push above info to IEC
> encoder/handler or decorate it?) and how we keep custom types compatible
> with above?
>
> That is why I rather opt for extending API in a way which does not force
> existing drivers to do anything. When any of community members,
> regardless if its developer or user, will find it necessary to be ported
> in another driver, she or he have right to do it. It is not only yours
> duty to keep all drivers and languages the same.
>
> Speaking of which I am also not concerned about making all languages
> having the same functionality as languages tend to offer different
> options which might be hard to be ported. Lets stick to basics which are
> same (connection strings, field definitions, read/write/subscribe
> syntax) and let various runtime lead their own ways toward implementation.
>
> Key point is simple - we won't be able to maintain all languages
> equally. We should not hold moving ie. go or java forward because we
> can't port new API functionality to C/Python/C#/whenever. If there is
> someone who *does* use above in production and *wish* to have new API
> parts then that person/organization duty is to do it.
>
> Best,
> Łukasz
>
>
> On 08.03.2021 13:17, Christofer Dutz wrote:
> > Hi,
> >
> > I must admit that I would be in favor of keeping it as simple as
> possible (max age in the connection string) and to implement more of the
> missing parts in plc4x (like the subscription simulation layer) and hereby
> getting the drivers we have a bit more aligned, than to implement more and
> more special API features, that only one or two drivers support. Cause this
> way we're running away form the project-promise of running a given program
> at any type of PLC with any protocol.
> >
> > I mean ... at the current velocity the project is underway, I wouldn't
> really want to add a new MetaData layer that probably in the end only 1-2
> people will be implementing and which we must not only find out how to fill
> with life in the first place, but also port to all of our supported
> languages.
> >
> > If someone's willing to bring in some serious man/womenpower, I'm fine
> with that ... or we add it to some wish-list for future extensions. But I
> wouldn't want to start something like this right now.
> >
> > Chris
> >
> >
> >
> >
> >
> > -Ursprüngliche Nachricht-
> > Von: Łukasz Dywicki 
> > Gesendet: Montag, 8. März 2021 13:07
> > An: dev@plc4x.apache.org
> > Betreff: Re: Source Time of PLC Value?
> >
> > I have not mentioned metadata term in my answer, so credits for mining
> it API go to you. :-)
> >
> > Now since you brought it I remember that JDBC has a "result set
> metadata". That might be thing we still miss. The result code is most
> important and available instantly, other information is supplemental and
> can be read additionally.
> >
> >
> > Best,
> > Łukasz
> >
> > On 08.03.2021 13:01, Ben Hutcheson wrote:
> >> +1 for Łukasz‘s metadata approach, it would avoid having to create
> >> duplicate PLcValue classes and give us a lot of flexibility in the
> future.
> >>
> >> On Mon, Mar 8, 2021 at 5:14 AM Christofer Dutz
> >> 
> >> wrote:
> >>
> >>> Hi all,
> >>>
> >>> sorry for being late to the party ... KNX is currently consuming all
> >>> my cycles.
> >>> Just wanted to add my thoughts to the discussion.
> >>>
> >>> Initially I thought about adding this sort of information to the API,
> >>> but then I thought that we have so little protocols supporting this
> >>> sort of concept that blowing up every PLCValue with this time
> >>> information just would waste CPU time and Memory.
> >>>
> >>> When it comes to simulating subscriptions by polling in the
> >>> background, I thought it would be a valid solution to provide a
> >>> default age a value can have in the cache and to make it possible to
> >>> override this in the connection string options. If a value is too old,
> a return code of:
> >>> STALE_DATA could be returned.
> >>>
> >>> Also, we do have an option of adding an additional set of PlcValue
> types.
> >>> If a driver supports this quality-of-service type of data, we could
> >>> return special versions of PlcValues, that have these properties?
> >>>
> >>> This way we don't have to waste the CPU time and Memory for protocols
> >>> that don't support this concept (We could even implement the methods
> >>> on the default PlvValues to simply return some constants to the
> >>> 

Re: [DISCUSS] Minimum sampling interval on change of state subscription

[Lukas Ott]

Hi,

concerning limiting the data rate is a really valid point as the newer PLCs
are doing exactly that (e.g. they have a Data collector and Data Processor
included - and we did exactly that as well with some IIoT sensors that we
collected and processed the data directly on the microcontroller) - as the
older ones are not build for sending data - it would be quite helpful to
configure a timer but one second may be too long as default value

Best,
Lukas

Am Mo., 8. März 2021 um 12:49 Uhr schrieb Ben Hutcheson <
ben.hut...@gmail.com>:

> Hi,
>
> If we were to let the server control a minimum rate for change of state
> subscriptions then we could overload the client.
>
> I think allowing a value of 0 would be a good idea in case you really do
> want to capture every change even if it is incredibly fast, but still
> defaulting to 1s.
>
> Ben
>
> On Mon, Mar 8, 2021 at 5:20 AM Christofer Dutz 
> wrote:
>
> > Hi all,
> >
> > yeah ... I wanted to say something to that too:
> >
> > Change of State shouldn't have a sampling interval (Perhaps a min
> interval
> > to prevent flooding an application with too many updates)
> > The use case seems a bit like a polling use case and we have a separate
> > set of subscription properties for that. For polling, there should be a
> > sampling interval and that's even included in the API.
> >
> > If we are "simulating" a change of state functionality on a protocol,
> that
> > doesn't support this (like S7, Modbus, ...) we should have a generic
> > property to control this sampling interval throughout all PLC4X drivers.
> As
> > I recall we currently don't have this subscription simulation layer ...
> not
> > yet ...
> >
> > Chris
> >
> >
> > -Ursprüngliche Nachricht-
> > Von: Łukasz Dywicki 
> > Gesendet: Montag, 8. März 2021 11:08
> > An: dev@plc4x.apache.org
> > Betreff: Re: [DISCUSS] Minimum sampling interval on change of state
> > subscription
> >
> > Hey Ben,
> > I began writing this answer shortly after you sent your mail but
> > eventually left it for a day or two to thing it through.
> > Looking at API I believe we have three major cases:
> > - polling/push interval
> > - change of value
> > - every value
> >
> > Looking at above change of value should not require any interval cause it
> > should be determined by device we subscribe to. It knows for sure that
> > value changed and should push an update to us. Same applies to event
> field.
> > For cases where we can specify update interval the first (cyclic) option
> > is intended. I know very little of OPC UA so above might be not entirely
> > valid in context of it. The real question is shall we fit OPC into our
> API
> > or our API into OPC.
> >
> > Looking closer at cyclic subscriptions we don't have a clear indication
> of
> > who does the time handling. Is it device (or server) who post updates
> back
> > to us at given frequency? Or we poll it given interval? How our API
> caller
> > will know who controls time?
> >
> > To sum all this - I would say that case you have seems to fit more into
> > cyclic subscription than change of state.
> >
> > Best,
> > Łukasz
> >
> >
> > On 06.03.2021 13:06, Ben Hutcheson wrote:
> > > Looking at the change of state subscription interface there's no
> > > explanation or way to modify the Duration parameter which defaults to
> > > one second. This is used in OPC UA as a minimum reporting time so will
> > > never report back faster than 1 second.
> > >
> > > What's everyone's thoughts on adding this as an optional parameter?
> > >
> > > I thought about changing the default but I think 1 second is a good
> > > value for it.
> > > I also think an absolute minimum value should be allowed of 5 or 10ms.
> > >
> > >  * Adds a new field to the to be constructed request which should be
> > > updated as soon as
> > >  * a value changes in the PLC.
> > >  *
> > >  * @param name   alias of the field.
> > >  * @param fieldQuery field query string for accessing the field.
> > >  * @return builder.
> > >  */
> > > PlcSubscriptionRequest.Builder addChangeOfStateField(String name,
> > > String fieldQuery);
> > >
> >
>

Re: DF1 protocol ...cant find documentation

[Lukas Ott]

Hi Gaurav,

Welcome to the list :-),

Yes it really is supported. Here you ll find some more details:
https://plc4x.apache.org/developers/code-gen/protocol/df1.html

The best way to get started you can find here:
https://plc4x.apache.org/users/getting-started/plc4j.html
to understand more read here:
https://plc4x.apache.org/users/getting-started/general-concepts.html

For release 0.6 you ll find the java code here:
https://github.com/apache/plc4x/blob/rel/0.6/protocols/df1/src/main/java/org/apache/plc4x/protocol/df1/Df1Protocol.java


Example code you ll find here:
https://github.com/apache/plc4x/tree/develop/plc4j/examples

Currently not sure if we ported DF1 to release 0.8

Cheers,
otluk

Am Fr., 19. Feb. 2021 um 03:41 Uhr schrieb Gaurav P :

> Hi Team ,
> I am new to PLC4x , trying to integrate with DF1
> but cant find any documentation 
> https://plc4x.apache.org/users/protocols/df1.html
>
> is it really supported? if yes where can I get documentation  and an
> example code
> --
> B*e * the *Ch*ange
>

Re: [DISCUSS] Start Implementing turnkey-examples?

[Lukas Ott]

+1 for that - as we could use this approach also for other Drivers

Am Mi., 17. Feb. 2021 um 08:48 Uhr schrieb Christofer Dutz <
christofer.d...@c-ware.de>:

> Hi all,
>
> you probably noticed, I started a call for help on soncial media to test
> the latest auto-discovery for KNX in Go.
> Turns out that I have heard back exactly 0 times.
>
> I did ask the one or the other, why they didn't respond and it seems
> "checkout our repo and then run this command" seems to high of a barrier.
>
> So I started thinking: Probably for Linux folks this isn't a huge barrier
> as they are used to getting their hands dirty.
> Windows people are used to downloading an installer or an Exe and running
> that.
>
> This got me thinking: Wouldn't it be good to start creating Go Windows Exe
> files which use what we want to test (Especially regarding auto-discovery
> and browsing).
> But in addition to this, I would like to make the Exes automatically
> capture the traffic (filtered to only the packets that are of interest) and
> to prepare feedback packages consisting of log-information and a pcap file.
> Cause I am a bit worried that "Could you create a wireshark capture of the
> traffic" is too complicated too :-/
>
> We could then start a "Help us by testing these on your systems" page
> where they can download the Exe files.
>
> What do you think?
>
>
> Chris
>

Re: Additional Drivers for GOLang ?

[Lukas Ott]

Hello Wolfgang,

First of all welcome to the list :-).

We indeed want to bring other drivers to GO. Just one mail before we were
looking for developers who are willing to do that :-) so feel free to start
developing. We are happy to help.
So concrete timeline no - roadmap yes - priority yes - ressources not yet -

For the Modbus-Simulator
I personally like: https://www.openplcproject.com/

here is a Docker based Modbus simulator:
https://github.com/NModbus/NModbus.DeviceSimulator

Regards,
otluk


Am Do., 11. Feb. 2021 um 10:17 Uhr schrieb Wolfgang Huse <
wolfgang.h...@nutanix.com>:

> Hello,
> as I try to integrate PLC4x into an Golang-Framework I would like to know
> when additional drivers like S7 or OPCUA will be available in GO ? Is there
> any timeline ?
>
> For the meantime, anybody knows a good Modbus-Simulator for Mac or Docker?
>
> Regards,
> Wolfgang Huse
>