Q: Redundant Owner connections support in OpENer

[Lorenzo]

Hi everyone,

first of all thanks for accepting me to this group. 

I am Lorenzo, a firmware engineer in the PLC world.

I am working on a small proof of concept for containerizing an EIP adapter an so, OpENer is the stack to be (and to integrate) !

Thanks to everyone contributing to such a src code, especially the sampleapplication who helps a lot in understanding how the stack init, callbacks and so on...

So, I searched a while in the code but I was not able to understand if the stack supportd the Redundant Owner or not, cause in my project we would like to be able to share the same connection(s) between the adapter (OpENer) and several originators.

Do anyone know if it is supported ?

Thanks

Lorenzo

[martin...@gmail.com]

Hi Lorenzo,

no, redundant owner connections are not supported, but for sharing a connections it is not necessary in all cases.

Redundant owner is only needed were an O->T connection needs to be able to have several owners.

If you want to share T->O (adapter to originator) connections, this is possible via Input-Only and Listen-Only connections

Best regards

Martin

[Lorenzo]

Hi Martin,
thanks for your feedback. 

We need to share the same connection(s) between several owners (ORIGINATOR), so the Redundant Owner facility.

Would it be heavy, to your opinion, to add such a support in the stack? Have you got any entry point to give me for starting to dig more in the code?

Best Regards,

Lorenzo

[martin...@gmail.com]

Hi Lorenzo,

I guess its not super hard to do but a considerable amount of work. Entry point would be the (LARGE_)FORWARD_OPEN in the case were the redundant owner flag in the message is checked.

There you would need to replace the error message response with a mechanism, where you can register other connections (predefined how many) as a redundant owner connection.

Then you would need to implement the Claim Output Ownership (COO) flag and priority mechanism, so that OpENer knows which O->T data shall be used.

Of course also checks on EO connections, timeouts, timeout behavior, PTP/multicast connections etc.

Probably best to start the list of RO connections and the COO stuff, and then checking with the Conformance Tester on the timeout behavior.

If you have specific questions feel free to ask.

Best regards,

Martin