KSENT User Manual Firmware V02 - kopfweb.de · KSENT User Manual Firmware V02.07 KOPF GmbH...

$Page 1: KSENT User Manual Firmware V02 - kopfweb.de · KSENT User Manual Firmware V02.07 KOPF GmbH Kapbachstraße 6 76829 Landau ... 17.09.2014 C:\KSent\Common\Specifications\KSENTUserManual.doc$
KSENT

User Manual

Firmware V02.07

KOPF GmbH Kapbachstraße 6 76829 Landau Telefon +49 (0)6341/91 767-0 Telefax +49 (0)6341/91 767-50 Mailto: [email protected]

KOPF GmbH – Kapbachstraße 6 – D-76829 LANDAU - TELEFON (06341) 91767-0 - TELEFAX (06341) 91767-50 – www.kopfweb.de 17.09.2014 C:\KSent\Common\Specifications\KSENTUserManual.doc

2 / 23

INDEX 1 General Information ...................................................................................................................... 3

2 Hardware ...................................................................................................................................... 6

2.1 Connector of Automotive Interface 4 SENT ............................................................................ 6

2.2 Connection-Cable .................................................................................................................. 7

2.3 Firmware Automotive Interface .............................................................................................. 7

2.4 USB Driver Installation ........................................................................................................... 7

3 PC Software „KAiUpdate“ ............................................................................................................. 8

3.1 Installation.............................................................................................................................. 8

3.2 Quick Startup ......................................................................................................................... 8

4 PC Software „KFlexExplorer“ ........................................................................................................ 9

4.1 Installation.............................................................................................................................. 9

4.2 Quick-Startup ......................................................................................................................... 9

4.3 Options SENT ...................................................................................................................... 14

4.3.1 Timer Set ....................................................................................................................... 14

4.3.2 RX Init ........................................................................................................................... 14

4.3.3 TX Init ............................................................................................................................ 14

4.3.4 CAN-Gateway Init .......................................................................................................... 15

4.3.5 Options Set.................................................................................................................... 15

5 AD-to-SENT-Converter ............................................................................................................... 17

6 SENT Status via External IOs ..................................................................................................... 18

7 SPC-Feature (Infineon TLE4998C4) ........................................................................................... 19

8 CAN-Gateway ............................................................................................................................ 20

9 Single Secure Sensors ............................................................................................................... 21

10 RS232-Communication ............................................................................................................ 22

11 AID ........................................................................................................................................... 23

11.1 USB SENT Receive All ...................................................................................................... 23

11.2 DA-Converter ..................................................................................................................... 23


3 / 23

1 General Information The following description is used for a Quick-Startup with the “Automotive Interface 4 SENT”-Tool (abbr.: AI4 SENT) in connection with the “KFlexExplorer”-Application-Software. The “Automotive Interface 4 SENT” is used as SENT-Receiver and/or SENT-Transmitter and in connection with the PC-Software “KFlexExplorer” to analyse or simulate SENT-Data. With the “KFlexExplorer” the AI4 SENT can be configured to run in autonomous operation ‘Stand-Alone’ without a PC. SENT-Communication between a User-Specific-Application and the AI4 SENT is applicable by implementing the AID.DLL, this is also applicable from LabView. For an example how to use the AID.DLL see section: KUSBTransfer. Functional survey:

• 2 SENT-Receive-Channels • 2 SENT-Transmit-Channels • 2 Channel DA-Converter • 2 Channel AD-Converter • 1 CAN-Gateway with separate ID per Fast-Channel 0/1 and Slow-Channel 0/1 • PC Interface (USB, RS232)

At max. speed with active DA-Converter-Option (resp. Serial-Communication-, CAN-Gateway- or AD-to-SENT-Converter-Option) and operation on both SENT-Channels the AI4SENT can either operate as transmitter or operate as receiver only, otherwise it is possible to operate as transmitter and receiver in parallel.


4 / 23

Firmware history: Up from Firmware V1.30 there is the possibility to save a configuration in EEPROM (see section Fehler! Verweisquelle konnte nicht gefunden werden. ) thus the AI4SENT is ‘Stand-Alone’ activated by a present configuration on system start. From Firmware V1.34 the functionality to transmit / receive Serial Communication Messages (e.g. miscellaneous information such as part numbers or fault codes) within serial data bit of ‘Status And Communication Nibble’. From Firmware V1.35 the ‘Synchronisation Period’ is transferred via USB additionally for received SENT-Frames. ! Hint: To use the ‘Synchronisation Period’ functionality the AID.DLL has to be updated and the User-Interface needs an expansion of one Sync-Parameter for the functions KSENT_RX and KSENT_RXPoll (For detailed description of Parameters see documentation of the AID.DLL). From Firmware V1.36 there is the functionality to transmit the received SENT-Frames on the user configurable CAN-Gateway (e.g.: to log SENT-Frames or display graphically within an CAN environment). From Firmware V1.37 the Clock Resolution of the SENT-Receive-Channels can be configured from 3us…to 10us clock ticks and allows a reception of messages with ±25% timing range. From Firmware V1.38 the AD-to-SENT-Converter-Option to send analogue input Voltage as digital Signal on SENT (e.g. to simulate a Sensor with the AI4) and the ‘Stand-Alone’ functionality for Transmit is available. From Firmware V1.39 the Status of received SENT-Frames or a Timeout on SENT is output via two external IOs for each SENT-Receive-Channel (For detailed description see Chapter 6). With Firmware V1.41 the SPC-Feature with overlaid master trigger pulse within synchronisation period (Infineon TLE4998C4) is implemented as Sensor simulation or ECU interface (For detailed description see Chapter 7). ! Hint: To use the SPC-Feature the AI4SPC cable (Art. No.: 070 010 172) is required. From Firmware V1.42 there is the functionality to receive data on the user configurable CAN-Gateway and transmit the data via SENT-Frames (e.g.: to change SENT-Data within an CAN environment). With Firmware V1.43 the “NEW” SPC-Feature with separated master trigger pulse (Infineon TLE4998C4) is implemented as Sensor simulation or ECU interface (For detailed description see Chapter 7). ! Hint: To use the SPC-Feature the AI4SPC cable (Art. No.: 070 010 172) is required. Firmware V1.46 additionally communication with the AI4 SENT via RS232 (e.g. for SPS applications) is possible, except for monitoring applications with high data rates (For further description see Chapter 9). Firmware V2.00 supports either the legacy checksum generation (according to SAE J2716 standard in revision FEB2008 and older) or the new recommended checksum generation (according to SAE J2716 standard in revision JAN2010) and with Slow-Serial-Message-Communication (in Short resp. Enhanced format) optionally. ! Hint: “KFlexExplorer V2.00” or newer Versions required. Firmware V2.04 supports Basic-Clock-Ticks up to nominal 90µs.


5 / 23

! Hint: “KFlexExplorer V2.04” or newer Versions required. Firmware V2.07 supports reception or transmission of Single Secure Sensor protocol features (Rolling-Counter and Inverted-Copy) optionally. Support CAN-Gateway feature with additional output of Slow-Serial-Message-Communication. ! Hint: “KFlexExplorer V2.07” or newer Versions required.


6 / 23

2 Hardware Following there is a Technical-Data description and the individual steps that are necessary in order to operate with the AI4SENT. Bestelloptionen 070 010 240: 12-Bit DA-Wandler 070 010 240A: 16-Bit-DA-Wandler

2.1 Connector of Automotive Interface 4 SENT Connector of AI4SENT (Sub-D Connector – Male):

Supply (USB or Sub-D-Pin can used): 14

1 2 3 4 5 6 7 98 10 11 12 13

15 16 17 18 19 20 21 22 23 24 25 1 VCC (5V ±4%) 2, 25 GND

SENT-Transmitter (J2716 5V):

6 Channel 0 20 Channel 1

SENT-Receiver (J2716 5V):


SENT-Trigger Out (5V CMOS, Attention: No over voltage protection on this pins) 12 Channel 0, High during first SENT-Nibble 21 Channel 1, High during first SENT-Nibble SENT-Trigger In (5V CMOS, Attention: No over voltage protection on this pins) 13 Channel 0, Rising Edge Sensitive 19 Channel 1, Rising Edge Sensitive Analog Input (12V, 10Bit):


Analog Output (5V, 12Bit Optional: 16 Bit, Attention: No over voltage protection on this pins)

22 Channel 0 8 Channel 1 5 Ext. Reference In – Default: Connect to Pin 1 to use internal VCC For high precision applications an external 5V DA Reference better than ±2%

could be applied. RS232: 9 RxD 10 TxD 11 CTS (not used) CAN (High Speed, internal termination 180R):

3 CAN Low 4 CAN High


7 / 23

External IO4: 23 Channel 0, High during Nibble- or CRC-Error on SENT

External IO6:

7 Channel 1, High during Nibble- or CRC-Error on SENT External IO5 (only repeatedly transmission without pause):

24 Channel 0, High during Timeout on SENT External IO7 (only repeatedly transmission without pause):

18 Channel 1, High during Timeout on SENT

2.2 Connection-Cable The AI4SENT Connection-Cable is not included in delivery but available on request. The AI4SPC Connection-Cable is not included in delivery but available on request.

2.3 Firmware Automotive Interface Firmware-Updates can be programmed with the software “KAiUpdate” which is available for free. For a detailed description how to do the Firmware-Update see: AIUsbCommunication.doc. Visit our Homepage for more information about the current Versions and for further development Downloads (www.kopfweb.de).

2.4 USB Driver Installation When the AI4SENT is plugged the first time to the USB-Interface of a PC the appropriate USB-Driver is required. You can find the latest USB-Driver in the download area on our homepage http://kopfweb.de/index.php/de/download-ftp within the “USBDriver” folder. After installation the PC detects the AI4SENT as „Automotive Interface USB“.


8 / 23

3 PC Software „KAiUpdate“ The software “KAiUpdate” is used to update the AI4SENT device with another firmware or to read its version info. You can find this tool in the Download area on our homepage http://kopfweb.de/index.php/de/download-ftp within the “KAiUpdate” folder. There are no specific system requirements to fulfil except a free USB-Port. Possibly the additional installation of NET-Frameworks will be required which is included on CD.

3.1 Installation Installation of the Application-Software gets started by double clicking on the file “KAiUpdate.exe” (see folder: KSENT\KAiUpdate). The installation manger directs you through the installation procedure.

3.2 Quick Startup Please follow these steps to update your AI4 device with a different firmware:

1. Connect the AI4 device to the USB port of your PC 2. Now start the KAiUpdate-Tool

3. Press Refresh to list all detected AI’s 4. Select one of the listed AI4 device you would like to update 5. Press Select custom Firmware and browse to the destination folder of the firmware file

(KSENT_*.s19) 6. It is important that the two check boxes on the right-hand side of the update button are both

active 7. Now press the Update button


9 / 23

4 PC Software „KFlexExplorer“ The software “KFlexExplorer” is for Basic-Configuration and SENT-Analysis /-Simulation with the AI4SENT. You can find this tool in the Download area on our homepage http://kopfweb.de/index.php/de/download-ftp within the “KFlexExplorer” folder. There are no specific system requirements to fulfil except a free USB-Port. Possibly the additional installation of NET-Frameworks will be required which is included on CD.

4.1 Installation Installation of the Application-Software gets started by double clicking on the file “Setup.exe” (see folder: KSENT\Windows\Release). The installation manger directs you through the installation procedure.

4.2 Quick-Startup After installation there is created an Item „KFlexExplorer“ in the Windows Start-Menu as well as on the Desktop. Double clicking on the Desktop-Icon is starting the Software. Note: Select SENT for Bustype (Menu Bustype item SE NT)


10 / 23

With menu item Options/SENTConfig the ‘SENTOptions’ window is displayed.

Basically:

1. Select connected AI in box Select AI Serial Number 2. Select the required timing range of the AI in box Resolution 3. Optional: open a LogFile for SENT-Data logging 4. Press OK to confirm SENTOptions

Init as Receiver:

1. RX Init Len: Set SENT-Frame-Length in Nibbles to be received 2. RX Init TimeUnit: Set Basic-Clock-Tick in µs 3. Enable CRC whether the checksum has be checked or not

Init as Transmitter:

1. TX Init Len: Set SENT-Frame-Length in Nibbles for transmission 2. TX Init TimeUnit: Set Basic-Clock-Tick in µs 3. TX Init SyncLow: Set low time (e.g. 5*TimeUnit) of Sync-Pulse in µs 4. TX Init SyncHigh: Set high time (e.g. 51*TimeUnit) of Sync-Pulse () in µs 5. Enable CRC whether the checksum has be generated or not


11 / 23

Start of SENT-Transceiver: 1. Press Run 2. Status: Changes from Stop to Running 3. Display of received SENT-Data

Send single SENT-Frames:

1. Input the Data-Bytes (Hex.) in the lower window at Ch0 or Ch1 2. Set Ch0/1-Cyclic: 1 3. Select the SENT-Frames by click on Ch0 or Ch1 4. Press Send

Send continuous SENT-Frames:

1. Input the Data-Bytes (Hex.) in the lower window at Ch0 or Ch1 2. Set Ch0/1-Cyclic: 0 3. Select the SENT-Frames by click on Ch0 or Ch1 4. Press Send

Send cyclic SENT-Frames:

1. Input the Data-Bytes (Hex.) in the lower window at Ch0 or Ch1 2. Set Ch0/1-Cyclic: 5000 (e.g. for 5ms cycle) 3. Select the SENT-Frames by click on Ch0 or Ch1 4. Press Send

In menu Options/SendSerialCom the ‘SENT Serial Comm unication’ window is displayed.

Send SENT-Frames with Short Serial Message Communic ation:

1. Precondition: Serial Message Communication - Short is enabled at TX Init configuration in SENT Options menu 2. Configure Serial Messages for any index (1...16) at Ch0 or Ch1 3. Enable/Disable the Serial Message


12 / 23

4. Input the Serial-ID-Address (Hex. 0..F) 5. Input the Serial-Data-Byte (Hex.) to be transmitted 6. Press Send

Short Serial Messages Communication is send continuously index-by-index when enabled. Each Serial Message is transmitted bitwise within ‘Status And Communication’ Nibble in a sequence of 16 consecutive SENT Frames (for detailed information refer to SAE J2716 standard). Send SENT-Frames with Enhanced Serial Message Commu nication:

1. Precondition: Serial Message Communication - Enhanced is enabled at TX Init configuration in SENT Options menu 2. Configure Serial Messages for any index (1...16) at Ch0 or Ch1 3. Enable/Disable the Serial Message 4. Choose the Data-Field (0: 12Bit Serial-Data with 8Bit Serial-ID; 1: 16Bit Serial-Data with 4Bit Serial-ID) 5. Input the Serial-ID (Hex. 0…FF resp. 0…F) 6. Input the Serial-Data (Hex. 0…FFF resp. 0…FFFF) to be transmitted 7. Press Send

Enhanced Serial Messages Communication is send continuously index-by-index when enabled. Each Serial Message is transmitted bitwise within ‘Status And Communication’ Nibble in a sequence of 18 consecutive SENT Frames (for detailed information refer to SAE J2716 standard). Receive SENT-Frames with Short or Enhanced Serial M essages Communication:

1. Precondition: Serial Message Communication – Short or Enhanced is enabled at RX Init configuration in SENT Options menu 2. Reception of SENT-Frames with Options Set: OperationMode = “Monitoring Mode” and

TriggerInX = “Off” Reception of Serial Messages is displayed as separated data within Received Messages edit and indicated with Type ‘Serial Com’ (e.g. Serial Com ⇒ ID, Data, CRC). Choose type of CRC generation:

1. Select the type of CRC generation (0: legacy CRC implementation according to old SAE J2716 standard in revision FEB2008 or older; 1: recommended CRC implementation according to new SAE J2716 standard in revision JAN2010)

Send single SPC-Frames:

1. Precondition: TX Init ‘SPC’ in Menu SENTOptions is enabled 2. Input the Data-Bytes (Hex.) in the lower window at Ch0 or Ch1 3. Set Ch0/1-Cyclic: 1 (send single SPC-Frame per external trigger pulse) 4. Select the SPC-Frame to transmit by clicking on Ch0 or Ch1 5. Press Send

Receive cyclic SPC-Frames (by generating SPC-Pulse for Sensor):

1. Precondition: RX Init ‘SPC’ in Menu SENTOptions is enabled 2. Value of Data-Bytes (Hex.) in the lower window at Ch0 or Ch1 is don’t care 3. Set Ch0/1-Cyclic: 1000 (e.g. for 1ms SPC-Pulse cycle; Max. 2,4ms) 4. Select the SPC-Pulse to generate by clicking on Ch0 or Ch1 5. Press Send

Stand-Alone operation:

1. Precondition: In addition to user defined Settings in Menu SENTOptions 2. Select ‘Stand-Alone’ as Operation Mode at Option Set 3. Press OK


13 / 23

CAN-Gateway operation: 1. Precondition: In addition to user defined Settings in Menu SENTOptions 2. Select required ‘Baudrate’ 4. Enable or Disable ‘Extended Mode’ (Extended or Standard Identifier format) 5. Enable ‘Enable’ for RX or TX (receive or transmit on CAN) 6. Set ‘IDs’ of Channel 0 and 1 7. Press OK

Example of SENT-to-CAN-Gateway with SPC. Example of CAN-to-SENT-Gateway with SPC.


14 / 23

4.3 Options SENT

4.3.1 Timer Set All information’s refer to both SENT- Receiver- and Transmitter-Channels. Resolution: High: Res. of one nominal* SENT-Clock-Tick (max. 22µs*) in 40ns Steps

Mid: Res. of one nominal* SENT-Clock-Tick (max. 45µs*) in 80ns Steps Low: Res. of one nominal* SENT-Clock-Tick (max. 90µs*) in 160ns Steps *a tolerance of additional 30% is applicable for Receiver and Transmitter.

4.3.2 RX Init All information’s refer to both SENT-Receiver-Channels. Len: Number of Nibbles per frame CRC: 0: Disable

1: Enable CRC in last nibble (excluding ‘Status And Communication Nibble’ except SPC-Feature is including)

RC: 0: Disable 1: Enable 8 bit Rolling-Counter (= 0 to 255 with rollover back to 0) in nibble 4 and 5 according to Single Secure Sensor specification in SAE J2716

IC: 0: Disable 1: Enable Inverted-Copy (= 15 - nibble 1 value) in nibble 6 according to Single Secure Sensor specification in SAE J2716

TimeUnit: Time for one SENT-Clock-Tick in x[ns] Steps (x: Resolution) Default: 3µs (75*40ns)

SerialMsgFormat: 0: Disable 1: Enable Short Serial Message Communication within ‘Status And Communication Nibble’ 2: Enable Enhanced Serial Message Communication within ‘Status And Communication Nibble’

SPC: 0: Disable 1: Enable SPC V1-Feature (TLE4998C4 with overlaid master trigger pulse within synchronisation period) to receive real sensor data 2: Enable SPC V2-Feature (TLE4998C4 with separated master trigger pulse) to receive real sensor data

MasterLowTime: Time of SPC master trigger low pulse (tmlow) in x[ns] Steps (x: Resolution) Default: 8,24µs (206*40ns)

4.3.3 TX Init All information’s refer to both SENT-Transmitter-Channels. Len: Number of Nibbles per frame CRC: 0: Disable

1: Enable CRC in last Nibble (excluding ‘Status And Communication Nibble’ except SPC-Feature is including)

RC: 0: Disable 1: Enable 8 bit Rolling-Counter (= 0 to 255 with rollover back to 0) in nibble 4 and 5 according to Single Secure Sensor specification in SAE J2716

IC: 0: Disable


15 / 23

1: Enable Inverted-Copy (= 15 - nibble 1 value) in nibble 6 according to Single Secure Sensor specification in SAE J2716

TimeUnit: Time for one SENT-Clock-Tick in x[ns] Steps (x: Resolution) Default: 3µs (75*40ns)

SyncLow: Low-Time of the Sync Pulse in x[ns] Steps (x: Resolution) Default: 15µs ⇒ 5*Clock-Ticks (375*40ns)

SyncHigh: High-Time of the Sync Pulse in x[ns] Steps (x: Resolution) Default: 153µs ⇒ 51*Clock-Ticks (3825*40ns)

SerialMsgFormat: 0: Disable 1: Enable Short Serial Message Communication within ‘Status And Communication Nibble’ 2: Enable Enhanced Serial Message Communication within ‘Status And Communication Nibble’

SPC: 0: Disable 1: Enable SPC V1-Feature (TLE4998C4 with overlaid master trigger pulse within synchronisation period) to transmit simulated sensor data 2: Enable SPC V2-Feature (TLE4998C4 with separated master trigger pulse) to transmit simulated sensor data

TotalTriggerTime: Time of SPC total master trigger pulse (tmtr) in x[ns] Steps (x: Resolution) Default: 39µs (975*40ns)

4.3.4 CAN-Gateway Init All information’s refer to both SENT-Transmitter-Channels. Baudrate: Baudrate for CAN-Gateway (High-Speed-Bus) in Kbit/s: 33,333 / 50 / 62,5 / 83,333 / 100 / 125 / 200 / 250 / 333,333 / 500 / 1000 Extended Mode: 0: Standard Format (11-Bit Identifier) when disabled 1: Extended Format (29-Bit Identifier) when enabled CANGw0: 0: TX / RX – Disable

1: TX – Enable data transmission via SENT to CAN-Gateway on Channel 0 2: RX – Enable data reception via CAN to SENT-Gateway on Channel 0

CANId0: Identifier for CAN-Gateway on Channel 0 CANGw1: 0: TX / RX – Disable

1: TX – Enable data transmission via SENT to CAN-Gateway on Channel 1 2: RX – Enable data reception via CAN to SENT-Gateway on Channel 1

CANId1: Identifier for CAN-Gateway on Channel 1

4.3.5 Options Set Operation Mode: 0: Polling Mode – Received SENT-Frames not send direct via USB

AND clear stored Options in the EEPROM 1: Monitoring Mode – Received SENT-Frames send direct via USB

AND not store Options in the EEPROM 2: Stand-Alone Mode – Received SENT-Frames not send direct via USB

AND store Options to the EEPROM TriggerIn0 / 1: 0: Off – No trigger is used for sending SENT-Frame via USB / DA

1: Next Received – On trigger next received SENT-Frame is send via USB / DA 2: Last Buffered – On trigger last buffered SENT-Frame is send via USB / DA SAE J2716: Select type of CRC generation

0: Legacy (according to SAE J2716 standard in revision FEB2008 or older) 1: Recommended (according to SAE J2716 standard in revision JAN2010) DAMode: Unused DA0Bit: DA for RX-Channel 0: Bit Number of the 1st Bit (count bits from the left-hand

side, including Status&Communication nibble)


16 / 23

DA0Len Bit0-6: DA for RX-Channel 0: Number of Bits DA0Len Bit7: 0: MSN first, 1: LSN first DA1Bit: DA for RX-Channel 1: Bit Number of the 1st Bit (count bits from the left-hand

side, including Status&Communication nibble) DA1Len Bit0-6: DA for RX-Channel 1: Number of Bits DA1Len Bit7: 0: MSN first, 1: LSN first ADGain: Multiplier for AD-Converter of TX-Channels

1)2(

10231000

max

−=→

××=

ADLenSENT

SENT

AIN

ExtRefInADGain

(For calculation see following description: “5. AD-to-SENT-Converter ”) AD0Bit: AD for TX-Channel 0: Bit Number of the 1st Bit (count bits from the left-hand

side, including Status&Communication nibble) AD0Len Bit0-6: AD for TX-Channel 0: Number of Bits AD0Len Bit7: 0: MSN first, 1: LSN first AD1Bit: AD for TX-Channel 1: Bit Number of the 1st Bit (count bits from the left-hand

side, including Status&Communication nibble) AD1Len Bit0-6: AD for TX-Channel 1: Number of Bits AD1Len Bit7: 0: MSN first, 1: LSN first


17 / 23

5 AD-to-SENT-Converter General description of the AD-to-SENT-Converter functionality by means of following flowchart from analogue Voltage to digital SENT Signal:

• Analogue input AIN (AIN0 or AIN1) with potential divider for voltage in range 0…15V • An external reference for the AD-Converter ExtRefIn with max. 5V • A/D-Converter with 10Bit resolution • The Multiplier ADGain to convert from different AD-Voltage-Ranges to SENT-Signals • Temporary calculation of internal Variables • Output on SENT (Sent0Out or Sent1Out) with configured resolution (by ADLen )

Formula for calculation of ADGain:

1)2(

10231000

max

−=→

××=

ADLenSENT

SENT

AIN

ExtRefInADGain

Example calculation of ADGain for 10Bit AD-Converte r to 12Bit SENT-Signal:

1. Analogue input AIN0 (Pin15) is in range 0…5V ⇒ AINmax = 5V 2. As external reference ExtRefIn (Pin5) the VCC (Pin1) is used ⇒ ExtRefIn = 5V 3. SENT-Signal output with AD0Len (Options Set) 12Bit resolution ⇒ ADLen = 12 4. Calculate ADGain:

4003

9,400210234095

55

1000

40951)2( 12

≈

=××=

=−=→

ADGainV

VADGain

SENT


18 / 23

Table of different calculations for ADGain:

AIN ExtRefIn SENT 4Bit 8Bit 10Bit 12Bit 16Bit

5V 5V 15 249 1000 4003 64062 10V 5V 7 125 500 2001 32031 12V 5V 6 104 417 1668 26692

6 SENT Status via External IOs Detailed description of the different States of received SENT-Frames or a Timeout on SENT output via two External IOs for each SENT-Channel (e.g. as HW trigger for measurement):

• Nibble-Error is set a) within the active SENT-Frame by a Nibble-Value < 0 or > 15 or b) by missing Nibble/s of active SENT-Frame, but within reception of

the next valid ‘Synchronisation Period’ (dependent on settings of RX Init ‘Len’).

• CRC-Error is set if the checksum of a completely received SENT-Frame is not correct (dependent on settings of RX Init ‘CRC’).

• RC-Error is set if the sequence of the Rolling-Counter is not received correctly (dependent on settings of RX Init ‘RC’).

• IC-Error is set if the value of the Inverted-Copy is not received correctly (dependent on settings of RX Init ‘IC’).

• SENT-Timeout is set by missing Frame/s or if no valid ‘Synchronisation Period’ is received. The Timeout is set if the time since last falling edge gets greater than maximum Pause-Pulse length (of 768 Ticks – time is dependent on settings of RX Init ‘TimeUnit’).

• Next valid ‘Synchronisation Period’ resets all Error-/Timeout-States.

*Output of RC- or IC-Error is equivalent to CRC-Error.


19 / 23

7 SPC-Feature (Infineon TLE4998C4) General description of the SPC-Feature for simulating or monitoring the Infineon TLE4998C4 Sensor. The AI4SENT can either operate as transmitter (when TX Init ‘SPC’ enabled) or as receiver (when RX Init ‘SPC’ enabled) for the Infineon SPC-Protocol – therefore an additional AI4SPC cable (Art. No.: 070 010 172) is required. SPC V1 Mode: In this mode the master trigger pulse is generated within the synchronisation period and the basic clock tick is calculated with the status nibble. SPC V2 Mode: In this mode the master trigger pulse is generated within a separated trigger period and the basic clock tick is calculated with the synchronisation period. Some basic limitations for Parameters:

• Number of SPC-Nibbles is configurable from 1...8 • Cycle of SPC-Frames (when TX Init ‘SPC’ enabled) is fixed to TX ‘Cyclic’ = 1 • Cycle of SPC-Pulses (when RX Init ‘SPC’ enabled) is limited to TX ‘Cyclic’ 1…2400µs

Additional limitations for Parameters of ‘SPC V1’ are given with the TLE4998C4:

• Settings of DA-Converter are fixed to Options Set ‘DAxBit’ = 4, DAxLen = 12 • Only with ‘Status And Communication Nibble’ = 3 (workaround for the first TLE4998C4

charge) Transmit SPC-Frames: When AI4 is operating as a transmitter: If the AI4 gets an external SPC-Pulse trigger (e.g. by ECU) via the SPCxOut line, it will output an SPC-Frame on this line. For configuration see Chapter 4.2 (as ‘Stand-Alone’ transmitter). Receive SPC-Frames: When AI4 is operating as a receiver: The AI4 outputs an SPC-Pulse via the SPCxOut line to trigger an SPC-Frame from a Sensor (e.g. TLE4998C4) connected to this line. For configuration see Chapter 4.2 (as ‘Stand-Alone’ receiver). Description of the AI4SPC connection cable: Supply: red VCC (external 5V supply used only for ‘Stand-Alone’ operation) brown GND SPC-Transmitter or SPC-Receiver: yellow SPC0Out, TX → connect to ECU SPC-Input RX → connect to Sensor SPC-Output blue SPC1Out, TX → connect to ECU SPC-Input RX → connect to Sensor SPC-Output Analog Output (5V, 12Bit Optional: 16 Bit, Attention: No over voltage protection on this pins)

grey AOut0 pink AOut1 – ExtRefIn, is internally connected to VCC supply


20 / 23

8 CAN-Gateway General description of the CAN-Gateway feature for either transmitting or receiving via CAN:

• CAN-to-SENT -Gateway as interface to receive data via CAN and to transmit this data 1:1 on SENT

• SENT-to-CAN -Gateway as interface to receive SENT data and transmit this data 1:1 via CAN (optionally decoded slow-channel data on separate CAN-Identifier)

• Configurable ID (extended or standard format) for each SENT fast- and slow-channel* • One High speed CAN bus with selectable Baud rate (up to 1Mbit/s)

*Separate CAN-Identifier for decoded slow-channel data is only supported with SENT-to-CAN

SENT-to-CAN-Gateway: When ‘CANGw Tx’ is selected then the AI4 will copy (nibble by nibble aligned at the left) the received SENT-Frame data into the CAN-Message to be transmitted. If the CRC calculation is enabled the CRC-Nibble will contain the actually received checksum. Each SENT-Channel has its specific CAN-Identifier on the shared high speed CAN bus. CAN-to-SENT-Gateway: When ‘CANGw Rx’ is selected then the AI4 will copy (nibble by nibble aligned at the left) the received CAN-Message data into the SENT-Frame to be transmitted. If the CRC calculation is enabled the CRC-Nibble will be overwritten by the internally calculated checksum. Each SENT-Channel has its specific CAN-Identifier on the shared high speed CAN bus. Exemplary layout of copying data from SENT-to-CAN (CAN-to-SENT vice versa):

Exemplary layout of copying decoded slow-channel data from SENT-to-CAN: CAN

CAN

CAN

t [µs]

DLC = 4 Bytes Byte0 Byte1 Byte2 Byte3

CAN ID0/1 8-bit ID 12-bit Data field6-bit

CRC0

t [µs]

DLC = 4 Bytes Byte0 Byte1 Byte2 Byte3

CAN ID0/1

4-

bit

ID

16-bit Data field6-bit

CRC1

//

//

Bit[7:0] Bit[7:0] Bit[7:4] Bit[7:4]Bit[1:0] Bit[0]

Bit[7:4] Bit[3:0] Bit[7:4] Bit[7:4]Bit[7:0] Bit[1:0] Bit[0]

t [µs]

DLC = 2 Bytes Byte0 Byte1

CAN ID0/1

4-

bit

ID

8-bit Data

field

4-

bit

CRC

//

Bit[7:4] Bit[3:0]Bit[7:4] Bit[3:0]

Short Serial Message Format:

Enhanced Serial Message Format with 8-bit Identifier and 12-bit Data field (Config = 0):

Enhanced Serial Message Format with 4-bit Identifier and 16-bit Data field (Config = 1):


21 / 23

9 Single Secure Sensors General description of the Single Secure Sensor feature (according to Single Secure Sensor specification in SAE J2716) with the AI4 SENT. Some parameters of the Single Secure Sensor interface are fixed to the following settings:

• “Len” must be 8 nibble • “RC” is the 8 bit Rolling-Counter (0 to 255 with rollover back to 0) in nibble 4* and 5* • “IC” is the Inverted-Copy (15 – nibble 1* value) in nibble 6*

*The nibble indexes are counted from zero including the Status and Communication nibble 0.

The Single Secure Sensor interface can be used to simulate or monitor the SENT communication of single secure sensors with the AI4 SENT.


22 / 23

10 RS232-Communication General description of the RS232-Communication feature for simple applications with no need of high data rates (e.g. controlling applications by SPS). The parameters of the RS232 interface are fixed to the following settings:

• 9600 Baud • None Parity • 1 Stop-Bit

The RS232 Interface can be used to control the AI4 SENT and / or sample on states and frames of the SENT communication. ! Hint: With this RS232 Interface it is not possible to receive as high data rates as needed for logging every frame of the SENT communication. For detailed description of the communication protocols refer to documentation of the AID.DLL (see Chapter 5 SSLP). For detailed description of the communication parameters and services refer to documentation of the AID.DLL (see Chapter 6 Parameters and Services – for KSENT Commands).


23 / 23

11 AID The AID.DLL is delivered as open Interface to the AI4. For detailed description of the API calls see AID-Documentation.

11.1 USB SENT Receive All With KSENT_RX function it is only possible to receive data when before the parameter TriggerInMode is set to 1 with KSENT_OptionsSet. In this mode the received SENT-Data has to be called cyclically via USB otherwise the AI is executing an internal RESET after typ. 5s to cancel the USB-Mode.

11.2 DA-Converter Parameters for the DA-Converter by function call of OptionsSet (AID & KUSBTransfer): DA0Bit: DA for RX-Channel 0: Bit Number of the LSBit DA0Len Bit0-6: DA for RX-Channel 0: Number of Bits DA0Len Bit7: 0: MSN first, 1: LSN first DA1Bit: DA for RX-Channel 1: Bit Number of the LSBit DA1Len Bit0-6: DA for RX-Channel 1: Number of Bits DA1Len Bit7: 0: MSN first, 1: LSN first DA Parameters for Pedal-Sensor FPM with TC667/MLX90 316: DA0Bit: 0 DA0Len Bit0-6: 12 DA0Len Bit7: 1 ⇒ DA0Len = 140 DA1Bit: 0 DA1Len Bit0-6: 12 DA1Len Bit7: 1 ⇒ DA1Len = 140

Date post:	03-Mar-2019
Category:	Documents
Upload:	vandan
View:	269 times
Download:	0 times

KSENT User Manual Firmware V02 - kopfweb.de · KSENT User Manual Firmware V02.07 KOPF GmbH...

Documents