DRV10987: Hello, i'm trying to configrate drv10987 controller with GUI109xx software

Hello Dogan Birdal,

Let me address your questions below:

2 )  With drv10983 controller i configrate motor parameter and write eeprom then disconnect GUI with controller motor run correctly there not any problem but when i turn off power suplly and turn on again controoler parameters which i wrote eeprom deleted. Can you please let me know how can i write eeprom permanently to save parameters even supply turn off

The steps for programming the EEPROM are in the datasheet. I've copied them below:

However, I see you are using the GUI so I will put these steps in context of the GUI. On the Basic Settings, there is a button called eeWrite which will follow the steps in the datasheet. However, the GUI will not automatically populate the EEPROM Programming Key (enProKey). The user must type in 0xB6 in the space themselves. I've showed the example below.

1 )  i'm trying to configrate drv10987 controller with GUI109xx software when i connect board to PC and open the GUI i get error 

"DRV10983 USB2ANY.lvclass:Read Register.vi<ERR>
Register reading not successful!! Please"

Before we get into troubleshooting, I first want to acknowledge some basic checks to ensure everything is working as expected. Assuming you are using an EVM:

1. When powering the EVM and Device with a VCC > 6.2V and VCC < 28V, is VREG = 5V, and V1P8 = 1.8V?
2. If J2 is configured to use the potentiometer (R2), does the device try to start spinning a motor when it is turned clockwise?
3. Do you connect the USB2ANY after the device is powered up and observe that the yellow light on the USB2ANY is not flashing (i.e. steadily on)?
4. Are the markings or text on the top of IC show DRV10987?
5. When opening the GUI, is the DRV10987 option selected in the drop down?
6. After hitting continue on this error message, are you able to click the Enable Configuration Button and have the button turn green without any error? Can you click the manual refresh button without triggering any errors?
7. Did you close the GUI and start the program in administrative mode to ensure there are no permission errors with the GUI accessing the LabView Runtime program?

Once you have confirmed these steps, we can move onto more

Best,

-Cole

Hey Dogan,

Thanks for taking a look at these steps. I apologize in the delay for answering your first question.

The first thing that seems worrisome is that the VREG = 5V. While the DRV10983 can change VREG from 5V to 3.3V by changing VregSel(0x2A[2]), the DRV10987 has a fixed VREG = 5V. Sometimes, VREG < 5V is indicative of damage for the device and could explain why you are having trouble writing to the device.

Probing the SW pin on the DRV10987, and looking for regular switching activity could help prove if there is damage. Alternatively, trying to power VREG externally with 5.1V and retrying the process could also prove that there is some damage on that pin.

I will agree that changing the DRV10987 out twice and getting the same result is a bit strange, but the damage could still happen. Sending a picture of your test set up might help explain something as well.

I will say, the hardest part users of this part, when it comes to soldering, is getting a solid connection from the power pad to the PCB (usually through the use of melting solder paste). If this power pad is not soldered correctly, strange behavior can occur. Unfortunately, there is no known way to verify if the power pad has been soldered correctly.

The only other thing I want to mention, the DRV10983 has 8 bit registers while the DRV10987 has 16 bit registers, so a file created from DRV10983 subsection of the GUI, cannot be loaded directly to the DRV10987. The GUI should be handling this convention in the background but it is pretty easy to probe the SDA and SCL pins to check.

Best,

-Cole

Hey Dogan,

I'm glad the hardware is now fixed.

Let's get through the new questions:

1 ) When i write to eeprom i get a error "eeprom not ready please try again" you can see image in blow. After click "retry" eeror diappear i think it write to eeprom but don't understand why gives this error every each time

This is normal, when the user clicks the button, the GUI reads the setting the EEPROM write enable bit (0x35[2]), if it is 0b0, the window will flag it and write the bit for you. Clicking retry will check if the bit is enabled (and since it is) the EEPROM write process will begin. If the write was not successful or the bit wasn't set, then the error message would appear again.

As a result, you should interpret the message as "If it doesn't show up after clicking retry then programming was successful."

2 ) there are diferent parameters range and confiduration between "DRV10987 Tuning Guide" and "DRV10987 EVM GUI " interface. Is it depend of diferent version?  in blow you can see the version i use also i can't find any other version for GUI

No, you have the correct version. Previously, we updated the GUI and datasheet with the correct names. Unfortunately, the tuning guide did not get an update. This is why there are some dependencies. As for "range", you'll have to be more specific so we can note them for changes later. Sorry for the inconvenience.

3 )  I configure parameters and try to run motor on GUI or Potentiometer but it's not change motor side. i mean driver doesn't even try spin. Also GUI constantly giving the same "current oveload"  error. By the way the motor is the same which is i spin wtih drv10983 correctly. So i don't think it could be becouse of paramters. 

Unfortunately, I will have to disagree with your analysis. After powering up the device, please click the eeRefresh button to copy EEPROM contents into the register spaces and read if your desire parameters were programmed to the correct registers.

The reason I mention this step to check your settings is because of your second screen shot. I see that the motor resistance is programmed to 0 and I would infer that it is unintentional. 0 resistance means the driver will try to input infinite current in the motor (in reality, it will apply the maximum voltage to get the maximum current, which is VCC). Combine this with a low dead time configuration and its very likely that the device is actually applying a large amount of current and hitting the over current protection (which is about 3A to 4A peak). You could also check this is an oscilloscope.

I am happy you are going through the tuning guide, please continue to do so. I highly suggest you look at this post regarding the motor parameters: 

https://e2e.ti.com/support/motor_drivers/f/38/t/725126

Getting Phase resistance, the BEMF constant, and the Lead Time correct will lead to successful motor start up more than 80% of the time. Following the tuning guide should fix any other issues you face.

Best,

-Cole