LDC1612: IDRIVEx register setting results

David,

The data sheet advice (section 7.4.1) is to configure the device in Sleep Mode.
If an active device is to be reconfigured, it needs to first be put in Sleep mode, reconfigured, and then exit out of Sleep mode. 
Is the customer using this sequence?

The field INIT_DRIVEx field is used to store the initial drive current that is measured during the calibration phase.
Can the customer read this value and share it?

Also, the data sheet advises the user to set the field INIT_DRIVEx to b00000 when writing to the IDRIVEx bits. 
Can you confirm the customer is doing this?

Can the customer monitor the sensor signal pins that corresponds to the two IDRIVEx settings with a high impedance probe and a oscilloscope?
It would be helpful to see the INxA and INxB waveforms with respect to ground. If they can measure the differential signal between the pins, that might be helpful as well.
Are the sensor signal frequencies close to the intended values?
The idea behind these questions are to confirm the sensor signals do indeed agree with the STATUS bits values they are seeing.

Regards,
John

Hi John

Much appreciate your response.

Got a question, you mentioned that the device needs to be put into sleep mode for reconfiguration, does it mean that the device can't be reconfigured when active? I spot that there's RP_OVERRIDE_EN function which allows the register configuration while active, I think the customer was using this instead of the sleep mode.

*Edited: The customer confirmed the STATUS became normal after using the sleep - configure - active sequence. Could you elaborate a bit what & why issues would happen if the customer try to temper the IDRIVE when the device is active?

The customer is trying to get the waveform at the moment, I will get you posted.

Regards

Hi John

Got it.

Adding another question, about the I2C timing.

Is a wait time required before reconfiguring the device after putting device to sleep mode? Also is such time required after configuring the device before putting the device back to active again?

I saw the datasheet mentions tBUF：min1.3μs, does this mean the timing is good as long as this wait time is met?

Regards

David,

The t_wakeup ≤ 2ms given in the data sheet is the delay from the DISABLED state to the SLEEP state.
Going from NORMAL to SLEEP will be less than about half of that, or ≤ 1ms.
Going from SLEEP to NORMAL will be about 0.38ms.

regards,
John

Hi John

I have found the 0.38ms specification in the DS, is the ≤ 1ms specification noted somewhere in DS as well?

Regards