Eaton MTL F809F Plus DTM Operating Instructions

The default high pre alarm limit for device retransmission rate is about 0.1%, which is approximately equal to one retransmission per hour. The calculation of retransmission rate is divided into three stages: from 1 to 5000 PTs, the displayed value approaches the actual value from low to avoid initial false alarms; The accuracy gradually improves with 5000 to 100000 PT; After exceeding 100000 PTs, use moving average to suppress occasional events and respond to changes in communication performance. If a single device retransmits high on site, check the branch lines, connectors, water inlet, and the device itself; If multiple or all devices retransmit high, check if there is only one terminal on the segment or if the terminal has failed, and check the connection between the trunk cable, host, and trunk junction box.

In equipment alarms, if the signal low/low warning only affects one device, focus on checking branch lines and water damage; If multiple devices are affected, check the number of terminals and the segment for water ingress. If there is only one high pre alarm/alarm for retransmission, check the device communication; If there are multiple units, check the terminal and trunk lines. The retransmission rate alarm is a key indicator of the health of device communication, and should be compared with historical values during operation, not just absolute values. The device node can reset the retransmission and retransmission rate of the device using "Reset Retransmissions Count"; If the alarm has been locked and caused by retransmission, the alarm can be confirmed after reset. If there are no other alarms on the segment, it will be cleared.

Alarm limit optimization and maintenance strategy

The "Alarm Limits Optimization" wizard for segment TB can adjust the power low/high limit, noise high limit, device signal amplitude low/high limit, and select whether the device increases or decreases to trigger an alarm. After selecting the power supply model, the wizard provides low/high limits according to the model, such as F101 and F801, which are approximately 21.3 to 24.2V, F102, F6xx, F802, 918 * 1, which are approximately 27.7 to 30.2V, and 918 * 2, which are approximately 18.5 to 22.5V. For non list models, select custom and enter according to the data table. The signal amplitude is adjusted by the current value ± percentage. Only when the calculated low limit is higher than the current low limit and the high limit is lower than the current high limit, will it be accepted. Otherwise, the old value will be retained. The noise high limit is set according to the actual average value, and remains unchanged if the actual value exceeds the threshold listed in the table. All limits must be kept low ≤ low<high ≤ high high, with high being at least 1V (voltage) or 20mV (signal) higher than low.

Daily maintenance suggestion: After commissioning, manually upload first, then run alarm limit optimization, and finally upload once from the DCS engineering station to avoid template coverage; Use 'Private Print' as the debugging report, grouped by parameters and limits with the NE107 symbol; Compare the current value with the exported XML using 'Compare' to track whether the alarm limit has been changed; The trend function is completed by the FDT framework or asset management system and is not within DTM. For unmanned stations, enable latch alarms and confirm them regularly; For the segment being investigated, only scan that segment temporarily, and restore all active segments after completion to avoid missed monitoring.