Other Parts Discussed in Thread: DRV10987, , USB2ANY, DRV10983
Hi,
May I know where can download DRV10987 EVM GUI parameter file?
Thanks.
Regards,
Eric
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi,
May I know where can download DRV10987 EVM GUI parameter file?
Thanks.
Regards,
Eric
Hey Eric,
Please refer to the DRV10987EVM User's Guide: http://www.tij.co.jp/jp/lit/ug/slou476/slou476.pdf
Specifically, max sure the DRV10987 is powered to the appropriate VCC and there is a voltage on the speed pin (by turning the potentiometer clockwise if you have the EVM). Make sure the USB2ANY is correctly connected to the device and open the DRV109xx Software (download is on the Tools and Software tab of the DRV10987 product folder) and select the DRV10987. Usually, the error you see is because the USB2ANY is not connect to the device correctly or the device is asleep since there's no voltage on the speed pin.
Section 5: Out of the Box Quick Start Guide in the user's guide has more information.
Best,
-Cole
Hi Cole,
Thanks your information.
Would you kindly help to check if cna use "Runtian_ZWL12_22_2p5A.csv" to DRV1987 EVM?
BTW, we use WIN10 OS and still got the same error message and will find other OS to check again.
Thanks.
Regards,
Eric
Hey Eric,
TI has stopped providing the Runtian configure .csv file, please refer to this E2E post for more details including how to get the motor spinning. In summary, we used to offer a motor with the EVM. However, TI no longer offers the motor in the EVM which removes the need for the file.
Please refer to the user's guide as mentioned before to get the EVM operational and then refer to the DRV10987 Tuning Guide to tune the motor.
Does this error occur every time you start up the EVM GUI? Or are you able to get the the Enable Configure button on the GUI to turn green and then you get the error some time (i.e. seconds) later?
Note that the GUI and LabView 2014 run time engine is compatible with Windows 10 and should not contribute to the error.
Best,
-Cole
Hi Ulf:
No, this should need to install "LVRTE2014f2std.exe" file from http://www.ni.com/download/labview-run-time-engine-2014/4887/en/
Hi Eric,
I had installed the "LVRTE2014f2std.exe" and also I rebooted the PC before using the GUI.
I have looked with my scope on the I²C clock and data line everything seem to be normal.
Regards,
Ulf
Hey Eric,
I was successfully able to set up all of the DRV10987EVMs that I ordered to make sure there wasn't a problem with our stocked kits and our procedure for testing them.
At this point, it seems that either the DRV10987 is damaged or the USB2ANY. By probing the voltages on VREG, 1P8V, and 3P3V, we will be able to tell if the DRV10987 is damaged. If the DRV10987 is not damaged then we can move on to the USB2ANY.
Let me know if you need anything else.
Best,
-Cole
Hi Cole,
I have also trouble with a DRV10987EVM. I use WIN10 64bit.
At My DRV10987EVM board I can measure VREG = 5.07V, 1P8V = 1.796V, 3P3V = 3.272V.
If I use the USB2ANY Explorer the I²C Bus seem to be normal:
Start DRV10987EVM Application on PC:
Errormessage after click on OK:
Message before click on eeWrite:
Errormessage after click on eeWrite:
Signals on the I²C Bus after click on eeWrite:
The DRV10987EVM was shipped from Mouser at 11.Jan 2018 and arrived on 15.Jan 2018.
The DRV10987 delivers the normal voltages, but I can not change any values to optimise the controller for a motor and it make no reaction on a change on the Poti and also no reaction if I use a PWM signal.
I hope you can help me to identify the problem.
Best Regards,
Ulf
Hi Cole,
I measure VREG/ 1P8V/ 3P3V as below for your check again.
VREG: 5V
1P8V: 1.79V
3P3V: 3.28V
So do I need to update USB2ANY FW?
BTW if you load "Runtian_ZWL12_22_2p5A.csv" file through DRV10987 GUI and restart GUI again then you should find the error message.
Thanks.
Regards,
Eric
Hey Ulf,
Thanks for giving all of the information with screenshots. I will say, your issues are separate from the errors that Eric is recieving. Please make your own thread so I can accurately track and answer your questions.
For now, I encourage you to reinstall the DRV109xx GUI software, ensure the 2014 LabView run time engine is correctly installed, and follow the steps in the Out-of-the-Box Quick Start Guide in the DRV10987EVM User's Guide. Specifically, steps 10-12 should help you start using the GUI.
Best,
-Cole
Hey Eric,
Yeah those look like the expected voltages, so far, no evidence showing the DRV10987EVM or device was damaged.
For the firmware, I believe we already ruled that out for being a potentional problem if you already checked out the USB2ANY Firmware Explorer and got 2.7.0.0 (like Ulf in the above comment).
Alright, please confirm that this is the steps you take in your setup:
Thank you,
-Cole
Hi Cole:
Update information as below for your reference.
Thanks.
Thanks.
Regards,
Eric
Hey Eric,
Thanks again for sticking it out for this long.
I will double check on a WIN10 system for you but for now, I have one more step that I'd like to confirm:
In between step 4 and step 5 in the previous post, can you successfully click the enable configure button and have it turn green with no errors?
Also, the file you gave me is a file specifically made for the DRV10983. The registers between the DRV10983 and DRV10987 are different and the header says DRV10983 instead of DRV10987. Unfortunately, this file will not work for you. I've attached a similar DRV10987 file that should help you evaluate the steps.
DRV109837EVM_Runtian_1-23-18 - Copy.123
Thanks,
-Cole
Hi Cole:
Thanks your information and I re-install DRV10987 GUI Tool again then can workable on another WIN10 NB.
But I still another question about EEPROM eeWrite function.
Would you kinldy provide your suggestion about how can download our current setup to DRV10987 EEPROM?
Thanks.
Regards,
Eric
Hey Eric,
If I'm understanding correctly, then it sounds like you've got everything working now. That is great news.
As for EEPROM eeWrite function, let me describe about how our device implements EEPROM: EEPROM is non-volatile memory (as I'm sure you know, which means that the contents are stored and held after cycling power). On powerup, our device takes the settings in EEPROM and then copies them to what are called "shadow registers" on our device, which is volatile memory (which will be reset everytime power is cycled).
When a drop down menu setting (e.g. Rhase Resistance or Kt) is changed in our GUI, the GUI actually writes to the volatile memory space (i.e. shadow registers) to change our device behavior. If we want to store these settings in non-voilatile memory we need to use the eeWrite button to transfer the settings from our to the EEPROM.
So, the device should be powered up to the operation voltage range (we tend to use VCC=22V). Then, the settings we'd like to store in EEPROM should be manually selected or loaded into the GUI (i.e. using DRV10987EVM_Runtian_1-23-18-Copy.csv file you now have). Finally, the eeWrite button should be used to write the settings into EEPROM. You may get a message that says EEPROM Not Ready! but if you click okay and then message doesn't appear again, then your settings should be written into EEPROM. You can check this by simply turning the device on then off and resetting the GUI to see if the settings you chose are now populated after clicking the Enable Configure button and clicking Manually Refresh.
Hope this answers your question,
-Cole