WO2025003007A1

WO2025003007A1 - Parallel single input/output connections of multiple secondary devices to a primary device

Info

Publication number: WO2025003007A1
Application number: PCT/EP2024/067456
Authority: WO
Inventors: Matteo Colombo; Tim Boescke; Markus Koesler; Daniel Dietze; Alex Lollio
Original assignee: Ams Osram International GmbH
Current assignee: Ams Osram International GmbH
Priority date: 2023-06-29
Filing date: 2024-06-21
Publication date: 2025-01-02
Anticipated expiration: 2025-12-29

Abstract

A device control system has a primary node, which has a controller, configured to send a signal to a primary circuitry, the signal including a command and a unique identifier of a first device or a second device; a first node, comprising: one or more first devices, connected to one another in series, each of which having a unique identifier; and first circuitry, configured to receive a signal from the primary node via the omnibus and to send data corresponding to the signal to a first device; the second node, comprising: one or more second devices, connected to one another in series, each of which having a unique identifier; and second circuitry, configured to receive a signal from the primary node via the omnibus, and to send data corresponding to the signal to a second device.

Description

PARALLEL SINGLE INPUT/OUTPUT CONNECTIONS OF MULTIPLE SECONDARY DEVICES TO A PRIMARY DEVICE

Technical Field

[0001] Various aspects of this disclosure generally relate to a communication protocol for a primary device and one or more secondary devices, connected in parallel to the primary device.

Background

[0002] Various devices or systems of devices may require connection of a primary device to one or more secondary devices. In some instances, these connections may be achieved using a single-wire interface. In other instances, these connections may be achieved using multiple (e.g. 2 or more than 2) single-wire interfaces, such that, for example, 2 different signals are transmitted between devices simultaneously, a first signal on the first wire and a second signal on the second wire. Any such configuration requires a communication protocol, so that data may be reliably transferred between devices.

[0003] One such protocol is known as the Open System Protocol (OSP), which is a communication protocol for use with a primary device and one or more secondary devices. OSP may be used in a variety of implementations and has broad applicability. In one common implementation, OSP may be utilized in the context of a single microprocessor (primary device) and multiple smart light emitting diode (LED) devices.

[0004] In OSP and other related or similar communications protocols, the secondary devices are conventionally connected (e.g. to one another, to the primary device) in serial. With respect to OSP, this serial connection permits OSP’s auto-addressing function, in which a communication is sent from the primary device to a first secondary device, and then from the first secondary device to the second secondary device, and so on until the final secondary device. During these communications, the devices auto-generate their own unique identifier or address, typically by incrementing the unique identifier of the previous device in the chain. Once the addresses are generated, the resulting addresses are sent to the primary device.

[0005] In many contexts, however, it may be desirable to implement a system of secondary devices that are connected to the primary device in parallel.

[0006] First, such parallel connections may create redundancy, which may be necessary for satisfying certain safety standards. For example, parallel connections may be necessary to satisfy certain aspects of International Organization for Standardization (ISO) Standard 26262, “Road vehicles — Functional Safety”, which describes various functional safety aspects related to automotive risks and defines various Automotive Safety Integrity Levels, which are in some instances key to certain automotive safety certifications.

[0007] Next, parallel connections of secondary devices to a primary device may improve latency of transmitted and/or received data. Serial connections as conventionally exist in the OSP standard and in other related standards may become quite lengthy and therefore require serial transmissions between multiple secondary devices. Each element along the chain of serial connections increases the transmission time between the primary device and the intended secondary device. Parallel connections may reduce the number of elements within the chain, such that transmissions from a primary device reach the intended secondary device more rapidly. Particularly in implementations with tight latency constraints, this improvement in latency may be significant.

[0008] As a further benefit, and in some circumstances, the parallel connection between the primary device and the secondary devices may simplify the network cable routing. Long serial connections may be associated with cabling difficulties, as the single serial cable must be routed so as to ensure that the relevant secondary device may be placed at its desired location. Often, this requires the cable to be arranged in a complicated serpentine pattern, or to double back on itself, which reduces efficiency and increases material costs. A parallel connection greatly simplifies the difficulties in routing cables and allows for a more efficient and/or less expensive configuration.

[0009] However, because the conventional auto-addressing function as described above assumes a serial connection among the secondary devices, this auto-addressing function would not operate correctly with secondary devices connected in parallel. Moreover, were secondary devices to be connected to the primary device in parallel, various physical layer conflicts between secondary devices connected in parallel could arise. In the following, parallel connections between a primary device and multiple secondary devices will be described. Although reference is often made to OSP, the principles and methods disclosed herein are not limited to OSP and are intended to be broadly applied to parallel connections between a primary device and multiple secondary devices.

Brief Description of the Drawings

[0010] In the drawings, like reference characters generally refer to the same parts throughout the different views. The drawings are not necessarily to scale, emphasis instead generally being placed upon illustrating the exemplary principles of the disclosure. In the following description, various exemplary embodiments of the disclosure are described with reference to the following drawings, in which:

FIG. 1 depicts a conventional, serial connection between a primary device and a plurality of secondary devices;

FIG. 2 depicts a primary device being connected in parallel to five secondary devices; FIG. 3 depicts a hybrid model in which a primary device is connected in parallel to a plurality of secondary devices;

FIG. 4 depicts a further hybrid model in which a primary device is connected in parallel to each of a plurality of secondary devices; FIG. 5 depicts a further hybrid model in which a primary device is connected in parallel to a plurality of secondary devices;

FIG. 6 depicts a sample configuration of a secondary device;

FIG. 7 depicts a parallel connection of the primary device to a first secondary device chain and a second secondary device chain;

FIG. 8 depicts an exemplary implementation of the MCU mode;

FIG. 9 depicts a parallel connection of the primary device to a first secondary device chain and a second secondary device chain;

FIG. 10 depicts a device control system, including a primary Controller Area Network (CAN) node; and

FIG. 11 depicts an optional configuration of the device control system.

Description

[0011] The following detailed description refers to the accompanying drawings that show, by way of illustration, exemplary details and embodiments in which aspects of the present disclosure may be practiced.

[0012] The word "exemplary" is used herein to mean "serving as an example, instance, or illustration". Any embodiment or design described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments or designs.

[0013] Throughout the drawings, it should be noted that like reference numbers are used to depict the same or similar elements, features, and structures, unless otherwise noted.

[0014] The phrase “at least one” and “one or more” may be understood to include a numerical quantity greater than or equal to one (e.g., one, two, three, four, [...], etc.). The phrase "at least one of" with regard to a group of elements may be used herein to mean at least one element from the group consisting of the elements. For example, the phrase "at least one of with regard to a group of elements may be used herein to mean a selection of one of the listed elements, a plurality of one of the listed elements, a plurality of individual listed elements, or a plurality of a multiple of individual listed elements.

[0015] The words “plural” and “multiple” in the description and in the claims expressly refer to a quantity greater than one. Accordingly, any phrases explicitly invoking the aforementioned words (e.g., “plural [elements]”, “multiple [elements]”) referring to a quantity of elements expressly refers to more than one of the said elements. For instance, the phrase “a plurality” may be understood to include a numerical quantity greater than or equal to two (e.g., two, three, four, five, [...], etc.).

[0016] The phrases “group (of)”, “set (of)”, “collection (of)”, “series (of)”, “sequence (of)”, “grouping (of)”, etc., in the description and in the claims, if any, refer to a quantity equal to or greater than one, i.e., one or more. The terms “proper subset”, “reduced subset”, and “lesser subset” refer to a subset of a set that is not equal to the set, illustratively, referring to a subset of a set that contains less elements than the set.

[0017] The term “data” as used herein may be understood to include information in any suitable analog or digital form, e.g., provided as a file, a portion of a file, a set of files, a signal or stream, a portion of a signal or stream, a set of signals or streams, and the like. Further, the term “data” may also be used to mean a reference to information, e.g., in form of a pointer. The term “data”, however, is not limited to the aforementioned examples and may take various forms and represent any information as understood in the art.

[0018] The terms “processor” or “controller” as, for example, used herein may be understood as any kind of technological entity that allows handling of data. The data may be handled according to one or more specific functions executed by the processor or controller. Further, a processor or controller as used herein may be understood as any kind of circuit, e.g., any kind of analog or digital circuit. A processor or a controller may thus be or include an analog circuit, digital circuit, mixed-signal circuit, logic circuit, processor, microprocessor, Central Processing Unit (CPU), Graphics Processing Unit (GPU), Digital Signal Processor (DSP), Field Programmable Gate Array (FPGA), integrated circuit, Application Specific Integrated Circuit (ASIC), etc., or any combination thereof. Any other kind of implementation of the respective functions, which will be described below in further detail, may also be understood as a processor, controller, or logic circuit. It is understood that any two (or more) of the processors, controllers, or logic circuits detailed herein may be realized as a single entity with equivalent functionality or the like, and conversely that any single processor, controller, or logic circuit detailed herein may be realized as two (or more) separate entities with equivalent functionality or the like.

[0019] As used herein, “memory” is understood as a computer-readable medium (e.g., a non-transitory computer-readable medium) in which data or information can be stored for retrieval. References to “memory” included herein may thus be understood as referring to volatile or non-volatile memory, including random access memory (RAM), read-only memory (ROM), flash memory, solid-state storage, magnetic tape, hard disk drive, optical drive, 3D XPointTM, among others, or any combination thereof. Registers, shift registers, processor registers, data buffers, among others, are also embraced herein by the term memory. The term “software” refers to any type of executable instruction, including firmware.

[0020] Unless explicitly specified, the term “transmit” encompasses both direct (point-to- point) and indirect transmission (via one or more intermediary points). Similarly, the term “receive” encompasses both direct and indirect reception. Furthermore, the terms “transmit,” “receive,” “communicate,” and other similar terms encompass both physical transmission (e.g., the transmission of radio signals) and logical transmission (e.g., the transmission of digital data over a logical software-level connection). For example, a processor or controller may transmit or receive data over a software -lev el connection with another processor or controller in the form of radio signals, where the physical transmission and reception is handled by radio-layer components such as RF transceivers and antennas, and the logical transmission and reception over the software-level connection is performed by the processors or controllers. The term “communicate” encompasses one or both of transmitting and receiving, i.e., unidirectional or bidirectional communication in one or both of the incoming and outgoing directions. The term “calculate” encompasses both ‘direct’ calculations via a mathematical expression/formula/relationship and ‘indirect’ calculations via lookup or hash tables and other array indexing or searching operations.

[0021] FIG. 1 depicts a conventional, serial connection between a primary device 102 and a plurality of secondary devices 104a - 104e. The primary device 102 is connected to secondary device 104a, which is serially connected to secondary devices 104b, 104c, 104d, and 104e. In the auto-addressing procedure described above, the primary device 102 sends a message 110 to secondary device 104a, which sends a message to secondary device 104b, and so on, to ultimately reach secondary device 104e. At each step, the corresponding secondary device determines its address as an increment of the previous address. The addresses are then sent 112 up the chain to the primary device 102.

[0022] In contrast to the conventional, serial connection between the primary device and the plurality of secondary devices, FIGs. 2-5 depict various configurations of parallel connections between a single primary device and multiple secondary devices and/or hybrid combinations of serial connections and parallel connections.

[0023] FIG. 2 depicts a primary device 202 being connected in parallel to five secondary devices: 204, 206, 208, 210, and 212. FIG. 3 depicts a primary device 302 connected in parallel to five secondary devices 304a, 306a, 308a, 310a, and 312a. Each of these secondary devices connected in parallel to the primary device 302 is connected in serial to at least one other device. In this manner, secondary device 304a is connected in serial to secondary device 304b; secondary device 306a is connected in serial to secondary device

306b, and so forth. [0024] FIG. 3 depicts a hybrid model in which a primary device 302 is connected in parallel to a plurality of secondary devices 304a, 306a, 308a, 310a, and 312a. Each of the secondary devices that is connected in parallel to the primary device 302 is further connected in serial to another secondary device. In this manner, secondary device 304a is connected in serial to secondary device 304b; secondary device 306a is connected in serial to secondary device 306b; secondary device 308a is connected in serial to secondary device 308b; secondary device 310a is connected in serial to secondary device 310b; and secondary device 312a is connected in serial to secondary device 312b. In this manner, each of the secondary devices connected in parallel to the primary device 302 is further connected in serial to one other secondary device.

[0025] FIG. 4 depicts a further hybrid model in which a primary device 402 is connected in parallel to each of a plurality of secondary devices 404, 406, 408a, 410 and 412. Secondary device 408a is connected in serial to secondary device 408b, which is connected in serial to secondary device 408c. In this manner, a secondary device connected in parallel to the primary device 402 is further connected in serial to multiple other secondary devices, so as to form a chain of secondary devices.

[0026] FIG. 5 depicts a further hybrid model in which a primary device 502 is connected in parallel to a plurality of secondary devices 504a, 506a, 508a, 510a, and 512a. Each of these secondary devices connected in parallel to the primary device 502 is further connected in serial to an additional secondary device, such that secondary device 504a is connected in serial to secondary device 504b; secondary device 506a is connected in serial to secondary device 506b; secondary device 510a is connected in serial to secondary device 510b; and secondary device 512a is connected in serial to secondary device 512b. As an extension beyond the previous hybrid models, secondary device 508a includes a further parallel connection, such that secondary device 508a is connected in parallel to each of secondary device 508b 1 and secondary device 508b2. [0027] In light of FIGs. 2-5, it can be seen that a wide variety of connections is possible such that the primary device is connected in parallel to at least two secondary devices, or that a primary device is connected in serial to a secondary device, and that secondary device is connected in parallel to at least two other secondary devices. The configurations depicted in FIGs. 2-5 are provided for demonstrative purposes and are not intended to be limiting. Instead, however, they are rather presented to show a variety of connection possibilities, and the skilled person will appreciate that any portion or combination of portions of these figures may be combined with one another, and that a wide variety of parallel connections and/or parallel and serial connections are possible.

[0028] FIG. 6 depicts a sample configuration of a secondary device 602. The secondary device may include two input/output ports, each having two pins. In this case, the first input/output port includes a first pin connected to a first transmission line 604 and a second pin connected to a second transmission line 606. The second input output port includes a third pin connected to a third transmission line 608 and a forth pin connected to a fourth transmission line 610. The transmission lines associated with each of the pins may be connected to a pullup resistor or a pulldown resistor, such as depicted in 612, wherein the first transmission line 604 is connected to a pull-up resistor and the second transmission line 606 is connected to a pulldown resistor, and in 614 wherein the third transmission line 608 is connected to a pull-up resistor and the fourth transmission line 610 is connected to a pulldown resistor. Naturally, this configuration is given for demonstrative purposes only, and the polarities of the pins and corresponding transition lines may be reversed as desired for a given implementation. The resistance of the various pull-up resistors and pulldown resistors depends at least on the type of signal encoding used, the magnitude of the supply voltage, and the range of voltage is used for signal transmission. The skilled person will be capable of selecting an appropriate resistance for the pull-up resistors and pulldown resistors based on these factors; however, in a nonlimiting example the pull-up resistors and pulldown resistors may each be approximately 10k ohms.

[0029] Various systems may be capable of a plurality of communication modes. With respect to OSP, the OSP protocol may be capable, in relevant part, of at least 3 modes known as a low-voltage differential signaling mode (LVDS mode); an end of line (EOL) mode or microcontroller (MCU) mode; and a controller area network (CAN) mode, in which communication is performed over a CAN omnibus. Attention will first be turned to the CAN mode.

[0030] Before describing the configurations related to the various modes, however, a brief note about the nomenclature related to the communications elements is helpful. A foundational issue can be described as the communication between a primary device and a plurality of secondary devices that are connected in parallel to the primary device. In general the primary device is or includes a controller (e.g. a microcontroller) that transmits instructions to the secondary devices. In each example herein other than the examples in which communication occurs on a CAN omnibus, the primary device may be essentially synonymous with the controller, and the secondary devices are the devices that receive instruction from the controller. These secondary devices, however, may be configured in multiple device chains (e.g. corresponding to the parallel connection), such that a first plurality of secondary devices is grouped in a first device chain, and a second plurality of secondary devices is grouped in a second device chain. In examples in which the CAN omnibus is used, there may be a primary CAN node that includes the controller. Furthermore, the secondary devices may be configured in a first CAN node, and a second CAN node. In summary, the term “primary” as used herein is always associated with the controller and/or a node that includes the controller. The terms “first devices” and “second devices” are associated with secondary devices (e.g. devices other than the primary device; devices that are controlled by the primary device). [0031] Turning to the CAN omnibus configuration, the CAN mode relies on communication between devices (between the primary device and the one or more secondary devices and/or between the one or more secondary devices and one or more additional secondary devices) with a CAN bus. The CAN omnibus permits communication between devices without an intermediary host computer. The CAN omnibus utilizes a message-based protocol, in which signals are sent from a transmitting device to all other nodes on the CAN network. Each device on the CAN network is connected to a CAN node, which may include a microcontroller and transceiver. Each CAN node corresponds to a predetermined address, and messages are transmitted with a recipient node’s address in a message header.

[0032] FIG. 7 depicts a parallel connection of the primary CAN node 702 (e.g. the primary device) to a first CAN node 704 (e.g. a first secondary device chain with CAN circuitry) and a second CAN node 706 (e.g. a second secondary device chain with CAN circuitry), according to the CAN mode (e.g. using a CAN omnibus). The primary CAN node 702 includes at least a controller 710 (e.g. a microcontroller, a processor) and primary CAN circuitry 712. The skilled person will appreciate the requirements for the primary CAN circuitry 712, but the primary CAN circuitry 712 will generally include at least a processor and a transceiver (not depicted). The first CAN node 704 may include first CAN circuitry 720 and one or more first devices 722, 724, 726 (e.g. one or more first secondary devices), connected serially to one another. It is noted that the first CAN node 704 is depicted as including an exemplary number of three secondary devices; however, the actual number can be greater or fewer, without limitation. The second CAN node 706 may include second CAN circuitry 730 and one or more second devices 732, 734, and 736 (e.g. one or more second secondary devices), connected serially to one another. As with the first CAN node, the second CAN node 706 includes an exemplary number of three secondary devices, although the actual number may be greater or fewer. [0033] In this manner, each branch of each parallel connection is equipped with its own

CAN node, such that transmissions are received and routed to the intended destinations.

That is, a transmission from the controller 710 (e.g. the primary device) that is intended, for example, for secondary device 734 will be sent from the primary CAN node 702 (e.g. via the first CAN circuitry 712) to all other CAN nodes (e.g. in this case, to the first CAN node 704 and the second CAN node 706). This transmission will be received by CAN node 704, and specifically by first CAN circuitry 720, which will determine that the intended recipient, secondary device 734, is not within the device chain connected to first CAN circuitry 720, and the first CAN circuitry 720 will ignore this transmission. Conversely, CAN node 706, and specifically second CAN circuitry 730, will receive the transmission from the primary device 710 (e.g. from the primary CAN node 702) and will determine that the intended recipient, secondary device 734, is within the second device chain connected to second CAN circuitry 730. Accordingly, second CAN circuitry 730 will pass the message to secondary device 732, which will in turn pass the message to secondary device 734.

Because secondary device 734 is the intended recipient, secondary device 734 will not pass the transmission to secondary device 736.

[0034] This configuration solves the auto addressing problem generated by the parallel connection, in which the OSP auto addressing function may result in errors and or double use of the same address when used in parallel without the CAN omnibus configuration. In this configuration, each secondary device is assigned its own address, of which the corresponding CAN node has knowledge. That is, each secondary device may include a memory (or other device or configuration of devices capable of storing information) corresponding to a unique address for the secondary device. The corresponding CAN node has knowledge of each of the addresses for the secondary devices to which it is connected. In this manner, the CAN node may determine from a message header whether the intended recipient is among the devices connected to the CAN node. As stated above, if the intended recipient is among the devices connected to this CAN node, the CAN node will forward the message. If, however, the intended recipient is not 1 of the devices connected to the can mode, then the can mode will not forward the message.

[0035] This configuration also solves the problem of collisions among the parallel devices. The CAN system is robust and includes various protections against the generation of message collisions within the CAN omnibus network. Accordingly, use of a can omnibus system is sufficient to protect against colliding messages. This can omnibus configuration may be particularly useful when the primary device and at least one secondary device are located on different circuit boards, such that a cable or wire connection between devices is practical.

[0036] Turning to the non-CAN-omnibus configurations (e.g. the MCU modes), these configurations may be implemented without the need for a CAN node between the primary device and the parallel connected secondary devices. The MCU mode may be particularly useful when the primary device and at least one of the secondary devices are located on the same circuit board.

[0037] The MCU mode may be understood as “MCU mode, normal” or “MCU mode, end of line”. In the MCU mode, normal, a single input/output uses a single-ended mode for the signaling. In this manner, received signals may be encoded (e.g. using a Manchester code) and sent to the controller’s SIOx P port. For transmitting, the SIOx P port may be configured to deliver the signal in non-return to zero format. The SIOx N may be configured to deliver a corresponding clock signal. In MCU mode, end of line, the signal input/output port may consider itself to be at the end of the serial connection.

[0038] FIG. 8 depicts an exemplary implementation of the MCU mode. In this figure, a circuit board 802 includes a primary device 804 (e.g. the controller), secondary devices 806 and 808 (e.g. the first device chain and the second device chain), and optional CAN node 810. The primary device 804 (the controller) may transmit a message to the parallel- connected secondary devices 806 and 808. As with the CAN omnibus configurations, each secondary device (the device or devices in each of the first device chain and the second device chain) has its own unique address, which is stored locally on the secondary device or on a device (e.g. a memory) closely associated with the secondary device. The primary device 804 (the controller) sends the message with the address of the intended recipient, such as in the header. Due to the parallel connection, the message is received by both secondary devices (e.g. by the first device chain and the second device chain), which each assess the message for a recipient address corresponding to their own address or to an address within a serial chain to which they are connected. In one configuration, the first secondary device in each of the first device chain and the second device chain determine based on the unique identifier/address whether the message is intended for that particular device and, if not, they simply pass the message to the next device in the chain. In an alternative configuration, the first secondary device in each of the first device chain and the second device chain have access to, or “know”, the addresses of the remaining devices in their respective serial connections, and they determine whether the message is for a device in their serial connection. If so, then they pass the message to the next device, and if not, they disregard or delete the message. In this manner, the first secondary device of each of the first device chain and the second device chain may perform a gatekeeping function, according to this alternative configuration.

[0039] In an optional configuration, one or more of the secondary devices 806 808 may be further connected in serial to a CAN node 810 which may be configured to then transmit the message across a CAN omnibus to another CAN node as in the previously described configuration.

[0040] In a further optional configuration, each memory storing the unique identifier may include one or more one time programmable (OTP) memory flags. These OPT memory flags may each permit a sub ranging of the addresses. The unique identifier may optionally be stored such that the end user may utilize an electrical touch down to obtain ID/position of each device for storage in the controller.

[0041] In an optional configuration, a controller’s single input/output 2 (SIO2) port may be connected to ground or to a supply voltage when the OTP bit is set to a parallel mode, which will provide four different parallel addresses. In this manner, the device may be connected when the OPT is set to a parallel mode to permit auto-addressing.

[0042] In an optional configuration, a flag may be programmed to enable the parallel group addressing: e.g. when the parallel mode is enabled, such as through an LED channel 3, it may be possible to create seven different subranges with the same approach as above, using the external resistor.

[0043] Of note, the direct connection between the primary device and the plurality of parallel connected secondary devices (e.g. without the interim can bus) is associated with certain dangers arising out of conflicting messages. As can be seen from at least FIG. 6, the transmitters of a given node operate by selectively connecting the transmission line with either a supply voltage or a ground voltage, depending on the configuration. Should two nodes attempt to transmit concurrently, this can result in a short circuit, which may result in damage to any of the primary device, the secondary device, or a component of same. To prevent such damage, the primary device and/or the secondary device may be configured with a current limiter 824, 826, and/or 828. The current limiter may be any high impedance device or circuit, capable of limiting the current passing through the transmission lines between devices connected in parallel.

[0044] FIG. 9 depicts an alternative to the configuration depicted in FIG. 7. In this alternative configuration, FIG. 9 depicts a parallel connection of the primary device 902 to a first secondary device chain 912 and a second secondary device chain 922, according to the CAN mode (e.g. using a CAN omnibus). Primary device 902 includes at least a controller (e.g. a microcontroller, a processor) 904 and a CAN node 906. As described above with respect to FIG. 7, the CAN node 906 will generally include at least a processor and a transceiver (not depicted). The first secondary device chain 912 may include a CAN node 914 and one or more secondary devices 916, 918, and 920. The second secondary device chain 922 may include a CAN node 924 and one or more secondary devices 926, 928, and 930. In this configuration, and in contrast to the configuration depicted in FIG. 7, the secondary devices of the first secondary device chain 912 and the secondary devices of the second secondary device chain 922 are connected to their respective CAN nodes 914 and 924 in parallel. In this manner, the CAN node 906 of the primary device 902 sends a signal to all other CAN nodes, which causes the signal to be received by each of CAN node 914 and can no 924. Assuming, for example, that the signal is intended for secondary device 928, CAN node 914 will receive the signal, determine that the signal is not intended for any of its secondary devices, and ignore and/or dispose of the corresponding data. Conversely, CAN node 924 will receive the signal and determine that the signal is for secondary device 928. At which time, CAN node 924 will send the signal directly to secondary device 928. In a first optional configuration, CAN node 924 will send the signal to each of its secondary devices, namely 926, 928, and 930. At which time, each of the secondary devices will receive the signal and determine whether the signal is intended for that particular secondary device. If the signal is intended for that particular secondary device, the secondary device will decode/utilize the signal. If the signal is not intended for that secondary device, then the secondary device will ignore/dispose of the signal data. In a second optional configuration, CAN node 924 will transmit the signal directly, and only to the intended recipient. In this case, CAN node 924 would determine that the signal was intended for secondary device 928 and transmit the signal directly and only to secondary device 928.

[0045] FIG. 10 depicts a device control system, including a primary Controller Area Network (CAN) node 1002, including a controller 1004, configured to send a signal to a primary CAN circuitry 1006, for delivery to a first CAN node 1012 and a second CAN node 1022 via a CAN omnibus; wherein the signal includes a command and a unique identifier of a first device or a second device; the primary CAN circuitry 1006; the first CAN node 1012, including one or more first devices 1014, 1016, connected to one another in series, each device of the one or more first devices having a unique identifier; and first CAN circuitry 1018, configured to receive a signal from the primary CAN node 1002 via the CAN omnibus and to send data corresponding to the signal to a first device of the one or more first devices; the second CAN node 1022, including one or more second devices 1024, 1026, connected to one another in series, each device of the one or more second devices having a unique identifier; and second CAN circuitry 1028, configured to receive a signal from the primary CAN node 1002 via the CAN omnibus, and to send data corresponding to the signal to a second device of the one or more second devices 1024, 2026; wherein the first CAN node 1012 and the second CAN node 1022 are connected to the primary CAN node in parallel. As described above, and in an optional configuration, the one or more first devices 1014, 1016 of the first CAN node 1012 may be connected to the first CAN circuitry 1018 in parallel, rather than in serial. Similarly, the one or more second devices 1024, 1026 of the second CAN node 1022 may be connected to the second CAN circuitry 1028 in parallel, rather than in serial.

[0046] In some configurations, the one or more first devices 1014, 1016 and the one or more second devices 1024, 1026 may be intelligent light emitting diodes (LEDs). In this manner, the controller 1004 may be able to control the intelligent LEDs remotely by sending commands to the first CAN node 1012 and the second CAN node 1022 via the CAN omnibus. The parallel nature of the connections of the first CAN node 1012 and the second CAN node 1022 to the primary CAN node 1002 may permit simplified wiring, redundancy, and reduced latency compared to an approach in which each of the intelligent LEDs are connected to the controller 1004 in serial. [0047] FIG. 11 depicts an optional configuration in which the device control system may include a first device chain 1112 (e.g. a first chain of secondary devices), connected to an output port of a controller 1104, and including one or more first devices 1114, 1116, 1118 (e.g. one or more first secondary devices) connected to one another in series; wherein each of the one or more first devices has a unique identifier; a second device chain 1122 (e.g. a second chain of secondary devices), connected to the output port of the controller 1104, and including one or more second devices 1124, 1126, 1128 (e.g. one or more second secondary devices), connected to one another in series; wherein each of the one or more second devices has a unique identifier; wherein the first device chain 1112 is connected in parallel to the second device chain 1122; and the controller 1104, including the output port; wherein the first device chain 1112 and the second device chain 1122 are connected to the controller in parallel; wherein the controller 1104 is configured to send a signal concurrently to the first device chain and the second device chain via the output port; wherein the signal includes a command and the unique identifier of one of the one or more first devices or of the one or more second devices; and wherein the one or more first devices and the one or more second devices are intelligent light emitting diodes.

[0048] Each of the intelligent light emitting diodes may include a unique identifier storage (not pictured), in which the unique identifier corresponding to the corresponding intelligent light emitting diode is stored, and a processor, configured to cause the corresponding light emitting diode to illuminate according to the command if the unique identifier of the signal matches the unique identifier of the unique identifier storage.

[0049] In an optional configuration, the first device chain and the second device chain are on a common substrate with the controller. Alternatively, at least one of the first device chain 1112 or the second device chain 1122 may be on a separate substrate from the controller. [0050] The device control system may optionally be configured to implement a low impedance mode when the controller 1104 sends the signal and to implement a high impedance mode when the controller 1104 does not send the signal. The device control system may further include a current limiter, which may be configured to limit a current to the first device chain or the second device chain.

[0051] A vehicle may include the device control system as described above. In this manner, the device control system may contribute to the vehicle obtaining a safety certification, such as, for example, a functional safety certification. The functional safety certification may be, for example, a certification under ISO) standard 26262:2018, “Road vehicles — Functional safety”.

[0052] To control individual secondary devices (e.g. to control individual intelligent LEDs), it is necessary that each secondary device have a unique identifier. This unique identifier may be analogous to an address. Such identifier may be included in a signal from the primary device to the secondary devices. The wherein the first CAN circuitry is configured to send the data corresponding to the signal to a first device of the one or more first devices if the unique identifier of the signal corresponds to a unique identifier of a first device of the one or more first devices; and wherein the second CAN circuitry is configured to send the data corresponding to the signal to a second device of the one or more second devices if the unique identifier of the signal corresponds to a unique identifier of a second device of the one or more second devices. The communication protocol used may include a portion of the data packet in which the unique identifier is sent. For example, in OSP, the unique identifier may be sent in the header.

[0053] The unique identifiers of the secondary devices connected to a CAN node may be known to the corresponding CAN circuitry. In this manner, the CAN circuitry may decode a signal, or at least partially decode the signal sufficiently to determine the unique identifier, and then determine whether the unique identifier corresponds to any secondary device connected to the CAN circuitry. The CAN circuitry may be configured not to send the data corresponding to the command to its one or more first devices (or in the case of a CAN circuitry on the second CAN node, to the one or more second devices) if the unique identifier of the signal does not correspond to a unique identifier of any device connected to the CAN circuitry.

[0054] This unique identifier may be stored in a local memory of the respective one or more first devices and the one or more second devices. As stated above, the unique identifiers of the devices connected to a particular CAN node are also known to that CAN node. Furthermore, the unique identifiers may be stored in the primary CAN node and/or the controller, such that instructions from the controller may be routed to a desired device. [0055] Although the skilled person will appreciate the contents of CAN circuitry, the primary CAN circuitry may include at least a transceiver, which may be configured to receive a signal from a primary CAN controller and to send a corresponding signal on the CAN omnibus. Alternatively or additionally, the transceiver may be configured to receive a signal from the CAN omnibus and send a corresponding signal to the primary CAN controller. The CAN circuitry may further include a CAN controller. The CAN controller may be distinct from the controller 1004, as the controller 1004 may be tasked with management of the secondary devices, while the CAN controller may be tasked primarily with managing transmissions between CAN nodes.

[0056] Similarly, each of the first CAN circuitry and the second CAN circuitry may include a transceiver, which may be configured to receive a signal from a respective first CAN controller or second CAN controller and to send a corresponding signal on the CAN omnibus, or to receive a signal from the CAN omnibus and send a corresponding signal to the respective first CAN controller or second CAN controller. [0057] The controller is configured 1004 may be configured to output the signal as a transistor-transistor-logic signal. In this manner, the primary CAN circuitry may be configured to convert the transistor-transistor-logic signal to a CAN omnibus signal. [0058] The device control system may further include a current limiter. The current limiter may be a high impedance device that is configured to limit a current to the first device chain or the second device chain. The use of this current limiter may avoid the risk of short-circuit or excessive current flow in a situation in which two secondary devices attempt to communicate concurrently. Various mechanisms for limiting current flow are known, and any such mechanism may be utilized, depending on the implementation. In this manner, when one of the secondary devices transmits, then a conflict of impedance is created with the remaining secondary devices in idle state.

[0059] In this manner, a communication driver may only be active when in a transmit state, and will otherwise exhibit a high impedance. A separate clock line may always be under control of the controller. In this configuration, the controller may control when a secondary device can transmit data back to the controller.

[0060] In an optional configuration, the transmission between devices may be configured to use a universal asynchronous receiver-transmitter (UART) protocol. In this manner, the controller’s transmit line may always be under the control of the controller. The secondary device may then only be driven when in transmit state and may otherwise exhibit a high impedance. It is expressly noted that the UART procedure may be optionally combined with the configurations in which one or more CAN nodes are used to transmit over the CAN omnibus.

[0061] In an optional configuration, the controller may include a first terminal and a second terminal. In this manner, the controller may be configured to send the signal via the first terminal. The controller is may be configured to receive data from the CAN omnibus via the second terminal. [0062] In this mode, the single input/output SIOx P may always be in an output state and may transmit an encoded signal (e.g. encoded in Manchester code). The single input/output SIOx N may always be in input state and may receive encoded signals (e.g. encoded in Manchester code).

[0063] The principles and methods disclosed herein may permit for the connection of multiple secondary devices to a primary device in parallel. This may have particular usefulness in the context of vehicles and vehicle safety. In this manner, any aspect of this disclosure may be utilized in a vehicle, such that the vehicle includes the device control system disclosed herein. This may permit the vehicle to operate the secondary devices with redundancy, which may qualify, or partially qualify, the vehicle for one or more safety certification levels. For example, the added redundancy may contribute to a safety certification under ISO standard 26262:2018, “Road vehicles — Functional safety”. In addition to the redundancy benefit of the principles and methods disclosed herein, the parallel connection of the secondary devices to the primary device may reduce latency in communications and simplify wiring or other physical connections between devices.

[0064] The principles and methods disclosed herein may be utilized with any signal encoding technique for transmission of the signal between the primary device and the secondary devices. In one optional configuration, the signals may be transmitted using a Manchester code. Other options for encoded transmissions include, but are not limited to, any other form of phase-shift keying (PSK), frequency-shift keying (FSK), amplitude-shift keying (ASK), quadrature amplitude modulation (QAM), or otherwise.

[0065] In an optional configuration, the primary device may be configured to send a broadcast to each of the secondary devices or to a subset of a plurality of the secondary devices. This may be achieved, for example, by reserving one or more unique identifies / addresses for a broadcast transmission. [0066] It is expressly noted that references to the CAN bus / CAN omnibus herein relate to the physical level of the CAN omnibus, which may include and/or relate to the electrical signals and/or electrical signal levels. This is in contrast to the logical level of the CAN omnibus, such as the bit fields, CAN protocol, etc., which are generally not intended by the references to the CAN omnibus herein.

[0067] While the above descriptions and connected figures may depict components as separate elements, skilled persons will appreciate the various possibilities to combine or integrate discrete elements into a single element. Such may include combining two or more circuits for form a single circuit, mounting two or more circuits onto a common chip or chassis to form an integrated element, executing discrete software components on a common processor core, etc. Conversely, skilled persons will recognize the possibility to separate a single element into two or more discrete elements, such as splitting a single circuit into two or more separate circuits, separating a chip or chassis into discrete elements originally provided thereon, separating a software component into two or more sections and executing each on a separate processor core, etc.

[0068] Further aspects of the disclosure will be made by way of example:

[0069] In Example 1, a device control system, including a primary Controller Area Network (CAN) node, including: a controller, configured to send a signal to a primary CAN circuitry, for delivery to a first CAN node and a second can NODE via a CAN omnibus; wherein the signal includes a command and a unique identifier of a first device or a second device; the primary CAN circuitry; the first CAN node, including: one or more first devices, connected to one another in series, each device of the one or more first devices having a unique identifier; and first CAN circuitry, configured to receive a signal from the primary CAN node via the CAN omnibus and to send data corresponding to the signal to a first device of the one or more first devices; the second CAN node, including: one or more second devices, connected to one another in series, each device of the one or more second devices having a unique identifier; and second CAN circuitry, configured to receive a signal from the primary CAN node via the CAN omnibus, and to send data corresponding to the signal to a second device of the one or more second devices; wherein the first CAN node and the second CAN node are connected to the primary CAN node in parallel

[0070] In Example 2, the device control system of Example 1, wherein the one or more first devices and the one or more second devices are intelligent light emitting diodes.

[0071] In Example 3, the device control system of Example 1 or 2, wherein the first CAN circuitry is configured to send the data corresponding to the signal to a first device of the one or more first devices if the unique identifier of the signal corresponds to a unique identifier of a first device of the one or more first devices; and wherein the second CAN circuitry is configured to send the data corresponding to the signal to a second device of the one or more second devices if the unique identifier of the signal corresponds to a unique identifier of a second device of the one or more second devices.

[0072] In Example 4, the device control system of Example 3, wherein the first CAN circuitry is further configured not to send the data corresponding to the command to the first device of the one or more first devices if the unique identifier of the signal does not correspond to a unique identifier of any device of the one or more first devices; and wherein the second CAN circuitry is further configured not to send the data corresponding to the command to the second device of the one or more second devices if the unique identifier of the signal does not correspond to a unique identifier of any device of the one or more second devices.

[0073] In Example 5, the device control system of any one of Examples 1 to 4, wherein the first CAN circuitry is connected in serial to the one or more first devices and/or wherein the second CAN circuitry is connected in serial to the one or more second devices. [0074] In Example 6, the device control system of any one of Examples 1 to 5, wherein the first CAN circuitry is connected in parallel to the one or more first devices and/or wherein the second CAN circuitry is connected in parallel to the one or more second devices.

[0075] In Example 7, the device control system of any one of Examples 1 to 6, wherein the unique identifier of each of the one or more first devices and the one or more second devices is stored in a local memory of the respective one or more first devices and the one or more second devices; and wherein the unique identifiers are further stored in the primary CAN node.

[0076] In Example 8, the device control system of any one of Examples 1 to 7, wherein the primary CAN circuitry includes: a transceiver, configured to receive a signal from a primary CAN controller and to send a corresponding signal on the CAN omnibus, or to receive a signal from the CAN omnibus and send a corresponding signal to the primary CAN controller; and the primary CAN controller.

[0077] In Example 9, the device control system of any one of Examples 1 to 8, wherein the first CAN circuitry includes: a transceiver, configured to receive a signal from a first CAN controller and to send a corresponding signal on the CAN omnibus, or to receive a signal from the CAN omnibus and send a corresponding signal to the first CAN controller; and the first CAN controller; and wherein the second CAN circuitry includes: a transceiver, configured to receive a signal from a second CAN controller and to send a corresponding signal on the CAN omnibus, or to receive a signal from the CAN omnibus and send a corresponding signal to the second CAN controller; and the second CAN controller.

[0078] In Example 10, the device control system of 9, wherein the controller is configured to output the signal as a transistor-transistor-logic signal, and wherein the primary CAN circuitry is configured to convert the transistor-transistor-logic signal to a CAN omnibus signal. [0079] In Example 11, the device control system of any one of Examples 1 to 10, wherein the device control system further includes a current limiter, configured to limit a current to the first device chain or the second device chain.

[0080] In Example 12, the device control system of Example 11, wherein the one or more first devices and the one or more second devices are intelligent light emitting diodes; wherein the controller is a first controller, and wherein each intelligent light emitting diode of the one or more first devices and the one or more second devices includes a second controller, configured to execute the command if the unique identifier in the signal corresponds to the unique identifier of the corresponding one or more first devices or one or more second devices.

[0081] In Example 13, the device control system of any one of Examples 1 to 12, wherein the controller includes a first terminal and a second terminal, and wherein the controller is configured to send the signal via the first terminal, and wherein the controller is configured to receive data from the CAN omnibus via the second terminal.

[0082] In Example 14, the a vehicle including the device control system of any one of Examples 1 to 13.

[0083] In Example 15, the vehicle of Example 14, wherein the device control system satisfies International Standards Organization (ISO) standard 26262:2018, “Road vehicles — Functional safety”.

[0084] In Example 16, a device control system, including: a first device chain, connected to an output port of a controller, and including one or more first devices, connected to one another in series; wherein each of the one or more first devices has a unique identifier; a second device chain, connected to the output port of the controller, and including one or more second devices, connected to one another in series; wherein each of the one or more second devices has a unique identifier; wherein the first device chain is connected in parallel to the second device chain; and the controller, including the output port; wherein the first device chain and the second device chain are connected to the controller in parallel; wherein the controller is configured to send a signal concurrently to the first device chain and the second device chain via the output port; wherein the signal includes a command and the unique identifier of one of the one or more first devices or of the one or more second devices; and wherein the one or more first devices and the one or more second devices are intelligent light emitting diodes.

[0085] In Example 17, the device control system of Example 16, wherein each of the intelligent light emitting diodes includes a unique identifier storage, in which the unique identifier corresponding to the corresponding intelligent light emitting diode is stored, and a processor, configured to cause the corresponding light emitting diode to illuminate according to the command if the unique identifier of the signal matches the unique identifier of the unique identifier storage.

[0086] In Example 18, the device control system of Example 16 or 17, wherein the first device chain and the second device chain are on a common substrate with the controller. [0087] In Example 19, the device control system of Example 16 or 17, wherein at least one of the first device chain or the second device chain is on a separate substrate from the controller.

[0088] In Example 20, the device control system of any one of Examples 16 to 19, wherein the device control system is configured to implement a low impedance mode when the controller sends the signal and to implement a high impedance mode when the controller does not send the signal.

[0089] In Example 21, the device control system of any one of Examples 16 to 20, wherein the device control system further includes a current limiter, configured to limit a current to the first device chain or the second device chain.

[0090] In Example 22, a vehicle including the device control system of any one of Examples

16 to 21. [0091] In Example 23, the vehicle of Example 22, wherein the device control system satisfies International Standards Organization (ISO) standard 26262:2018, “Road vehicles — Functional safety”

[0001] It is appreciated that implementations of methods detailed herein are demonstrative in nature, and are thus understood as capable of being implemented in a corresponding device. Likewise, it is appreciated that implementations of devices detailed herein are understood as capable of being implemented as a corresponding method. It is thus understood that a device corresponding to a method detailed herein may include one or more components configured to perform each aspect of the related method.

[0002] All acronyms defined in the above description additionally hold in all claims included herein.

Reference Numbers

102 primary device

104a-e secondary devices, in serial

202 primary device

204-212 secondary devices, in parallel

302 primary device

304a-312a secondary devices, in parallel

304b-312b secondary devices, in serial 402 primary device 404-412 secondary devices, in parallel

408a-408c secondary devices, in serial

502 primary device

504a-512a secondary devices, in parallel

504b-512b secondary devices, in serial

508b 1-2 secondary devices, further parallel branch

602 secondary device, configuration

604 first transmission line

606 second transmission line

608 third transmission line

610 fourth transmission line

612 resistor

702 primary CAN node

704 first CAN node

706 second CAN node

710 controller

712 primary CAN circuitry

720 first CAN circuitry

722-726 one or more first devices

730 second CAN circuitry

732-736 one or more second devices

802 circuit board

804 primary device

806-808 secondary devices

810 optional CAN node 24-828 optional current limiter 02 primary device 04 controller 06 CAN node, primary device 12 first secondary device chain 14 CAN node for first secondary devices 16-920 first secondary devices 922 second secondary device chain 924 CAN node for second secondary devices 926-930 second secondary devices 1002 CAN node 1004 controller 1006 primary CAN circuitry 1012 first CAN node 1014-1018 first devices in series 1022 second CAN node

1024-1028 second devices in series 1104 controller 1112 first device chain

1114-1118 one or more first devices 1122 second device chain 1124-1128 one or more second devices

Claims

1. A device control system, comprising: a primary node (1002), comprising: a controller (1004), configured to send a signal to a primary circuitry (1006), for delivery to a first node (1012) and a second node(1022) via an omnibus; wherein the signal comprises a command and a unique identifier of a first device or a second device; the primary circuitry (1006); the first node (1012), comprising: one or more first devices (1014, 1016), connected to one another in series, each device of the one or more first devices having a unique identifier; and first circuitry (1018), configured to receive a signal from the primary node (1102) via the omnibus and to send data corresponding to the signal to a first device of the one or more first devices; the second node (1022), comprising: one or more second devices (1024, 1026), connected to one another in series, each device of the one or more second devices having a unique identifier; and second circuitry (1028), configured to receive a signal from the primary node (1002) via the omnibus, and to send data corresponding to the signal to a second device of the one or more second devices (1024, 1026); wherein the first node (1012) and the second node (1022) are connected to the primary node (1002) in parallel; wherein the signal comprises a recipient address; wherein a first device (1014) of the one or more first devices (1014, 1016) is associated with a first address subrange, and wherein the first device (1014) is configured to send the signal to another of the one or more first devices if a subrange of the recipient address corresponds to the first address subrange; wherein a second device (1024) of the one or more second devices (1024, 1026) is associated with a second address subrange, different from the first address subrange; and and wherein the second device (1024) is configured to send the signal to another of the one or more second devices if a subrange of the recipient address corresponds to the second address subrange.

2. The device control system of claim 1, wherein the one or more first devices (1014, 1016) and the one or more second devices (1024, 1026) are intelligent light emitting diodes.

3. The device control system of claim 1 or 2, wherein the first circuitry (1018) is configured to send the data corresponding to the signal to a first device of the one or more first devices if the unique identifier of the signal corresponds to a unique identifier of a first device of the one or more first devices; and wherein the second circuitry (1028) is configured to send the data corresponding to the signal to a second device of the one or more second devices if the unique identifier of the signal corresponds to a unique identifier of a second device of the one or more second devices.

4. The device control system of claim 3, wherein the first circuitry (1018) is further configured not to send the data corresponding to the command to the first device of the one or more first devices if the unique identifier of the signal does not correspond to a unique identifier of any device of the one or more first devices; and wherein the second circuitry (1028) is further configured not to send the data corresponding to the command to the second device of the one or more second devices if the unique identifier of the signal does not correspond to a unique identifier of any device of the one or more second devices.

5. The device control system of any one of claims 1 to 4, wherein the first circuitry (1018) is connected in serial to the one or more first devices and/or wherein the second circuitry (1028) is connected in serial to the one or more second devices.

6. The device control system of any one of claims 1 to 5, wherein the first circuitry (1018) is connected in parallel to the one or more first devices and/or wherein the second circuitry (1028) is connected in parallel to the one or more second devices.

7. The device control system of any one of claims 1 to 6, wherein the unique identifier of each of the one or more first devices and the one or more second devices is stored in a local memory of the respective one or more first devices and the one or more second devices; and wherein the unique identifiers are further stored in the primary node.

8. The device control system of any one of claims 1 to 7, wherein the primary circuitry (1006) comprises: a transceiver, configured to receive a signal from a primary controller and to send a corresponding signal on the omnibus, or to receive a signal from the omnibus and send a corresponding signal to the primary controller; and the primary controller.

9. The device control system of any one of claims 1 to 8, wherein the first circuitry (1018) comprises: a transceiver, configured to receive a signal from a first controller and to send a corresponding signal on the omnibus, or to receive a signal from the omnibus and send a corresponding signal to the first controller; and the first controller; and wherein the second circuitry comprises: a transceiver, configured to receive a signal from a second controller and to send a corresponding signal on the omnibus, or to receive a signal from the omnibus and send a corresponding signal to the second controller; and the second controller.

10. The device control system of 9, wherein the controller is configured to output the signal as a transistor-transistor-logic signal, and wherein the primary circuitry is configured to convert the transistor-transistor-logic signal to a omnibus signal.

11. The device control system of any one of claims 1 to 10, wherein the device control system further comprises a current limiter, configured to limit a current to the first device chain or the second device chain.

12. The device control system of claim 11, wherein the one or more first devices and the one or more second devices are intelligent light emitting diodes; wherein the controller is a first controller, and wherein each intelligent light emitting diode of the one or more first devices and the one or more second devices comprises a second controller, configured to execute the command if the unique identifier in the signal corresponds to the unique identifier of the corresponding one or more first devices or one or more second devices.

13. The device control system of any one of claims 1 to 12, wherein the controller (1004) comprises a first terminal and a second terminal, and wherein the controller (1004) is configured to send the signal via the first terminal, and wherein the controller is configured to receive data from the omnibus via the second terminal.

14. The device control system of any one of claims 1 to 13, wherein the first device (1014) is configured to not send the signal to the another of the one or more first devices if the subrange of the recipient address does not correspond to the first address subrange; and wherein the second device (1024) is configured to not send the signal to another of the one or more second devices if a subrange of the recipient address does not correspond to the second address subrange.

15. The device control system of any one of claims 1 to 14, wherein the first device (1014) is configured to determine the first address subrange at start-up, and wherein the second device (1024) is configured to determine the second address subrange at start up.

16. The device control system of claim 15, wherein the first address subrange is stored in a first memory, and the second address subrange is stored in a second memory; and wherein the first device (1014) is configured to determine the first address subrange at start-up by reading the first address subrange from the first memory, and wherein the second device (1024) is configured to determine the second address subrange at start-up by reading the second address subrange from the second memory.

17. The device control system of claim 15, further comprising one or more first ohmic resistors, corresponding to the first address subrange, and one or more second ohmic resistors, corresponding to the second address subrange; wherein the first device (1014) is configured to determine the first address subrange at start-up by measuring a resistance of the one or more first ohmic resistors, or a current or voltage at the one or more first ohmic resistors, and wherein the second device (1024) is configured to determine the second address subrange at start-up by measuring a resistance of the one or more second ohmic resistors, or a current or voltage at the one or more second ohmic resistors,

18. The device control system of any one of claims 1 to 17, wherein the first device of the one or more first devices is a main first device and all other devices of the one or more first devices are ancillary first devices; wherein the ancillary first devices are each configured to receive their respective recipient address via a message; wherein the second device of the one or more second devices is a main second device and all other devices of the one or more second devices are ancillary second devices; wherein the ancillary second devices are each configured to receive their respective recipient address via a message;

19. A vehicle comprising the device control system of any one of claims 1 to 18.

20. The vehicle of claim 19, wherein the device control system satisfies International Standards Organization (ISO) standard 26262:2018, “Road vehicles — Functional safety”.

21. A device control system, comprising: a first device chain (1112), connected to an output port of a controller (1104), and comprising one or more first devices (1114, 1116, 1118), connected to one another in series; wherein each of the one or more first devices (1114, 1116, 1118) has a unique identifier; a second device chain (1122), connected to the output port of the controller (1104), and comprising one or more second devices (1124, 1126, 1128), connected to one another in series; wherein each of the one or more second devices (1124, 1126, 1128) has a unique identifier; wherein the first device chain (1112) is connected in parallel to the second device chain (H22); and the controller (1104), comprising the output port; wherein the first device chain (1112) and the second device (1122) chain are connected to the controller (1104) in parallel; wherein the controller (1104) is configured to send a signal concurrently to the first device chain (1112) and the second device chain (1122) via the output port; wherein the signal comprises a command and the unique identifier of one of the one or more first devices (1114, 1116, 1118) or of the one or more second devices (1124, 1126, 1128); and wherein the one or more first devices (1114, 1116, 1118) and the one or more second devices (1124, 1126, 1128) are intelligent light emitting diodes.

22. The device control system of claim 21, wherein each of the intelligent light emitting diodes comprises a unique identifier storage, in which the unique identifier corresponding to the corresponding intelligent light emitting diode is stored, and a processor, configured to cause the corresponding light emitting diode to illuminate according to the command if the unique identifier of the signal matches the unique identifier of the unique identifier storage.

23. The device control system of claim 21 or 22, wherein the first device chain (1112) and the second device chain (1122) are on a common substrate with the controller (1104).

24. The device control system of claim 21 or 22, wherein at least one of the first device chain (1112) or the second device chain (1122) is on a separate substrate from the controller (1104).

25. The device control system of any one of claims 21 to 24, wherein the device control system is configured to implement a low impedance mode when the controller (1104) sends the signal and to implement a high impedance mode when the controller (1104) does not send the signal.