Distributed multi-screen collaborative touch control panel assembly system and method

Abstract

The invention discloses a distributed multi-screen collaborative touch control panel assembly system and a distributed multi-screen collaborative touch control panel assembly method. The touch control type control panel assembly system comprises more than three touch control type control panel assemblies, and the touch control panel assemblies are interconnected and intercommunicated through a two-way bus. Information synchronization and updating are carried out among the touch control panel assemblies through the messages, and a distributed control structure is formed. The system has the beneficial effects that the cooperative work mechanism of the multiple touch airborne control panel assemblies is realized in a manner of interconnection, intercommunication and mutual backup of the touch airborne control panel assemblies, so that the reliability and the real-time performance of a control panel assembly system in an airborne cockpit when the control panel assembly system is operated by multiple drivers at the same time are ensured; and meanwhile, the situation of safety and reliability risks caused by faults of a single touch screen is also avoided.

Description

Technical Field

[0001] The present invention relates to an on-board control panel in an aircraft cockpit. In particular, it is a distributed multi-screen collaborative touch control panel component system and method. Background Art

[0002] With the rapid development of visualization technology and artificial intelligence technology, more and more traditional hardware devices have been replaced by intelligent hardware devices. Inevitably, the traditional control panel components inside the on-board cockpit are also facing the trend of being replaced by high-definition and intelligent touch screens. However, different from the application environment of general control devices, the on-board cockpit control panel components have extremely high requirements in terms of maneuverability, reliability, and real-time performance. Although a single intelligent touch screen softwareizes the hardware of the on-board cockpit control panel component and improves the system integration, when actually operating, it will face the problem of timely response when the control panel component system is manipulated by multiple people at the same time, and there is even a situation where a single touch screen suddenly fails while the control panel component can still be normally manipulated and respond, which is unacceptable in the safety requirements of on-board devices. Summary of the Invention

[0003] The present invention provides a distributed multi-screen collaborative digital touch intelligent control panel component system and method, which solves the real-time problem of multiple drivers clicking simultaneously faced by a single-screen touch on-board cockpit control panel component and the safety problem caused by a single touch screen failure, and ensures the reliability, safety, and real-time performance of the driver during driving operations.

[0004] In order to achieve the above invention purpose, the technical solution of the present invention is as follows: Compared with the prior art, the beneficial effects of the present invention are at least as follows: By means of the interconnection and mutual backup of touch on-board control panel components, a mechanism for the collaborative work of multiple touch on-board control panel components is realized, which ensures the reliability and real-time performance of the control panel component system in the on-board cockpit when faced with being operated by multiple drivers at the same time, and also avoids the situation of safety and reliability risks caused by a single touch screen failure. Brief Description of the Drawings

[0005] Figure 1 It is a schematic diagram of the system architecture of the present invention.

[0006] Figure 2 It is a schematic diagram of the software message of the present invention.

[0007] Figure 3 It is a system working flowchart of the present invention.

[0008] Figure 4 It is a multi-screen synchronization strategy diagram of the system of the present invention. Detailed Embodiments

[0009] The present invention will be further described in detail below with reference to the accompanying drawings through specific embodiments. It should be noted here that the description of these embodiments is for helping to understand the present invention, but does not limit the present invention. In addition, the technical features involved in the various embodiments of the present invention described below can be combined with each other as long as they do not conflict with each other.

[0010] Please refer to Figures 1 to 4 , which shows a touch control panel component system for distributed multi-screen collaboration.

[0011] The touch control panel component system includes: three touch control panel components. In other embodiments, the number of touch control panel components is not limited to 3 and can be extended to more.

[0012] The touch control panel components are interconnected through a dual-channel CAN bus. The touch control panel components synchronize and update information through the above CAN messages to form a distributed control structure. The information interaction between the touch control panel components includes: data messages sent from the aircraft system to the touch control panel components, data messages uploaded from the touch control panel components to the aircraft system, and synchronization messages between the touch control panel components. In other embodiments, the communication method is not limited to CAN messages and is also applicable to other bus communication methods. The message types are not limited to the above bus message types, and the user can customize the message names and functions according to actual needs.

[0013] The touch control panel component has a hardware part and a software part. The front end of the hardware part is a liquid crystal touch display screen, a power drive board, a communication interface board, and a processor core board. The power drive board provides a working power supply of 24VD and a backup power supply of 28VD for the entire hardware part. The communication interface board includes 2-way serial communication and 2-way network communication. The RS232 serial communication is mainly used for external debugging and serial communication with other devices. The network port is mainly used for network communication during debugging and network communication between different devices. The software part is the P2020 chip running in the processor core board. The software part mainly executes functions such as system hardware initialization, touch screen display driving, CAN bus transceiver, message decoding sent from the aircraft system, capturing touch inputs on the screen of the touch control panel component, encoding of uploaded messages, application program scheduling, interface switching, and multi-screen data synchronization.

[0014] Install the touch control panel component system on the top of the front end of the aircraft cockpit. The rear housing of the system is embedded in the mounting plate on the top of the cockpit. The backup housing is provided with communication and power interfaces to achieve data communication between different touch control panel components and data communication between the touch control panel component and the aircraft system. The front end of the system is the touch display screen of each touch control panel component. After installation, the interface of each touch control panel component is parallel to the cockpit panel on the top of the head. The touch display screen of the touch control panel component provides a realized information display and human-machine interaction interface for the pilots in the cockpit.

[0015] The touch control panel component system operates according to the following process: Step S1: Power on the system.

[0016] Step S2: After power-on, the touch control panel component runs the bootloader kernel program to complete hardware status detection and initialization. If the touch control panel component completes the hardware status detection and initialization, it jumps to Step S3. If the touch control panel component does not complete the hardware status detection and initialization, it returns to Step S1.

[0017] Step S3: The touch control panel component loads the application program: Sub-step S31, CAN message reading and decoding; Sub-step S32, touch screen driving and display; Sub-step S33, capture the touch action on the screen. If no touch action is captured, update the always cycle and return to Sub-step S31. If a touch action is captured, read the touch information.

[0018] Step S4: According to the appendix Figure 4The synchronization strategy shown is used for message synchronization between touchscreens. The specific description is as follows: Generally, it is divided into 3 operating modes: idle state, multi-screen synchronization state, and local control state. The idle state means that there are no touch events on the touchscreen. When in the idle state, if a local touch event is detected, it enters the local control state. At this time, local touch events are preferentially processed. When the software is in the idle state, if a bus synchronization event is detected, it enters the multi-screen synchronization state. At this time, bus touch events are preferentially processed. When in the multi-screen synchronization state or the local control state, only events from the corresponding event sources are processed, and events from other event sources are temporarily ignored. For example, when in the multi-screen synchronization state, local touch events are not responded to temporarily. When in the multi-screen synchronization state or the local control state, if it is detected that the touch event has been released, a short timer of 100 ms is started. Before the timer expires, the original event sources (bus or local) are still preferentially processed. Once a new event is detected on the original event source, it re-enters the original state. If no event is detected after the timer times out, it switches to the idle state. When in the multi-screen synchronization state, if no event message from the bus is detected for a long time, it automatically enters the idle state. When in the multi-screen synchronization state, if a local touch event is detected, it is forced into the local touch state after 3 s without a synchronization message. When in the local touch state, each processed local event will be sent to other screens through the CAN bus so that other screens can respond synchronously. Among them, the core of multi-screen synchronization lies in the correct switching between multiple event sources. Each event source corresponds to a buffer, which are: 1) local events; 2) bus event synchronization buffer 1; and 3) bus event synchronization buffer 2.

[0019] Step S5: Determine whether the message synchronization between the touch control board components is successful: If so, jump to step S6; if not, further determine whether the touch control board components are faulty: If so, return to step S1; if not, return to step S4.

[0020] Step S6: Determine whether the message of the touch action read needs to be uploaded: If so, encode the data and upload it to the aircraft system through the dual-channel CAN bus.

[0021] Step S7: Return to step S3 and execute the tasks of the next clock cycle of the application program.

[0022] The above only expresses the implementation modes of the present invention, and its description is relatively specific and detailed, but it cannot be understood as a limitation on the scope of the invention patent. It should be noted that for those of ordinary skill in the art, without departing from the concept of the present invention, several modifications and improvements can still be made, and these all belong to the protection scope of the present invention. Therefore, the protection scope of the present invention patent shall be subject to the appended claims.

Claims

1. A touch control panel component system for distributed multi-screen collaboration, characterized in that, Including: More than three touch control panel components, which are interconnected through a dual - bus. Information synchronization and update are carried out among the touch control panel components through the above - mentioned messages, forming a distributed control structure.

2. The touch control panel component system for distributed multi-screen collaboration according to claim 1, characterized in that, The information interaction among the touch control panel components includes: data messages sent from the aircraft system to the touch control panel components, data messages uploaded from the touch control panel components to the aircraft system, and synchronization messages among the touch control panel components.

3. The touch control board component system for distributed multi-screen collaboration according to claim 1, wherein The touch control panel component has a hardware part and a software part. The front - end of the hardware part is a liquid crystal touch display screen, a power - driving board, a communication interface board, and a processor core board. The power - driving board provides a working power supply of 24VD and a backup power supply of 28VD for the entire hardware part. The communication interface board includes 2 - way serial communication and 2 - way network communication. The RS232 serial communication is mainly used for external debugging and serial communication with other devices. The network port is mainly used for network communication during debugging and network communication between different devices. The software part is the P2020 chip running in the processor core board. The software part mainly performs system hardware initialization functions, touch - screen display driving functions, CAN - bus sending and receiving functions, message receiving and decoding functions sent from the aircraft system, functions of capturing touch inputs on the screen of the touch control panel component, encoding functions of uploaded messages, application program scheduling functions, interface switching functions, and multi - screen data synchronization functions.

4. A method for a distributed multi - screen collaborative touch control panel component system, characterized in that Step S1: Power on the system; Step S2: After power - on, the touch control panel component runs the boot - loading kernel program to complete hardware status detection and initialization. If the touch control panel component completes hardware status detection and initialization, jump to Step S3; if the touch control panel component does not complete hardware status detection and initialization, return to Step S1. Step S3: The touch control panel component loads the application program: Sub - step S31, CAN message reading and decoding; Sub - step S32, touch - screen driving and display; Sub - step S33, capture the touch action on the screen. If no touch action is captured, update the clock cycle and return to Sub - step S31; if a touch action is captured, read the touch information. Step S4: Perform message synchronization among the touch - screens. Step S5: Determine whether the message synchronization among the touch control panel components is successful. If so, jump to Step S6; if not, further determine whether the touch control panel component is faulty. If so, return to Step S1; if not, return to Step S4. Step S6: Determine whether the message of the captured touch action needs to be uploaded. If so, encode the data and upload it to the aircraft system through the dual - way CAN bus. Step S7: Return to Step S3 to execute the tasks of the next clock cycle of the application program.

5. The method of the touch control board component system for distributed multi-screen collaboration according to claim 4, wherein, In step S4, there are generally three operating modes: idle mode, multi-screen synchronization mode, and local control mode; the idle mode means: the state where there is no touch event on the touch screen. When in the idle mode, if a local touch event is detected, it enters the local control mode, and at this time, the local touch event is preferentially processed, and the software is in the idle mode. If a bus synchronization event is detected, it enters the multi-screen synchronization mode, and at this time, the bus touch event is preferentially processed; when in the multi-screen synchronization mode or the local control mode, only the events from the corresponding event sources are processed, and the events from other event sources are temporarily ignored; when in the multi-screen synchronization mode or the local control mode, if it is detected that the touch event has been released, a short timer is started. Before the timer expires, the original event source (bus or local) is still preferentially processed; once a new event is detected on the original event source, it re-enters the original state; If no event is detected after the timer times out, it switches to the idle state; When in the multi-screen synchronization mode, if no event message from the bus is detected for a long time, it automatically enters the idle mode; when in the multi-screen synchronization mode, if a local touch event is detected, it is forced to enter the local touch state after a certain time without a synchronization message; when in the local touch state, each processed local event will be sent to other screens via the CAN bus so that other screens can respond synchronously; among them, the core of multi-screen synchronization lies in the correct switching between multiple event sources, and each event source corresponds to a buffer, which are respectively: 1) local events; 2) bus event synchronization buffer 1; 3) bus event synchronization buffer 2.

Images