Modulebus Max scan time setting is locked at 100ms what could be locking it? the available max should be 300ms.
This System is 5.1 Rev B
CBM Version 5.1.0/1 Build (5.1.100.13)
We need to increase the scan time to reduce the controller load.
Thanks.
CBM Version 5.1.0/1 Build (5.1.100.13)
We need to increase the scan time to reduce the controller load.
Thanks.
Asked 10 months ago
Answers
1
Hi Mark,
Looks like the help file may be wrong. My CBM says 100ms Max as well.
You can avoid IO scanning load entirely by using either Profibus or Profinet. If you have a large volume of IO, then only put signals that you need to scan at a very high rate on direct IO. Put everything else on Profibus.
Looks like the help file may be wrong. My CBM says 100ms Max as well.
You can avoid IO scanning load entirely by using either Profibus or Profinet. If you have a large volume of IO, then only put signals that you need to scan at a very high rate on direct IO. Put everything else on Profibus.
Answered 10 months ago
1
I'm no pro on AC 800M hardware, but different CPUs seem to have different Scant Cycle Time restrictions.
This image is from 5.1 FP4 Rev containing Control Builder M version 5.1.1-3 (Build 5.1.1300.11)
CPU / valid Scan Cycle Time range
PM851: 0...100ms
PM856: 0...100ms
PM860: 0...100ms
PM861: 0...100ms
PM864: 0...100ms
PM865: 0...300ms
PM866: 0...100ms
PM891: 0...300ms
This image is from 5.1 FP4 Rev containing Control Builder M version 5.1.1-3 (Build 5.1.1300.11)
CPU / valid Scan Cycle Time range
PM851: 0...100ms
PM856: 0...100ms
PM860: 0...100ms
PM861: 0...100ms
PM864: 0...100ms
PM865: 0...300ms
PM866: 0...100ms
PM891: 0...300ms
Add new comment