Canon imageRUNNER ADVANCE C350 series Service Manual page 238

2
Technical Explanation > MEAP > Maintenance > Points to Note When Enabling the [Quick Startup Settings for Main Power] Setting
■ Points to Note When Enabling the [Quick Startup Settings for
Main Power] Setting
If some of the MEAP applications are running on the device, the following problems will occur.
● The [Quick Startup Settings for Main Power] setting cannot be
enabled.
If a MEAP application that restricts the device from shifting to deep sleep mode is running,
even when the setting of [Quick Startup Settings for Main Power] is enabled (On), the device
starts normally instead of quick startup.
In that case, it does not affect the behavior of the MEAP application.
● Changes made in the settings of a MEAP application are not
reflected.
If the startup setting [Quick Startup Settings for Main Power] is enabled (On), even when the
Main Power Supply Switch of the machine is turned OFF, a shutdown process is not executed
internally.
Therefore, in the case of a MEAP application where changes in settings are enabled when
the device is restarted, changes in settings are not reflected just by changing the settings.
Follow either of the restart procedures shown below to enable the changes made in the
settings.
• Execute restart from remote UI.
• Turn OFF the Main Switch, and then turn it ON within 20 seconds.
● After recovery from quick startup, MEAP applications do not work
properly.
MEAP applications that are scheduled to execute processes at specified times may not work
properly after recovery from quick restart.
Unexpected problems such as that the application executes a task at an unexpected timing
may occur.
Problems may occur in the following two cases.
2 Technical Explanation > MEAP > Maintenance > Points to Note When Enabling the [Quick Startup Settings for Main Power] Setting
In the case of "Schedule: Execute the task every 24 hours"
A schedule is set to start the specified task at the specified time and repeat "fixed-delay
execution".
If execution is delayed for some reason, the delay time is ignored.
Problem: If 24 hours have passed since the last execution of the task, the task is executed
only once.
=> The task may be executed at a timing other than the time the user expects it to be
executed.
31/Dec 1/Jan
Starting
Stopped
(Quick startup standby)
The timing the task is expected to be executed
The timing the task was actually executed
In the case of "Schedule: Execute the task at 00:00 every day"
A schedule is set to start the specified task at the specified time and repeat "fixed-rate
execution".
If execution was delayed for some reason, two or more tasks are continuously executed to
"make up for the delay".
Problem: The tasks of Jan. 1, Jan. 2, and Jan. 3 are executed after quick startup.
31/Dec 1/Jan
Starting
Stopped
(Quick startup standby)
The timing the task is expected to be executed
The timing the task was actually executed
2-195
2/Jan 3/Jan 4/Jan 5/Jan
F-2-343
2/Jan 3/Jan 4/Jan 5/Jan
F-2-344
2-195