![[MAT logo]](../../../images/MAT-linux-h100.gif)
Explanation from a PLC background: the MatPLC reduces scan time at the expense of latency - at the top/bottom of the scan, it simply uses the latest available values rather than waiting for fresh ones. This is by default.
Using synch, the user can configure a global scan which interleaves scans of the ladder with refreshing the I/O, classical PLC style.
For modules like a modbus slave, one would normally leave it asynchronous, serving requests as they come in.
Similarly for any other modules that don't really belong in the global cycle. Perhaps they might even have a mini-global-cycle of their own - for instance, an I/O module and a corresponding DSP module might be synched together but not to anything else.
$Date: 2003/09/05 11:36:00 $