[
https://issues.apache.org/jira/browse/PLC4X-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17304981#comment-17304981
]
Adrian Lazar commented on PLC4X-286:
------------------------------------
Thank you very much for the kind offer!
I had a feeling that all my problems were coming from using Windows, so I
rebuilt Pcap4j and PLC4X (had to because of the stupid naming that Pcap4j chose
in his module-info, see the [PR|https://github.com/kaitoy/pcap4j/pull/280]) on
a Linux PC and now I can see the broadcasting message is sent and some devices
on the network reply.
I had to figure out how the Wireshark filter works and finally, I got it.
I can see that the package sent is of length 1024, way too much, while other
applications do 60 or 56. Anyhow, now I have a working environment and will
look into why those tests are failing. 🤔
> Add profinet-DCP
> ----------------
>
> Key: PLC4X-286
> URL: https://issues.apache.org/jira/browse/PLC4X-286
> Project: Apache PLC4X
> Issue Type: Improvement
> Components: Driver-Ethernet/IP, Driver-Profinet, Driver-S7
> Affects Versions: 0.9.0
> Reporter: Adrian Lazar
> Priority: Major
> Labels: beginner, feature, question
>
> I found some work done towards implementing the
> [profinet-DCP|https://profinetuniversity.com/naming-addressing/profinet-dcp/]Â
> protocol on the [feature/profinet
> branch|[https://github.com/apache/plc4x/tree/feature/profinet]].
> I see that the profinet protocol is not on the develop branch anymore, was it
> replaced with the s7 protocol?
> If someone would have the time to guide me, I could work on it to update,
> test, and bring this discovery feature to PLC4X.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
