• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 82 subscribers
  • Views 899 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Motorware with DRV8412EVM

ErichG
Prodigy 90 points

Other Parts Discussed in Thread: MOTORWARE, DRV8412, DRV8412DDWEVM, BOOSTXL-DRV8301, CONTROLSUITE

I have low voltage BDC, Stepper and BLDC applications that I'd like to develop common hardware for. I've made good headway with the DRV8412EVM for BDC and steppers--ControlSuite labs and GUI for this module worked through successfully. Now I'd like to add the F28069M control card and begin learning/implementing MotorWare libraries. Are there any fundamental incompatibilities between the DRV8412EVM and Motorware?  

If I'm not mistaken, I'll need to modify the following motorware drivers:

  • PWM to drive 3 pwm inputs to the DRV8412 (vs 6 High/low channels).
  • Current feedback scheme. 

I'm hoping to get some confirmation of this plan. I'll then follow up with detailed questions on how I ought to actually go about these modifications. The Motorware hardware obfuscation ;) layer has confused  preliminary attempts at this.

The DRV8412 is not necessarily my final hardware target. It's just a handy dev environment with the 4 half bridges that I need. 

I trust the HAL will come in handy in the long run.

Thanks, Erich

  • 0
    TI__Guru** 119680 points

    the DRV8412 EVM is quite old...I haven't looked at it in some time, but I'm pretty sure it is missing some of the sensing / filter that we would require for using FAST in InstaSPIN-FOC or -MOTION, specifically on the voltage sensing and filters.

    I would highly recommend using a known good EVM for initial evaluation. Otherwise you're going to be spending all of your time on debug.

     

  • 0 in reply to ChrisClearman
    Prodigy 90 points

    I anticipated your recommendation for learning Motorware. Fact is that I will eventually need a four half-bridge inverter. I prefer to modify a dev module before spinning a custom board. Recommendations?

    To be clear, the DRV8412DDWEVM has no phase voltage or current feedback. 

    The DRV8412EVM (which I am using) has Voltage and Current feedback for each phase. 

    I was unaware of the filter requirement for FAST. Perhaps I missed this. Where should I refer to in documentation? 

    Thanks, Erich

  • 0 in reply to ErichG
    TI__Guru** 119680 points

    please see chapter 5 of SPRUHJ1 for the voltage/current requirements.

    there is not a 4 h-bridge EVM that is ready for use with InstaSPIN. Obviously we try to build 3-ph inverter based hardware....your request is unusual and would have to be customized.

     

  • 0 in reply to ChrisClearman
    Prodigy 90 points

    Thanks, Yes, It appears like the Voltage FB  filter may be all all that I'd need to modify to make this work for me. 

  • 0 in reply to ErichG
    TI__Guru** 119680 points

    I know something else we added since the 8412 EVM design was the kelvin ground connections on current sense and generally better layout of the current measurement. You'll want to at least be aware of this as you move forward....the BOOSTXL-DRV8301 is a nice design of the current sense to use as an example.

     

  • 0 in reply to ChrisClearman
    Prodigy 90 points

    Thanks again.

  • 0 in reply to ChrisClearman
    Prodigy 90 points

    OK. I'm suffering from information overload. I'm capable of working through the ControlSuite examples, but Motorware is wearing me down. I resolve for now to work through the labs rather diving into the hardware abstraction layer but I'll need to dig deeper eventually. 

    When I graduate form the dev kits and labs I'll need to modify the the PWM phase connections and current feedback scheme. I'm having a hard time tracing data flow in Motorware to hardware through the HAL. Is there a (good) reference that explains the resource mapping required of the HAL ? (I've been using the schematics as a final reality check for pin-outs).  Seems like I've seeing this information somewhere but lost it(?)

  • 0 in reply to ErichG
    TI__Guru** 119680 points

    Erich,

    I understand the overload...it's a much different type of solution than a simple controlSUITE example.  There are positives and negatives, but it's certainly more complex.  And I agree it isn't documented well enough for a new user.

    We have some things we are working on this summer in regards to updating the drivers, showing examples of using the other peripherals, and extending the documentation, especially as it relates to the HAL.

    For now, the best thing to do is walk through a proj_lab##.c, (also follow main and ctrl files) and see how the HAL_ calls are used.

    ErichG said:
    (I've been using the schematics as a final reality check for pin-outs).

    Yes, when dealing with the ADC and PWM (or really any I/O) you do need to note where the internal channels are brought out as pins and connect to your inverter.