• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 83 subscribers
  • Views 1081 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.

LAUNCHXL-F28069M: Implementing Custom Voltage source inverter (VSI)

Roberto Riccardi
Prodigy 20 points

Part Number: LAUNCHXL-F28069M
Other Parts Discussed in Thread: MOTORWARE, DRV8301, BOOSTXL-DRV8301

Hello, 

I am trying to implement code so that the 28069M launchpad is able to identify our custom VSI. 

The goal:

To run a PMSM with a custom inverter and the 28069M launchpad

The system:

PMSM - Emrax 208, 300Vdc, 80kW motor, with RM44IE encoder

Custom VSI

LEM current sensors (no voltage sensors since we are using an encoder)

Launchpad - 28069M

Done so far:

We have been using the BOOSTXL-DRV8301 to get familiar with CCS and Instaspin. Have successfully completed most of the applicable motorware/instaspin labs (1, 2, 3, 5c, 12a - not getting accurate results because the DRV8301 cannot deliver the power needed which is understood).

We have designed a motherboard which fits on the 28069M and we have associated our necessary pins with those on the launchpad.

I have searched online for topics related to using the 28069M with a custom VSI and have failed to find anything. I have looked through the drv8301.c and .h files and I am at a loss. Any advice on where to start, and/or what to look for would be much appreciated.

Thank you, 

Roberto

  • 0
    TI__Genius 17175 points

    If your custom hardware does not use one of the DRV83xx integrated drivers, you won't need any of the drv8301 source or headers as they're designed to support the SPI connection between the C2000 and the DRV devices. You'll need to create a new user.h that is going to be specific to the custom hardware and add the correct information. Make sure to remove the DRV8301_SPI pre-defined symbol so the project doesn't try to call HAL_writeDrvData(). You could take a look at the projects for the HVKIT to get an idea of what your project will resemble, as this kit features discrete drivers instead of integrated drivers.

    Once you're able to compile the project without the DRV source and headers, you should be running proj_lab01b and proj_lab01c to verify the signal chain and feedback circuitry for your HW. It's going to be critical to ensure you have correct feedback in order for InstaSPIN to work properly. Update the user.h (and user_j1.h if using the boosterpack structure) accordingly, paying special attention to the "CURRENTS AND VOLTAGES" section as well as the USER_VOLTAGE_FILTER_POLE_Hz value

    You shouldn't need to mess with the HAL if you've designed a pin-for-pin compatible VSI that fits on the Launchpad. I may be forgetting a few steps here but this should get you started

    Sean

  • 0 in reply to Sean Bigley
    Prodigy 20 points

    Hello Sean, 

    Sorry for the late reply. I was in exam period.

    Thank you for the advice, it has helped me a lot.

    Quick question. We currently do not have voltage sensors included in our setup. Would I be able to use InstaSpin without them (Current sensors + encoder)?

    Thanks again, 

    Roberto

  • 0 in reply to Roberto Riccardi
    TI__Guru** 116920 points
    Both InstaSPIN-FOC and instaSPIN-Motion lab projects in motorware can't support the inverter without 3-phase voltages sensor. You have to change control algorithm and flow if you only want to use spinTAC in instaSPIN-Motion based on the inverter w/o 3-phase voltages sensor.