![Mitsubishi Electric QJ71AS92 Скачать руководство пользователя страница 61](http://html.mh-extra.com/html/mitsubishi-electric/qj71as92/qj71as92_user-manual_1811845061.webp)
4 - 7 4 - 7
MELSEC-Q
4 SETTINGS AND PROCEDURES FOR OPERATION
4.5 Start-Up
After powering on the programmable controller, the QJ71AS92 is placed in the normal
operation status (ready to communicate data with the slaves) via the following
communication phases.
Off-line phase
Detection phase
In this phase, the QJ71AS92 is initialized. Communication in the AS-i system is not started.
If sufficient power is not supplied from the AS-i power supply to the AS-i system, the
QJ71AS92 remains in the offline phase. (The "U ASI" LED is not lit.)
When AS-i power is supplied, the QJ71AS92 switches to the detection phase.
In this phase, the QJ71AS92 checks for the slaves that are ready for communication in the
AS-i system. It remains in the detection phase until it finds at least one slave.
Activation phase
In this phase, the slaves found by the QJ71AS92 in the detection phase become ready to
communicate.
Normal operation
In the normal operation status, the QJ71AS92 can communicate data with all the slaves
that are ready for communication. The QJ71AS92 sends a management message to check
for a newly connected slave, and if it exists, makes it ready for communication.
The normal operation phase has the configuration mode and protected operation
mode. The QJ71AS92 is put in either mode that has been registered to the EEPROM
after powering on.
The configuration mode and protected operation mode can be switched between each
other by writing an instruction (command) from the CPU module.
(a) Configuration
mode
In this mode, the QJ71AS92 communicates with all detected slaves.
(However, output data is not output to the slave of slave address 0.)
This mode is used to set the slave address.
(b) Protected
operation
mode
In this mode, the QJ71AS92 communicates with all registered slaves.
Normally, this mode is used to make communication.
To use this mode, the configuration data of the slave must be registered.
If a slave not registered as configuration data is detected at start of
communication, a configuration error will occur.
Downloaded from