BUILD-STABLE: Job 'PLC4X/PLC4X/develop [develop] [285]':
Is back to normal.
Lukas,
for me the situation is more like this:
I have been working on PLC4X for 3,5 years full time now. If I sum up the paid
gigs I got for the Java stuff in that time, I would probably be a beggar if
codecentric hadn't been paying my bills. I am working on Go, because I am paid
for it becau
On Thu, 2021-03-11 at 19:13 +0100, Łukasz Dywicki wrote:
> [snip] ..
> While I do appreciate work made to bring all (C/Python/C#?) languages
> under Apache PLC4X umbrella I also do see that sometimes they are
> being
> {snip]
> Isn't it a time to make sure that C/C#/Python can still compile with
Hey Matthias and Chris,
I agree with you about complexity and alignment. I am far from trying to
cover each and every case. At the same time I am aware that making thing
fine in first run is crucial to avoid major changes afterwards. That's
also why I did throw pseudo-code upfront to brainstorm. Le
nalim2 commented on pull request #227:
URL: https://github.com/apache/plc4x/pull/227#issuecomment-796902458
Seems good to me
This is an automated message from the Apache Git Service.
To respond to the message, please log on t
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [284]':
Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/284/";>PLC4X/PLC4X/develop
[develop] [284]"
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [283]':
Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/283/";>PLC4X/PLC4X/develop
[develop] [283]"
Hi,
I had the same problem with PLC4X and also with plain Milo. One OPC UA Server
didn’t allow to set a time on write and another OPC UA Server didn’t work
without setting a time :-) … so I think it is a good idea to make this
configurable …. there are so many options available in OPC UA…
Btw:
Quick ref for the Commit:
https://github.com/apache/plc4x/commit/d45f748b08d6c083a22993e756114ec8840589fa#diff-1acc535ea354b79f066d86f661256a6d2c2fee45e9be4d212458943591aafe31
sry for the fragmentation
Am Do., 11. März 2021 um 16:35 Uhr schrieb Matthias Milan Strljic <
matthias.strl...@gmail.com
Hi Jim and Ben,
I think I know where this comes from. In the rework process we missed the
changes i added at the commit "d45f748b08d6c083a22993e756114ec8840589fa"
where it enforced the timestamp of a value to "null" because Siemens does
not allow you to write the timestamps of a value on your own.
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [282]':
Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/282/";>PLC4X/PLC4X/develop
[develop] [282]"
Hi Jim,
nvm i over read the part with "Reading was OK" :D
Am Do., 11. März 2021 um 16:21 Uhr schrieb Matthias Milan Strljic <
matthias.strl...@gmail.com>:
> Hi Jim,
>
> an addition to what Ben wrote. Make sure that you wrote the symbol of a
> Siemens value correct. Some versions of Siemens TIA
Hi Jim,
an addition to what Ben wrote. Make sure that you wrote the symbol of a
Siemens value correct. Some versions of Siemens TIA Variable mappings
require the ["]-Symbol included. So your path could also be required to
escape those.
In your case this could be something like:
builder.addItem("S7
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [281]':
Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/281/";>PLC4X/PLC4X/develop
[develop] [281]"
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [280]':
Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/280/";>PLC4X/PLC4X/develop
[develop] [280]"
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [279]':
Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/279/";>PLC4X/PLC4X/develop
[develop] [279]"
Hi Jim,
Just a few thoughts,
Check to see if you have write permission on the ua server.
Is there a leading space before your address, s= S7...?
On Thu, Mar 11, 2021 at 9:29 AM Wang, Jim wrote:
> Hi PLC4X team,
>
> When I use PLC4X's OPCUA protocol to write PLC, I always get ACCESS_DENIED
>
Hi PLC4X team,
When I use PLC4X's OPCUA protocol to write PLC, I always get ACCESS_DENIED for
the PLC's tag (Reading is OK.)
I list my code and message I get below in FYI: sections.
How can I get rid of this issue?
Thanks,
Jim
FYI: my codes
==
public stat
Hi Lukasz,
I see your point there and I am not against "fatter" data structure either.
My problem is just that we should not make it complicated to use, but
mainly to implement. And if we add to go the route with additional
metadata, I would consider the need for a policy to homogenize certain
pro
BUILD-STABLE: Job 'PLC4X/PLC4X/develop [develop] [276]':
Is back to normal.
BUILD-UNSTABLE: Job 'PLC4X/PLC4X/develop [develop] [275]':
Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/275/";>PLC4X/PLC4X/develop
[develop] [275]"
Thanks Lukas,
then just forget all I said ... *pulling out a MIB brain-reset-thing*
Chris
Von: Christofer Dutz
Gesendet: Donnerstag, 11. März 2021 09:14
An: dev@plc4x.apache.org
Betreff: AW: add lebbing to adopters section
Hi Marcus,
just noticed the logo was in the email you sent to me direc
Hi Marcus,
just noticed the logo was in the email you sent to me directly ... I'll take
care of everything.
Thanks ;-)
CHris
Von: Marcus Gotthardt - Lebbing engineering & consulting GmbH
Gesendet: Donnerstag, 11. März 2021 08:56
An: dev@plc4x.apache.org
Betreff: add lebbing to adopters secti
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,
>
>
>
> p
Hi Marcus,
thanks for that ... highly appreciated.
Is there a link to a company logo anywhere?
I'll add it right away.
Chris
Von: Marcus Gotthardt - Lebbing engineering & consulting GmbH
Gesendet: Donnerstag, 11. März 2021 08:56
An: dev@plc4x.apache.org
Betreff: add lebbing to adopters sectio
25 matches
Mail list logo
