NodeInfo and CustomNodeInfo

We’re trying to add support for Yaskawa Sigma-10 drives.
I added a Product element for it (with our customizations) to CustomNodeInfo.xml.
It is not until I remove the Yaskawa Vendor element from NodeInfo.xml that RMP pays any attention to my entry in CustomNodeInfo.xml.

The docs suggest that what’s in custom should automagically replace anything in nodeinfo.

Vendor entries in CustomNodeInfo.xml will fully replace Vendor entries in NodeInfo.xml

Is this expected behavior? Up until now, we’ve had other Yaskawa products in CustomNodeInfo that seem to get used.

Hi @todd_mm,

It isn’t what I would expect for 10.6.4.

If we find a Vendor in CustomNodeInfo.xml that also exists in NodeInfo.xml, we go through each Product in CustomNodeInfo.xml. If a NodeInfo.xml entry for that product is found, we remove and replace it with the your CustomNodeInfo.xml version.

My guess is there is some malformed xml which is breaking the c++ parser so it aborts the process. Send me an email with original implementation and I’ll take a look.

1 Like

Following for model training and anyone who finds a similar issue in the future.

It looks like we don’t handle duplicate Product entries within CustomNodeInfo.xml. Double check to make sure that you have just 1 entry for each node type in CustomNodeInfo.

1 Like