DRV2605: diagnostic fail

Zoe Ko

Expert 3810 points

Part Number: DRV2605
Other Parts Discussed in Thread: USB2ANY, DRV2625, DRV2625EVM-CT,

Hi team,

Have you ever been drv2605 reports diagnostic fail” but “vibrator still works normally?

Do you have any ideas or any suggestions?

Thank you!

The following is the test steps:

# Set Diagnostic Mode

haptic w 0x01 0x06

# Set GO bit

haptic w 0x0c 0x01

# Check if vibrator vibrates

# Read the register 0x0c (GO bit) and 0x00 (Status)

haptic r 0x0c

haptic r 0x00

if the values of status register is 0x60 or 0x64, PASS; otherwise, FAIL.

There are some devices that the vibrator works well but the status register (0x00) of haptic IC drv2605 shows 0x6C.

(Normally, 0x60 or 0x64 is expected)

over 7 years ago

0 Yinuo Hsiao over 7 years ago

Prodigy 140 points

We got '6C' of status register after diagnostic. In previous experience, '6C' means the vibrator may be stuck or open. Is there any other cases when status register shows '6C'? Thank you.

0 Ivan Salazar over 7 years ago in reply to Yinuo Hsiao

TI__Guru** 108975 points

Hi Zoe, Samma,

What is the actuator you're using?
Have you set the input parameters for auto calibration? Are you running calibration before the diagnostics?

Best regards,
-Ivan Salazar
Applications Engineer - Low Power Audio & Actuators

0 Yinuo Hsiao over 7 years ago in reply to Ivan Salazar

Prodigy 140 points

Dear Ivan,

1. We use Nidec BMR-3135A.
2. Yes. We have set input parameters for auto calibration and we do calibration before diagnostics.

0 Kelly Griffin over 7 years ago in reply to Yinuo Hsiao

TI__Genius 10512 points

Hi Samma,

Can you send your other settings? Are you setting the rated votlage and overdrive voltage correctly?

0 Yinuo Hsiao over 7 years ago in reply to Kelly Griffin

Prodigy 140 points

Hi Kelly,

The setting is provided by TI FAE.

//rated vol = 1.3 v, ov = 1.5 v, risetime unknown
.actuator = {
.device_type = ERM,
.g_effect_bank = LIBRARY_B,
.loop = CLOSE_LOOP,
.rated_vol = 0x3d,
.over_drive_vol = 0x4d,
.drive_time = 0x13;
},

0 Yinuo Hsiao over 7 years ago in reply to Yinuo Hsiao

Prodigy 140 points

We have a device and the status register is 0x6C and sometimes is 0x60 after diagnostics.

Test Steps:
1. Write register 0x01 with 0x06 // diagnostics mode
2. Write register 0x0C with 0x01 // set Go bit
3. Read status register 0x00
4. Repeat step 2 and 3
--> The vibrator works fine, but the status register sometimes shows 0x6C and sometimes shows 0x60.

0 Kelly Griffin over 7 years ago in reply to Yinuo Hsiao

TI__Genius 10512 points

Hi Samma,

If the status is 0x60 or 0x64, then the calibration is passing as you mentioned above.

When you see 0x6C, then something is failing.. Your voltage settings seem to be correct above. Does calibration pass every time?

When you calibrate the device, what is the environment? Some key things are having the ERM attached to a mass to provide a mechanical ground. Also isolate the mass+ERM from the table or any other vibrations. Typically, we use gel pads or foam to isolate the mass+ERM from the table.

0 Kelly Griffin over 7 years ago in reply to Kelly Griffin

TI__Genius 10512 points

Hi Samma,

Any feedback here?

0 Yinuo Hsiao over 7 years ago in reply to Kelly Griffin

Prodigy 140 points

Dear Kelly,

During these days, we did A-B-A tests to verify which parts is faulty.

We found that the error comes from EVM. The following table shows the summary:

The error does not always happen. Sometimes it passed the diagnostics and sometimes failed.

	EVM_1	EVM_2	EVM_3
MASS_1 (with haptic_1)	Error rate 5.4% (9/111)	-	Error rate: 0% (0/117)
MASS_2 (with haptic_2)	-	Error rate 15 % (16/107)	Error rate: 0% (0/183)
MASS_3 (with haptic_3)	Error rate 8% (8/100)	Error rate 11 % (15/138)	Error rate: 0% (0/172)

Thanks for your feedback. I'll double check if the environment affects the test results.

From our EVM vendor, they could not figure out why their device causes diagnostic error. (EVM does vibrate and the electrical signal seems fine, too)

Could you give us some hint about the meaning of "Actuator is timing out" and "giving out–of-range back-EMF"?

0 Zoe Ko over 7 years ago in reply to Yinuo Hsiao

TI__Expert 3810 points

Hi Kelly,

Could you help the questions from Samma?
Also, do you know which haptic part with GUI can do diagnostic test?
Thank you!

0 Kelly Griffin over 7 years ago in reply to Zoe Ko

TI__Genius 10512 points

Hi Samma,

The results are interesting. Is the ERM being mounted on the EVM or on an external mass?
Actuator is timing out: Our closed-loop algorithm is not able to converge on a solution with respect to the closed-loop algorithm.
Actuator BEMF out-of-range: This occurs when the BEMF of the actuator is either 0 or too high for our device. Our device can reduce the gain on the BEMF voltage in order to read it, but if the lowest gain setting is still too high, then this could be the issue.

We have improved the robustness of these algorithms with our new DRV2625 device. This device has more advanced diagnostic features as well. I would recommend it for future projects. It will also use Haptic Control Console, HCC, like DRV2605. We have a user guide online for this software. When you use HCC with DRV2605, you need the USB2ANY communication board as well.

0 Yinuo Hsiao over 7 years ago in reply to Kelly Griffin

Prodigy 140 points

Dear Kelly,

Thanks for your quick reply.

ERM is mounted on an external mass.

Is there any method that we can classify more clearly which error that vibrator falls in?

As for the EVM, do you mean that if we use drv2605_EVM (or drv2626_EVM) + USB2ANY then we can do diagnostic test by sending command from PC (console)?

Best Regards,

Samma

0 Yinuo Hsiao over 7 years ago in reply to Kelly Griffin

Prodigy 140 points

Dear Kelly,

As for our situation, is the actuator is timing-out or BEMF is out-of-range?

0 Kelly Griffin over 7 years ago in reply to Yinuo Hsiao

TI__Genius 10512 points

Hi Samma,

With the DRV2605, there is no way to distinguish the type of failure (timing out or out-of-range).

If you use the DRV2625EVM-CT, then you do not need the USB2ANY board to communicate with the PC. This newer device has more advanced diagnostics and more robust algorithms for tracking the BEMF of the ERM. From your last post, it seems like the EVM was the issue. Are you seeing failures in your end product?

0 Yinuo Hsiao over 7 years ago in reply to Kelly Griffin

Prodigy 140 points

Dear Kelly,

The failure (diagnostic result fail - status register 0x6C) is found in our end product.
According to the test mentioned before, the fail is caused by some faulty vibrator.

Since the vendor of vibrator cannot see the failure by their test method,
I'd like to use DRV2605EVM-CT to setup an environment for them to do the same test like us.

If we use DRV2605EVM-CT and USB2ANY, then we could do diagnostic function and see result via PC?
Thank you.e2e.ti.com/.../2571860

Best Regards,
Samma

0 Kelly Griffin over 7 years ago in reply to Yinuo Hsiao

TI__Genius 10512 points

Hi Samma,

Yes, you can perform diagnostics using those EVMS, your PC, and Haptic Control Console. FYI, there is no additional diagnostic information when using the PC as compared to reading the register value.

0 Kelly Griffin over 7 years ago in reply to Kelly Griffin

TI__Genius 10512 points

Hi Samma,

Please let us know if you have any additional questions. I will close this thread for now.

0 Yinuo Hsiao over 7 years ago in reply to Kelly Griffin

Prodigy 140 points

Hi Kelly,

Thank you. I think the information has been already sufficient for us. :)
This thread can be closed.

Regards,
Samma

Motor drivers

Motor drivers forum

DRV2605: diagnostic fail