Multi-protocol slave station design for wind power control system

Abstract

Disclosed in the present invention is a multi-protocol slave station design for a wind power control system, comprising a Web end, external sensors, a single-chip microcomputer MCU and a wind turbine master controller. The Web performs protocol switching, and configures a corresponding equipment baud rate and a slave station number; the external sensors receive external analog quantities, and convert analog signals into digital quantities; the single-chip microcomputer MCU comprises a TCP-SPI converter, a virtual file system, a buffer, an SFUD interface, an eth interface, an RTT scheduling interface and a plurality of protocol stack interfaces. The single-chip microcomputer MCU performs comparative scheduling on the digital quantities and configuration information by means of the RTT scheduling interface, allocates same to the corresponding protocol stack interfaces and transmits same to the wind turbine master controller. Compared with the prior art, the present invention allocates adaptive protocols by means of the configuration information, so as to support a plurality of different network protocols and integrate equipment configurations of different protocols, allowing for high adaptability and normalization, and thus improving network flexibility and scalability.

Description

A multi-protocol slave station design for wind power control systems Technical Field

[0001] The present invention relates to the field of industrial communication control, and in particular to a multi-protocol slave station design for a wind power control system. Background Art

[0002] Wind power, an emerging clean energy source that uses natural wind power to generate electricity, is attracting increasing attention. In a wind power system, slave stations, as controlled nodes, play a crucial role in determining the stable operation of the system.

[0003] Different wind power manufacturers use different intelligent instruments, controllers, actuators and other field equipment, which makes the industrial bus diversified and complicated. The main communication methods currently used in wind power generation systems include MODBUS-RTU, PROFIBUS-DP, CANOPEN, CAN and other bus mechanisms.

[0004] Based on different application scenarios and control requirements, different slave station protocols are applied to wind power systems, such as CANopen, DP, Modbus, etc. It is difficult for existing slave stations to integrate the currently mentioned protocols into one device. They are all made into different modules and adapted to different protocols separately, which makes them unstandardized and unadaptable. For wind power slave station systems that support multiple slave station protocols, the traditional single-protocol slave station design can no longer meet the needs of modern applications.

[0005] However, for wind power slave systems that support multiple slave protocols, the traditional single-protocol slave design can no longer meet the needs of modern applications. Therefore, a slave solution that supports multiple protocols is needed.

[0006] Summary of the Invention

[0007] The purpose of the present invention is to address the shortcomings of different slave stations using different protocols, which cannot be integrated into one device, have poor usage standardization and low adaptability, and cannot meet the needs of modern applications. To address this shortcoming, a multi-protocol slave station design for wind power control systems is proposed.

[0008] In order to achieve the above objectives, the present invention adopts the following technical solutions:

[0009] A multi-protocol slave station design for a wind power control system includes a web terminal, external sensors, a single-chip microcomputer (MCU), and a wind turbine master control. The web performs protocol switching and configures the corresponding device baud rate and slave station number. The external sensor receives external analog quantities and converts the analog signals into digital quantities. The single-chip microcomputer (MCU) includes a TCP-SPI converter, a virtual file system, a buffer, an SFUD interface, an ETH interface, an RTT scheduling interface, and several protocol stack interfaces. The single-chip microcomputer MCU is connected to the web terminal via the TCP protocol. The single-chip microcomputer MCU is connected to the external sensor via the ETH interface and receives the digital quantities converted by the external sensor. The virtual file system is used to store device configuration information. The single-chip microcomputer MCU compares and schedules the digital quantities and configuration information via the RTT scheduling interface, distributes them to the corresponding protocol stack interface, and transmits them to the wind turbine master control.

[0010] As a further preferred embodiment of the present invention, the virtual file system is constructed based on FatFs by the SFUD interface through SPI FLASH, and SPI FLASH is a non-volatile memory based on the SPI serial communication interface.

[0011] As a further preference of the present invention, the following steps are included:

[0012] S1. The MCU uses the LWIP protocol stack to establish a TCP connection and obtains the configuration information of the fan master communication station through the web terminal. The configuration information of the fan master communication station includes the configuration information of the fan master and the configuration information of the slave station. The configuration information of the slave station includes the protocol used by the slave station, baud rate, slave station site number, function code, register length, and slave station network IP. The configuration information of the fan master includes: PLC model, master station site number, and master station network IP.

[0013] S2. Convert the configuration information of the wind turbine master and slave devices into JSON format based on the custom protocol and store it in the virtual file system;

[0014] S3. Use the tool cjson to convert the JSON-formatted file to obtain the configuration information of the wind turbine master and slave devices, and import the configuration information of the wind turbine master and slave devices into the RTT scheduling interface;

[0015] S4, the buffer in the MCU obtains digital values ​​from the external sensor and stores them in the slave data stream;

[0016] S5. Configure the corresponding protocol stack according to the different protocol types of the wind turbine master control, that is, configure the protocol stack according to the protocol stack interface supported by the wind turbine master control;

[0017] S6, RTT scheduling interface selects the corresponding protocol stack according to the configuration information of the slave station;

[0018] S7. Use the rt-thread scheduling mechanism to transmit the slave data stream to the wind turbine master control, and the temporary slave station is built;

[0019] S8. Perform short-term multi-protocol switching test and long-term single-protocol stability test on temporary slave stations;

[0020] S9. When both tests are qualified, the temporary slave becomes the final slave and the slave construction is completed.

[0021] As a further preferred embodiment of the present invention, the t-thread scheduling mechanism specifically includes:

[0022] S6.1. Read the configuration information of the wind turbine master and slave devices, configure the protocol type and protocol parameters of the wind turbine master, and use a semaphore to trigger a detection thread; the detection thread includes hardware thread decoupling and software thread decoupling;

[0023] S6.2, hardware thread decoupling initializes the hardware corresponding to the protocol stack according to the configuration information of the slave device;

[0024] S6.3. Software thread decoupling: Through the thread mechanism, combined with the different protocols of the wind turbine master control, several protocol stacks are divided, and each protocol stack forms an independent stack space;

[0025] S6.4. Initialize the protocol stack according to the configuration information of the wind turbine master and slave devices, and use mutex locks and semaphores to control resource access to ensure that the protocol stacks are isolated from each other;

[0026] S6.5. The protocol stack matches the corresponding protocol stack interface and communicates externally.

[0027] S6.6, the RTT scheduling interface matches the corresponding protocol stack according to the current configuration information of the device, and transmits the slave station data stream with the stored data volume to the corresponding protocol stack.

[0028] As a further preferred embodiment of the present invention, the short-time multi-protocol switching test includes:

[0029] Use a Python automation script to periodically poll and switch the protocol stack to check whether the protocol stack has been successfully switched and whether communication with the wind turbine master control is normal. The periodic polling includes switching the protocol stack every 2-5 minutes, and the test time is set to one to two weeks.

[0030] As a further preferred embodiment of the present invention, the long-term single-protocol stability test includes:

[0031] Use the same protocol to communicate with the wind turbine master control for a long time, and use a Python automated script to record the packet loss rate and whether the communication is disconnected. The long time is set to one to two weeks. Beneficial effects:

[0032] The multi-protocol slave station design for a wind power control system proposed in this invention has the following beneficial effects compared with the prior art:

[0033] 1. The present invention supports a variety of network protocols by adjusting the adapted protocol through configuration information, and can integrate the equipment of different protocols with high adaptability and standardization;

[0034] 2. The present invention configures multiple protocols, thereby improving the flexibility and scalability of the network;

[0035] 3. The present invention enables communication between different network devices and applications, thereby achieving more efficient data transmission and a better user experience;

[0036] 4. Improve system stability and reliability: The multi-protocol slave station design adopted in the present invention can improve the reliability of the wind power control system. When one protocol fails, other protocols can take over its work, thereby ensuring the stability and reliability of the system.

[0037] 5. Reduce hardware costs: The present invention adopts certain alternative solutions to reduce hardware costs, especially in the case of software-defined multi-protocol and virtualized multi-protocol, the hardware cost is significantly reduced, which can save a lot of investment;

[0038] 6. Improve flexibility and scalability: The present invention adopts virtualized multi-protocol and software-defined multi-protocol methods to improve the flexibility and scalability of the system, thereby better meeting possible future needs.

[0039] 7. Enhanced system interoperability: Wind power control systems from different manufacturers may use different protocols. The present invention adopts a multi-protocol slave station design to achieve interoperability between different manufacturers, thereby better realizing resource sharing and information exchange. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] FIG1 is a diagram showing a multi-protocol slave station data flow according to the present invention;

[0041] FIG2 is a diagram of the overall architecture of a multi-protocol slave station according to the present invention;

[0042] FIG3 is a flow chart of the RTT scheduling interface of the present invention. DETAILED DESCRIPTION

[0043] The present invention will be described in detail below with reference to the accompanying drawings and specific embodiments.

[0044] The present invention uses rt-thread as the main system architecture, divides the source program of the adaptation of four protocol stacks (MODBUS-RTU, PROFIBUS-DP, CANOPEN, CAN) into four main processes, removes program coupling, performs internal parameter changes, and uses an external configuration tool to control the current adaptation protocol. It supports a variety of different network protocols, thereby improving the flexibility and scalability of the network. This technology enables communication between different network devices and applications, thereby achieving more efficient data transmission and a better user experience.

[0045] The present invention is applicable to cabin radar, ground-based radar, laser radar, optical fiber sensor, and clearance radar.

[0046] Embodiment 1: In conjunction with Figure 1, a multi-protocol slave station design for a wind power control system includes a web terminal, an external sensor, a single-chip microcomputer MCU and a wind turbine master control. The web performs protocol switching and configures the corresponding device baud rate and slave station number. The external sensor receives external analog quantities and converts the analog signals into digital quantities; the single-chip microcomputer MCU includes a TCP-SPI converter, a virtual file system, a buffer, an SFUD interface, an eth interface, an RTT scheduling interface (a conversion interface based on the RT-THREAD protocol) and several protocol stack interfaces. The single-chip microcomputer MCU is connected to the web terminal through the TCP protocol, and the single-chip microcomputer MCU is connected to the external sensor through the eth interface and receives the digital quantities converted by the external sensor. The virtual file system is constructed based on FatFs by the SFUD interface through SPI FLASH. SPI FLASH is a non-volatile memory based on the SPI serial communication interface; the virtual file system is used to store device configuration information; the single-chip microcomputer MCU compares and schedules the digital quantities and configuration information through the RTT scheduling interface, distributes them to the corresponding protocol stack interface, and transmits them to the wind turbine master control.

[0047] Example 2: In conjunction with Figure 2, a multi-protocol slave station design for a wind power control system includes the following steps:

[0048] S1. The MCU uses the LWIP protocol stack to establish a TCP connection. LWIP is a TCP / IP-based protocol stack that includes basic protocols such as TCP and HTTP. It obtains the configuration information of the wind turbine master control communication master station through the web terminal.

[0049] The fan master control communication master station is the interactive device between the fan master control and the slave station. The configuration information of the fan master control communication master station includes the configuration information of the fan master control and the configuration information of the slave station. The configuration information of the slave station includes the protocol used by the slave station, baud rate, slave station site number, function code, register length, and slave station network IP.

[0050] The configuration information of the slave station is distinguished according to the protocol used by the slave station. Profibus-DP involves the slave station site number and baud rate; Modbus-RTU involves the slave station site number, baud rate, function code, and register length; Modbus-Tcp involves the slave station site number, baud rate, function code, register length, and slave station network IP; Canopen involves the slave station site number and baud rate.

[0051] The configuration information of the fan master control includes: PLC model, master station site number, and master station network IP.

[0052] S2. Convert the configuration information of the wind turbine master and slave devices into JSON format based on the custom protocol and store it in the virtual file system;

[0053] S3. Use the tool cjson to convert the JSON-formatted file to obtain the configuration information of the wind turbine master and slave devices, and import the configuration information of the wind turbine master and slave devices into the RTT scheduling interface;

[0054] S4, the buffer in the MCU obtains digital values ​​from the external sensor and stores them in the slave data stream;

[0055] S5. Configure the corresponding protocol stack according to the different protocol types of the wind turbine master control, that is, configure the protocol stack according to the protocol stack interface supported by the wind turbine master control;

[0056] The different protocols of the wind turbine master control include CANopen protocol, MODBUS-RTU protocol, MODBUS-TCP protocol and PROFIBUS-DP protocol.

[0057] S6. The RTT scheduling interface selects the corresponding protocol stack according to the configuration information of the slave station.

[0058] S7. Use the rt-thread scheduling mechanism to transmit the slave data stream to the wind turbine master control, and the temporary slave station is built.

[0059] S8. Perform short-term multi-protocol switching test and long-term single-protocol stability test on temporary slave stations.

[0060] S9. When both tests are qualified, the temporary slave becomes the final slave and the slave construction is completed.

[0061] Example 3: With reference to FIG3 , the t-thread scheduling mechanism specifically includes:

[0062] S6.1. Read the configuration information of the wind turbine master and slave devices, configure the protocol type and protocol parameters of the wind turbine master, and use a semaphore to trigger a detection thread; the detection thread includes hardware thread decoupling and software thread decoupling.

[0063] S6.2, hardware thread decoupling initializes the hardware corresponding to the protocol stack according to the configuration information of the slave device; if profibus-dp or modbus-rtu is used, the RS485 interface is initialized; if canopen is used, the CAN interface is initialized; if modbus-tcp is used, the ETH interface is initialized; and the parameters in the connector are called through RTT to determine the switch selector to adapt to the CAN interface or DP / 485 interface.

[0064] S6.3. Software thread decoupling uses the thread mechanism and combines different protocols of the wind turbine master control to divide several protocol stacks, each of which forms an independent stack space.

[0065] S6.4. Initialize the protocol stack according to the configuration information of the wind turbine master and slave devices, and use mutex locks and semaphores to control resource access to ensure that the protocol stacks are isolated from each other.

[0066] S6.5. The protocol stack matches the corresponding protocol stack interface and communicates externally.

[0067] S6.6, the RTT scheduling interface matches the corresponding protocol stack according to the current configuration information of the device, and transmits the slave station data stream with the stored data volume to the corresponding protocol stack.

[0068] Example 4: After the temporary slave station is built, a short-term multi-protocol switching test and a long-term single-protocol stability test are performed

[0069] Test plan 1: Short-term multi-protocol switching test

[0070] Use Python automation scripts to periodically poll and switch the protocol stack (switching every 2-5 minutes for one to two weeks) to check whether the protocol stack has been successfully switched and whether communication with the PLC in the wind turbine master control is normal.

[0071] Test plan 2: Long-term single-protocol stability test

[0072] Use the same protocol to communicate with the PLC in the wind turbine master control for a long period of time (one to two weeks for each protocol test), and use a Python automated script to record the packet loss rate and whether the communication is disconnected.

[0073] 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 above embodiments do not limit the present invention in any form, and any technical solutions obtained by equivalent replacement or equivalent transformation fall within the scope of protection of the present invention.

Claims

1. A multi-protocol slave station design for wind power control system, characterized in that: It includes a web terminal, an external sensor, a single-chip microcomputer MCU and a fan main control. The web performs protocol switching and configures the corresponding device baud rate and slave station number. The external sensor receives external analog quantities and converts analog signals into digital quantities. The single-chip microcomputer MCU includes a TCP-SPI converter, a virtual file system, a buffer, an SFUD interface, an eth interface, an RTT scheduling interface and several protocol stack interfaces. The single-chip microcomputer MCU is connected to the web terminal through the TCP protocol, and the single-chip microcomputer MCU is connected to the external sensor through the eth interface and receives the digital quantity converted by the external sensor. The virtual file system is used to store the configuration information of the device. The single-chip microcomputer MCU compares and schedules the digital quantity and configuration information through the RTT scheduling interface, distributes them to the corresponding protocol stack interface, and transmits them to the fan main control.

2. A multi-protocol slave station design for a wind power control system according to claim 1, characterized in that: The virtual file system is constructed based on FatFs by the SFUD interface through SPI FLASH, and SPI FLASH is a non-volatile memory based on the SPI serial communication interface.

3. A multi-protocol slave station design for a wind power control system according to claim 1, characterized in that: The following steps are involved: S1. The single-chip microcomputer MCU uses the LWIP protocol stack to build a TCP connection, and obtains the configuration information of the fan master control communication master station through the web terminal. The configuration information of the fan master control communication master station includes the configuration information of the fan master control and the configuration information of the slave station. The configuration information of the slave station includes the protocol used by the slave station, the baud rate, the slave station site number, the function code, the register length, and the slave station network IP; The configuration information of the fan master control includes: PLC model, master station site number, master station network IP; S2. Convert the configuration information of the wind turbine master control and slave devices into JSON format based on the custom protocol and store it in the virtual file system; S3. Use the tool cjson to convert the file in json format to obtain the configuration information of the wind turbine master control and slave station equipment, and import the configuration information of the wind turbine master control and slave station equipment into the RTT scheduling interface; S4, the buffer in the MCU obtains digital quantities through external sensors and stores them in the slave station data stream; S5. According to different protocol types of the wind turbine master control, the corresponding protocol stack is configured, that is, the protocol stack is configured according to the protocol stack interface supported by the wind turbine master control; S6, the RTT scheduling interface selects the corresponding protocol stack according to the configuration information of the slave station; S7, use the rt-thread scheduling mechanism to transmit the slave data stream to the fan master control, and the temporary slave is built; S8. Perform short-term multi-protocol switching test and long-term single-protocol stability test on temporary slave stations; S9. When both tests are qualified, the temporary slave station becomes the final slave station and the slave station construction is completed.

4. A multi-protocol slave station design for a wind power control system according to claim 3, characterized in that: The different protocol types of the device include canopen protocol, modbus-rtu protocol, modbus-tcp protocol and profibus-dp protocol.

5. A multi-protocol slave station design for a wind power control system according to claim 3, characterized in that: The t-thread scheduling mechanism specifically includes: S6.

1. Read the configuration information of the fan master control and slave devices, configure the protocol type and protocol parameters of the fan master control, and use the semaphore to trigger the detection thread; the detection thread includes hardware thread decoupling and software thread decoupling; S6.2, hardware thread decoupling initializes the hardware corresponding to the protocol stack according to the configuration information of the slave device; S6.3, software thread decoupling Through the thread mechanism, combined with different types of protocols of the wind turbine master control, several protocol stacks are divided, and each protocol stack forms an independent stack space; S6.

4. Initialize the protocol stack according to the configuration information of the wind turbine master control and slave devices, and use mutex locks and semaphores to control resource access to ensure that the protocol stacks are separated from each other; S6.5, the protocol stack matches the corresponding protocol stack interface and communicates externally; S6.6, the RTT scheduling interface matches the corresponding protocol stack according to the current configuration information of the device, and transmits the slave station data stream storing the data volume to the corresponding protocol stack.

6. A multi-protocol slave station design for a wind power control system according to claim 3, characterized in that: The short-time multi-protocol switching test includes: Use a python automation script to periodically poll and switch the protocol stack to check whether the protocol stack is successfully switched and whether the communication with the wind turbine master control is normal; the periodic polling includes switching the protocol stack every 2-5 minutes, and the test time is set to one to two weeks.

7. A multi-protocol slave station design for a wind power control system according to claim 3, characterized in that: The long-term single-protocol stability test includes: The same protocol is used to communicate with the wind turbine master control for a long time, and the packet loss rate and whether the communication is disconnected are recorded through a python automation script. The long time is set to one to two weeks.

Images