Multi-split air conditioner

Abstract

The embodiment of the invention discloses a multi-split air conditioner which comprises a bus and a plurality of node devices connected to the bus, and the node devices comprise a plurality of indoor units and / or a plurality of outdoor units. Each node device comprises a corresponding controller, the interrupt end of each controller and the receiving end of each controller are connected with the sending end of the bus, and the sending end of each controller is connected with the receiving end of the bus; each controller comprises a timer; under the condition that the interrupt end of each controller does not detect the interrupt signal within the target duration, sending target data to other node equipment through the bus; wherein the target duration comprises first target duration and second target duration, the first target duration of each node device is the same, the second target duration of each node device is different, and the second target duration of each node device is generated by the timer of each controller. According to the embodiment of the invention, the communication efficiency of the multi-split air conditioner is improved.

Description

Technical Field

[0001] The embodiments of the present application relate to the technical field of air conditioning, and are related to but not limited to a multi-split air conditioner. Background Art

[0002] A multi-split air conditioner is an air conditioning system that has multiple indoor units, multiple outdoor units, and may even have other electronic equipment on a bus line between the indoor and outdoor units.

[0003] In the communication process of this multi-split air conditioner involving a large number of node devices, the traditional communication method is to set up a host and other devices as slaves. The host polls each slave one by one in a certain order, and the slave can only respond to the host after being asked.

[0004] However, this communication method has low communication efficiency and can no longer meet the requirements of existing multi-split air conditioners in terms of communication data volume, communication efficiency, and data update speed. Therefore, how to improve the communication efficiency of multi-split air conditioners has become a technical problem that needs to be solved urgently. Summary of the invention

[0005] In view of this, a multi-split air conditioner provided in an embodiment of the present application can solve this technical problem.

[0006] The embodiment of the present application provides a multi-split air conditioner, comprising:

[0007] A bus, and a plurality of node devices respectively connected to the bus, wherein the plurality of node devices include a plurality of indoor units and / or a plurality of outdoor units;

[0008] Each node device includes a corresponding controller, an interrupt terminal of each controller and a receiving terminal of each controller are connected to a transmitting terminal of the bus, and a transmitting terminal of each controller is connected to a receiving terminal of the bus;

[0009] Each of the controllers includes a timer;

[0010] The controller is configured to:

[0011] When the interruption end does not detect an interruption signal within a target time period, sending target data to other node devices via the bus;

[0012] Among them, the target duration includes a first target duration and a second target duration, the first target duration of each node device is the same, the second target duration of each node device is different, and the second target duration of each node device is generated by the timer of each controller.

[0013] In the embodiment of the present application, each node device in the multi-split air conditioner can determine whether the bus is idle by detecting the interrupt signal through the interrupt terminal of the controller, that is, each node device can grab the line when detecting that the bus is in an idle state, and send data after successfully grabbing the line. This communication method improves the communication efficiency of the multi-split air conditioner, has high reliability, flexible communication mechanism, and is suitable for multi-split air conditioners with a large number of nodes on the bus. In addition, since the second target duration corresponding to each node device is different, it can effectively avoid multiple node devices from successfully grabbing the line at the same time, and effectively avoid data conflicts.

[0014] In some embodiments, the timer is provided with a timing function, and the controller sends target data to other power-saving devices through the bus when the interrupt terminal does not detect an interrupt signal within the target duration, and is configured as follows:

[0015] When it is determined to send the target data to the other node device, start the timing function of the timer, and the timing duration of the timer is the target duration;

[0016] During the timing process of the timer, detecting the interrupt signal through the interrupt terminal;

[0017] When the timer ends and the interrupt signal is not detected, the target data is sent to the other node devices through the bus.

[0018] In this embodiment, when each node device in the multi-split air conditioner has a data transmission demand, the counting function of the timer can be started while the interrupt signal is detected at the interrupt end, and the timing is performed according to the corresponding timing duration. When the interrupt signal is not detected at the interrupt end after the timing, it indicates that the bus is idle, that is, the line is grabbed successfully, and data can be sent directly. This method of detecting whether there is an interrupt signal within the corresponding timing duration simplifies the communication line grabbing mechanism, which helps to improve communication efficiency.

[0019] In some embodiments, the controller is further configured to:

[0020] During the timing process of the timer, when the interrupt signal is detected through the interrupt end, the timer is reset, and the timing duration of the reset timer is the target duration.

[0021] In this embodiment, during the timer timing process of each node device in the multi-split air conditioner, as long as an interrupt signal is detected indicating that the bus is in a non-idle state, the timing will be restarted according to the corresponding timing duration. This method of resetting the timer timing when an interrupt signal is detected can dynamically adjust the line grabbing strategy according to the bus status, and can quickly restart the timing and grab the line for the node device, which helps to improve the timeliness and efficiency of data transmission, and further improve the reliability of the communication method.

[0022] In some embodiments, the second target duration of each node device is generated by a timing error of a timer of each controller, an error in a power-on time of each node device, and an error in an initialization completion time of each controller.

[0023] In this embodiment, different timing durations are generated for each node device according to the errors of different hardware components. This method allows each node device to generate a different timing duration, which can effectively prevent multiple node devices from successfully grabbing the line at the same time, that is, it can effectively avoid data conflicts on the bus.

[0024] In some embodiments, the controller is further configured to:

[0025] In the process of sending the target data to the other node devices through the bus, when a data conflict is detected on the bus, the sending of the target data to the other node devices is stopped.

[0026] In this embodiment, when a data conflict is detected on the bus, the adverse effect of the data conflict on the multi-split air conditioner can be reduced in time by stopping sending data.

[0027] In some embodiments, after stopping sending the target data to the other node devices, the controller is further configured to:

[0028] Changing the first target duration to a third target duration to obtain a changed target duration, wherein the changed target duration includes the third target duration and the second target duration, wherein the third target duration is shorter than the first target duration;

[0029] When the interrupt end does not detect an interrupt signal within a target duration, the controller sends target data to other node devices via the bus, and is configured to:

[0030] When the interrupt end does not detect the interrupt signal within the changed target duration, the target data is sent to other node devices via the bus.

[0031] In this embodiment, when a data conflict is detected on the bus and data transmission is stopped, reducing the first target time helps to improve the success rate of the node device that detects the data conflict when grabbing the line in the next communication, thereby reducing the possibility of future conflicts and improving the communication efficiency of the node device.

[0032] In some embodiments, when the interrupt terminal does not detect the interrupt signal within the changed target duration, after sending the target data to other node devices via the bus, the controller is further configured to:

[0033] The third target duration is changed to the first target duration.

[0034] In this embodiment, after the node device corresponding to the first target duration is changed and the communication line is successfully grabbed, the third target duration is restored to the first target duration so that the node device grabs the line according to the original time the next time. That is, after the node device successfully sends data, it no longer affects the communication efficiency of other node devices.

[0035] In some embodiments, the bus includes a sending channel and a receiving channel. When the controller detects that a data conflict exists on the bus during the process of sending the target data to the other node devices through the bus, the controller is configured to:

[0036] In the process of sending the target data to the other node devices through the sending channel, receiving the target data through the receiving channel to obtain received data;

[0037] Determining whether the bus hits at least one of the preset conflict detection rules according to the target data and the received data;

[0038] When the bus hits the preset conflict detection rule, detecting that there is a data conflict on the bus;

[0039] The preset conflict detection rule includes at least one of a parity error of the received data, a data frame error of the received data, a duration of receiving the target data exceeding a preset duration, and inconsistency between the target data and the received data.

[0040] In this embodiment, each node device receives its own data while sending data through the sending channel and receiving channel of the bus, and determines whether there is a data conflict on the bus based on the sent data and the received data combined with the preset conflict detection rules. This method helps to improve the efficiency and accuracy of data conflict detection.

[0041] In some embodiments, the controller determines to send the target data to the other node devices, and is configured to:

[0042] The target data to be sent to the other node devices is determined from data of multiple data types according to a preset sending priority, wherein the data of the multiple data types include at least one of change type data, periodic collection type data, and broadcast type data, and the priorities of the change type data, the periodic collection type data, and the broadcast type data decrease in sequence.

[0043] In this embodiment, the type of data sent each time is determined by a preset sending priority, which can ensure that more important data is sent first, and can also avoid sending a large amount of data at the same time, causing delays in multi-split air conditioner data transmission and reducing data transmission stability.

[0044] In some embodiments, the controller is further configured to:

[0045] Receiving response data sent by the other node device, the response data is sent by the other node device after receiving the target data and when a preset waiting time ends, and the preset waiting time is less than the target time;

[0046] The response data is used to indicate whether the other node device receives the target data correctly or incorrectly.

[0047] In this embodiment, after receiving data sent by a node device, the receiver does not need to detect whether the bus is in an idle state, and can directly send response data within a shorter preset waiting time, which helps the sender to quickly confirm whether the data is successfully received, thereby improving the communication efficiency when the sender determines the reliability of data transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] The drawings herein are incorporated into the specification and constitute a part of the specification. These drawings illustrate embodiments consistent with the present application and are used together with the specification to illustrate the technical solution of the present application.

[0049] Figure 1 It is a schematic diagram of a communication system of a multi-split air conditioner disclosed in an embodiment of the present application;

[0050] Figure 2 It is a schematic diagram of the architecture of the controller disclosed in the embodiment of the present application;

[0051] Figure 3 It is a flow chart of a communication control method for a multi-split air conditioner disclosed in an embodiment of the present application;

[0052] Figure 4 It is a timing diagram of node device communication disclosed in the embodiment of the present application;

[0053] Figure 5It is a flow chart of another communication control method for a multi-split air conditioner disclosed in an embodiment of the present application;

[0054] Figure 6 It is a timing diagram of multiple node devices simultaneously grabbing line communication disclosed in the embodiment of the present application;

[0055] Figure 7 It is a flow chart of another communication control method of a multi-split air conditioner disclosed in an embodiment of the present application;

[0056] Figure 8 It is a timing diagram of multiple node devices in an embodiment of the present application that simultaneously seize the line for communication after a data conflict occurs. DETAILED DESCRIPTION

[0057] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the specific technical solution of the present application will be further described in detail below in conjunction with the drawings in the embodiments of the present application. The following embodiments are used to illustrate the present application, but are not used to limit the scope of the present application.

[0058] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein are only for the purpose of describing the embodiments of this application and are not intended to limit this application.

[0059] In the following description, reference is made to “some embodiments”, which describe a subset of all possible embodiments, but it will be understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0060] It should be pointed out that the terms "first\second\third" involved in the embodiments of the present application are used to distinguish similar or different objects, and do not represent a specific ordering of the objects. It can be understood that "first\second\third" can be interchanged in a specific order or sequence where permitted, so that the embodiments of the present application described here can be implemented in an order other than that illustrated or described here.

[0061] Today's home appliances, due to the rapid development of intelligence and control technology, have put forward higher requirements on communication data volume, communication efficiency, data update speed, etc. Especially for multi-split air conditioners, which are air conditioning systems with multiple indoor units, multiple outdoor units, and even other electronic devices on a bus of the indoor and outdoor units of the air conditioner.

[0062] In the communication process of this multi-split air conditioner involving a large number of node devices, the traditional multi-split air conditioner adopts a master-slave structure and adopts the method of host polling slave responses, that is, all node devices are set as one host and multiple slaves. For example, in the communication process of the multi-split air conditioner, the outdoor unit is generally used as the host, and other indoor units or node devices are used as slaves. The host initiates communication commands to each slave one by one in a certain order, and the slave can only respond to the host after being asked. This communication method is usually suitable for multi-split air conditioners with a small number of node devices connected to the bus (less than 32 node devices) and low requirements for the real-time performance of data interaction.

[0063] However, when faced with complex multi-split air conditioners with a large number of node devices (for example, the number of nodes on some multi-split air conditioner buses can be as many as 256), this communication method will have problems such as long polling time, low communication efficiency, and inability to achieve rapid data exchange. At the same time, when a node device needs to send data, the host must poll the node device before the node device can send data. For example, when 180 node devices are connected to the bus, if the communication interval between the host and each slave is 1 second, the communication time for one round is 3 minutes, that is, the host's communication command takes 3 minutes to be transmitted to the farthest node device in this system, and the communication efficiency is obviously very low.

[0064] It can be seen that in the complex multi-split air conditioner communication, the traditional communication method has obvious deficiencies in communication efficiency and can no longer meet the requirements for data interaction of the existing multi-split air conditioners in terms of communication data volume, communication efficiency, and data update speed, which seriously affects the working efficiency of the multi-split air conditioner and is not suitable for multi-split air conditioners with a large number of node devices. Therefore, how to improve the communication efficiency of multi-split air conditioners has become a technical problem that needs to be solved urgently.

[0065] In view of this, the embodiment of the present application provides a multi-split air conditioner, including: a bus and a plurality of node devices connected to the bus respectively, each node device including a corresponding controller, the interrupt end of each controller and the receiving end of each controller are connected to the transmitting end of the bus, and the transmitting end of each controller is connected to the receiving end of the bus; when the interrupt end of each controller does not detect an interrupt signal within the target duration, the target data is sent to other node devices through the bus. When each node device in the multi-split air conditioner proposed in the embodiment of the present application has a data transmission demand, it can determine whether the bus is idle by detecting the interrupt signal by the interrupt end of the controller, that is, each node device can grab the line when it detects that the bus is in an idle state, and can send data when the line grab is successful. This communication method improves the communication efficiency of the multi-split air conditioner, has high reliability, and a flexible communication mechanism, and is suitable for multi-split air conditioners with a large number of nodes on the bus. In addition, since the second target duration corresponding to each node device is different, it can effectively avoid multiple node devices from successfully grabbing the line at the same time, and effectively avoid data conflicts.

[0066] In order to make the purpose and technical solution of the present application clearer and more intuitive, the multi-split air conditioner disclosed in the present application is described in detail below with reference to the accompanying drawings.

[0067] The multi-split air conditioner provided in the embodiment of the present application includes a bus and a plurality of node devices respectively connected to the bus. The plurality of node devices connected to the bus may be composed of devices of various forms, for example, the plurality of node devices may include a plurality of indoor units and / or a plurality of outdoor units.

[0068] It should be noted that the multi-split air conditioner provided in the embodiment of the present application does not have a master unit and a slave unit.

[0069] In some embodiments, the multiple node devices connected to the bus may also include other types of devices such as humidifiers and dehumidifiers to form a multi-split system including an air-conditioning indoor unit, an air-conditioning outdoor unit, and other types of devices, which is not limited in this application. The following will take a multi-split air conditioner composed of multiple indoor units and / or multiple outdoor units connected to the bus as an example to describe the multi-split air conditioner of this solution in detail.

[0070] In the multi-split air conditioner provided in the embodiment of the present application, the bus is used to connect multiple node devices so that data can be transmitted between the node devices through the bus.

[0071] In the multi-split air conditioner provided in the embodiment of the present application, each node device includes a corresponding controller. The controller is the control center of each node device, and uses various interfaces and lines to connect various parts of each node device.

[0072] In the multi-split air conditioner provided in the embodiment of the present application, the bus includes a transmitting end of the bus and a receiving end of the bus, and each controller includes a transmitting end of the controller, a receiving end of the controller, and an interrupt end of the controller. Wherein, the way in which each node device is connected to the bus can be: the transmitting end of each controller is connected to the receiving end of the bus, the receiving end of each controller is connected to the transmitting end of the bus, and the interrupt end of each controller is connected to the transmitting end of the bus, that is, the interrupt end of each controller and the receiving end of each controller are connected to the transmitting end of the bus.

[0073] In the multi-split air conditioner provided in the embodiment of the present application, each node device is connected to the receiving end of the bus through the sending end of each controller, and the receiving end of each controller is connected to the sending end of the bus, forming a data transmission channel of the bus, and the data transmission channel of the bus includes a sending channel and a receiving channel.

[0074] In the multi-split air conditioner provided in the embodiment of the present application, data transmission between various node devices through the bus includes: data transmission and data reception between various node devices through the sending channel and receiving channel of the bus.

[0075] In the multi-split air conditioner provided in the embodiment of the present application, the interrupt end of each controller is used to detect whether there is data transmission on the bus, that is, the interrupt end of each controller is used to detect whether other node devices are performing data transmission through the bus.

[0076] In the multi-split air conditioner provided in the embodiment of the present application, the interrupt end of each controller detects whether there is data transmission on the bus, including: the interrupt end of each controller determines whether there is data transmission on the bus by detecting an interrupt signal, wherein, when the interrupt end of each controller detects the interrupt signal, it indicates that there is data transmission on the bus and the bus is in a non-idle state; when the interrupt end of each controller does not detect the interrupt signal, it indicates that there is no data transmission on the bus and the bus is in an idle state.

[0077] In some embodiments, the bus includes multiple communication ICs, and the multiple communication ICs of the bus correspond one-to-one to the controllers of multiple node devices. Each communication IC is connected to the controller of the corresponding node device, so that data can be transmitted between the node devices through the bus.

[0078] In some embodiments, the controller corresponding to each node device in the multi-split air conditioner may be a microcontroller MCU. It should be understood that in the multi-split air conditioner provided in the embodiment of the present application, the MCU of each node device may be connected to the corresponding communication IC, so that data can be transmitted between the node devices through the corresponding MCU and the corresponding communication IC.

[0079] See also Figure 1 , Figure 1Schematic diagram of the communication system of the multi-split air conditioner disclosed in the embodiment of the present application. Figure 1 The multi-split air conditioner shown includes a bus AB and node devices 1 to 6 respectively connected to the bus AB. The bus AB corresponds to multiple communication ICs. The controllers corresponding to the node devices 1 to 6 can be MCUs. Each MCU includes an MCU sending end, an MCU receiving end, and an MCU interrupt end. Each communication IC includes a sending end OUT and a receiving end IN.

[0080] like Figure 1 In the communication system of the multi-split air conditioner shown, the node devices 1 to 6 are connected to the corresponding communication IC through their respective MCUs, thereby accessing the bus AB, so that data can be transmitted between the node devices 1 to 6. The node devices 1 to 6 are connected to the bus AB in the following manner: the MCU transmitting end of each of the node devices 1 to 6 is connected to the receiving end IN of the corresponding communication IC, the MCU receiving end of each of the node devices 1 to 6 is connected to the transmitting end OUT of the corresponding communication IC, and the interrupt end of each of the node devices 1 to 6 is connected to the transmitting end OUT of the corresponding communication IC, and the node devices 1 to 6 are connected to the bus AB in this connection manner.

[0081] For example, when node device 1 sends data to node device 2, node device 1 transmits the data to bus AB through the MCU transmitting end of node device 1 and the receiving end IN of the corresponding communication IC, and the corresponding communication IC of node device 2 transmits the data to node device 2 through the transmitting end OUT and the corresponding MCU receiving end of node device 2, so that node device 2 receives the data sent by node device 1, thus completing the communication process of data transmission from node device 1 to node device 2. When node device 1 sends data to node device 2, the MCU interrupt end of each node device except node device 1 will detect the interrupt signal.

[0082] The above schematic diagram of the communication system of the multi-split air conditioner can facilitate the understanding of the communication system structure of the multi-split air conditioner disclosed in the embodiment of the present application. The focus of the embodiment of the present application is how the controller of each node device controls the corresponding node device to communicate in the multi-split air conditioner. The communication control method of the multi-split air conditioner provided in the embodiment of the present application will be described in detail later, and will not be further described in detail here. In order to further understand the working logic of the controller corresponding to each node device in the multi-split air conditioner provided in the embodiment of the present application, the architecture of the controller will be further introduced below, so as to fully understand how the various components in the controller work together.

[0083] See also Figure 2 , Figure 2 is a schematic diagram of the architecture of the controller disclosed in the embodiment of the present application, such as Figure 2The controller 200 shown may include, but is not limited to, components such as a processor 201 , a memory 202 , a communication interface 203 , and a timer 204 .

[0084] The processor 201 is used to call the executable program code stored in the memory 202 and execute any communication control method of the multi-split air conditioner corresponding to the executable program code. Optionally, the processor 201 may include one or more processing units; preferably, the processor 201 may include an application processor and a modem processor, etc.

[0085] It should be understood that in the embodiment of the present application, the processor 201 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0086] The memory 202 is used for executable program codes, and the executable code is executed by the processor 201 to implement any communication control method of a multi-split air conditioner disclosed in the embodiment of the present application. The memory 202 may include a program storage area and a data storage area, wherein the program storage area may store executable program codes required for at least one function, etc.; the data storage area may store various types of data generated during the operation of the node device, etc. Optionally, the memory 202 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices.

[0087] The communication interface 203 is used to connect and communicate with the bus, other node devices or servers according to various communication protocol types. Optionally, the controller corresponding to each node device can establish a communication connection with the bus and other node devices through the communication interface 203, so that the controller corresponding to each node device can send data to other node devices through the communication interface 203 to achieve communication.

[0088] The timer 204 is used to detect the operation time of the node device, the time corresponding to each working node of the node device, the operation time of each component of the node device, the time corresponding to each component of the node device at each working node, etc. Optionally, the timer 204 can be used to record the power-on time of each node device, the time when each controller is initialized, and the time from power-on to completion of initialization of each controller.

[0089] It should be noted that the power-on time of each node device is used to indicate the specific time point when each node device is connected to the power supply and starts to operate. By recording the power-on time of each node device, it is possible to understand when each node device starts to work.

[0090] It should be noted that the time when each controller is initialized is the specific time point from the power-on of the node device to the completion of the controller initialization. The initialization process includes self-test, register configuration, communication setting, etc. Recording the time when each controller is initialized can help understand the time when the controller of each node device is ready.

[0091] It should be noted that the duration from power-on to completion of initialization of each controller represents the total duration from the node device powering on to the completion of initialization of the controller. Recording the duration from power-on to completion of initialization of each controller can help understand the time required for the controller of each node device to be ready, so as to evaluate the startup speed of the controller.

[0092] Understandably, Figure 2 The controller architecture shown in the figure does not constitute a specific limitation on the air conditioner. The controller architecture may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0093] Through the introduction of the controller architecture, the functions of each component of each node device controller can be understood. On this basis, the following will further introduce how the controller of each node device in the multi-split air conditioner provided by the embodiment of the present application controls the corresponding node device to communicate in the multi-split air conditioner.

[0094] See also Figure 3 , Figure 3 1 is a flow chart of a communication control method for a multi-split air conditioner disclosed in an embodiment of the present application. Figure 3 The method shown is applied to the controller corresponding to each node device, and may include the following steps:

[0095] Step 301: Detect an interrupt signal through an interrupt terminal within a target duration.

[0096] In the embodiment of the present application, the controller corresponding to each node device includes an interrupt terminal, and the interrupt terminal of each controller is connected to the transmitting terminal of the bus. Before each node device sends target data to other node devices through the bus, it is necessary to determine the target state of the bus, and the target state of the bus includes an idle state or a non-idle state.

[0097] It should be noted that when multiple node devices have data sending needs at the same time, determining the target state of the bus can effectively prevent each node device from directly sending data, causing data conflicts on the bus communication line. Data conflicts mean that multiple node devices send data at the same time or in the same time period.

[0098] It should be noted that the bus being in an idle state means that there is no data transmission on the bus of the multi-split air conditioner, and data can be sent in this state; the bus being in a non-idle state means that there is data transmission on the bus of the multi-split air conditioner, and data cannot be sent in this state.

[0099] In an embodiment of the present application, determining the target state of the bus includes: detecting an interrupt signal through an interrupt end within a target duration to obtain a detection result, the detection result including detecting the interrupt signal within the target duration or not detecting the interrupt signal within the target duration, and the target duration corresponding to each node device is different; determining the target state of the bus according to the detection result; wherein, when the detection result is that the interrupt signal is detected within the target duration, determining the target state of the bus to be a non-idle state; when the detection result is that the interrupt signal is not detected within the target duration, determining the target state of the bus to be an idle state.

[0100] It should be noted that the purpose of the controller corresponding to each node device detecting the interrupt signal according to its corresponding target duration is to avoid the occurrence of data conflicts on the bus when multiple node devices have data sending requirements at the same time after each node device determines the target state of the bus at the same time, and to ensure that each node device can send data according to an orderly communication mechanism.

[0101] In the embodiment of the present application, which node device has a shorter target duration indicates which node device can determine the target state of the bus fastest and send data first. It is understandable that when multiple node devices have data transmission requirements at the same time, the node device with a shorter target duration has the highest probability of successfully grabbing the line, that is, it can send data after successfully grabbing the line first.

[0102] For example, assuming that node device 1 and node device 2 have data sending requirements at the same time, the first target duration of node device 1 and node device 2 are both 100ms, the second target duration of node device 1 is 10ms, and the second target duration of node device 2 is 20ms, then, node device 1 and node device 2 simultaneously detect whether there is an interrupt signal within 100ms through the interrupt end. When no interrupt signal is detected within 100ms, node device 1 and node device 2 simultaneously detect whether there is an interrupt signal through the interrupt end within the corresponding second target duration of 10ms and the second target duration of 20ms respectively. Since the second target duration of node device 1 is less than the second target duration of node device 2, node device 1 will first determine that the bus is in an idle state, and at this time, node device 1 will start sending data first. At the same time, when node device 1 sends data, node device 2 will detect an interrupt signal through its corresponding interrupt end. The interrupt end of node device 2 will not detect the interrupt signal until node device 1 completes data sending and the bus is in an idle state. At this time, the interrupt end corresponding to node device 2 will continue to detect the interrupt signal according to the corresponding first target time of 100ms and the second target time of 20ms. When node device 2 has not detected an interrupt signal within the first target time of 100ms and the second target time of 20ms, it is determined that the bus is in an idle state. At this time, node device 2 can send data.

[0103] It should be understood that since the multi-split air conditioner provided in the embodiment of the present application does not have a master machine and a slave machine, each node device can grab the line when there is a need to send data, and can send data after successfully grabbing the line.

[0104] In an embodiment of the present application, the target duration corresponding to each node device includes a first target duration and a second target duration. The first target duration of each node device is the same, and the second target duration of each node device is different. The second target duration of each node device is generated by a timer of each controller.

[0105] The first target duration indicates the fixed time that each node device needs to wait for the bus to be in an idle state. The second target duration indicates the delay duration that the controller of each node device needs to detect again after failing to detect an interrupt signal through the interrupt terminal within the first target duration. If the interrupt terminal of the controller fails to detect an interrupt signal within the second target duration, it indicates that the bus is in an idle state.

[0106] It should be noted that the first target duration can be set by those skilled in the art according to actual needs, and this application does not limit the specific value of the first target duration.

[0107] In some implementations, the second target duration of each node device is generated by a timer of each controller, including: obtaining errors of different components in the controller through the timer; generating different random numbers according to the errors of different components; and generating the second target duration according to the different random numbers. Optionally, different random numbers can be generated according to the errors of different components through a random number generator.

[0108] It should be noted that due to the errors in the working time and working accuracy of different components in the controller of each node device, each node device timer can generate different second target durations for each node device according to the errors of different components. The different second target durations of each node device can avoid the situation where each node device sends data at the same time after determining that the bus is in an idle state when multiple node devices have data transmission requirements at the same time, thereby causing data conflicts on the bus.

[0109] Step 302: When the interrupt terminal does not detect an interrupt signal within the target duration, target data is sent to other node devices via the bus.

[0110] In the embodiment of the present application, if the interrupt terminal does not detect an interrupt signal within the target duration, it means that the bus is in an idle state within the target duration and data can be sent.

[0111] For example, see Figure 4 , Figure 4 It is a timing diagram of the node device communication disclosed in the embodiment of the present application. When the node device 1 is in the process of sending data from time a to time b, during the period from time a to time b, the interrupt end of the controller of the node device 2 can detect the interrupt signal, determine that the bus is in a non-idle state, and do not send data. After the node device 1 completes the data transmission at time b, the interrupt end of the controller of the node device 2 detects the interrupt signal according to the target duration T2 of the node device 2. Within the target duration T2, that is, during the period from time b to time c, the node device 2 cannot detect the interrupt signal, then it is determined that the bus is in an idle state during the period from time b to time c, and the node device 2 can send data, that is, the node device 2 sends data during the period from time c to time d.

[0112] In some embodiments, the data transmission channel of the bus includes a sending channel and a receiving channel. When the interrupt terminal does not detect an interrupt signal within the target duration, the target data is sent to other node devices through the bus, including: when the interrupt terminal does not detect an interrupt signal within the target duration, the target data is sent to other node devices through the sending channel of the bus.

[0113] In some implementations, sending target data to other node devices via a bus includes: sending the target data to other node devices via the bus according to a preset sending duration, where the preset sending duration is used to send a type of target data.

[0114] It should be noted that the preset sending duration can be set by technical personnel in this field according to actual needs, and this application does not limit the specific value of the preset sending duration.

[0115] In some embodiments, if the interrupt end does not detect an interrupt signal within the target time length, after sending the target data to other node devices through the bus, the step of detecting the interrupt signal through the interrupt end within the target time length is re-executed, and if the interrupt end does not detect an interrupt signal within the target time length, sending the target data to other node devices through the bus.

[0116] It should be noted that re-executing the step of detecting the interrupt signal through the interrupt end within the target time means that when the node device completes data transmission once and wants to send data again, it is necessary to detect the interrupt signal through the interrupt end again. Only after it is determined that the bus is in an idle state again can it be determined that the line has been successfully grabbed again and data can be sent again.

[0117] For example, see Figure 4 After node device 2 completes data transmission between time c and time d, if node device 2 still has data transmission requirements, it starts detecting interrupt signals at time d according to the target duration T2 of node device 2 through the interrupt end of the controller. If node device 2 cannot detect interrupt signals within the target duration T2, that is, between time d and time e, it is determined that the bus is in an idle state between time d and time e, and node device 2 can send data again, that is, node device 2 sends data again between time e and time f.

[0118] It can be seen that by implementing the embodiment of the present application, each node device in the multi-split air conditioner can determine whether the bus is idle by detecting the interrupt signal through the interrupt terminal of the controller, that is, each node device can grab the line when detecting that the bus is in an idle state, and send data after successfully grabbing the line. This communication method improves the communication efficiency of the multi-split air conditioner, has high reliability, flexible communication mechanism, and is suitable for multi-split air conditioners with a large number of nodes on the bus. In addition, since the second target duration corresponding to each node device is different, it can effectively avoid multiple node devices from successfully grabbing the line at the same time, and effectively avoid data conflicts.

[0119] Through the above-mentioned steps and processes, the execution steps of a communication control method for a multi-split air conditioner provided in an embodiment of the present application can be understood. The following will further introduce the step-by-step process of the communication control method for a multi-split air conditioner provided in an embodiment of the present application in detail.

[0120] See also Figure 5 , Figure 5 FIG. 1 is a flow chart of another communication control method for a multi-split air conditioner disclosed in an embodiment of the present application. Figure 5 The method shown is applied to the controller corresponding to each node device, and may include the following steps:

[0121] Step 501, when it is determined to send target data to other node devices, start the timing function of the timer, and the timing duration of the timer is the target duration.

[0122] In the embodiment of the present application, each node device needs to determine the target data to be sent to other node devices before detecting an interrupt signal through an interrupt terminal within a target duration.

[0123] As an optional implementation, determining to send target data to other node devices includes: determining the target data to be sent to other node devices from data of multiple data types according to a preset sending priority, wherein the data of the multiple data types include at least one of change type data, periodic collection type data, and broadcast type data, and the priorities of the change type data, the periodic collection type data, and the broadcast type data decrease in sequence.

[0124] It should be noted that in order to improve the communication efficiency of the multi-split air conditioner, the node device only sends one type of target data each time the line is successfully grabbed. Therefore, it is necessary to classify the data of each node device into multiple data types according to the preset sending priority. When determining to send target data to other node devices, the target data to be sent to other node devices can be determined from the data of multiple data types.

[0125] Among them, the change type data has the highest priority, that is, the change type data is sent at any time after each successful line grabbing. The change type data includes the command data set by the user, system protection parameters, etc. The command data set by the user refers to the device temperature, wind speed, heating, cooling, air supply and other command data set by the user. The system protection parameters refer to the overcurrent protection, overvoltage protection, overload protection and other data of each node device.

[0126] Among them, the sending priority of periodic collection type data is the second, that is, after each successful line grabbing, if the node device has no data of change type, the periodic collection type data is sent. Periodic collection type data includes the temperature of the environment where the node device is located, operating parameters (compressor operating frequency, fan speed, etc.), pipeline gas pipe temperature of the node device, liquid pipe temperature of the node device and other data.

[0127] Among them, broadcast type data has the lowest priority, that is, after each successful line grabbing, if the node device has no change type data and periodic collection type data, it will send broadcast type data. Broadcast type data refers to the data that a node device needs to send to all other node devices.

[0128] In this implementation, the type of data sent each time is determined by a preset sending priority, which can ensure that more important data is sent first, and can also avoid sending a large amount of data at the same time, causing delays in multi-split air conditioner data transmission and reducing data transmission stability.

[0129] In the embodiment of the present application, the timer of each node device is provided with a timing function. When it is determined to send target data to other node devices, the timing function of the timer is started, and the timing duration of the timer is the target duration.

[0130] It should be noted that when each node device determines to send target data to other node devices, it is necessary to start the timing function of the corresponding timer. The timing function of the timer corresponding to each node device starts timing according to the set target duration. The data can only be sent immediately after the timing function of the timer continuously decreases from the target duration to 0 during the timing process.

[0131] Exemplarily, if node device 1 determines to send target data to other node devices, the timing function of the timer of node device 1 is started, and the target duration is set to 110ms in the timing function of the timer of node device 1, and the target duration includes a first target duration of 100ms and a second target duration of 10ms. When the timing function of the timer of node device 1 is started, the target duration of the timer is reduced by 1 in units of ms for every 1ms.

[0132] In an embodiment of the present application, the second target duration of each node device is generated by the timing error of the timer of each controller, the error of the power-on time of each node device, and the error of the initialization completion time of each controller.

[0133] It should be noted that due to the timing accuracy of the timer of each controller, the power-on time of each node device and the time when each controller is initialized are different. Therefore, the timing error of the timer of each controller, the error of the power-on time of each node device, and the error of the time when each controller is initialized can be obtained through the timer, and the second target duration of each node device is generated according to the timing error of the timer of each controller, the error of the power-on time of each node device, and the error of the time when each controller is initialized.

[0134] In this embodiment, different timing durations are generated for each node device according to the errors of different hardware components. This method allows each node device to generate a different timing duration, which can effectively prevent multiple node devices from successfully grabbing the line at the same time, that is, it can effectively avoid data conflicts on the bus.

[0135] As an optional implementation, the controller obtains a first random number, a second random number and a third random number through a timer, the first random number is generated based on the timing error of the timer, the second random number is generated based on the error of the power-on time of the corresponding node device, and the third random number is generated based on the error of the corresponding controller initialization completion time; the controller calculates the first random number, the second random number and the third random number according to a preset formula through the timer to generate a second target duration for each node device.

[0136] Optionally, the preset formula includes summing the first random number, the second random number, and the third random number.

[0137] Optionally, the preset formula includes second target duration = (first random number + second random number + third random number) mod maximum random time. The preset formula indicates that a random time value within the maximum random time range is obtained by adding the first random number, the second random number and the third random number and taking the modulus.

[0138] The maximum random time is a value set by those skilled in the art as required, so that the second target duration of each node device is within a preset time range. For example, the maximum random time can be any value within the range of 0 to 70 ms, and according to the maximum random time, the second target duration of each node device generated by the timer is within the range of 0 to 70 ms.

[0139] Optionally, a random number generator may generate a first random number based on a timing error of a timer, generate a second random number based on an error at a power-on time of a corresponding node device, and generate a third random number based on an error at a time when initialization of a corresponding controller is completed.

[0140] Step 502: During the timing of the timer, an interrupt signal is detected through the interrupt terminal.

[0141] Step 503: When the timer expires and no interrupt signal is detected, the target data is sent to other node devices via the bus.

[0142] In an embodiment of the present application, when a node device determines to send target data to other node devices and starts the timing function of the timer, the timer starts timing according to the corresponding target duration, and during the timing of the timer, continues to detect interrupt signals through the interrupt end. If no interrupt signal is detected at the end of the timing, it indicates that the bus is in an idle state and data can be sent.

[0143] Exemplarily, the target duration of node device 1 is 110ms, which includes a first target duration of 100ms and a second target duration of 10ms. After the timing function of the timer of node device 1 is started, when the target duration is continuously reduced from 110ms to 0 and no interrupt signal is detected, it means that no data is transmitted on the bus within the target duration, the bus is in an idle state, and node device 1 can send data immediately.

[0144] As an optional implementation, when the timer expires and no interrupt signal is detected, after sending the target data to other node devices through the bus, response data sent by other node devices can also be received. The response data is sent by other node devices when the target data is received and the preset waiting time expires, and the preset waiting time is less than the target time. The response data is used to indicate that the other node devices correctly receive the target data or incorrectly receive the target data.

[0145] Optionally, when a node device sends target data to other node devices through the bus, the target data will carry the address of the sending device and the address of the receiving device. When the receiving device receives the target data sent by the sending device, the receiving device can send response data back to the sending device according to the address of the receiving device.

[0146] Optionally, the receiving device may send back response data to the sending device according to the address of the receiving device, including: the receiving device may send back response data to the sending device according to the address of the receiving device after the preset waiting time ends. The response data includes an acknowledgment character (ACK) or a negative acknowledgement character (NACK), ACK is used to indicate that the receiving device correctly receives the target data, and NACK is used to indicate that the receiving device incorrectly receives the target data.

[0147] It should be noted that the receiving device does not need to detect an interrupt signal through the interrupt terminal when sending response data back to the sending device according to the address of the receiving device, but only needs to send back the response data immediately after the preset waiting time ends.

[0148] It should be noted that the preset waiting time can be set by those skilled in the art according to actual needs, and the present application does not limit the specific value of the preset waiting time. For example, the preset waiting time can be set to 5ms.

[0149] In this implementation, after receiving data sent by a node device, the receiver does not need to detect whether the bus is in an idle state, and can directly send response data within a shorter preset waiting time, which helps the sender to quickly confirm whether the data is successfully received, thereby improving the communication efficiency when the sender determines the reliability of data transmission.

[0150] For other implementations of steps 502 to 503 , reference may be made to the contents of steps 301 to 302 , which will not be described in detail here.

[0151] Step 504: During the timing process of the timer, when an interrupt signal is detected through the interrupt terminal, the timer is reset, and the timing duration of the reset timer is the target duration.

[0152] In an embodiment of the present application, while the timer is timing according to the corresponding target duration, the interrupt signal is continuously detected through the interrupt end. When the interrupt end detects the interrupt signal, it indicates that there are other node devices on the bus transmitting data at this time, and the bus is in a non-idle state and data cannot be sent. At the same time, the timer is reset so that the timer re-times according to the target duration.

[0153] For example, see Figure 6 , Figure 6 It is a timing diagram of multiple node devices simultaneously grabbing lines for communication disclosed in an embodiment of the present application. Figure 6 The device includes node 1, node 2 and node 3. When node 1 completes data transmission at time b, the interrupt terminals of node 2 and node 3 cannot detect interrupt signals at the same time. Then, from time b, the timers of node 2 and node 3 start timing according to their corresponding target durations, in units of ms. The target duration of the timer decreases by 1 every 1ms. Among them, the target duration of node 2 is T2, and the target duration of node 3 is T3. Figure 6As shown, the target duration T2 of node device 2 is less than the target duration T3 of node device 3. At time c, the target duration T2 of the timer of node device 2 is first reduced to 0, and node device 2 is the first to successfully grab the line and can send data immediately. At time c, since node device 2 starts to send data, at time c, the interrupt end of node device 3 will detect an interrupt signal, indicating a failure to grab the line, and the timer of node device 3 will be reset. Since node device 2 has been sending data from time c to time d, the timer of node device 3 will be continuously reset until time d when node device 2 completes data sending. After the interrupt end of node device 3 cannot detect the interrupt signal, the timer of node device 3 will start timing according to the target duration T3. Figure 6 As shown, from time d to time e, the target duration T3 of the timer of node device 3 is continuously reduced to 0, indicating that the interrupt end of node device 3 did not detect an interrupt signal from time d to time e, indicating that the bus is in an idle state, and node device 3 successfully grabs the line at time e and can send data immediately. From time e to time f is the time for node device 3 to send data.

[0154] It can be seen that by implementing the embodiment of the present application, each node device in the multi-split air conditioner can determine whether the bus is idle by detecting the interrupt signal at the interrupt end of the controller, that is, each node device can grab the line when detecting that the bus is in an idle state, and send data when the line is successfully grabbed. This communication method improves the communication efficiency of the multi-split air conditioner, has high reliability, flexible communication mechanism, and is suitable for multi-split air conditioners with a large number of nodes on the bus. In addition, since the second target duration corresponding to each node device is different, it can effectively avoid multiple node devices from successfully grabbing the line at the same time, and effectively avoid data conflicts. In addition, when each node device in the multi-split air conditioner has a data transmission demand, the counting function of the timer can be started while detecting the interrupt signal at the interrupt end, and the timing is based on the corresponding timing duration. When the interrupt end still does not detect the interrupt signal until the timing ends, it means that the bus is idle, that is, the line is successfully grabbed, and data can be sent directly. This method of detecting whether there is an interrupt signal within the corresponding timing duration simplifies the communication line grabbing mechanism, which helps to improve communication efficiency. In addition, during the timing process of the timer for each node device in the multi-split air conditioner, as long as an interrupt signal is detected indicating that the bus is in a non-idle state, the timing will be restarted according to the corresponding timing duration. This method of resetting the timer when an interrupt signal is detected can dynamically adjust the line grabbing strategy according to the bus status, and can quickly restart the timing and grab the line for the node device, which helps to improve the timeliness and efficiency of data transmission, and further improve the reliability of the communication method.

[0155] Based on the above steps, the steps of the communication control method of the multi-split air conditioner provided by the embodiment of the present application have been understood in detail. However, if a node device mistakenly detects that there is no data transmission on the bus, and sends data to other node devices while other node devices are sending data, data conflicts will occur on the bus. Figure 7 , Figure 7 FIG. 1 is a flow chart of another communication control method for a multi-split air conditioner disclosed in an embodiment of the present application. Figure 7 The method shown is applied to the controller corresponding to each node device, and may include the following steps:

[0156] Step 701: Detect an interrupt signal through an interrupt terminal within a target duration.

[0157] Step 702: When the interrupt terminal does not detect an interrupt signal within the target duration, target data is sent to other node devices via the bus.

[0158] The implementation of steps 701 to 702 may refer to the contents of steps 301 to 302 and steps 501 to 504 described above, and will not be described in detail here.

[0159] Step 703: When a data conflict is detected in the process of sending target data to other node devices via the bus, the sending of target data to other node devices is stopped.

[0160] In an embodiment of the present application, in the process of sending target data to other node devices via the bus, it is possible to detect whether there is a data conflict on the bus, so as to determine whether to continue sending the target data to other node devices based on the conflict detection result.

[0161] Optionally, when a data conflict is detected on the bus during the process of sending target data to other node devices via the bus, sending the target data to other node devices is stopped immediately.

[0162] Optionally, in the process of sending target data to other node devices via the bus, when no data conflict is detected on the bus, the target data continues to be sent to other node devices.

[0163] It should be noted that the data conflict on the bus means that at least two node devices are sending data at the same time. In this case, the data sent by each node device will be erroneous, resulting in a data conflict on the bus.

[0164] For example, see Figure 8 , Figure 8 It is a timing diagram of multiple node devices in an embodiment of the present application that simultaneously seize the line for communication after a data conflict occurs. Figure 8In the period between time b and time c, both node device 1 and node device 2 are sending data, so the period between time b and time c is the time when data conflict occurs on the bus. When node device 1 and / or node device 2 detects data conflict on the bus at time c, node device 1 and node device 2 stop sending target data at the same time.

[0165] As an optional implementation, the bus includes a sending channel and a receiving channel. In the process of sending target data to other node devices through the bus, it is detected that there is a data conflict on the bus, including:

[0166] In the process of sending target data to other node devices through the sending channel, the target data is received through the receiving channel to obtain received data;

[0167] Determine whether the bus hits at least one of the preset conflict detection rules according to the target data and the received data;

[0168] When the bus hits the preset conflict detection rule, it is detected that there is a data conflict on the bus;

[0169] The preset conflict detection rules include at least one of a parity error in received data, a data frame error in received data, a duration of receiving target data exceeding a preset duration, and inconsistency between target data and received data.

[0170] It should be noted that parity error refers to checking the integrity of received data by adding an extra odd or even bit in the target data transmission. The number of "1" in the data determines the setting of the odd or even bit. Data frame error refers to checking whether the start bit, length, etc. of each frame of received data and target data are the same.

[0171] It should be noted that those skilled in the art can set a variety of preset conflict detection rules according to actual needs, and this application does not limit this.

[0172] In this implementation, each node device receives its own data while sending data through the sending channel and receiving channel of the bus, and determines whether there is a data conflict on the bus based on the sent data and the received data combined with preset conflict detection rules. This approach helps to improve the efficiency and accuracy of data conflict detection.

[0173] Step 704, changing the first target duration to a third target duration to obtain a changed target duration, wherein the changed target duration includes the third target duration and the second target duration, wherein the third target duration is smaller than the first target duration.

[0174] In the embodiment of the present application, since the node device stops sending target data to other node devices due to data conflict on the bus, in order to allow the node device to successfully grab the line again and send the target data as soon as possible, the first target time length of the node device can be reduced to increase the success rate of grabbing the line for the node device to send the target data again, thereby improving the communication efficiency of the node device.

[0175] It should be noted that the method of reducing the first target duration of the node device is for the node devices that detect data conflicts, that is, which node devices passively stop sending target data to other node devices due to detecting data conflicts when sending target data, and the first target duration of these node devices will be reduced.

[0176] Exemplarily, if the node devices that detect data conflicts include node device 1 and node device 2, the first target duration of node device 1 and node device 2 is 100ms, the second target duration of node device 1 is 60ms, and the second target duration of node device 2 is 20ms. Then the first target duration of node device 1 and node device 2 can be changed from 100ms to 10ms, and the changed target duration of node device 1 is the sum of the first target duration 10ms and the second target duration 60ms, so the changed target duration of node device 1 is 70ms, and the changed target duration of node device 2 is the sum of the first target duration 10ms and the second target duration 20ms, so the changed target duration of node device 1 is 30ms.

[0177] It can be understood that if the second target duration of each node device generated by the timer is pre-set to be within the range of 0 to 70ms, then after the timing function of the timer of each node device is started, the timing interval of the second target duration of each node device is 100ms to 170ms. Then, after the first target duration is changed from 100ms to 10ms, the timing interval of the second target duration is 10ms to 80ms.

[0178] Step 705: Detect an interrupt signal through the interrupt terminal within the modified target duration.

[0179] The specific implementation of step 705 may refer to the contents of the aforementioned steps 301 and 502, which will not be repeated here.

[0180] Step 706: When the interrupt terminal does not detect an interrupt signal within the changed target duration, the target data is sent to other node devices via the bus.

[0181] In an embodiment of the present application, after obtaining the changed target duration, the interrupt signal continues to be detected through the interrupt end according to the changed target duration until the interrupt signal is continuously not detected by the interrupt end within the changed target duration, and the target data is sent to other node devices through the bus again.

[0182] For example, see Figure 8 , Figure 8 It is a timing diagram of multiple node devices in an embodiment of the present application that simultaneously seize the line for communication after a data conflict occurs. Figure 8 At time c, node device 1 and node device 2 simultaneously stop sending target data, and simultaneously change the first target duration of node device 1 and node device 2 to the third target duration, so that the changed target duration of node device 1 is T1', and the changed target duration of node device 2 is T2'.

[0183] like Figure 8 As shown, since both node device 1 and node device 2 have stopped sending data at time c, the bus is in an idle state at time c. Node device 1 and node device 2 start the timer at the same time from time c. The timer of node device 1 starts timing according to the changed target duration T1', and the timer of node device 2 starts timing according to the changed target duration T2'. Since the second target duration of node device 2 is less than the second target duration of node device 1, the changed target duration T2' of node device 2 is less than the changed target duration T1' of node device 1. Therefore, at time d, the changed target duration T2' of the timer of node device 2 is first reduced to 0, indicating that the bus is in an idle state from time c to time d. At time d, node device 2 is the first to successfully grab the line, and node device 1 fails to grab the line. Node device 2 can immediately send data again at time d.

[0184] like Figure 8 As shown, after node device 1 fails to grab the line at time d, the timer of node device 1 is reset. Since node device 2 has been sending data from time d to time e, the interrupt end of node device 1 will continue to detect the interrupt signal from time d to time e, and the timer of node device 1 will be reset continuously until node device 2 completes data transmission at time e. After the interrupt end of node device 1 cannot detect the interrupt signal, the timer of node device 1 will start timing according to the changed target duration T1' and continue to detect the interrupt signal through the interrupt end. Figure 8 As shown, from time e to time f, the changed target duration T1' of the timer of node device 1 is continuously reduced to 0, indicating that from time e to time f, the interrupt end of node device 1 did not detect an interrupt signal, the bus was in an idle state, and node device 1 successfully grabbed the line at time f and can send data immediately. From time f to time g is the time for node device 1 to send data again.

[0185] As an optional implementation, when the interrupt terminal does not detect an interrupt signal within the changed target duration, after sending target data to other node devices via the bus, the third target duration is changed to the first target duration.

[0186] It should be noted that when the node device that has changed the first target duration successfully grabs the line and completes data transmission, in order to ensure the communication efficiency of other node devices that have not changed the target duration, the third target duration of the node device that has changed the first target duration needs to be restored to the first target duration.

[0187] like Figure 8 As shown, when node device 1 completes data transmission between time f and time g, the changed target duration T1' of node device 1 is changed to target duration T1, and, when node device 2 completes data transmission between time d and time e, the changed target duration T2' of node device 2 is changed to target duration T2 (not shown in the figure). When node device 1 completes data transmission between time f and time g and needs to send data again, the timer of node device 1 starts from time g, and continuously detects interrupt signals through the interrupt end within the target duration T1 until time h, when the target duration T1 of the timer of node device 1 is continuously reduced to 0, indicating that the interrupt end of node device 1 did not detect an interrupt signal between time g and time h, indicating that the bus is in an idle state, and node device 1 successfully grabs the line at time h and can send data immediately, and time h to time i is the time for node device 1 to send data again.

[0188] In this implementation, after the node device corresponding to the first target duration is changed and the communication line is successfully grabbed, the third target duration is restored to the first target duration so that the node device grabs the line at the original time the next time, that is, after the node device successfully sends data, it no longer affects the communication efficiency of other node devices.

[0189] For other implementations of step 706, reference may be made to the contents of the aforementioned steps 302 and 503, which will not be described in detail here.

[0190] It can be seen that by implementing the embodiment of the present application, each node device in the multi-split air conditioner can determine whether the bus is idle by detecting the interrupt signal at the interrupt end of the controller, that is, each node device can grab the line when it detects that the bus is in an idle state, and send data when the line grabbing is successful. This communication method improves the communication efficiency of the multi-split air conditioner, has high reliability, flexible communication mechanism, and is suitable for multi-split air conditioners with a large number of nodes on the bus. And, since the second target duration corresponding to each node device is different, it can effectively avoid multiple node devices from successfully grabbing the line at the same time, and effectively avoid data conflicts. And, when a data conflict is detected on the bus, by stopping sending data, the adverse effects of the data conflict on the multi-split air conditioner can be reduced in time. And, when a data conflict is detected on the bus and the data is stopped, by reducing the first target duration, it is helpful to improve the success rate of the node device that detects the data conflict when grabbing the line next time, so as to reduce the possibility of future conflicts, thereby improving the communication efficiency of the node device.

[0191] It should be understood that, although the steps in the above-mentioned flowcharts are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the above-mentioned flowcharts may include a plurality of sub-steps or a plurality of stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these sub-steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the sub-steps or stages of other steps. In addition, the above-mentioned multiple embodiments can be implemented independently, and can also be combined with each other, which is not limited here.

[0192] It should be understood that "one embodiment" or "an embodiment" or "some embodiments" mentioned throughout the specification means that specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, "in one embodiment" or "in one embodiment" or "in some embodiments" appearing throughout the specification may not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It should be understood that in various embodiments of the present application, the size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application. The above-mentioned sequence numbers of the embodiments of the present application are only for description and do not represent the advantages and disadvantages of the embodiments. The above description of each embodiment tends to emphasize the differences between the various embodiments, and the same or similar aspects can be referenced to each other. For the sake of brevity, this article will not repeat them.

[0193] The term "and / or" in this article is only a description of the association relationship of associated objects, indicating that there may be three relationships. For example, object A and / or object B can represent three situations: object A exists alone, object A and object B exist at the same time, and object B exists alone.

[0194] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0195] In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in a processor or an instruction in the form of software. The steps of the method disclosed in conjunction with the embodiment of the present application can be directly embodied as a hardware processor for execution, or a combination of hardware and software modules in a processor for execution. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor executes the instructions in the memory, and completes the steps of the above method in conjunction with its hardware. To avoid repetition, it is not described in detail here.

[0196] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0197] In the several embodiments provided in the present application, it should be understood that the disclosed products and methods can be implemented in other ways. The embodiments described above are merely illustrative. For example, the division of the modules is only a logical function division. There may be other division methods in actual implementation, such as: multiple modules or components can be combined, or can be integrated into another system, or some features can be ignored, or not executed. In addition, the coupling, direct coupling, or communication connection between the components shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.

[0198] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0199] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0200] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the relevant technology. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0201] The above is only an implementation method of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A multi-split air conditioner, characterized in that: include: A bus, and a plurality of node devices respectively connected to the bus, wherein the plurality of node devices include a plurality of indoor units and / or a plurality of outdoor units; Each node device includes a corresponding controller, an interrupt terminal of each controller and a receiving terminal of each controller are connected to a transmitting terminal of the bus, and a transmitting terminal of each controller is connected to a receiving terminal of the bus; Each of the controllers includes a timer; The controller is configured to: When the interruption end does not detect an interruption signal within a target time period, sending target data to other node devices via the bus; Among them, the target duration includes a first target duration and a second target duration, the first target duration of each node device is the same, the second target duration of each node device is different, and the second target duration of each node device is generated by the timer of each controller.

2. The multi-split air conditioner according to claim 1, characterized in that: The timer is provided with a timing function, and the controller sends target data to other power-saving devices through the bus when the interrupt end does not detect an interrupt signal within the target time, and is configured as follows: When it is determined to send the target data to the other node device, start the timing function of the timer, and the timing duration of the timer is the target duration; During the timing process of the timer, detecting the interrupt signal through the interrupt terminal; When the timer ends and the interrupt signal is not detected, the target data is sent to the other node devices through the bus.

3. The multi-split air conditioner according to claim 2, characterized in that: The controller is also configured to: During the timing process of the timer, when the interrupt signal is detected through the interrupt end, the timer is reset, and the timing duration of the reset timer is the target duration.

4. The multi-split air conditioner according to claim 1, characterized in that: The second target duration of each node device is generated by a timing error of a timer of each controller, an error of a power-on time of each node device, and an error of an initialization completion time of each controller.

5. The multi-split air conditioner according to any one of claims 1 to 4, characterized in that: The controller is also configured to: In the process of sending the target data to the other node devices through the bus, when a data conflict is detected on the bus, the sending of the target data to the other node devices is stopped.

6. The multi-split air conditioner according to claim 5, characterized in that: After stopping sending the target data to the other node devices, the controller is further configured to: Changing the first target duration to a third target duration to obtain a changed target duration, wherein the changed target duration includes the third target duration and the second target duration, wherein the third target duration is shorter than the first target duration; The controller sends target data to other node devices through the bus when the interrupt end does not detect an interrupt signal within the target duration, and is configured to: When the interrupt end does not detect the interrupt signal within the changed target duration, the target data is sent to other node devices via the bus.

7. The multi-split air conditioner according to claim 6, characterized in that: In the case that the interrupt end does not detect the interrupt signal within the changed target duration, after sending the target data to other node devices via the bus, the controller is further configured to: The third target duration is changed to the first target duration.

8. The multi-split air conditioner according to claim 5, characterized in that: The bus includes a sending channel and a receiving channel. When the controller sends the target data to the other node devices through the bus, if it detects that there is a data conflict on the bus, the controller is configured to: In the process of sending the target data to the other node devices through the sending channel, receiving the target data through the receiving channel to obtain received data; Determining whether the bus hits at least one of the preset conflict detection rules according to the target data and the received data; When the bus hits the preset conflict detection rule, detecting that there is a data conflict on the bus; The preset conflict detection rule includes at least one of a parity error of the received data, a data frame error of the received data, a duration of receiving the target data exceeding a preset duration, and inconsistency between the target data and the received data.

9. The multi-split air conditioner according to claim 2, characterized in that: The controller determines to send the target data to the other node devices, and is configured to: The target data to be sent to the other node devices is determined from data of multiple data types according to a preset sending priority, wherein the data of the multiple data types include at least one of change type data, periodic collection type data, and broadcast type data, and the priorities of the change type data, the periodic collection type data, and the broadcast type data decrease in sequence.

10. The multi-split air conditioner according to claim 1, characterized in that: The controller is also configured to: Receiving response data sent by the other node device, the response data is sent by the other node device after receiving the target data and when a preset waiting time ends, and the preset waiting time is less than the target time; The response data is used to indicate whether the other node device correctly receives the target data or incorrectly receives the target data.

Images