A method and system for remote diagnosis of PLC
By configuring communication protocol, data acquisition server and web server in the PLC system, combined with error code mapping table, fast and efficient diagnosis of remote PLC is achieved, solving the problems of inefficient and costly maintenance of traditional PLCs, and improving production efficiency and Security.
Patent Information
- Application Number
- CN202411337110.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-25
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2044-09-25
AI Technical Summary
Traditional PLC maintenance and troubleshooting problems are geographically restricted, inefficient, expensive, and insufficient real-time. Especially when multiple devices are distributed in different locations, multiple technicians are required to go to each site for diagnosis and repair, resulting in time and Resources are wasted and there is a lack of effective means of analyzing large amounts of data.
By configuring the communication protocol, using the shortest path algorithm, automatically selecting the best communication path, selecting the data acquisition server to set data acquisition rules, configuring the web server to obtain real-time data, and creating an error code mapping table to integrate the error resolution function into the web application. Display error messages and troubleshooting results in real time.
It realizes the fast and efficient remote diagnosis PLC, reduces manual interpretation time, improves problem positioning efficiency and data transmission accuracy, reduces the possibility of errors and production downtime risks, and improves production efficiency and safety.
Smart Images

Figure CN118859910B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of remote diagnosis, and in particular to a method and system for remotely diagnosing a PLC. Background Art
[0002] In traditional PLC maintenance and troubleshooting, technicians need to arrive at the site to diagnose and repair. When multiple devices are distributed in different locations, multiple technicians are required to go to each site separately. This model leads to a waste of time and resources; on-site maintenance involves travel expenses, labor costs and other costs; when a fault occurs during the production process, if it is not handled in time, it may cause the production line to stop and cause economic losses; traditional methods often lack effective analysis methods for large amounts of data. Therefore, a method and system for remote diagnosis of PLC is provided. Summary of the invention
[0003] The object of the present invention is to provide a method and system for remote diagnosis of PLC to solve the problems of geographical limitation, low efficiency, high cost and lack of real-time performance mentioned in the above background technology.
[0004] To achieve the above object, the present invention provides a method for remotely diagnosing a PLC, comprising:
[0005] S1. Configure the communication protocol to establish a connection with the PLC, and automatically select the best communication path through the shortest path algorithm when configuring the communication protocol;
[0006] S2. Select a data acquisition server and set data acquisition rules to read data from the PLC and store the data in the database;
[0007] S3. Configure the Web server to ensure that the Web application obtains real-time data from the data collection server;
[0008] S4. Create a mapping table containing all known error codes and their corresponding fault descriptions to integrate the error parsing function into the Web application;
[0009] S5. Display error information and fault diagnosis results in real time on the Web interface.
[0010] As a further improvement of the technical solution, in S1, the configuration communication protocol is specifically:
[0011] Configure the PLC's communication parameters: set the IP address, configure the port and node ID, and enable remote access;
[0012] The best communication path is automatically selected through the shortest path algorithm based on bandwidth requirements, bandwidth cost, energy consumption and firewall penetration capability.
[0013] As a further improvement of the technical solution, the shortest path algorithm is specifically:
[0014] ;
[0015] ;
[0016] represents the optimal path; Represents a single path; Represents the set of all available paths; express Belongs to the path collection A path in Indicates the path The minimum bandwidth of Indicates the path energy consumption; Indicates the current bandwidth demand; Indicates the maximum permissible energy consumption; Indicates the minimum firewall penetration capability score; Indicates the path Firewall penetration score; Indicates the path The comprehensive evaluation function of Indicates the path Costs; is the weight coefficient of the cost-effectiveness ratio; is the weight coefficient of delay; Indicates the path Delays; is the weight coefficient of energy consumption; It is the weight coefficient of the firewall penetration capability.
[0017] As a further improvement of the technical solution, in S2, the data collection rules are set, specifically:
[0018] S2.1. Use the Modbus protocol to set register address 0x0001 to indicate the error status.
[0019] S2.2. Select the address range 0x1000 to 0x10FF to record error information, and use the error information in this address range as the diagnostic buffer;
[0020] S2.3. Use the Modbus client software to configure the data acquisition server so that it queries the error flag address 0x0001 of the PLC through the data acquisition server every second, and the data acquisition server receives the error report from the PLC;
[0021] S2.4. Monitor the change of the error flag through the data acquisition server. Once the change is detected, read the content of the diagnostic buffer immediately.
[0022] As a further improvement of the technical solution, in S3, configuring the Web server includes the following steps:
[0023] S3.1. Select a Web server and install it.
[0024] S3.2. Configure the basic settings of the web server and set up SSL / TLS certificates for encrypted HTTP communication;
[0025] Among them, basic settings include listening ports and default website directories;
[0026] S3.3, develop a web application to obtain real-time data from the data collection server;
[0027] S3.4. Configure an interface for interacting with the data acquisition server in the Web application to obtain real-time data, and build a time synchronization model based on the impact of daylight saving time and network partitions to reduce the impact of time asynchrony between the Web application and the data acquisition server.
[0028] As a further improvement of the technical solution, in S3.4, constructing the time synchronization model is specifically:
[0029] ;
[0030] represents the weighted average timestamp, , Indicates The timestamp of the time server, Indicates The weight of the time server, Indicates the number of servers; Indicates the amount of daylight saving time adjustment; Indicates the timestamp after taking into account the daylight saving time adjustment, which represents the result of time synchronization.
[0031] As a further improvement of the technical solution, in S4, creating a mapping table includes the following steps:
[0032] S4.1. Determine the PLC model used, obtain the error codes HwE001, SwE001, CommE001 and error descriptions. HwE001 indicates an input module failure, check whether the power cord is loose; SwE001 indicates a program runtime error, check the program logic; CommE001 indicates that it cannot connect to the specified IP address, confirm whether the network settings are correct, and check the network connection status;
[0033] S4.2. Use a database management system to create a table to record each error code and its corresponding fault description, and design a mapping table. The mapping table contains two columns: one for the error code and the other for the fault description.
[0034] As a further improvement of the technical solution, in S5, the error information and fault diagnosis results are displayed in real time on the Web interface, including the following steps:
[0035] S5.1, integrate error reporting and Web applications to ensure that error reports received from PLCs can be correctly captured by the data acquisition server and forwarded to the Web server;
[0036] S5.2, configure the server script to monitor the error report sent by the data acquisition server. After receiving the error report, the script uses the error code mapping table created in step S4 to perform error analysis and obtain the error description;
[0037] S5.3. The web interface is used to display the current system status and any error messages that occur. The interface is updated in real time.
[0038] As a further improvement of the technical solution, in S5.2, configuring the server script includes the following steps:
[0039] S5.21. Select Python language and Flask framework;
[0040] S5.22. Create an HTTP server using the Flask framework and configure the HTTP server to listen to a specific port;
[0041] S5.23. Create a route to receive error report data and write a processing function to handle the HTTP POST request, which will contain the error report data sent from the data collection server;
[0042] S5.24, parse the received data, use the created error code mapping table to parse the error code, obtain a detailed fault description, and store the parsed error information in the database;
[0043] S5.25. Send an HTTP response to the data collection server to confirm that the data has been successfully received.
[0044] On the other hand, the present invention provides a system for remotely diagnosing PLC, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the above-mentioned method for remotely diagnosing PLC.
[0045] Compared with the prior art, the present invention has the following beneficial effects:
[0046] 1. In the method and system for remote diagnosis of PLC, the error analysis function is integrated into the Web application, so that the operator or maintenance team can quickly view the specific error information and fault diagnosis results on the Web interface, simplifying the problem location process. By mapping the error code to the specific fault description, the time for manual interpretation can be reduced, helping technicians to identify problems more quickly and take corresponding solutions.
[0047] 2. In the method and system for remote diagnosis of PLC, the communication protocol configuration can ensure fast and efficient data transmission, which is very important for real-time control and monitoring; effective communication protocols can reduce errors and losses in the data transmission process and ensure the accuracy of data; automated data collection reduces the need for manual intervention and reduces the possibility of errors; real-time data collection enables operators to respond immediately to any abnormal situation, improving production efficiency and safety. BRIEF DESCRIPTION OF THE DRAWINGS
[0048] Figure 1 The figure is a flow chart of the overall method of the present invention. DETAILED DESCRIPTION
[0049] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0050] See also Figure 1 As shown, this embodiment provides a method for remotely diagnosing a PLC, comprising the following steps:
[0051] S1. Configure the communication protocol to establish a connection with the PLC;
[0052] In this embodiment, the configuration communication protocol is specifically:
[0053] Configure the PLC's communication parameters: set the IP address, configure the port and node ID, and enable remote access;
[0054] The best communication path is automatically selected through the shortest path algorithm based on bandwidth requirements, bandwidth costs, energy consumption and firewall penetration capabilities;
[0055] Among them, selecting a path based on bandwidth requirements can ensure that data transmission does not exceed the network's carrying capacity, avoiding congestion and delays; by considering energy consumption, the system can select a path with lower energy consumption for data transmission; considering firewall penetration capabilities can ensure that data can be transmitted securely even when there is a firewall between networks, which helps prevent data leakage or interception. Selecting the optimal path can also reduce potential failure points during data transmission, thereby improving the reliability and stability of the overall system; the shortest path algorithm usually takes into account the delay of the path, which can ensure that data can reach the destination in the shortest time, which is particularly important for application scenarios that require real-time data; automated path selection reduces the need for manual intervention, reduces the risk of configuration errors, and makes network management simpler and more efficient. The shortest path algorithm is as follows:
[0056] ;
[0057] ;
[0058] represents the optimal path; Represents a single path; Represents the set of all available paths; express Belongs to the path collection A path in Indicates the path The minimum bandwidth of Indicates the path energy consumption; Indicates the current bandwidth demand; Indicates the maximum permissible energy consumption; Indicates the minimum firewall penetration capability score; Indicates the path The firewall penetration capability score (e.g., a score from 1 to 10, with 1 being the worst and 10 being the best); Indicates the path The comprehensive evaluation function of Indicates the path Costs; is the weight coefficient of the cost-effectiveness ratio; is the weight coefficient of delay; Indicates the path Delays; is the weight coefficient of energy consumption; is the weight coefficient of the firewall penetration ability. The negative sign is used here because the higher the firewall penetration ability score, the more The smaller the contribution, because we want to minimize .
[0059] When there are three paths:
[0060] Path A: , , , , ;
[0061] represents the minimum bandwidth of path A; represents the cost of path A; represents the delay of path A; represents the energy consumption of path A; Indicates the firewall penetration capability score of path A;
[0062] Path B: , , , , ;
[0063] represents the minimum bandwidth of path B; represents the cost of path B; represents the delay of path B; represents the energy consumption of path B; Indicates the firewall penetration capability score of path B;
[0064] Path C: , , , , ;
[0065] represents the minimum bandwidth of path C; represents the cost of path C; represents the delay of path C; represents the energy consumption of path C; represents the firewall penetration capability score of path C;
[0066] If the current bandwidth demand , maximum permissible energy consumption , minimum firewall penetration score , weight coefficient , , , ,but:
[0067] Comprehensive evaluation of Path A ;
[0068] Comprehensive evaluation of Path B ;
[0069] Comprehensive evaluation of Path C ;
[0070] Since the minimum bandwidth requirement of Path B is , does not meet the current bandwidth requirements , so Path B is excluded; at the same time, the firewall penetration capability score of Path C is 9, which meets the minimum firewall penetration capability score requirement. Therefore, only Path A and Path C are considered. Among these two paths, their comprehensive evaluation is calculated, and the path with the lowest comprehensive evaluation is selected as the optimal path.
[0071] S2. Select a data acquisition server and set data acquisition rules to read data from the PLC and store the data in the database;
[0072] The data read from PLC include: status data, process variables, control signals, event records, statistical information, etc.
[0073] In this embodiment, the data collection rules are set as follows:
[0074] S2.1. Use the Modbus protocol to set register address 0x0001 to indicate the error status.
[0075] S2.2. Select the address range 0x1000 to 0x10FF to record error information, and use the error information in this address range as the diagnostic buffer;
[0076] S2.3. Use the Modbus client software to configure the data acquisition server so that it queries the error flag address 0x0001 of the PLC through the data acquisition server every second, and the data acquisition server receives the error report from the PLC;
[0077] S2.4, monitor the change of the error flag through the data acquisition server, and once the change is detected, immediately read the content of the diagnostic buffer;
[0078] Specifically:
[0079] from pymodbus.client.sync import ModbusTcpClient
[0080] import time
[0081] # Configure Modbus client
[0082] client = ModbusTcpClient('192.168.1.100') # Assume the IP address of the PLC is 192.168.1.100
[0083] client.connect()
[0084] # Error flag address
[0085] error_flag_address = 0x0001
[0086] # Diagnostic buffer address range
[0087] diagnostic_buffer_start = 0x1000
[0088] diagnostic_buffer_end = 0x10FF
[0089] # Define a function to read the error flag
[0090] def read_error_flag():
[0091] result = client.read_holding_registers(error_flag_address, count=1, unit=1)
[0092] return result.registers[0]
[0093] # Define a function to read the diagnostic buffer
[0094] def read_diagnostic_buffer():
[0095] result = client.read_holding_registers(diagnostic_buffer_start,count=(diagnostic_buffer_end-diagnostic_buffer_start+1), unit=1)
[0096] return result.registers
[0097] # Main loop
[0098] while True:
[0099] error_flag = read_error_flag()
[0100] if error_flag != 0: # If the error flag is not 0, an error has occurred
[0101] print("Error detected!")
[0102] diagnostic_data = read_diagnostic_buffer()
[0103] # Further process the diagnostic data, such as sending it to a data collection server
[0104] time.sleep(1) # Poll once per second
[0105] S3. Configure the Web server to ensure that the Web application obtains real-time data from the data collection server;
[0106] In this embodiment, configuring the Web server includes the following steps:
[0107] S3.1. Select Web server, select ache HTTP Server, and install it;
[0108] S3.2. Configure the basic settings of the web server and set up SSL / TLS certificates for encrypted HTTP communication;
[0109] Among them, basic settings include listening ports and default website directories;
[0110] S3.3, develop a web application to obtain real-time data from the data collection server;
[0111] S3.4. Configure an interface for interacting with the data collection server in the Web application. The interface is a RESTful API based on the HTTP protocol, which is used to obtain real-time data. A time synchronization model is built in combination with the impact of daylight saving time and network partitions to reduce the impact of time asynchrony between the Web application and the data collection server.
[0112] Among them, time synchronization is crucial to ensure the consistency of data obtained from the data acquisition server and the data displayed in the Web application. If there is a time difference between the Web application and the data acquisition server, it may lead to misreading or misprocessing of the data; for applications that rely on timestamps, such as event recording, alarm triggering, etc., accurate time synchronization can ensure the accuracy of these operations and avoid misjudgments caused by time deviation; changes in daylight saving time will cause time jumps. If not handled, it may cause deviations in the time of data collection and display. By building a time synchronization model to consider the impact of daylight saving time, it can ensure that the timestamp of the data is always accurate; network partitions may cause some nodes to lose contact with other nodes, thereby affecting time synchronization. When building a time synchronization model, the impact of network partitions is taken into account to ensure that the system can still maintain relatively accurate time even in the case of network partitions; building a time synchronization model is specifically as follows:
[0113] ;
[0114] represents the weighted average timestamp, , Indicates The timestamp of the time server, Indicates The weight of the time server, Indicates the number of servers; Indicates the daylight saving time adjustment amount (+1 hour or -1 hour, or 0 hour); Indicates the timestamp after taking into account the daylight saving time adjustment, which represents the result of time synchronization.
[0115] If there are three time servers G, H and K, the timestamp of server G is , the weight is ; The timestamp of server H is , the weight is ; The timestamp of server K is , the weight is ; When in daylight saving time, the daylight saving time adjustment is hours, if server H is unavailable due to network partition, its weight Can be set to 0, then the weighted average timestamp .
[0116] S4. Create a mapping table containing all known error codes and their corresponding fault descriptions to integrate the error parsing function into the Web application;
[0117] In this embodiment, creating a mapping table includes the following steps:
[0118] S4.1. Determine the PLC model used, obtain the error codes HwE001, SwE001, CommE001 and error descriptions. HwE001 indicates an input module failure, check whether the power cord is loose; SwE001 indicates a program runtime error, check the program logic; CommE001 indicates that it cannot connect to the specified IP address, confirm whether the network settings are correct, and check the network connection status;
[0119] S4.2. Use a database management system to create a table to record each error code and its corresponding fault description, and design a mapping table. The mapping table contains two columns: one for the error code and the other for the fault description.
[0120] S5. Real-time display of error information and fault diagnosis results on the Web interface;
[0121] In this embodiment, the error information and fault diagnosis results are displayed in real time on the Web interface, including the following steps:
[0122] S5.1, integrate error reporting and Web applications to ensure that error reports received from PLCs can be correctly captured by the data acquisition server and forwarded to the Web server;
[0123] S5.2, configure the server script to monitor the error report sent by the data acquisition server. After receiving the error report, the script uses the error code mapping table created in step S4 to perform error analysis and obtain the error description;
[0124] Among them, configuring the server script includes the following steps:
[0125] S5.21. Select Python language and Flask framework;
[0126] S5.22. Use the Flask framework to create an HTTP server and configure the HTTP server to listen to a specific port. The port usually used to receive data will not be the standard port 80 or 404. Instead, choose an uncommon port such as 8000, 8080, etc.
[0127] S5.23. Create a route to receive error report data and write a processing function to handle the HTTP POST request, which will contain the error report data sent from the data collection server;
[0128] Among them, the processing function (handle_error_report) is specifically:
[0129] from flask import Flask, request
[0130] app = Flask(__name__)
[0131] # Define a route to receive error report data
[0132] @app.route(' / error_report', methods=['POST'])
[0133] def handle_error_report():
[0134] # Get the data in the POST request
[0135] data = request.get_json() # Assume the data is sent in JSON format
[0136] # Error code in parsing data
[0137] error_code = data['error_code']
[0138] # Use the error code mapping table to parse the error code and obtain a detailed fault description
[0139] fault_description = get_fault_description(error_code)
[0140] # Store the parsed error information in the database
[0141] store_error_info(error_code, fault_description)
[0142] # Send an HTTP response to the data collection server to confirm that the data has been successfully received
[0143] return 'Error report received and processed.'
[0144] S5.24, parse the received data, decode it into SON format data, use the created error code mapping table to parse the error code, obtain a detailed fault description, and store the parsed error information in the database;
[0145] S5.25, sending an HTTP response to the data collection server to confirm that the data has been successfully received;
[0146] S5.3. The web interface is used to display the current system status and any error information that occurs. The interface is updated in real time so that users can see new error reports in a timely manner.
[0147] This embodiment also provides a system for remote diagnosis of PLC, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the above-mentioned method for remote diagnosis of PLC.
[0148] The above shows and describes the basic principles, main features and advantages of the present invention. Those skilled in the art should understand that the present invention is not limited by the above embodiments, and the above embodiments and descriptions are only preferred examples of the present invention, and are not intended to limit the present invention. Without departing from the spirit and scope of the present invention, the present invention may have various changes and improvements, and these changes and improvements all fall within the scope of the present invention to be protected.
Claims
1. A method for remote diagnosis of PLC, It is characterized in that The following steps are involved: S1. Configure the communication protocol to establish a connection with the PLC, and automatically select the best communication path through the shortest path algorithm when configuring the communication protocol; S2. Select a data acquisition server and set data acquisition rules to read data from the PLC and store the data in the database; S3. Configure the Web server to ensure that the Web application obtains real-time data from the data collection server; S4. Create a mapping table containing all known error codes and their corresponding fault descriptions to integrate the error parsing function into the Web application; S5. Real-time display of error information and fault diagnosis results on the Web interface; In S1, the communication protocol is configured as follows: Configure the PLC's communication parameters: set the IP address, configure the port and node ID, and enable remote access; The shortest path algorithm automatically selects the best communication path based on bandwidth requirements, bandwidth costs, energy consumption, and firewall penetration capabilities; The shortest path algorithm is specifically: ; ; represents the optimal path; Represents a single path; Represents the set of all available paths; express Belongs to the path collection A path in Indicates the path The minimum bandwidth of Indicates the path energy consumption; Indicates the current bandwidth demand; Indicates the maximum permissible energy consumption; Indicates the minimum firewall penetration capability score; Indicates the path Firewall penetration score; Indicates the path The comprehensive evaluation function of Indicates the path Costs; is the weight coefficient of the cost-effectiveness ratio; is the weight coefficient of delay; Indicates the path Delays; is the weight coefficient of energy consumption; It is the weight coefficient of the firewall penetration capability.
2. The method for remotely diagnosing a PLC according to claim 1, Features: In S2, data collection rules are set, specifically: S2.
1. Use the Modbus protocol to set register address 0x0001 to indicate the error status. S2.
2. Select the address range 0x1000 to 0x10FF to record error information, and use the error information in this address range as the diagnostic buffer; S2.
3. Use the Modbus client software to configure the data acquisition server so that it queries the error flag address 0x0001 of the PLC through the data acquisition server every second, and the data acquisition server receives the error report from the PLC; S2.
4. Monitor the change of the error flag through the data acquisition server. Once the change is detected, read the content of the diagnostic buffer immediately.
3. The method for remotely diagnosing a PLC according to claim 1, Features: In the S3, configuring the web server includes the following steps: S3.
1. Select a Web server and install it. S3.
2. Configure the basic settings of the web server and set up SSL / TLS certificates for encrypted HTTP communication; Among them, basic settings include listening ports and default website directories; S3.3, develop a web application to obtain real-time data from the data collection server; S3.
4. Configure an interface for interacting with the data acquisition server in the Web application to obtain real-time data, and build a time synchronization model based on the impact of daylight saving time and network partitions to reduce the impact of time asynchrony between the Web application and the data acquisition server.
4. The method for remotely diagnosing a PLC according to claim 3, Features: In S3.4, the time synchronization model is constructed as follows: ; represents the weighted average timestamp, , Indicates The timestamp of the time server, Indicates The weight of the time server, Indicates the number of servers; Indicates the amount of daylight saving time adjustment; Indicates the timestamp after taking into account the daylight saving time adjustment, which represents the result of time synchronization.
5. The method for remotely diagnosing a PLC according to claim 1, Features: In S4, creating a mapping table includes the following steps: S4.
1. Determine the PLC model used, obtain the error codes HwE001, SwE001, CommE001 and error descriptions. HwE001 indicates an input module failure, check whether the power cord is loose; SwE001 indicates a program runtime error, check the program logic; CommE001 indicates that it cannot connect to the specified IP address, confirm whether the network settings are correct, and check the network connection status; S4.
2. Use a database management system to create a table to record each error code and its corresponding fault description, and design a mapping table. The mapping table contains two columns: one for the error code and the other for the fault description.
6. The method for remotely diagnosing a PLC according to claim 1, Features: In the S5, the error information and the fault diagnosis result are displayed in real time on the web interface, including the following steps: S5.1, integrate error reporting and Web applications to ensure that error reports received from PLCs can be correctly captured by the data acquisition server and forwarded to the Web server; S5.2, configure the server script to monitor the error report sent by the data acquisition server. After receiving the error report, the script uses the error code mapping table created in step S4 to perform error analysis and obtain the error description; S5.
3. The web interface is used to display the current system status and any error messages that occur. The interface is updated in real time.
7. The method for remotely diagnosing a PLC according to claim 6, Features: In S5.2, configuring the server script includes the following steps: S5.
21. Select Python language and Flask framework; S5.
22. Create an HTTP server using the Flask framework and configure the HTTP server to listen to a specific port; S5.
23. Create a route to receive error report data and write a processing function to handle the HTTP POST request, which will contain the error report data sent from the data collection server; S5.24, parse the received data, use the created error code mapping table to parse the error code, obtain a detailed fault description, and store the parsed error information in the database; S5.
25. Send an HTTP response to the data collection server to confirm that the data has been successfully received.
8. A system for remotely diagnosing a PLC, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, Features: The processor executes the computer program to implement the method for remotely diagnosing a PLC as described in any one of claims 1 to 7.
