Forums

This is a sensorless SINE technique.

If you want to use a sensor, hall effect BLDC or encoder FOC (way too expensive for an e-bike) should be used. Both of these are demonstrated on various kits (DRV8312-C2-KIT, DRV8301-HC-C2-KIT)

Dear Chris,

I cannot find demonstration code of hall effect BLDC or encoder FOC in ControlSuite. C:\TI\controlSUITE\development_kits\DRV830x-HC-C2-KIT_v103

There are only demonstrate for senserless. Could you please advise where is the location of  demonstration code of both "hall effect BLDC or encoder FOC" ?

Thank you.

sensored BLDC is shown with the DRV8312 kit

C:\ti\controlSUITE\development_kits\DRV8312-C2-KIT_v127\BLDC_Sensorless

Hi Chris,

Regarding the SINE technique which you mention before , Do you have more information now ? Can you share to us ? Thank you.

Sutthinee,

Yes, I'm evaluating it now and we are doing some thorough dyno analysis.  I'm pleased with the results so far.  You have DRV8301 and F28035, correct?  Send me a message with your email and we can discuss.

It probably won't be released public until late summer.

Hi Chris,

We are using DRV8301 and F28030. 

My e-mail : nees@ccspgroup.com

Thank you.

Dear Chris,

Did you email me for the SINE technique? I didn't receive your mail for the SINE technique yet.  Could you please share to me ? Thank you.

I understand that the drv8301 developemtent kit for InstaSpin comes with SPI capabilities but I am curious if we lose any functinality that the drv8302 has by adding SPI or if this is just an additional perk the drv8301 has over drv8302?

there are more gain settings available by using the DRV8301.

Also, from the SW side we are basing more of the projects that are upcoming for the DRV830x kits on the DRV8301, just to choose one.

BUT - because of our own SPI limitation we will be using DRV8302 on a new 2MTR kit and a LaunchPad in the fall.

So we like them both :)

I am using a DRV8301 board and running the PM_Sensorless project.  I am able to run my Build 5 great which is the closed Current loop with speed estimation and have tuned my PIDs for my application.  When moving to Build level 6, my PID values for the current controlled loop do not seem to be correct anymore when lsw = 1.  The motor will not spin with the level 5 current PIDs. It seems to me that that going from 5 to 6 should not effect my current loop at all.  Any thoughts?

I have the same problem which is when ever I set the Enable_Flag to 1, the fault LED lights up.  I looked at the DRV8301)stat_reg1.all and the 9 and 10 bit are set to one which represents GVDD_UV and FAULT are active.  The board was working fine while I running at level 7 of  the PM_sensorless project.  I was running in current mode and switching to speed mode and all of a sudden the board quit working and the fault led lit up.  I have the same problem on another one of my drv8301 and I was wondering what I can do to fix the problem.

now it faults on everything? Even after full power cycle and using a known good program (like InstaSPIN-BLDC GUI?)

if so, it sounds like HW damage (short).

Yesterday was the first time that I used this board and it already broke.  I doesn't seem right that the board will short at $300 a piece when I followed the directions from level 1 to level 7 step by step.  Is there anything you can do.  This is my third board already.

please try the board with a known working project, and if you can a known working motor.

the board is very robust and should not be damaged.

if the DRV device is tripping it's usually one of two things

- Torque command making a step response: try de-tuning your Speed controller (very low Kp, no Ki) and making your ramp slope shallower 

- If your motor is low inductance it could have some very nasty start-up current spikes. you will need a much higher PWM frequency

I tried running the GUI program originally programmed in flash and got the same results (the fault trips).  I know you said that this fault is usually because of two reason but I had the motor spinning successfully on each of my three boards.  Here's what happen when each of the board broke..

1.)     I was running step 7 and the motor was running fine in current mode, but when I switched to speed mode, the motor stopped and the board fault (which I think is a short).  i went all the way from step 1 to step 7 on this board and used it for over a week.  I was able to switch the board from current control to speed control successfully on this board and I was tuning the PIDs.  The difference between when I switched from current control to speed control the time I broke the board is that I switched while the board was ramping up (at low speeds) and I switched the the speed control.  I didn't think this would short anything because I was pulling such low power.

2.)    The second board broke the same way with the same fault (GVDD_UV) the first day.

Both were at low speeds (600 RPM) and low power (1-2 Amps DC) at 57v (too high?).  I should mention that I am using a 3 peak H.P. motor although I never got close to this power.  I changed my switching frequency to 16 kHz because thats what we use today and the inductance is .000206 H.  Can you think of anything I did wrong and hopefully help fix my boards?