Hello. I'm Marilyn Rosales. And in this video, I will cover how to run the Universal Project and Lab SysConfig version found within the Motor Control Software Development Kit. This is the third video in the series. If you're unfamiliar with the universal project within the Motor Control SDK or how to run the non-SysConfig version, then please watch the first two videos in the series, which will cover an overview of the universal project itself and how to get started running the project.

The C2000 motor controls SysConfig tool is based on top of the C2000 SysConfig tool in order to be able to utilize all of the design benefits SysConfig has. The integrated support for the universal project makes it easy to select features, and handle device resources and configurations. In order to help explain the features that this project has, you can read through the C2000 Motor Control SysConfig tool application report for a more in-depth review. The project structure for the SysConfig base project is similar to a project you will find within the C2000WARE SDK.

Let's take a closer look at the project in CCS. Similarly to the non-SysConfig version of the project, the SysConfig version can be found within the Motor Control SDK under the solutions folder. Import the project that ends with sysconfig. Once a project has been imported, locate the c2000.cfg file and double-click it to open it. Within the GUI, you will see the Universal Motor Control Lab is already added, along with all of its dependencies.

In the leftmost pane are all of the libraries within the Motor Control SDK, as well as all of the device resources and how much of what is currently being used. In the center pane are the main settings for the lab, such as the build level, DRV board, HAL mode which will be discussed later in this video, and various command interfaces and debug features. Then we have the Motor-specific settings, such as Control Algorithm, Motor Selected and Motor parameters. All of these settings can be changed at any time during your development in order to explore different features that the lab has to offer.

Lastly are the Device Resources. This is a summary of all of the hardware and software resources being used with the current settings selected for the lab. On the rightmost pane, you will see all of the generated files from the lab. If you click on any of the files, you will see the code generated for each of the files based on the configured settings.

Let's go ahead and build a project so SysConfig can generate the files being used. After the build is complete, you can take a look at the project structure. As discussed previously, the project structure is similar to C2000WARE project.

Files generated by SysConfig can be located within the Generated Source files, and the reference files needed are located within the Referenced Source directory. When using the LaunchPad, make sure that the LaunchPad target configuration is set as the active one. If it is not, then right-click on the target configuration file and set it as the active one.

Now that we have gone through a general overview of the project, we can run the lab by simply debugging the project, loading the watch expressions for the build level selected. By default, it is build level 3 [? and ?] starting the motor. Note that details for setting up the motor and running the project can be found in the second video of the series. After running the project, you should see the motor spinning at the speed defined through the Expressions window

Let's go ahead, and I'll stop the motor and exit the debug view in order to go back to the main project. Utilizing SysConfig now provides a way to view the configuration of the different modules within the device, and be able to easily modify them based on your specific application needs. You also have the ability to easily change any of the PinMux settings, which is helpful when working on a custom board design.

Tracking all of the resources is simple due to the view provided in SysConfig. You can see how many peripherals are still free to use for other purposes within your application. Within the GUI itself, the HAL Mode setting allows you to change between Demo Mode and Custom Mode. When Demo Mode is selected, the settings for the required resources are locked. If you want to change any of the settings based on your system needs, then the setting can be changed to Custom Mode, in which you will see the required resources unlocked, and have the ability to change the parameters yourself.

Now let's take a look at the generated files this tool will only generate code that corresponds to settings chosen. Any files that get modified will be signified by an icon change. Opening the file, you will be able to see what specifically changed within the file after changing a setting in the GUI. Files generated by SysConfig can now be altered. If there are files do you wish to modify for your own application needs, then you can always choose to not include the generated file in your project and simply use it as a reference for your own files.

To view the reference files used by the lab you can go to the top right corner and select Referenced Files. A view will appear that will show all of the referenced files. Let's go ahead and add field-weakening control, or FWC for short. Upon adding this feature, you will notice that the FWC library got added to the project automatically, and its required .c file got added to the referenced files. That being said, the tool is able to handle all dependencies needed based on the selected settings.

SysConfig will also generate warnings or errors if any settings are chosen that are not supported by the project, which can be a helpful debug tool. Overall, the integration of the Universal Motor Control Lab with SysConfig makes it easy to identify potentially incorrect setups, manage device resources, reduce code size, and manage project resources with the click of a button. Thank you for watching.