Bender ISOMETER iso165C - 6 Operation; Messages; Imd_Info; Imd_Request

iso165C_D00154_03_M_XXEN/01.2019
15
Operation
6. Operation
6.1 Messages
Communication between a requesting instance in the vehicle environment and the ISO-
METER® takes place over the HS-CAN bus. The ISOMETER® can handle the following
HS-CAN messages:
The messages contain either DataByte or DataWord values. The byte order for the Data-
Word values is:
6.2 IMD_Info
IMD_Info is cyclically sent once per second from the ISOMETER® and contains data values
that represent the insulation resistance and the internal operating states of the VIFC and
IMC.
Data value descriptions can be found in Chapter 7.3 on page 20.
The following example contains IMC status information:
*DLC = Data Length Code
Message CAN-ID Direction Cyclic
IMD_Info 0x37 Tx 1s
IMD_Request 0x22 Rx -
IMD_Response 0x23 Tx -
Byte order
DataByte
7............0
Byte order DataWord
LowByte HighByte
7............0 15...........8
Byte no.012345 6 7
D_IMC_R_ISO D_IMC_STATUS D_VIFC_STATUS Unused Unused
CAN-ID
(Info)
DLC* Data1 Data2 Data3 Data4 Data5 Data6
0x37 0x6 dc dc
IMC_STATUS_LS
B
IMC_STATUS_MSB dc dc
6.3 IMD_Request
IMD_Request is a request to the ISOMETER® and will always generate an answer message
IMD_Response. It can handle Control (CTL), SET and GET commands.
A request has the following format:
Definitions of DataWord1 and DataWord2 for different commands can be found in "Command descriptions"
on page 17.
For synchronous processing of the asynchronously received IMD_Request commands,
the VIFC implements a queue which operates on the First In, First Out (FIFO) principle. If
the queue is full, an error response is generated and the request is dropped by the ISO-
METER®. The “Queue full“ error response is not generated for every single request and
may be generated only after a certain number of requests have been made.
To avoid processing commands that could mistakenly modify the system configuration
during standard operation, the ISOMETER® has implemented a locking mechanism. The
locking state can be changed with the command S_VIFC_CTL_LOCK.
Byte01234 5 6 7
CMD Data1 Data2 Data3 Data4
Unused Unused Unused
DataWord1 DataWord2
Control (CTL) commands
CMD DBC command description Locked
0x21 S_IMC_CTL_SELFTEST
0xC8 S_VIFC_CTL_IMC_RESET
0xCA S_VIFC_CTL_LOCK
0xCB S_VIFC_CTL_MEASUREMENT
SET commands
CMD DBC command description Locked
0x28 S_IMC_SET_R_ISO_ERR_THR X
0x29 S_IMC_SET_R_ISO_WRN_THR X
0x2B S_IMC_SET_MEAN_FACTOR X
0xD2 S_VIFC_SET_HV_RELAIS