Generate JARs to try out the examples

[Kai Wähner]

Hello,

I would like to generate the JARs to try out the examples.

*./mvnw install -P build-executable-jars -DskipTests*

shows

*WARNING: The requested profile "build-executable-jars" could not be
activated because it does not exist.*

The reason is probably that this profile is not defined in the main
pom.xml, but in the folder *plc4x/plc4j/examples*

Can someone please let me know the correct Maven command to generate the
JAR files so that I can create the examples? Thank you.

Best regards,
Kai Waehner

Re: Generate JARs to try out the examples

[Kai Wähner]

Thanks. I wasn't aware you can use more than one profile. I can confirm
that the built now works and generates the JARs.

Can you also point me to some documentation or example how to send some
hello world messages using a hello world driver? I assume I have to use
DummyDriver somehow?

⇒   java -cp
/Users/kai.waehner/git-projects/plc4x/plc4j/examples/hello-world-plc4x/target/plc4j-hello-world-plc4x-0.5.0-SNAPSHOT-jar-with-dependencies.jar
org.apache.plc4x.java.examples.helloplc4x.HelloPlc4x
Missing required options: connection-string, field-addresses
usage: HelloPlc4x
--connection-stringConnection String
--field-addresses  Field Addresses (Space separated).


Looks like there is no complete getting started example available
somewhere? After I have it running, I am happy to write a more detailed
summary and create a PR for the readme file.



On Fri, Jul 19, 2019 at 5:47 PM Julian Feinauer <
j.feina...@pragmaticminds.de> wrote:

> Hi Kai,
>
> I think you need the profile "with-java" (cannot check it right now).
> So you would need to add "-Pwith-java" to the mvn cl string.
>
> Julian
>
> Von meinem Mobiltelefon gesendet
>
>
>  Ursprüngliche Nachricht --------
> Betreff: Generate JARs to try out the examples
> Von: Kai Wähner
> An: dev@plc4x.apache.org
> Cc:
>
> Hello,
>
> I would like to generate the JARs to try out the examples.
>
> *./mvnw install -P build-executable-jars -DskipTests*
>
> shows
>
> *WARNING: The requested profile "build-executable-jars" could not be
> activated because it does not exist.*
>
> The reason is probably that this profile is not defined in the main
> pom.xml, but in the folder *plc4x/plc4j/examples*
>
> Can someone please let me know the correct Maven command to generate the
> JAR files so that I can create the examples? Thank you.
>
> Best regards,
> Kai Waehner
>

Re: Generate JARs to try out the examples

[Kai Wähner]

No, I don't have a PLC.

But from your response I understand that you need one to use PLC4X even for
Hello World examples.

I assume there is no "free / open test generator" as all of these protocols
are proprietary and not using any standards (this is the main motivation
for the PLC4X project).

I saw FactoryIO (https://factoryio.com/editions/) in one of the PLC4X
videos on Youtube. I could use it and its S7 emulator for a hello world
with the 30 day trial. Is this the best / easiest option if you don't have
any hardware?


On Fri, Jul 19, 2019 at 8:40 PM Julian Feinauer <
j.feina...@pragmaticminds.de> wrote:

> Hey Kai,
>
> Indeed our documentation could be a bit better :)
> So you do not have a real plc to check against?
> The hello plc4x example is made for connecting to a Siemens S7 device, I
> think.
> So you can give it a IP and a field address of a Siemens S7 plc and it
> will fetch the results.
> Regarding the demo driver...i have to check (when by daughter finally
> decides to sleep... :) and respond then back to you.
>
> Julian
>
> Von meinem Mobiltelefon gesendet
>
>
>  Ursprüngliche Nachricht ----
> Betreff: Re: Generate JARs to try out the examples
> Von: Kai Wähner
> An: Julian Feinauer
> Cc: dev@plc4x.apache.org
>
> Thanks. I wasn't aware you can use more than one profile. I can confirm
> that the built now works and generates the JARs.
>
> Can you also point me to some documentation or example how to send some
> hello world messages using a hello world driver? I assume I have to use
> DummyDriver somehow?
>
> ⇒   java -cp
> /Users/kai.waehner/git-projects/plc4x/plc4j/examples/hello-world-plc4x/target/plc4j-hello-world-plc4x-0.5.0-SNAPSHOT-jar-with-dependencies.jar
> org.apache.plc4x.java.examples.helloplc4x.HelloPlc4x
> Missing required options: connection-string, field-addresses
> usage: HelloPlc4x
> --connection-stringConnection String
> --field-addresses  Field Addresses (Space separated).
>
>
> Looks like there is no complete getting started example available
> somewhere? After I have it running, I am happy to write a more detailed
> summary and create a PR for the readme file.
>
>
>
> On Fri, Jul 19, 2019 at 5:47 PM Julian Feinauer <
> j.feina...@pragmaticminds.de> wrote:
>
>> Hi Kai,
>>
>> I think you need the profile "with-java" (cannot check it right now).
>> So you would need to add "-Pwith-java" to the mvn cl string.
>>
>> Julian
>>
>> Von meinem Mobiltelefon gesendet
>>
>>
>>  Ursprüngliche Nachricht 
>> Betreff: Generate JARs to try out the examples
>> Von: Kai Wähner
>> An: dev@plc4x.apache.org
>> Cc:
>>
>> Hello,
>>
>> I would like to generate the JARs to try out the examples.
>>
>> *./mvnw install -P build-executable-jars -DskipTests*
>>
>> shows
>>
>> *WARNING: The requested profile "build-executable-jars" could not be
>> activated because it does not exist.*
>>
>> The reason is probably that this profile is not defined in the main
>> pom.xml, but in the folder *plc4x/plc4j/examples*
>>
>> Can someone please let me know the correct Maven command to generate the
>> JAR files so that I can create the examples? Thank you.
>>
>> Best regards,
>> Kai Waehner
>>
>

Re: Generate JARs to try out the examples

[Kai Wähner]

Thanks for the details. Sounds perfect.

I have a call with Uwe in 15min anyway. I will then ask Chris for access.

My testing is just for technical evaluation and learning (so also no high
volume), so no specific use case. Having said this, I see a lot of added
value and demand at several projects. I am very sure the AHA effect will
show up quickly in these projects.



On Mon, Jul 22, 2019 at 1:18 PM Julian Feinauer <
j.feina...@pragmaticminds.de> wrote:

> Hey Kai,
>
>
>
> we have Hardware in the codecentric IoT Lab and you can request access to
> it (via Chris Dutz).
>
> We also have a driver for OPC UA where there exist multiple free tools.
>
>
>
> But, yes, the basic idea is to map all those proprietary protocols to a
> nice JDBC Like interface, so the most “AHA” you get out of using it against
> a real one.
>
>
>
> If you could / would elaborate a bit about your use cases or your ideas
> you can of course ask Chris for an access to the codecentric IoT Lab and
> test against real PLCs via remote.
>
>
>
> Julian
>
>
>
> *Von: *Kai Wähner 
> *Antworten an: *"megachu...@gmail.com" 
> *Datum: *Montag, 22. Juli 2019 um 13:13
> *An: *Julian Feinauer 
> *Cc: *"dev@plc4x.apache.org" 
> *Betreff: *Re: Generate JARs to try out the examples
>
>
>
> No, I don't have a PLC.
>
>
>
> But from your response I understand that you need one to use PLC4X even
> for Hello World examples.
>
>
>
> I assume there is no "free / open test generator" as all of these
> protocols are proprietary and not using any standards (this is the main
> motivation for the PLC4X project).
>
>
>
> I saw FactoryIO (https://factoryio.com/editions/) in one of the PLC4X
> videos on Youtube. I could use it and its S7 emulator for a hello world
> with the 30 day trial. Is this the best / easiest option if you don't have
> any hardware?
>
>
>
>
>
> On Fri, Jul 19, 2019 at 8:40 PM Julian Feinauer <
> j.feina...@pragmaticminds.de> wrote:
>
> Hey Kai,
>
>
>
> Indeed our documentation could be a bit better :)
>
> So you do not have a real plc to check against?
>
> The hello plc4x example is made for connecting to a Siemens S7 device, I
> think.
>
> So you can give it a IP and a field address of a Siemens S7 plc and it
> will fetch the results.
>
> Regarding the demo driver...i have to check (when by daughter finally
> decides to sleep... :) and respond then back to you.
>
>
>
> Julian
>
> Von meinem Mobiltelefon gesendet
>
>
>
>  Ursprüngliche Nachricht 
> Betreff: Re: Generate JARs to try out the examples
> Von: Kai Wähner
> An: Julian Feinauer
> Cc: dev@plc4x.apache.org
>
> Thanks. I wasn't aware you can use more than one profile. I can confirm
> that the built now works and generates the JARs.
>
>
>
> Can you also point me to some documentation or example how to send some
> hello world messages using a hello world driver? I assume I have to use
> DummyDriver somehow?
>
>
>
> ⇒   java -cp
> /Users/kai.waehner/git-projects/plc4x/plc4j/examples/hello-world-plc4x/target/plc4j-hello-world-plc4x-0.5.0-SNAPSHOT-jar-with-dependencies.jar
> org.apache.plc4x.java.examples.helloplc4x.HelloPlc4x
> Missing required options: connection-string, field-addresses
> usage: HelloPlc4x
> --connection-stringConnection String
> --field-addresses  Field Addresses (Space separated).
>
>
>
>
>
> Looks like there is no complete getting started example available
> somewhere? After I have it running, I am happy to write a more detailed
> summary and create a PR for the readme file.
>
>
>
>
>
>
>
> On Fri, Jul 19, 2019 at 5:47 PM Julian Feinauer <
> j.feina...@pragmaticminds.de> wrote:
>
> Hi Kai,
>
>
>
> I think you need the profile "with-java" (cannot check it right now).
>
> So you would need to add "-Pwith-java" to the mvn cl string.
>
>
>
> Julian
>
> Von meinem Mobiltelefon gesendet
>
>
>
>  Ursprüngliche Nachricht 
> Betreff: Generate JARs to try out the examples
> Von: Kai Wähner
> An: dev@plc4x.apache.org
> Cc:
>
> Hello,
>
> I would like to generate the JARs to try out the examples.
>
> *./mvnw install -P build-executable-jars -DskipTests*
>
> shows
>
> *WARNING: The requested profile "build-executable-jars" could not be
> activated because it does not exist.*
>
> The reason is probably that this profile is not defined in the main
> pom.xml, but in the folder *plc4x/plc4j/examples*
>
> Can someone please let me know the correct Maven command to generate the
> JAR files so that I can create the examples? Thank you.
>
> Best regards,
> Kai Waehner
>
>

Re: Generate JARs to try out the examples

[Kai Wähner]

Thanks, Matthias.

This sounds great for a first start. I will also sync with Chris next week
about the Codecentric IoT lab.

This should be sufficient for getting started.

Kai

On Wed, Jul 24, 2019 at 11:14 AM Strljic, Matthias Milan <
matthias.strl...@isw.uni-stuttgart.de> wrote:

> Hi Kai,
>
>
>
> for testing you could use the DummyDriver, our TestLab (as Julian
> mentioned) or u can use a public OPC UA  example server like the
>
> " opcua:tcp://opcua.demo-this.com:51210/UA/SampleServer" but there be
> aware that those are not from us. This are just public OPC UA servers to
> demonstrate OPC UA.
>
>
>
> Here a nice List of public servers
> https://github.com/node-opcua/node-opcua/wiki/publicly-available-OPC-UA-Servers-and-Clients
> .
>
>
>
> You can find a simple example of writing, reading and subscribing of
> different data types at a manual test example at the ManualPLC4XOpcua.java
> <https://github.com/apache/plc4x/blob/develop/plc4j/drivers/opcua/src/test/java/org/apache/plc4x/java/opcua/ManualPLC4XOpcua.java>
> class.
>
> I hope this helps you 😊
>
>
>
> GL and have fun!
>
>
>
> Best wishes
>
> Matthias Strljic, M.Sc.
>
>
>
> Universität Stuttgart
>
> Institut für Steuerungstechnik der Werkzeugmaschinen und
> Fertigungseinrichtungen (ISW)
>
>
>
> Seidenstraße 36
>
> 70174 Stuttgart
>
> GERMANY
>
>
>
> Tel: +49 711 685-84530
>
> Fax: +49 711 685-74530
>
>
>
> E-Mail: matthias.strl...@isw.uni-stuttgart.de
>
> Web: http://www.isw.uni-stuttgart.de
>
>
>
> -Original Message-
> From: Kai Wähner 
> Sent: Monday, July 22, 2019 1:13 PM
> To: Julian Feinauer 
> Cc: dev@plc4x.apache.org
> Subject: Re: Generate JARs to try out the examples
>
>
>
> No, I don't have a PLC.
>
>
>
> But from your response I understand that you need one to use PLC4X even
> for Hello World examples.
>
>
>
> I assume there is no "free / open test generator" as all of these
> protocols are proprietary and not using any standards (this is the main
> motivation for the PLC4X project).
>
>
>
> I saw FactoryIO (https://factoryio.com/editions/) in one of the PLC4X
> videos on Youtube. I could use it and its S7 emulator for a hello world
> with the 30 day trial. Is this the best / easiest option if you don't have
> any hardware?
>
>
>
>
>
> On Fri, Jul 19, 2019 at 8:40 PM Julian Feinauer <
> j.feina...@pragmaticminds.de> wrote:
>
>
>
> > Hey Kai,
>
> >
>
> > Indeed our documentation could be a bit better :) So you do not have a
>
> > real plc to check against?
>
> > The hello plc4x example is made for connecting to a Siemens S7 device,
>
> > I think.
>
> > So you can give it a IP and a field address of a Siemens S7 plc and it
>
> > will fetch the results.
>
> > Regarding the demo driver...i have to check (when by daughter finally
>
> > decides to sleep... :) and respond then back to you.
>
> >
>
> > Julian
>
> >
>
> > Von meinem Mobiltelefon gesendet
>
> >
>
> >
>
> >  Ursprüngliche Nachricht 
>
> > Betreff: Re: Generate JARs to try out the examples
>
> > Von: Kai Wähner
>
> > An: Julian Feinauer
>
> > Cc: dev@plc4x.apache.org
>
> >
>
> > Thanks. I wasn't aware you can use more than one profile. I can
>
> > confirm that the built now works and generates the JARs.
>
> >
>
> > Can you also point me to some documentation or example how to send
>
> > some hello world messages using a hello world driver? I assume I have
>
> > to use DummyDriver somehow?
>
> >
>
> > ⇒   java -cp
>
> > /Users/kai.waehner/git-projects/plc4x/plc4j/examples/hello-world-plc4x
>
> > /target/plc4j-hello-world-plc4x-0.5.0-SNAPSHOT-jar-with-dependencies.j
>
> > ar org.apache.plc4x.java.examples.helloplc4x.HelloPlc4x
>
> > Missing required options: connection-string, field-addresses
>
> > usage: HelloPlc4x
>
> > --connection-stringConnection String
>
> > --field-addresses  Field Addresses (Space separated).
>
> >
>
> >
>
> > Looks like there is no complete getting started example available
>
> > somewhere? After I have it running, I am happy to write a more
>
> > detailed summary and create a PR for the readme file.
>
> >
>
> >
>
> >
>
> > On Fri, Jul 19, 2019 at 5:47 PM Julian Feinauer <
>
> > j.feina...@pragmaticminds.de> wrote:
>
> >
>
> &g

Re: [KAFKA] Refactoring the Kafka Connect plugin?

[Kai Wähner]

Hi Chris,

great that you will work on the connector.

I am not deep technical, but if you need guidance from Kafka Connect
experts, I can connect you to a Confluent colleague to can help with best
practices for building the connector.

For example, we have implemented a wildcard option into our MQTT Connector
to map MQTT Topics to Kafka Topics in a more flexible way (e.g. 1000s of
cars from different MQTT Topics can be routed into 1 Kafka Topic). This
might also be interesting for this connector as you expect to various PLCs.

This guide might also help:
https://www.confluent.io/wp-content/uploads/Verification-Guide-Confluent-Platform-Connectors-Integrations.pdf



On Wed, Jul 31, 2019 at 4:39 PM Christofer Dutz 
wrote:

> Hi all,
>
> I am currently planning on cleaning up the Kafka Connect adapter a little
> as this was implemented as part of a proof of concept and is still I a
> state I wouldn’t use in production ;-)
> But a lot has happened since then and I’m planning on making it a really
> usable tool in the next few days.
>
> A lot has changed since we created the integration module QT3 2018 and I
> would like to refactor it to use the Scraper for the heavy lifting.
>
> Currently a user has to provide a parameter “query” which contains a
> comma-separated list of connection-strings with appended address. This is
> purely unmanageable.
>
> I would like to make it configurable via JSON or Yaml file.
>
> I think it would make sense to define groups of fields that are collected
> on one device at an equal rate. So it’s pretty similar to the scraper
> example, however I would like to not specify the source in the job, but the
> other way around.
> When specifying the “sources” I would also provide which jobs should run
> on a given collection.
> As the connector was initially showcased in a scenario where data had to
> be collected on a big number of PLCs with equal specs,
> I think this is the probably most important use-case and in this it is
> also probably more common to add new devices to collect standard data on
> than the other way around.
>
> Also should we provide the means to also set per connection to which
> kafka-topic the data should be sent to.
> We could provide the means to set a default and make it optional however.
> When posting to a topic we also need to provide means for partitioning, so
> I would provide sources with an optional “name”.
> Each message would not only have the data requested, but also the
> source-url, source-name and the job-name with a timestamp.
>
> So I guess it would look something like this:
>
> #
> 
> # Licensed to the Apache Software Foundation (ASF) under one
> # or more contributor license agreements.  See the NOTICE file
> # distributed with this work for additional information
> # regarding copyright ownership.  The ASF licenses this file
> # to you under the Apache License, Version 2.0 (the
> # "License"); you may not use this file except in compliance
> # with the License.  You may obtain a copy of the License at
> #
> #http://www.apache.org/licenses/LICENSE-2.0
> #
> # Unless required by applicable law or agreed to in writing,
> # software distributed under the License is distributed on an
> # "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
> # KIND, either express or implied.  See the License for the
> # specific language governing permissions and limitations
> # under the License.
> #
> 
> ---
> # Defaults used throughout all collections
> defaults:
>   # If not specified, all data goes to this topic (optional)
>   default-topic: some/default
>
> # Defines connections to PLCs
> sources:
>   # Connection to a S7 device
>  - name: machineA
> # PLC4X connection URL
> url: s7://1.2.3.4/1/1
> jobs:
>   # Just references the job "s7-dashboard". All data will be published
> to the default topic
>   - name: s7-dashboard
>   # References the job "s7-heartbeat", however is configures the
> output to go to the topic "heartbeat"
>   - name: s7-heartbeat
> topic: heartbeat
>
>   # Connection to a second S7 device
>   - name: machineB
> url: s7://10.20.30.40/1/1
> # Sets the default topic for this connection. All jobs data will go to
> "heartbeat"
> topic: heartbeat
> jobs:
>   - s7-heartbeat
>
>   # Connection to a Beckhoff device
>   - name: machineC
> url: ads://1.2.3.4.5.6
> topic: heartbeat
> jobs:
>   - ads-heartbeat
>
> # Defines what should be collected how often
> jobs:
>   # Defines a job to collect a set of fields on s7 devices every 500ms
>   - name: s7-dashboard
> scrapeRate: 500
> fields:
>   # The key will be used in the Kafka message to identify this field,
> the value here contains the PLC4X address
>   inputPreasure: %DB.DB1.4:INT
>   outputPreasure: %Q1:BYTE
>   temperature: %I3:INT
>
>   # 

Re: Next PLC4X Meetup on 22.08.2019 in the codecentric Office in Frankfurt

[Kai Wähner]

I also blocked my calendar and will join...

As mentioned before, am not really a good coder, but will create some nice
content in the next few months about *PLC4X + Kafka* and start "promoting"
this combination (blog, slides, meetup talks). Happy to chat about use
cases, ideas, challenges for combining these two technologies.

I see huge demand for this combination in IoT and integration projects.

Looking forward to meet the PLC4X team in person in Frankfurt.


On Tue, Aug 13, 2019 at 2:15 PM Julian Feinauer <
j.feina...@pragmaticminds.de> wrote:

> Hi Lukas,
>
> awesome that you will be there!
> We didn’t manage to meet in Stuttgart in-between.
> But perhaps we can organize some common cars to go to Ffm as we are quite
> few people from Stuttgart, or?
>
> Julian
>
> Am 13.08.19, 11:04 schrieb "Ott, Lukas" :
>
> Hi Chris,
>
> Call me in + 1 Developer.
>
> - My Focus on documentation and learning to setup.
>
>
> Lukas Ott
> Associate Consultant Business
> Industry Consulting Manufacturing - North and Central Europe
> DXC Technology
>
> Hewlett-Packard-Str. 1, 61352 Bad Homburg, Germany
> M: +49.173.705.2298 | lo...@dxc.com | LinkedIn | Twitter Me
> Notice of temporary leave: 1 September 2019 – 29 September 2019, 1
> October 2019 – 4 October 2019
>
> DXC Technology • This is a PRIVATE message. If you are not the
> intended recipient, please delete without copying and kindly advise us by
> e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail
> shall not operate to bind DXC to any order or other contract unless
> pursuant to explicit written agreement or government initiative expressly
> permitting the use of e-mail for such purpose• Registered Office:
> Hewlett-Packard-Str. 1, 61352 Bad Homburg, Germany• Board of Directors:
> Michael Eberhardt (Chairman), Chairman of the Supervisory Board: William L.
> Deckelman • Registered in Germany: HRB 11307
>
> -Original Message-
> From: Christofer Dutz 
> Sent: Montag, 12. August 2019 17:03
> To: dev@plc4x.apache.org
> Subject: Next PLC4X Meetup on 22.08.2019 in the codecentric Office in
> Frankfurt
>
> Hi all,
>
> I would like to announce the next PLC4X meetup, which is planned on
> 22.08.2019.
> We will be hosting the meetup in the codecentric office in Frankfurt
> where the carpet still has a big stain from our graduation party ;-)
> codecentric AG Kreuznacher Str. 30
> 60486 Frankfurt
> (Near the train-station Frankfurt West)
>
> As some of you would be coming from further away, we’ll start a little
> earlier than with normal meetups.
> It’s planned that we start at 14:00 (2 PM).
>
> We have the following topics, we would like to talk and potentially
> work on:
>
>   *   The new Code Generation
>   *   API Changes to the PLC4X API
>
> If you have any other topics, please come forward and mention them.
>
> Looking forward to some awesome coding and perhaps a beverage or two
> ;-)
>
> Chris
>
> DXC Technology Deutschland GmbH: Hewlett-Packard-Str. 1, 61352 Bad
> Homburg, Germany - Board of Directors: Claus Schuenemann (Chairman),
> Michael Eberhardt - Registered in Bad Homburg: HRB 14227.
> DXC Technology Company -- This message is transmitted to you by or on
> behalf of DXC Technology Company or one of its affiliates.  It is intended
> exclusively for the addressee.  The substance of this message, along with
> any attachments, may contain proprietary, confidential or privileged
> information or information that is otherwise legally exempt from
> disclosure. Any unauthorized review, use, disclosure or distribution is
> prohibited. If you are not the intended recipient of this message, you are
> not authorized to read, print, retain, copy or disseminate any part of this
> message. If you have received this message in error, please destroy and
> delete all copies and notify the sender by return e-mail. Regardless of
> content, this e-mail shall not operate to bind DXC Technology Company or
> any of its affiliates to any order or other contract unless pursuant to
> explicit written agreement or government initiative expressly permitting
> the use of e-mail for such purpose.
>
>
>

Re: [KAFKA] Refactoring the Kafka Connect plugin?

[Kai Wähner]

s.active=%I0.2:BOOL
>
> jobs.ads-heartbeat.scrapeRate=1000
> jobs.ads-heartbeat.active=Main.running
>
>
> Chris
>
>
>
> Am 01.08.19, 15:46 schrieb "Christofer Dutz" <
> christofer.d...@c-ware.de>:
>
> Hi Kai,
>
> that document is exactly the one I'm currently using.
> What I'm currently working on is updating the current plugin to
> not schedule and handle the connection stuff manually, but use the scraper
> component of PLC4X.
> Also is the current configuration not production ready and I'll be
> working on to make it more easily usable.
>
> But it will definitely not hurt to have some Kafka Pro have a look
> at what we did and propose improvements. After all we want the thing to be
> rock-solid :-)
>
> Chris
>
>
>
> Am 31.07.19, 17:03 schrieb "Kai Wähner" :
>
> Hi Chris,
>
> great that you will work on the connector.
>
> I am not deep technical, but if you need guidance from Kafka
> Connect
> experts, I can connect you to a Confluent colleague to can
> help with best
> practices for building the connector.
>
> For example, we have implemented a wildcard option into our
> MQTT Connector
> to map MQTT Topics to Kafka Topics in a more flexible way
> (e.g. 1000s of
> cars from different MQTT Topics can be routed into 1 Kafka
> Topic). This
> might also be interesting for this connector as you expect to
> various PLCs.
>
> This guide might also help:
>
> https://www.confluent.io/wp-content/uploads/Verification-Guide-Confluent-Platform-Connectors-Integrations.pdf
>
>
>
> On Wed, Jul 31, 2019 at 4:39 PM Christofer Dutz <
> christofer.d...@c-ware.de>
> wrote:
>
> > Hi all,
> >
> > I am currently planning on cleaning up the Kafka Connect
> adapter a little
> > as this was implemented as part of a proof of concept and is
> still I a
> > state I wouldn’t use in production ;-)
> > But a lot has happened since then and I’m planning on making
> it a really
> > usable tool in the next few days.
> >
> > A lot has changed since we created the integration module
> QT3 2018 and I
> > would like to refactor it to use the Scraper for the heavy
> lifting.
> >
> > Currently a user has to provide a parameter “query” which
> contains a
> > comma-separated list of connection-strings with appended
> address. This is
> > purely unmanageable.
> >
> > I would like to make it configurable via JSON or Yaml file.
> >
> > I think it would make sense to define groups of fields that
> are collected
> > on one device at an equal rate. So it’s pretty similar to
> the scraper
> > example, however I would like to not specify the source in
> the job, but the
> > other way around.
> > When specifying the “sources” I would also provide which
> jobs should run
> > on a given collection.
> > As the connector was initially showcased in a scenario where
> data had to
> > be collected on a big number of PLCs with equal specs,
> > I think this is the probably most important use-case and in
> this it is
> > also probably more common to add new devices to collect
> standard data on
> > than the other way around.
> >
> > Also should we provide the means to also set per connection
> to which
> > kafka-topic the data should be sent to.
> > We could provide the means to set a default and make it
> optional however.
> > When posting to a topic we also need to provide means for
> partitioning, so
> > I would provide sources with an optional “name”.
> > Each message would not only have the data requested, but
> also the
> > source-url, source-name and the job-name with a timestamp.
> >
> > So I guess it would look something like this:
> >
> > #
> >
> 
> > # Licensed to the Apache Software Foundation (ASF) under one
> > 

Re: Next PLC4X Meetup on 22.08.2019 in the codecentric Office in Frankfurt

[Kai Wähner]

Good morning,

so we „officially“ begin at 2pm, right?
I arrive ~12:30pm in Frankfurt.

Looking forward to meet you today...

Kai

On Sun 18. Aug 2019 at 19:22, Bjoern Hoeper  wrote:

> Hi everyone,
> I sadly cannot participate because I am still on holiday on Thursday.
> I wish all of you a productive meeting and I am really sad not seeing you
> all again.
> Greetings from Hallig Hooge
> Björn
>
> Outlook für Android herunterladen
>
> 
> From: Christofer Dutz 
> Sent: Sunday, August 18, 2019 4:32:35 PM
> To: dev@plc4x.apache.org 
> Subject: Re: Next PLC4X Meetup on 22.08.2019 in the codecentric Office in
> Frankfurt
>
> Sure that's possible.
>
> I'll be there starting 9:00-9:15 :-)
>
> Chris
>
> Holen Sie sich Outlook für Android
>
> 
> From: Strljic, Matthias Milan 
> Sent: Sunday, August 18, 2019 3:23:25 PM
> To: dev@plc4x.apache.org 
> Subject: AW: Next PLC4X Meetup on 22.08.2019 in the codecentric Office in
> Frankfurt
>
> Hi Chris,
>
>
> for the meetup would it be possible to start even earlier at you place?
>
> Because for me it would not make a big difference if we start at 10- 10:30
> and so we would have more time together ❤
>
>
> Greetings
>
> Mathi
>
> 
> Von: Christofer Dutz 
> Gesendet: Mittwoch, 14. August 2019 10:38:54
> An: dev@plc4x.apache.org
> Betreff: Re: Next PLC4X Meetup on 22.08.2019 in the codecentric Office in
> Frankfurt
>
> Hi Markus,
>
> I feel really sorry for you  NOT! :-P
>
> Enjoy.
>
> Hope you're planning in ApacheCon EU in Berlin in October ...
>
> Chris
>
> Am 14.08.19, 10:27 schrieb "Markus Sommer" :
>
> Hi all,
>
> I would have liked to get to know everyone.
>
> Unfortunately I can't attend the meeting because I'm lying on the
> beach in Greece at the moment.
>
> Best regards
>
> Markus
>
> Freundliche Grüße
>
> Markus Sommer
> Geschäftsführer
>
> isb innovative software businesses GmbH
> Otto-Lilienthal-Strasse 2
> D - 88046 Friedrichshafen
>
> Tel.:+49 (0) 7541 3834-14
> Mob:  +49 (0) 171 537 8437
> Fax: +49 (0) 7541 3834-20
> E-Mail: som...@isb-fn.de
> Web: www.isb-fn.de
>
> Geschäftsführer: Markus Sommer, Thomas Zeler
> Sitz: Friedrichshafen
>
> Registergericht: Amtsgericht Ulm HRB-Nr. 631624
> Important Note: This e-mail and any attachments are confidential, may
> contain trade secrets and may well also be legally privileged or otherwise
> protected from disclosure. If you have received it in error, you are on
> notice of its status.
> Please notify us immediately by reply e-mail and then delete his
> e-mail and any attachment from your system. If you are not the intended
> recipient please understand that you must not copy this e-mail or any
> attachments or disclose the contents to any other person. Thank you.
>
>
> -Ursprüngliche Nachricht-
> Von: Julian Feinauer 
> Gesendet: Dienstag, 13. August 2019 11:15
> An: dev@plc4x.apache.org; Lukas Ott 
> Betreff: Re: Next PLC4X Meetup on 22.08.2019 in the codecentric Office
> in Frankfurt
>
> Hi Lukas,
>
> awesome that you will be there!
> We didn’t manage to meet in Stuttgart in-between.
> But perhaps we can organize some common cars to go to Ffm as we are
> quite few people from Stuttgart, or?
>
> Julian
>
> Am 13.08.19, 11:04 schrieb "Ott, Lukas" :
>
> Hi Chris,
>
> Call me in + 1 Developer.
>
> - My Focus on documentation and learning to setup.
>
>
> Lukas Ott
> Associate Consultant Business
> Industry Consulting Manufacturing - North and Central Europe
> DXC Technology
>
> Hewlett-Packard-Str. 1, 61352 Bad Homburg, Germany
> 
> M: +49.173.705.2298 | lo...@dxc.com | LinkedIn | Twitter Me
> Notice of temporary leave: 1 September 2019 – 29 September 2019, 1
> October 2019 – 4 October 2019
>
> DXC Technology • This is a PRIVATE message. If you are not the
> intended recipient, please delete without copying and kindly advise us by
> e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail
> shall not operate to bind DXC to any order or other contract unless
> pursuant to explicit written agreement or government initiative expressly
> permitting the use of e-mail for such purpose• Registered Office: 
> Hewlett-Packard-Str.
> 1, 61352 Bad Homburg, Germany
> •
> Board of Directors: Michael Eberhardt (Chairman), Chairman of the
> Supervisory Board: William L. Deckelman • Registered in Germany: HRB 11307
>
> -Original Message-
> From: Christofer Dutz 
> Sent: Montag, 

Re: Next PLC4X Meetup on 22.08.2019 in the codecentric Office in Frankfurt

[Kai Wähner]

Alright... Will arrive at Codecentric office ~12:45. Cu there.

Kai

On Thu 22. Aug 2019 at 08:08, Julian Feinauer 
wrote:

> Hey Kai,
>
> We start at around 10 am. But I think others will join all day... So feel
> free to join whenever you like :)
>
> Julian
>
> Von meinem Mobiltelefon gesendet
>
>
>  Ursprüngliche Nachricht 
> Betreff: Re: Next PLC4X Meetup on 22.08.2019 in the codecentric Office in
> Frankfurt
> Von: Kai Wähner
> An: dev@plc4x.apache.org
> Cc:
>
> Good morning,
>
> so we „officially“ begin at 2pm, right?
> I arrive ~12:30pm in Frankfurt.
>
> Looking forward to meet you today...
>
> Kai
>
> On Sun 18. Aug 2019 at 19:22, Bjoern Hoeper  wrote:
>
> > Hi everyone,
> > I sadly cannot participate because I am still on holiday on Thursday.
> > I wish all of you a productive meeting and I am really sad not seeing you
> > all again.
> > Greetings from Hallig Hooge
> > Björn
> >
> > Outlook für Android<https://aka.ms/ghei36> herunterladen
> >
> > 
> > From: Christofer Dutz 
> > Sent: Sunday, August 18, 2019 4:32:35 PM
> > To: dev@plc4x.apache.org 
> > Subject: Re: Next PLC4X Meetup on 22.08.2019 in the codecentric Office in
> > Frankfurt
> >
> > Sure that's possible.
> >
> > I'll be there starting 9:00-9:15 :-)
> >
> > Chris
> >
> > Holen Sie sich Outlook für Android<https://aka.ms/ghei36>
> >
> > 
> > From: Strljic, Matthias Milan 
> > Sent: Sunday, August 18, 2019 3:23:25 PM
> > To: dev@plc4x.apache.org 
> > Subject: AW: Next PLC4X Meetup on 22.08.2019 in the codecentric Office in
> > Frankfurt
> >
> > Hi Chris,
> >
> >
> > for the meetup would it be possible to start even earlier at you place?
> >
> > Because for me it would not make a big difference if we start at 10-
> 10:30
> > and so we would have more time together ❤
> >
> >
> > Greetings
> >
> > Mathi
> >
> > 
> > Von: Christofer Dutz 
> > Gesendet: Mittwoch, 14. August 2019 10:38:54
> > An: dev@plc4x.apache.org
> > Betreff: Re: Next PLC4X Meetup on 22.08.2019 in the codecentric Office in
> > Frankfurt
> >
> > Hi Markus,
> >
> > I feel really sorry for you  NOT! :-P
> >
> > Enjoy.
> >
> > Hope you're planning in ApacheCon EU in Berlin in October ...
> >
> > Chris
> >
> > Am 14.08.19, 10:27 schrieb "Markus Sommer" :
> >
> > Hi all,
> >
> > I would have liked to get to know everyone.
> >
> > Unfortunately I can't attend the meeting because I'm lying on the
> > beach in Greece at the moment.
> >
> > Best regards
> >
> > Markus
> >
>
> <https://www.google.com/maps/search/Otto-Lilienthal-Strasse+2+%0D%0A+D+-+88046+Friedrichshafen?entry=gmail&source=g>>
> Freundliche Grüße
> >
> > Markus Sommer
> > Geschäftsführer
> >
> > isb innovative software businesses GmbH
> > Otto-Lilienthal-Strasse 2
> <https://www.google.com/maps/search/Otto-Lilienthal-Strasse+2+%0D%0A+D+-+88046+Friedrichshafen?entry=gmail&source=g>
> > D - 88046 Friedrichshafen
> <https://www.google.com/maps/search/Otto-Lilienthal-Strasse+2+%0D%0A+D+-+88046+Friedrichshafen?entry=gmail&source=g>
> >
> > Tel.:+49 (0) 7541 3834-14
> > Mob:  +49 (0) 171 537 8437
> > Fax: +49 (0) 7541 3834-20
> > E-Mail: som...@isb-fn.de
> > Web: www.isb-fn.de<http://www.isb-fn.de>
> >
> > Geschäftsführer: Markus Sommer, Thomas Zeler
> > Sitz: Friedrichshafen
> >
> > Registergericht: Amtsgericht Ulm HRB-Nr. 631624
> > Important Note: This e-mail and any attachments are confidential, may
> > contain trade secrets and may well also be legally privileged or
> otherwise
> > protected from disclosure. If you have received it in error, you are on
> > notice of its status.
> > Please notify us immediately by reply e-mail and then delete his
> > e-mail and any attachment from your system. If you are not the intended
> > recipient please understand that you must not copy this e-mail or any
> > attachments or disclose the contents to any other person. Thank you.
> >
> >
> > -Ursprüngliche Nachricht-
> > Von: Julian Feinauer 
> > Gesendet: Dienstag, 13. August 2019 11:15
> > An: 

Re: [DISCUSS] Integrate CRUNCH into PLC4X

[Kai Wähner]

*"So in the mid- or longterm I agree that it would be nice to rename PLC4X
to something like "Industrial IoT and Industrie 4.0 we kick your ass" or
something with subprojects like - CRUNCH as processing pipeline - PLC4X as
connection - hopefully some more to come"*

>From an external perspective, I am not sure how much value it brings if the
PLC4X project is "blown up" with several additional components.

I like the simplicity of it solving a specific problem: "*It is our goal to
create a set of libraries, that allow unified access to any type of PLC*".

PLC4X already integrates with many other "processing frameworks" like
Kafka, Nifi, Logstash. If you add "processing and hopefully some more"
components in the future, the project will grow, including its features,
but also complexity. Not sure if the "Hadoop approach" is the better way
here, too. You can pick and choose what you need (HDFS, Parquet, Avro,
Hive, Impala, many more), but they are independent of each other for
releases, bug fixes, dependencies. This has all its trade-offs, of course.

Personally, I would like to see PLC4X improving in the things it was build
for, including more protocol implementations (and increases maturity), more
language support beyond Java, and other (small) enhancements. My point of
view is not 100% objective as I focus on Kafka, of course.
But I am not sure if it is counterintuitive to provide features like data
processing which are already solved by the frameworks PLC4X integrates with
(Kafka, Nifi, et al). For example, with Kafka Connect and the PLC4X
connector, you can do data processing (filtering etc) out-of-the-box,
already (without the need for another engine / app; just use Connect SMT,
https://docs.confluent.io/current/connect/transforms/index.html).

Just my two cents (from a Kafka enthusiast)...

On Mon, Sep 2, 2019 at 11:25 AM Julian Feinauer <
j.feina...@pragmaticminds.de> wrote:

> Hi Matthias,
>
> I agree with you view on things.
> In fact CRUNCH will be something like the "scraper on steroids" as it has
> tons of other more useful features.
> So I guess lots of users (Kafka Adapter, ES Adapter, ...) will love it.
>
> Regarding the Structure, I agree with you. It is not uncommon to have
> subprojects in a project and thus a PMC is not a project but a comitee
> managing one or more projects AFAIR.
> So in the mid- or longterm I agree that it would be nice to rename PLC4X
> to something like "Industrial IoT and Industrie 4.0 we kick your ass" or
> something with subprojects like
> - CRUNCH as processing pipeline
> - PLC4X as connection
> - hopefully some more to come
>
> But first step would be to start with one further subproject which would
> be crunch.
>
> Julian
>
> Am 29.08.19, 14:47 schrieb "Strljic, Matthias Milan" <
> matthias.strl...@isw.uni-stuttgart.de>:
>
> Hi all,
>
> Is there a way to encapsulate all components in the project in kind of
> sub projects?
> Because we will have at the end PLC4X which is a "lib"-attempt of a
> jdbc-Driver for PLC in different languages.
> This uses a separated project which has a template-based code
> generation to built efficient the de-/serialization layer.
> On top of PLC4X we have different sub-projects like the scraper,
> Connectors, Bridge-Servers,  platform independent Thrift-Server... etc.
> But those are not really modules of PLC4X, they are more modules
> specific for PLC4J and will stay those modules, or?
>
> Because I would like to see CRUNCH as a more advanced Scraper
> extension. If the code and doc quality is ok. But now it is also for me not
> that clear if I should vote for it or not. Then in my opinion is not
> directly a part of "PLC4X the JDBC driver API"-thing. As the Scraper,
> Thrift, code gen and the connectors it is more a nice tool but it is
> directly connected with our community and our PLC4X eco system.
> So is there a "Apache way" to manage/advertise/maintain some of those
> elements as a kind of sub project?
>
> Sry if I sound there I bit silly. I have there not that much
> experience in managing OS projects.
>
> Greetings
> Matthias Strljic, M.Sc.
>
> Universität Stuttgart
> Institut für Steuerungstechnik der Werkzeugmaschinen und
> Fertigungseinrichtungen (ISW)
>
> Seidenstraße 36
> 70174 Stuttgart
> GERMANY
>
> Tel: +49 711 685-84530
> Fax: +49 711 685-74530
>
> E-Mail: matthias.strl...@isw.uni-stuttgart.de
> Web: http://www.isw.uni-stuttgart.de
>
> -Ursprüngliche Nachricht-
> Von: Julian Feinauer 
> Gesendet: Saturday, August 24, 2019 6:23 PM
> An: dev@plc4x.apache.org
> Betreff: AW: [DISCUSS] Integrate CRUNCH into PLC4X
>
> Hi Otto,
>
> Thanks for your comment.
> Indeed I agree with all of your points and I think this is also one
> reason why I'd like to integrate it.
> It's better to develop software in such a community where you
> challenge each other.
>
> So if others see it also positive I agree to

Re: [DISCUSS] Rename CRUNCH to something different

[Kai Wähner]

I would vote for something like Niclas proposed. Much clearer than having
yet another product / component name...

For instance, PLC4X DSP, PLC4X Signal Processor, or something what clearly
describes in one or two words / shortcuts what the component does.

See Kafka and its ecosystem: Kafka Connect, Kafka Streams, Confluent Schema
Registry, Confluent Rest Proxy, Confluent Control Center, etc...

Kai

On Sun, Sep 15, 2019 at 9:05 AM Julian Feinauer <
j.feina...@pragmaticminds.de> wrote:

> Hi,
>
> I was thinking about naming and came up with ideas like...
>
> - trace4j
> - dsp4j (digital signal processing, that is)
> - pluse (as we detect pulses and stuff)
> - oscilloscope <-- I quite like that, it fits quite well as we really look
> into signals
>
> What are thoughts on those?
>
> J
>
> Am 08.09.19, 22:38 schrieb "Niclas Hedhman" :
>
> peanut gallery; I would recommend a descriptive name, in format of
> "PLC4X
> Abc", rather than a stand-alone name. Somewhere in the future, you may
> have
> a dozen of these and one wouldn't know where to start looking.
>
> Cheers
> Niclas
>
> On Mon, Sep 9, 2019 at 4:51 AM Julian Feinauer <
> j.feina...@pragmaticminds.de>
> wrote:
>
> > Hi all,
> >
> > I just discussed (off-list) with Justin the next steps needed.
> > They are
> >
> > * fill out software grant (pm)
> > * Start IP clearance vote on incubator list (JF)
> > * Gather ICLA from all contributors of CRUNCH
> >
> > Parallel I’d like to start a discuss on how we should call it as
> PLC4X
> > subproject.
> >
> > Any ideas or suggestions?
> >
> > Julian
> >
>
>
> --
> Niclas Hedhman, Software Developer
> http://polygene.apache.org - New Energy for Java
>
>
>

Re: [DISCUSS] Rename CRUNCH to something different

[Kai Wähner]

> To: dev@plc4x.apache.org 
> Subject: Re: [DISCUSS] Rename CRUNCH to something different
>
> Hey,
>
> As i'm electrical engineer i like the name oscilloscope.
> But full ack to Kai, name should be clearer.
> Furthermore i like Kai's suggestion PLC4X DSP as it is
> short and clear what Crunch does ... processing and analyzing digitalized
> data. Maybe we could also call it PLC4X MSP for 'Mixed Signal Processing'
> or any other artifical acronym.
>
> Best
> Tim
>
> Am 15.09.19, 18:20 schrieb "Kai Wähner" <
> megachu...@gmail.com>:
>
> I would vote for something like Niclas proposed. Much
> clearer than having
> yet another product / component name...
>
> For instance, PLC4X DSP, PLC4X Signal Processor, or
> something what clearly
> describes in one or two words / shortcuts what the
> component does.
>
> See Kafka and its ecosystem: Kafka Connect, Kafka
> Streams, Confluent Schema
> Registry, Confluent Rest Proxy, Confluent Control
> Center, etc...
>
> Kai
>
> On Sun, Sep 15, 2019 at 9:05 AM Julian Feinauer <
> j.feina...@pragmaticminds.de> wrote:
>
> > Hi,
> >
> > I was thinking about naming and came up with ideas
> like...
> >
> > - trace4j
> > - dsp4j (digital signal processing, that is)
> > - pluse (as we detect pulses and stuff)
> > - oscilloscope <-- I quite like that, it fits quite
> well as we really look
> > into signals
> >
> > What are thoughts on those?
> >
> > J
> >
> > Am 08.09.19, 22:38 schrieb "Niclas Hedhman" <
> nic...@hedhman.org>:
> >
> > peanut gallery; I would recommend a descriptive
> name, in format of
> > "PLC4X
> > Abc", rather than a stand-alone name. Somewhere
> in the future, you may
> > have
> > a dozen of these and one wouldn't know where to
> start looking.
> >
> > Cheers
> > Niclas
> >
> > On Mon, Sep 9, 2019 at 4:51 AM Julian Feinauer <
> > j.feina...@pragmaticminds.de>
> > wrote:
> >
> > > Hi all,
> > >
> > > I just discussed (off-list) with Justin the
> next steps needed.
> > > They are
> > >
> > > * fill out software grant (pm)
> > > * Start IP clearance vote on incubator list
> (JF)
> > > * Gather ICLA from all contributors of CRUNCH
> > >
> > > Parallel I’d like to start a discuss on how we
> should call it as
> > PLC4X
> > > subproject.
> > >
> > > Any ideas or suggestions?
> > >
> > > Julian
> > >
> >
> >
> > --
> > Niclas Hedhman, Software Developer
> > http://polygene.apache.org - New Energy for Java
> >
> >
> >
>
>
>
>
>
>
>
>
>
>
>

Re: [DISCUSS] Rename CRUNCH to something different

[Kai Wähner]

I am also curious how a 4J project complements a 4X project?

I only need the Java part (for Kafka), but it also seems confusing to me if
a project with a vision of Java, Python and other supporting languages now
adds dedicated 4J projects (which the Python developer cannot really use)?

Did you think about this topic?

Kai

On Thu 19. Sep 2019 at 09:20, Julian Feinauer 
wrote:

> Although I'm a bit sad that discussion coools down I like Björn s proposal
> of something like
>
> Analyze4j
>
> Probably traceAnalyzer4j would even be more accurate. And it is already
> coupled to plc4x at as subproject.
>
> Julian
> 
> From: Bjoern Hoeper 
> Sent: Tuesday, September 17, 2019 4:49:32 AM
> To: dev@plc4x.apache.org 
> Subject: AW: [DISCUSS] Rename CRUNCH to something different
>
> Hi Everyone,
> as Chris already mentioned a logic analyzer is quite a nice tool and in
> (loose) analogy to plc4x I would propose something like "Analyze4PLC" Or
> "PLCAnalyze4J" it would keep the logic in the naming convention somehow and
> make clear what the intention of the framework is.
> Just my 50 cents.
> Best,
> Björn
>
> -Ursprüngliche Nachricht-
> Von: Julian Feinauer 
> Gesendet: Dienstag, 17. September 2019 00:03
> An: dev@plc4x.apache.org; megachu...@gmail.com
> Betreff: Re: [DISCUSS] Rename CRUNCH to something different
>
> Hi Kai,
>
> I understand your point. But I dislike to call things like "process" or
> "compute" as these are such overused words. Windows calc does compute,
> Mainframes do compute, Hadoop nodes do compute...
>
> Target audience is PLC4X users so something between IT and OT. And in
> fact, as the lib is quite a bit specialiced and think its reasonable to
> have people look at the docs first : )
>
> But, I mean we are (as Chris pointed out) still in the process of consent
> building, so its good to get so many opinions here.
>
> Julian
>
> Am 16.09.19, 13:43 schrieb "Kai Wähner" :
>
> The question is "who should understand what the component does" when he
> reads the component name (without any further descriptions)?
>
> If it is software developers, then they will have no idea what
> "osciloscope" means (I don't either). I only understand simple words
> like
> Connect, Process, Store, etc. :-)
>
> Even if osciloscope is more accurate, the question is who is the
> audience
> for potential users of PLC4X and its sub-components.
>
> Kai
>
> On Mon, Sep 16, 2019 at 10:14 AM Christofer Dutz <
> christofer.d...@c-ware.de>
> wrote:
>
> > Hi Julian,
> >
> > A common pattern of modern ASF duels seems to be writing longer and
> longer
> > emails till someone finally gives up ;-)
> >
> > Chris
> >
> >
> > Am 16.09.19, 18:51 schrieb "Julian Feinauer" <
> > j.feina...@pragmaticminds.de>:
> >
> > Hi,
> >
> > ist not that i disagree with you, I just don’t agree : D
> > Logic Analyzer sounds weird for me (but I'm also not so used to
> that).
> >
> > So we should go on discussing.. and if no consensus is found we
> meet
> > somewhere, two men, nobody else, no guns (and no bears!). Knifes are
> > probably okay (have to check the Apache Policy on consensus finding
> > again...) : )
> >
> > Julian
> >
> > Am 16.09.19, 09:45 schrieb "Christofer Dutz" <
> > christofer.d...@c-ware.de>:
> >
> > Hi julian,
> >
> > Well  coming back to your explanation:
> > I would never use an oszyloscope to analyze such plc signals
> they
> > have a far to low frequency for oszylloscope analysis. Especially an
> > oszylloscope requires things to have a frequency and you couldn't
> detect
> > simple low frequent logic level shifts.
> > Thinking about how I usually analyze signals in the IoT
> space, I
> > always use my Logic-Analyzer which is much more suited for such
> tasks.
> > So if we would stick to your reasoning, I would prefer "logic
> > analyzer" instead of "oszylloscope".
> >
> > Chris
> >
> >
> > Am 16.09.19, 17:37 schrieb "Julian Feinauer" <
> > j.feina...@pragmaticminds.de>:
> >
> > Hi,
> >
> > although I agre

Re: [PLC-Simulator/Frontend] Opinions on Tech stack?

[Kai Wähner]

I was just smiling a little bit while reading this because I remembered my
presentations almost 10 years ago about such discussions...

Just for reference (you don't need to agree with my categorization), and
today you think much more about "Vue/Angular/React/JS-Framework of the
week". I discussed the following ~10 years ago:

[image: image.png]

http://www.kai-waehner.de/blog/2010/12/30/categorization-of-web-frameworks-in-the-java-environment/
https://www.slideshare.net/KaiWaehner/categorization-of-java-web-frameworks-jsf-wicket-tapestry-gwt-zk-flex-javafx-grails-lift-spring-mvc-roo


*From my experience, I would clearly vote for your option 1) => *
*Simple handwritten html+javascript (Jquery?) served by the Spring Boot
backend (easy to start with but might get a bit messy over time)*

If the UI gets a lot of traction and evolves over time, some refactoring
(and the inclusion of a web framework) is probably reasonable. But *I would
definitely start with a "quick and dirty" keep it simple solution which
just works. A web framework makes it much more complex from the beginning.*
I had a project with GWT... GWT was awesome, but also the biggest pain in
the project becasue most people of the team did not understand the
framework in detail... And the UI is not they main part of PLC4X.

Start simple, if it works well and gets traction, plan a good web
architecture without pressure in parallel and release it in another major
release of this Apache project. I guess most other Apache projects started
similarly (even today most UIs are not really nice).

Best regards,
Kai Waehner


Just my two cents from my experience.




On Tue, Oct 15, 2019 at 1:53 PM Tim Kläsener 
wrote:

> Hi everyone again,
>
> We're currently looking into creating a frontend for interacting with
> the PLC Simulator, i.e. having an administration interface for
> changing properties/input/output and, if time allows, some fancier
> visual representations of the devices the PLCs control.
>
> As for the REST service, I've so far developed it with Spring Boot
> which should be okay from a licensing perspective (let me know if you
> have any concerns), now I'm looking into different options for
> developing the frontend:
>
> 1. Simple handwritten html+javascript (Jquery?) served by the Spring
> Boot backend (easy to start with but might get a bit messy over time)
> 2. Separate single page application using
> Vue/Angular/React/JS-Framework of the week (better separation of
> concerns but requires JS-toolset)
> 3. Java-based web UI framework like Vaadin or Royale
>
> Any other suggestions or reasons to choose one option over the others?
>
> Cheers,
>
> Tim
>