[Reference] To realize faster startup, the power configuration has been changed to always supply power to the All-night Power Supply PCB. With this change, the

time to display the main menu after turning on the main power switch is shortened and the time until the screen can be operated on is also shortened.

This machine provides power to following PCBs even when in the main power switch is OFF.

- AC Driver PCB

- All-night Power Supply PCB

- Relay PCB

- Main Controller PCB 1

[Caution] 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, the behavior of the MEAP application is not affected.

- 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 chang-

ing the settings.

Follow either of the restart procedures shown below to enable the changes made in the settings.

a) Execute restart from remote UI.

b) Turn OFF the Main Switch, and then turn it ON within 20 seconds.

- After a 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 the application executes a task at an unexpected timing may occur.

Problems may occur in the following two cases.

- 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.