topic Re: MBD Toolbox - Tip of the Day in Model-Based Design Toolbox (MBDT)

MBD Toolbox - Tip of the Day

Daniel_Popa — Tue, 25 Apr 2017 08:38:45 GMT

This topic is intended to offer tips and tricks about using Model-Based Design Toolbox, Matlab Simulink and/or any other tools used for loading and debugging the applications created with MBD Toolboxes.

If you have a piece of advice that you want to share with others this is the place to add it.

Comment below and help others to become proficient with NXP's MBD Toolboxes

Summary:

Tip #1: How to use Block Priorities

Tip #2: How to use Model Workspace vs Matlab Workspace

Tip #3: How to add custom code

Tip #4: How to show/hide Block Execution Order

Tip #5: How to use S-Function to inject custom code calls anywhere

Tip #6: How to investigate model fails with build_exception.mat

Tip #7: How to measure code execution time

Tip #8: How to create stand-alone callable functions

Tip #9: How to Write to/Read from any address

Tip #10: About the Timings & Interrupts of standard models

Tip #11: How to tune any controller in real-time

Tip #12: How to keep a single toolbox visible

Tip #13: How to address licensing errors

Tip #14: How to make visible a missing toolbox in Simulink Library

Tip #15: About Automotive Math and Motor Control Library Set

Tip #16: How to SIL

Tip #17: How to PIL

Tip #18: How to use custom Linker Command Files

Tip #19: How to generate meaningful names for variables in Code Generation

Tip #20: How to control Symbolics

Tip #21: Multitasking in Simulink

Tip #22: How to migrate a Simulink model

Tip #23: New Perspective for Large and Complex Production Software Development

Tip #24: How to Integrate Custom C-code with existing Simulink Models

Re: MBD Toolbox - Tip of the Day

Daniel_Popa — Tue, 25 Apr 2017 08:55:25 GMT

Tip #1: MBD Toolbox - Block Priorities

Did you know that each MBD Toolbox/Simulink block have a Priority field - where you can specify the order of block/generated code execution?

You can use this option to alter the program flow and optimize the application.

E.g. From this: reading input data one by one as 8.0, 8.3, 8.6

to this: reading input data one of the other 8.0, 8.1, 8.2

Re: MBD Toolbox - Tip of the Day

Daniel_Popa — Wed, 26 Apr 2017 09:36:28 GMT

Tip #2: MBD Toolbox - Model Workspace vs. Matlab Workspace

Have you ever faced this kind of Simulink errors ?

Usually, the Simulink models refers some parameters that are present in the Matlab workspace. If the workspace is cleared then you need to reload the parameters again form m-file or mat-file.

For some cases it is easy to keep these parameters in the model workspace. This way you can share the Simulink model without any additional m-files/mat-files

Just right click on the Simulink canvas and select Explore:

Then, add any parameters in the Model Workspace.

Re: MBD Toolbox - Tip of the Day

Daniel_Popa — Thu, 27 Apr 2017 12:54:18 GMT

Tip #3: MBD Toolbox - Add custom code to your Simulink model

Did you know that using NXP Model Based Design Toolbox, one has the possibility to add custom C code into the Simulink model? This C code section will work with NXP blocks for different peripherals ?

There may be cases when one needs to execute some code that is not part of the model but are instead hand coded. In these instances, user specific files will need to be included in the build directory created by toolbox.

You can specify which files to include in the build directory by creating/modifying a file called {toolbox name}_user_copy_required_files.m and locate it somewhere in one of the Matlab paths.

There is an example of this file located in the ‘mscripts’ directory that demonstrates how to include user specific files.

Re: MBD Toolbox - Tip of the Day

Daniel_Popa — Mon, 01 May 2017 18:11:40 GMT

Tip #4: MBD Toolbox - Show Block Execution Order

In case you want to enable/disable the display of the Simulink Execution Order (discussed in Tip #1) there is an easy way to do that: Display -> Blocks -> Sorted Execution Order

Why would someone hide the execution order number ? Can you think of such scenario ? Leave a reply below.

Re: MBD Toolbox - Tip of the Day

Daniel_Popa — Tue, 02 May 2017 14:45:37 GMT

Tip #5: MBD Toolbox - Use S-Function to call your custom code anywhere in the model

Using the S-Function Builder and the Mode Based Design Toolbox - Add Custom Code capabilities (Tip #3) you can call your hand written functions in any place within your models.

This way you can enhance the Simulink model with multiple capabilities that may not be fully covered by Toolbox Blocks.

Using this approach you can interlace Simulink automatically generated C with your own legacy code.

Here is an example how to achieve this task: https://community.nxp.com/thread/450048

Are you using legacy code in the Simulink modelling ? Leave a comment below with the issues you have faced and how you resolved it.

Re: MBD Toolbox - Tip of the Day

Daniel_Popa — Wed, 03 May 2017 15:13:37 GMT

Tip #6: MBD Toolbox - Use build_exception.mat to find out why the model failed

Have you ever faced issues when trying to build your Simulink models and the build console reported something like "Error: Errors occurred - aborting" without any other additional information? Isn't this frustrating?

Did you know you can navigate to the build folder and search for the build_exception.mat file that offers you very detailed information about the error stack, cause and messages that were catch during the build procedure.

By simply loading this build_exception.mat file into the MATLAB workspace you could save a lot of time.

Here is a snapshot of what to expect when loading this file.

Re: MBD Toolbox - Tip of the Day

Daniel_Popa — Thu, 04 May 2017 13:29:26 GMT

Tip #7: MBD Toolbox - Measuring Code Execution Time

Using Model Based Design Toolbox, measuring the execution time of any routine is easy. Just drag-and-drop the Profiler Function block into your models or subsystems you want to check for execution time and read that output values in real time with FreeMASTER or send it over UART/CAN/etc

You can find the block within the Utility Blocks group:

Re: MBD Toolbox - Tip of the Day

Daniel_Popa — Fri, 05 May 2017 14:38:53 GMT

Tip #8: MBD Toolbox - Use Atomic Subsystem to create stand-alone callable functions

Have you ever faced a situation where you had to read and understand a large amount of C-code generated from a large Simulink model where all the code is inline? Then you probably spend a lot of time to figure out that are the input/output and local data.

Did you know you can transform parts of the model into Atomic Subsystems and then configure the Code Generation to call Reusable Functions ?

Let's consider the following example that consists in a PI Speed Controller and a Speed Estimator:

Choosing to model the MotorSpeedController as an Atomic Subsystem gives you access to Block Parameters (Subsystem)/Code Generation where you can set different code generation behaviors

Selecting Reusable Function option the generated code will become much more clear.

Here is the snapshot of the reusable function call (on the left) vs Inline Code (on the right):

Re: MBD Toolbox - Tip of the Day

Daniel_Popa — Mon, 08 May 2017 13:14:16 GMT

Tip #9: MBD Toolbox - Write to/Read from any address within the microprocessor address space

Do you need fast access to any memory mapped register of a particular peripheral within the microprocessor address space ? Do you need to perform an initialization of any specific peripheral register ?

With MBD Toolbox and DataMemWrite/DataMemRead Simulink blocks these tasks are very easy. Just check the Reference Manual for the address you need to set and give a try with MBD Toolbox dedicated blocks. No extra code is needed.

Re: MBD Toolbox - Tip of the Day

Daniel_Popa — Tue, 09 May 2017 14:23:30 GMT

Tip #10: MBD Toolbox - Timings & Interrupts

Did you know that all the blocks that are not coupled with a specific function call/event are still executed on a default interrupt based routine called Model Step Function?

This ***_step() that is triggered based on the settings from Solver/Fixed-Step size

This is a code snippet:

There is a conversion mechanism between Simulink Fixed Step Size value to the MCU System Tick that takes into consideration the MCU Clock Frequency.

Next time you design your model, keep in mind that all the generated code is called on a interrupt. Only FreeMASTER callback for data visualization is called on main() infinite loop.

Re: MBD Toolbox - Tip of the Day

Daniel_Popa — Fri, 12 May 2017 13:50:03 GMT

Tip #11: MBD Toolbox - Change position/speed/current controller gains in real-time

Using FreeMASTER you can change the variables in real-time for any running system.

A good example is the the need for tunning the controllers (position/speed/current).

By default the Simulink PID controller block uses constant values that can not be changed from outside during simulation or execution. But, if you change the Controller Parameters SOURCE to EXTERNAL you can overcome that limitation and you may change the gains on the fly.

The Simulink model will become:

Now, you can add the gains in the FreeMASTER tool and tune your controller in real time.

This way you have no excuse for obtaining a "perfect: system response.

Re: MBD Toolbox - Tip of the Day

Daniel_Popa — Wed, 24 May 2017 14:49:02 GMT

Tip #12: MBD Toolbox - Using multiple toolboxes in the same Matlab instance

Even if multiple installations and instantiations of the NXP MBD Toolbox within a single Matlab release is supported there might be situations when you might want to keep only one active and visible toolbox library in Simulink.

You can do that very easy by resetting the Matlab Search Path to Defaults and then load only the Toolbox you are interested in.

Re: MBD Toolbox - Tip of the Day

Daniel_Popa — Thu, 25 May 2017 08:15:46 GMT

Tip #13: MBD Toolbox - Common license error codes

Have you tried to use the Model Based Design Toolbox but you end-up having a Licensing Error like this ?

Most of the times you can fix this by yourself. The NXP MBD Toolbox is using FlexLM license manager from Flexera Software.

FlexLM error codes with description and possible causes can be found here: FLEXlm Error Codes

The most common source of errors for Model Based Design are:

Error Code	Description
-1	Cannot find license file.
-2	Invalid license file syntax.
-5	No such feature exists.
-8	Invalid (inconsistent) license key or signature. The license key/signature and data for the feature do not match. This usually happens when a license file has been altered.
-9	Invalid host. The hostid of this system does not match the hostid specified in the license file.
-10	Feature has expired.
-11	Invalid date format in license file.
-18	License server does not support this feature.
-21	License file does not support this version.
-30	Cannot read license file.
-31	Feature start date is in the future.
-54	No FEATURESET line in license file.
-55	Incorrect FEATURESET line in license file.

Re: MBD Toolbox - Tip of the Day

Daniel_Popa — Tue, 06 Jun 2017 15:33:28 GMT

Tip #14: MBD Toolbox - Simulink Missing Toolbox Library

Have you tried to use a toolbox that you have installed but is does not seems to be present in the Simulink Library ?

Sometimes the Simulink might not update the information correctly. With a simple F5 you can force a library refresh. If something is broken the Simulik will inform about that:

Just click on Fix and select the "Generate Repositories in Memory"

That should do the trick and made all installed toolboxes available in the Simulink Library.

Re: MBD Toolbox - Tip of the Day

Daniel_Popa — Wed, 07 Jun 2017 08:51:21 GMT

Tip #15: MBD Toolbox - Automotive Math and Motor Control Library supported features

Did you know that using the NXP AMMC Library in conjunction with NXP MBD Toolbox you can design and implement your entire application using just Simulink blocks in a fraction of the time compared other SW development approaches.

No hand-written code is required.

Here is an example of that could be achieved in case of FOC for PMSM.

Re: MBD Toolbox - Tip of the Day

Daniel_Popa — Thu, 15 Jun 2017 08:29:21 GMT

Tip #16: MBD Toolbox - How To SIL

Did you know you can test the numerical equivalence between model components and production code that you generate from the those components via the software-in-the-loop (SIL) ?

With a SIL simulation, you test very early in the project design stage, the C-source code on your host computer. Based on that you can establish the testing strategy and start testing the functional components by preparing the harness tests to create a functional baseline of the application.

Check this video to see how you can easily convert any Simulink model created with Model Based Design Toolbox to a SIL simulation: Video Link : 7844

(view in My Videos)

Re: MBD Toolbox - Tip of the Day

Daniel_Popa — Fri, 16 Jun 2017 05:26:40 GMT

Tip #17: MBD Toolbox - How To PIL

Did you know you can tie the standard Simulink model simulation with the actual code executing on the real hardware to create a co-simulation environment ?

In this co-simulation the outputs of the control algorithm and functions that are executed on the real microprocessor are fed back into the Simulink virtual simulation allowing you to detect and analyze potential issues that can only be detected once the final application is built.

Check this video to see how you can easily convert any Simulink model created with Model Based Design Toolbox to a PIL simulation: Video Link : 7845

(view in My Videos)

Re: MBD Toolbox - Tip of the Day

q380742432 — Mon, 19 Jun 2017 01:03:23 GMT

I tried this method, but it didn't work

Re: MBD Toolbox - Tip of the Day

Daniel_Popa — Mon, 19 Jun 2017 09:03:26 GMT

Hello,

This works only if the toolbox is already installed successfully on that PC. In your particular case - there is a licensing problem. Please confirm this after we will fix the DISK ID issue.

Thank you!

Daniel