5.2 Configuration example
Create a TTD log with a storage interval of 30 seconds and a capacity of 2 hours, and extend it to 4 hours in the historical server. Simultaneously, create a tiered log with a 1-minute average value. The process is as follows:
Create a History Log Template object in the Library Structure.
In its Log Template aspect, add a log with type Direct, and select TTD as the data source.
In the "TTD Data Collection" tab, set the "TTD log storage interval" to 30 seconds and the "TTD log value count" to 240.
Set the "History Log Value Count" to 480 to achieve a 4-hour history storage.
Add a log of type Hierarchical, define its aggregation method as Time Average, set the storage interval to 1 minute, and specify a capacity of 24 hours.
On the target process object, add the Log Configuration aspect and apply this template to its VALUE attribute.
Finally, by executing the download through the Synchronize View of the TTD Node Configuration aspect, this log can be created and activated in the controller.
6. System Management and Performance Optimization 6.1 System Status Monitoring
The System Status Viewer aspect is a powerful tool for troubleshooting. It can be applied at multiple levels:
Network layer: Displays the communication status of all nodes on the MB300 network.
Controller node layer: Displays the hardware status within the controller, such as I/O modules, power supplies, fans, batteries, etc. On the AC 450 controller, the Local Devices graphical display provides an intuitive view for hardware diagnostics.
Service structure layer: Displays the operational status of various system services, such as the MasterBus 300 RTA Management Service.
6.2 Performance considerations
To optimize the load of the RTA board and MB300 network, the following guidelines must be followed:
Data Subscription: Only use update rates of 1, 3, and 9 seconds for attributes that support circular subscription. The list of attributes eligible for circular subscription is provided in the appendix. Subscribing to a faster update rate (<1 second) can significantly increase system load.
OPC Log: It is recommended to use a 9-second cyclic subscription. If a longer sampling time (such as more than 2 minutes) is required, a non-cyclic subscription can be used.
Write operation: Only write operations to DAT objects are supported. Frequent writes can significantly increase the CPU load of the controller.
CPU Load Monitoring: The CPU load of the RTA board can be monitored in real-time by using the ANPER - SYSTEM LOAD command in the command line of the RTA board. It is recommended to keep this load below 50%.
6.3 Backup and recovery
RTA Board Configuration: After modifying the configuration of the RTA board (such as event processing text), you must click the RTA Board Backup button in the RTA Board Configuration tab to save the configuration to a local file. These files are located in ProgramDataABBAC400ConnectAdvantBaseDataRTAInit. It is recommended to regularly back up these files.
Central Backup: Starting from Feature Pack, the system provides the Advant Master Central Backup function, allowing centralized backup and recovery of the AMPL application on the controller. The backup is defined in the Maintenance Structure and supports both manual and scheduled tasks. The backup files are stored in the standard DUAP format.
