EP3015994A1 - Flexible sent device configuration - Google Patents

Flexible sent device configuration Download PDF

Info

Publication number
EP3015994A1
EP3015994A1 EP15191631.9A EP15191631A EP3015994A1 EP 3015994 A1 EP3015994 A1 EP 3015994A1 EP 15191631 A EP15191631 A EP 15191631A EP 3015994 A1 EP3015994 A1 EP 3015994A1
Authority
EP
European Patent Office
Prior art keywords
data
configuration
diagnostic
sent
integrated circuit
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
EP15191631.9A
Other languages
German (de)
French (fr)
Other versions
EP3015994B1 (en
Inventor
Ivan SHEVELENOK
Asparuh GRIGOROV
Viktor Kassovski
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Melexis Technologies NV
Original Assignee
Melexis Technologies NV
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Melexis Technologies NV filed Critical Melexis Technologies NV
Publication of EP3015994A1 publication Critical patent/EP3015994A1/en
Application granted granted Critical
Publication of EP3015994B1 publication Critical patent/EP3015994B1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/445Program loading or initiating
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0766Error or fault reporting or storing
    • G06F11/0772Means for error signaling, e.g. using interrupts, exception flags, dedicated error registers
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0706Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
    • G06F11/0736Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in functional embedded systems, i.e. in a data processing system designed as a combination of hardware and software dedicated to performing a certain function
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0751Error or fault detection not based on redundancy
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0766Error or fault reporting or storing
    • G06F11/0778Dumping, i.e. gathering error/state information after a fault for later diagnosis
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/34Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38Information transfer, e.g. on bus
    • G06F13/382Information transfer, e.g. on bus using universal interface adapter
    • G06F13/385Information transfer, e.g. on bus using universal interface adapter for adaptation of a particular data processing system to different peripheral devices
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38Information transfer, e.g. on bus
    • G06F13/42Bus transfer protocol, e.g. handshake; Synchronisation
    • G06F13/4282Bus transfer protocol, e.g. handshake; Synchronisation on a serial bus, e.g. I2C bus, SPI bus
    • G06F13/4295Bus transfer protocol, e.g. handshake; Synchronisation on a serial bus, e.g. I2C bus, SPI bus using an embedded synchronisation

Definitions

  • the invention relates to the field of data transmission according to the Single Edge Nibble Transmission (SENT) standard. More specifically, it relates to an integrated circuit device, e.g. a SENT transmitter device such as a SENT-capable sensor, for transmitting data via the SENT protocol and a related method for implementing the SENT protocol in integrated circuits in an application independent manner.
  • SENT Single Edge Nibble Transmission
  • the SENT protocol (SAE J2716 standard) provides signal transmission from a transmitter device, e.g. an integrated circuit (IC) sensor, to a receiver device, e.g. an Electronic Control Unit (ECU).
  • IC integrated circuit
  • ECU Electronic Control Unit
  • the SENT protocol may for example provide a low-cost and efficient alternative to, for example, analogue or PWM interfaces for sensor applications.
  • the SENT encoding scheme may be particularly suitable for use in applications where high resolution sensor data needs to be communicated from a sensor to an ECU.
  • the SENT standard defines a unidirectional communications scheme from a transmitting device, e.g. a sensor, to a receiving device, e.g. a controller, which does not require a coordination and/or synchronization signal from the receiving device.
  • the transmission may proceed independently of the receiver module.
  • An integrated circuit sensor for automotive applications may provide an output mode for reporting sensor information and/or other diagnostic information, such as cyclic redundancy check (CRC) information, via a SENT telegram compliant with the SAE-J2716 Surface Vehicle Information Report standard.
  • CRC cyclic redundancy check
  • the number of nibbles is typically fixed for each application of the encoding scheme, but can vary between applications.
  • An integrated circuit (IC) device for SENT communication may use a fixed configuration for its communication channels, e.g. defining a data mapping to fast and slow channels.
  • a device e.g. a transmitter or receiver device as known in the art, that is adapted for SENT communication may have a configuration-specific hardware design or firmware to take the SENT protocol configuration into account.
  • the SENT serial data communication protocol may be used for transmission of signal values, e.g. messages, from a transmitter device to a receiver device with high resolution.
  • the implementation of the SENT protocol in IC implies a fixed user message configuration for its communication channels, e.g. fast and slow channels.
  • the configuration may depend on the intended application, and changing the configuration in order to address different applications may require redesign of the IC hardware and/or firmware.
  • the configuration may be hardwired, such that the IC device is specifically designed for a single configuration corresponding to a specific application.
  • the IC device may be provided by a read-only memory (ROM) which can be programmed for a specific SENT message configuration.
  • ROM read-only memory
  • the IC can be redesigned for a different configuration by adapting the firmware accordingly; however, the end-product device provided with such application-specific ROM may be only suitable for use in the configuration the firmware is designed for.
  • the device may comprise a one-time programmable non-volatile memory (OTP), such that the change of the SENT message configuration can be realized through programming the device with a suitable software construct, taking into account the restrictions of the available memory space.
  • OTP one-time programmable non-volatile memory
  • a device can be programmed to a specific application after manufacturing but prior to use.
  • an IC device may also comprise a FLASH memory or an electrically erasable programmable read-only memory (EEPROM), such that the change of the SENT message configuration can be realized through software change, taking into account restrictions of the available memory space.
  • EEPROM electrically erasable programmable read-only memory
  • Configuration of an integrated circuit SENT transmitter device may comprise, for the SENT fast channels, e.g. the data transmitted via the data nibbles, defining the number of channels, the information associated with each channel, the data nibbles order format, the method of status bits processing, the fast channel diagnostic error codes and the reporting priority of the fast channel diagnostic error codes.
  • configuration for the SENT slow channels may further comprise the defining of the association of every SENT slow channel message with an ID number, an ID memory location, a message order, the slow channel diagnostic error codes and the reporting priority of slow channel diagnostic error codes.
  • the present invention relates to an integrated circuit device comprising an output port for transmitting a data stream, a processing means for controlling the transmission of the data stream in accordance with a single-edge nibble transmission protocol, and a configuration means for receiving and storing configuration data.
  • the processing means is adapted for, e.g. configured or programmed for, reporting a plurality of diagnostic statuses via the data stream by transmitting for each diagnostic status a corresponding diagnostic code defined by the configuration data.
  • the processing means is furthermore adapted for reporting the plurality of diagnostic statuses in a diagnostic status reporting order defined by the configuration data.
  • the configuration means may be adapted for receiving configuration instructions from a user and for storing this configuration data in accordance with the configuration instructions.
  • the processing means may be adapted for retrieving at least one address pointer from the configuration means.
  • the at least one address pointer may reference data or may reference a program routine for acquiring this data, in which the data is to be transmitted in a corresponding SENT fast channel or in a corresponding SENT slow channel message of the data stream.
  • the processing means may be adapted for detecting the plurality of diagnostic statuses and for setting a status bit state in a status and communication nibble transmitted via the data stream taking into account the detected diagnostic statuses and a status bit mask in the configuration data.
  • the processing means may be adapted for reporting at least one diagnostic status of the plurality of diagnostic statuses by transmitting a diagnostic code value via a SENT fast channel.
  • the processing means may be adapted for reporting at least one diagnostic status of the plurality of diagnostic statuses by transmitting a diagnostic code value via a SENT slow channel message.
  • the processing means may be adapted to retrieve at least one value from the configuration means for selecting the number of nibbles to transmit per SENT telegram.
  • the configuration means may comprise a configuration memory for storing the configuration data.
  • An integrated circuit device may furthermore comprise input/output means for acquiring and digitizing data.
  • the processing means may comprise a data memory and an instruction memory.
  • the instruction memory may comprise instructions according to a program logic for controlling the input/output means such as to acquire and digitize data, and for controlling the data transmission via the output port such as to comply with the SENT protocol.
  • the present invention relates to a method for controlling an integrated circuit device adapted for transmitting data via a data stream in accordance with a single-edge nibble transmission protocol.
  • the method comprises receiving configuration instructions from a user, storing configuration data in accordance with the configuration instructions, and controlling a transmission of a data stream in accordance with a single-edge nibble transmission protocol.
  • This controlling of the transmission of the data stream comprises reporting a plurality of diagnostic statuses via the data stream by transmitting for each diagnostic status a corresponding diagnostic code defined by the configuration data. Reporting the plurality of diagnostic statuses is furthermore performed in a diagnostic status reporting order defined by the configuration data.
  • the controlling of the transmission may furthermore comprise retrieving at least one address pointer from the configuration data in order to reference data or reference a program routine for acquiring this data, and transmitting the data in a corresponding SENT fast channel or in a corresponding SENT slow channel message of the data stream.
  • the controlling of the transmission may comprise detecting the plurality of diagnostic statuses and setting a status bit state in a status and communication nibble transmitted via the data stream taking into account the detected diagnostic statuses and a status bit mask in the configuration data.
  • the reporting of the plurality of diagnostic statuses may comprise transmitting a diagnostic code value via a SENT fast channel and/or via a SENT slow channel message.
  • the SENT configuration can be changed without requiring a hardware or firmware update of the transmitter device, e.g. without requiring hardware or software redesign.
  • SENT Single Edge Nibble Transmission
  • SAE J2716 a protocol, such as the SAE J2716 standard, that defines a transmission telegram consisting of a plurality of nibbles in sequence, in which each nibble consists of 4 bits coded by Pulse Width Modulation (PWM) with reference to the falling edge, hence the term "single edge nibble" in the protocol acronym.
  • PWM Pulse Width Modulation
  • the first nibble of such telegram e.g. directly following a synchronization pulse, may for example contain internal status and diagnostic information. This first nibble may be followed by one to six data nibbles, e.g. for reporting sensor information.
  • a final nibble in the transmission telegram may for example comprise redundancy check information.
  • nibbles may be fixed for a specific application of the encoding scheme, this number may vary between applications. For example, if one 12-bit value is to be transmitted, three data nibbles may be used, while if two 8-bit values need to be transmitted, four data nibbles may be used.
  • SENT may also provide a mechanism for broadcasting information at a much slower rate, for example for communicating information that is less time-critical, such as conversion coefficients from raw data to physical values, the manufacturer's name, the type of sensor or an serial identification tag of the sensor.
  • This mechanism may rely on bits in the status and communication (S&C) nibble of the SENT telegram, e.g. two bits in the S&C nibble may be designated to convey the slow channel. These bits may be accumulated from a plurality of consecutive telegrams, e.g. from 16 or 18 adjacent messages, and grouped to form a message ID, a message value and a CRC.
  • S&C status and communication
  • the present invention relates to an integrated circuit (IC) device comprising an output port for transmitting a data stream; a processing means, e.g. a processor, for controlling the transmission of this data stream in accordance with a single-edge nibble transmission protocol; and a configuration means for receiving and storing configuration data, e.g. for receiving configuration instructions from a user and for storing configuration data corresponding to these configuration instructions.
  • the processing means is adapted for reporting a plurality of diagnostic statuses, e.g. errors, via the data stream by transmitting for each diagnostic status a corresponding diagnostic code defined by the configuration data.
  • the processing means is furthermore adapted for reporting this plurality of diagnostic statuses in a diagnostic status reporting order defined by the configuration data.
  • the integrated circuit device 1 may be an application specific standard product (ASSP) for collecting and transmitting sensor data.
  • ASSP application specific standard product
  • product flexibility is preferred in order to serve multiple end users, which makes an extra cost for using CPU resources cost effective as it avoids the cost of redesigns.
  • This device may provide an output mode for reporting data, e.g. sensor information and/or diagnostic information, via SENT telegrams compliant with the SAE-J2716 Surface Vehicle Information Report.
  • the integrated circuit sensor may be a SENT transmitter device, e.g. a SENT data transmitter.
  • the device 1 comprises an output port 5 for transmitting a data stream, e.g. for relaying SENT telegrams over a wire harness to a receiving node, such as a SENT receiver device.
  • the data may be transmitted to an engine control unit.
  • the integrated circuit device may also comprise input/output means 6 for acquiring and digitizing data, e.g. sensor data.
  • the input/output means may comprise output signal lines for controlling the acquisition and digitization of data by a sensor component and input signal lines for receiving digitized data from this sensor component.
  • the integrated circuit device 1 further comprises a processing means 2, e.g. a processor, for controlling the transmission of the data stream in accordance with a single-edge nibble transmission protocol, e.g. in accordance with the SENT protocol defined by the SAE-J2716 Surface Vehicle Information Report standard.
  • the processing means may be a processing component of the integrated circuit device.
  • the processing means may comprise a data memory 7, e.g. a processor register memory and/or a random access memory, and an instruction memory 8, e.g. a read-only memory (ROM) or a programmable non-volatile memory such as a one-time programmable memory (OTP) or an electrically erasable read-only memory (EEPROM).
  • ROM read-only memory
  • OTP programmable non-volatile memory
  • OTP one-time programmable memory
  • EEPROM electrically erasable read-only memory
  • the processing means may further comprise runtime instruction processing means for fetching and executing instructions stored in the instruction memory.
  • Such instructions may comprise program logic for controlling the input/output means 6 (I/O) such as to acquire and digitize data, e.g. sensor data.
  • these instructions may also comprise program logic for controlling the data transmission via the output port 5 such as to comply with the SENT protocol.
  • the processing means 2 may be programmed to perform such task, e.g. via machine-executable instructions forming a firmware program stored in the instruction memory 8.
  • the integrated circuit device 1 further comprises a configuration means 3 for receiving and storing configuration data.
  • the integrated circuit device 1 may be provided with a configuration port 9 for receiving the configuration data, e.g. which may be provided by a user in order to set up the device for a specific application.
  • the configuration means 3 may for example comprise a configuration memory 4, such as an OTP memory, a flash memory or an electrically erasable programmable read-only memory (EEPROM), for storing the configuration data. It is an advantage of such configuration means 3 that the device can be easily adapted to a specific application without requiring a hardware redesign and/or change of a firmware product controlling the processing means 2.
  • Embodiments of the present invention enable a SENT message configuration of the device, for example in order to adapt to a specific application, by supplying the corresponding configuration data to the device.
  • the device can be easily reconfigured without requiring changes in hardware or firmware.
  • This SENT message configuration may be realized via programming of a configuration memory map stored in the configuration memory 4, e.g. in a programmable configuration memory.
  • This configuration does not require a change of software, such as a change of software by providing a firmware program to control the device in accordance with a specific configuration, or a change of hardware, e.g. by replacing a ROM module or redesigning the physical architecture of the device.
  • the memory allocated to the configuration memory map may be independent of the specific configuration, such that changing the configuration of the device can be advantageously performed without affecting the memory in use in the integrated circuit device.
  • the processing means 2 may be adapted for encapsulating data, e.g. sensor data, in nibble frames in the data stream taking the configuration data into account.
  • data e.g. sensor data
  • at least one SENT telegram may be transmitted, e.g. a serial stream of such telegrams.
  • Such telegram may comprise a sequence of a synchronization pulse, a first nibble comprising internal status and diagnostic information, one to six data nibbles, e.g. for reporting sensor information and a nibble for sending a CRC, and may be optionally terminated by pause pulse.
  • the number of data nibbles may be typically fixed for each application of the encoding scheme, but can vary between applications.
  • the data transmitted in the data nibbles are commonly referred to as fast channel data, as opposed to slow channel data discussed further hereinbelow.
  • the configuration data may comprise at least one value for selecting the number of nibbles to transmit per SENT telegram, e.g. may comprise two such values corresponding to the number of nibbles to allocate per fast channel to be transmitted.
  • the number of nibbles may be fixed to 3 nibbles, thus 12 bits, per fast channel, e.g. the device may transmit two data 12 bit values per SENT telegram.
  • this does not allow transmitting 16 bits data, e.g. raw analog-to-digital converter data, via the SENT fast channel, it may advantageously enable a more robust and simple software implementation.
  • the configuration data may also comprise a flag for controlling the transmission of a pause frame, e.g. a pause pulse terminating each telegram, in accordance with the SENT protocol.
  • the processing means 2 may be adapted to retrieve at least one value from the configuration means for selecting the number of nibbles to transmit per SENT telegram, e.g. a plurality of values for selecting the number of nibbles to transmit, e.g. one such value per fast channel.
  • the processing means 2 may be adapted to retrieve at least one flag from the configuration means for activating or deactivating a pause frame in the SENT telegrams transmitted via the data stream.
  • the configuration data may also comprise at least one address pointer, e.g. one address pointer per fast channel for accessing the data to be transmitted.
  • address pointer may store a memory address or I/O port address where the data to be transmitted can be retrieved, or such address pointer may store an instruction memory address of a program routine for retrieving the data to be transmitted.
  • the processing means 2 may be adapted for retrieving at least one address pointer from the configuration means that references the data to be transmitted or that references a program routine for acquiring the data to be transmitted, in which this data is to be transmitted in a corresponding SENT fast channel of the data stream.
  • embodiments of the present invention advantageously provide more flexibility, e.g. may provide more versatile configuration options.
  • the configuration data may also comprise application specific fast channel configuration information, e.g. application specific fast channel configuration information such as information relating to secure sensor configuration, a flag to invert the nibble order for the second fast channel and/or a flag to invert the data for the second fast channel.
  • application specific fast channel configuration information such as information relating to secure sensor configuration, a flag to invert the nibble order for the second fast channel and/or a flag to invert the data for the second fast channel.
  • the processing means 2 may be adapted for retrieving such application specific fast channel configuration information from the configuration means.
  • the processing means 2 is adapted for reporting a plurality of diagnostic statuses, e.g. errors, via the data stream by transmitting for each diagnostic status a corresponding diagnostic code defined by the configuration data.
  • the configuration data may comprise a mask to enable or disable status reporting in at least one SENT status bit, e.g. the status bits in the status and communication (S&C) nibble of each transmitted SENT telegram.
  • the processing means 2 may be adapted for detecting a plurality of diagnostic statuses, e.g. errors, and for setting a status bit state in a status and communication nibble and a status bit mask in the configuration data.
  • This status bit mask may comprise for each diagnostic status which may be detected by the processing means a flag, or plurality of flags, to indicate whether and/or by which status bit the corresponding diagnostic status is to be reported.
  • each error that may be detected by the processing means e.g. which is provided for by a firmware executed by the processing means, may have a separate reporting configuration for each SENT status bit.
  • the processing means 2 may furthermore be adapted for reporting at least one diagnostic status of said plurality of diagnostic statuses by transmitting a diagnostic code value via a SENT fast channel.
  • the configuration data may comprise a plurality of correspondences between diagnostic statuses that can be detected by the processing means 2 and values to be transmitted via a SENT fast channel.
  • the configuration data may comprise such a plurality of correspondences for each SENT fast channel.
  • the processing means 2 is furthermore adapted for reporting the plurality of diagnostic statuses in a diagnostic status reporting order defined by the configuration data. For example, if a plurality of statuses is detected, each of this plurality of statuses having a corresponding value to be transmitted via the same SENT fast channel defined in the configuration data, this plurality of statuses may be reported in consecutive SENT telegrams in an order defined in the configuration data. However, in embodiments of the present invention, if a plurality of statuses is detected, e.g. a number N>1 of simultaneously occurring errors, only the status with the highest priority may be reported, e.g. by replacement of the fast channel data by an error code, e.g.
  • a corresponding error code in for example the range 4089 ... 4095 as may configured for each status, as described hereinabove.
  • the lower priority statuses may be communicated by a configurable diagnostic error code, e.g. a code configured for each error, sent in a SENT slow channel diagnostic message, as described further hereinbelow.
  • the SENT standard also provides a mechanism for broadcasting information at a slower rate, for example for communicating information that is less (or even not at all) time-critical, such as conversion coefficients from raw data to physical values, manufacturer's name or type of sensor.
  • This mechanism may rely on bits in the status and communication (S&C) nibble of the SENT telegram, e.g. the first nibble in a telegram transmitted before the data nibbles forming the fast channel or fast channels.
  • S&C status and communication
  • two bits in the S&C nibble may be designated to convey the slow channel.
  • These bits may be accumulated from a plurality of consecutive telegrams, e.g. from 16 or 18 consecutive messages, and may be grouped to form a message ID, a message value and a CRC.
  • the configuration data may comprise a value for selecting the number of SENT slow channel messages.
  • the configuration data may have a maximum number of slow channel messages which may be configured, e.g. may provide for up to 32 SENT slow channel messages, or even a higher number of slow channel messages, e.g. 64, 128 or 256, as may be determined by storage constraints and design considerations.
  • the configuration data may comprise a plurality of identification (ID) numbers, and for each ID number a corresponding slow channel message.
  • ID numbers may be 8-bit or 4-bit messages IDs.
  • the configuration data may comprise a flag for selecting between a 12-bit or 16-bit data format for the slow channel messages.
  • the configuration data may also comprise at least one address pointer, e.g. one address pointer per slow channel message for accessing the data to be transmitted in combination with the corresponding identification number defined in the configuration data.
  • address pointer may store a memory address or I/O port address where the data to be transmitted can be retrieved, or such address pointer may store an instruction memory address of a program routine for retrieving the data to be transmitted.
  • the processing means 2 may be adapted for retrieving at least one address pointer from the configuration means that references the data to be transmitted or that references a program routine for acquiring the data to be transmitted, in which this data is to be transmitted in a corresponding SENT slow channel message of the data stream.
  • the processing means 2 is adapted for reporting a plurality of diagnostic statuses, e.g. errors, via the data stream by transmitting for each diagnostic status a corresponding diagnostic code defined by the configuration data.
  • the processing means 2 may be adapted for detecting a plurality of diagnostic statuses, e.g. errors, and for reporting at least one diagnostic status of this plurality of diagnostic statuses by transmitting a diagnostic code value via a SENT slow channel message.
  • the configuration data may comprise a plurality of correspondences between diagnostic statuses that can be detected by the processing means 2 and values to be transmitted via a SENT slow channel message, e.g. corresponding slow channel message identification numbers and/or slow channel messages.
  • a plurality of statuses, e.g. errors, detectable by the firmware executing on the processing means may have corresponding 12-bit SENT slow channel error codes defined in the configuration data.
  • the processing means 2 is adapted for reporting the plurality of diagnostic statuses in a diagnostic status reporting order defined by the configuration data. For example, if a plurality of statuses is detected, each of this plurality of statuses having a corresponding value to be transmitted via the SENT slow channel defined in the configuration data, this plurality of statuses may be reported in consecutive SENT slow channel messages in an order defined by the configuration data. Thus, a fully configurable sequence of SENT slow channel messages may be provided by a table in the configuration data.
  • the processing means 2 may be adapted for reporting the plurality of diagnostic statuses in a diagnostic status reporting order defined by the configuration data, such that a status to be reported that has the highest priority as defined by this diagnostic status reporting order is transmitted via a fast channel, while the statuses to be reported that have lower priorities are transmitted via the slow channel.
  • the processing means 2 may furthermore be adapted for validating the configuration data, e.g. when received by the configuration means 3, such as via the configuration port 9.
  • the device hardware 21 may be adapted for performing the SENT message transmission, e.g. via the output port 5 under control of the processing means 2, to a receiver, e.g. an ECU.
  • the device hardware 21 may be controlled by a firmware product 22, e.g. may execute on the processing means 2.
  • the firmware product 22 may handle SENT slow channels message composition and SENT fast channels message composition. This message composition may be performed taking into account the configuration data stored by the configuration means 3, e.g. by taking into account at least one fully configurable data structure 23.
  • This data structure may for example comprise a table of errors ERROR_TABLE, which may be set up to link any or each error to a fast channel SENT data configuration table FS_DATA_TABLE, e.g. for defining a corresponding fast channel error code and/or a corresponding status bit to flag, and/or to a slow channel SENT data configuration table SS_DATA_TABLE, e.g. for defining a corresponding error message.
  • a table of errors ERROR_TABLE which may be set up to link any or each error to a fast channel SENT data configuration table FS_DATA_TABLE, e.g. for defining a corresponding fast channel error code and/or a corresponding status bit to flag, and/or to a slow channel SENT data configuration table SS_DATA_TABLE, e.g. for defining a corresponding error message.
  • the configuration means 3 may receive inputs 24 to reconfigure the stored configuration data, e.g. may receive signal value configuration or memory pointer data for changing an entry in the fast or slow channel configuration table, and/or an instruction to enable or disable an entry in the table of errors and/or a priority setup table.
  • the present invention also relates to a method for controlling an integrated circuit device adapted for transmitting data via a data stream in accordance with a single-edge nibble transmission protocol, e.g. for controlling a device according to embodiments of the first aspect of the present invention.
  • a single-edge nibble transmission protocol e.g. for controlling a device according to embodiments of the first aspect of the present invention.
  • FIG. 3 shows an exemplary method 30 according to embodiments of the present invention.
  • the method 30 comprises receiving 31 configuration instructions from a user and storing 32 configuration data in accordance with these configuration instructions.
  • Such receiving and storing may be performed by a configuration means of a device according to embodiments of the present invention, for instance as explained hereinabove; for example configuration instructions may be received via a configuration input port and corresponding configuration data may be stored in a configuration memory, e.g. a reprogrammable non-volatile memory.
  • the method 30 further comprises controlling 33 a transmission of a data stream in accordance with a single-edge nibble transmission protocol.
  • this controlling may be performed by a processing means, e.g. a processor, as explained hereinabove.
  • the controlling 33 of the transmission of the data stream furthermore comprises reporting 34 a plurality of diagnostic statuses via the data stream by transmitting 35 for each diagnostic status a corresponding diagnostic code defined by the configuration data, e.g. stored in the configuration memory. Reporting the plurality of diagnostic statuses is furthermore performed in a diagnostic status reporting order defined by the configuration data, e.g. stored in the configuration memory.
  • Controlling 33 of the transmission may furthermore comprise retrieving at least one address pointer from the configuration data in order to reference data or reference a program routine for acquiring such data, and transmitting these data in a SENT fast channel or in a SENT slow channel message of the data stream.
  • Controlling 33 of the transmission may also comprise detecting the plurality of diagnostic statuses and setting a status bit state in a status and communication nibble transmitted via the data stream taking into account the detected diagnostic statuses and a status bit mask in the configuration data.
  • Reporting 34 the plurality of diagnostic statuses may also comprise transmitting 35 a diagnostic code value via a SENT fast channel and/or via a SENT slow channel message.

Abstract

The present invention relates to an integrated circuit device (1) comprising an output port (5) for transmitting a data stream and a processing means (2) for controlling the transmission of the data stream in accordance with a single-edge nibble transmission protocol. The device also comprises a configuration means (3) for receiving and storing configuration data. The processing means (2) is adapted for reporting a plurality of diagnostic statuses via the data stream by transmitting for each diagnostic status a corresponding diagnostic code defined by the configuration data, and wherein the processing means (2) is furthermore adapted for reporting the plurality of diagnostic statuses in a diagnostic status reporting order defined by the configuration data.

Description

    Field of the invention
  • The invention relates to the field of data transmission according to the Single Edge Nibble Transmission (SENT) standard. More specifically, it relates to an integrated circuit device, e.g. a SENT transmitter device such as a SENT-capable sensor, for transmitting data via the SENT protocol and a related method for implementing the SENT protocol in integrated circuits in an application independent manner.
  • Background of the invention
  • The SENT protocol (SAE J2716 standard) provides signal transmission from a transmitter device, e.g. an integrated circuit (IC) sensor, to a receiver device, e.g. an Electronic Control Unit (ECU). The SENT protocol may for example provide a low-cost and efficient alternative to, for example, analogue or PWM interfaces for sensor applications.
  • The SENT encoding scheme may be particularly suitable for use in applications where high resolution sensor data needs to be communicated from a sensor to an ECU. The SENT standard defines a unidirectional communications scheme from a transmitting device, e.g. a sensor, to a receiving device, e.g. a controller, which does not require a coordination and/or synchronization signal from the receiving device. Thus, the transmission may proceed independently of the receiver module.
  • An integrated circuit sensor for automotive applications may provide an output mode for reporting sensor information and/or other diagnostic information, such as cyclic redundancy check (CRC) information, via a SENT telegram compliant with the SAE-J2716 Surface Vehicle Information Report standard. The number of nibbles is typically fixed for each application of the encoding scheme, but can vary between applications.
  • An integrated circuit (IC) device for SENT communication as known in the art may use a fixed configuration for its communication channels, e.g. defining a data mapping to fast and slow channels. Thus a device, e.g. a transmitter or receiver device as known in the art, that is adapted for SENT communication may have a configuration-specific hardware design or firmware to take the SENT protocol configuration into account.
  • The SENT serial data communication protocol may be used for transmission of signal values, e.g. messages, from a transmitter device to a receiver device with high resolution. The implementation of the SENT protocol in IC implies a fixed user message configuration for its communication channels, e.g. fast and slow channels. The configuration may depend on the intended application, and changing the configuration in order to address different applications may require redesign of the IC hardware and/or firmware.
  • For example, the configuration may be hardwired, such that the IC device is specifically designed for a single configuration corresponding to a specific application. Alternatively, the IC device may be provided by a read-only memory (ROM) which can be programmed for a specific SENT message configuration. Thus, the IC can be redesigned for a different configuration by adapting the firmware accordingly; however, the end-product device provided with such application-specific ROM may be only suitable for use in the configuration the firmware is designed for.
  • The device may comprise a one-time programmable non-volatile memory (OTP), such that the change of the SENT message configuration can be realized through programming the device with a suitable software construct, taking into account the restrictions of the available memory space. Thus, a device can be programmed to a specific application after manufacturing but prior to use. Furthermore, an IC device may also comprise a FLASH memory or an electrically erasable programmable read-only memory (EEPROM), such that the change of the SENT message configuration can be realized through software change, taking into account restrictions of the available memory space.
  • Configuration of an integrated circuit SENT transmitter device may comprise, for the SENT fast channels, e.g. the data transmitted via the data nibbles, defining the number of channels, the information associated with each channel, the data nibbles order format, the method of status bits processing, the fast channel diagnostic error codes and the reporting priority of the fast channel diagnostic error codes. Furthermore, configuration for the SENT slow channels may further comprise the defining of the association of every SENT slow channel message with an ID number, an ID memory location, a message order, the slow channel diagnostic error codes and the reporting priority of slow channel diagnostic error codes.
  • Summary of the invention
  • It is an object of embodiments of the present invention to provide easy configuration and reconfiguration of a SENT-capable integrated circuit device.
  • The above objective is accomplished by a method and device according to the present invention.
  • In a first aspect, the present invention relates to an integrated circuit device comprising an output port for transmitting a data stream, a processing means for controlling the transmission of the data stream in accordance with a single-edge nibble transmission protocol, and a configuration means for receiving and storing configuration data. The processing means is adapted for, e.g. configured or programmed for, reporting a plurality of diagnostic statuses via the data stream by transmitting for each diagnostic status a corresponding diagnostic code defined by the configuration data. The processing means is furthermore adapted for reporting the plurality of diagnostic statuses in a diagnostic status reporting order defined by the configuration data.
  • In an integrated circuit device according to embodiments of the present invention, the configuration means may be adapted for receiving configuration instructions from a user and for storing this configuration data in accordance with the configuration instructions.
  • In an integrated circuit device according to embodiments of the present invention, the processing means may be adapted for retrieving at least one address pointer from the configuration means. The at least one address pointer may reference data or may reference a program routine for acquiring this data, in which the data is to be transmitted in a corresponding SENT fast channel or in a corresponding SENT slow channel message of the data stream.
  • In an integrated circuit device according to embodiments of the present invention, the processing means may be adapted for detecting the plurality of diagnostic statuses and for setting a status bit state in a status and communication nibble transmitted via the data stream taking into account the detected diagnostic statuses and a status bit mask in the configuration data.
  • In an integrated circuit device according to embodiments of the present invention, the processing means may be adapted for reporting at least one diagnostic status of the plurality of diagnostic statuses by transmitting a diagnostic code value via a SENT fast channel.
  • In an integrated circuit device according to embodiments of the present invention, the processing means may be adapted for reporting at least one diagnostic status of the plurality of diagnostic statuses by transmitting a diagnostic code value via a SENT slow channel message.
  • In an integrated circuit device according to embodiments of the present invention, the processing means may be adapted to retrieve at least one value from the configuration means for selecting the number of nibbles to transmit per SENT telegram.
  • In an integrated circuit device according to embodiments of the present invention, the configuration means may comprise a configuration memory for storing the configuration data.
  • An integrated circuit device according to embodiments of the present invention may furthermore comprise input/output means for acquiring and digitizing data.
  • In an integrated circuit device according to embodiments of the present invention, the processing means may comprise a data memory and an instruction memory.
  • In an integrated circuit device according to embodiments of the present invention, the instruction memory may comprise instructions according to a program logic for controlling the input/output means such as to acquire and digitize data, and for controlling the data transmission via the output port such as to comply with the SENT protocol.
  • In a second aspect, the present invention relates to a method for controlling an integrated circuit device adapted for transmitting data via a data stream in accordance with a single-edge nibble transmission protocol. The method comprises receiving configuration instructions from a user, storing configuration data in accordance with the configuration instructions, and controlling a transmission of a data stream in accordance with a single-edge nibble transmission protocol. This controlling of the transmission of the data stream comprises reporting a plurality of diagnostic statuses via the data stream by transmitting for each diagnostic status a corresponding diagnostic code defined by the configuration data. Reporting the plurality of diagnostic statuses is furthermore performed in a diagnostic status reporting order defined by the configuration data.
  • In a method according to embodiments of the present invention, the controlling of the transmission may furthermore comprise retrieving at least one address pointer from the configuration data in order to reference data or reference a program routine for acquiring this data, and transmitting the data in a corresponding SENT fast channel or in a corresponding SENT slow channel message of the data stream.
  • In a method according to embodiments of the present invention, the controlling of the transmission may comprise detecting the plurality of diagnostic statuses and setting a status bit state in a status and communication nibble transmitted via the data stream taking into account the detected diagnostic statuses and a status bit mask in the configuration data.
  • In a method according to embodiments of the present invention, the reporting of the plurality of diagnostic statuses may comprise transmitting a diagnostic code value via a SENT fast channel and/or via a SENT slow channel message.
  • It is an advantage of embodiments of the present invention that the SENT configuration can be changed without requiring a hardware or firmware update of the transmitter device, e.g. without requiring hardware or software redesign.
  • It is an advantage of embodiments of the present invention that an application independent SENT data protocol implementation is provided in an integrated circuit device in an efficient manner.
  • It is an advantage of embodiments of the present invention that versatile configuration and/or reconfiguration of the SENT transmissions of an integrated circuit device can be achieved through the update of a data structure stored in a memory unit, e.g. a non-volatile memory of the device.
  • Particular and preferred aspects of the invention are set out in the accompanying independent and dependent claims. Features from the dependent claims may be combined with features of the independent claims and with features of other dependent claims as appropriate and not merely as explicitly set out in the claims.
  • These and other aspects of the invention will be apparent from and elucidated with reference to the embodiment(s) described hereinafter.
  • Brief description of the drawings
    • FIG. 1 shows an exemplary integrated circuit device according to embodiments of the present invention.
    • FIG. 2 shows an exemplary data flow structure of a device according to embodiments of the present invention.
    • FIG. 3 shows an exemplary method according to embodiments of the present invention.
  • The drawings are only schematic and are non-limiting. In the drawings, the size of some of the elements may be exaggerated and not drawn on scale for illustrative purposes.
  • Any reference signs in the claims shall not be construed as limiting the scope.
  • In the different drawings, the same reference signs refer to the same or analogous elements.
  • Detailed description of illustrative embodiments
  • The present invention will be described with respect to particular embodiments and with reference to certain drawings but the invention is not limited thereto but only by the claims. The drawings described are only schematic and are non-limiting. In the drawings, the size of some of the elements may be exaggerated and not drawn on scale for illustrative purposes. The dimensions and the relative dimensions do not correspond to actual reductions to practice of the invention.
  • The terms first, second and the like in the description and in the claims, are used for distinguishing between similar elements and not necessarily for describing a sequence, either temporally, spatially, in ranking or in any other manner. It is to be understood that the terms so used are interchangeable under appropriate circumstances and that the embodiments of the invention described herein are capable of operation in other sequences than described or illustrated herein.
  • Moreover, the terms top, under and the like in the description and the claims are used for descriptive purposes and not necessarily for describing relative positions. It is to be understood that the terms so used are interchangeable under appropriate circumstances and that the embodiments of the invention described herein are capable of operation in other orientations than described or illustrated herein.
  • It is to be noticed that the term "comprising", used in the claims, should not be interpreted as being restricted to the means listed thereafter; it does not exclude other elements or steps. It is thus to be interpreted as specifying the presence of the stated features, integers, steps or components as referred to, but does not preclude the presence or addition of one or more other features, integers, steps or components, or groups thereof. Thus, the scope of the expression "a device comprising means A and B" should not be limited to devices consisting only of components A and B. It means that with respect to the present invention, the only relevant components of the device are A and B.
  • Reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment, but may. Furthermore, the particular features, structures or characteristics may be combined in any suitable manner, as would be apparent to one of ordinary skill in the art from this disclosure, in one or more embodiments.
  • Similarly it should be appreciated that in the description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. This method of disclosure, however, is not to be interpreted as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.
  • Furthermore, while some embodiments described herein include some but not other features included in other embodiments, combinations of features of different embodiments are meant to be within the scope of the invention, and form different embodiments, as would be understood by those in the art. For example, in the following claims, any of the claimed embodiments can be used in any combination.
  • In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. In other instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
  • Where hereinbelow is referred to the Single Edge Nibble Transmission (SENT) protocol, reference is made a protocol, such as the SAE J2716 standard, that defines a transmission telegram consisting of a plurality of nibbles in sequence, in which each nibble consists of 4 bits coded by Pulse Width Modulation (PWM) with reference to the falling edge, hence the term "single edge nibble" in the protocol acronym. The first nibble of such telegram, e.g. directly following a synchronization pulse, may for example contain internal status and diagnostic information. This first nibble may be followed by one to six data nibbles, e.g. for reporting sensor information. A final nibble in the transmission telegram may for example comprise redundancy check information. While the number of nibbles may be fixed for a specific application of the encoding scheme, this number may vary between applications. For example, if one 12-bit value is to be transmitted, three data nibbles may be used, while if two 8-bit values need to be transmitted, four data nibbles may be used.
  • SENT may also provide a mechanism for broadcasting information at a much slower rate, for example for communicating information that is less time-critical, such as conversion coefficients from raw data to physical values, the manufacturer's name, the type of sensor or an serial identification tag of the sensor. This mechanism may rely on bits in the status and communication (S&C) nibble of the SENT telegram, e.g. two bits in the S&C nibble may be designated to convey the slow channel. These bits may be accumulated from a plurality of consecutive telegrams, e.g. from 16 or 18 adjacent messages, and grouped to form a message ID, a message value and a CRC. In a first aspect, the present invention relates to an integrated circuit (IC) device comprising an output port for transmitting a data stream; a processing means, e.g. a processor, for controlling the transmission of this data stream in accordance with a single-edge nibble transmission protocol; and a configuration means for receiving and storing configuration data, e.g. for receiving configuration instructions from a user and for storing configuration data corresponding to these configuration instructions. The processing means is adapted for reporting a plurality of diagnostic statuses, e.g. errors, via the data stream by transmitting for each diagnostic status a corresponding diagnostic code defined by the configuration data. The processing means is furthermore adapted for reporting this plurality of diagnostic statuses in a diagnostic status reporting order defined by the configuration data.
  • An integrated circuit device 1 according to embodiments of the present invention is shown in FIG. 1. The integrated circuit device may be an application specific standard product (ASSP) for collecting and transmitting sensor data. For ASSP ICs, product flexibility is preferred in order to serve multiple end users, which makes an extra cost for using CPU resources cost effective as it avoids the cost of redesigns.
  • This device, e.g. an integrated circuit sensor for automotive applications, may provide an output mode for reporting data, e.g. sensor information and/or diagnostic information, via SENT telegrams compliant with the SAE-J2716 Surface Vehicle Information Report. Thus, the integrated circuit sensor may be a SENT transmitter device, e.g. a SENT data transmitter. The device 1 comprises an output port 5 for transmitting a data stream, e.g. for relaying SENT telegrams over a wire harness to a receiving node, such as a SENT receiver device. For example, the data may be transmitted to an engine control unit. The integrated circuit device may also comprise input/output means 6 for acquiring and digitizing data, e.g. sensor data. For example, the input/output means may comprise output signal lines for controlling the acquisition and digitization of data by a sensor component and input signal lines for receiving digitized data from this sensor component.
  • The integrated circuit device 1 further comprises a processing means 2, e.g. a processor, for controlling the transmission of the data stream in accordance with a single-edge nibble transmission protocol, e.g. in accordance with the SENT protocol defined by the SAE-J2716 Surface Vehicle Information Report standard. The processing means may be a processing component of the integrated circuit device. The processing means may comprise a data memory 7, e.g. a processor register memory and/or a random access memory, and an instruction memory 8, e.g. a read-only memory (ROM) or a programmable non-volatile memory such as a one-time programmable memory (OTP) or an electrically erasable read-only memory (EEPROM). The processing means may further comprise runtime instruction processing means for fetching and executing instructions stored in the instruction memory. Such instructions may comprise program logic for controlling the input/output means 6 (I/O) such as to acquire and digitize data, e.g. sensor data. Particularly, these instructions may also comprise program logic for controlling the data transmission via the output port 5 such as to comply with the SENT protocol. Furthermore, where hereinbelow reference is made to the processing means 2 being adapted for performing a task, it will be clear that the processing means may be programmed to perform such task, e.g. via machine-executable instructions forming a firmware program stored in the instruction memory 8.
  • The integrated circuit device 1 further comprises a configuration means 3 for receiving and storing configuration data. For example, the integrated circuit device 1 may be provided with a configuration port 9 for receiving the configuration data, e.g. which may be provided by a user in order to set up the device for a specific application. The configuration means 3 may for example comprise a configuration memory 4, such as an OTP memory, a flash memory or an electrically erasable programmable read-only memory (EEPROM), for storing the configuration data. It is an advantage of such configuration means 3 that the device can be easily adapted to a specific application without requiring a hardware redesign and/or change of a firmware product controlling the processing means 2. Embodiments of the present invention enable a SENT message configuration of the device, for example in order to adapt to a specific application, by supplying the corresponding configuration data to the device. The device can be easily reconfigured without requiring changes in hardware or firmware. This SENT message configuration may be realized via programming of a configuration memory map stored in the configuration memory 4, e.g. in a programmable configuration memory. This configuration does not require a change of software, such as a change of software by providing a firmware program to control the device in accordance with a specific configuration, or a change of hardware, e.g. by replacing a ROM module or redesigning the physical architecture of the device. Furthermore, the memory allocated to the configuration memory map may be independent of the specific configuration, such that changing the configuration of the device can be advantageously performed without affecting the memory in use in the integrated circuit device.
  • The processing means 2 may be adapted for encapsulating data, e.g. sensor data, in nibble frames in the data stream taking the configuration data into account. In the data stream transmitted via the output port, at least one SENT telegram may be transmitted, e.g. a serial stream of such telegrams. Such telegram may comprise a sequence of a synchronization pulse, a first nibble comprising internal status and diagnostic information, one to six data nibbles, e.g. for reporting sensor information and a nibble for sending a CRC, and may be optionally terminated by pause pulse. The number of data nibbles may be typically fixed for each application of the encoding scheme, but can vary between applications. The data transmitted in the data nibbles are commonly referred to as fast channel data, as opposed to slow channel data discussed further hereinbelow. For example, if one 12-bit value is to be transmitted, three data nibbles may be used forming a single fast channel, while if two 8-bit values need to be transmitted, two data nibbles may be used for each of two fast channels. The configuration data may comprise at least one value for selecting the number of nibbles to transmit per SENT telegram, e.g. may comprise two such values corresponding to the number of nibbles to allocate per fast channel to be transmitted. Alternatively, the number of nibbles may be fixed to 3 nibbles, thus 12 bits, per fast channel, e.g. the device may transmit two data 12 bit values per SENT telegram. Although this does not allow transmitting 16 bits data, e.g. raw analog-to-digital converter data, via the SENT fast channel, it may advantageously enable a more robust and simple software implementation.
  • The configuration data may also comprise a flag for controlling the transmission of a pause frame, e.g. a pause pulse terminating each telegram, in accordance with the SENT protocol. Thus, the processing means 2 may be adapted to retrieve at least one value from the configuration means for selecting the number of nibbles to transmit per SENT telegram, e.g. a plurality of values for selecting the number of nibbles to transmit, e.g. one such value per fast channel. The processing means 2 may be adapted to retrieve at least one flag from the configuration means for activating or deactivating a pause frame in the SENT telegrams transmitted via the data stream.
  • Furthermore, the configuration data may also comprise at least one address pointer, e.g. one address pointer per fast channel for accessing the data to be transmitted. For example such address pointer may store a memory address or I/O port address where the data to be transmitted can be retrieved, or such address pointer may store an instruction memory address of a program routine for retrieving the data to be transmitted. Thus, the processing means 2 may be adapted for retrieving at least one address pointer from the configuration means that references the data to be transmitted or that references a program routine for acquiring the data to be transmitted, in which this data is to be transmitted in a corresponding SENT fast channel of the data stream. Where in a device as known in the art a fixed memory address referencing the data to be transmitted in the or each fast channel may be used, e.g. hardcoded in the firmware as a low cost and low complexity implementation, embodiments of the present invention advantageously provide more flexibility, e.g. may provide more versatile configuration options.
  • The configuration data may also comprise application specific fast channel configuration information, e.g. application specific fast channel configuration information such as information relating to secure sensor configuration, a flag to invert the nibble order for the second fast channel and/or a flag to invert the data for the second fast channel. Thus, the processing means 2 may be adapted for retrieving such application specific fast channel configuration information from the configuration means.
  • The processing means 2 is adapted for reporting a plurality of diagnostic statuses, e.g. errors, via the data stream by transmitting for each diagnostic status a corresponding diagnostic code defined by the configuration data.
  • The configuration data may comprise a mask to enable or disable status reporting in at least one SENT status bit, e.g. the status bits in the status and communication (S&C) nibble of each transmitted SENT telegram. For example, the processing means 2 may be adapted for detecting a plurality of diagnostic statuses, e.g. errors, and for setting a status bit state in a status and communication nibble and a status bit mask in the configuration data. This status bit mask may comprise for each diagnostic status which may be detected by the processing means a flag, or plurality of flags, to indicate whether and/or by which status bit the corresponding diagnostic status is to be reported. For example, each error that may be detected by the processing means, e.g. which is provided for by a firmware executed by the processing means, may have a separate reporting configuration for each SENT status bit.
  • The processing means 2 may furthermore be adapted for reporting at least one diagnostic status of said plurality of diagnostic statuses by transmitting a diagnostic code value via a SENT fast channel. For example, the configuration data may comprise a plurality of correspondences between diagnostic statuses that can be detected by the processing means 2 and values to be transmitted via a SENT fast channel. Furthermore, the configuration data may comprise such a plurality of correspondences for each SENT fast channel. These values to be transmitted via a SENT fast channel to indicate a diagnostic status may lie within a predetermined range, e.g. in order to easily differentiate such values from normal data values communicated via the fast channel, for example in the range of 4089 to 4095 for a 12-bit channel.
  • The processing means 2 is furthermore adapted for reporting the plurality of diagnostic statuses in a diagnostic status reporting order defined by the configuration data. For example, if a plurality of statuses is detected, each of this plurality of statuses having a corresponding value to be transmitted via the same SENT fast channel defined in the configuration data, this plurality of statuses may be reported in consecutive SENT telegrams in an order defined in the configuration data. However, in embodiments of the present invention, if a plurality of statuses is detected, e.g. a number N>1 of simultaneously occurring errors, only the status with the highest priority may be reported, e.g. by replacement of the fast channel data by an error code, e.g. a corresponding error code in for example the range 4089 ... 4095 as may configured for each status, as described hereinabove. However, it is an advantage of embodiments of the present invention that the lower priority statuses may be communicated by a configurable diagnostic error code, e.g. a code configured for each error, sent in a SENT slow channel diagnostic message, as described further hereinbelow.
  • The SENT standard also provides a mechanism for broadcasting information at a slower rate, for example for communicating information that is less (or even not at all) time-critical, such as conversion coefficients from raw data to physical values, manufacturer's name or type of sensor. This mechanism may rely on bits in the status and communication (S&C) nibble of the SENT telegram, e.g. the first nibble in a telegram transmitted before the data nibbles forming the fast channel or fast channels. For example, two bits in the S&C nibble may be designated to convey the slow channel. These bits may be accumulated from a plurality of consecutive telegrams, e.g. from 16 or 18 consecutive messages, and may be grouped to form a message ID, a message value and a CRC.
  • The configuration data may comprise a value for selecting the number of SENT slow channel messages. Alternatively, the configuration data may have a maximum number of slow channel messages which may be configured, e.g. may provide for up to 32 SENT slow channel messages, or even a higher number of slow channel messages, e.g. 64, 128 or 256, as may be determined by storage constraints and design considerations.
  • The configuration data may comprise a plurality of identification (ID) numbers, and for each ID number a corresponding slow channel message. The ID numbers may be 8-bit or 4-bit messages IDs. The configuration data may comprise a flag for selecting between a 12-bit or 16-bit data format for the slow channel messages. Furthermore, the configuration data may also comprise at least one address pointer, e.g. one address pointer per slow channel message for accessing the data to be transmitted in combination with the corresponding identification number defined in the configuration data. For example such address pointer may store a memory address or I/O port address where the data to be transmitted can be retrieved, or such address pointer may store an instruction memory address of a program routine for retrieving the data to be transmitted. Thus, the processing means 2 may be adapted for retrieving at least one address pointer from the configuration means that references the data to be transmitted or that references a program routine for acquiring the data to be transmitted, in which this data is to be transmitted in a corresponding SENT slow channel message of the data stream.
  • The processing means 2 is adapted for reporting a plurality of diagnostic statuses, e.g. errors, via the data stream by transmitting for each diagnostic status a corresponding diagnostic code defined by the configuration data.
  • For example, the processing means 2 may be adapted for detecting a plurality of diagnostic statuses, e.g. errors, and for reporting at least one diagnostic status of this plurality of diagnostic statuses by transmitting a diagnostic code value via a SENT slow channel message. For example, the configuration data may comprise a plurality of correspondences between diagnostic statuses that can be detected by the processing means 2 and values to be transmitted via a SENT slow channel message, e.g. corresponding slow channel message identification numbers and/or slow channel messages. For example, a plurality of statuses, e.g. errors, detectable by the firmware executing on the processing means may have corresponding 12-bit SENT slow channel error codes defined in the configuration data.
  • The processing means 2 is adapted for reporting the plurality of diagnostic statuses in a diagnostic status reporting order defined by the configuration data. For example, if a plurality of statuses is detected, each of this plurality of statuses having a corresponding value to be transmitted via the SENT slow channel defined in the configuration data, this plurality of statuses may be reported in consecutive SENT slow channel messages in an order defined by the configuration data. Thus, a fully configurable sequence of SENT slow channel messages may be provided by a table in the configuration data. As described hereinabove, the processing means 2 may be adapted for reporting the plurality of diagnostic statuses in a diagnostic status reporting order defined by the configuration data, such that a status to be reported that has the highest priority as defined by this diagnostic status reporting order is transmitted via a fast channel, while the statuses to be reported that have lower priorities are transmitted via the slow channel.
  • The processing means 2 may furthermore be adapted for validating the configuration data, e.g. when received by the configuration means 3, such as via the configuration port 9.
  • An exemplary data flow structure of a device according to embodiments of the present invention is shown in FIG. 2. The device hardware 21 may be adapted for performing the SENT message transmission, e.g. via the output port 5 under control of the processing means 2, to a receiver, e.g. an ECU. The device hardware 21 may be controlled by a firmware product 22, e.g. may execute on the processing means 2. The firmware product 22 may handle SENT slow channels message composition and SENT fast channels message composition. This message composition may be performed taking into account the configuration data stored by the configuration means 3, e.g. by taking into account at least one fully configurable data structure 23.
  • This data structure may for example comprise a table of errors ERROR_TABLE, which may be set up to link any or each error to a fast channel SENT data configuration table FS_DATA_TABLE, e.g. for defining a corresponding fast channel error code and/or a corresponding status bit to flag, and/or to a slow channel SENT data configuration table SS_DATA_TABLE, e.g. for defining a corresponding error message.
  • The configuration means 3 may receive inputs 24 to reconfigure the stored configuration data, e.g. may receive signal value configuration or memory pointer data for changing an entry in the fast or slow channel configuration table, and/or an instruction to enable or disable an entry in the table of errors and/or a priority setup table.
  • In a second aspect, the present invention also relates to a method for controlling an integrated circuit device adapted for transmitting data via a data stream in accordance with a single-edge nibble transmission protocol, e.g. for controlling a device according to embodiments of the first aspect of the present invention. Specific details relating to such method according to embodiments will be clear in view of the description provided hereinabove in relation to the first aspect of the present invention.
  • FIG. 3 shows an exemplary method 30 according to embodiments of the present invention. The method 30 comprises receiving 31 configuration instructions from a user and storing 32 configuration data in accordance with these configuration instructions. Such receiving and storing may be performed by a configuration means of a device according to embodiments of the present invention, for instance as explained hereinabove; for example configuration instructions may be received via a configuration input port and corresponding configuration data may be stored in a configuration memory, e.g. a reprogrammable non-volatile memory.
  • The method 30 further comprises controlling 33 a transmission of a data stream in accordance with a single-edge nibble transmission protocol. For example, this controlling may be performed by a processing means, e.g. a processor, as explained hereinabove. The controlling 33 of the transmission of the data stream furthermore comprises reporting 34 a plurality of diagnostic statuses via the data stream by transmitting 35 for each diagnostic status a corresponding diagnostic code defined by the configuration data, e.g. stored in the configuration memory. Reporting the plurality of diagnostic statuses is furthermore performed in a diagnostic status reporting order defined by the configuration data, e.g. stored in the configuration memory.
  • Controlling 33 of the transmission may furthermore comprise retrieving at least one address pointer from the configuration data in order to reference data or reference a program routine for acquiring such data, and transmitting these data in a SENT fast channel or in a SENT slow channel message of the data stream.
  • Controlling 33 of the transmission may also comprise detecting the plurality of diagnostic statuses and setting a status bit state in a status and communication nibble transmitted via the data stream taking into account the detected diagnostic statuses and a status bit mask in the configuration data.
  • Reporting 34 the plurality of diagnostic statuses may also comprise transmitting 35 a diagnostic code value via a SENT fast channel and/or via a SENT slow channel message.

Claims (15)

  1. An integrated circuit device (1) comprising:
    - an output port (5) for transmitting a data stream,
    - a processing means (2) for controlling the transmission of said data stream in accordance with a single-edge nibble transmission protocol, and
    - a configuration means (3) for receiving and storing configuration data, wherein said processing means (2) is adapted for reporting a plurality of diagnostic statuses via said data stream by transmitting for each diagnostic status a corresponding diagnostic code defined by said configuration data, and wherein the processing means (2) is furthermore adapted for reporting said plurality of diagnostic statuses in a diagnostic status reporting order defined by said configuration data.
  2. The integrated circuit device (1) according to claim 1, wherein said configuration means (3) is adapted for receiving configuration instructions from a user and for storing said configuration data in accordance with said configuration instructions.
  3. The integrated circuit device (1) according to any of the previous claims, wherein the processing means (2) is adapted for retrieving at least one address pointer from the configuration means (3), wherein said at least one address pointer references data or references a program routine for acquiring said data, wherein said data is to be transmitted in a corresponding SENT fast channel or in a corresponding SENT slow channel message of the data stream.
  4. The integrated circuit device (1) according to any of the previous claims, wherein the processing means (2) is adapted for detecting the plurality of diagnostic statuses and for setting a status bit state in a status and communication nibble transmitted via the data stream taking into account the detected diagnostic statuses and a status bit mask in the configuration data.
  5. The integrated circuit device (1) according to any of the previous claims, wherein the processing means (2) is adapted for reporting at least one diagnostic status of said plurality of diagnostic statuses by transmitting a diagnostic code value via a SENT fast channel.
  6. The integrated circuit device (1) according to claim 1, wherein the processing means (2) is adapted for reporting at least one diagnostic status of said plurality of diagnostic statuses by transmitting a diagnostic code value via a SENT slow channel message.
  7. The integrated circuit device (1) according to any of the previous claims, wherein the processing means (2) is adapted to retrieve at least one value from the configuration means (3) for selecting the number of nibbles to transmit per SENT telegram.
  8. The integrated circuit device (1) according to any of the previous claims, wherein said configuration means (3) comprises a configuration memory (4) for storing said configuration data.
  9. The integrated circuit device (1) according to any of previous claims, furthermore comprising input/output means (6) for acquiring and digitizing data.
  10. The integrated circuit device (1) according to any of previous claims, in which the processing means (2) comprises a data memory (7) and an instruction memory (8).
  11. The integrated circuit device (1) according to any of previous claims, in which the instruction memory (8) comprises instructions according to a program logic for controlling the input/output means (6) such as to acquire and digitize data, and for controlling the data transmission via the output port (5) such as to comply with the SENT protocol.
  12. A method (30) for controlling an integrated circuit device adapted for transmitting data via a data stream in accordance with a single-edge nibble transmission protocol, the method comprising:
    - receiving (31) configuration instructions from a user,
    - storing (32) configuration data in accordance with said configuration instructions, and
    - controlling (33) a transmission of a data stream in accordance with a single-edge nibble transmission protocol,
    wherein said controlling (33) of said transmission of said data stream comprises reporting (34) a plurality of diagnostic statuses via said data stream by transmitting (35) for each diagnostic status a corresponding diagnostic code defined by said configuration data, and wherein said reporting said plurality of diagnostic statuses is performed in a diagnostic status reporting order defined by said configuration data.
  13. The method (30) according to claim 12, wherein said controlling (33) of the transmission furthermore comprises retrieving at least one address pointer from said configuration data in order to reference data or reference a program routine for acquiring said data, and transmitting said data in a corresponding SENT fast channel or in a corresponding SENT slow channel message of the data stream.
  14. The method (30) according to claim 12 or claim 13, wherein said controlling (33) of the transmission comprises detecting the plurality of diagnostic statuses and setting a status bit state in a status and communication nibble transmitted via the data stream taking into account the detected diagnostic statuses and a status bit mask in the configuration data.
  15. The method (30) according to any of claims 12 to 14, wherein said reporting (34) the plurality of diagnostic statuses comprises transmitting a diagnostic code value via a SENT fast channel and/or via a SENT slow channel message.
EP15191631.9A 2014-10-29 2015-10-27 Flexible sent device configuration Active EP3015994B1 (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
GB1419205.8A GB2531748A (en) 2014-10-29 2014-10-29 Flexible SENT device configuration

Publications (2)

Publication Number Publication Date
EP3015994A1 true EP3015994A1 (en) 2016-05-04
EP3015994B1 EP3015994B1 (en) 2018-06-06

Family

ID=52103549

Family Applications (1)

Application Number Title Priority Date Filing Date
EP15191631.9A Active EP3015994B1 (en) 2014-10-29 2015-10-27 Flexible sent device configuration

Country Status (3)

Country Link
US (1) US10540221B2 (en)
EP (1) EP3015994B1 (en)
GB (1) GB2531748A (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4002771A1 (en) * 2020-11-19 2022-05-25 Allegro MicroSystems, LLC Signaling between master and one or more slave components to share absolute and incremental data
WO2023201130A1 (en) * 2022-04-12 2023-10-19 Allegro Microsystems, Llc Sensor signaling of absolute and incremental data

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10204024B2 (en) * 2015-06-17 2019-02-12 Ford Global Technologies, Llc Sent error generator
US10129339B1 (en) 2017-11-15 2018-11-13 Sensata Technologies, Inc. Communication system configured for transmitting sensor values from N sensing sources to a control unit
JP7205103B2 (en) * 2018-08-08 2023-01-17 富士電機株式会社 Receiving device, receiving method, and receiving program
JP7296426B2 (en) * 2021-06-22 2023-06-22 株式会社日立製作所 Management system and management method for managing information systems

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8694879B1 (en) * 2010-09-14 2014-04-08 Continental Automotive Systems, Inc Efficient use of CRC with limited data
US20140258566A1 (en) * 2013-03-08 2014-09-11 Microchip Technology Incorporated Dynamic Pause Period Calculation for Serial Data Transmission

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU665521B2 (en) * 1990-10-03 1996-01-11 Thinking Machines Corporation Parallel computer system
US6519275B2 (en) * 2001-06-29 2003-02-11 Motorola, Inc. Communications system employing differential orthogonal modulation
US20090106461A1 (en) * 2005-01-31 2009-04-23 Yokogawa Electric Corporation Information Processing Apparatus and Information Processing Method
US8250911B2 (en) * 2010-08-13 2012-08-28 GM Global Technology Operations LLC Control module response testing systems and methods
US8907437B2 (en) * 2011-07-22 2014-12-09 Allegro Microsystems, Llc Reinforced isolation for current sensor with magnetic field transducer
US8645020B2 (en) * 2012-06-21 2014-02-04 Freescale Semiconductor, Inc. Channel diagnostic system for sent receiver
US10204024B2 (en) * 2015-06-17 2019-02-12 Ford Global Technologies, Llc Sent error generator

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8694879B1 (en) * 2010-09-14 2014-04-08 Continental Automotive Systems, Inc Efficient use of CRC with limited data
US20140258566A1 (en) * 2013-03-08 2014-09-11 Microchip Technology Incorporated Dynamic Pause Period Calculation for Serial Data Transmission

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"J2716_201001 SENT - Single Edge Nibble Transmission for Automotive Applications", 27 January 2010 (2010-01-27), pages 1 - 56, XP008149400, ISSN: 0148-7191, Retrieved from the Internet <URL:http://standards.sae.org/j2716_201001/> *
INFINEON TECHNOLOGIES AG: "TLE4998S4 - Programmable Linear Hall Sensor", no. v 0.1, 1 January 2007 (2007-01-01), pages 1 - 34, XP002493681, Retrieved from the Internet <URL:http://www.infineon.com/dgdl/TLE4998S4_Target_Data_Sheet_V0_1.pdf?folderId=db3a304412b407950112b408e8c90004&fileId=db3a304412b407950112b408ec480009&location=Search.TLE4998S4_Target_Data_Sheet_V0_1.pdf> [retrieved on 20070131] *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4002771A1 (en) * 2020-11-19 2022-05-25 Allegro MicroSystems, LLC Signaling between master and one or more slave components to share absolute and incremental data
US11368533B2 (en) 2020-11-19 2022-06-21 Allegro Microsystems, Llc Signaling between master and one or more slave components to share absolute and incremental data
WO2023201130A1 (en) * 2022-04-12 2023-10-19 Allegro Microsystems, Llc Sensor signaling of absolute and incremental data

Also Published As

Publication number Publication date
GB201419205D0 (en) 2014-12-10
EP3015994B1 (en) 2018-06-06
GB2531748A (en) 2016-05-04
US10540221B2 (en) 2020-01-21
US20160124798A1 (en) 2016-05-05

Similar Documents

Publication Publication Date Title
EP3015994B1 (en) Flexible sent device configuration
CN109729628B (en) Bus protocol for dynamic lighting applications
CN106066834B (en) Bus communication with multi-device message transfer
EP3729735B1 (en) Methods and apparatus for configuring a flex ethernet node
US9519603B2 (en) Method and apparatus to enable multiple masters to operate in a single master bus architecture
KR101921771B1 (en) Method and apparatus for adapting the data transmission security in a serial bus system
CN106200567B (en) Improve the CAN communication method and data frame structure of traffic rate
CN107193252B (en) Slave device, method for controlling slave device, and recording medium
KR101711698B1 (en) Method for processing data, and data processing apparatus
CN113553285A (en) Electronic control unit, frame generation method, and recording medium
KR101923511B1 (en) Apparatus for communicating diagnostic vehicle and method thereof
CN106257854B (en) Single-side nibble transmission error generator
EP3300337A1 (en) Communication method
US20080147923A1 (en) Supplemental Communication Interface
US20140188253A1 (en) Method and system for reprogramming
EP2233255A2 (en) Data transformation network apparatus and robot controlling system and method using the same
JP2015033952A (en) Control system
CN110223620B (en) Drive control method, drive control assembly and display device
US20200409902A1 (en) Method for addressing an integrated circuit on a bus and corresponding device
CN105981319A (en) Participant station for a bus system, and method for increasing the data rate of a bus system
CN107015542B (en) Bus steering engine and control device, control system and control method thereof
KR102196371B1 (en) Reference signal mapping method and apparatus
US9491110B2 (en) Method and device for securing data packets to be transmitted via an interface
CN113223445A (en) Data transmission method and system applied to LED chip and related assembly
KR100916665B1 (en) Air-conditioner and operating method thereof

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20161028

RBV Designated contracting states (corrected)

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20180103

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

Ref country code: AT

Ref legal event code: REF

Ref document number: 1006845

Country of ref document: AT

Kind code of ref document: T

Effective date: 20180615

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602015011711

Country of ref document: DE

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20180606

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 4

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180606

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180606

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180606

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180906

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180906

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180606

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180606

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180907

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180606

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180606

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180606

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1006845

Country of ref document: AT

Kind code of ref document: T

Effective date: 20180606

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180606

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180606

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180606

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181006

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180606

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180606

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180606

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180606

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180606

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180606

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602015011711

Country of ref document: DE

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20190307

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180606

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180606

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181027

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180606

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181031

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181031

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181027

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180606

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181027

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180606

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180606

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180606

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20151027

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20191027

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20191027

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230517

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20230920

Year of fee payment: 9

Ref country code: BE

Payment date: 20230920

Year of fee payment: 9

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20230920

Year of fee payment: 9