motorware 16

Dear Chris,

In my experience, when I was a newcomer of Motorware (before I was familiar to controlSUITE style) I feel confused with the order of lessons in document "InstaSPIN Projects and Labs User's Guide" - Version 1.0.13. I feel that this arrangement is only preparing for the users those who have TI's development kits, and have motors with full of identified parameters... While most of users don't have the condition, they have their own kit and their motor need to be identified before running the amazing and fantastic of Motorware system.

The problem is I must test Motorware functions with my hardware to test my ADC inputs, PWM outputs, SCI interface and so on... as you thought, and I feel that the style of ControlSUITE is easier to do this in every BUILD LEVEL, for example:

 /*------------------------------------------------------------------------------

Following is the list of the Build Level choices.
------------------------------------------------------------------------------*/
#define LEVEL1  1      		// Module check out, duty cycle waveforms and PWM update
#define LEVEL2  2           // Verify ADC, park/clarke, calibrate the offset and run V/f Open-loop.
#define LEVEL3  3           // DCbus compensation, speed measurement test and run V/f Closed-loop with Encoder Feedback
#define LEVEL4  4           // Two current PI regulator and Verify current model for V/f Sensorless Control
#define LEVEL5  5           // Sensored closed-loop FOC

/*------------------------------------------------------------------------------
This line sets the BUILDLEVEL to one of the available choices.
------------------------------------------------------------------------------*/
#define   BUILDLEVEL LEVEL1


#ifndef BUILDLEVEL
#error  Critical: BUILDLEVEL must be defined !!
#endif  // BUILDLEVEL

By developing a project in this way, user can manage and reduce the bugs which always seem to appear after adding more codes into the project. I researched deeply the lab11a, b and c as you suggested but I don't find that it's easy to check hardware and test firmware. I know the motorware is desiged for motor control and focus on FOC algorithm specially. But in my opinion, before users can use the awesome functions in Motorware library, they need to check the operation of every and/or bunch of functions to understand and check their hardware and InstaSPIN's firmware. So that I hope the training documents should be designed for user in general, not only for experts in the field of FOC vector control.

That is only my personal point of view, as an user of Motorware.

Thank you for your listening and discussing,

Mr. Tran

Mr. Tran,

This is valid, and I agree it would be useful for HW bring-up. Having a lab for that has been on our list for a long time.  Being upfront with you, I wouldn't expect to see this happen anytime soon just due to other priorities.

Thanks for the feedback.

Did dual motor control make it into this release?  Is that what was meant by "2 inverter control"?