A method for collaborative communication between an electric vehicle controller and an instrument panel

By optimizing the communication between the electric vehicle controller and the instrument panel through change detection and adaptive compression mechanisms, the problems of high bus load rate and delayed reporting of key information were solved, achieving the effects of reducing bus load rate and timely information transmission.

CN123123393APending Publication Date: 2026-11-17ZHEJIANG BLUEPOINT POWER TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611350405.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-09-02
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In the existing communication between electric vehicle controllers and instruments, the increase in the number of data items leads to a sharp rise in bus load rate, which poses risks of data frame loss, increased transmission delay and bus crash. In addition, traditional communication strategies have security risks such as wasted bus bandwidth and delayed reporting of critical information.

Method used

By generating a change flag array through cycle-by-cycle change detection, data segments are dynamically divided. Combined with a two-level adaptive compression mechanism and dynamic priority scheduling, only changed data is sent and critical information is processed first, ensuring reduced bus load and timely information transmission.

Benefits of technology

It effectively reduces bus load, avoids redundant transmission, ensures timely reporting of critical information, and improves communication efficiency and security.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123123393A_ABST
    Figure CN123123393A_ABST
Patent Text Reader

Abstract

This invention discloses a collaborative communication method between an electric vehicle controller and an instrument panel, relating to the field of collaborative communication technology. This method uses cycle-by-cycle change detection to send data only when a valid change occurs. Unchanged data is automatically reused from historical values ​​by the receiving end, fundamentally avoiding redundant transmission. Combined with a two-level adaptive compression mechanism, it dynamically selects bit-width reduction or differential encoding based on bus busy levels, minimizing transmission volume while ensuring accuracy and effectively mitigating bus congestion risks. Dynamic priority scheduling ensures fault codes unconditionally receive the highest arbitration priority, guaranteeing abnormal states are reported with the shortest delay. Data items with excessive urgent changes receive the second-highest priority, preventing critical information from being blocked. Non-urgent data frames gradually increase their priority through a waiting time promotion mechanism, fundamentally eliminating the hidden danger of long-term waiting for low-priority data.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of collaborative communication technology, specifically to a collaborative communication method between an electric vehicle controller and an instrument panel. Background Technology

[0002] The collaborative communication between the electric vehicle controller and the instrument panel is a core element to ensure the normal operation of the vehicle. The controller needs to transmit the operating data to the instrument panel in real time so that the driver can accurately grasp the vehicle status. Currently, the controller and the instrument panel generally use controller local area network bus technology for data exchange. This technology is widely used in the field of vehicle control due to its high communication speed and strong anti-interference capability. However, as electric vehicles become increasingly feature-rich, the number of data items that need to be transmitted continues to increase. To ensure the smoothness of the instrument display, existing technologies typically send all data items continuously at a fixed millisecond interval, causing the bus load rate to rise sharply. When the load rate exceeds the safety threshold, it can easily lead to problems such as data frame loss, increased transmission delay, or even bus crash, directly affecting vehicle safety and driving experience. In addition, parameters such as temperature often change extremely slowly or even remain completely unchanged in adjacent cycles, but existing communication strategies do not take advantage of this characteristic and still send all data in a fixed format, resulting in a serious waste of bus bandwidth. At the same time, traditional buses use a fixed priority arbitration mechanism, and low-priority data frames may not get a chance to be sent for a long time during congestion, resulting in critical information such as fault codes not being reported in a timely manner, posing a safety hazard. Therefore, there is an urgent need for a controller and instrument collaborative communication method that can effectively reduce bus load rate while ensuring the real-time performance of critical data, in order to overcome the shortcomings of the existing technology. Summary of the Invention

[0003] The purpose of this invention is to provide a method for collaborative communication between an electric vehicle controller and an instrument panel, so as to solve the problems mentioned in the background art.

[0004] To achieve the above objectives, the present invention provides the following technical solution: a method for collaborative communication between an electric vehicle controller and an instrument panel, comprising the following steps: S1. The controller collects seven operational data items in each statistical period, calculates the change amount for each item, compares each change amount with the corresponding preset threshold, sets the corresponding change flag to 1 when the change amount is greater than the threshold, otherwise sets it to 0, and generates a seven-bit change flag array for output. S2. Based on the change flag array, divide the data into a changed set and an unchanged set, construct a first data segment of fixed length to carry the flags, and construct a second data segment of variable length to carry only the current value of the changed data item; S3. Obtain the real-time bus load rate according to the total amount of data within the statistical period, compare it with two preset thresholds to determine the compression mode, and determine the compression mode marker code in the data frame header. S4. Read the change flag array and the change value corresponding to each data item, and check if there is a fault code. If there is, set the highest priority. If there is no fault code but there are data items whose change exceeds the emergency threshold, set the second highest priority in order of change size. S5. Verify the integrity of the received data frame through the instrument, extract the change flag array, perform corresponding decompression according to the compression mode mark, restore the values ​​of each changed data item, merge and output to the display interface and update the historical cache.

[0005] Preferably, step S1 specifically includes the following steps: S101. During the initial power-on initialization phase of the controller, its internal central processing unit loads a preset threshold parameter table from the electrically erasable read-only memory to the random access memory. After loading is completed, the controller locks the parameter table in a specified address range of the memory. S102. Read the battery voltage, battery current and throttle opening signal on the analog input channel, convert the analog voltage value into the corresponding digital physical quantity value, extract the pulse signal of the wheel speed sensor, convert it into the real-time vehicle speed value by the period method, read the motor temperature and controller temperature values ​​in the temperature sensor register through the single bus, count the currently active fault code code value in the internal fault status register, and store the seven data items collected into the current period data buffer in standard physical units. S103. Read the previous cycle values ​​of the seven data items sequentially from the historical data buffer. If the current period is the first communication cycle and the historical buffer is empty, copy the current value directly to the historical buffer, initialize all change flags to 1, force all data items to be sent, and proceed directly to the next step.

[0006] Preferably, step S1 further includes the following steps: S104. If the current period is not the first communication cycle, take the current cycle's first... Item value and the first historical cycle Item value Calculate the change ,in Once all data items have been calculated sequentially, they are stored in the change register group; S105. Read the change from the change register. At the same time, the corresponding judgment threshold is retrieved from the threshold parameter table. Perform a numerical comparison; if If the change is valid, it is considered a valid change; otherwise, it is considered an invalid change. After each data item is independently compared, an array of flag bits is generated based on the comparison results. The current period's data is copied to the historical buffer to overwrite the old value and used as the comparison benchmark for the next period. The array of flag bits is then output to the next step.

[0007] Preferably, step S2 specifically includes the following steps: S201. Read the seven-bit change flag array, scan the array bit by bit, and record the bit indices of all bits with a value of 1 and all bits with a value of 0. S202. Based on the scan results, retrieve all data items with a change flag bit of 1 from the current period data buffer, and put each data item into the ordered queue of changed data in a fixed order. Mark all data items with a change flag bit of 0 as unchanged data, and only record the name of the data item to which they belong. S203. Examine each data item in the ordered queue of changed data one by one. For each data item, determine the number of bytes occupied according to its data type. Add up the number of bytes of all changed data items to get the total byte length of the second data segment. If the changed data queue is empty, the total length of the second data segment is zero. S204. The controller extracts the seven change flag bits and fills them into an eight-bit binary byte according to the positional relationship of vehicle speed first and fault code last. The highest bit is reserved and filled with zero. This byte becomes the first data segment of the differentiated data frame. Its length is fixed at one byte and must be sent in every frame of data. S205. According to the order of the data items in the changing data queue, take out the current value of each data item in turn, convert the value into binary form, and write it into the buffer of the second data segment one by one according to the byte width occupied by each item. S206. The controller assembles each field in a forward-to-back order. After assembly, the data frame is stored in the transmission buffer and awaits transmission. When the receiving end receives the frame, it automatically uses the old value received in the previous cycle for all unchanged data items.

[0008] Preferably, step S3 specifically includes the following steps: S301. Record the total amount of data sent by all nodes on the bus in each statistical cycle. After the statistics are completed, divide the total amount of data by the duration of the statistical cycle and then by the physical transmission rate of the bus to obtain the real-time load rate, which is then transmitted to the central processing unit in the form of a percentage. S302. Read the first threshold and the second threshold from the internal non-volatile memory. The first threshold is less than the second threshold. Compare the real-time load rate with the two thresholds in turn. If it is less than the first threshold, it is determined to be in no compression mode and the differentiated data frame is directly sent into the transmission buffer. If it is greater than or equal to the first threshold and less than the second threshold, it is determined to start the first compression mode. If it is greater than or equal to the second threshold, it is determined to start the second compression mode. S303. When starting the first compression mode, examine each data item in the change data queue one by one, extract the maximum and minimum values ​​of the data item, calculate the effective value range, and use this range to determine the actual bit width.

[0009] Preferably, step S3 further includes the following steps: S304. Compare the actual bit width with the original bit width of the data item, adjust the values ​​corresponding to all data items, and then concatenate the binary values ​​in the original order to generate a compressed data segment and a compression parameter description field. Record the actual bit width of each changed data item and whether it has been reduced in order. S305. After processing by the first compression mode, each data item in the compressed data segment is further differentially encoded to complete the second compression mode. S306. Write a compression mode marker code into the header of the data frame. No compression is marked as 00, the first compression mode is marked as 01, and the second compression mode is marked as 10. Append the compression parameter description field before the compressed data segment and send it into the transmission buffer along with the mode marker.

[0010] Preferably, step S4 specifically includes the following steps: S401. Read the seven-bit change flag array from the register, and at the same time read the specific change value corresponding to each data item with a change flag of 1 from the change amount register group; S402. The controller checks whether the change flag bit corresponding to the fault code is 1. If it is 1, it immediately sets the priority field of the current data frame to the highest allowed priority value. This value has the highest preemption authority during bus arbitration. After setting, it jumps directly to the next step. S403. If the current frame does not contain a fault code, the controller checks each data item with the change flag bit set to 1 to see if any of the data items has a change exceeding the pre-stored emergency change threshold. The data item with the largest change among all data items that exceed the emergency threshold is marked as an emergency data item. S404. If an emergency data item is marked, the priority of its corresponding data frame is raised to the second highest level after the fault code. If multiple data items exist at the same time, they are arranged in order of priority from largest to smallest change, with the largest change having the highest priority and the rest decreasing in order, but all of them are higher than non-emergency data frames. S405. If the current frame has no fault code and no urgent data item, read the length of time the data frame has been waiting in the transmission queue and the cumulative number of times it has failed to participate in arbitration. Combine this with the preset importance weight of the data item to calculate the promotion offset. S406. Assemble the identifier in order from the most significant bit to the least significant bit, and then append it to the header of the data frame.

[0011] Preferably, step S5 specifically includes the following steps: S501: After continuously monitoring the bus through the instrument, it starts receiving data frames after detecting the frame header identifier. After receiving the data, it performs cyclic redundancy check calculation on all fields after the frame header except for the check byte. It compares the calculation result with the frame tail check byte. If they do not match, it discards the frame and waits for the next cycle of data. If they match, it enters the parsing process. S502. Extract the first data segment from a fixed position in the data frame, namely the seven change flag bits of one byte, and parse the value of each bit according to the pre-agreed bit mapping relationship. S503. Extract the compression parameter description field from the data frame, read the actual bit width, whether it has been reduced, and the compression mode type of each changed data item. If it is an uncompressed mode, directly read the original value of the second data segment. If it is a first compression mode, restore the reduced binary value of the corresponding position in the second data segment to the original physical quantity value according to the effective value range and actual bit width of each data item. If it is a second compression mode, after completing the bit width restoration, add the difference of differential encoding to the corresponding data item value saved in the previous cycle to obtain the actual value of the current cycle. S504. Extract the previous cycle running dataset from the local storage. For data items with a change flag of 0, directly use the value of the corresponding data item from the previous cycle. For data items with a change flag of 1, take out the restored current value from the decompressed second data segment in the order of arrangement and replace the old value of the corresponding data item in the local dataset. The unchanged data and the changed data are merged to form the complete running dataset of the current cycle. S505: Output all data items in the reconstructed dataset to the visualization interface, update the speedometer, battery indicator, temperature display and fault code area on the dashboard, and then store the dataset in the local historical cache, overwriting the data of the previous cycle, as the prediction benchmark for differential decoding in the next cycle.

[0012] Compared with the prior art, the beneficial effects of the present invention are: This invention detects changes cycle by cycle and only sends data when there is a valid change. Unchanged data is automatically reused by the receiving end from historical values, thus avoiding redundant transmission at the source. Combined with a two-level adaptive compression mechanism, it dynamically selects bit width reduction or differential encoding according to the bus busy level, thereby minimizing the amount of data transmitted while ensuring accuracy and effectively alleviating the risk of bus congestion. This invention utilizes dynamic priority scheduling to ensure that fault codes unconditionally receive the highest arbitration priority, guaranteeing that abnormal states are reported with the shortest delay. Data items with excessive urgent changes receive the second-highest priority, preventing critical information from being blocked. Non-urgent data frames are gradually promoted in priority through a waiting time promotion mechanism, fundamentally eliminating the hidden danger of long-term waiting for low-priority data. Attached Figure Description

[0013] Figure 1 An overall method flowchart is provided for embodiments of the present invention. Detailed Implementation

[0014] 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.

[0015] Example 1:

[0016] Please see Figure 1 This invention provides a technical solution: a method for collaborative communication between an electric vehicle controller and an instrument panel, comprising the following steps: S1. The controller collects seven operational data items in each statistical period, calculates the change amount for each item, compares each change amount with the corresponding preset threshold, sets the corresponding change flag to 1 when the change amount is greater than the threshold, otherwise sets it to 0, and generates a seven-bit change flag array for output. S2. Based on the change flag array, divide the data into a changed set and an unchanged set, construct a first data segment of fixed length to carry the flags, and construct a second data segment of variable length to carry only the current value of the changed data item; S3. Obtain the real-time bus load rate according to the total amount of data within the statistical period, compare it with two preset thresholds to determine the compression mode, and determine the compression mode marker code in the data frame header. S4. Read the change flag array and the change value corresponding to each data item, and check if there is a fault code. If there is, set the highest priority. If there is no fault code but there are data items whose change exceeds the emergency threshold, set the second highest priority in order of change size. S5. Verify the integrity of the received data frame through the instrument, extract the change flag array, perform corresponding decompression according to the compression mode mark, restore the values ​​of each changed data item, merge and output to the display interface and update the historical cache.

[0017] S1 specifically includes the following steps: S101. During the initial power-on initialization phase of the controller, its internal central processing unit loads a preset threshold parameter table from the electrically erasable read-only memory to the random access memory. The parameter table stores the corresponding judgment thresholds for seven data items, namely vehicle speed, throttle opening, battery current, battery voltage, motor temperature, controller temperature, and fault code. After loading, the controller locks the parameter table in the specified address range of memory. S102. Read the battery voltage, battery current and throttle opening signal on the analog input channel, convert the analog voltage value into the corresponding digital physical quantity value, extract the pulse signal of the wheel speed sensor, convert it into the real-time vehicle speed value by the period method, read the motor temperature and controller temperature values ​​in the temperature sensor register through the single bus, count the currently active fault code code value in the internal fault status register, and store the seven data items collected into the current period data buffer in standard physical units. S103. Read the previous cycle values ​​of seven data items sequentially from the historical data buffer. If the current period is the first communication cycle and the historical buffer is empty, copy the current value directly to the historical buffer, initialize all change flag bits in the array to 1, force all data items to be sent, and proceed directly to the next step. S1 also includes the following steps: S104. If the current period is not the first communication cycle, take the current cycle's first... Item value and the first historical cycle Item value Calculate the change ,in Once all data items have been calculated sequentially, they are stored in the change register group; S105. Read the change from the change register. At the same time, the corresponding judgment threshold is retrieved from the threshold parameter table. Perform a numerical comparison; if If the change is valid, it is considered a valid change; otherwise, it is considered an invalid change. After each data item is independently compared, an array of flag bits is generated based on the comparison results. The current period's data is copied to the historical buffer to overwrite the old value and used as the comparison benchmark for the next period. The array of flag bits is then output to the next step. S2 specifically includes the following steps: S201. Read the seven-bit change flag array. Each bit corresponds to seven data items: vehicle speed, throttle opening, battery current, battery voltage, motor temperature, controller temperature, and fault code. Scan the array in bit order and record the bit indices of all bits with a value of 1 and all bits with a value of 0. S202. Based on the scan results, retrieve all data items with a change flag bit of 1 from the current period data buffer, and put each data item into the ordered queue of changed data in a fixed order. Mark all data items with a change flag bit of 0 as unchanged data, and only record the name of the data item to which they belong. S203. Examine each data item in the ordered queue of changed data one by one. For each data item, determine the number of bytes occupied according to its data type. Add up the number of bytes of all changed data items to get the total byte length of the second data segment. If the changed data queue is empty, the total length of the second data segment is zero. S204. The controller extracts the seven change flag bits and fills them into an eight-bit binary byte according to the positional relationship of vehicle speed first and fault code last. The highest bit is reserved and filled with zero. This byte becomes the first data segment of the differentiated data frame. Its length is fixed at one byte and must be sent in every frame of data. S205. According to the order of data items in the changed data queue, take out the current value of each data item in turn, convert the value into binary form, and write it into the buffer of the second data segment one by one according to the byte width occupied by each item. The data items are arranged closely together without leaving any gaps in the middle. If the changed data queue is empty, the second data segment remains empty and no content is written into the buffer. The actual length of the second data segment changes dynamically with the number of changed data items. S206. The controller assembles each field in a forward-to-back order. First, a fixed frame header identifier is written, then a total length indicator byte is written. The value of this byte is equal to the fixed length of the first data segment plus the actual length of the second data segment. Next, the content of the first data segment is written, then the content of the second data segment is written, and finally a check byte is appended. After assembly, the data frame is stored in the transmission buffer to await transmission. All data items marked as unchanged are never written to the second data segment. After the receiving end receives the frame, it automatically uses the old value received in the previous cycle for all unchanged data items. S3 specifically includes the following steps: S301. Record the total amount of data sent by all nodes on the bus in each statistical cycle. After the statistics are completed, divide the total amount of data by the duration of the statistical cycle and then by the physical transmission rate of the bus to obtain the real-time load rate, which is then transmitted to the central processing unit in the form of a percentage. S302. Read the first threshold and the second threshold from the internal non-volatile memory. The first threshold is less than the second threshold. Compare the real-time load rate with the two thresholds in turn. If it is less than the first threshold, it is determined to be in no compression mode and the differentiated data frame is directly sent into the transmission buffer. If it is greater than or equal to the first threshold and less than the second threshold, it is determined to start the first compression mode. If it is greater than or equal to the second threshold, it is determined to start the second compression mode. S303. When starting the first compression mode, check each data item in the change data queue one by one, take out the maximum and minimum values ​​of the data item, calculate the effective value range, use the range to determine the actual bit width, the actual bit width is obtained by dividing the effective value range by the display precision, then take the logarithm of the number to the base two and round up to get the actual bit width. S3 also includes the following steps: S304. Compare the actual bit width with the original bit width of the data item. If it is less than the original bit width, reduce it and requantize the current value according to the precision, mapping it to the reduced bit width. If the actual bit width is greater than or equal to the original bit width, keep the original bit width unchanged. After adjusting the values ​​corresponding to all data items, concatenate the binary values ​​in the original order to generate a compressed data segment and a compression parameter description field. Record the actual bit width of each changed data item and whether it has been reduced in order. S305. After the first compression mode processing, each data item in the compressed data segment is further differentially encoded. The current cycle value is taken and the previous cycle value is subtracted. The difference is used to replace the current value itself and written into the compressed data segment. The bit width of the difference is predetermined based on the maximum possible change range of the data item in the adjacent cycle, thereby completing the second compression mode. S306. Write a compression mode flag code into the header of the data frame. No compression is recorded as 00, the first compression mode is recorded as 01, and the second compression mode is recorded as 10. Append the compression parameter description field before the compressed data segment and send it into the transmission buffer along with the mode flag. S4 specifically includes the following steps: S401. Read the seven-bit change flag array from the register, and at the same time read the specific change value corresponding to each data item with a change flag of 1 from the change amount register group; S402. The controller checks whether the change flag bit corresponding to the fault code is 1. If it is 1, it immediately sets the priority field of the current data frame to the highest allowed priority value. This value has the highest preemption authority during bus arbitration. After setting, it jumps directly to the next step. S403. If the current frame does not contain a fault code, the controller checks one by one the data items with the change flag bit set to 1 to see if any of the data items has a change amount that exceeds the pre-stored emergency change threshold. This threshold is set during the calibration phase. The data item with the largest change amount among all data items that exceed the emergency threshold is marked as an emergency data item. S404. If an emergency data item is marked, the priority of its corresponding data frame is raised to the second highest level after the fault code. If multiple data items exist at the same time, they are arranged in order of priority from largest to smallest change, with the largest change having the highest priority and the rest decreasing in order, but all of them are higher than non-emergency data frames. S405. If the current frame has no fault code and no urgent data item, read the length of time the data frame has been waiting in the transmission queue and the cumulative number of times it has failed to participate in arbitration. Combine the preset importance weight of the data item to calculate the promotion offset. The longer the waiting time, the more failures, and the higher the weight, the larger the offset. Add it to the base priority so that the actual priority gradually increases with the waiting time. S406. Assemble the identifier in order from high bit to low bit. Fill the highest bit field with the dynamic priority value, followed by a two-bit change identifier field, filled with the corresponding code (all unchanged becomes zero zero, some changes become zero one, all changes become one one), then a two-bit reduction identifier field, filled with the mark according to the compression mode (no compression zero zero, first mode zero one, second mode one zero), and the lowest bit field is filled with the fixed identification code of the controller node. After assembly, it is appended to the header of the data frame. S5 specifically includes the following steps: S501: After continuously monitoring the bus through the instrument, it starts receiving data frames after detecting the frame header identifier. After receiving the data, it performs cyclic redundancy check calculation on all fields after the frame header except for the check byte. It compares the calculation result with the frame tail check byte. If they do not match, it discards the frame and waits for the next cycle of data. If they match, it enters the parsing process. S502. Extract the first data segment from a fixed position in the data frame, namely the seven-bit change flag of one byte. Analyze the value of each bit according to the pre-agreed bit mapping relationship to determine whether the vehicle speed, throttle opening, battery current, battery voltage, motor temperature, controller temperature, and fault code have changed effectively in the current frame. S503. Extract the compression parameter description field from the data frame, read the actual bit width, whether it has been reduced, and the compression mode type of each changed data item. If it is an uncompressed mode, directly read the original value of the second data segment. If it is a first compression mode, restore the reduced binary value of the corresponding position in the second data segment to the original physical quantity value according to the effective value range and actual bit width of each data item. If it is a second compression mode, after completing the bit width restoration, add the difference of differential encoding to the corresponding data item value saved in the previous cycle to obtain the actual value of the current cycle. S504. Extract the previous cycle running dataset from the local storage. For data items with a change flag of 0, directly use the value of the corresponding data item from the previous cycle. For data items with a change flag of 1, take out the restored current value from the decompressed second data segment in the order of arrangement and replace the old value of the corresponding data item in the local dataset. The unchanged data and the changed data are merged to form the complete running dataset of the current cycle. S505: Output all data items in the reconstructed dataset to the visualization interface, update the speedometer, battery indicator, temperature display and fault code area on the dashboard, and then store the dataset in the local historical cache, overwriting the data of the previous cycle, as the prediction benchmark for differential decoding in the next cycle.

[0018] 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 process, method, article, or apparatus.

[0019] 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 method for collaborative communication between an electric vehicle controller and an instrument panel, characterized in that, The method includes the following steps: S1. The controller collects seven operational data items in each statistical period, calculates the change amount for each item, compares each change amount with the corresponding preset threshold, sets the corresponding change flag to 1 when the change amount is greater than the threshold, otherwise sets it to 0, and generates a seven-bit change flag array for output. S2. Based on the change flag array, divide the data into a changed set and an unchanged set, construct a first data segment of fixed length to carry the flags, and construct a second data segment of variable length to carry only the current value of the changed data item; S3. Obtain the real-time bus load rate according to the total amount of data within the statistical period, compare it with two preset thresholds to determine the compression mode, and determine the compression mode marker code in the data frame header. S4. Read the change flag array and the change value corresponding to each data item, and check if there is a fault code. If there is, set the highest priority. If there is no fault code but there are data items whose change exceeds the emergency threshold, set the second highest priority in order of change size. S5. Verify the integrity of the received data frame through the instrument, extract the change flag array, perform corresponding decompression according to the compression mode mark, restore the values ​​of each changed data item, merge and output to the display interface and update the historical cache.

2. The method for collaborative communication between an electric vehicle controller and an instrument panel according to claim 1, characterized in that, S1 specifically includes the following steps: S101. During the initial power-on initialization phase of the controller, its internal central processing unit loads a preset threshold parameter table from the electrically erasable read-only memory to the random access memory. After loading is completed, the controller locks the parameter table in a specified address range of the memory. S102. Read the battery voltage, battery current and throttle opening signal on the analog input channel, convert the analog voltage value into the corresponding digital physical quantity value, extract the pulse signal of the wheel speed sensor, convert it into the real-time vehicle speed value by the period method, read the motor temperature and controller temperature values ​​in the temperature sensor register through the single bus, count the currently active fault code code value in the internal fault status register, and store the seven data items collected into the current period data buffer in standard physical units. S103. Read the previous cycle values ​​of the seven data items sequentially from the historical data buffer. If the current period is the first communication cycle and the historical buffer is empty, copy the current value directly to the historical buffer, initialize all change flags to 1, force all data items to be sent, and proceed directly to the next step.

3. The method for collaborative communication between an electric vehicle controller and an instrument panel according to claim 2, characterized in that, S1 further includes the following steps: S104. If the current period is not the first communication cycle, take the current cycle's first... Item value and the first historical cycle Item value Calculate the change ,in Once all data items have been calculated sequentially, they are stored in the change register group; S105. Read the change from the change register. At the same time, the corresponding judgment threshold is retrieved from the threshold parameter table. Perform a numerical comparison; if If the change is valid, it is considered a valid change; otherwise, it is considered an invalid change. After each data item is independently compared, an array of flag bits is generated based on the comparison results. The current period's data is copied to the historical buffer to overwrite the old value and used as the comparison benchmark for the next period. The array of flag bits is then output to the next step.

4. The method for collaborative communication between an electric vehicle controller and an instrument panel according to claim 1, characterized in that, S2 specifically includes the following steps: S201. Read the seven-bit change flag array, scan the array bit by bit, and record the bit indices of all bits with a value of 1 and all bits with a value of 0. S202. Based on the scan results, retrieve all data items with a change flag bit of 1 from the current period data buffer, and put each data item into the ordered queue of changed data in a fixed order. Mark all data items with a change flag bit of 0 as unchanged data, and only record the name of the data item to which they belong. S203. Examine each data item in the ordered queue of changed data one by one. For each data item, determine the number of bytes occupied according to its data type. Add up the number of bytes of all changed data items to get the total byte length of the second data segment. If the changed data queue is empty, the total length of the second data segment is zero. S204. The controller extracts the seven change flag bits and fills them into an eight-bit binary byte according to the positional relationship of vehicle speed first and fault code last. The highest bit is reserved and filled with zero. This byte becomes the first data segment of the differentiated data frame. Its length is fixed at one byte and must be sent in every frame of data. S205. According to the order of the data items in the changing data queue, take out the current value of each data item in turn, convert the value into binary form, and write it into the buffer of the second data segment one by one according to the byte width occupied by each item. S206. The controller assembles each field in a forward-to-back order. After assembly, the data frame is stored in the transmission buffer and awaits transmission. When the receiving end receives the frame, it automatically uses the old value received in the previous cycle for all unchanged data items.

5. The method for collaborative communication between an electric vehicle controller and an instrument panel according to claim 1, characterized in that, S3 specifically includes the following steps: S301. Record the total amount of data sent by all nodes on the bus in each statistical cycle. After the statistics are completed, divide the total amount of data by the duration of the statistical cycle and then by the physical transmission rate of the bus to obtain the real-time load rate, which is then transmitted to the central processing unit in the form of a percentage. S302. Read the first threshold and the second threshold from the internal non-volatile memory. The first threshold is less than the second threshold. Compare the real-time load rate with the two thresholds in turn. If it is less than the first threshold, it is determined to be in no compression mode and the differentiated data frame is directly sent into the transmission buffer. If it is greater than or equal to the first threshold and less than the second threshold, it is determined to start the first compression mode. If it is greater than or equal to the second threshold, it is determined to start the second compression mode. S303. When starting the first compression mode, examine each data item in the change data queue one by one, extract the maximum and minimum values ​​of the data item, calculate the effective value range, and use this range to determine the actual bit width.

6. The method for collaborative communication between an electric vehicle controller and an instrument panel according to claim 5, characterized in that, S3 specifically includes the following steps: S304. Compare the actual bit width with the original bit width of the data item, adjust the values ​​corresponding to all data items, and then concatenate the binary values ​​in the original order to generate a compressed data segment and a compression parameter description field. Record the actual bit width of each changed data item and whether it has been reduced in order. S305. After processing by the first compression mode, each data item in the compressed data segment is further differentially encoded to complete the second compression mode. S306. Write a compression mode marker code into the header of the data frame. No compression is marked as 00, the first compression mode is marked as 01, and the second compression mode is marked as 10. Append the compression parameter description field before the compressed data segment and send it into the transmission buffer along with the mode marker.

7. The method for collaborative communication between an electric vehicle controller and an instrument panel according to claim 1, characterized in that, S4 specifically includes the following steps: S401. Read the seven-bit change flag array from the register, and at the same time read the specific change value corresponding to each data item with a change flag of 1 from the change amount register group; S402. The controller checks whether the change flag bit corresponding to the fault code is 1. If it is 1, it immediately sets the priority field of the current data frame to the highest allowed priority value. This value has the highest preemption authority during bus arbitration. After setting, it jumps directly to the next step. S403. If the current frame does not contain a fault code, the controller checks each data item with the change flag bit set to 1 to see if any of the data items has a change exceeding the pre-stored emergency change threshold. The data item with the largest change among all data items that exceed the emergency threshold is marked as an emergency data item. S404. If an emergency data item is marked, the priority of its corresponding data frame is raised to the second highest level after the fault code. If multiple data items exist at the same time, they are arranged in order of priority from largest to smallest change, with the largest change having the highest priority and the rest decreasing in order, but all of them are higher than non-emergency data frames. S405. If the current frame has no fault code and no urgent data item, read the length of time the data frame has been waiting in the transmission queue and the cumulative number of times it has failed to participate in arbitration. Combine this with the preset importance weight of the data item to calculate the promotion offset. S406. Assemble the identifier in order from the most significant bit to the least significant bit, and then append it to the header of the data frame.

8. The method for collaborative communication between an electric vehicle controller and an instrument panel according to claim 1, characterized in that, S5 specifically includes the following steps: S501: After continuously monitoring the bus through the instrument, it starts receiving data frames after detecting the frame header identifier. After receiving the data, it performs cyclic redundancy check calculation on all fields after the frame header except for the check byte. It compares the calculation result with the frame tail check byte. If they do not match, it discards the frame and waits for the next cycle of data. If they match, it enters the parsing process. S502. Extract the first data segment from a fixed position in the data frame, namely the seven change flag bits of one byte, and parse the value of each bit according to the pre-agreed bit mapping relationship. S503. Extract the compression parameter description field from the data frame, read the actual bit width, whether it has been reduced, and the compression mode type of each changed data item. If it is an uncompressed mode, directly read the original value of the second data segment. If it is a first compression mode, restore the reduced binary value of the corresponding position in the second data segment to the original physical quantity value according to the effective value range and actual bit width of each data item. If it is a second compression mode, after completing the bit width restoration, add the difference of differential encoding to the corresponding data item value saved in the previous cycle to obtain the actual value of the current cycle. S504. Extract the previous cycle running dataset from the local storage. For data items with a change flag of 0, directly use the value of the corresponding data item from the previous cycle. For data items with a change flag of 1, take out the restored current value from the decompressed second data segment in the order of arrangement and replace the old value of the corresponding data item in the local dataset. The unchanged data and the changed data are merged to form the complete running dataset of the current cycle. S505: Output all data items in the reconstructed dataset to the visualization interface, update the speedometer, battery indicator, temperature display and fault code area on the dashboard, and then store the dataset in the local historical cache, overwriting the data of the previous cycle, as the prediction benchmark for differential decoding in the next cycle.