Communication method, corresponding system, device, signal, and vehicle

JP2024120049A5Inactive Publication Date: 2025-05-01STMICROELECTRONICS APPL GMBH +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2024099746
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2018-03-26
Filing Date
2024-06-20
Publication Date
2025-05-01
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

Existing vehicle communication systems face challenges in achieving high data rates, robustness, and safety while maintaining cost-effectiveness, particularly in decentralized LED lighting systems, which are complex and costly due to the use of single-chip analog/bipolar Application Specific Integrated Circuits (AS IC) and application specific standard product (ASSP) controllers.

Method used

A communication system utilizing a CAN FD (Controller Area Network Flexible Data rate) protocol with a master-slave architecture, incorporating differential bus wiring, cyclic redundancy check (CRC), and error checking, along with a master device and slave devices connected via a communication bus, ensuring robust data transfer and safety features.

Benefits of technology

The system provides a cost-effective, high data rate communication network suitable for vehicle lighting systems, ensuring robustness and safety through differential bus wiring, CRC, and error checking, while maintaining compatibility with standard CAN FD networks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

To provide a method, a system, and a device that facilitate the implementation or the like of a high data rate vehicle network.SOLUTION: In a vehicle V, a first device 10 and a set of second devices 20 are coupled via a bus 30. A method includes: transmitting first message representing actions for execution by the set of second devices and a second message that conveys identifiers identifying the second devices that will request their respective responses to the first device within expected response periods; receiving the first message sent from the first device to the second devices on the bus; reading respective action data message portions of a set of action data message portions; performing respective actions as functions of the read respective action data message portions; receiving the second message sent from the first device; and causing the response message to be sent to the first device, thereby causing responses to be made with respect to the second message within their respective expected response periods.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to bus-supported communications, e.g. for use in automotive applications. It is something.

[0002] For example, one or more embodiments may include a lighting system for a vehicle (e.g., front lights, rear lights, etc.). , interior lights) and the corresponding lighting module (e.g. For example, it can be applied to communication between a device such as a smartphone or an LED light module. [Background technology]

[0003] Various applications, for example in the automotive sector, are carried out on one or more bus networks. It involves the exchange of data over a wide area. It has high data rates, robustness, defect detection, safety, and low cost. This is a desirable feature for such applications.

[0004] Existing standardized vehicle communication systems with high data rates (e.g., 1 Mb / s) These may involve complex and precise protocol controllers using expensive components. In particular, single chip analog / bipolar application specific integrated circuits (AS This is the case when the technology is implemented as an integrated circuit (IC) and / or an application specific standard product (ASSP).

[0005] Vehicle lights (e.g., front lights, rear lights, interior lights) are becoming increasingly sophisticated and It is becoming more and more distributed (e.g., matrix LED, ambient LED). Controlling sophisticated and distributed systems involves high data rate control. In addition, automotive lighting, especially for front and rear lighting systems, Dual-grade safety and robustness are desirable.

[0006] The LED driver is a single-chip, e.g., bipolar-CMOS-DMOS (BCD) technology. If chip technology is used, it may be cost effective. If not, e.g. For example, high data rate protocol controllers using BCD technology are expensive and require high accuracy. It depends on the clock source (crystal).

[0007] Employ differential wiring for clock and data signals to facilitate robustness It is possible, but this may increase the wire "harness" costs.

[0008] Therefore, in vehicles, for example, to drive distributed lighting sources such as LED matrices, The increasing complexity of communication networks can lead to increased production costs; This may be incompatible with most business models in the automotive industry. .

[0009] One or more embodiments may include, for example, a CAN (Controller Area Network) bus. This is applicable to vehicles without a host computer. Known techniques can facilitate communication between a device and, for example, a microcontroller. The operation of the CAN bus is determined by, for example, ISO11898-2:2015 and ISO1 In the message, as handled in standards such as 1898-2:2016, It is possible that the protocol is based on the [Prior art documents] [Non-patent literature]

[0010] [Non-Patent Document 1] ISO11898-2:2015 and ISO11898-2:2016 Summary of the Invention [Problem to be solved by the invention]

[0011] Despite the extensive activity in this field, further improved solutions are desired.

[0012] For example, distributed LEDs that meet automotive requirements in terms of robustness, defect detection and safety. Enabling cost-effective, high data rate vehicle networks for driving light sources, etc. A solution that can facilitate this is desirable. Similar solutions are also available, for example, Implementation of high data rate networks for implementation in production automation systems, etc. In some cases, it may be possible to facilitate the realization of [Means for solving the problem]

[0013] One object of one or more embodiments is to provide such an improved solution. The aim of this project is to contribute to the development of

[0014] According to one or more embodiments, such an object is achieved as set forth in the following claims. This can be achieved by a method having the following features.

[0015] One or more embodiments may relate to a corresponding system.

[0016] One or more embodiments may include, for example, a transmitter and a receiver that are intended to operate together. The term may refer to a corresponding device such as a transmitter (interface).

[0017] One or more embodiments may be associated with a corresponding signal.

[0018] One or more embodiments may relate to a corresponding vehicle, such as a motor vehicle, e.g., an automobile. There is a match.

[0019] The claims are an integral part of the technical teachings provided herein in connection with the embodiments. do.

[0020] One or more embodiments may include, for example, an electronic control unit (ECU) and an LED light module. Suitable for implementing a communication network for communication between lighting modules such as lighting fixtures It is possible to provide a suitable hardware solution.

[0021] One or more embodiments are directed to a master station that can be used in automotive applications. It is possible to implement a Reeve communication bus interface.

[0022] Such a communication bus interface for use in automotive applications is It is a standardized standard for driving light modules ("CAN FD Light") in It is possible to rely on the CAN FD (Flexible Data Rate) protocol.

[0023] One or more embodiments may be used in non-automotive applications, such as automation systems. Standardized for use in networks that rely on network technologies other than CAN FD networks It is possible.

[0024] For example, one or more embodiments may use differential bus wiring and Defined edge density for measurement purposes (e.g., one reset for every 10 bits) It is possible to provide a gradual transition from a dominant to a positive edge.

[0025] One or more embodiments may use cyclic redundancy checks (CRCs) and error correction for security reasons. It is possible to carry out a check.

[0026] In one or more embodiments, the data exchange relies on a master-slave scheme. In this case, the slave "satellite" receives the Send data via the communication bus only upon request. Such an operating scheme is If normal operation is intended to avoid collisions, then a collision is treated as an error. In some cases, the conflict resolution feature that deals with conflicts may not be involved.

[0027] In one or more embodiments, normal operation of the communication bus involves a master transmitting a signal to a slave (defined as Such data transmissions may involve the transmission of (periodic) data. The system is controlled by slaves as a kind of network "heartbeat" or watchdog. It can be used to receive periodic data streams within a defined time slot. If no signal is received, the slave goes into fail-safe (or limp-home) mode. It is possible to enter.

[0028] In one or more embodiments, data, such as diagnostic data, from a slave may be received, e.g., It can be requested by the master using a dedicated command frame. An addressed slave is expected to respond to such a request within a certain time frame. Such a response can be used by the master to detect the availability of a slave. It is possible to use. [Brief description of the drawings]

[0029] [Figure 1] Schematic diagram of a possible implementation of an embodiment. [Diagram 2] Schematic diagram of a possible implementation of a master device in an embodiment. [Diagram 3] Schematic diagram of a possible implementation of a slave device in an embodiment. [Figure 4] 4 is an exemplary schematic diagram of a possible operation of an embodiment; [Diagram 5] 13 is an exemplary block diagram of a possible operation of an embodiment for managing "broadcast" frames. [Figure 6] FIG. 13 is an exemplary block diagram of a possible operation of an embodiment for managing “diagnostic” frames. [Figure 7] FIG. 13 is an exemplary block diagram of a possible operation of an embodiment for managing "error" frames. [Figure 8] 4 is an exemplary block diagram of a possible implementation of a master communication cycle in an embodiment. [Figure 9] 4 is an exemplary block diagram of a possible implementation of a slave communication cycle in an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0030] In the following description, a number of examples are provided for the purpose of providing a thorough understanding of the illustrative embodiments of the present description. One or more specific details are illustrated. An embodiment may include one or more of the specific details. It is possible to implement the present invention without the above or with other methods, components, materials, etc. In other cases, known structures, materials, and / or methods may be used to avoid obscuring certain aspects of the embodiments. Or operations are not illustrated or described in detail.

[0031] In the context of this description, references to "one embodiment" or "one embodiment" refer to the embodiment. A particular feature, structure, or characteristic described in connection with an embodiment may be present in at least one embodiment. It is intended to represent that one or more of the above-described In some cases, "in one embodiment" or "in one embodiment" may be used. The phrase "in the present invention" does not necessarily refer to one and the same embodiment. The forms, structures, or characteristics of may be combined in any suitable manner in one or more embodiments. It is possible to do so.

[0032] The references used in this document are provided merely for convenience and do not represent any representation in respect of the scope of protection or It does not define the scope of the examples.

[0033] As noted, one or more embodiments may be used in automotive applications. The intention is to provide a "robust" master-slave bus interface that can There is a match.

[0034] One or more embodiments may utilize a standardized CAN FD physical interface. and may depend on the protocol and provide a certain edge density for synchronization purposes. It is possible to use differential bus wiring while still providing

[0035] One or more embodiments may use cyclic redundancy checks (CRCs) and error correction for security compliance. It is possible to implement a check.

[0036] The drawing in FIG. 1 is an exemplary schematic diagram of a configuration in which a first device 10 is mounted, for example, on a vehicle V. A set of second devices 201, 202,...,20 n , and are connected via bus 30 For example, bus 30 may be a differential bus. 1 is an example of one possible differential bus.

[0037] In such a configuration as illustrated in FIG. 1, a first device 10 receives a set of operational data messages. A "first" message carrying a message portion is transmitted on the bus 30, and the second device of the set 201,202,...,20 n Each second device in the Each action is identified by identifying the respective action data message portion that is addressed to them. Respond to them by performing

[0038] As illustrated in FIG. 1, one or more embodiments may include, for example, an LED cluster (e.g., Applying the technology to a local communication bus network to drive multiple devices (e.g., lights on a vehicle) Such a bus network is compatible with standard CAN FD networks. If there are CAN FD Lite networks, they are referred to in this document as "CAN FD Lite" networks. It will be forced.

[0039] Otherwise, reference to such possible applications is for illustrative purposes only. The present invention is intended to be illustrative and not to be construed as limiting the scope of the invention (even if indirectly). It is understood that

[0040] For example, a communication system such as that illustrated in FIG. and / or may also be suitable for use with drivers for interior or room lights.

[0041] As long as they can rely on a master-slave architecture, any of them for use with other types of ECUs and drivers (not necessarily in the vehicle) A similar communication system may be suitable for this purpose.

[0042] FIG. 1 shows a master device 10, e.g., for an LED cluster in the rear lights of a vehicle. 1 is an example of a system according to an embodiment having an electronic control unit (ECU).

[0043] Again, it is emphasized that reference to such possible applications is for illustrative purposes only. and should not be construed as limiting the embodiments, even indirectly. ).

[0044] One or more embodiments may include multiple "satellite" or slave devices 201, 202, 203, 204, 205, 206, 207, 208, 209, 210, 211, 212, 213, 214, 215, 216, 217, 218, 219, 220, 221, 222, 2,...,20 n , for example, a (linear) L An ED drive circuit may be included.

[0045] In one or more embodiments, the master device 10 and the slave devices 201, 202 ,...,20 n Both are powered by a power source 40, e.g., a battery provided on the vehicle. It is possible to have the following supplied.

[0046] In one or more embodiments, the master device 10 and the slave devices 201, 20 2,...,20 n can be referenced to different grounds.

[0047] A master device 10 as illustrated in FIG. 1 comprises the following components: - a main (e.g. "buck") converter 101; an optional (e.g., again "back") converter 102, -Low Dropout (LDO) Linear Voltage Regulator, Standby, Reset and and a window and watchdog circuit block 103; Voltage Supervisor, Power Good, Oscillator and Enable circuit block 104; - Microcontroller 106, A transceiver for communicating with other ECUs that may be installed in the vehicle. a transceiver circuit 105 (e.g., a LIN2.2 / HS-CAN transceiver); and - to a transceiver 105 for communicating with other ECUs located within the vehicle an access point for the connected external communication bus 107; It is possible for the device to have one or more of the following:

[0048] In one or more embodiments, the microcontroller 106 controls the main converter. 101 and / or from an optional converter 102. The microcontroller 106 is coupled to the circuit block 103 and to the transceiver 105. and adapted for communication and / or collaboration with the communication bus 30. It is possible.

[0049] Except for the aspects described below, such an architecture for the master device 10 This is prior art and therefore it is unnecessary to provide a more detailed description here. is doing.

[0050] In one or more embodiments, the "master" functionality of device 10 is implemented by a microcontroller. embedded within the controller 106 and a CAN FD transceiver (not shown in FIG. 1). This can be achieved using a protocol controller.

[0051] For example, in one or more embodiments as illustrated herein, The microcontroller 10 is a microcontroller (μC) that handles bus communication. The controller can handle the CAN FD protocol without any software intervention It is possible to use an embedded CAN FD protocol controller. This may occupy resources of the microcontroller core and may be undesirably slow. This is a preferable option compared to running different controllers via SW, which may be required. Accordingly, one or more embodiments may be implemented to transmit CAN FD messages. By transmitting and controlling their content through software, existing hardware processors can be This makes it easier to reuse protocol controllers.

[0052] In one or more embodiments, the slave device 20 may include an LED that uses BCD technology. It is possible to implement it as a driver.

[0053] In one or more embodiments, data exchange on the communication bus 30 is master-slave It is possible to rely on a scheme, in which case slaves 201, 202, ..., 20 n When a request is received from the master device 10, the data is transmitted via the communication bus 30 (only). It is possible to transmit.

[0054] As noted, in one or more embodiments, Such an operating scheme may be intended to avoid collisions in normal operation. If the collision resolution feature is not involved, it can be handled as an error. There are Normal operation of the communication bus 30 is as follows: the master 10 communicates with the slaves 201, 202, ..., 20 n The data is sent periodically (i.e. at defined time intervals) to (Slaves 201, 202, ..., 20 n It involves receiving Such a periodic data stream may be transmitted by the slave to the network. This periodic data can be used as a "heartbeat" or watchdog. As a result of a data stream not being received within a defined time slot, the stream The server can enter a fail-safe (or limp-home) mode.

[0055] In one or more embodiments, the slaves 201, 202,..., 20 n From Data, such as diagnostic data, may be transmitted, for example, by the master 10 on the bus 30 in a "second" memory. A command frame such as the START command is requested by the master 10. There may be cases where a certain (one) addressed slave 20 i It is possible for , for example, to be able to respond to requests issued by the master within a certain time frame. Through such a bus network 30, the slaves 20 i Response sent by Slave 20 i by the master 10 to detect the availability and / or correct operation of It is possible to use it like this.

[0056] It is understood that: - The first message discussed here is basically the same as the message in e.g. the CAN bus protocol. Broadcast messages traditionally sent in message-based protocols The CAN bus protocol allows one device to communicate on the bus. A message sent to the other device is received by the other device simultaneously. Devices receiving these messages will receive the information conveyed by such broadcast messages. each of the actions can be performed as a function of the portion of the action data that is - A so-called "physically" broadcast on the bus by one (master) device On the other hand, the second message is actually basically a request message sent to other (slave) Each slave device is "logically" addressed to an individual slave device, e.g. Each response, for example a diagnostic message, is directed to the master device within a certain time interval. Each slave device is required to respond by transmitting The possibility of such a response is possible as long as each of the non-collision response intervals (periods) is assigned to each Such collisions will be avoided.

[0057] It should further be noted that in the framework of this description, the terms "frame" and "message" are used interchangeably. Both terms, “message” and “message” are used to denote messages exchanged between participants on the communication bus 30. It may be used.

[0058] In one or more embodiments, the communication protocol includes bit rate switching. It is possible to use CAN FD format frames (only) without and with standard ID. It is possible.

[0059] Extensions such as support for extended IDs, classic CAN frames or bit rate switches It is possible to include optional coding, if supported by the implementation. Frames that are not intended to change these modes of operation can be ignored. The bits that are set are maintained at their fixed value.

[0060] FIG. 2 is an exemplary block diagram of a possible implementation of a master device 10 according to some embodiments. be.

[0061] Throughout the figures accompanying this document, like parts or elements are represented with like references / numbers, And the corresponding descriptions will not be repeated for the sake of brevity.

[0062] Thus, FIG. 2 shows a master device 10, which is - an access point to a communication bus 30, e.g. a CAN bus, an access point to the second communication bus 107; a transceiver circuit 105 for cooperation with a communication bus 107; - a transceiver circuit, such as a CAN FD transceiver, for cooperation with the communication bus 30 Road 108, -Communication protocols (HW and / or SW) such as CAN FD protocol controllers Communication with the Corcontroller 1062, e.g. with the "CAN FD Lite" protocol extension Protocol extensions (e.g., SW) 1061 and possibly other circuit blocks 1 063, and a microcontroller 106 including It is possible to provide the following.

[0063] In one or more embodiments, a CAN FD label may be used as illustrated herein. Additional CAN FD protocol extensions 10 are required to realize the master side of the CAN FD protocol. 61 can control the CAN FD protocol controller 1062.

[0064] In one or more embodiments, access to the physical interface of bus 30 is otherwise given by using a conventional CAN FD transceiver 108 It is possible.

[0065] FIG. 3 illustrates a slave device 20 according to some embodiments. i Example blocks of possible implementations of FIG.

[0066] As illustrated in FIG. i teeth, -Communication and protocol controllers such as "CAN FD Light" Col controller circuit 201, memory area 202, a transceiver 2, such as a CAN FD transceiver, for cooperation with a communication bus 30; 03, and - possibly further ECU circuit blocks 204, It is possible to provide the following.

[0067] Except for the aspects described below, the slave device 20 i About this kind of architecture The technique is prior art and therefore it is not necessary to provide a more detailed description here. .

[0068] For example, in one or more embodiments, the communications and protocol controller circuit 2 The 01 implementation reduces the need for embedded processors to run the software. It is possible to rely on application specific hardware for this purpose.

[0069] In one or more embodiments, the communication and protocol controller circuit 201 includes: A precision oscillator (not shown in Figure 3) is used to generate and sample the data bits. The device may have a casing (shown in the figure).

[0070] FIG. 4 shows the communication and 2 is a schematic diagram illustrating a possible operation of the protocol controller circuit 201. FIG.

[0071] The communication and protocol controller 201 as illustrated in FIG. -Communication Controller 2010, - a transmitter circuit 2012, a transmission error counter (TEC) circuit 2013, and a receiver circuit 2014 and a receive error counter (REC) circuit 2015. -La 2011, and -Optional voltage, process and temperature compensated and / or correspondingly trimmed optocouplers Silent 2016, It has.

[0072] In one or more embodiments, the transmitter circuit 2012 and / or the receiver circuit 20 14 includes a transceiver, such as a CAN FD transceiver, for communication on the bus 30. It is possible to configure the system to cooperate with server 203.

[0073] In one or more embodiments, the transmitter circuit 2012 includes a frame prepare (2012 a), Bit stuffing (2012b), CRC insertion (2012c), Frame error Checking (2012d), Error Counting (2012e), and Acknowledgement ( 2012f) can be implemented.

[0074] In one or more embodiments, the receiver circuit 2014 performs bit decoding ( Sampling (2014a), Error Detection (2014b), Bit Destuffing (2 014c), CRC verification (2014d), and acknowledgment generation (2014e). It is possible to configure the above.

[0075] In one or more embodiments, the communications controller 2010 may include a In order to do so, each of them transmits data to the protocol controller 2011, and the protocol controller 2011.

[0076] In one or more embodiments, the CAN FD based communication bus 30 Applying a master-slave architecture allows you to take advantage of the advantages of the CAN FD protocol (e.g. For example, you can enjoy high data rates, robust differential signaling, and CRC for safety purposes. It also provides the possibility of achieving high accuracy in clocks for multilateral communication. Timing (e.g. arbitration, error signal handling, frame checking by all ECUs) The need for a central master for communication, high complexity, and lack of a guaranteed communication speed due to the absence of a central master. This eliminates shortcomings such as the absence of lots.

[0077] In one or more embodiments as illustrated herein, a high bandwidth (e.g., 50 0 kb / s, preferably 1 Mb / s) and the communication is ASIL B (Automotive Safety Integrity Level B) It is possible to involve checks against safety conditions. For example, the fulfillment of such a safety condition may be achieved by the This can be facilitated by a CRC value.

[0078] In one or more embodiments as illustrated herein, for example, a master on bus 30 10 and the result of receiving a data frame such as the "first" message transmitted by Then, the receiver (slave 201, 202, ..., 20 n ) is "acknowledge dge) bit, so that if the system is working correctly, it will send at least one The acknowledge bit is received by the sender (master 10).

[0079] Therefore, slaves 201, 202, ..., 20 n At least one acknowledgement from As a result of receiving the bit, the master 10 determines that it is still connected to the bus network 30. It is possible to detect that the participants of the bus network 30 are the same. Because it is connected to a wire, the transmitter can detect if it is not working properly. and thus can be in a "passive" state so as not to disturb bus communication. It is possible to enter.

[0080] In one or more embodiments, a passive (e.g., recessive) Participants of the bus network 30 in the However, there are cases where it is not possible to drive the bus, i.e., to force a certain value of the bus differential voltage. There are cases where it is not possible to do so.

[0081] In one or more embodiments, data sampling is performed individually in multiple receiver circuits. It is possible to generate a ring clock so that the minimum edges of the data stream Density is beneficial, e.g., at least every 10th bit recessive to dominant. This allows for easy synchronization of the receiver circuitry to the data stream. This will make it easier.

[0082] In one or more embodiments, the differential bus network provides a low-cost, "robust" In one or more embodiments, the web on the network facilitates data transfer. It is also possible to achieve orgasm, and slaves 201, 202, ..., 20 n The wake-up pattern (W UP) to filter time T filter (Short) to use the way It is possible to back up the data.

[0083] Thus, one or more embodiments may be implemented with a 1 Mb / s bandwidth of 10 Mbps for compatibility reasons. It allows the use of traditional CAN FD protocol without the need for bit rate switching. Therefore, only a subset of the traditional CAN FD protocol features (bits per second) are available. (without implementing the standard switching feature) (otherwise conventional CAN FD protocol) It is possible to explore the compatibility by running

[0084] A communication network as described herein may conceptually include any CAN and / or CAN Suitable for use with the FD protocol "flavors".

[0085] For example, in one or more of the embodiments illustrated herein, -For example, to increase the data payload of each frame (e.g. up to 64 bytes), allowing the use of the CAN FD base frame without the need to resort to extended IDs. It is possible to use the file format (FBFF) (only), - The bits in the control field are fixed and the Extended ID (EID, IDE bits are always dominant), bit rate switch (BRS, always dominant) and error status indication (E One frame format (SI, always dominant) without the need to support It is possible to support (only) FBFF, e.g. FD frame (FDF) It can be set to recessive (statically).

[0086] In one or more embodiments, one (and only one) frame format, e.g., C Supporting the AN FD base frame format is an even easier implementation. This may reduce costs and may facilitate cost reduction.

[0087] The data field in the CAN FD base frame format is a maximum of 64 bytes. Depending on the number of data bytes, it can be CRC17 or CRC2. In one or more embodiments, one ( It is possible to send and accept CRC delimiter bits of only one byte.

[0088] In one or more embodiments, the network participant 20 may maintain a reception error counter. (REC) 2015 and a transmission error counter (TEC) 2013. do.

[0089] In one or more embodiments, the network participants 201, 202,...,2 0 n 20 network participants ini The receive error counter 2015 in a certain thread As a result of reaching the threshold, 20 network participants i to the communication bus 30 It can be assumed that the

[0090] In one or more embodiments, the network participants 201, 202,...,2 0 n 20 network participants in i The transmission error counter in As a result of reaching this node, node 20i stops transmitting data and clears the bus. It is possible to enter a passive (recessive) state to avoid confusion. .

[0091] In one or more embodiments, the network participants 201, 202,...,2 0 n Any of the transmission error counters in i From As a result of the data not being received by a participant i Mass that can be sent to It is possible to reset the slave 20 by a command from the master 10. i To The receipt of a reset command in the It is possible to unlock the slave which may have entered a passive state by do.

[0092] One or more embodiments may be implemented that are compatible with the "de facto" standard of CAN bus. It is possible to adopt REC / TEC as long as it is (already) provided by the supplier.

[0093] The security concept of one or more embodiments is based on a master-slave protocol structure and Sending messages within a set time frame and receiving those messages correctly It is possible to construct a rule regarding the actions involved in doing something.

[0094] One or more embodiments may address situations such as those described below.

[0095] a. TEC threshold exceeded i. TEC in Master: The master recognizes that it is no longer associated with the slave. -> A warning message is issued (e.g. to the driver: lamp, dash message, etc.) ii. TEC in a slave: A slave can send a diagnostic message to the master. Recognize that this is not possible -> Enter a fail-safe state ("limp home"), e.g. If the LED backlight is turned on,

[0096] b. REC threshold exceeded i. REC at the master: If there is a "distortion" in the network (e.g., a shorted cable or (other reasons) -> Master sends a fail-safe command to the slave and a warning message Issues a message (for example, to a driver).

[0097] ii. REC at the slave: "Distortion occurs" in the network -> the slave stops communication Stops (thus avoiding the potential risk of the bus blocking other slaves' communications) (avoid) and enter fail-safe state.

[0098] c. Master sends the "first" message i. Master does not receive acknowledgement -> TEC increases in master and Same reaction as above.

[0099] ii. Slave does not receive the "first" message in a given time frame -> Distortion in the network (same as REC failure in the slave, same reaction as above) Response).

[0100] d. Master sends "second" message i. Master does not receive ACK -> same reaction as above.

[0101] ii. Master does not receive a response from the addressed slave -> network distortion Raw (at least in the slaves involved, the same reaction as above).

[0102] iii. Slave does not receive the "2nd" message -> no action; communication continues with the "1st" message Verified by Sage, and identical reaction in that regard to that stated above.

[0103] e. The slave responds to the "second" message by sending a diagnostic frame i. The master does not receive a diagnostic frame within a certain time frame or returns a distorted response. Receive -> Network distortion (at least in the slaves involved, not in the master) (Same response as described above for REC failure in

[0104] ii. Slave does not receive acknowledgement: Network distortion -> Slave Same reaction as above to TEC failure in the slave; possible TEC failure in the slave In its absence (see below) no response is provided and the "first" message from the master is The communication is verified by receipt of the message.

[0105] As mentioned above, one or more embodiments may implement a REC / TEC concept for a slave. Along with "dropping", for example, parts of the original CAN(FD) protocol It is possible to aim to keep it (only) in the master as The master (only) evaluates its TEC / REC.

[0106] In one or more embodiments, in a failsafe / limp home situation, the switch The device (e.g. LED driver for backlighting in an automobile) goes into a safe state. For example, the backlights may be turned on (at least partially) and the car may be darkened. It can be seen by other drivers in the dark and can also be used to detect, for example, excessive temperature or other other auxiliary functions that may increase power consumption to avoid other disturbances Refuse.

[0107] Of course, the type and nature of the failsafe / limp home situation depends on the types of slaves involved. may vary as a function of time, e.g., to avoid driver confusion during night driving periods. In some cases, the interior lights may simply be turned off.

[0108] In one or more embodiments, a main controller (Shuma) is connected to the bus 107. Failure in network connection to the sea / body controller or higher level controller In the event of damage, the master may enter a fail-safe state. As a result of entering the safe state, a master issues commands to its associated slaves. Each can enter a fail-safe state by sending a warning message. It is possible to react to network distortions by using a warning message, for example. The driver will be notified via a notification pad and / or dashboard message.

[0109] In one or more embodiments, any transmitter may transmit a data frame to a receiver. At least one Acknowledge ("ACK") bit is generated as a result of successful reception. Therefore, the transmitter is still able to receive the For example, it is possible to identify whether the transmitter is coupled to at least a portion of the The transmit error counter is incremented as a result of an ACK bit not being received by that transmitter. will be done.

[0110] For example, in one or more embodiments, as illustrated herein, master 10 may be May be used as a "watchdog trigger" and / or network "heartbeat" The receiving slaves 201, 202 send out messages at regular intervals. 2,...,20 n The master 10 can recognize whether or not it is communicating. The master 10 may periodically request status information from each connected slave 20. There are slaves 201, 202, ..., 20 n Slave 20 in i Master 10 If the slave does not respond to a status information request issued by the slave i "Non-existence" of It is possible to detect (e.g., a fault).

[0111] For example, in one or more embodiments as illustrated herein, any transmitter may to compare the bits it transmits over bus 30 with the bits it receives on bus 30. As a result of determining that the transmitted bits are not equal to the received bits, As a result, it is possible to assume the presence of an error and therefore to estimate the transmission error counter of the transmitter. The transmitter node can increase the TEC by a certain threshold. As a result of reaching the hold, the transmitter stops transmitting data and goes into passive mode. It is possible to enter a state.

[0112] For example, in one or more embodiments as illustrated herein, a received The frame may be determined, for example, by checking one or more of the following characteristics: It is possible to verify the accuracy.

[0113] That is, its characteristics are: - the accuracy of the received CRC, - receiving a CRC field followed by one recessive bit as a CRC delimiter, - the accuracy of bit stuffing of received frames; It is.

[0114] In one or more embodiments, the received CRC does not match the received frame. As a result of this case, it is possible to discard the received frame and set the REC of the receiver to It is possible to increase the

[0115] In one or more embodiments, the bit stuffing of the received frame is correct. As a result of this, it is possible to discard a received frame and the receiver's R It is possible to increase EC.

[0116] In one or more embodiments, the transmitted frames may be characterized, for example, as having one of the following characteristics: It is possible to verify the accuracy by checking one or more Its features are: -The transmitted bits are received by the transceiver, so the transmitted bits and the received bits are Uniformity between bits, - At least one receiver issues an ACK bit to the receiver. Acknowledgement of a transmitted frame by the receiver circuitry of the

[0117] In one or more embodiments, the transmitted and received bits are identical. As a result of not finding that the frame was transmitted, it can be considered invalid. , transmission is halted and the transmitter's TEC is increased.

[0118] In one or more embodiments, the transmitter circuit receives an ACK bit from the receiver. As a result, the transmitted frame is not received by any of the receivers. The TEC of the transmitter can be considered as not being increased and the transmitted frame is There are cases where the message may not be retransmitted.

[0119] In one or more embodiments, slave devices 201, 202,..., 20 n of Oscillators 2016 are designed to have a maximum of their oscillation frequency that is, for example, ±2% of the predicted value. It is possible to have an allowable deviation. Thus, in one or more embodiments The maximum frequency offset between two slaves is a maximum value, e.g., up to ±4% of the vibration frequency. , it is possible to reach

[0120] In one or more embodiments, frames transmitted by a slave are is intended to be decoded by another slave on the same communication bus 30. There may be no difference between the number of slaves that receive a frame sent by another slave. As a result of this, the receive error counter of the first slave may be incremented. No frames are transmitted by these slaves and therefore no distortion is caused to the communication. will never occur.

[0121] Thus, in one or more embodiments, the REC of the receiver is set to the value shown in Table 1 below. As shown in the example, the error-free frames are sorted according to the length of the received frames. As a result of receiving it, it may be reduced.

[0122] In one or more embodiments, the receiver REC may be, for example, a classical CAN-extended CAN partial networking (CA) working with frame format (CEFF) N PN), decreases by 1 unit for Data Length Codes (DLCs) up to 8 In the case of longer frames, this behavior may be Because many frames generated from the slaves can be considered within 10. This is because the frame may not be recognized by other slaves on the communication bus 30. In the worst case, all of the frames originating from the slave are In addition, the REC of the receiver may not be recognized by other slaves. It may be increased by more than one unit per frame because This is because errors, CRC errors, and CRC delimiter errors may be added.

[0123] In one or more embodiments, the master may receive a ACK from the slave for each slave response. In practice, in one or more embodiments, In this case, the slave response may be shorter than the frame sent by the master ( (e.g. carrying a lower number of data bytes).

[0124] A signal transmitted by one slave on bus 30 and transmitted to other slaves coupled to bus 30 To "compensate" for the slave responses going to the slaves, they increase their REC. A long frame sent by the master that is correctly received by the slave is illustrated in Table 1. Thus, the REC of the slave is set to a length according to the length of the frame transmitted by the master. It is possible to reduce it.

[0125] [Table 1]

[0126] FIG. 5 illustrates a "broadcast" frame implemented in one or more embodiments. A block diagram illustrating a possible logic flow describing the protocol, e.g., when a master This is the case when a "first" message is sent and a slave receives such a message.

[0127] In FIG. 5, the logic blocks to the left of the thick vertical line are executed by the master device 10. The logic blocks to the right of the thick vertical line represent the operations performed by the slave devices. Place 201,202,...,20 n Among the slave devices 20 i Implemented in This represents the action that can be taken.

[0128] The meaning of the logical blocks in FIG.

[0129] -300: Send the "first" message with the broadcast ID, -301: Received "first" message, -302: An error was detected in the "first" message received (Y=error detected, N= No error detected), -303: In the case of a positive (Y) output of block 302, increase the REC of the slave. -304: Transmission completed, -305: Send an ACK bit if the block 302 has a negative (N) output; -306: Decrease REC of the slave. -307: Finished with "reception successful" status, -308: ACK bit received, -309: Error detected in received ACK bit (Y=error detected, N=no error) detection), -310: If the block 309 has a negative (N) output, the system ends with a "successful transmission" status. -311: In case of a positive (Y) output of block 309, the TE of the master is optionally Increase C and send an error frame. -312: Transmission completed, -313: Error frame received, -314: Increase the REC of the slave. -315: Transmission completed.

[0130] In order to facilitate understanding of the operation described in the block diagram of FIG. 5, the following is a more simplified explanation. will be explained.

[0131] As illustrated in FIG. 5, in one or more embodiments, a For example, to set an actuator value, the master 10 may ,202,...,20 n It is possible to send a "first" message to

[0132] In one embodiment, the "first" message is sent to a slave connected to communication bus 30. B201, 202,...,20 n It may include settings for all of the above.

[0133] In another embodiment, the "first" message is sent to a slave connected to the communication bus 30. 201,202,...,20 n A subset of all slaves, e.g. B201, 202,...,20 n There may be a single slave in the may be included.

[0134] In one or more embodiments, the master 10 may, after sending the "first" message: Slave 201, 202,...,20 n You may not expect a response from At least one acknowledge bit from at least one slave, e.g., CAN In knowledge slots, one may expect.

[0135] In one or more embodiments as illustrated herein, the master 10 comprises at least No acknowledge bit is received from any slave, e.g. C As a result, in the AN acknowledge slot, the master 10 In one or more embodiments, the master 10 increases the counter on the communication bus 30. In some cases, the UE may transmit an error frame.

[0136] In one or more embodiments as illustrated herein, the slaves 201, 202, . ..,20 n checks the integrity of the received "first" message and An acknowledge bit can be sent if the message is error-free In such a case, the "first" message is considered valid. In further embodiments, receiving additional error frames does not result in any additional reactions. This will increment the receive error counter without any response.

[0137] In one or more embodiments, the slaves 201, 202,..., 20 n Yes, that They may pick data from the "first" message that is valid for them. In one or more embodiments, the "first" message includes a broadcast ID, e.g. For example, in the standard ID field of a CAN message, it may carry

[0138] FIG. 6 describes a diagnostic frame protocol that may be implemented in one or more embodiments. FIG. 1 is a block diagram illustrating a possible logic flow for, for example, a master sending a "second" message; A slave sends a message and one slave receives such a message and responds to it. This is the case when

[0139] As in FIG. 5, the logic block on the left side of the thick vertical line in FIG. 6 is the master device 10. The logic blocks to the right of the bold vertical line represent the operations performed in Slave 201, 202,...,20 n Any of the slave devices 20 i In reality It represents the action to be taken.

[0140] The meaning of the logical blocks in FIG.

[0141] -400: (target) send "second" message with slave ID, -401: "Second" message received, -402: Error detected in the "second" message received (Y=Error detected, N=Error Error not detected), -403: In the case of a positive (Y) output of block 402, increase the REC of the slave; -404: Transmission terminated, -405: Send an ACK bit if the block 402 has a negative (N) output; -406: Decrease REC of the slave. -407: 10-bit bus idle wait, -408: Error detected (Y=Error detected, N=No error detected), -409: Send a response message with the slave ID, -410: ACK bit received, -411: Error detected in received ACK bit (Y=error detected, N=no error) detection), -412: When the block 411 outputs positive (Y), the TEC of the master is increased and the Send error frame, -413: Error frame received, -414: Increase the REC of the slave. -415: Transmission completed, -416: Waiting for TREC, -417: Check if TREC timeout has been reached (Y=TREC timeout N=TREC timeout not reached) -418: Trigger watchdog failure if block 417 outputs positive (Y), -419: Receives a response message in case of negative (N) output of block 417; -420: Error detected in received response message (Y=Error detected, N=Error Non-detection), -421: In the case of a positive (Y) output of block 420, the REC of the master is increased and the Send error frame, -422: Error frame received, -423: Increase the TEC and REC of the slave. -424: Transmission completed, -425: Send an ACK bit if block 420 has a negative (N) output; -426: Decrease REC of the master, -427: Finished with "received successfully" status, -428: ACK bit received, -429: Error detected in received ACK bit (Y=error detected, N=no error) detection), -430: In the case of a positive (Y) output of block 429, increase the TEC of the slave; -431: Transmission completed, -432: Decrease the TEC of the slave in case of a negative (N) output of block 429; -433: Finished with "sent successfully" status.

[0142] In order to facilitate understanding of the operation described by the block diagram of FIG. A brief explanation is given below.

[0143] As illustrated in FIG. 6, in one or more embodiments, the master 10 In the message ID, for example, the standard ID field of a CAN message, slave 2 0 i The slaves connected to the communication bus 30 are identified by including a slave ID. B201, 202,...,20 n Among them, a certain slave 20 i Request diagnostic data from The master 10 may transmit a "second" message to the master 10 within a specific time window. Wait for a response from the addressed slave in TREC, e.g. a response message If the master 10 does not receive a response within the time window TREC, As a result of this, it is possible for a watchdog error to be triggered.

[0144] In one or more embodiments, the “first” signal transmitted by master 10 on bus 30 is As a result of correctly receiving the "2" message, slave 20 i is the ACK slot Respond with an ACK bit and wait a certain time interval (period), e.g. at least one second of bus idle. 0 bit, wait and then send the response message.

[0145] In one or more embodiments, the slaves 201, 202,..., 20 n Inside Other slaves in the master may receive the response message incorrectly (for example, (due to the frequency offset of each oscillator relative to the frequency). As a result of incorrectly receiving the message, the receiving slaves 201, 202,... ,20 n The REC may be increased.

[0146] In one or more embodiments as illustrated herein, the master 10 issues Any slave not addressed by the received "second" message will not respond and will not be The slave ignores any response messages sent by the slave.

[0147] In one or more embodiments as illustrated herein, upon request from master 10 The frame is slave 201, 202, ..., 20 n Sent (only) by. Therefore, if an error occurs, slaves 201, 202, ..., 20 n What is the meaning of No frames are retransmitted.

[0148] In one or more embodiments as illustrated herein, the "second" message is It may be labeled with the ID of the slave that was addressed. Optionally, The second message is generated by the unused ID bits in the Standard ID field. It is possible to have frames labeled as broadcast frames by The lower 10 bits of the slave ID field can indicate the slave that is addressed. while the 11th bit marks the frame as a broadcast frame. (It is possible to do this.)

[0149] FIG. 7 illustrates an error and overload frame that may be implemented in one or more embodiments. FIG. 1 is a block diagram illustrating a possible logic flow describing a system protocol.

[0150] As in FIGS. 5 and 6, the logic blocks to the left of the thick vertical lines in FIG. 7 are master devices. The logic blocks to the right of the bold vertical line represent the operations performed by the device 10. The lock is connected to slave devices 201, 202, ..., 20 n Any of the slave devices 20 i The symbols represent the operations to be performed in the

[0151] The meaning of the logical blocks in FIG.

[0152] -500: Error detected (Y=Error detected, N=No error detected), -501: In case of negative (N) output of block 500, the end is in "transmission successful" state. -502: In the case of a positive (Y) output of block 500, increase the TEC of the master and Sending an error frame, -503: Transmission completed, -504: Error frame received, -505: Increase the REC of the slave. -506: Transmission completed.

[0153] The operation described by the block diagram of FIG. 7 will be briefly explained below for ease of understanding. will be explained.

[0154] In one or more embodiments, the error frame is sent to the slaves 201, 202, .. .,20 n Transmitted (only) by Master 10, not by the This may result in the slave's REC being incremented by 1. The same behavior may result in an error It can also be applied to the case of overload frames that are treated as frames. do.

[0155] In one or more embodiments, the bus participants (slaves 201, 202, ..., 20 n ) is not capable of arbitrating communication on bus 30 because communication This is because it can be initiated and / or controlled (only) by the master 10 .

[0156] In one or more embodiments as illustrated herein, any of the data on bus 30 may be Collisions also cause the associated error counter to be incremented. Detects errors as collisions and counts transmission errors without retransmitting the frame. It is possible to increase the number of slaves 201, 202, ..., 20 n One of the If a slave detects an erroneous bit on bus 30 (e.g., a dominant instead of an expected recessive), In some cases, the DMA controller may detect a transmission error (eg, a 0x0 bit) and increment its transmission error counter.

[0157] As you can see, error messages are, so to speak, errors themselves, i.e. they are They may not fulfill the AN protocol requirements. They are simply a set of There may be, for example, six consecutive dominant bits. Therefore, they are errors. The slave side will discard them without any reaction. is possible.

[0158] One concept underlying one or more embodiments is the concept of a "first" message and a "second" message. As long as the "first" message is the (only) message sent by the master, The watchdog will be activated only if the first and / or second message are received correctly. This is to reset the timer.

[0159] FIG. 8 illustrates a possible communication cycle for the master unit 10 in one or more embodiments. FIG. 1 is a block diagram illustrating a possible implementation.

[0160] The meaning of the logical blocks in FIG.

[0161] -600: Start communication, -601: Slave 20 i Should a request for diagnostic data be issued to Decide whether to do this (Y=Slave 20 i Issue a diagnostic data request to N=20 slaves i To (without issuing a diagnostic data request to the -602: Slave 20 when block 601 positive (Y) output i The "second" message Send a message, -603: Slave 20 i Reset the watchdog timer of -604: Slave 20 i Whether a response message with diagnostic data was received from Check (Y = diagnostic data received, N = diagnostic data not received), -605: Slave 20 i Check whether the watchdog timer has expired (Y =Watchdog expired, N=Watchdog not expired), -606: Slave 20 when block 605 positive (Y) output i Watched for Detects a timeout. -607: Send "first" message if negative (N) output of block 601; -608: Optionally, T WAIT stand-by.

[0162] In one or more embodiments, the master 10 may send a "first" message, e.g. For controller settings, (for example, cyclically) slaves 201, 202, ... ,20 n and those slaves will watch for such cycles. It is possible to use the "first" message as a watchdog trigger. Slave 20 in a while i As a result of the watchdog timeout not being received by the Consequences of a watchdog timeout being detected As a slave 20 i is capable of entering a fail-safe state.

[0163] In one or more embodiments, the master 10 may i It may request diagnostic data from the addressed slave 20 i For a certain amount of time Failure to respond within a certain time frame can result in a watchdog timer being triggered. Therefore, the master is connected to the slave 20 i Capable of acting on loss of communication with It is.

[0164] In one or more embodiments as illustrated herein, the data includes at least two different In this manner, the slaves 201, 202, ..., 20 n It is possible to send to.

[0165] In the first case, the master 10 sends the "first" message to all slaves 201. ,202,...,20 n In such a case, the master device 10 is slave 201, 202, ..., 20 n may not expect a response from

[0166] In the second case, the master 10 sends a "second" message to a specific slave 20. i fart Slaves 201, 202, ..., 20 n The second message message as a broadcast frame, e.g. for actuator settings Therefore, the addressed slave (and only the slave) can respond with a response message. The diagnostic data is then sent back to the 'second' message. Such diagnostic data is ignored by other slaves on the bus 30. Due to the frequency offset of may be seen as an error frame by other slaves and each of them This may increase the REC.

[0167] In one or more embodiments, the "second" message may be a dedicated frame. may be ignored by other slaves.

[0168] In one or more embodiments, the "first" message is a specific broadcast The "second" message may use the I / O ID of the addressed slave. It may contain D.

[0169] In one or more embodiments, the available remaining bits in the Standard ID field The bit is used to transmit diagnostic request data to the multiple slaves and to only the addressed slave. This can be used to distinguish between specific requirements of the

[0170] FIG. 9 illustrates one or more embodiments of slave units 201, 202,..., 20 n FIG. 1 is a block diagram illustrating a possible implementation of the communication cycle.

[0171] The meaning of the logical blocks in FIG.

[0172] -700:Communication begins, -701: Reset watchdog timer, -702: Detect whether a valid message was received (Y = valid message was received) , N=no valid message received), -703: If the positive (Y) output of block 702 is received, the valid message is Determine if it is a "first" or "second" message (Y = "first" message) message received, N="second" message received), -704: Response message with diagnostic data when block 703 has a negative (N) output Send, -705: If the output of block 702 is negative (N), is it possible to determine whether the watchdog has expired? (Y = watchdog expired, N = watchdog not expired), -706: Issue a watchdog failure if block 705 outputs positive (Y).

[0173] In one or more embodiments, the master 10 includes slaves 201, 202,..., 20 n Such data is sent to each watchdog. It can be used by each slave to reset the If the frame is not intended to be used for the purpose of If the watchdog is received by one slave before it expires, a watchdog failure is set. Such a watchdog failure may result in a fail-safe state. may be used by the slave in the future.

[0174] In one or more embodiments, the slave 20 i was addressed to it. As a result of receiving the "second" message, the receiving slave 20 i is the requested diagnosis The interrupted data is then sent to the interrupted device, which responds by sending a response message containing the interruption data.

[0175] In one or more embodiments, the master 10 may transmit, for example, For example, to send 64 bytes (i.e. 512 bits, where 1 byte is equal to 8 bits) of data, Bus participants, e.g. slaves 201, 202,...,20 n , is the master Therefore, one slave receives the data transmitted from the master 10. It "picks" the information it needs from any set of 512 bits of data received from This type of frame is called a "first" message. do.

[0176] The number of bits that a slave may read in a "first" message is The location of the data in a given slave may vary depending on the particular implementation of the bus. The determination can be made during the initialization sequence.

[0177] For example, each slave might read 8 bits of data in the "first" message. The total amount of data sent by the master 10 in a "first" message is For example, if there are 64 bytes (i.e., 512 bits) per "first" message, It is possible to supply up to 64 slaves with the same data. The amount of data sent by the master 10 in the "first" message and the amount of data sent by the slave Once the amount of data to be read is defined, the addressable portion is created by the "first" message. It is possible to define the maximum number of slaves that can be

[0178] In one or more embodiments, the number of possible bus participants (i.e., the number of slaves) is , it is possible to increase the number of slaves by supplying "multiple chains" of slaves. In that case, the first "first" message is sent to the slaves in the first chain (for example, 64 The second "first" message addresses the first slave in the second chain, It is possible to address a slave, and so on. The message ID field is a dedicated ID (e.g. the CAN FD ID field ) can be used to address the

[0179] In one or more embodiments, a slave uses its slave address. Each thread can be individually addressed by The server responds with this diagnostic request frame.

[0180] In one or more embodiments, the "second" message sent by master 10 and slave 201, 202,...,20 n The data of the response message sent by For example, the ST SPI (Serial Peripheral Interface) developed by a company belonging to the ST Group is included in the Embedding protocols such as the Referral Interface (4.1) protocol is a It makes it easy to read or write certain data to an address.

[0181] In one or more embodiments, in the data of the "second" message from the master The SPI command based on the embedded ST SPI protocol is a memory address and the corresponding request. The number of data bytes for a request (read / write) can be configured. The block then returns a specific address instead of the address and the data bytes of the requested memory address. It is possible to respond to the ST SPI protocol with bytes. Such specific bytes are It is called the "Global Status Byte" (GSB) and contains important status bits. Such status bits include, for example, an error that occurred, a reset that occurred, , etc. Therefore, the global status register is sent with each diagnostic response. It is possible to return it.

[0182] In one or more embodiments, the “first” message is (All) slaves 201, 202, ..., 20 n Sent by master 10 to The ID field of the "first" message is the address of the It may contain an identification number of one of the chains addressed. The slaves in the group can receive the data transferred by that frame (for example, up to 64 It is possible to obtain these data from a single slave (bytes of data). The number of data bits read by the function is defined at the time of execution of the function (e.g., the so-called (This is a "hard coded" value) in the overall data field of the "first" message. The location of the data directed to a slave in the addressed chain is determined by the chain initialization period. It is possible to decide during the period.

[0183] In one or more embodiments, a "first" message may begin with, for example, "1." And an 11-bit frame ID followed by three "1"s and the chain identification number being addressed, e.g. For example, a 7-bit number may be used. For example, a chain coded on 5 bits Using the identification numbers allows identification and allocation of up to 64 slave chains. where each chain contains, for example, a maximum of 63 slaves.

[0184] In one or more embodiments, a particular “first” message, referred to herein as “initialization” The slaves 201, 202, ..., 203 in the communication bus 30 are connected to each other via a frame. n to determine their "membership" in a chain and The result of receiving an initialization frame is that the relative positions of the As such, the slaves can read and write the received broadcast frames from the communication bus 30. For example, a "first" message is a condition for reading the data intended for it. The number of bits read by a slave in The INT_TIME_CONFIGURATION_TIME may be the same as the INT_TIME_CONFIGURATION_TIME and may be defined in the bus implementation (eg, a hard-coded value).

[0185] In one or more embodiments, the ID for the chain initialization frame can be, for example: For example, it is possible to set the value to "1_0110_0000_00".

[0186] In one or more embodiments, a slave may receive, for example, three bytes from the initialization frame. For example, the first byte of a The second byte represents its position in the chain, and the third byte represents the address. Therefore, the buffer in the data field of the initialization frame may represent a slave. The dimensions in the bit and the required by one slave to be properly initialized. Depending on the amount of data required, a single It is possible to use an initialization frame. For example, the data field of the initialization frame For example, if the field is 64 bytes long and one slave is properly initialized, For example, if 3 bytes of data are required, a maximum of 21 bytes can be stored in one CAN FD frame. It is possible to initialize slaves.

[0187] In one or more embodiments, the wake-up pattern (WUP) is a specific "first 1" message. The wake-up pattern ID is For example, T at 1Mb / s FILETER (short) and ISO11898-2 The wake-up pattern can be selected to meet the requirements of the communication bus. When operating at a lower bit rate, FILETER Use (long) is possible.

[0188] In one or more embodiments, the reserved WUP ID is "1_000_1 11_000". The WUP is an optional wake-up frame. It is possible for there to be repetition or enhancement in the data bytes.

[0189] In one or more embodiments, the master 10 may transmit a CAN FD frame. By sending a "second" message, it is possible to select a specific slave i The CAN FD ID in the "second" message may be Slave ID, e.g. 9-bit slave ID, and call such a frame the "second" frame and one bit to identify such a frame as a unicast frame. It may contain one bit that

[0190] In one or more embodiments, the CAN FD I / F used in bus 30 The most significant bit (MSB) of D is used to denote a so-called "unicast" frame, i.e., a frame sent to a single slave. It is equal to "0" to identify a frame that is addressed to only the block, and "Block Identify "broadcast" frames, i.e. frames addressed to all slaves. If the SYNCHRONOUS_CHAIN_INIT_FRAME is set to 0, then the SYNCHRONOUS_CHAIN_INIT_FRAME may be set to 1, in which case the SYNCHRONOUS_CHAIN_INIT_FRAME and the SYNCHRONOUS_CHAIN_INIT_FRAME may be set to 0. As will be understood, the "1" and "0" are References to values ​​are merely exemplary and, in one or more embodiments, may in fact be complementary. In some cases, a selective choice (e.g., values ​​of "0" and "1", respectively) may be employed.

[0191] In one or more embodiments, the unicast frame does not contain any data. As a result of not having a DDR_SEND_TIME_TIME, the addressed slave will not be able to read / write data as defined in the implementation. In some cases, default diagnostic data may be sent. Otherwise, the unicast frame If the frame contains data, such data shall be It is a SPI command based on the

[0192] In one or more embodiments, a UNICODE containing the SPI commands as described above may be used. The slave receiving the cast frame transmits the code via the ST SPI 4.1 protocol. The UE responds with the requested data via a coded "second" message.

[0193] In one or more embodiments, the master 10 may include a CAN FD ID field. By sending a frame containing the slave ID of slave 20 i Address The optional data byte can be sent via ST SPI SDI (ST Serial Peripheral Interface Serial Data Input) Frame Encapsulated It may contain.

[0194] In one or more embodiments, the slave 20i transmits a response message on the communication bus 30. A diagnostic response frame is sent to the 2nd message received. The response message is selected to be a CAN FD frame. The CAN FD ID of the response message is the slave ID, e.g. For example, a 9-bit slave ID and a single bit to identify such a frame as a response message. It contains a 1 bit that identifies such a frame as a unicast frame. It is possible to include

[0195] In one or more embodiments, the data bytes of the response message include: ST SPI SDO (Serial Peripheral Interface, as developed by the ST Group of companies) It is possible to include a (Interface Serial Data Output) frame in the slave. The "second" message received thus contains data within the frame data field. If the data byte does not match the global status byte, the slave The received “secondary bit” in a CAN FD frame may contain only a GSB. " message.

[0196] In one or more embodiments, a different default response may be used. This can be specified in the equipment data sheet.

[0197] A frame ID in some embodiments, such as a CAN FD standard frame ID. Possible uses of are shown by way of example in Table 2 below.

[0198] [Table 2]

[0199] In one or more embodiments, the protocol controller may be a CAN The FD protocol may be implemented.

[0200] In one or more embodiments, performing CAN FD wakeup frame detection. The building blocks for the simplified master / slave communication structure are can be used and modified to make the slave Respond (only) to requests made by.

[0201] As already noted, The "first" message described throughout this description is essentially a message sent by one device, e.g. A message sent on the bus by one device is received (simultaneously) by (all) the other devices. These latter devices then receive the operational data portion carried by the broadcast message. A protocol such as the CAN bus protocol that allows each operation to be performed as a function of Broadcast messages, as traditionally sent in message-based protocols, It supports -Similarly, one (master) device can "physically" broadcast data on the bus. Although the second message described throughout this description is in fact a Essentially, it is a "logical" address to each of the other (slave) devices as a request message. In this case, the slave device can transmit, for example, diagnostic messages. Each of the devices is required to react by transmitting a response - within a certain time interval - to the master device. At that time, the master device assigns respective collision-free response intervals to the slave devices. Insofar as such responses are assigned, possible collisions are avoided.

[0202] Therefore, the first message can be considered a true "broadcast" message. Conversely, it is possible to physically broaden the bus 30 by one (master) device. while the second message is logically addressed to an individual one of the slave devices. The second message can essentially be considered as a "unicast" message insofar as it is processed by the It is possible to do so.

[0203] In one or more embodiments, a method includes: - a first device (e.g., 10) and a pair of second devices (e.g., 201,202,...,20 n ) and combine; - configuring the first device as a master device to transmit on the bus; a) a set of operation data representing operations for execution by a second device on the set of second devices; a first message carrying a data message portion; and - b) a second message addressed to a second device in the set of second devices; The second message is addressed to the first device within a respective expected response period. the second device carrying an identifier that identifies each of the second devices that request a respective response. Message; and - configuring the second device as a slave device; -c) receiving the first message from the first device configured as a master device, and receiving each operational data message in the set of operational data message portions on the and reading the respective operational data message portions and calculating the operational data as a function of the respective operational data message portions read. to perform each action; -d) the second message sent from the first device configured as a master device. A response message is sent to the first device that is configured as a master device and receives the response message on the bus. Respond thereto within their respective expected response periods by transmitting on the bus. , It encompasses:

[0204] In one or more embodiments, the first device configured as a master device In a first message transmitted on the bus from the first device configured as a master device, Each of the second devices configured as slaves is Send an initialization message on the bus containing initialization data indicating which A second device that is capable of receiving a signal from the master device and is configured as a slave device. receiving an initialization message transmitted on the bus from the first device configured as a and dedicated thereto in the set of operational data message parts. A function of the initialization data to read each operational data message portion that is It is possible to initialize it by

[0205] In one or more embodiments, a method is configured as a slave device. The method may include distributing a set of second devices to a plurality of subsets of second devices. In this case, the first device configured as the master device transmits a first operation message a subset identification index that identifies the second device of the subset to which the A first message may be sent on the bus to

[0206] In one or more embodiments, the first device configured as a master device is A first message may be transmitted on the bus at a fixed rate.

[0207] In one or more embodiments, the second devices in the set of second devices each include It is possible to switch to the fail-safe state as a result of the expiration of the checkdog timer. be.

[0208] In one or more embodiments, a second device in the set of second devices is a master device. a first device configured to receive a message selected from the first message and the second message; It is possible to reset each watchdog timer as a result of receiving a It is.

[0209] In one or more embodiments, the first device receives a signal from a second device in a set of second devices. Each of the reactions required from the first device does not arrive at the first device within its respective expected reaction time. and / or each from a second device in a set of second devices. Each of the Cs indicates that the reaction does not reach the first device within the respective expected reaction time period. It is possible to trigger a hitchdog error signal.

[0210] In one or more embodiments, the bus may comprise a differentially wired bus.

[0211] In one or more embodiments, a system includes a first device (e.g., 10) and a bus. A set of second devices (e.g., 201, 202,. ..,20 n ), the first device and the second device being respectively a master device and a slave device. The master device and the slave device may be configured as a slave device. It is possible for the device to be configured to operate in the manner described in one or more embodiments.

[0212] In one or more embodiments, a set of second devices (e.g., 30) are connected to the bus (e.g., 31). For example, 201, 202,...,20 n ) as a first device (e.g., 10) via the bus, - a set of operation data representing operations for performance by a second device on the set of second devices; a first message carrying a message portion; and - second messages addressed to second devices in the set of second devices, each Each of the first devices is requested to respond within an expected response period of the second message. the second device carrying an identifier that identifies the respective one of the second devices to which the message is addressed. message, It is possible to configure the device to transmit the above.

[0213] In one or more embodiments, a first device is connected to a set of second devices via a bus. The apparatus for combining the second devices in the set of second devices is Capable of responding to failure to reach the first device within an expected response time period. and / or each response from a second device in the set of second devices is a respective expected a watchdog error signal indicating that the first device does not reach the first device within a predetermined response period; It is possible to configure the device to trigger a signal.

[0214] In one or more embodiments, a first device (e.g., , 10) are coupled to a set of second devices (e.g., 201, 202, ..., 20 n ) Devices to be included within the i )but, - a set of operation data representing operations for performance by a second device on the set of second devices; receiving a first message on the bus carrying a message portion; and transmitting the set of operational data. reading at least one respective operational data message portion in the message portion; and at least one of the read respective operational data message portions. Each performs one of the actions, on the bus as the one of the second devices to which each second message is addressed. each second message conveying an identifier that identifies the device, Each of the second messages requests a respective response from the first device within a response period. receiving messages and responding thereto within their respective expected response times; The response message from the device can be configured as a master device. The received signal is transmitted over the bus to the first device that is receiving the signal.

[0215] In one or more embodiments, a set of first devices coupled to a first device via a bus. The devices contained within the two devices fail as a result of the expiration of their respective watchdog timers. It is possible to configure the device to switch to a safety state.

[0216] In one or more embodiments, a set of first devices coupled to a first device via a bus. A device included in the second device performs a message transfer process on the result of a message received from the first device via the bus. As a result, it is possible to configure each watchdog timer to be reset. .

[0217] In one or more embodiments, a set of first devices coupled to a first device via a bus. 2. The device contained within the device has application-specific hardware implemented therein. The system may include a HW communication and protocol controller (eg, 201) that

[0218] In one or more embodiments, a set of first devices coupled to a first device via a bus. The device to be included in the device includes a light illumination source driver, preferably a vehicle light driver. It is possible to have

[0219] In one or more embodiments, a vehicle (e.g., a V) may include one or more It is possible to provide an example-based system.

[0220] In one or more embodiments, a system according to one or more embodiments A first device (e.g., 10) is connected to a set of second devices (e.g., 201, 202,... ,20 n ) a signal that can be transmitted on a bus (e.g., 30) to transmit a message to - a set of operation data representing operations for performance by a second device on the set of second devices; a second message carrying the message portion; and a second message addressed to a second device in the set of second devices, and requesting respective responses from the first device within respective expected response periods, and the second device carrying an identifier that identifies the respective one of the second devices to which the message is addressed. 2 messages, It is possible to have:

[0221] In one or more embodiments, the second device is configured as a slave device. a first message carrying a set of operational data message portions dedicated to said It is possible for the transmitted signal to occur at a constant rate.

[0222] Without prejudice to the underlying principles, the details and examples may be modified without departing from the scope of protection. However, if the product differs significantly from what is described as an example only, There is.

[0223] Although the specific embodiment of the present invention has been described in detail above, it is understood that the present invention is not limited to the above embodiment. Of course, various modifications are possible without departing from the spirit and scope of the present invention. [Explanation of symbols]

[0224] 10: 1st device 20 i :Second device 30: Bus V: Vehicles

Claims

1. encoding, by the first device, messages in a CAN FD format using a Serial Peripheral Interface (SPI) protocol, each message including a CRC field and a CRC delimiter following the CRC field; and sending, by the first device, a message addressed to a second device in a set of second devices, the message including an identifier identifying each one of the second devices to which the message is addressed; A method comprising:

2. 2. The method of claim 1, wherein the CRC delimiter comprises a recessive bit.

3. 2. The method of claim 1, wherein each message further comprises a memory address, a data byte, and a write request based on the SPI protocol.

4. 2. The method of claim 1, wherein each message further comprises a memory address, a data byte, and a read request based on the SPI protocol.

5. the encoding and transmitting the message are performed by a protocol control unit of the first device; The method of claim 1 , wherein transmitting the message comprises transmitting the message to the second device over a bus.

6. receiving, by a second device in a set of second devices, messages from a first device conveying an identifier identifying the second device as one of the second devices to which a message is addressed, the messages being encoded in CAN FD format using a Serial Peripheral Interface (SPI) protocol, each message in the messages including a CRC field and a CRC delimiter following the CRC field; and verifying, by the second device, the accuracy of the CRC field and the presence of the CRC delimiter. A method comprising:

7. 7. The method of claim 6, further comprising: switching, by the second device, to a fail-safe state as a result of expiration of a respective watchdog timer.

8. 8. The method of claim 7, further comprising: resetting, by the second device, the respective watchdog timer as a result of the message received from the first device.

9. The method of claim 6 , wherein the second device is a light illumination source driver.

10. The method of claim 9 , wherein the second device is a vehicle light driver.

11. 7. The method of claim 6, wherein the CRC delimiter comprises a recessive bit.

12. each message of the messages further comprising a memory address, a data byte, and a write request based on the SPI protocol; 7. The method of claim 6, further comprising: in response to receiving the memory address, the data byte, and the write request, writing, by the second device, the data byte into a memory.

13. 7. The method of claim 6, wherein each of the messages further comprises a memory address, a data byte, and a read request based on the SPI protocol.

14. receiving the message and verifying the accuracy of the CRC field and the presence of the CRC delimiter is performed by a communications and protocol controller circuit of the second device; The method of claim 6 , wherein receiving the message comprises receiving the message from the first device over a bus.

15. A device in a set of second devices coupled to a first device, comprising: receiving messages from a first device conveying an identifier identifying the device as one of the second devices to which the messages are addressed, the messages being encoded in a CAN FD format using a Serial Peripheral Interface (SPI) protocol, each message including a CRC field and a CRC delimiter following the CRC field; and Verifying the accuracy of the CRC field and the presence of the CRC delimiter.

23. An apparatus configured to:

16. 16. The apparatus of claim 15, further configured to switch to a fail-safe state as a result of expiration of a respective watchdog timer.

17. 17. The apparatus of claim 16, further configured to reset the respective watchdog timer as a result of the message received from the first device.

18. 16. The apparatus of claim 15, wherein the CRC delimiter comprises a recessive bit.

19. each message of the messages further comprising a memory address, a data byte, and a write request based on the SPI protocol; 16. The apparatus of claim 15, wherein the apparatus is further configured to, in response to receiving the memory address, the data byte, and the write request, write the data byte into a memory.

20. 16. The apparatus of claim 15, wherein each of the messages further comprises a memory address, a data byte, and a read request based on the SPI protocol.