Motion Event Instructions 
 
  Rockwell Automation Publication MOTION-RM002H-EN-P-February 2018  285 
Tip: 
For the 1756-OB16IS module, outputs 0 to 7 can be forced by forcing the Data Bit 
to 0 or 1 and its corresponding bit in the ScheduleMask to 0. For outputs 8 to 15, 
only the Data Bit needs to be forced. For the 1732E-OB8M8SR and 1756-OB16IEFS 
modules, force outputs 0 to 7 and outputs 0 to 15 in the same manner that you use 
for the 1756-OB16IS module. 
Due to the limit of 16 schedules supported by the 1756-OB16IS and 
1732E-OB8M8SR modules and 32 for the 1756-OB16IEFS module, some 
constraints are applied to the number of events that can be processed every coarse 
update period. 
Only 8 schedules are available each coarse update for the 1756-OB16IS and 
1732E-OB8M8SR modules. This allows for two consecutive coarse updates in 
which each update contains 8 output events. As a group of 8 schedules are 
currently being processed by the scheduled output modules, a second group of 8 
schedules can concurrently be set up for the next coarse update. 
Similarly, only 16 schedules are available each coarse update for the 
1756-OB16IEFS module. This allows for two consecutive coarse updates in which 
each update contains 16 output events. As a group of 16 schedules are currently 
being processed by the scheduled output modules, a second group of 16 schedules 
can concurrently be set up for the next coarse update. 
The following diagram illustrates the relationship between the coarse update 
period, a cam latch event and the time slots for the 1756-OB16IS.