Chapter 4. ConfigurationGFK-2224Q January 2017 474.2 Rack-based and RX7i Embedded InterfacesThe configuration process for the rack-based and RX7i embedded Ethernet interfaces includes:▪ Assigning a temporary IP address for initial network operation, such as connecting the programmer todownload the hardware configuration.▪ Configuring the characteristics of the Ethernet interface.▪ Configuring Ethernet Global Data (if used).▪ (Optional, not required for most systems). Setting up the RS-232 port for Local Station Manager operation.This is part of the basic Ethernet Interface configuration.▪ (Optional, not required for most systems). Configuring advanced parameters. This requires creating aseparate ASCII parameter file that is stored to the PLC with the hardware configuration. The EthernetInterface has a set of default Advanced User Parameter values that should only be changed in exceptionalcircumstances by experienced users. The Advanced User Parameters definitions and configuration aredescribed in Appendix A.▪ (Optional) Setting up the PLC for Modbus/TCP Server operation. See Chapter 8 for information aboutconfiguring Modbus/TCP Server operation.This chapter discusses only the configuration of the PACSystems Ethernet Interface. Information about overallsystem configuration is available in other PACSystems documentation and in the Logic Developer online help.Ethernet Configuration DataThe PACSystems PLC is configured exclusively by the Machine Edition PLC Logic Developer-PLC programmer.The Programmer can be connected over the Ethernet network. For initial programmer connection, an initial IPaddress must be manually assigned to the Ethernet interface as described next in this chapter. ThePACSystems PLC does not support auto-configuration.Generating / Storing / Loading the ConfigurationThe PACSystems Ethernet interfaces use several types of configuration data: Ethernet Configuration, optionalEthernet Global Data Configuration, and optional Advanced User Parameter (AUP) Configuration. Theseconfiguration parameters are generated at the programmer, stored from the programmer to the PLC CPU aspart of the hardware configuration Store sequence and may be loaded from the PLC CPU into the programmeras part of the Configuration Load sequence. The optional AUP file must be manually generated with a texteditor and then imported into the programmer. The programmer then stores any AUP files to the PLC within theConfiguration Store operation. Once stored to the PLC, the PACSystems main CPU maintains the configurationdata over power cycles.Backup Configuration DataThe PACSystems Ethernet interface saves a backup copy of the most recent Ethernet Configuration and AUPConfiguration in non-volatile memory for use when the PLC is cleared. (Ethernet Global Data configuration ismaintained only in the PLC CPU.) The PACSystems Ethernet interfaces maintain the backup configuration datain nonvolatile memory without battery power. (A PLC Configuration Clear does not affect the backupconfiguration data in the Ethernet interface.)When the PLC configuration was not stored from the programmer, the Ethernet interface uses its backupconfiguration data if valid. If that data is invalid or has never been configured, factory default configurationvalues are used.Locally Edited Configuration DataIf the PLC configuration was not stored from the programmer, the CHSOSW and CHPARM Station Managercommands can be used to locally edit Ethernet configuration or AUP configuration data. These StationManager commands are not active if the PLC configuration has been stored from the programmer.
