PSoC™ Creator Component Datasheet - Single Edge Nibble Transmission (SENT_TX) 1.0
The Single Edge Nibble Transmission (SENT) encoding scheme is intended for automotive applications as a simple low cost alternative to CAN or LIN. It transmits sensor data from a sensor module to an Engine Control Unit (ECU).
SENT is a one wire (apart from Supply & Ground), unidirectional communications scheme from a sensor/transmitting device to a controller/receiving device, which does not include a coordination signal from the controller/receiving device. Transmission occurs independently of any action of the receiver module; that is, the transmission shall not require a synchronization signal from the receiver module. The sensor signal is transmitted as a series of pulses with data encoded as falling to falling edge periods.
Assumptions used to design the encoding scheme:
- Actual Transmission time may be dependent on the data values being sent and the actual clock variation of the Component.
- Message pulse order is fixed & always containing 6 data nibbles.
- Maximum allowed clock tick time variation is <= ±20%.
- Transmission time for the longest data message and max transmitter clock variation is less than 1.0 millisecond at 3 microsecond clock tick time and 6 data nibbles.
Note that this SENT_TX Component defines only the physical and data link layers of SAE J2716 APR2016 (Issued 2007-04, Revised 2016-04) protocol implementation. You can add your stack on top of this based on your application. At the end, top level stack you will need to provide necessary values for Status/Communication, Data, and pulses, which will be converted into pulse widths and sent out by this SENT_TX Component.
- Compliant with SAE J2716 APR2016 (Issued 2007-04, Revised 2016-04) without any serial message formats
- Selectable clock tick period (3 to 90 µs)
- Optional Pause Pulse for constant frame length of 282 clock ticks
- Supports both Legacy CRC & New CRC implementations
- Selectable Transmit Mode