8.1.1 Diagnostic
8.1.1.1 Diagnostic buffer
- The diagnostic buffer is part of the CPU system memory. The diagnostics buffer contains errors detected by the CPU or modules with diagnostics functionality. This includes events such as CPU per mode switching, hardware plugging and unplugging
8.1.1.2 Open diagnostic buffer
premise
- Create a project
- Add a PLC device
- In online mode
- Double-click the Online Diagnostics column under the Debug column in the Project Tree to display the Online Diagnostics page in the main window, and click the Diagnostics Buffer column under the Diagnostics column in the Online Diagnostics page to jump to the Diagnostics Buffer page
8.1.1.3 Error level
- Error levels are criteria used to classify and identify different types of errors that occur in software, systems, or processes. These levels are typically defined based on the error's severity, impact on the system, and user or operator experience
NOTE
- Error levels are divided into four levels: 0-3, corresponding to normal, warning, error, and fatal
- The error levels, event abbreviations and other displays of the diagnostic buffer have their respective meanings as shown in the following table:
| Error level | Event abbreviation | Event number | Detailed description |
|---|---|---|---|
| 0 | Cancel PLC password protection | 0x1000 | 0 user cancels PLC password protection function |
| 0 | Turn on PLC password protection | 0x1001 | 0 user turns on PLC password protection function |
| 0 | Set admin password | 0x1002 | The admin password has been changed to non-empty |
| 0 | PLC software downloaded successfully | 0x1003 | PLC software downloaded successfully |
| 2 | PLC software download failed | 0x1004 | PLC software download failed |
| 0 | PLC hardware download successful | 0x1005 | PLC hardware download successful |
| 2 | PLC hardware download failed | 0x1006 | PLC hardware download failed |
| 3 | PLC abnormal power outage | 0x1007 | PLC abnormal power outage |
| 3 | Failed to read SD card | 0x1008 | Failed to read SD card |
| 0 | User clears PLC program | 0x1009 | User clears PLC program |
| 1 | The network service exited abnormally | 0x100A | The network service exited abnormally |
| 1 | COMM exited abnormally | 0x100B | COMM exited abnormally |
| 1 | PRG exited abnormally | 0x100C | PRG exited abnormally |
| 2 | PLC software download failed | 0x2004 | Download error: The program unit 1 in task 0 does not exist in the PLC and the download is refused |
| 2 | PLC software download failed | 0x2006 | Download error: The PLC has insufficient memory and the download is refused |
| 1 | PLC forced value write warning | 0x2008 | Forced value write warning: Variable 0 does not exist in the PLC |
| 1 | PLC forced value write warning | 0x2009 | Forced value write warning: Variable 0 is repeatedly set to a write value |
| 2 | PLC forced value writing failed | 0x2010 | Forced value writing error: Variable 0 was repeatedly set to a permanent value |
| 2 | PLC diagnostic log recovery failed | 0x2011 | Diagnostic log recovery failed: The diagnostic backup data is damaged |
| 2 | PLC array access exception | 0x2012 | Program unit "0" is at row 1 and column 2, trying to access the array "3" of type "4" with an index value of The element of 5 triggers an out-of-bounds exception |
| 2 | The programming error task is not configured | 0x2013 | The array out-of-bounds behavior is recognized, but there is no programming error program to process it, and the CPU status changes to STOP |
| 2 | The task timed out three times in a row | 0x2014 | Task "0" timed out three times in a row, and the CPU status changed to STOP |
| 2 | The execution timeout task is not configured | 0x2015 | The task "0" has a timeout behavior, but there is no execution timeout program to process it, and the CPU status changes to STOP |
| 1 | A task execution timeout exception occurred | 0x2016 | The execution end time of task "0" exceeded the set watchdog time, triggering a timeout exception |
| 1 | Execution cycle skip behavior occurred | 0x2017 | The actual execution time of task "0" exceeded the set cycle time, and the number of cycle skip behaviors occurred "1" |
| 2 | The number of call nesting levels exceeds 16, PLC STOP | 0x2018 | Program error: The number of call nesting levels for program unit 1 in task 0 exceeds the maximum allowed 16 levels, and PLC enters STOP |
| 0 | Start LocalIO | 0x3800 | LocalIO information: Start the Local IO system |
| 0 | The lbus driver was opened successfully | 0x3801 | LocalIO information: The lbus driver was opened successfully, no errors |
| 2 | Invalid pointer | 0x3802 | LocalIO information: Invalid pointer, the parameter to open the lbus driver function is a null pointer |
| 2 | Invalid parameter | 0x3803 | LocalIO information: The incoming parameter is incorrect |
| 2 | No memory | 0x3804 | LocalIO information: Memory allocation failed, or memory mapping failed |
| 2 | Failed to open the device | 0x3805 | LocalIO information: Failed to open the device. This error occurs when the execution of the Linux system call fails or the related onboard IO device fails to be opened |
| 2 | Error opening lbus driver | 0x3806 | LocalIO information: Unable to open lbus driver |
| 2 | Invalid onboard IO type | 0x3807 | OnboardIO information: Invalid onboard IO type, this error is generated when PWM/PTO output to input pin |
| 2 | Invalid onboard IO mode | 0x3808 | OnboardIO information: Invalid onboard IO mode. This error occurs when the opened onboard IO handle is PTO/PWM, but it will use the PWM/PTO function |
| 2 | Invalid PTO mode | 0x3809 | OnboardIO information: Invalid PTO mode |
| 2 | Pin exceeds limit | 0x380a | OnboardIO information: The bound pin exceeds the limit. For T3, there are only 0~15 onboard IOs. This will occur when the pin binding under PTO/PWM/HSC exceeds this limit. mistake |
| 2 | Pin setting error | 0x380b | OnboardIO information: Pin setting error. This error occurs when binding a pulse output pin to an input pin |
| 2 | Error getting current time | 0x380c | LocalIO information: Error getting current time, this may be the reason when handshake times out |
| 2 | The number of process data exceeds the limit | 0x380d | LocalIO information: The number of process data exceeds the limit, and the number of process data with exchange needs to be reduced |
| 2 | Handshake timeout | 0x380e | LocalIO information: Handshake timeout, this is usually an internal FPGA error |
| 2 | Process data exchange error | 0x380f | LocalIO information: Process data exchange error, possibly due to handshake timeout |
| 2 | No module is configured | 0x3810 | LocalIO information: No module is configured |
| 2 | Type mismatch | 0x3811 | LocalIO information: Type mismatch, hardware component unavailable |
| 0 | Reconfiguring hardware components | 0x3812 | LocalIO information: Types match and hardware components are available after reconfiguration |
| 2 | Hardware component removed or missing | 0x3813 | LocalIO information: Hardware component removed or cannot be addressed |
| 0 | Reconnect the hardware component | 0x3814 | LocalIO information: The hardware component has been reconnected |
| 2 | Site not set up | 0x3815 | LocalIO information: Site not set up |
| 2 | Function not yet supported | 0x3816 | LocalIO information: Function not yet supported |
| 0 | Power information of LocalIO | 0x3817 | LocalIO information: Power status information of the LocalIO module (normal power on, abnormal) |
| 1 | PWM configuration exceeds hardware limits | 0x3818 | OnboardIO information: PWM configuration exceeds hardware limits. For example, the pulse width of the configured PWM pulse generator is less than the period adjustment accuracy |
| 1 | The number of LocalIO modules does not match | 0x3819 | LocalIO information: The number of modules configured in LocalIO is inconsistent with the number of modules scanned |
| 2 | OnboardIO has no relevant configuration | 0x381a | OnboardIO information: OnboardIO has no configured IO type |
| 2 | OnboardIO initialization failed | 0x381b | OnboardIO information: OnboardIO initialization failed |
| 2 | LocalIO initialization failed | 0x381c | LocalIO information: LocalIO initialization failed |
| 2 | OnboardIO BIO initialization failed | 0x381d | OnboardIO information: OnboardIO BIO initialization failed |
| 2 | OnboardIO HSC initialization failed | 0x381e | OnboardIO information: OnboardIO HSC initialization failed |
| 2 | OnboardIO PWM initialization failed | 0x381f | OnboardIO information: OnboardIO PWM initialization failed |
| 2 | OnboardIO PTO initialization failed | 0x3820 | OnboardIO information: OnboardIO PTO initialization failed |
| 2 | lbus failed to send data packet | 0x3821 | LocalIO information: lbus failed to send data packet |
| 2 | lbus failed to receive data packet | 0x3822 | LocalIO information: lbus failed to receive data packet |
| 0 | Shut down LocalIO | 0x3823 | LocalIO information: Shut down the Local IO system |
| 1 | Start PNIO event | 0x3C00 | Start Profinet IO system event |
| 1 | Channel disappears (new channel appears) | 0x3C01 | PN driver warning: Diagnostic alarm, channel disappears (new channel appears) |
| 1 | There is a problem outside the device | 0x3C02 | PN driver warning: Process alarm, there is a problem outside the device, such as excessive temperature |
| 2 | The module (submodule) is pulled out | 0x3C03 | PN driver error: pull out alarm, the module (submodule) is pulled out |
| 0 | Module (submodule) is loaded | 0x3C04 | PN driver notification: Loading alarm, module (submodule) is loaded |
| 1 | The status of the module (submodule) changes | 0x3C05 | PN driver warning: Status alarm, the status of the module (submodule) changes |
| 1 | The parameters of the module (submodule) have changed | 0x3C06 | PN driver warning: Update alarm, the parameters of the module (submodule) have changed |
| 1 | Application relationship redundancy changes | 0x3C07 | PN driver warning: Redundancy alarm, application relationship redundancy changes |
| 1 | The IO device is controlled by the monitor | 0x3C08 | PN driver warning: Monitor control alarm, the IO device is controlled by the monitor |
| 1 | IO device control is released | 0x3C09 | PN driver warning: Monitor release alarm, IO device control is released |
| 1 | Wrong module (submodule) was loaded | 0x3C0A | PN driver warning: Load error alert, the loaded module (submodule) is wrong and not required |
| 0 | The device establishes data communication again | 0x3C0B | PN driver notification: The submodule returns to the alarm, the device can re-provide valid data or the output unit can re-process the received data |
| 1 | Details disappeared | 0x3C0C | PN driver warning: Diagnosis disappeared alarm, details disappeared |
| 1 | There is a problem with multipoint communication | 0x3C0D | PN driver warning: Multipoint communication mismatch alarm, there is a problem with multipoint communication |
| 1 | Port data changes | 0x3C0E | PN driver warning: Port data change alarm, port data changes, such as connection or disconnection |
| 1 | Clock synchronization has changed | 0x3C0F | PN driver warning: Data synchronization change alarm, clock synchronization has changed |
| 1 | There is a problem with the synchronization application | 0x3C10 | PN driver warning: Isochronous mode problem alert, there is a problem with the synchronization application |
| 1 | There is a problem with the network component | 0x3C11 | PN driver warning: Network component problem alarm, there is a problem with the network component, such as frame loss due to resource bottlenecks |
| 1 | Time synchronization has changed | 0x3C12 | PN driver warning: Time data change alarm, time synchronization has changed |
| 1 | There is a problem with dynamic frame encapsulation | 0x3C13 | PN driver warning: Dynamic frame encapsulation alarm, there is a problem with the dynamic frame encapsulation operation process |
| 1 | There is a problem with the media redundancy operation that supports planned frame replication | 0x3C14 | PN driver warning: MRPD alert, there is a problem with the media redundancy operation that supports planned frame replication |
| 1 | Inconsistent parameter settings | 0x3C15 | PN driver warning: Inconsistent parameter settings affect multiple interfaces |
| 1 | Connect to upload and save display | 0x3C16 | PN driver warning: Upload and save alert, Connect to upload and save display |
| 1 | The module was pulled out | 0x3C17 | PN driver warning: Module pulled out alarm, the module was pulled out |
| 2 | Disconnected from IO device | 0x3C18 | PN driver error: Device failure alarm, application relationship with IO device is released (device number: 0) |
| 0 | Establish a connection with the IO device | 0x3C19 | PN driver notification: Device reconnection alarm, the application relationship with the IO device is established (device number: 0) |
| 1 | Short circuit | 0x3C1A | PN driver warning: short circuit |
| 1 | Voltage is too low | 0x3C1B | PN driver warning: Voltage is too low |
| 1 | Voltage is too high | 0x3C1C | PN driver warning: Voltage is too high |
| 1 | Overload | 0x3C1D | PN driver warning: Overload |
| 1 | The temperature is too high | 0x3C1E | PN driver warning: The temperature is too high |
| 1 | Broken line | 0x3C1F | PN driver warning: Broken line |
| 1 | Higher than the upper limit | 0x3C20 | PN driver warning: Higher than the upper limit |
| 1 | Below the lower limit | 0x3C21 | PN driver warning: Below the lower limit |
| 1 | Error | 0x3C22 | PN driver warning: Device error |
| 1 | Simulation activation | 0x3C23 | PN driver warning: Simulation activation |
| 1 | The channel is missing parameters | 0x3C24 | PN driver warning: The channel is missing parameters, the parameters are not written or underwritten |
| 1 | Parameter setting error | 0x3C25 | PN driver warning: Parameter setting error, incorrect or too many parameters are written |
| 1 | Power supply failure | 0x3C26 | PN driver warning: Power supply failure |
| 1 | Fuse blown | 0x3C27 | PN driver warning: Fuse blown |
| 1 | Communication failure | 0x3C28 | PN driver warning: Communication failure, sequence error |
| 1 | Ground fault | 0x3C29 | PN driver warning: Ground fault |
| 1 | Reference point lost | 0x3C2A | PN driver warning: Reference point lost |
| 1 | Process event loss/sampling error | 0x3C2B | PN driver warning: Process event loss/sampling error |
| 1 | Threshold warning | 0x3C2C | PN driver warning: Threshold warning |
| 1 | Output is off | 0x3C2D | PN driver warning: Output is off |
| 1 | Functional safety event | 0x3C2E | PN driver warning: Functional safety event |
| 1 | External fault | 0x3C2F | PN driver warning: External fault |
| 1 | Temporary failure | 0x3C30 | PN driver warning: Temporary failure |
| 1 | Security destination address mismatch | 0x3C31 | PN driver warning: Security destination address mismatch |
| 1 | Invalid security destination address | 0x3C32 | PN driver warning: Invalid security destination address |
| 1 | Security source address is invalid or does not match | 0x3C33 | PN driver warning: Security source address is invalid or does not match |
| 1 | The safety watchdog time is set to 0 ms | 0x3C34 | PN driver warning: The safety watchdog time is set to 0 ms |
| 1 | Parameter "F_SIL" exceeds the SIL value applied by the device | 0x3C35 | PN driver warning: Parameter "F_SIL" exceeds the SIL value applied by the device |
| 1 | Parameter "F_CRC_Length" does not match the generated value | 0x3C36 | PN driver warning: Parameter "F_CRC_Length" does not match the generated value |
| 1 | Wrong version of F parameter | 0x3C37 | PN driver warning: Wrong version of F parameter |
| 1 | The data in the received F parameter block is inconsistent (CRC1 error) | 0x3C38 | PN driver warning: The data in the received F parameter block is inconsistent (CRC1 error) |
| 1 | Device diagnostic information | 0x3C39 | PN driver warning: Device specific or non-specific diagnostic information |
| 1 | The watchdog time for saving dynamic parameters has been exceeded | 0x3C3A | PN driver warning: The watchdog time for saving dynamic parameters has been exceeded |
| 1 | Watchdog time for repairing dynamic parameters exceeded | 0x3C3B | PN driver warning: Watchdog time for repairing dynamic parameters exceeded |
| 1 | Dynamic parameters are inconsistent (iParCRC error) | 0x3C3C | PN driver warning: Dynamic parameters are inconsistent (iParCRC error) |
| 1 | The F_Block_ID is not supported | 0x3C3D | PN driver warning: The fail-safe data block ID (F_Block_ID) is not supported |
| 1 | Transmission error: Data inconsistent | 0x3C3E | PN driver warning: Transmission error: Data inconsistent (CRC2 error) |
| 1 | Transmission error: Timeout | 0x3C3F | PN driver warning: Transmission error: Timeout (watchdog time (F_WD_Time or F_WD_Time_2) exceeded) |
| 1 | Unable to transfer data | 0x3C40 | PN driver warning: Unable to transfer data |
| 1 | The remote device is not suitable | 0x3C41 | PN driver warning: The remote device is not suitable |
| 1 | Media redundancy is not suitable | 0x3C42 | PN driver warning: Media redundancy is not suitable |
| 1 | Synchronization mismatch | 0x3C43 | PN driver warning: Synchronization mismatch |
| 1 | Sync pattern mismatch | 0x3C44 | PN driver warning: Sync pattern mismatch |
| 1 | Multipoint communication is not suitable | 0x3C45 | PN driver warning: Multipoint communication is not suitable |
| 1 | Fiber link information | 0x3C46 | PN driver warning: Fiber link information |
| 1 | A network function problem occurred | 0x3C47 | PN driver warning: A network function problem occurred |
| 1 | The time master does not exist or there is an accuracy problem | 0x3C48 | PN driver warning: The time master does not exist or there is an accuracy problem |
| 1 | A dynamic frame encapsulation problem occurred | 0x3C49 | PN driver warning: A dynamic frame encapsulation problem occurred |
| 1 | A media redundancy problem has occurred supporting planned frame replication | 0x3C4A | PN driver warning: A media redundancy problem has occurred supporting planned frame replication |
| 1 | Information about multiple interface problems | 0x3C4B | PN driver warning: Information about multiple interface problems |
| 1 | Applies to diagnostic propagation in hierarchical structures | 0x3C4C | PN driver warning: Applies to diagnostic propagation in hierarchical structures |
| 1 | Connection status mismatch - connection disconnected | 0x3C4D | PN driver warning: Connection status mismatch - connection disconnected |
| 1 | Media attachment unit type mismatch | 0x3C4E | PN driver warning: Media attachment unit (MAU, Medium Attachment Unit) type mismatch |
| 1 | Line delay mismatch | 0x3C4F | PN driver warning: Line delay mismatch |
| 1 | Station's peer name does not match | 0x3C50 | PN driver warning: Station's peer name does not match |
| 1 | Peer port mismatch | 0x3C51 | PN driver warning: Peer port mismatch |
| 1 | Peer RT_CLASS_3 mismatch | 0x3C52 | PN driver warning: Peer RT_CLASS_3 mismatch |
| 1 | Peer media connection unit type mismatch | 0x3C53 | PN driver warning: Peer media connection unit type mismatch |
| 1 | Peer media redundancy domain mismatch | 0x3C54 | PN driver warning: Peer media redundancy domain mismatch |
| 1 | Peer device not detected | 0x3C55 | PN driver warning: Peer device not detected |
| 1 | Peer line delay mismatch | 0x3C56 | PN driver warning: Peer line delay mismatch |
| 1 | Peer PTCP mismatch | 0x3C57 | PN driver warning: Peer PTCP mismatch |
| 1 | Peer-to-peer preamble length mismatch | 0x3C58 | PN driver warning: Peer-to-peer preamble length mismatch |
| 1 | Peer shard mismatch | 0x3C59 | PN driver warning: Peer shard mismatch |
| 1 | Manager role failed | 0x3C5A | PN driver warning: Manager role failed |
| 1 | Media redundancy ring open | 0x3C5B | PN driver warning: Media redundancy ring open |
| 1 | Multiple Managers | 0x3C5C | PN Driver Warning: Multiple Managers |
| 1 | Dedicated partner ring port lost | 0x3C5D | PN driver warning: Dedicated partner ring port lost |
| 1 | No synchronization information received | 0x3C5E | PN driver warning: No synchronization information received |
| 1 | Jitter out of bounds | 0x3C5F | PN driver warning: Jitter out of bounds |
| 1 | Output time failed | 0x3C60 | PN driver warning: Output time failed - output update missing or out of order |
| 1 | Failed to enter time | 0x3C61 | PN driver warning: Failed to enter time |
| 1 | Master device signal error | 0x3C62 | PN driver warning: Master device signal error - Master device signal update error detected |
| 1 | Multicast consumer communication timeout | 0x3C63 | PN driver warning: Multicast consumer communication timeout |
| 1 | Address resolution failed | 0x3C64 | PN driver warning: Address resolution failed |
| 1 | Energy budget | 0x3C65 | PN driver warning: Energy budget |
| 1 | Frame dropped | 0x3C66 | PN driver warning: dropped frame - no resources |
| 1 | A frame delay error occurred with frame ID "0x0100" | 0x3C67 | PN driver warning: A frame delay error occurred with frame ID "0x0100" |
| 1 | A frame delay error occurred with frame ID "0x0FFF" | 0x3C68 | PN driver warning: A frame delay error occurred with frame ID "0x0FFF" |
| 1 | The media redundancy duplication that supports planned frame replication for frame ID "0x0700" is invalid | 0x3C69 | PN driver warning: The media redundancy duplication that supports planned frame replication for frame ID "0x0700" is invalid |
| 1 | Media redundancy duplication that supports planned frame replication for frame ID "0x0FFF" is invalid | 0x3C6A | PN driver warning: Media redundancy duplication that supports planned frame replication for frame ID "0x0FFF" is invalid |
| 1 | Standard gateway does not match | 0x3C6B | PN driver warning: Standard gateway does not match |
| 1 | The interface station name is unclear | 0x3C6C | PN driver warning: The interface station name is unclear |
| 1 | The IP address range of the interface is unclear | 0x3C6D | PN driver warning: The IP address range of the interface is unclear |
| 1 | MultipleInterfaceMode.NameOfDevice mode conflict | 0x3C6E | PN driver warning: Multiple interface device name (MultipleInterfaceMode.NameOfDevice) mode conflict |
| 1 | Dependent entity information | 0x3C6F | PN driver warning: Dependent entity information |
| 2 | The device is missing a module | 0x3C70 | PN driver warning: The configuration is different from the actual topology (modules are missing) |
| 2 | Device equipped with module error | 0x3C71 | PN driver error: The configuration is different from the actual topology (module error) |
| 2 | Device equipped with submodule error | 0x3C72 | PN driver error: The configuration is different from the actual topology (submodule error) |
| 1 | End PNIO event | 0x3C73 | PN driver warning: End Profinet IO system event |
| 0 | Start CPU | 0x3000 | Start system and CPU |
| 0 | The CPU mode is the simulated PLC mode | 0x3001 | The CPU mode is the simulated PLC mode, simulating real hardware |
| 1 | In the simulated PLC mode, the real hardware IO system is not supported | 0x3002 | The CPU mode is the simulated PLC mode and the real hardware IO system is not supported |
| 0 | Total time data in the CPU core | 0x3003 | Controls the CPU time data status |
| 0 | Set system time successfully | 0x3101 | NTP server is not connected, manual time setting is successful |
| 1 | Failed to set system time | 0x3102 | The NTP server is connected and manual time setting failed |
| 0 | Whether to enable NTP server | 0x3103 | Enable NTP server set to 0 |
| 0 | Set time zone | 0x3104 | Time zone set to 0 |
| 0 | Set the NTP minimum polling time | 0x3105 | The NTP minimum polling interval is set to 0 |
| 0 | Set the NTP maximum polling time | 0x3106 | The NTP maximum polling interval is set to 0 |
| 0 | Set NTP server | 0x3107 | NTP server is set to 0 |
| 1 | The setting of time is not supported in the simulation PLC mode | 0x3108 | The CPU mode is the simulation PLC mode, and the setting of time and other information is not supported |
| 0 | Total diagnostic information of CPU network configuration | 0x3109 | Control CPU network status |
| 0 | IP address modification | 0x3201 | CPU 0: The IP address of network port 0 is modified to 1 |
| 1 | Network control is not supported in simulated PLC mode | 0x3202 | The CPU mode is simulated PLC mode and network control is not supported |
| 0 | Network port insertion status | 0x3203 | CPU information: 0 The network port is considered to be inserted or activated |
| 1 | Network port plug-in status | 0x3204 | CPU information: 0 The network port is considered to be unplugged or inactive |
| 2 | IP conflict | 0x3205 | CPU information: Set the IP of 0 network port to 1, 1 is already occupied |
| 0 | Gateway modification | 0x3206 | CPU information: The gateway of network port 0 is modified to 1 |
| 0 | Total diagnostic information of the LED light | 0x3207 | Control the status of the LED light |
| 0 | Total diagnostic information of CPU configuration | 0x3208 | CPU configuration information |
| 0 | SD card total diagnostic information | 0x3209 | Control SD card status |
| 0 | Insert SD card | 0x3501 | The SD card is inserted and the PLC is about to restart |
| 3 | Remove SD card | 0x3502 | The SD card has been removed, the error code is 3502, and the PLC is about to restart |
| 3 | Start without SD card | 0x3504 | There is no SD card when starting the PLC, the error code is 3504 |
| 3 | SD card format error | 0x3505 | SD card format error, error code is 3505 |
| 0 | Total diagnostic information of the CPU state machine | 0x3506 | Control the diagnostic information of the CPU state machine |
| 0 | CPU status change information | 0x3601 | CPU information: System initialization changes the CPU status from 0 to 1 |
| 0 | CPU status change information | 0x3602 | CPU information: Turn the switch to change the CPU status from 0 to 1 |
| 0 | CPU status change information | 0x3603 | CPU information: The user interface modified the CPU status from 0 to 1 |
| 1 | CPU status change information | 0x3604 | CPU information: The switch is off and the CPU status cannot be modified through the user interface |
| 0 | Shut down the CPU | 0x3605 | The system is finished and the CPU is shut down |
| 0 | Start EtherCAT | 0x4000 | EtherCAT IO system started successfully |
| 0 | Available network port information | 0x4001 | EtherCAT bus configuration notification, currently available network port information |
| 0 | Socket communication closed | 0x4002 | EtherCAT bus configuration notification |
| 0 | Initialization command successful | 0x4003 | EtherCAT bus configuration notification |
| 0 | No readable process data | 0x4004 | EtherCAT bus configuration notification |
| 0 | DC Sync | 0x4005 | EtherCAT bus configuration notification |
| 0 | State transition | 0x4006 | EtherCAT bus configuration notification |
| 0 | No slave found | 0x4007 | EtherCAT bus configuration notification |
| 0 | The slave station was discovered and configured | 0x4008 | EtherCAT bus configuration notification, the bus discovered the slave station and configured it successfully |
| 0 | Reconfigure slave | 0x4009 | EtherCAT bus configuration notification, slave has been successfully reconfigured after being lost |
| 0 | Successfully wake up the slave station | 0x400a | EtherCAT bus configuration notification, the slave station has been successfully woken up after being lost |
| 1 | State transition | 0x400b | EtherCAT bus configuration warning, the slave did not transition to the specified state |
| 1 | Slave found | 0x400c | EtherCAT bus configuration warning, missing slave found |
| 2 | The network port cannot be used | 0x400d | The EtherCAT bus configuration is wrong and the current network port cannot be used |
| 2 | Initialization failed | 0x400e | EtherCAT bus configuration error, bus initialization failed |
| 2 | Failed to create socket | 0x400f | EtherCAT bus configuration error, failed to create socket communication, please run with root privileges |
| 2 | State transition failed | 0x4010 | EtherCAT bus configuration error, the bus cannot transition to the specified state |
| 2 | The attempt to execute the command failed | 0x4011 | The EtherCAT bus configuration error, the bus failed to attempt to execute the command |
| 2 | wkc error | 0x4012 | EtherCAT bus configuration error, bus execution command returns wkc error |
| 2 | Initialization command timeout | 0x4013 | EtherCAT bus configuration error, bus initialization command failed |
| 2 | No slaves found | 0x4014 | EtherCAT bus configuration error, no configurable slaves |
| 2 | The number of slave stations is wrong | 0x4015 | The EtherCAT bus configuration is wrong, the number of slave stations on the upper and lower computers is inconsistent |
| 2 | Same address error | 0x4016 | EtherCAT bus configuration error, slave configuration address is duplicated |
| 2 | Invalid address error | 0x4017 | EtherCAT bus configuration error, slave has invalid address |
| 2 | Slave initialization failed | 0x4018 | EtherCAT bus configuration error, slave initialization failed |
| 2 | Slave station lost error | 0x4019 | EtherCAT bus configuration error, slave station lost |
| 2 | Configuration IO mapping error | 0x401a | EtherCAT bus configuration error, IO mapping error |
| 2 | Application layer status code error | 0x401b | EtherCAT bus configuration error, application layer status code error |
| 2 | RxPDO does not match the address requirements | 0x401c | EtherCAT bus configuration error, RxPDO does not match the slave address requirements |
| 2 | TxPDO does not match the address requirements | 0x401d | EtherCAT bus configuration error, TxPDO does not match the address requirements |
| 2 | Reading SDO returns wkc error | 0x401e | EtherCAT bus configuration error, reading SDO returns wkc error |
| 2 | The number of slaves does not match the number of SDOs read | 0x401f | EtherCAT bus configuration error, the number of slaves does not match the number of SDOs read |
| 2 | Writing SDO returns wkc error | 0x4020 | EtherCAT bus configuration error, writing SDO returns wkc error |
| 2 | The number of slave stations does not match the number of written SDOs | 0x4021 | The EtherCAT bus configuration error, the number of slave stations does not match the number of written SDOs |
| 1 | The number of slave stations on the upper and lower computers is inconsistent | 0x4022 | EtherCAT bus configuration warning, the number of slave stations on the upper and lower computers is inconsistent |
| 2 | EtherCAT SDO common error | 0x40ff | SDO common error code |
| 2 | SDO communication is normal | 0x4100 | SDO communication is normal |
| 2 | The switching bit has not changed | 0x4101 | EtherCAT SDO communication error, the switching bit has not changed, error code 0x05030000 |
| 2 | Protocol time timeout | 0x4102 | EtherCAT SDO communication error, protocol timeout, error code 0x05040000 |
| 2 | The client\server command code is invalid or unknown | 0x4103 | EtherCAT SDO communication error, the client\server command code is invalid or unknown, error code 0x05040001 |
| 2 | Memory overflow | 0x4104 | EtherCAT SDO communication error, memory overflow, error code 0x05040005 |
| 2 | The object does not support access | 0x4105 | EtherCAT SDO communication error, the object does not support access, error code 0x06010000 |
| 2 | Trying to read a write-only object | 0x4106 | EtherCAT SDO communication error, trying to read a write-only object, error code 0x06010001 |
| 2 | Trying to write a read-only object | 0x4107 | EtherCAT SDO communication error, trying to write a read-only object, error code 0x06010002 |
| 2 | The sub-index cannot be written, SI0 must be 0 before writing | 0x4108 | EtherCAT SDO communication error, the sub-index cannot be written, SI0 must be 0 before writing, error code 0x06010003 |
| 2 | SDO full access does not support variable length objects | 0x4109 | EtherCAT SDO communication error, SDO full access does not support variable length objects, error code 0x06010004 |
| 2 | The object data length exceeds the mailbox data length | 0x410a | EtherCAT SDO communication error, the object data length exceeds the mailbox data length, error code 0x06010005 |
| 2 | Mapping to RxPDO object, SDO download blocked | 0x410b | EtherCAT SDO communication error, mapped to RxPDO object, SDO download blocked, error code 0x06010006 |
| 2 | The object is not in the object dictionary | 0x410c | EtherCAT SDO communication error, the object is not in the object dictionary, error code 0x06020000 |
| 2 | The object cannot be mapped to PDO | 0x410d | EtherCAT SDO communication error, the object cannot be mapped to PDO, error code 0x06040041 |
| 2 | The number and length of mapping objects will exceed the length of PDO | 0x410e | EtherCAT SDO communication error, the number and length of mapping objects will exceed the length of PDO, error code 0x06040042 |
| 2 | General parameters are incompatible | 0x410f | EtherCAT SDO communication error, general parameters are incompatible, error code 0x06040043 |
| 2 | Internal incompatibility of the device | 0x4110 | EtherCAT SDO communication error, internal incompatibility of the device, error code 0x06040043 |
| 2 | Access failed due to hardware reasons | 0x4111 | EtherCAT SDO communication error, access failed due to hardware reasons, error code 0x06060000 |
| 2 | Data type does not match, service parameter length does not match | 0x4112 | EtherCAT SDO communication error, data type does not match, parameter length does not match, error code 0x06070010 |
| 2 | Data type mismatch, parameter length is too long | 0x4113 | EtherCAT SDO communication error, data type mismatch, parameter length is too long, error code 0x06070012 |
| 2 | Data type mismatch, parameter length is too short | 0x4114 | EtherCAT SDO communication error, data type mismatch, parameter length is too short, error code 0x06070013 |
| 2 | Subindex does not exist | 0x4115 | EtherCAT SDO communication error, subindex does not exist, error code 0x06090011 |
| 2 | The write operation exceeds the data range of the parameter | 0x4116 | EtherCAT SDO communication error, the write operation exceeds the data range of the parameter, error code 0x06090030 |
| 2 | The parameter value is too large | 0x4117 | EtherCAT SDO communication error, the parameter value is too large, error code 0x06090031 |
| 2 | The parameter value is too small | 0x4118 | EtherCAT SDO communication error, the parameter value is too small, error code 0x06090032 |
| 2 | The maximum value is less than the minimum value | 0x4119 | EtherCAT SDO communication error, the maximum value is less than the minimum value, error code 0x06090031 |
| 2 | General error | 0x411a | EtherCAT SDO communication error, general error, error code 0x08000000 |
| 2 | Data cannot be sent or stored to the application | 0x411b | EtherCAT SDO communication error, data cannot be sent or stored to the application, error code 0x08000020 |
| 2 | Data cannot be sent to or stored in the application due to local control | 0x411c | EtherCAT SDO communication error, data cannot be sent to or stored in the application due to local control, error code 0x08000021 |
| 2 | Data cannot be sent to or stored in the application due to the current device status | 0x411d | EtherCAT SDO communication error, data cannot be sent to or stored in the application due to the current device status, error code 0x08000022 |
| 2 | The dynamic generation of the object dictionary failed or there is no object dictionary | 0x411e | EtherCAT SDO communication error, the dynamic generation of the object dictionary failed or there is no object dictionary, error code 0x08000023 |
| 2 | Unknown error | 0x411f | EtherCAT SDO communication error, unknown error, error code 0xffffffff |
| 2 | SOE common error | 0x41ff | EtherCAT SOE communication error, SOE common error |
| 2 | SOE works normally | 0x4200 | EtherCAT SOE communication is normal, SOE works normally, error code 0x0000 |
| 2 | No IDN | 0x4201 | EtherCAT SOE communication error, no IDN, error code 0x1001 |
| 2 | The object access is invalid | 0x4202 | EtherCAT SOE communication error, the object access is invalid, error code 0x1009 |
| 2 | Unnamed | 0x4203 | EtherCAT SOE communication error, unnamed, error code 0x2001 |
| 2 | The name transmitted is too short | 0x4204 | EtherCAT SOE communication error, the name transmitted is too short, error code 0x2002 |
| 2 | The name transmitted is too long | 0x4205 | EtherCAT SOE communication error, the name transmitted is too long, error code 0x2003 |
| 2 | The name is read-only and cannot be changed | 0x4206 | EtherCAT SOE communication error, the name is read-only and cannot be changed, error code 0x2004 |
| 2 | The name is write-protected at this time | 0x4207 | EtherCAT SOE communication error, the name is write-protected at this time, error code 0x2005 |
| 2 | Attribute transmission is too short | 0x4208 | EtherCAT SOE communication error, attribute transmission is too short, error code 0x3002 |
| 2 | The attribute transmission is too long | 0x4209 | EtherCAT SOE communication error, the attribute transmission is too long, error code 0x3003 |
| 2 | The attribute is read-only and cannot be changed | 0x420a | EtherCAT SOE communication error, the attribute is read-only and cannot be changed, error code 0x3004 |
| 2 | The attribute is write-protected at this time | 0x420b | EtherCAT SOE communication error, the attribute is write-protected at this time, error code 0x3005 |
| 2 | No unit | 0x420c | EtherCAT SOE communication error, no unit, error code 0x4001 |
| 2 | Unit transmission is too short | 0x420d | EtherCAT SOE communication error, unit transmission is too short, error code 0x4002 |
| 2 | The unit transmission is too long | 0x420e | EtherCAT SOE communication error, the unit transmission is too long, error code 0x4003 |
| 2 | The unit is read-only and cannot be changed | 0x420f | EtherCAT SOE communication error, the unit is read-only and cannot be changed, error code 0x4004 |
| 2 | The unit is write-protected at this time | 0x4210 | EtherCAT SOE communication error, the unit is write-protected at this time, error code 0x4005 |
| 2 | No minimum input value | 0x4211 | EtherCAT SOE communication error, no minimum input value, error code 0x5001 |
| 2 | The minimum input value transmission is too short | 0x4212 | EtherCAT SOE communication error, the minimum input value transmission is too short, error code 0x5002 |
| 2 | The minimum input value transmitted is too long | 0x4213 | EtherCAT SOE communication error, the minimum input value transmitted is too long, error code 0x0x5003 |
| 2 | The minimum input value is read-only and cannot be changed | 0x4214 | EtherCAT SOE communication error, the minimum input value is read-only and cannot be changed, error code 0x5004 |
| 2 | The minimum input value is write-protected at this time | 0x4215 | EtherCAT SOE communication error, the minimum input value is write-protected at this time, error code 0x5005 |
| 2 | No maximum input value | 0x4216 | EtherCAT SOE communication error, no maximum input value, error code 0x0x6001 |
| 2 | The maximum input value transmission is too short | 0x4217 | EtherCAT SOE communication error, the maximum input value transmission is too short, error code 0x6002 |
| 2 | The maximum input value transmission is too long | 0x4218 | EtherCAT SOE communication error, the maximum input value transmission is too long, error code 0x6003 |
| 2 | The maximum input value is read-only and cannot be changed | 0x4219 | EtherCAT SOE communication error, the maximum input value is read-only and cannot be changed, error code 0x6004 |
| 2 | The maximum input value is write-protected at this time | 0x421a | EtherCAT SOE communication error, the maximum input value is write-protected at this time, error code 0x6005 |
| 2 | Running data transmission is too short | 0x421b | EtherCAT SOE communication error, running data transmission is too short, error code 0x7002 |
| 2 | The running data transmission is too long | 0x421c | EtherCAT SOE communication error, the running data transmission is too long, error code 0x7003 |
| 2 | The operating data is read-only and cannot be changed | 0x421d | EtherCAT SOE communication error, the operating data is read-only and cannot be changed, error code 0x0x7004 |
| 2 | Run data write protection | 0x421e | EtherCAT SOE communication error, run data write protection, error code 0x0x700A |
| 2 | The operating data is less than the minimum input value | 0x421f | EtherCAT SOE communication error, the operating data is less than the minimum input value, error code 0x7006 |
| 2 | The operating data is greater than the maximum input value | 0x4220 | EtherCAT SOE communication error, the operating data is greater than the maximum input value, error code 0x7007 |
| 2 | Invalid running data: IDN configuration is not supported | 0x4221 | EtherCAT SOE communication error, invalid running data: IDN configuration is not supported, error code 0x0x7008 |
| 2 | A password is required for write protection of running data | 0x4222 | EtherCAT SOE communication error, a password is required for write protection of running data, error code 0x7009 |
| 2 | Run data write protection, periodic configuration | 0x4223 | EtherCAT SOE communication error, run data write protection, periodic configuration, error code 0x700A |
| 2 | Invalid indirect addressing | 0x4224 | EtherCAT SOE communication error, invalid indirect addressing, error code 0x700B |
| 2 | Process data write-protected due to other settings, periodic configuration | 0x4225 | EtherCAT SOE communication error, process data write-protected due to other settings, periodic configuration, error code 0x700C |
| 2 | Error reserved | 0x4226 | EtherCAT SOE communication error, error reserved, error code 0x700D |
| 2 | The process command has been activated | 0x4227 | EtherCAT SOE communication error, the process command has been activated, error code 0x7010 |
| 2 | The process command cannot be interrupted | 0x4228 | EtherCAT SOE communication error, the process command cannot be interrupted, error code 0x7011 |
| 2 | The process command cannot be executed at this time (status reason) | 0x4229 | EtherCAT SOE communication error, the process command cannot be executed at this time (status reason), error code 0x7012 |
| 2 | The process command cannot be executed (invalid or wrong parameters) | 0x422a | EtherCAT SOE communication error, the process command cannot be executed (invalid or wrong parameters), error code 0x7013 |
| 2 | No data status | 0x422b | EtherCAT SOE communication error, no data status, error code 0x7014 |
| 2 | No default value | 0x422c | EtherCAT SOE communication error, no default value, error code 0x8001 |
| 2 | The default value transmitted is too long | 0x422d | EtherCAT SOE communication error, the default value transmitted is too long, error code 0x8002 |
| 2 | The default value is read-only and cannot be changed | 0x422e | EtherCAT SOE communication error, the default value is read-only and cannot be changed, error code 0x8004 |
| 2 | Invalid driver number | 0x422f | EtherCAT SOE communication error, invalid driver number, error code 0x800A |
| 2 | Unknown error | 0x4230 | EtherCAT SOE communication error, unknown error, error code 0xffff |
| 2 | EtherCAT mailbox communication error, general error | 0x42ff | EtherCAT mailbox communication error, general error |
| 2 | Email communication is normal | 0x4300 | EtherCAT email communication is normal |
| 2 | Syntax error in 6-octet mailbox header | 0x4301 | EtherCAT mailbox communication error, syntax error in 6-octet mailbox header, error code 0x0001 |
| 2 | The email protocol is not supported | 0x4302 | EtherCAT email communication error, the email protocol is not supported, error code 0x0002 |
| 2 | Channel Field contains an incorrect value | 0x4303 | EtherCAT mailbox communication error, Channel Field contains an incorrect value, error code 0x0003 |
| 2 | This service is not supported | 0x4304 | EtherCAT mailbox communication error, this service is not supported, error code 0x0004 |
| 2 | Invalid mailbox header | 0x4305 | EtherCAT mailbox communication error, invalid mailbox header, error code 0x0005 |
| 2 | The data length of the receiving mailbox is too short | 0x4306 | EtherCAT mailbox communication error, the data length of the receiving mailbox is too short, error code 0x0006 |
| 2 | Insufficient storage space in the slave station | 0x4307 | EtherCAT mailbox communication error, insufficient storage space in the slave station, error code 0x0007 |
| 2 | Data length is inconsistent | 0x4308 | EtherCAT mailbox communication error, data length is inconsistent, error code 0x0008 |
| 2 | Unknown error | 0x4309 | EtherCAT mailbox communication error, unknown error, error code 0xffff |
| 2 | Generic Error | 0x431f | EtherCAT ALS Error, Generic Error |
| 2 | ALS OK | 0x4320 | EtherCAT ALS OK |
| 2 | Unclear error | 0x4321 | Unclear error, application layer error code 0x0001 |
| 2 | No memory | 0x4322 | EtherCAT ALS error, no memory, error code 0x0002 |
| 2 | Invalid status request | 0x4323 | EtherCAT ALS error, invalid status request, error code 0x0011 |
| 2 | Unknown status request | 0x4324 | EtherCAT ALS error, unknown status request, error code 0x0012 |
| 2 | The power-on state is not supported | 0x4325 | EtherCAT ALS error, the power-on state is not supported, error code 0x0013 |
| 2 | No valid firmware | 0x4326 | EtherCAT ALS error, no valid firmware, error code 0x0014 |
| 2 | Invalid email configuration | 0x4327 | EtherCAT ALS error, invalid email configuration, error code 0x0015 |
| 2 | Invalid email configuration | 0x4328 | EtherCAT ALS error, invalid email configuration, error code 0x0016 |
| 2 | Invalid sync manager configuration | 0x4329 | EtherCAT ALS error, invalid sync manager configuration, error code 0x0017 |
| 2 | No valid input | 0x432a | EtherCAT ALS error, no valid input, error code 0x0018 |
| 2 | No valid output | 0x432b | EtherCAT ALS error, no valid output, error code 0x0019 |
| 2 | Synchronization error | 0x432c | EtherCAT ALS error, synchronization error, error code 0x001A |
| 2 | Synchronization manager watchdog error | 0x432d | Synchronization manager watchdog error, application layer error code 0x001B |
| 2 | Invalid sync manager content | 0x432e | EtherCAT ALS error, invalid sync manager content, error code 0x001C |
| 2 | Invalid output configuration | 0x432f | EtherCAT ALS error, invalid output configuration, error code 0x001D |
| 2 | Invalid input configuration | 0x4330 | EtherCAT ALS error, invalid input configuration, error code 0x001E |
| 2 | Invalid watchdog configuration | 0x4331 | EtherCAT ALS error, invalid watchdog configuration, error code 0x001F |
| 2 | The slave station needs a cold start | 0x4332 | EtherCAT ALS error, the slave station needs a cold start, error code 0x0020 |
| 2 | The slave station needs to be initialized | 0x4333 | EtherCAT ALS error, the slave station needs to be initialized, error code 0x0021 |
| 2 | The slave station needs to be pre-run | 0x4334 | EtherCAT ALS error, the slave station needs to be pre-run, error code 0x0022 |
| 2 | The slave station needs to run safely | 0x4335 | EtherCAT ALS error, the slave station needs to run safely, error code 0x0023 |
| 2 | Invalid input mapping | 0x4336 | EtherCAT ALS error, invalid input mapping, error code 0x0024 |
| 2 | Invalid output mapping | 0x4337 | EtherCAT ALS error, invalid output mapping, error code 0x0025 |
| 2 | Inconsistent settings | 0x4338 | EtherCAT ALS error, inconsistent settings, error code 0x0026 |
| 2 | Free running is not supported | 0x4339 | EtherCAT ALS error, free running is not supported, error code 0x0027 |
| 2 | Synchronization not supported | 0x433a | EtherCAT ALS error, synchronization not supported, error code 0x0028 |
| 2 | Free run requires 3 buffer mode | 0x433b | EtherCAT ALS error, free run requires 3 buffer mode, error code 0x0029 |
| 2 | Background watchdog | 0x433c | EtherCAT ALS error, background watchdog, error code 0x002A |
| 2 | No valid input and output | 0x433d | EtherCAT ALS error, no valid input and output, error code 0x002B |
| 2 | Major synchronization error | 0x433e | EtherCAT ALS error, major synchronization error, error code 0x002C |
| 2 | Unsynchronized error | 0x433f | EtherCAT ALS error, Unsynchronized error, error code 0x002D |
| 2 | Invalid input FMMU configuration | 0x4340 | EtherCAT ALS error, invalid input FMMU configuration, error code 0x002E |
| 2 | Invalid distributed clock synchronization configuration | 0x4341 | EtherCAT ALS error, invalid distributed clock synchronization configuration, error code 0x0030 |
| 2 | Invalid distributed clock latch configuration | 0x4342 | EtherCAT ALS error, invalid distributed clock latch configuration, error code 0x0031 |
| 2 | Phase locked loop error | 0x4343 | EtherCAT ALS error, phase locked loop error, error code 0x0032 |
| 2 | Distributed clock synchronization IO error | 0x4344 | EtherCAT ALS error, distributed clock synchronization IO error, error code 0x0033 |
| 2 | Distributed clock synchronization timeout | 0x4345 | EtherCAT ALS error, distributed clock synchronization timeout, error code 0x0034 |
| 2 | Distributed clock invalid synchronization cycle time | 0x4346 | EtherCAT ALS error, distributed clock invalid synchronization cycle time, error code 0x0035 |
| 2 | Invalid distributed clock sync0 cycle time | 0x4347 | EtherCAT ALS error, invalid distributed clock sync0 cycle time, error code 0x0036 |
| 2 | Invalid distributed clock sync1 cycle time | 0x4348 | EtherCAT ALS error, invalid distributed clock sync1 cycle time, error code 0x0037 |
| 2 | Email communication AOE error | 0x4349 | EtherCAT ALS error, email communication AOE error, error code 0x0041 |
| 2 | Email communication EOE error | 0x434a | EtherCAT ALS error, email communication EOE error, error code 0x0042 |
| 2 | Email communication COE error | 0x434b | EtherCAT ALS error, email communication COE error, error code 0x0043 |
| 2 | Email communication FOE error | 0x434c | EtherCAT ALS error, email communication FOE error, error code 0x0044 |
| 2 | Email communication SOE error | 0x434d | EtherCAT ALS error, email communication SOE error, error code 0x0045 |
| 2 | Email communication VOE error | 0x434e | EtherCAT ALS error, email communication VOE error, error code 0x004f |
| 2 | EEPROM inaccessible | 0x434f | EtherCAT ALS error, EEPROM inaccessible, error code 0x0050 |
| 2 | EEPROM error | 0x4350 | EtherCAT ALS error, EEPROM error, error code 0x0051 |
| 2 | Restart the slave locally | 0x4351 | EtherCAT ALS error, restart the slave locally, error code 0x0060 |
| 2 | Device identifier value changed | 0x4352 | EtherCAT ALS error, device identifier value changed, error code 0x0061 |
| 2 | The application controller can be used | 0x4353 | EtherCAT ALS error, the application controller can be used, error code 0x00f0 |
| 2 | Unknown error | 0x4354 | EtherCAT ALS error, unknown error, error code 0xffff |
| 2 | EtherCAT error terminator | 0x4355 | EtherCAT error terminator |
8.1.1.4 Jump
- Project tree jumps to device view: Open the corresponding device view by double-clicking the alarm icon in the hardware diagnostic status column of the project tree
- The device view parent node can jump to the corresponding child node
- The child nodes of the device view can jump to the corresponding entry in the corresponding diagnostic buffer and freeze the display of the diagnostic buffer
- The corresponding entry in the diagnostic buffer can open the corresponding device view
NOTE
- When the host computer changes from online to offline, the corresponding hardware diagnostic status becomes invalid
- If the diagnostic buffer does not already have the Geoaddress device, it will not jump
8.1.1.5 Repeat
- During the operation of the diagnostic system, the buffer will continuously receive fault or information records from each monitoring point. In order to improve the effectiveness and analyzability of diagnostic information, the system takes measures to merge statistics for records that appear continuously and repeatedly within a 5-minute time window. This combined statistics process aims to streamline the presentation of diagnostic information and reduce the interference of redundant information, thereby improving the efficiency and accuracy of troubleshooting