Rockwell Automation 47C626 AutoMax Programming Executive V4.2 - Manual (Page 75)

5Ć41
cannot communicate with older versions of the AutoMax Executive
software. The Version 4 AutoMax Executive software cannot
communicate with racks containing older versions of the AutoMax
OSs. However, the Version 4 Executive is able to check a rack to
verify that no tasks are running and to erase the old operating
system. This will also cause parameter object files and tasks to be
deleted. You can then load a Version 4 operating system to the rack.
All earlier versions of the operating systems must be replaced by
Version 4 OSs before you can go online or communicate over the
AutoMax network. When loading the OS to 6011 Processors, only the
Ethernet OS will be allowed. NOTE: The Version 4 AutoMax OS will
automatically erase any UDC OSs that are incompatible with the
Version 4 AutoMax OS, requiring new UDC OSs to be loaded.
The leftmost AutoMax Processor in the rack will check for
compatibility between the AutoMax OS and the UDC OS. If you
replace a UDC with another UDC that already contains an OS that 's
incompatible, the new UDC will be disabled and its OS OK" LED will
turn off.
Precautions in Loading the AutoMax Operating System
Normally, when the operating system is loaded to the AutoMax
Processors in a rack, the AutoMax operating system currently on the
Processors (if any) is written over. However, it is possible that the
operating system in the rack is a later version than the operating
system contained in the Programming Executive software you are
using. In this case, the Programming Executive will be unable to
establish communication with the rack in order to load the new
AutoMax operating system until you erase the existing operating
system. The procedure for erasing the operating system for all of the
AutoMax Processors in a rack is described in section 5.4.5.
The situation described above cannot occur when loading the
operating system to UDC modules since communication is
established first with the AutoMax Processor in the rack first and then
with the UDC module rather than the UDC module directly. The
existing operating system on a UDC module (if any) will be written
over when you load any UDC operating system to that module.
AutoMax Processor modules have onĆboard battery backup, so you will
need to reĆload the AutoMax operating system only when enhancements
become available, when you change the password for the rack using
the PWOS.EXE utility described in 9.2.1, or when an AutoMax Processor
module in the rack is replaced. Note carefully that all tasks in the rack
will be deleted when you load the AutoMax operating system to the
Processor(s) in the rack. To ensure that the values of any tunable
variables will be maintained in their respective tasks, you should
save all application tasks in the rack that contain tunable variables
back to the personal computer from the rack (see 14.4) after you
have finished tuning variables, and before you load the new
operating system. If you are loading a more recent version of the
operating system, you may need to reĆcompile your application tasks
using the corresponding Programming Executive software before
downloading them to the rack.
UDC modules use nonĆvolatile Flash memory to store their operating
systems and UDC application tasks, so you will need to reĆload the
UDC operating system only when enhancements become available
or when a UDC module in the rack is replaced. Note carefully that all
tasks in the UDC module will be deleted when you load the UDC
operating system to that particular UDC module.