MotorWare v16 released

ChrisClearman

Guru** 119600 points

Other Parts Discussed in Thread: MOTORWARE, BOOSTXL-DRV8305EVM, LAUNCHXL-F28069M, DRV8301-69M-KIT, CONTROLSUITE, DRV8305, BOOSTXL-DRV8301, LVSERVOMTR, TMS320F28075

MotorWare 1_01_00_16 is now available

Support for BOOSTXL-DRV8305EVM extended to LAUNCHXL-F28069M
New Projects: Control of 2 motors from a single LAUNCHXL-F28069M
- InstaSPIN-FOC: Sensorless velocity control (proj_lab11d)
- InstaSPIN-MOTION: Sensorless velocity (lab06e), Encoder Velocity (lab12c), Encoder Position (lab13f)
New Project: Hall sensor start-up with user selectable transition to FAST Sensorless
- InstaSPIN-FOC: Hall Start-up (proj_lab11e) demonstrated on DRV8301-69M-KIT
Updated SpinTAC libraries to increase supported number of pole pairs
Fixed InstaSPIN Project & Lab User’s Guide for truncated InstaSPIN-MOTION labs
Fixed \sw\ide\ccs\cmd\f2806x\F28062F.cmd
Updated default user.h #define USER_MAX_VS_MAG_PU (0.5)
New Tutorial on using drivers and code examples from controlSUITE

over 9 years ago

ChrisClearman over 9 years ago

TI__Guru** 119600 points

Good news: New projects
Bad news: There are not lab write-ups for the new projects yet. You should be able to follow the code though, especially for the 2 motor projects.

One thing we did miss is minor.
Many of the proj_lab##.js files were not updated to include support for the DRV8305 SPI Variables.
If working with the BOOSTXL-DRV8305EVM you can simply edit the .js to add:
expAdd ("gDrvSpi8305Vars");

Or use the INSTAPINSUNIVERSALGUI which has a tab for all DRV8305 Variables

Tran Binh Duong over 9 years ago

Expert 2550 points

That's an amazing news!

Thank you for the alert!

Harvey Wang over 9 years ago

Intellectual 340 points

Hi Chris,
Glad to hear the new release being in place. Does the proj_lab11e support hall start-up in both directions(CW and CCW)?

ChrisClearman over 9 years ago in reply to Harvey Wang

TI__Guru** 119600 points

the HALLBLDC module supports both

typedef enum
{
BLDC_CW = 0, //!< ClockWise
BLDC_CCW = 1 //!< CounterClockWise
} BLDC_DIR_e;

and the default for proj_lab11e is

BLDC_DIR_e gDirection = BLDC_CCW;

Andrew Buckin over 9 years ago in reply to ChrisClearman

Expert 2130 points

SPI library has not changed.!!!

ChrisClearman over 9 years ago in reply to Andrew Buckin

TI__Guru** 119600 points

correct, and it will not.

please use

docs\tutorials\controlsuite_examples_drivers_tutorial.pdf

to pull in the controlSUITE examples for SPI

Andrew Buckin over 9 years ago in reply to ChrisClearman

Expert 2130 points

change the mode of SPI is possible only once. a very interesting approach to the quality of the code. How many of these features is in the MotorWare?

chao yang over 9 years ago

Expert 1620 points

Hello Chris

I have some questions about motorware 16.

1.In new lab11e,on line 857,there is a bool type variable "gFlag120" which is defined as false all the time, I may be unclear about it.What does it mean?

2.About dual motor sensorless velocity control,I found two interrupts( interrupt void motor1_ISR(void) and interrupt void motor2_ISR(void) ) in lab11d.c,I think it is strict to the time slots.So I wonder software execution clock tree of dual motor control system.

3.I want to try the lab about high frequency Injection.But I cannot buy a qualified saliency PMSM in my country.Can you recommend me an appropriate motor ?

4.If run dual motor control,I must buy two BOOSTXL-DRV8301 and one LAUNCHXL-F28069M.Is that correct?

chao

ChrisClearman over 9 years ago in reply to Andrew Buckin

TI__Guru** 119600 points

sorry Andrew, I don't follow the question

ChrisClearman over 9 years ago in reply to chao yang

TI__Guru** 119600 points

1. I believe this is spurious code that was in the proj_lab##.c during development but isn't required. The state switching functionality was pulled out into HALLBLDC module. To be honest, I just tried this lab after launch and I have some additional concerns. We are looking at improving it for the next release.

2. each motor has it's own interrupt, which starts with its own PWM SOC and ends from an ADC EOC flag, which is independent for each. What is required is that you offset the PWM frequencies so that you aren't overlapping the sampling window for the two motors. See HAL_setupAdcs

3. The one used in the lab is Anaheim Automation BLY341S-24V-3000
In my personal experience it is very challenging to get this to work with most motors, even if they claim high saliency.

4. The example uses one LAUNCHXL-F28069M and two of either BOOSTXL-DRV8301 or BOOSTXL-DRV8305
For the MOTION examples it uses the Teknic LVSERVOMTR

Andrew Buckin over 9 years ago in reply to ChrisClearman

Expert 2130 points

Try to Change SPI MODE and see the result on the oscilloscope.
void SPI_setMode(SPI_Handle spiHandle,const SPI_Mode_e mode)

Ronnie Kroekenstoel over 9 years ago in reply to ChrisClearman

Prodigy 60 points

Hello Chris,

I'm looking into proj_lab11e now, and some things are unclear to me. Now I read you have some concerns about this lab. Is there already an improved version of this lab or is there more information about the concerns?

ChrisClearman over 9 years ago in reply to Ronnie Kroekenstoel

TI__Guru** 119600 points

The new lab has not been created or released. We are planning it for MotorWare v17. Unfortunately there will be significant changes so I would suggest to hold off on this version if possible...

Ronnie Kroekenstoel over 9 years ago in reply to ChrisClearman

Prodigy 60 points

Is there a planned release date for version 17?

ChrisClearman over 9 years ago in reply to Ronnie Kroekenstoel

TI__Guru** 119600 points

no hard date set yet. My guess is Q3.

Oleksandr Kozaruk78 over 9 years ago in reply to ChrisClearman

Prodigy 30 points

Andrew is referring to e2e.ti.com/.../455235
It was said that the bug is confirmed and will be fixed in the next release. New release is here, and the bug as well.
The same bug is in SPI_setMode.

Recently I had to port gpio lib for tms320f28075, since it was not supported in version 16. Here are some of the findings:

uint16_t GPIO_getPortData(GPIO_Handle gpioHandle, const GPIO_Port_e gpioPort)

The port is 32 bit wide, and the function returns 16 bit value

void GPIO_setPortData(GPIO_Handle gpioHandle, const GPIO_Port_e gpioPort, const uint16_t data)

Again, input parameter 'data' is 16 bit, though a port has 32 bits.

GPIO_getData and GPIO_read duplicate each other, do the same thing.

For f280x gpio.h GPIO_Number_e enum has GPIO_numGpios. It is not a total number of GPIO, as one might think, since there is a gap between gpio 44 and 50

And some questions, just out of curiosity:
I wonder, why all gpio functions require a handle. Are there MCUs in C2000 family that have more than 2 gpio controllers?
What's the meaning of GPIO_init ?

Sasha.

Gary H over 9 years ago in reply to ChrisClearman

Expert 1855 points

Any update on the next release of Motorware? Getting ready to start a new motor control project and thought I would check.

ChrisClearman over 9 years ago in reply to Gary H

TI__Guru** 119600 points

it is most likely October. Not before.

Charlie Allan over 9 years ago in reply to chao yang

Intellectual 960 points

Regarding your question 3 about motors with enough saliency for high frequency injection, any hard drive motor should do. At least Seagate and WD use sensorless algorithms and start unidirectionally using the saliency to detect position using high frequency injection.

Stephen McFadyen over 9 years ago in reply to ChrisClearman

Prodigy 160 points

Hi Chris,

Do you have a preview version of Lab11e in Motorware? It seems to be incomplete and not working, and is apparently going to be fixed in motorware v17.

You mentioned October, is that prediction still holding? If so, when do you think it'll be available?

thanks! -

ChrisClearman over 9 years ago in reply to Stephen McFadyen

TI__Guru** 119600 points

I do not have a preview version I can share.

lab11e has been rewritten

we are doing final testing of v17 now and I hope to release before end of month.

Stephen McFadyen over 9 years ago in reply to ChrisClearman

Prodigy 160 points

Thanks very much, I'll be looking forward to it. I did get it to work with some modifications, but I would like to see if there's a nicer solution. Has TI given up on providing a decent HFI example with speed control? Seems like marketing material on the subject, an example using torque control, and a disclaimer saying that it's inherently tricky and it's just there for reference material.

ChrisClearman over 9 years ago in reply to Stephen McFadyen

TI__Guru** 119600 points

we have stopped developing the HFI solutions further. it is not something that works across different motors easily so it's not a broad "insta" solution. It will work with very salient motors but under high load the saliency lessens and then the technique is no longer effective. Very challenging problem that would be quite impressive to fully solve.

Chek Castillo over 9 years ago in reply to ChrisClearman

Prodigy 70 points

Any news regarding the release date of Motorware 17?

ChrisClearman over 9 years ago in reply to Chek Castillo

TI__Guru** 119600 points

Should be on the web by Friday.

Be sure to sign up for the ALERT ME feature on the MotorWare tool folder to get an update when it is available for download

ChrisClearman over 9 years ago in reply to ChrisClearman

TI__Guru** 119600 points

Update, looks like we are trying to fit in a couple more things so we will release on Monday 10/30.
It may not replicate to the web in your region until 11/1-11/2. We will post when available.

ChrisClearman over 8 years ago in reply to ChrisClearman

TI__Guru** 119600 points

sorry for the delay. we decided to patch this reported issue
e2e.ti.com/.../2014744

so the release should go out Friday/Monday.

C2000™︎ microcontrollers

C2000 microcontrollers forum

MotorWare v16 released