Warm boot, Cold boot – ProSoft Technology MVI69-101S User Manual
Page 87

Reference MVI69-101S
♦ CompactLogix or MicroLogix Platform
IEC 60870-5-101 Slave Communication Module
ProSoft Technology, Inc.
Page 87 of 149
March 16, 2009
Warm Boot
This block is sent from the CompactLogix or MicroLogix processor to the module
when the module is required to perform a warm-boot (software reset) operation.
This block is commonly sent to the module any time configuration data
modifications are made in the controller tags data area. This forces the module to
read the new configuration information and to restart. The structure of the control
block is shown in the following table.
Block Request
Offset Description
Length
0 9998
1
1 to x
Not used
blk_size
Cold Boot
This block is sent from the CompactLogix or MicroLogix processor to the module
when the module is required to perform the cold boot (hardware reset) operation.
This block is sent to the module when a hardware problem is detected by the
ladder logic that requires a hardware reset. The structure of the control block is
shown in the following table.
Block Request
Offset Description
Length
0 9999
1
1 to x
Not used
blk_size
5.2.6 Data Flow Between MVI69-101S Module and CompactLogix or
MicroLogix Processor
The following topics describe the flow of data between the two pieces of
hardware (CompactLogix or MicroLogix processor and MVI69-101S module) and
the IEC 60870-5-101 master unit. Each port on the module is configured to
emulate a common slave device. The database used in the module is used for
both ports and only one port can be utilized at one time.