I have walking prototype,
Here are code changes: https://github.com/apache/plc4x/pull/241
Because current project structure enforces separation of API and SPI I
had to take some steps:
1) There is no way for user to know driver context, hence I touched
public API. EventPlcConnection is added witho
splatch opened a new pull request #241:
URL: https://github.com/apache/plc4x/pull/241
--
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, plea
Łukasz Dywicki created PLC4X-297:
Summary: Port CANopen driver to new CAN bus api
Key: PLC4X-297
URL: https://issues.apache.org/jira/browse/PLC4X-297
Project: Apache PLC4X
Issue Type: Sub-tas
Łukasz Dywicki created PLC4X-296:
Summary: Reorganize stack configuration and generated driver
initialization
Key: PLC4X-296
URL: https://issues.apache.org/jira/browse/PLC4X-296
Project: Apache PLC4X
Łukasz Dywicki created PLC4X-295:
Summary: Introduce high level transport API for CAN bus
Key: PLC4X-295
URL: https://issues.apache.org/jira/browse/PLC4X-295
Project: Apache PLC4X
Issue Type:
Łukasz Dywicki created PLC4X-294:
Summary: Introduce API for connection state events
Key: PLC4X-294
URL: https://issues.apache.org/jira/browse/PLC4X-294
Project: Apache PLC4X
Issue Type: New
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [429]':
Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/429/";>PLC4X/PLC4X/develop
[develop] [429]"
Kudos should go primarily to Adrian who cleaned up mspec, tested it
against real hardware and added missing parts. My role was limited to
assistance in few places.
Looking forward to work with him and others on next steps.
Best,
Łukasz
On 19.04.2021 19:56, Lukas Ott wrote:
> +1 Lukasz you are aw
+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:
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
BUILD-STABLE: Job 'PLC4X/PLC4X/develop [develop] [428]':
Is back to normal.
The issue doesn't seem to have been solved yet ... thinking of changing out
Jenkinsfile ...
Chris
-Ursprüngliche Nachricht-
Von: Christofer Dutz
Gesendet: Sonntag, 18. April 2021 13:33
An: dev@plc4x.apache.org
Betreff: AW: [BUILD-FAILURE]: Job 'PLC4X/PLC4X/develop [develop] [416]'
Se
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [419]':
Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/419/";>PLC4X/PLC4X/develop
[develop] [419]"
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
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
ph
15 matches
Mail list logo
