Inline custom device synchronization

[thumble]

Hello,

In one of our projects, we need to pay special attention to synchronization. There are several custom devices (CD) that must work together in a deterministic way. The question is: is there a mean to ensure the execution order of the inline part of those devices into the PCL or, at least, to predict it? (In one given PCL cycle I want to be sure CD1 is called before CD2).

Thx for reply

[Jarrod_S. · Accepted solution]

There is a way to control the execution order of inline model custom devices, but not inline hardware custom devices. It is a little cryptic to say the least.

To set the execution order, simply add the following property to your main custom device node:

Property name: nivs.{8f8f48dc-2a8c-4a7c-98b5-164e566940d6}

Data type: U16

Value: 0 - 255

Only use values of 0 through 255. Lower numbers execute first. If there is a tie, then the first device added to the system definition goes first. The default priority assignment if this property is not set is 127.

[thumble]

OK, furthermore can I assume that the overall order if "read" of H/W CD's, "execute" model CD's (submited to priority) and "write" of H/W CD's ?