Reliance Electric AutoMax Programming Executive V3.5

Reliance Electric AutoMax ®  Programming Executor V3.5: Deep Analysis of the Core Software Platform for Distributed Control Systems

In the field of industrial automation and process control, a powerful, reliable, and easy-to-use programming and configuration software platform is the key to unleashing the potential of hardware systems. The AutoMax launched by Reliance Electric ® Distributed control systems, with their modularity, strong real-time performance, and networking capabilities, have been applied in numerous industrial scenarios. As its core programming and project management tool, AutoMax Programming Executive Version 3.5, provides users with a software that runs on Microsoft Windows ™ A complete environment for offline engineering design and online system operation in a graphical interface. This article aims to provide a comprehensive and in-depth technical analysis of the AutoMax programming actuator V3.5, offering a detailed application guide for automation engineers and technicians.

System Overview and Core Architecture

The AutoMax programming executor V3.5 marks a significant shift from early command-line or dedicated environments to modern graphical user interface (GUI) operations. It utilizes the 386 enhanced mode of Windows 3.1 (or higher) to provide engineers with an intuitive and efficient software engineering environment. The core design concept is to hierarchically and modularly manage a complete industrial control application project, mainly reflected in the four level structure of "Library → System → Section → Rack".

Library: The highest management level used to classify different project systems, with the default library being AMXLIB.

System: Represents a complete control application, such as a complete production line or a large process unit.

Region: Logical grouping of racks by function or physical location within the system for ease of management.

Rack: The most basic hardware unit, corresponding to a physical AutoMax chassis, including processors, I/O modules, communication modules, etc.

The software itself integrates four core applications, forming the backbone of offline engineering:

System Configurator: Used to create and manage the hierarchical structure mentioned above, and can import systems created in earlier versions (such as AutoMax V2) or ASD (AutoMax Software Designer) V8. x.

Rack Configurator: Graphically configure modules in physical racks, including local racks, remote I/O networks (supporting AutoMax and Shark remote racks, remote heads, digital tracks, etc.), and drive parameters (for UDC modules).

Variable Configurator: Maps meaningful variable names and descriptions to I/O points, network registers, and public memory locations, replacing the direct use of physical addresses in programming and greatly improving program readability and maintainability. It provides specific configuration forms for different types of modules (basic I/O, network interfaces, public memory).

Task Manager: Used to create, edit, compile, validate, and manage application tasks running on AutoMax processors or Universal Drive Controller (UDC) modules. Supports three programming languages: ladder logic (PC), control block language, and enhanced BASIC language.

Hardware and software environment requirements

To ensure stable software operation, V3.5 has clear requirements for the operating platform:

Computer: IBM compatible machine based on Intel 80386 or higher performance.

Memory: At least 2 MB RAM (4 MB is recommended for better performance).

Hard drive: At least 40 MB of free space.

Operating System: MS-DOS 5.0 or higher.

Graphics environment: Must run in 386 enhanced mode on Microsoft Windows 3.1 or later, and does not support real mode.

Peripheral devices: At least one idle serial port (COM1 or COM2) is required to connect to the AutoMax processor. A mouse is not necessary but strongly recommended as it can significantly improve operational efficiency in the Windows environment.

Network function: V3.5 supports the use of tokens, file locking, version control library (VCL), and other functions when workstations are connected to a local area network (LAN). This is crucial for multi engineer collaborative projects and can effectively prevent database file damage and task file change loss. VCL functionality requires Intersolv ™  Polytron Version Control System (PVCS) V5.0 or higher support.

Deep analysis of core functional modules

1. Rack and hardware configuration

The rack configurator is the core of building hardware images for control systems. Users can add supported modules from the module list, such as various processor modules (57C430A, 57C431, 57C435), digital/analog I/O modules, communication modules (network, remote I/O, Modbus, AB Link, etc.), and universal driver controller (UDC) modules.

Remote I/O configuration: By adding the 57C416 remote I/O interface module, the remote I/O network can be graphically expanded, remote racks or heads can be configured, and local heads, digital/analog tracks, etc. can be further attached to the remote heads to truly reflect the physical wiring structure.

General modules: For modules that are not directly supported or future hardware (marked as "external modules"), the software provides three types of general modules: GEN32, GEN32K, and GEN32KH, which allow users to allocate register space for variable mapping, ensuring system scalability and compatibility (subject to electrical and protocol requirements, see Appendix H of the manual for details).