CCS/LAUNCHXL-F28069M: Problem running GUI for InstaSpin FOC

Bill,

I will do my best to answer your CCS questions and then will likely have to pull someone in from the C2000 team to help with the rest.

You mentioned that you are using CCSv6.  Which version of CCSv6? 6.0.0, 6.0.1, 6.1.0, 6.1.1, 6.1.2, 6.1.3, 6.2.0.  Did some document specify that you needed to use that version?  The reason I ask is that it is very old.  The current version of CCS is 9.2.0 however since you noted that you are on 32bit Windows I would recommend CCSv8.3.1 as that is the last version to support 32bit.

1. In CCS, clicking on Getting Started brings up a window that says my browser (Firefox) does not support any of the video formats available for YouTube training videos.  I download all the updates to FireFox as soon as they are available, having just done so 2 days ago.  I'm running W7 32 bit.

Newer versions of CCS will use the Chromium browser by default that ships with CCS and this issue would not occur.

2. Opening Resource Explorer shows "Loading..." endlessly.  I thought it might be taking awhile to accumulate the 1000's of folders I installed, but I left it run for over 5 hours with no change.

I am not sure which version of CCSv6 you are running.  If it is pre-6.2 then it is likely what we call Resource Explorer classic which works by scanning folders and attempting to discover resources such as examples, docs... to display.  In CCSv8.3.1 you will see 2 entries on the view menu "Resource Explorer" and "Resource Explorer Classic".  The Resource Explorer tool will show you the current versions of C2000 software such as C2000Ware and the MotorControl SDK.  I am not sure if those newer packages support the kit that you have.  I will have to leave the to the C2000 team.  Resource Explorer classic will allow you to browse through older software packages that you have installed like controlSUITE.

3.  I cannot locate direct matches for the devkit I have or to use to filter selections.  What is the terminology used for the kit I have? 

The filters in Resource Explorer are more related to the MCU devices or LaunchPads.  For the F28069M LaunchPad it is not available as a filter but the F28069M device is.

8.  How do I determine which version USB driver/interface I have?  My USB devices show XDS100, but there are many selections in CCS with that designation.

The LaunchPad you are using has an XDS100v2 on it. http://www.ti.com/tool/LAUNCHXL-F28069M

I will loop in the C2000 team to help with the rest.

Regards,

John

John-

Thanks for the response.  I have v6.2.0.00050 of CCS (2014).  It either was the only download option available for 32 bit or the only one that I could determine was 32 bit compatible.

I noticed that there was a radio button available for "Simple" operation of CCS.  When selected, both menu items for Resource explorer are available and Classic did show a folder view. Still no idea where the files are that I need, what they are named or how to load and compile them in CCS.  The video by Dave Wilson that I referenced had very detailed instructions on how to configure and connect to the devkit as well as find the files to load, compile and download to the lauchpad. 

I'll wait for further instructions from the C2000 team.

Could you please have a look at the GUI Quick Start Guide and the InstaSPIN Labs User's guide in the folder below in motorWare if you have installed the software by default. And let me know if you still have any questions.

GUI Quick Start Guide at C:\ti\motorware\motorware_1_01_00_18\docs\guis\universal

InstaSPIN lab guide at C:\ti\motorware\motorware_1_01_00_18\docs\labs

I downloaded the 2 docs you linked to and I am still poring through them (the combined page count is almost 400 pages).  To be perfectly honest, my enthusiasm for this project is waning.

I hope to have the time to devote to trying the examples in the lab guide in the near future.

I was able to import and compile the 2A lab for the 2806x board;  it compiled without errors, but there were quite a few warnings.  I copied and renamed the .out file into the GUIUniversal webapps folder;  running the GUI, it appears to connect to the target, load the binary and restarts the launchpad, but that is all further I can get.  Under the Application tab, FOC section, I've clicked RsRecalc, Offset Recalc and Force Angle;  I click on enable and Run, but nothing happens.  Identify motor remains Red.  The Readme file says the Identify Motor indicator will turn green even if the motor is not connected (the motor is).

Do you guys have any FAE's in this part of the country, possibly through one of your reps or distributors that could visit my location and get me up and running?  I feel like I'm working with blinders on.

--Bump--

You should follow the instaSPIN lab guide to use the CCS to run or identify the motor directly, the GUI is just for a demo show with TI recommended the motor or the motor parameters are identified already, not for any unknown parameters motor. Let's know if you have any questions about the project using CCS.

Hmmm... I'm following the instructions provided in the 400 pages of documentation you recommended reading from the links you provided.  It gives the option of running the GUI from CSS or stand-alone.  Rereading the instructions for running it inside CSS, it appears to be the same app with the same functions, so I'm not sure what that gets me?  The GUI has a motor ID function to identify the parameters, but it doesn't run.  I can measure them manually or take them from the data sheet and edit the user.h file, but I doubt it will be anywhere near as accurate.

I guess I'll just keep reading and figure it out on my own.  Sorry to have bothered you.  Anybody else have any advice or experience they would like to share?

I don't think you need to read whole documentation since you just run the lab02a as you mentioned, even you only need to read the chapter about lab02a to run the project in CCS, or follow the qsg_gui_universal.pdf to run the GUI. Of course, you have to set up the hardware kit and create the binary file (.out) using CCS before running the GUI. 

Recommend you take a look at the "Updating software for your motor (user.h) " and "Using the GUI" sections in qsg_gui_universal.pdf if you are not using the recommended motor. You need to change some variables in user_j1.h or user_j5.h based on your motor as lab02a section in instaspin_labs.pdf.

Btw, can you run lab02a in CCS as following instaspin_labs.pdf? If no, please make sure that you are using top headers J1-J4 connect to BoosterPack and select J1 definition (#define J1)  in the user.h. If yes, the GUI should work well also if you copy the lab01a.out to the GUI folder and rename it to replace the appProgram.out.