KNX bus multi-device same screen time-sharing temperature control voice control method and device

Abstract

The present application relates to the field of KNX bus heating ventilation control technology, in particular to a KNX bus multi-device same screen time control voice control method and device. In view of the problems of control message centralized sending, parameter execution sequence conflict and device state feedback lag when same screen multi-device control, timing temperature control task and voice control event are concurrent, the KNX project, page and heating ventilation device parameter configuration are read, the mapping relationship and parameter dependence sequence of page slot, timing temperature control task and voice control event to KNX control action are established; the control event is converted into control message piece and added to the to-be-scheduled queue, the page sending window is established and the micro time slot is sent according to the KNX bus load distribution; the group address value write message is sent after the conflict disposal of the control message piece is executed, the control message piece is confirmed based on the state feedback condition, and the feedback disposal is executed on the subsequent control message piece, so as to improve the message sending order and state consistency of the heating ventilation device.

Description

Technical Field

[0001] This invention relates to the field of KNX bus HVAC control technology, specifically to a KNX bus multi-device simultaneous time-sharing temperature control voice control method and device. Background Technology

[0002] KNX bus-based intelligent central control systems are typically used in residential buildings, hotel rooms, and office buildings to control the on / off operation, operating modes, set temperatures, and fan speeds of HVAC equipment such as air conditioners, fresh air systems, fan coil units, and thermostats. Existing central control screens generally trigger control messages from corresponding group addresses via page slots, timed tasks trigger control commands at preset times, and voice control functions generate corresponding instructions after recognizing control commands. Device status is typically updated to the central control screen via bus feedback messages.

[0003] When multiple HVAC devices on the same page are operated continuously within a short period, multiple timed tasks arrive simultaneously, or voice commands are inserted into existing control processes, existing methods often send control messages continuously according to the order of event arrival or a fixed priority, failing to coordinate subsequent control based on the current bus occupancy and the actual feedback status of the devices. For control parameters of the same HVAC device, such as on / off states, operating modes, and set temperatures, which have a sequential relationship, subsequent parameters may take effect before preceding parameters, voice settings may overwrite existing settings, and control commands may continue to be issued even when status feedback is delayed, resulting in inconsistencies between the actual device status and the status displayed on the central control screen. Therefore, a KNX bus multi-device simultaneous time-sharing temperature control voice control method and device is needed to solve the above problems. Summary of the Invention

[0004] To address the above problems, this invention provides the following technical solution: a KNX bus multi-device simultaneous time-sharing temperature control voice control method, comprising: S1. Read the KNX project, central control screen page and HVAC equipment parameter configuration, establish a mapping relationship between page slots, timed temperature control tasks and voice control events and KNX control actions, and determine the parameter dependency order of each control function of the same HVAC equipment. S2. Convert the timed temperature control task, screen-on touch event, and voice control event verified by voice recognition into control message slices for KNX bus scheduling and add them to the scheduling queue. The control message slices are associated with HVAC equipment, control functions, target values, control sources, and status feedback conditions. S3. Establish a page sending window based on the associated page of the control message slice, and allocate transmission micro-slots to the control message slices in the page sending window according to the KNX bus load; S4. Based on the parameter dependency order and the control source, perform conflict handling on the control message slices, select the control message slices that can be sent, convert the control message slices that can be sent into KNX group address values ​​for controlling the corresponding HVAC equipment within the transmission micro-slot, write them into the message and send them, and establish a pending feedback state. S5. Receive and parse the KNX status feedback message, confirm the control message slice based on the status feedback conditions of the control message slice, and perform feedback processing on subsequent control message slices.

[0005] Furthermore, establishing the mapping relationship between page slots, timed temperature control tasks, and voice control events and KNX control actions includes: Based on the KNX project, central control screen page and HVAC equipment parameter configuration, determine the HVAC equipment and control functions corresponding to the page slots, timed temperature control tasks and voice control events; The parameter dependency order is determined based on the execution prerequisite relationships between the various control functions of the same HVAC equipment; For each page slot, timed temperature control task, and voice control event, a mapping item is generated. The mapping item is associated with the corresponding HVAC equipment, control function, KNX control action, status feedback condition, and parameter dependency order. The mapping items are aggregated to form the mapping relationship.

[0006] Furthermore, the step of converting the timed temperature control task, screen-sharing touch event, and voice control event verified by voice recognition into control message fragments for KNX bus scheduling and adding them to the scheduling queue includes: Based on the mapping relationship, determine the HVAC equipment, control function, and target value corresponding to the timed temperature control task and the screen-on touch event, and verify whether the voice control event can uniquely identify the HVAC equipment, control function, and target value. The timed temperature control task, the screen-sharing touch event, and the verified voice control event are converted into corresponding control message fragments. For multiple control message fragments with the same control function and the same target value for the same HVAC equipment, merge processing is performed and the target control message fragment used for the KNX bus scheduling is retained; The control message fragments that have undergone the merging process are added to the scheduling queue.

[0007] Furthermore, the step of establishing a page transmission window based on the associated page of the control message slice, and allocating transmission micro-slots to the control message slices within the page transmission window according to the KNX bus load, includes: Group control message fragments associated with the same page into the same page's sending window; The KNX bus load is determined based on the number of KNX bus messages, the number of control message fragments that have been sent and are in the pending feedback state, and the proportion of communication error messages. The duration of the transmission micro-slot is determined based on the KNX bus load, and the control message slices within the page transmission window are selected in a time-division manner according to the transmission micro-slot; The control message slices selected by the time division are allocated to the corresponding transmission micro-slots.

[0008] Furthermore, the conflict resolution of the control message fragments based on the parameter dependency order and the control source includes: The control message fragments are grouped according to the HVAC equipment, and then sorted within each equipment group according to parameter dependency order, control source priority, and generation time to obtain the equipment parameter execution chain; For control message segments with different target values ​​for the same control function of the same HVAC equipment, source conflict handling is performed according to the priority and transmission status of the control source. The source conflict handling is used to determine the target control message segment and the execution status. For control message slices of different control functions of the same HVAC equipment, after the control message slice with smaller parameter dependency order meets the status feedback condition, the control message slice with larger parameter dependency order is determined as the sendable object. The device parameter execution chain is updated based on the source conflict resolution and the sendable object.

[0009] Furthermore, the source conflict resolution includes: When the control message slice corresponding to the voice control event has a different target value from the unsent control message slice of the same control function of the same HVAC equipment, the control message slice corresponding to the voice control event is used as the target control message slice to replace the unsent control message slice, and the equipment parameter execution chain is redefined. When the control message corresponding to the voice control event has a different target value from the control message of the same control function of the same HVAC equipment that has been sent and is in the state of waiting for feedback, the control message corresponding to the voice control event is set to the waiting state. After the control message fragment that has been sent and is in the state awaiting feedback meets the state feedback condition, the device parameter execution chain is re-determined based on the feedback state.

[0010] Furthermore, establishing the pending feedback state includes: For each sent control message segment, a feedback expectation record is generated, which is associated with HVAC equipment, control function, status feedback conditions, control message segment version identifier, and sending time. The control message slice version identifier is used to characterize the order of control message slices for the same control function of the same HVAC equipment. The version identifier of the latest control message slice sent and not yet processed in the same control function of the same HVAC equipment is determined as the current feedback version identifier. Control message slices in the pending scheduling state or waiting state do not update the current feedback version identifier. Associate the sent control message fragments with the corresponding feedback expectation records and mark them as pending feedback status.

[0011] Furthermore, the step of receiving and parsing the KNX status feedback message, and confirming the control message slice based on the status feedback conditions of the control message slice, includes: For control message segments in the pending feedback state, when the version identifier of the control message segment to be recorded is the current feedback version identifier of the same control function of the same HVAC equipment, the KNX status feedback message whose reception time is later than the transmission time and meets the status feedback conditions will be matched to the corresponding control message segment. Update the control message fragment that matches the KNX status feedback message to the confirmed status, and release the subsequent control message fragments in the same HVAC equipment whose parameter dependency order is greater than the control message fragment and which have no other unconfirmed preceding control message fragments as sendable objects.

[0012] Furthermore, the feedback processing for subsequent control message fragments includes: When the control message fragment version identifier of the feedback expectation record is the current feedback version identifier, no KNX status feedback message is matched after the feedback waiting period, and no KNX group address value read message has been generated for the feedback expectation record, a KNX group address value read message for reading the status of the corresponding HVAC equipment is generated. When the control message segment version identifier of the feedback expectation record is the current feedback version identifier and the return result of the KNX group address value read message meets the status feedback condition of the feedback expectation record, the corresponding control message segment is updated to the confirmed status, and the subsequent control message segments in the same HVAC equipment whose parameter dependency order is greater than the control message segment and which do not have other unconfirmed preceding control message segments are released as sendable objects. When the control message segment version identifier of the feedback expectation record is the current feedback version identifier and the KNX group address value read message does not obtain a return result that satisfies the status feedback condition of the feedback expectation record, the corresponding control message segment is updated to the feedback abnormal state, and the subsequent control message segments of the corresponding HVAC equipment are set to the pause state.

[0013] This invention also provides a KNX bus multi-device simultaneous screen time-sharing temperature control voice control device for implementing the above method, comprising: The mapping relationship establishment module is used to read KNX projects, central control screen pages and HVAC equipment parameter configurations, establish mapping relationships that associate page slots, timed temperature control tasks and voice control events with KNX control actions, and determine the parameter dependency order of each control function of the same HVAC equipment. The control message conversion module is used to convert timed temperature control tasks, screen-on touch events, and voice control events verified by voice recognition into control message slices for KNX bus scheduling and add them to the scheduling queue. The control message slices are associated with HVAC equipment, control functions, target values, control sources, and status feedback conditions. The transmission window and micro-timeslot allocation module is used to establish a page transmission window based on the associated page of the control message slice, and allocate transmission micro-timeslots to the control message slices in the page transmission window according to the KNX bus load; The conflict handling and message sending module is used to handle conflicts of the control message slices according to the parameter dependency order and the control source, select the control message slices that can be sent, convert the control message slices that can be sent into KNX group address values ​​for controlling the corresponding HVAC equipment within the sending micro-time slot, write them into the message and send them, and establish a pending feedback state. The feedback processing module is used to receive and parse KNX status feedback messages, confirm the control message slice based on the status feedback conditions of the control message slice, and perform feedback processing on subsequent control message slices.

[0014] Compared with the prior art, the present invention has the following beneficial effects: By unifying timed temperature control tasks, simultaneous touch events, and voice control events into control message slices, and grouping control message slices associated with the same page into the page sending window, and allocating micro-time slots for sending according to the KNX bus load, control requests from multiple HVAC devices can enter the sending process in a time-sharing manner according to bus occupancy, thereby reducing the centralized sending of control messages when multiple devices operate on the same page or multiple timed tasks are triggered simultaneously.

[0015] By constructing a device parameter execution chain according to the parameter dependency order of the same HVAC equipment, and performing source conflict handling for different target values ​​of the same control function, unsent voice control message fragments can replace conflict message fragments, and sent conflict message fragments awaiting feedback can constrain voice control message fragments to wait, thereby avoiding the continued issuance of conflicting HVAC control parameters when the preceding control state is unclear.

[0016] By establishing an associated version identifier and feedback expectation record for the sent control message fragments, and releasing subsequent control message fragments only based on the status feedback message or status read result corresponding to the current feedback version identifier, late feedback and failure to obtain a valid status read result will not directly trigger subsequent control, thereby reducing the situation where the central control panel continues to control HVAC equipment based on expired status. Attached Figure Description

[0017] Figure 1 This is a schematic diagram illustrating the steps of the KNX bus multi-device simultaneous time-sharing temperature control voice control method provided by the present invention; Figure 2 The flowchart of the KNX bus multi-device simultaneous time-sharing temperature control voice control method provided by the present invention; Figure 3 A schematic diagram illustrating the association between control message slices, page sending windows, and sending micro-time slots provided by the present invention; Figure 4 A comparison chart of the delay in the completion of sending control message segments on the same screen, provided by the present invention. Figure 5 This invention provides a comparison chart of the error transmission ratio of subsequent control message segments under status feedback delay. Figure 6 The structural diagram of the KNX bus multi-device simultaneous screen time-sharing temperature control voice control device provided by the present invention. Detailed Implementation

[0018] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0019] To enable those skilled in the art to better understand the present invention, the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0020] Please see Figure 1 and Figure 2 , Figure 1 This is a schematic diagram illustrating the steps of the KNX bus multi-device simultaneous screen time-sharing temperature control voice control method provided by the present invention; Figure 2 This invention provides a flowchart of a KNX bus multi-device simultaneous time-sharing temperature control voice control method. The invention provides a KNX bus multi-device simultaneous time-sharing temperature control voice control method, comprising: S1. Read the KNX project, central control screen page and HVAC equipment parameter configuration, establish a mapping relationship between page slots, timed temperature control tasks and voice control events and KNX control actions, and determine the parameter dependency order of each control function of the same HVAC equipment. Specifically, the central control screen includes a processor, memory, KNX communication interface, display and touch components, and a voice recognition result receiving interface. The memory stores KNX projects, central control screen pages, HVAC equipment parameter configurations, mapping relationships, scheduling queues, equipment parameter execution chains, and feedback expectation records. The central control screen reads the control group address, status feedback group address, data point type, and read / write attributes of the communication object corresponding to the HVAC equipment from the KNX project; it reads the page identifier, slot identifier, and control functions bound to the slot from the central control screen page; and it reads the equipment identifier, target value range of each control function, status feedback conditions, feedback waiting time, and function execution prerequisite relationships from the HVAC equipment parameter configuration. When loading the configuration, the central control screen verifies that the control group address has write permissions, the status feedback group address can be decoded according to the corresponding data point type, the target value range is complete, and the page slot is bound to a valid control function. Page slots that fail the verification are marked as unschedulable, and no control message fragments are generated for those slots.

[0021] Furthermore, establishing the mapping relationship between page slots, timed temperature control tasks, and voice control events and KNX control actions includes: Based on the KNX project, central control screen page and HVAC equipment parameter configuration, determine the HVAC equipment and control functions corresponding to the page slots, timed temperature control tasks and voice control events; The parameter dependency order is determined based on the execution prerequisite relationships between the various control functions of the same HVAC equipment; For each page slot, timed temperature control task, and voice control event, a mapping item is generated. The mapping item is associated with the corresponding HVAC equipment, control function, KNX control action, status feedback condition, and parameter dependency order. The mapping items are aggregated to form the mapping relationship.

[0022] Specifically, the central control screen uses page and slot identifiers as query keys for page slots, task identifiers as query keys for timed temperature control tasks, and room, device name, and control words from the voice recognition results as query keys for voice control events. The retrieved device identifier and control function must uniquely pinpoint a writable KNX control action. For example, the "Air Conditioner Temperature" slot on the living room page, the timed temperature control task executed daily at 18:00 ("Set the living room air conditioner to 26 degrees Celsius"), and the voice control event recognized as "Adjust the living room air conditioner to 26 degrees" all point to the living room air conditioner's set temperature control function.

[0023] For the same HVAC equipment, the central control panel first reads the equipment-specific execution prerequisite relationships. If equipment-specific execution prerequisite relationships exist, the parameter dependency order is set according to those relationships. If no equipment-specific execution prerequisite relationships exist, the parameter dependency order is set according to a preset general order, which is: on / off control, operating mode, set temperature, fan speed, and fresh air level. Control functions with lower parameter dependency orders are the prerequisite control functions for control functions with higher parameter dependency orders.

[0024] Each mapping item records at least the trigger object identifier, HVAC equipment identifier, control function, KNX control action, status feedback condition, and parameter dependency order. The KNX control action consists of the control group address, corresponding data point type, and target value encoding rule; the status feedback condition consists of the status feedback group address, feedback data point type, and expected feedback value or expected feedback range. The central control screen aggregates mapping items using the trigger object identifier as an index and establishes a reverse index using the HVAC equipment identifier and control function, forming the mapping relationship. The forward index is used to convert page slots, timed temperature control tasks, or voice control events into KNX control actions, while the reverse index is used to locate the corresponding HVAC equipment and control function when status feedback arrives.

[0025] S2. Convert the timed temperature control task, screen-on touch event, and voice control event verified by voice recognition into control message slices for KNX bus scheduling and add them to the scheduling queue. The control message slices are associated with HVAC equipment, control functions, target values, control sources, and status feedback conditions. Specifically, the central control screen checks timed temperature control tasks at a fixed scan cycle of 500 milliseconds. Timed temperature control tasks that have reached their trigger time but have not yet been executed are identified as scheduled temperature control tasks. On-screen touch events are generated by slot operations on the currently displayed page and carry at least the page identifier, slot identifier, operation time, and user input value. Voice recognition results are parsed using command words, room, equipment, control function, and target value to form voice control events. Voice recognition verification passes only if the voice control event can uniquely identify the HVAC equipment, control function, and target value through a mapping relationship, and the target value falls within the target value range of the corresponding control function. Results that fail voice recognition verification only output a clarification prompt and are not added to the scheduling queue.

[0026] Furthermore, the step of converting the timed temperature control task, screen-sharing touch event, and voice control event verified by voice recognition into control message fragments for KNX bus scheduling and adding them to the scheduling queue includes: Based on the mapping relationship, determine the HVAC equipment, control function, and target value corresponding to the timed temperature control task and the screen-on touch event, and verify whether the voice control event can uniquely identify the HVAC equipment, control function, and target value. The timed temperature control task, the screen-sharing touch event, and the verified voice control event are converted into corresponding control message fragments. For multiple control message fragments with the same control function and the same target value for the same HVAC equipment, merge processing is performed and the target control message fragment used for the KNX bus scheduling is retained; The control message fragments that have undergone the merging process are added to the scheduling queue.

[0027] Specifically, the central control screen performs a forward index query on the mapping relationship between timed temperature control tasks and on-screen touch events to obtain the corresponding HVAC equipment, control functions, and target values. For voice control events, the central control screen matches the parsed room, equipment name, control word, and target value with the mapping items one by one; only when the matching result is a mapping item is the unique HVAC equipment, control function, and target value corresponding to the voice control event determined. For example, "turn it up a little" cannot determine the target value, and "turn on the air conditioner" corresponds to the air conditioners in multiple rooms; neither of these passes the uniqueness check.

[0028] The central control screen generates a control message fragment for each valid event. The control message fragment records the HVAC equipment, control function, target value, control source, generation time, associated page, parameter dependency order, status feedback conditions, control group address, data point type, transmission status, and control message fragment version identifier. The control source is a timed temperature control task, a simultaneous touch event, or a voice control event; the initial transmission status is "pending scheduling." Whenever the same control function of the same HVAC equipment generates a new control message fragment, the version identifier increments based on the most recent version identifier. ; In the formula, This indicates the version identifier of the most recently generated control message fragment. This indicates the version identifier of the newly generated control message fragment.

[0029] The central control screen uses HVAC equipment, control functions, and target values ​​as merging keys to search for control message fragments in the pending scheduling status. If multiple control message fragments with the same merging key exist, the control message fragment with the higher control source priority is retained. If the control source priorities are the same, the control message fragment with the later generation time and newer version identifier is retained, and the remaining control message fragments are marked as merged. The retained target control message fragments are written to the pending scheduling queue according to their generation time, maintaining associations with their associated page, control source, parameter dependency order, status feedback conditions, and version identifier.

[0030] S3. Establish a page sending window based on the associated page of the control message slice, and allocate transmission micro-slots to the control message slices in the page sending window according to the KNX bus load; For details, please refer to Figure 3 , Figure 3 This is a schematic diagram illustrating the association between control message slices, page sending windows, and sending micro-time slots provided by the present invention. The central control screen groups control message slices in the queue to be scheduled according to associated pages. Control message slices associated with the same page participate in scheduling within the same page sending window; control message slices generated by timed temperature control tasks or voice control events but not corresponding to the currently displayed page are associated with pages based on the page identifier recorded in the mapping relationship. The start time of the page sending window is the earliest enqueuing time of the control message slice to be scheduled for that page, and the default window length is 1 second. Page switching only affects newly generated on-screen touch events and does not delete already created page sending windows.

[0031] Furthermore, the step of establishing a page transmission window based on the associated page of the control message slice, and allocating transmission micro-slots to the control message slices within the page transmission window according to the KNX bus load, includes: Group control message fragments associated with the same page into the same page's sending window; The KNX bus load is determined based on the number of KNX bus messages, the number of control message fragments that have been sent and are in the pending feedback state, and the proportion of communication error messages. The duration of the transmission micro-slot is determined based on the KNX bus load, and the control message slices within the page transmission window are selected in a time-division manner according to the transmission micro-slot; The control message slices selected by the time division are allocated to the corresponding transmission micro-slots.

[0032] Specifically, the central control screen uses associated pages as grouping keys to write control message fragments in the queue to be scheduled into the corresponding page sending window. Each page sending window stores the page identifier, window start time, window end time, and control message fragment identifier within the window.

[0033] The central control screen counts the number of KNX bus messages every 2 seconds. Number of control message fragments that have been sent and are awaiting feedback Number of control message fragments in the queue to be scheduled and the number of communication error messages Communication error messages include duplicate messages, unacknowledged messages, and data point type mismatch messages. The reference message count is based on the configuration during installation and debugging. Based on this, calculate the KNX bus load using the following formula. : ; In the formula, Indicates message occupancy. Characterizes the feedback waiting degree. Characterizes the proportion of abnormal communication messages; To avoid a denominator of zero, 0.5, 0.3, and 0.2 are preset weights corresponding to the message occupancy rate, the feedback waiting rate, and the proportion of communication anomalies, respectively, with the sum of the three preset weights being 1. In this embodiment, the message occupancy rate directly represents the message occupancy of the KNX bus within the statistical period, and its preset weight is set to 0.5; the feedback waiting rate represents the degree of constraint that sent and pending feedback control message segments impose on the subsequent transmission of control message segments, and its preset weight is set to 0.3; the proportion of communication anomalies is used to correct the impact of duplicate messages, unacknowledged messages, and data point type mismatch messages on the KNX bus load, and its preset weight is set to 0.2. The preset weights are written into the device parameter configuration of the central control screen and remain unchanged during the control process.

[0034] The central control screen calculates the scheduling interval between the start times of adjacent transmission micro-time slots in milliseconds using the following formula. : ; In the formula, For KNX bus load, 80 milliseconds is the minimum scheduling interval between the start times of adjacent transmission micro-slots under low load, and 500 milliseconds is the maximum scheduling interval between the start times of adjacent transmission micro-slots under high load. The central control screen performs time-division selection based on the parameter dependency order, control source priority, and enqueue time of the control message pieces within the page transmission window, and groups one or more control message pieces to be determined that do not have parameter dependency conflicts with the same HVAC equipment into a transmission batch. Each transmission micro-slot is pre-allocated one transmission batch. The central control screen writes the start time and end time of the transmission micro-slot to the transmission batch; when each control message piece in the transmission batch is confirmed to be transmittable by S4, it is transmitted sequentially in the transmission micro-slot according to the equipment parameter execution chain and control source priority. Control message pieces that are confirmed to be untransmittable by S4 are removed from the transmission batch and retained for the next round of selection.

[0035] S4. Based on the parameter dependency order and the control source, perform conflict handling on the control message slices, select the control message slices that can be sent, convert the control message slices that can be sent into KNX group address values ​​for controlling the corresponding HVAC equipment within the transmission micro-slot, write them into the message and send them, and establish a pending feedback state. Specifically, upon reaching a transmission micro-slot, the central control screen performs parameter dependency order judgment and control source conflict handling on each control message fragment in the corresponding transmission batch for that micro-slot. It selects transmittable objects that meet the corresponding handling results and determines the transmission order of each transmittable object within the transmission batch according to the device parameter execution chain, control source priority, and enqueue time. For the selected transmittable control message fragment, the central control screen encodes the target value based on the control group address and data point type in the corresponding KNX control action, generating a KNX group address value for controlling the corresponding HVAC equipment and writing it into the message. Before transmission, the target value range, control group address write attribute, and device offline status are verified again. If the verification passes, the message is transmitted via the KNX communication interface; if the verification fails, the control message fragment is updated to a transmission failure status, and subsequent control message fragments in the device that use this control message fragment as a prerequisite are blocked.

[0036] Furthermore, the conflict resolution of the control message fragments based on the parameter dependency order and the control source includes: The control message fragments are grouped according to the HVAC equipment, and then sorted within each equipment group according to parameter dependency order, control source priority, and generation time to obtain the equipment parameter execution chain; For control message segments with different target values ​​for the same control function of the same HVAC equipment, source conflict handling is performed according to the priority and transmission status of the control source. The source conflict handling is used to determine the target control message segment and the execution status. For control message slices of different control functions of the same HVAC equipment, after the control message slice with smaller parameter dependency order meets the status feedback condition, the control message slice with larger parameter dependency order is determined as the sendable object. The device parameter execution chain is updated based on the source conflict resolution and the sendable object.

[0037] Specifically, the central control screen initially uses HVAC equipment as the grouping key. The sorting key for control message slices within each equipment group is: ; In the formula, Indicates the first A control message fragment, Indicates the order of its parameter dependencies. Indicates the priority of its control source. This indicates the generation time. The central control screen sorts the data in ascending lexicographical order according to the sorting key, that is, it first compares the order of smaller parameter dependencies; if the parameter dependency orders are the same, the higher priority is placed first; if both are still the same, the earlier generated control message is placed first. In this embodiment, the control source priorities of voice control events, screen-sharing touch events, and timed temperature control tasks are 3, 2, and 1, respectively.

[0038] When all conflicting objects are in an unsent state, the control message fragment with the higher priority from the control source is retained as the target control message fragment; when the control source priorities are the same, the control message fragment with the newer version identifier is retained. If there is a sent control message fragment among the conflicting objects that is in a pending feedback state, the already sent control action is not directly overwritten with the unacknowledged new target value. Instead, the control message fragment corresponding to the new target value is placed in a waiting state until the sent control message fragment is acknowledged or feedback processing is completed.

[0039] In the device parameter execution chain, control message slices with higher parameter dependency order are released only when their immediately adjacent or all preceding control message slices with lower parameter dependency order have met the status feedback conditions. For example, the parameter dependency order of air conditioner switch control is 1, the parameter dependency order of operating mode is 2, and the parameter dependency order of set temperature is 3. Only after the status feedback corresponding to the switch control indicates that the air conditioner is turned on does the operating mode control message slice become a sendable object, and only after the operating mode control receives the corresponding status feedback does the set temperature control message slice become a sendable object. The central control screen writes the target control message slice after source conflict resolution into the device parameter execution chain, removes merged control message slices from the chain, retains waiting status control message slices after the sent and feedback-pending control message slices, and marks the released control message slices as sendable objects.

[0040] Furthermore, the source conflict resolution includes: When the control message slice corresponding to the voice control event has a different target value from the unsent control message slice of the same control function of the same HVAC equipment, the control message slice corresponding to the voice control event is used as the target control message slice to replace the unsent control message slice, and the equipment parameter execution chain is redefined. When the control message corresponding to the voice control event has a different target value from the control message of the same control function of the same HVAC equipment that has been sent and is in the state of waiting for feedback, the control message corresponding to the voice control event is set to the waiting state. After the control message fragment that has been sent and is in the state awaiting feedback meets the state feedback condition, the device parameter execution chain is re-determined based on the feedback state.

[0041] Specifically, when a control message corresponding to a voice control event conflicts with an unsent control message, the central control screen replaces the unsent control message with the control message corresponding to the voice control event and marks the replaced control message as replaced. The central control screen then uses the replaced target control message to re-execute the sorting key calculation and device parameter execution chain generation, ensuring that the voice control event remains subject to parameter dependency order constraints.

[0042] The actual device status corresponding to a control message slice that has been sent and is in a pending feedback state has not yet been confirmed. At this time, the central control screen marks the control message slice corresponding to the voice control event as a waiting state and associates it with the feedback expectation record of the sent control message slice. Voice control message slices in the waiting state do not occupy transmission micro-time slots, nor are they written to the KNX bus. When the sent control message slice meets the status feedback conditions, the central control screen updates it to the confirmed state, uses this feedback state as the current device status, and restores the waiting voice control message slice to the pending scheduling state. Subsequently, the parameter dependency order and sorting position of the voice control message slice and subsequent control message slices of the same device are re-determined to obtain the updated device parameter execution chain. If the sent control message slice does not meet the status feedback conditions, the status is read or paused according to the feedback handling process of S5, instead of directly releasing the voice control message slice.

[0043] Furthermore, establishing the pending feedback state includes: For each sent control message segment, a feedback expectation record is generated, which is associated with HVAC equipment, control function, status feedback conditions, control message segment version identifier, and sending time. The control message slice version identifier is used to characterize the order of control message slices for the same control function of the same HVAC equipment. The version identifier of the latest control message slice sent and not yet processed in the same control function of the same HVAC equipment is determined as the current feedback version identifier. Control message slices in the pending scheduling state or waiting state do not update the current feedback version identifier. Associate the sent control message fragments with the corresponding feedback expectation records and mark them as pending feedback status.

[0044] Specifically, after the KNX communication interface completes the group address value writing and message transmission, the central control screen generates a feedback expectation record for that control message segment. The feedback expectation record includes at least the HVAC equipment, control function, status feedback conditions, control message segment version identifier, transmission time, feedback waiting period, and transmission status. The status feedback conditions retain the status feedback group address, data point type, and expected feedback value or expected feedback range.

[0045] The central control panel maintains a version identifier sequence for the same control function of the same HVAC equipment and maintains a separate current feedback version identifier. When a control message fragment completes transmission and enters the pending feedback state, the version identifier of that control message fragment is recorded as the current feedback version identifier for the corresponding HVAC equipment and control function; control message fragments in the pending scheduling state, waiting state, merged state, or replaced state do not update the current feedback version identifier. After the control message fragment corresponding to the current feedback version identifier completes feedback processing, if the waiting state control message fragment returns to the pending scheduling state and completes transmission, the current feedback version identifier is updated with the version identifier of that control message fragment. Feedback expectation records not corresponding to the current feedback version identifier are not used to release subsequent control message fragments even if a status feedback message satisfying the old target value is subsequently received. The central control panel writes the identifier of the transmitted control message fragment into the corresponding feedback expectation record and updates the transmission status of that control message fragment to the pending feedback state. The pending feedback state serves as both the feedback waiting degree statistical input for S3 and the equipment parameter execution chain release constraint input for S4.

[0046] S5. Receive and parse the KNX status feedback message, confirm the control message slice based on the status feedback conditions of the control message slice, and perform feedback processing on subsequent control message slices.

[0047] Specifically, the KNX communication interface continuously listens for the status feedback group address. The central control screen decodes the received KNX status feedback messages based on the data point types recorded in the mapping relationship to obtain the feedback group address, feedback value, and reception time; then, it queries the control message fragments of the status to be fed back and their expected feedback records based on HVAC equipment, control functions, and status feedback conditions.

[0048] Furthermore, the step of receiving and parsing the KNX status feedback message, and confirming the control message slice based on the status feedback conditions of the control message slice, includes: For control message segments in the pending feedback state, when the version identifier of the control message segment to be recorded is the current feedback version identifier of the same control function of the same HVAC equipment, the KNX status feedback message whose reception time is later than the transmission time and meets the status feedback conditions will be matched to the corresponding control message segment. Update the control message fragment that matches the KNX status feedback message to the confirmed status, and release the subsequent control message fragments in the same HVAC equipment whose parameter dependency order is greater than the control message fragment and which have no other unconfirmed preceding control message fragments as sendable objects.

[0049] Specifically, the central control screen calculates and matches the feedback result for each control message segment awaiting feedback status: ; In the formula, Indicates the first The feedback matching results of each control message fragment. This indicates the control message fragment version identifier in the feedback expectation record. This indicates the current feedback version identifier for the most recently sent control message fragment that has not yet completed feedback processing within the same control function of the same HVAC equipment. Indicates the time of receipt of the KNX status feedback message. Indicates the timing of controlling the transmission of message segments. This represents the feedback value after decoding. This represents the set of expected feedback values ​​or the expected feedback range defined by the state feedback conditions. It applies if and only if... At that time, the KNX status feedback message is matched to the corresponding control message fragment.

[0050] Upon successful matching, the central control screen updates the sending status of the corresponding control message to "confirmed" and displays the actual status obtained from decoding the status feedback message in the page slot. The central control screen then searches the device parameter execution chain of the same HVAC equipment and updates subsequent control messages whose parameter dependency order is adjacent to the confirmed control message and which do not have other unconfirmed preceding control messages as sendable objects.

[0051] Furthermore, the feedback processing for subsequent control message fragments includes: When the control message fragment version identifier of the feedback expectation record is the current feedback version identifier, no KNX status feedback message is matched after the feedback waiting period, and no KNX group address value read message has been generated for the feedback expectation record, a KNX group address value read message for reading the status of the corresponding HVAC equipment is generated. When the control message segment version identifier of the feedback expectation record is the current feedback version identifier and the return result of the KNX group address value read message meets the status feedback condition of the feedback expectation record, the corresponding control message segment is updated to the confirmed status, and the subsequent control message segments in the same HVAC equipment whose parameter dependency order is greater than the control message segment and which do not have other unconfirmed preceding control message segments are released as sendable objects. When the control message segment version identifier of the feedback expectation record is the current feedback version identifier and the KNX group address value read message does not obtain a return result that satisfies the status feedback condition of the feedback expectation record, the corresponding control message segment is updated to the feedback abnormal state, and the subsequent control message segments of the corresponding HVAC equipment are set to the pause state.

[0052] Specifically, the central control screen periodically checks the feedback waiting period for the pending status. If the control message version identifier for the expected feedback record remains the current feedback version identifier, and the difference between the current time and the sending time reaches the feedback waiting period, and no matching KNX status feedback message exists, the central control screen generates a KNX group address value read message based on the recorded status feedback group address. This read message does not change the device target value; it only requests the device or bus status object to return the current status. In this embodiment, the feedback waiting period is set to 2 seconds.

[0053] The central control screen decodes and judges the return result of the read message based on the same status feedback conditions as the above feedback. When the return result meets the expected feedback value or expected feedback range, the central control screen updates the corresponding control message slice to the confirmed state and releases subsequent control message slices in the same HVAC equipment whose parameter dependency order is greater than that of the control message slice and which have no other unconfirmed preceding control message slices as transmittable objects. When no return result is obtained from reading the message, the return result cannot be decoded according to the data point type, or the return result does not meet the status feedback conditions, the central control screen updates the corresponding control message slice to the feedback abnormal state and sets the subsequent control message slices of the corresponding HVAC equipment to the paused state, while retaining the actual known state or unknown state mark of the current equipment. The paused state prevents subsequent control message slices from entering the transmission micro-time slot, but does not affect the time-sharing scheduling of control message slices belonging to other HVAC equipment.

[0054] In one consistent embodiment, the living room fan coil unit is identified as FC-01, and the central control screen page is identified as P01. Slot A01 in page P01 is bound to the switch control function, with KNX control group address 1 / 1 / 1, status feedback group address 1 / 1 / 11, and data point type a one-bit switch quantity; slot A02 is bound to the operating mode control function, with KNX control group address 1 / 1 / 2, status feedback group address 1 / 1 / 12; slot A03 is bound to the set temperature control function, with KNX control group address 1 / 1 / 3, status feedback group address 1 / 1 / 13, and data point type a two-byte floating-point temperature quantity. The parameter dependency order of FC-01 is set as switch control 1, operating mode control 2, and set temperature control 3; the legal range of the set temperature is 16 degrees Celsius to 30 degrees Celsius, and the feedback waiting period is 2 seconds. The above data forms three mapping items corresponding to FC-01, and is written into the mapping relationship and device parameter configuration record respectively.

[0055] At 18:00:00, the timed temperature control task generates the control intent to "turn on FC-01 and set the temperature to 26 degrees Celsius". The central control screen generates a switch control message P1 and a set temperature control message P2 based on the mapping relationship. The target value of P1 is "on", the parameter dependency order is 1, and the control source is the timed temperature control task; the target value of P2 is 26 degrees Celsius, the parameter dependency order is 3, and the control source is the timed temperature control task. P1 and P2 are written to the scheduling queue of page P01. At 18:00:00.200, the central control screen receives a voice control event to "set the living room air conditioner to 24 degrees Celsius". The voice recognition result uniquely determines the set temperature control function of FC-01 and the target value of 24 degrees Celsius, and generates a set temperature control message P3. Since P2 and P3 belong to the same control function of the same HVAC equipment but have different target values, and P2 has not yet been sent, P3 replaces P2 as the target control message slice. P2 is marked as replaced, and the version identifier of P3 becomes the latest generated version identifier of the set temperature control function. Since P3 has not yet been sent, the version identifier of P3 does not update the current feedback version identifier of the set temperature control function.

[0056] Within the 2-second rolling statistical period at this moment, the number of KNX bus messages is 30, the number of reference messages is 50, the number of control message fragments awaiting feedback is 1, the number of control message fragments in the scheduling queue is 4, and the number of communication error messages is 1. Therefore, the KNX bus load is approximately 0.382, and the transmission micro-slot duration is approximately 240 milliseconds. The central control screen first allocates P1 to the first transmission micro-slot, reserving P3 after P1. When the first transmission micro-slot arrives, the central control screen encodes P1 as a KNX group address value with the value enabled (written to group address 1 / 1 / 1) and writes it into a message, establishing a feedback expectation record R1. R1 stores FC-01, switch control function, status feedback group address 1 / 1 / 11, expected feedback value as enabled, P1's version identifier, and P1's transmission time; P1 is marked as awaiting feedback.

[0057] 100 milliseconds after P1 is sent, the central control screen receives a status feedback message from group address 1 / 1 / 11, with a decoded value of "on". Since the reception time of this feedback message is later than the transmission time of P1, the version identifier of P1 remains the current feedback version identifier corresponding to the on / off control function of FC-01, and the feedback value meets the status feedback condition of R1. Therefore, P1 is updated to the confirmed state. The central control screen checks the device parameter execution chain of FC-01 and finds that the operating mode control function has not generated a control message fragment to be scheduled. Therefore, P3 is released as a transmittable object. In the next transmission micro-slot, P3 is encoded as a KNX group address value of 24 degrees Celsius written to group address 1 / 1 / 3, and a feedback expectation record R3 is established.

[0058] If a status feedback message with a value of 24 degrees Celsius is received from group address 1 / 1 / 13 within 2 seconds after P3 sends the message, P3 will directly update to the acknowledged status. If no such status feedback message is received, the central control screen generates a read message to read the KNX group address value of group address 1 / 1 / 13; if the returned temperature value is 24 degrees Celsius, P3 updates to the acknowledged status. If the read message does not return a temperature value or the returned value is not within the allowable range, the central control screen will put the subsequent control message segments of FC-01 into a paused state, while keeping the control message segments belonging to other HVAC equipment participating in scheduling.

[0059] Please see Figure 6 , Figure 6 This invention provides a structural diagram of a KNX bus multi-device simultaneous screen time-sharing temperature control voice control device. The invention also provides a KNX bus multi-device simultaneous screen time-sharing temperature control voice control device for implementing the above method, comprising: The mapping relationship establishment module is used to read KNX projects, central control screen pages and HVAC equipment parameter configurations, establish mapping relationships that associate page slots, timed temperature control tasks and voice control events with KNX control actions, and determine the parameter dependency order of each control function of the same HVAC equipment. The control message conversion module is used to convert timed temperature control tasks, screen-on touch events, and voice control events verified by voice recognition into control message slices for KNX bus scheduling and add them to the scheduling queue. The control message slices are associated with HVAC equipment, control functions, target values, control sources, and status feedback conditions. The transmission window and micro-timeslot allocation module is used to establish a page transmission window based on the associated page of the control message slice, and allocate transmission micro-timeslots to the control message slices in the page transmission window according to the KNX bus load; The conflict handling and message sending module is used to handle conflicts of the control message slices according to the parameter dependency order and the control source, select the control message slices that can be sent, convert the control message slices that can be sent into KNX group address values ​​for controlling the corresponding HVAC equipment within the sending micro-time slot, write them into the message and send them, and establish a pending feedback state. The feedback processing module is used to receive and parse KNX status feedback messages, confirm the control message slice based on the status feedback conditions of the control message slice, and perform feedback processing on subsequent control message slices.

[0060] Specifically, Figure 6The mapping relationship establishment module provides the mapping relationship and parameter dependency order to the control message slice conversion module; the control message slice conversion module outputs the queue to be scheduled to the sending window and micro-time slot allocation module; the sending window and micro-time slot allocation module outputs the control message slices with allocated sending micro-time slots to the conflict handling and message sending module; the conflict handling and message sending module writes the KNX group address value into the message and sends it to the KNX bus, and stores the established feedback expectation record as data accessible to the feedback handling module; the feedback handling module receives the KNX status feedback message and sends back the sendable object or the pause status of the subsequent control message slice to the conflict handling and message sending module to form a closed-loop scheduling.

[0061] Please see Figure 4 , Figure 4 This is a comparison chart showing the completion delay of screen-sharing control message fragment transmission provided by the present invention. In a verification configuration, background status messages generated by other bus devices continuously exist on the KNX bus. Figure 4 The horizontal axis represents the number of control message fragments to be scheduled within the same page, taking values ​​of 4, 8, 12, and 16; the vertical axis represents the transmission completion delay, in milliseconds. The transmission completion delay is defined as the time from when the corresponding control event enters the scheduling queue to when the last KNX group address value corresponding to the control event is written into the message and transmission is completed. In this embodiment, one transmission micro-slot corresponds to one transmission batch. The same transmission batch can include multiple control message fragments belonging to different HVAC devices and without parameter dependency conflicts. The control message fragments within the transmission batch are written to the KNX bus in a determined transmission order, and the start time of adjacent transmission batches is determined according to the scheduling interval. In the comparative method, control message fragments are sent one by one according to the arrival order of control events. When the KNX bus is detected to be busy, the transmission is retried after the bus is released. In the present invention, control message fragments with the same target value are first merged, and then control message fragments without parameter dependency conflicts are grouped into transmission batches. The scheduling interval of adjacent transmission batches is determined according to the KNX bus load. When the average value is taken after multiple repeated verifications, and the number of control message fragments is 4, 8, 12 and 16, the transmission completion delay of the control method is 84 milliseconds, 186 milliseconds, 319 milliseconds and 480 milliseconds respectively; the transmission completion delay of the present invention method is 70 milliseconds, 131 milliseconds, 203 milliseconds and 287 milliseconds respectively.

[0062] Please see Figure 5 , Figure 5 This is a comparison chart showing the proportion of subsequent control message fragment errors under the status feedback delay provided by the present invention. In another verification configuration, Figure 5The horizontal axis represents the status feedback delay, which is the time between the completion of the KNX group address value writing message corresponding to the preceding control message and the arrival of the corresponding KNX status feedback message at the central control screen, and is set to 50 milliseconds, 100 milliseconds, 150 milliseconds, and 200 milliseconds respectively; the vertical axis represents the proportion of subsequent control message erroneous transmissions. A subsequent control message erroneous transmission refers to a situation where a preceding control message is temporarily confirmed as having an acknowledged state based on the received KNX status feedback message, and is accordingly released and transmitted to subsequent dependent control message messages, but the feedback state obtained again within the preset stable confirmation observation period does not meet the status feedback conditions of the preceding control message.

[0063] To simulate the actual operating state when multiple KNX control terminals are connected to the bus, during the verification process, while keeping the number of bus background messages basically consistent, status feedback object update jitter, duplicate status feedback messages, and other KNX controller overwrite operations on the same HVAC equipment control function are injected according to a preset ratio. During the preset stable confirmation observation period after the preceding control message is confirmed, subsequent status feedback messages of the corresponding status feedback group address are continuously monitored and recorded to determine whether the preceding control state continues to meet the status feedback conditions.

[0064] The comparison method does not set feedback gating based on the current feedback version identifier, reception time, and status feedback conditions; it releases subsequent control message fragments immediately upon receiving any status feedback message corresponding to the target HVAC equipment. The present invention, however, is based on feedback expectation records, performing joint matching of the control message fragment version identifier, status feedback message reception time, and feedback value, and releasing subsequent control message fragments only upon successful matching. In this verification configuration, the delay of each status feedback is less than a 2-second feedback waiting period; therefore, the KNX group address value reading message was not triggered during the verification process. Figure 5 This reflects the effect of the feedback expectation recording and state feedback matching mechanism on suppressing the erroneous transmission of subsequent control message segments under different state feedback delays.

[0065] Because the status feedback object may initially return a transient state that meets the target value within a short period, and then revert to a state that does not meet the status feedback conditions due to device execution failure, status update jitter, or other KNX controller overwrites, the method of this invention may still generate a small number of subsequent control message fragment errors. As the status feedback delay increases, the interference-affected time window between the transmission of the preceding control message and the confirmation of the stable state increases accordingly, and the proportion of subsequent control message fragment errors increases. When the status feedback delay is 50 ms, 100 ms, 150 ms, and 200 ms, the proportions of subsequent control message fragment errors in the control method are 4.5%, 11.8%, 22.6%, and 36.5%, respectively; while those in the method of this invention are 1.2%, 2.4%, 3.1%, and 4.2%, respectively.

[0066] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0067] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A KNX bus multi-device simultaneous time-sharing temperature control voice control method, characterized in that, include: S1. Read the KNX project, central control screen page and HVAC equipment parameter configuration, establish a mapping relationship between page slots, timed temperature control tasks and voice control events and KNX control actions, and determine the parameter dependency order of each control function of the same HVAC equipment. S2. Convert the timed temperature control task, screen-on touch event, and voice control event verified by voice recognition into control message slices for KNX bus scheduling and add them to the scheduling queue. The control message slices are associated with HVAC equipment, control functions, target values, control sources, and status feedback conditions. S3. Establish a page sending window based on the associated page of the control message slice, and allocate transmission micro-slots to the control message slices in the page sending window according to the KNX bus load; S4. Based on the parameter dependency order and the control source, perform conflict handling on the control message slices, select the control message slices that can be sent, convert the control message slices that can be sent into KNX group address values ​​for controlling the corresponding HVAC equipment within the transmission micro-slot, write them into the message and send them, and establish a pending feedback state. S5. Receive and parse the KNX status feedback message, confirm the control message slice based on the status feedback conditions of the control message slice, and perform feedback processing on subsequent control message slices.

2. The method according to claim 1, characterized in that, The process of establishing a mapping relationship between page slots, timed temperature control tasks, and voice control events and KNX control actions includes: Based on the KNX project, central control screen page and HVAC equipment parameter configuration, determine the HVAC equipment and control functions corresponding to the page slots, timed temperature control tasks and voice control events; The parameter dependency order is determined based on the execution prerequisite relationships between the various control functions of the same HVAC equipment; For each page slot, timed temperature control task, and voice control event, a mapping item is generated. The mapping item is associated with the corresponding HVAC equipment, control function, KNX control action, status feedback condition, and parameter dependency order. The mapping items are aggregated to form the mapping relationship.

3. The method according to claim 1, characterized in that, The process of converting timed temperature control tasks, screen-on touch events, and voice control events verified by voice recognition into control message fragments for KNX bus scheduling and adding them to the scheduling queue includes: Based on the mapping relationship, determine the HVAC equipment, control function, and target value corresponding to the timed temperature control task and the screen-on touch event, and verify whether the voice control event can uniquely identify the HVAC equipment, control function, and target value. The timed temperature control task, the screen-sharing touch event, and the verified voice control event are converted into corresponding control message fragments. For multiple control message fragments with the same control function and the same target value for the same HVAC equipment, merge processing is performed and the target control message fragment used for the KNX bus scheduling is retained; The control message fragments that have undergone the merging process are added to the scheduling queue.

4. The method according to claim 1, characterized in that, The step of establishing a page transmission window based on the associated page of the control message slice, and allocating transmission micro-slots to the control message slices within the page transmission window according to the KNX bus load, includes: Group control message fragments associated with the same page into the same page's sending window; The KNX bus load is determined based on the number of KNX bus messages, the number of control message fragments that have been sent and are in the pending feedback state, and the proportion of communication error messages. The duration of the transmission micro-slot is determined based on the KNX bus load, and the control message slices within the page transmission window are selected in a time-division manner according to the transmission micro-slot; The control message slices selected by the time division are allocated to the corresponding transmission micro-slots.

5. The method according to claim 1, characterized in that, The conflict resolution of the control message fragments based on the parameter dependency order and the control source includes: The control message fragments are grouped according to the HVAC equipment, and then sorted within each equipment group according to parameter dependency order, control source priority, and generation time to obtain the equipment parameter execution chain; For control message segments with different target values ​​for the same control function of the same HVAC equipment, source conflict handling is performed according to the priority and transmission status of the control source. The source conflict handling is used to determine the target control message segment and the execution status. For control message slices of different control functions of the same HVAC equipment, after the control message slice with smaller parameter dependency order meets the status feedback condition, the control message slice with larger parameter dependency order is determined as the sendable object. The device parameter execution chain is updated based on the source conflict resolution and the sendable object.

6. The method according to claim 5, characterized in that, The source conflict resolution includes: When the control message slice corresponding to the voice control event has a different target value from the unsent control message slice of the same control function of the same HVAC equipment, the control message slice corresponding to the voice control event is used as the target control message slice to replace the unsent control message slice, and the equipment parameter execution chain is redefined. When the control message corresponding to the voice control event has a different target value from the control message of the same control function of the same HVAC equipment that has been sent and is in the state of waiting for feedback, the control message corresponding to the voice control event is set to the waiting state. After the control message fragment that has been sent and is in the state awaiting feedback meets the state feedback condition, the device parameter execution chain is re-determined based on the feedback state.

7. The method according to claim 1, characterized in that, The establishment of the pending feedback state includes: For each sent control message segment, a feedback expectation record is generated, which is associated with HVAC equipment, control function, status feedback conditions, control message segment version identifier, and sending time. The control message slice version identifier is used to characterize the order of control message slices for the same control function of the same HVAC equipment. The version identifier of the latest control message slice sent and not yet processed in the same control function of the same HVAC equipment is determined as the current feedback version identifier. Control message slices in the pending scheduling state or waiting state do not update the current feedback version identifier. Associate the sent control message fragments with the corresponding feedback expectation records and mark them as pending feedback status.

8. The method according to claim 7, characterized in that, The process of receiving and parsing the KNX status feedback message, and confirming the control message slice based on the status feedback conditions of the control message slice, includes: For control message segments in the pending feedback state, when the version identifier of the control message segment to be recorded is the current feedback version identifier of the same control function of the same HVAC equipment, the KNX status feedback message whose reception time is later than the transmission time and meets the status feedback conditions will be matched to the corresponding control message segment. Update the control message fragment that matches the KNX status feedback message to the confirmed status, and release the subsequent control message fragments in the same HVAC equipment whose parameter dependency order is greater than the control message fragment and which have no other unconfirmed preceding control message fragments as sendable objects.

9. The method according to claim 8, characterized in that, The feedback processing of subsequent control message fragments includes: When the control message fragment version identifier of the feedback expectation record is the current feedback version identifier, no KNX status feedback message is matched after the feedback waiting period, and no KNX group address value read message has been generated for the feedback expectation record, a KNX group address value read message for reading the status of the corresponding HVAC equipment is generated. When the control message segment version identifier of the feedback expectation record is the current feedback version identifier and the return result of the KNX group address value read message meets the status feedback condition of the feedback expectation record, the corresponding control message segment is updated to the confirmed status, and the subsequent control message segments in the same HVAC equipment whose parameter dependency order is greater than the control message segment and which do not have other unconfirmed preceding control message segments are released as sendable objects. When the control message segment version identifier of the feedback expectation record is the current feedback version identifier and the KNX group address value read message does not obtain a return result that satisfies the status feedback condition of the feedback expectation record, the corresponding control message segment is updated to the feedback abnormal state, and the subsequent control message segments of the corresponding HVAC equipment are set to the pause state.

10. A KNX bus multi-device simultaneous screen time-sharing temperature control voice control device, characterized in that, To implement the method according to any one of claims 1 to 9, comprising: The mapping relationship establishment module is used to read KNX projects, central control screen pages and HVAC equipment parameter configurations, establish mapping relationships that associate page slots, timed temperature control tasks and voice control events with KNX control actions, and determine the parameter dependency order of each control function of the same HVAC equipment. The control message conversion module is used to convert timed temperature control tasks, screen-on touch events, and voice control events verified by voice recognition into control message slices for KNX bus scheduling and add them to the scheduling queue. The control message slices are associated with HVAC equipment, control functions, target values, control sources, and status feedback conditions. The transmission window and micro-timeslot allocation module is used to establish a page transmission window based on the associated page of the control message slice, and allocate transmission micro-timeslots to the control message slices in the page transmission window according to the KNX bus load; The conflict handling and message sending module is used to handle conflicts of the control message slices according to the parameter dependency order and the control source, select the control message slices that can be sent, convert the control message slices that can be sent into KNX group address values ​​for controlling the corresponding HVAC equipment within the sending micro-time slot, write them into the message and send them, and establish a pending feedback state. The feedback processing module is used to receive and parse KNX status feedback messages, confirm the control message slice based on the status feedback conditions of the control message slice, and perform feedback processing on subsequent control message slices.

Images