Abstract: This paper applies industrial Ethernet technology to an industrial equipment monitoring system, realizing an embedded remote condition monitoring and fault diagnosis device based on the 32-bit high-performance processor AT91RM9200. This device is the core component of the electromechanical equipment condition monitoring and fault diagnosis system. The device achieves the connection between DeviceNet and Ethernet through the industrial Ethernet protocol (EtherNet/IP). A gateway-based network server was established by porting Linux and boa, and dynamic web page technology and B/S architecture UDP Socket communication technology were used to achieve dynamic real-time web page display. Keywords: state monitoring; AT91RM9200; industrial Ethernet; BOA; dynamic web page[b][align=center ] Design of the Embedded State Monitoring and Fault Diagnosing Instrument industrial equipment monitoring and control system. It is the core of the monitoring and diagnosing system. Ethernet/IP protocol is ported to realize the connection between DeviceNet and Ethernet, Linux and BOA is ported to set up a web server on the gateway and dynamic web page technology and UDP Socket communication technology is adopted to realize real-time web display. Keywords: state monitoring; AT91RM9200; EtherNet/IP; BOA; dynamic web page 1 Introduction Traditional condition monitoring and fault diagnosis devices typically employ fieldbus technology, but this approach has significant limitations: fieldbus types are diverse and differ considerably, making interoperability impossible and interconnection difficult, resulting in unsatisfactory information sharing and real-time performance. To better bridge the communication gap between terminal devices and remote monitoring systems, this paper proposes and designs an embedded condition monitoring and fault diagnosis device based on industrial Ethernet. Compared to traditional devices, it offers the following advantages: it achieves high system efficiency and uniformity; users can monitor a wide range of terminal devices anytime, anywhere via the Internet, replacing numerous front-end PCs and providing better real-time performance and effectiveness [1,2]. This device directly transmits real-time data collected on-site to an embedded web server via Ethernet. The server generates web pages for remote monitoring and fault diagnosis. Users can browse the on-site operating status, data acquisition information, and alarm information of the monitored equipment at any time by entering the device's IP address. 2 Device Structure and Features Currently, the overall system structure for condition monitoring and fault diagnosis of electromechanical equipment is shown in Figure 1: [align=center] Figure 1 Embedded Condition Monitoring and Fault Diagnosis System Structure[/align] This paper designs and develops the core device of this system—the embedded electromechanical equipment monitoring device, which is mainly divided into three modules: (1) Data acquisition module: including multiple field data acquisition units. It mainly completes the detection and acquisition of field data. (2) Data storage and processing module: including an embedded fieldbus/Ethernet monitoring industrial control computer and a database. It communicates with the fieldbus data acquisition unit through the EtherNet/IP protocol to achieve sensitive detection and data storage. (3) Online monitoring module: including an embedded Web server and a monitoring website. The server generates web pages for remote monitoring and fault diagnosis. Network users can keep track of the field operation at any time, making remote monitoring a reality. This device has the following three advanced features: 1) It uses industrial Ethernet to enable Ethernet/IP devices and field devices to communicate. To achieve this function, we ported the Ethernet protocol into embedded Linux. 2) It supports the monitoring of electromechanical equipment status through a browser. We ported BOA into embedded Linux and designed a dynamic webpage for real-time monitoring of electromechanical equipment. 3) Supports large-capacity data storage and uses a black box to monitor the real-time data resources of the device. By expanding the large-capacity IDE bus, we connect the IDE system hard disk to store a large amount of data [3]. 3 Hardware design of the device AT91RM9200 is a new microcontroller based on the ARM920T core launched by ATMEL for the field of system control and communication. It has an independent 16KB instruction and 16KB data cache, a full-function MMU virtual memory management unit, 16KB SRAM and 128KB ROM, 64MB NAND Flash memory, LCD controller, EBI interface controller, four 32-bit PIO controllers, 20-channel peripheral data controller (DMA), three synchronous serial controllers (SSC), four universal synchronous/asynchronous receivers/transmitters (USART), master/slave serial device interface SPI, 16-channel 12-bit ADC, one-channel 16-bit DAC, multimedia card interface (MCI), Ethernet 10/100 Base-T Ethernet media access controller (MAC), touch screen interface, IDE interface, etc. Based on the rich resources of the processor, this device has been configured and expanded. The processor collects voltage or current signals of electromechanical equipment through the 16-channel 12-bit ADC interface, and the IDE interface is connected to a large-capacity IDE hard disk for storing web, collected data, etc. Through the DM9161 chip, the microprocessor expands the EMAC interface to an Ethernet interface RJ45 and connects to the industrial Ethernet [4]. The AT91RM9200 connects to the CAN controller SJA1000 via the SPI interface. The CAN controller is connected to the CAN transceiver PCA82C250 for DeviceNet connectivity. The hardware structure is shown in Figure 2: [align=center] Figure 2 Hardware Structure Diagram[/align] 4. Software Architecture of the Device The software structure is shown in Figure 3: [align=center] Figure 3 Software Architecture Diagram[/align] 4.1 Porting the Industrial Ethernet Protocol Industrial Ethernet (EtherNet/IP) is a communication system suitable for industrial environments, capable of supporting the connection of a large number of field devices in a wide area. It uses the Common Industrial Protocol (CIP) as its application layer protocol. The CIP protocol supports various control, configuration, and information processing services, including explicit messages (for information transmission, flexible message exchange) and implicit messages (for control and real-time I/O data transmission), supporting polling, periodic, and state change data transmission triggering mechanisms, point-to-point unicast, and broadcast data transmission methods [5,6]. The design of the OE service simplifies the porting of EtherNet/IP, requiring only modification of the operating environment file to suit the ARM Linux operating system. 4.2 Porting BOA Download a mainstream version of the BOA source code package from www.boa.org. This system uses boa-0.94.13.tar.gz. Step 1: Modify the Makefile to compile the BOA source code and generate the BOA executable. Modify the Makefile because we are compiling ARM-based binary code. Therefore, we must modify CC and CPP in the Makefile, changing them to the path of the cross-compiler installation: CC=/opt/host/armv4l/bin/armv4l-unknown-linux-gcc CPP=/opt/host/armv4l/bin/armv4l-unknown-linux-gcc -E Then run `make` to compile and obtain the executable program boa. Step 2: Configure BOA. BOA loads a configuration file boa.conf upon startup. This file must be edited before running the boa program. A sample boa.conf file is already provided in the Boa source code directory; you can modify it based on this example. The main configuration content is as follows: User nobody Group 0 ServerName AT91RM9200 ErrorLog /var/log/boa/error_log AccessLog /var/log/boa/access_log DocumentRoot /var/www MimeTypes /etc/mime.types ScriptAlias ​​/cgi-bin/ /var/www/cgi-bin/ Based on this configuration, the log file directory /var/log/boa, the main directory for HTML documents /var/www (where static web pages are stored), and the directory for CGI scripts /var/www/cgi-bin (where CGI scripts are stored) need to be created. 4.3 CGI Web Page Design CGI (Common Gateway Interface) provides a channel for the web server to execute external programs. This server-side technology establishes the interaction between the web browser and the web server. First, the browser sends the request from the remote client to the web server. The web server then sends the data to the CGI program using STDIN. After executing the CGI program, it obtains the device information from the buffer. Finally, it uses STDOUT to output a structured HTML file containing the industrial equipment information, which is then sent back to the browser via the web server and displayed to the remote client. The CGI program can be written in C and can be embedded in HTML scripts. It is compiled using ARM-GCC. The CGI program can communicate with the remote client using GET, POST, or direct URL parameter passing methods. Below is a CGI program that displays the collected device data on a webpage, using SQLite as the database. SQLite is a powerful embedded relational database management system implemented with a small C library. It achieves a good balance between size and functionality, making it an ideal embedded database. #include <sqlite3.h> #include "sqlite3.h" main() { ... sqlite3* p_db; sqlite3_open("mydb", &p_db); /* Open the database */ /* Execute the SQL statement to select all records in the alarm table and execute the callback function on each row of the query result */ ret=sqlite3_exec(p_db, "select * from alarm;", callback,0, &errmsg); ... sqlite3_close(p_db); /* Close the database */ } int callback(void *p_data, int n_columns, char **column_names, char **column_values) { /* Callback function */ int i; for (i=0; i < n_columns; i++) printf("%s=%s\n",column_names[i],column_values[i]? column_values[i]:"NULL"); /* Print the query results */ return 0; } 4.4 Dynamic Web Page Technology The server is an embedded ARM, which can only run C++ service programs compiled under Linux based on the TCP/IP protocol using ARM-GCC. This paper uses UDP socket technology implemented in embedded C++ to communicate with the client. The client uses Flash or Java Applet to communicate with the service program and provide dynamic web pages. This paper uses Flash to complete the dynamic refresh, which adopts a thread mechanism. The background data is obtained by communicating with the server through UDP socket technology. The communication between the server and the client adopts an advanced B/S structure. Users do not need to install diagnostic software on the client side to remotely monitor and diagnose equipment, forming an open remote monitoring and fault diagnosis system. The UDP-based Socket communication B/S architecture is shown in Figure 4: [align=center] Figure 4 UDP Socket Communication B/S Architecture[/align] The system dynamic page is shown in Figure 5: [align=center] Figure 5 Main Interface of Status Monitoring and Fault Diagnosis System[/align] 5 Conclusion The author's innovation lies in applying industrial Ethernet technology, embedded Web Server technology, CGI technology, and dynamic web page technology to an embedded status monitoring and fault diagnosis device. Users can view the operating status and alarm information of field equipment at any time via a URL. Compared with traditional monitoring devices, this improves the real-time performance of monitoring, shortens maintenance time, and saves maintenance costs, truly realizing the transformation of the maintenance system from accident maintenance and scheduled maintenance to condition-based maintenance. References [1] Wang Jian, Zhang Hao, Yan Junwei, et al. Digital remote fault diagnosis system based on Internet/intranet [J]. Computer Engineering, 2000, 26 (10): 28-29 [2] Jin Zhen, Tang Minghao, Jiang Lin. Embedded implementation method of Internet remote monitoring system [J]. Computer Engineering, 2006, 1 (32): 245-247 [3] Hu Changlin, Liu Pengyuan, Li Yongjun, Wei Baohua. Overall design of equipment status monitoring and fault prediction system [J]. Microcomputer Information, 2006, 22 (9-1): 189-191 [4] ATMEL.ARM920TTM-based Microcontroller AT91RM9200 User's Manual [R]. August 2003. [5] Rinaldi, John. EtherNet/IP – An application-layer protocol for industrial automation [J]. Sensors (Peterborough, NH), May, 2003, 20(5):43-45.