MotorWare v18 Released

Motorware v18 has officially been released. Find some of the changes enumerated below:

  • HAL_setTrigger() change to fix issue where when USER_NUM_PWM_TICKS_PER_ISR_TICK was set to 2 or 3, and ISR execution time was less than half of ISR period, ADC trigger would sometimes be missed
  • Fixed issue in GPIO_setPortData() for F2805x that had incorrect parameter data width
  • Fixed usDelay() issues in all hal.c files, replaced with US_TO_CNT() macro
  • Fixed CMP saturation limit in HAL_WritePwmData() in hal.h for F2805x only, changed lower limit from _IQ(0.0) to 1
  • Update PWM_setSocAPulseSrc() in all pwm.c
  • Remove OVM functions in lab5h and remove svgen_current.c file in project
  • Fixed compiler error in hal.h for 06x projects with HVKit due to an error in #ifdef statement for HALL GPIO pin numbers
  • Fixed LED blinking timing error in main_ISR() for all FOC and MOTION files that have toggle led code (New Enhancement)
  • Changed the argument of CPU_USAGE_setParams() to variable instead of fixed timer period since timer period was changed in hal.c in MW17. Affects labs: 03b, 07, 11a, and 11b (these labs use the legacy CPU_USAGE module)
  • Changed the argument of FEM_setParams() to variable instead of fixed timer period since timer period was changed in hal.c in MW17. Affects labs: 03b, 07
  • Changed motor definition to resolve compiler error when using IPD projects in the below user.h files:
    • \boostxldrv8305_revA\28x\f2806xF\src\user_j1.h
    • \boostxldrv8305_revA\28x\f2806xF\src\user_j5.h

  • All functions running in main_ISR() in lab11x were added to “ramfunc” for reducing cycle time (New Enhancement)
  • Added lab07 and lab09 project for BoostXL-DRV8305 + F2806x  "boostxldrv8305_revA\f28x\f2806xF\projects\ccs"
  • Added Volt/Hertz module in modules/vs_freq/src directory. This module generates an output command voltage for a specific input command frequency according to the specified volts/hertz profile.
  • Added Angle Generator module in modules/angle_gen/src directory. This module generates angle output for a specific input command frequency.
  • Added proj_01b project for all kits and controllers.
  • Added proj_01c project for all kits and controllers.
  • Added gMotorVars[HAL_MTR2].CtrlVersion = version; to lab10d for bug fix
  • Relocated CLK_disableTbClockSync() to before timebase, compare control, action qualifier, dead band and trip zone initialization loops. This was done to fix issue where PWM sync could sometimes be lost when hard-resetting MCU
  • Changed RsRecalc functionality to have initial value of USER_MOTOR_Rs instead of 0, which will allow quicker settling time
  • Offsets removed from user_2motors.h to avoid issue where current/voltage offsets were defined in two separate header files
  • Added definition for updateRsOnLine() for lab11a, takes EST_Handle parameter instead of CTRL_Handle parameter as expected by runRsOnLine() in lab07
  • Added spi.c and drv8301.c source files to all F2802xF LaunchPad projects that were designed for DRV8301 BoosterPack

Sean

Did a reply answer your question? If yes, please click the "Verify Answer" button located at the bottom of that post.
Visit these helpful C2000 Links!

C2000 TI Wiki Pages
TI Forum Sitemap
ControlSUITE
C2000 Getting Started
CLA FAQs
Workshop Material!

32 Replies

  • Thanks Sean!

    Did a reply answer your question? If yes, please click the "Verify Answer" button located at the bottom of that post.
    Visit these helpful C2000 Links!

    C2000 TI Wiki Pages
    TI Forum Sitemap

    ControlSUITE
    C2000 Getting Started

    CLA FAQs
    Workshop Material!

  • Why is motorware released as an exe ?
    I find it most user unfriendly on a linux machine. I think the FAST observer is a great piece of work, but 'code composer studio' and motorware are just 'bloatware'
    I spend longer navigating through the maze than in writing new current or speed control loop. It's very frustrating.
    TI is killing it's wonderful FAST estimator thanks to the bloatware called 'motorware' and even bigger bloatware called 'controlsuite'
  • In reply to srinath mallikarjunan:

    Agree.

    It is better for TI to release libraries in zip format. I use Mac and the exe file format is really inconvenient.

    Robert Chen
    simple is beautiful.

  • Hello,

    I am wondering whether there is something wrong with the appearance of MotorWare.exe for Motorware 18, or this is only happened in my computer (since nobody reported it). I use Windows 8.1 pro for my PC.

     It does not disturb the work anyway, only I can't browse the documents from the Motoware application.

    Thank you!

    Best regards,

    Maria

  • In reply to Maria Todorova:

    Hi Maria,

    I have not seen the issue that you have shown in your picture above. I will try to find a laptop running Windows 8.1 pro at our office and see if I can replicate the problem.

    Sean

    Did a reply answer your question? If yes, please click the "Verify Answer" button located at the bottom of that post.
    Visit these helpful C2000 Links!

    C2000 TI Wiki Pages
    TI Forum Sitemap
    ControlSUITE
    C2000 Getting Started
    CLA FAQs
    Workshop Material!
  • In reply to Sean Bigley:

    Robert and Srinath,

    Mac and Linux installers are not currently supported by Motorware releases; we do not make any claims about their efficacy or fix bugs for these platforms at this time.

    Sean

    Did a reply answer your question? If yes, please click the "Verify Answer" button located at the bottom of that post.
    Visit these helpful C2000 Links!

    C2000 TI Wiki Pages
    TI Forum Sitemap
    ControlSUITE
    C2000 Getting Started
    CLA FAQs
    Workshop Material!
  • In reply to Sean Bigley:

    I agree with Robert and Srinath. There's a lot of great things about the InstaSpin system, but the documentation is convoluted. I spent 3 days just trying to figure out the right pdf to read, then I found the instaspin_labs guide which has all the information needed to get started. Lots of the included documentation is years out of date and conflicts with the new documentation.

    The motorware package seems unnecessary. It's just a browser showing you the file system that it installed on your computer. Even if you only officially support Windows, a zip file would still be easier.

    The GUI is fully useless. You can't use the GUI without compiling the code, at which point you might as well just use the user interface in CCS, which is what the labs are written for anyways. All the advertisement about an "easy to use GUI" made me think the system would be very different than it was. The GUI should just be removed, since it makes it massively more complicated, not easier.

    Controlsuite is not necessary for using InstaSpin, and takes up ~6GB of disk space, so I'm not sure why some documents recommend that you install it. I know that the hardware info for the boards is in Controlsuite, but you can also download that for your specific board from the board page on the TI site.

    All of these issues don't inspire confidence in using the system in a product...
  • In reply to Kyle Bartholomew:

    Whoever is in charge of marketing for TI has got it completely wrong.

    There are some great products in the ROM like FAST, system identification etc...,and all that's needed is API documentation, code and a miniaturised lab guide (Why should the lab guide go into minute CCS details like press this button in top right corner, press that button here etc...?)

    It took me 1 day to write a new current/torque controller using the FAST observer, but it took me 2 weeks to wade through the bloatware called motorware and the 300 page labguide (that could be shrunk to 30 pages), making me wonder if it's really worth the trouble. After all other companies like ST, NXP also offer their own observer's on ROM.

    Coming to "controlSuite", less said the better. Why do i need schematics for every Dev board TI has made since it's inception ? And again, provided as an exe!!

    I think motorware should be renamed bloatware & controlSuite should be renamed as junkSuite.

    You guys are killing a great combination of products called instaSpin with really bad documentation and piling on layer upon layer of irrelevant junk on a customer.

  • In reply to srinath mallikarjunan:

    Thanks for the feedback.

    I'll try to give you some reasoning...but we know that the overall experience could be improved.

    Why deliver as an .exe?

    - this is just common SW distribution practice. At one point we distributed the .exe in a .zip, but some systems don't like that.

    Why MotorWare.exe?

    - most people have a positive experience with the .exe since it easily lets them browse the contents of the installation. Without it you wouldn't find all available resources (especially when some of the resources are only on-line, some are in controlSUITE, etc.).  In fact, the complaint about not finding InstaSPIN_labs.pdf wouldn't have occurred if you started with MotorWare.exe and browsed the resources.

    Why controlSUITE also?

    - Two reasons. The first is that customers want the HW files for the EVMS, but we didn't want to duplicate them in MotorWare (and have it reach 6GB as well) so we pointed people to controlSUITE.  There has been a transition at TI to putting HW files into their own download though and trying to keep SW distribution products like controlSUITE smaller.  You'll see this as we transition to C2000Ware and C2000Ware + Software Development Kit (SDK) type of process.

    - Second, MotorWare was originally planned to be completely self enclosed, with all necessary software drivers included. Unfortunately this didn't happen for a variety of reasons so we fell back on pointing people to controlSUTIE examples for integrating the software outside of the main motor control system. It isn't a very elegant solution.

    - MotorWare v18 is planned to the be the last release for F2806x/5x/2x enabled InstaSPIN devices.  For new InstaSPIN devices we are moving to C2000Ware for the baseline software infrastructure and then Application SDK (which include a version of C2000Ware) which shows the full application.  So there will be a MotorWare SDK for these next gen InstaSPIN devices. 

    Regarding general comments about just having FAST and a 30pg API guide, etc:

    - I would say you are in the minority on this one and likely have significant motor control expertise. We welcome users like you but understand that MotorWare/InstaSPIN was not initially designed for high expertise customers. We released the proj_lab11 examples to try to fill this gap (in-line code which is more easily adaptable to custom control and just FAST as an estimator) but we did not simplify the rest of the documentation.  In the next version of InstaSPIN the library interface, labs and user's guide will be simplified.

    Regarding the GUI:

    - Your description fits the INSTASPINUNIVERSALGUI accurately, but I still find it much easier to use than the CCS Expressions described in the Lab Guide.  However, for the initial 3 EVMs (HVKIT, DRV8312, DRV8301-69M) there is also a demonstration GUI which is quite extensive to show off the capabilities of InstaSPIN-FOC and -MOTION: motorkitscncd69miso

    Thanks

  • In reply to ChrisClearman:

    Srinath, Kyle, and Robert,

    The TI C2000 development team follows the forum and appreciates your feedback.  Thank you for taking the time.   As Chris mentions, we know there are a number of things we could do better and are making progress.  

    I wanted to add to Chris’ comments regarding bloat and installer issues.  In January we introduced C2000Ware.  This package will be our platform moving forward for foundation/lowest level software.   These are libraries that would be common across application areas.

    • C2000Ware contains only the latest version of each sub-component in order to greatly reduce size of the download.  
      • Older versions of C2000Ware will also be available for download if needed.  
    • C2000ware also has native installers for windows, linux, mac and the TI cloud tools.  
    • By using the TI cloud resource explorer you can browse through the contents without having to download the whole install.  
    • As Chris mentioned, we will be moving application level software to an SDK format built on C2000Ware.  
      • The idea here is again to reduce the download size and duplication of software and to provide a common base (C2000Ware) for all of our software.
      • Different application areas will be released into different SDKs.  

    Our goal is to make all of our software look similar with an easy out-of-the-box experience.  Unfortunately it will take us some time.  Please continue to send constructive feedback.  I’ve noted additional items you have mentioned in this thread already.  

    Regards

    Lori

    Did a reply answer your question? If yes, please click the "yes" button located at the bottom of that post.
    Visit these helpful C2000 Links!
    C2000 TI Wiki Pages
    TI Forum Sitemap
    ControlSUITE
    C2000 Getting Started
    CLA FAQs
    Workshop Material!