Version Conflict! ATMOxAnalogInput, ATMOxAnalogInputArray and ATMOxAnalogOutputArray

[DavidNavas]

Hi everybody,

When using ATMOxAnalogInputArray and ATMOxAnalogOutputArray objects, a Version Conflict! related to DataSetManager appears:

By changing the DataSetManager versions in .ood , it seems to be solved: 

Once that conflict disappears, a new one is displayed, now related to NxDataDefBase:

On the other hand, the object ATMOxAnalogInput has this Verison conflict!:

It would be really helpful If someone could support me with these issues.

[nexidator · Accepted solution]

There is a known bug in CpStudio concerning this behavior: When multiple versions of the same baseRef are allowed, and it's not the first given version that is available and in use in the project, this obect is shown as cause of the version conflict although there is no problem with it. In reality, some other object required as baseRef is missing. I am afraid there is no easy way in CpStudio to find the missing object. When using the ObjectBrowser to download the objects, the required base objects should be selected automatically, that's why the bug does not occur that often. If you cannot work with the ObjectBrowser, you need to check all the baseRefs in the objects manually and recursively.

[MarvinW]

Since all these objects are requiring OES 4.11, we can delete the version attribute and keep only the versions attribute without negative consequences, right? Would this help a little with the problem?

[DavidNavas]

It was my bad, the object ATMOxProcessControlBase was missing. I left the versions atributte as it was at the very beginning and there is no more version conflict. Thanks for your help.

[nexidator]

@MarvinW That's right, the version attribute is only necessary for compatibility with older OES versions. But removing it would not avoid the misbehavior.