Re: AW: Further updates to CAN stuff in plc4j

2021-04-13 Thread Ɓukasz Dywicki
I began to scratch surface of Driver/Protocol/Context and here is what I found. Currently it is *impossible* to do any customization with ProtocolStackConfigurer or GeneratedDriverBase without really copying whole classes. Trouble I see is: 1) Protocol stack configurer rely on classes instead of

[BUILD-STABLE]: Job 'PLC4X/PLC4X/develop [develop] [391]'

2021-04-13 Thread Apache Jenkins Server
BUILD-STABLE: Job 'PLC4X/PLC4X/develop [develop] [391]': Is back to normal.

[BUILD-UNSTABLE]: Job 'PLC4X/PLC4X/develop [develop] [390]'

2021-04-13 Thread Apache Jenkins Server
BUILD-UNSTABLE: Job 'PLC4X/PLC4X/develop [develop] [390]': Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/390/;>PLC4X/PLC4X/develop [develop] [390]"

[BUILD-UNSTABLE]: Job 'PLC4X/PLC4X/develop [develop] [389]'

2021-04-13 Thread Apache Jenkins Server
BUILD-UNSTABLE: Job 'PLC4X/PLC4X/develop [develop] [389]': Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/389/;>PLC4X/PLC4X/develop [develop] [389]"

[BUILD-UNSTABLE]: Job 'PLC4X/PLC4X/develop [develop] [388]'

2021-04-13 Thread Apache Jenkins Server
BUILD-UNSTABLE: Job 'PLC4X/PLC4X/develop [develop] [388]': Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/388/;>PLC4X/PLC4X/develop [develop] [388]"

[BUILD-UNSTABLE]: Job 'PLC4X/PLC4X/develop [develop] [387]'

2021-04-13 Thread Apache Jenkins Server
BUILD-UNSTABLE: Job 'PLC4X/PLC4X/develop [develop] [387]': Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/387/;>PLC4X/PLC4X/develop [develop] [387]"

PLC4c: What I'm up to in PR#233

2021-04-13 Thread Thomas
Hi all, Re [PR233](https://github.com/apache/plc4x/pull/233). I aim to use PLC4c with digital twins (codegen'd Simulink models) for metal industry and have it talk to Siemens S7 PLCs. Currently use a customized version of libnodave but PLC4x is interesting as it (eventually) works with

[GitHub] [plc4x] sruehl merged pull request #239: Update S7Field.java

2021-04-13 Thread GitBox
sruehl merged pull request #239: URL: https://github.com/apache/plc4x/pull/239 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please

[GitHub] [plc4x] sruehl commented on pull request #239: Update S7Field.java

2021-04-13 Thread GitBox
sruehl commented on pull request #239: URL: https://github.com/apache/plc4x/pull/239#issuecomment-818639526 thanks for the PR -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific

[GitHub] [plc4x] thomas169 commented on pull request #233: Address string with tokenisation, refactoring, loopback s7 c example added. s7c write variable works

2021-04-13 Thread GitBox
thomas169 commented on pull request #233: URL: https://github.com/apache/plc4x/pull/233#issuecomment-818636113 I already signed up, but sure, will message mailing list. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use

[GitHub] [plc4x] Meng5 opened a new pull request #239: Update S7Field.java

2021-04-13 Thread GitBox
Meng5 opened a new pull request #239: URL: https://github.com/apache/plc4x/pull/239 fix S7 Driver read type of String with the address copied directly out of TIA portal bug. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

[GitHub] [plc4x] chrisdutz commented on pull request #233: Address string with tokenisation, refactoring, loopback s7 c example added. s7c write variable works

2021-04-13 Thread GitBox
chrisdutz commented on pull request #233: URL: https://github.com/apache/plc4x/pull/233#issuecomment-818599697 Hi Thomas, a general question ... could you be so kind and sign up for the dev@plc4x.apache.org list and tell us a bit about what you're up to? Chris -- This is