I'm using the cdc filein "apps/common/openCONFIGURATOR_projects/Demo_RMN_3CN". I have three nodes with nodeIds 1, 241 and 242.
I have two problems:
1/ Node 1 and 241 are working perfectly together. Node 241 is the MN in this case. According to the specs, Node 241 is supposed to send Pres of 241 in addition to MN frames (SoC, SoA, Preq). However, i don't see this Pres... (see pcap file, end of file). Do you know why ?
2/ When i'm launching node 242 in addition to node 1 and 241, i have an error with your cdc file:
nice to hear that you are trying Managing Node Redundancy feature.
1/ Like normal MNs the RMNs require the flag MN_PRES (Bit 12) in object 0x1F81 (NMT_NodeAssignment_AU32, sub-index corresponds to node-ID) to send PRes-MN.
2/ E_DLL_INVALID_FORMAT is commonly caused by too large PRes frames. That may be caused by misconfiguration, e.g. object 0x1F98 NMT_CycleTiming_REC sub-index 5 PResActPayloadLimit_U16 on CN is larger than object 0x1F8D NMT_PResPayloadLimitList_AU16 on MN. Once I came across an USB Ethernet adapter which forwarded too much bytes via PCAP. Maybe it was just a driver bug of Linux kernel. But it triggered E_DLL_INVALID_FORMAT for other CNs, when running as MN.
Best regards,
Daniel Krüger
SYS TEC electronic GmbH
Last edit: Daniel Krüger 2015-06-30
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for your help. You have helped me a lot.
MN Redundancy feature currently work on my test platform !
For information, here is the configuration:
- 3 Nodes which can all become MN.
- No CFM
I have excellent results !
Mathieu
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I'm trying to implement Managing Node Redundancy with openPowerlink v2.2.0. I read the documentation : http://openpowerlink.sourceforge.net/doc/2.2/2.2.0/d8/ddf/page_mnredundancy.html
And specs EPSG 302-A Section 3.
I'm using the cdc filein "apps/common/openCONFIGURATOR_projects/Demo_RMN_3CN". I have three nodes with nodeIds 1, 241 and 242.
I have two problems:
1/ Node 1 and 241 are working perfectly together. Node 241 is the MN in this case. According to the specs, Node 241 is supposed to send Pres of 241 in addition to MN frames (SoC, SoA, Preq). However, i don't see this Pres... (see pcap file, end of file). Do you know why ?
2/ When i'm launching node 242 in addition to node 1 and 241, i have an error with your cdc file:
Thanks in advance, hope you can answer my questions.
Mathieu
Last edit: Mathieu Goutel 2015-06-29
Hello Mathieu,
nice to hear that you are trying Managing Node Redundancy feature.
1/ Like normal MNs the RMNs require the flag MN_PRES (Bit 12) in object 0x1F81 (NMT_NodeAssignment_AU32, sub-index corresponds to node-ID) to send PRes-MN.
2/ E_DLL_INVALID_FORMAT is commonly caused by too large PRes frames. That may be caused by misconfiguration, e.g. object 0x1F98 NMT_CycleTiming_REC sub-index 5 PResActPayloadLimit_U16 on CN is larger than object 0x1F8D NMT_PResPayloadLimitList_AU16 on MN. Once I came across an USB Ethernet adapter which forwarded too much bytes via PCAP. Maybe it was just a driver bug of Linux kernel. But it triggered E_DLL_INVALID_FORMAT for other CNs, when running as MN.
Best regards,
Daniel Krüger
SYS TEC electronic GmbH
Last edit: Daniel Krüger 2015-06-30
Hello Daniel,
Thank you for your help. You have helped me a lot.
MN Redundancy feature currently work on my test platform !
For information, here is the configuration:
- 3 Nodes which can all become MN.
- No CFM
I have excellent results !
Mathieu