Driver integration: For distributed power systems (DPS), UDC modules and their associated power module interfaces (PMI), analog/digital tracks, and other hardware can be configured, and detailed driver parameters can be directly set in the software, achieving seamless integration of driver control and logic control.
2. Variable Mapping and Data Management
Variable configuration is the bridge that connects hardware addresses with software logic. The variable configurator of V3.5 adopts a "form" format to customize the display of register structures for different modules.
Network variable configuration: This is the most complex part. For the 57C404 network interface module, in addition to basic settings and status register views, the core is the "Area 1-55 View". In this view, two names can be defined for each register/bit on the network:
Network global name: It uniquely identifies the data point throughout the entire network and is stored in a system level network database to prevent address conflicts and provide unified semantics.
Local name: The variable name used to access the data point within a specific rack.
The two can be linked. After linking, changing the network global name will be synchronized to all racks that use it through the network database, ensuring consistency in network data definition. This design ensures the rigor of global management while allowing flexibility in local programming.
3. Task programming and execution management
The task manager supports multitasking environments. Each AutoMax processor can run multiple tasks with different priorities and share data through common memory or network variables.
programming language
Ladder diagram logic: Using a dedicated PC editor, sequential logic programming is performed in traditional ladder diagram format, supporting standard elements such as contacts, coils, timers, counters, shift registers, and online monitoring and forcing.
Control Block Language: A function call set based on BASIC syntax, designed specifically for process control loops such as PID, integration, and hysteresis, suitable for AutoMax processors and UDC modules (with slightly different sentence sets supported).
Enhanced BASIC language: used for advanced programming such as complex algorithms, numerical processing, and human-machine interface (HMI) communication.
Compile and Download: BASIC and control block tasks need to be compiled into object code (. OBJ) and downloaded to the processor. The ladder diagram task is already in binary format (. PC) and can be downloaded directly.
Online operation: Through the "Online!" menu, engineers can connect to a running rack, perform loading configurations and tasks, start stop tasks, monitor and modify variable values (including tuning and forcing), real-time edit ladder programs (online editing), view processor and task error logs, and perform a series of key debugging and maintenance operations.
4. System security and documentation
Security level: The system provides multi-level access control based on key switch position (PROTECT/SETUP/PROGRAMM) and password, protecting configurations and tasks from unauthorized modifications.
Document integration: Systems, regions, racks, and tasks can all be associated with independent document files (. SDC,. CDC,. RDC,. TDC) for storing design specifications, maintenance notes, and other information, promoting knowledge management and project handover.
Cross reference report: It can generate detailed rack cross reference and network cross reference reports, listing the usage locations and hardware mapping relationships of all variables, and pointing out potential errors such as unconfigured variables, address conflicts, multitasking write conflicts, etc. It is a valuable tool for debugging and code review.
Compatibility and upgrade path
V3.5 fully considers users' existing investments and upgrade paths:
Backward compatibility: It is possible to convert AutoMax V1, V2 systems, and ASD V8. x systems to V3.5 database format through the "import" function, while preserving the original configuration, variables, and task source code as much as possible.
Operating system compatibility: There is a clear compatibility matrix between the programming executor version and the operating system version running on the rack processor. V3.5 actuators support operating systems from early V2.1B to the latest V3.5, but some advanced features may be limited by the version of the operating system in the rack.
Parallel installation: V3.5 can be installed on the same computer as previous versions of actuators (such as V2.x, V3.0A-V3.4E), and can be switched and used through different startup methods (icons or environment variables).
Key workflows in engineering practice
A typical AutoMax project development process is as follows:
Project Planning: Create a project structure (system, region, rack) in the System Configurator.
Hardware modeling: In the rack configurator, add all modules based on physical design, configure remote I/O network and drive parameters.
Data definition: In the variable configurator, allocate meaningful variable names and descriptions for all I/O points, network data exchange areas, and common memory, especially planning network global variables.