BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [455]':
Check console output at "https://builds.apache.org/job/PLC4X/job/PLC4X/job/develop/455/";>PLC4X/PLC4X/develop
[develop] [455]"
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [456]':
Check console output at "https://builds.apache.org/job/PLC4X/job/PLC4X/job/develop/456/";>PLC4X/PLC4X/develop
[develop] [456]"
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 | Li
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
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 comb
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [457]':
Check console output at "https://builds.apache.org/job/PLC4X/job/PLC4X/job/develop/457/";>PLC4X/PLC4X/develop
[develop] [457]"
Hi all,
so while I was working on the Kafka Sink I sort of started thinking if such a
thing is a good idea to have at all.
A Kafka system would be able to provide a vast stream of data that would have
to be routed to a PLCs.
On the one side, I haven't seen a single usecase of someone writing to
Hi Chris,
here a few thoughts:
*I haven't seen a single use case of someone writing to a PLC with PLC4X *
=> This sounds similar to most IoT MQTT scenarios I see today. The main
challenge is to get data out of machines to analyze and use it. Writing
back (e.g. to control the systems) is the secon
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [458]':
Check console output at "https://builds.apache.org/job/PLC4X/job/PLC4X/job/develop/458/";>PLC4X/PLC4X/develop
[develop] [458]"
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [460]':
Check console output at "https://builds.apache.org/job/PLC4X/job/PLC4X/job/develop/460/";>PLC4X/PLC4X/develop
[develop] [460]"
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [461]':
Check console output at "https://builds.apache.org/job/PLC4X/job/PLC4X/job/develop/461/";>PLC4X/PLC4X/develop
[develop] [461]"
Hi,
I agree with what you say.
We use Kafka and plc4x exactly the same way in prod :)
Prepaid Björn can also comment here as he also consists a Kafka based plc
communication layer..
Julian
Von meinem Mobiltelefon gesendet
Ursprüngliche Nachricht
Betreff: Re: [KAFKA] Refacto
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [462]':
Check console output at "https://builds.apache.org/job/PLC4X/job/PLC4X/job/develop/462/";>PLC4X/PLC4X/develop
[develop] [462]"
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [463]':
Check console output at "https://builds.apache.org/job/PLC4X/job/PLC4X/job/develop/463/";>PLC4X/PLC4X/develop
[develop] [463]"
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [464]':
Check console output at "https://builds.apache.org/job/PLC4X/job/PLC4X/job/develop/464/";>PLC4X/PLC4X/develop
[develop] [464]"
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [465]':
Check console output at "https://builds.apache.org/job/PLC4X/job/PLC4X/job/develop/465/";>PLC4X/PLC4X/develop
[develop] [465]"
Hi,
I am currently investigating some of the more recent build failures (As they
were quite erratic).
I updated our Jenkins node and did some cleaning up, but still we have random
failures.
A quick check of our disk usage however showed that we are using quite a bit of
space on our disk.
We cu
17 matches
Mail list logo
