Does the workbench read an entire component at once?

[BobWirka]

When the workbench is running, does it read the values for a component in one operation, or does it do individual operations for each slot?

The question is whether it would be more efficient to have a component incorporate multiple I/O points; if the workbench reads the entire object with one operation, we'd cut down on the communication overhead.

How does this work?

Thanks,

Bob Wirka

[BobWirka]

Looking at the online docs, it seems that the SOX read/write operations are only for a single slot...

Have I answered my own question?

Bob Wirka

[Craig]

Hi Bob-

Sox read/write operations are single-slot.  However, when Workbench is viewing a Sedona component through a Sox connection to a Sedona device, it subscribes to the component.  This means that changes to any slot in the component generate Sox event messages to the client (the Workbench), and this is how the changes are reflected in the Workbench.