Hi there,
is there a plan to implement the dynamic node allocation feature? I cannot find something on the roadmap, but perhaps someone knows something ;)
Thanks and BR
Steffi
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Wolfgang,
we are also interested in DNA. The application in our case requires to use several nodes on the bus (up to 80). The customer whants to have the freedom to modify the plant adding/removing devices maybe in the middle of the nodes chain, depending on particular needs. Manually re-assigning ID's is not an option (devices will be hard to reach once thay have been installed).
We are using Altera Cyclon IV FPGA. I guess DNA implementation may require modifications in IP cores too.
We are available to contribute to the development and/or testing of course.
Best regards
Carlo
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
DNA is not part of the openPOWERLINK stack but you can download the draft standard for DNA from EPSG for reference. But just for my understanding, for the use-case described by you, you need to scale or replace the network with newer nodes without reassigning the IDs.
Just to make sure that there is not communication gap, in Powerlink you can replace a node without the need to reassign nodeids on other nodes. Cyclone IV uses on-board switches for nodeid and you just would need to set the same node id of the replaced node, on the new node.
For adding and removing nodes in the middle of the network, since Powerlink does not need a strict topology hierarchy to be defined in the program (unlike PN IRT), you can add newer nodes or remove nodes out of order. As long as the nodeids are unique and do not collide with the existing nodes, the nodes can be connected anyway needed. You only would need to update the network configuration file and PLC program as per the updated network.
But if you have other concerns like convenience of adding / removing nodes, etc, let me know for any help. Thanks.
I know that in Powerlink we can do all the things that you mentioned, but our use case is a different one. We need to completely reassign ID's to a full plant, to change its behavior. Let's say that when the plant is supposed to work clockwise ID's are assigned from 1 to 64, in ascending order. But sometimes the same plant needs to work counterclockwise and this requires to reassign all ID's in descending order, from 64 to 1.
So it's not just a matter of replacing or adding a couple of nodes. We definitely need DNA
Best regards
Carlo
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Carlo, Okay I understand. If its feasible for you, could you please share the use case, in a message would also be fine. For DNA, the node would need support in software (SoA frame flags and NMT command) as well as a Physical port on/off control capability on the openHUB in IP core (as you have mentioned).
Hi there,
is there a plan to implement the dynamic node allocation feature? I cannot find something on the roadmap, but perhaps someone knows something ;)
Thanks and BR
Steffi
Hello,
An implementation of DNA is not planned for openPOWERLINK.
What kind of application or device are you implementing that requires this feature?
Best regards,
Wolfgang
Hello Wolfgang,
we are also interested in DNA. The application in our case requires to use several nodes on the bus (up to 80). The customer whants to have the freedom to modify the plant adding/removing devices maybe in the middle of the nodes chain, depending on particular needs. Manually re-assigning ID's is not an option (devices will be hard to reach once thay have been installed).
We are using Altera Cyclon IV FPGA. I guess DNA implementation may require modifications in IP cores too.
We are available to contribute to the development and/or testing of course.
Best regards
Carlo
Hi Carlo,
DNA is not part of the openPOWERLINK stack but you can download the draft standard for DNA from EPSG for reference. But just for my understanding, for the use-case described by you, you need to scale or replace the network with newer nodes without reassigning the IDs.
Just to make sure that there is not communication gap, in Powerlink you can replace a node without the need to reassign nodeids on other nodes. Cyclone IV uses on-board switches for nodeid and you just would need to set the same node id of the replaced node, on the new node.
For adding and removing nodes in the middle of the network, since Powerlink does not need a strict topology hierarchy to be defined in the program (unlike PN IRT), you can add newer nodes or remove nodes out of order. As long as the nodeids are unique and do not collide with the existing nodes, the nodes can be connected anyway needed. You only would need to update the network configuration file and PLC program as per the updated network.
But if you have other concerns like convenience of adding / removing nodes, etc, let me know for any help. Thanks.
Best Regards,
aeicoriiotteam
Hi,
I know that in Powerlink we can do all the things that you mentioned, but our use case is a different one. We need to completely reassign ID's to a full plant, to change its behavior. Let's say that when the plant is supposed to work clockwise ID's are assigned from 1 to 64, in ascending order. But sometimes the same plant needs to work counterclockwise and this requires to reassign all ID's in descending order, from 64 to 1.
So it's not just a matter of replacing or adding a couple of nodes. We definitely need DNA
Best regards
Carlo
Hi Carlo, Okay I understand. If its feasible for you, could you please share the use case, in a message would also be fine. For DNA, the node would need support in software (SoA frame flags and NMT command) as well as a Physical port on/off control capability on the openHUB in IP core (as you have mentioned).
Best Regards,
#aeicoriiotteam