Calibration & Probing Blocks

MotoHawk:Blocks:Absolute Override

This MotoHawk® block provides a connection to MotoTune, and enables run-time modification and observation of wire values with the MotoTune™ tool. Normally the block behaves as a simple pass-through. Using MotoTune, the output value may be forced to a new value, ignoring the input value.

MotoHawk:Blocks:Calibration

This MotoHawk® block provides a connection from MotoTune that allows run-time modification of calibration values with the MotoTune tool. The block behaves in simulation like a Constant block, and accepts any Matlab value as its Default Value, including data-typing casts. If the value displayed on the block has an asterisk (*) next to it, this indicates that the value is being overridden by a workspace calibration struct variable, called MODEL_cals, where MODEL is the name of the model. When output values to Simulink differ from the MotoTune inputs, due to gain, offset, exponents, or enumeration choices, both values are shown.

Note: .m Driven Calibrations

There are a couple of ways to use m-file driven values for your calibrations. First, you can simply load Matlab workspace variables with calibration values and refer to those in the default value of the calibration. For instance, a .m file could contain a workspace definition like:

Temp_High_Thresh = 20

And then you could refer to that value in the calibration block by name. You could simply create a file containing the desired values that you then load it into the workspace prior to a build.

A second method is to use a command line feature that will pull the calibrations from a running module. If you are connected to a module such that MotoTune can communicate with it, you can issue a command at the Matlab prompt that will upload the calibrations from the module and create a file:

>> motohawk_upload_cals
Getting calibrations from ECU for model: testflts...
Successfully uploaded to .\testflts_load_cals.m

We automatically look for a file named <modelname>_load_cals and if it exists, we then overlay any values found in this file on top of the default values of the block. Notice the star in next to the value. This indicates that the value is being used from the uploaded file rather than the default value. You may optionally enable this behavior for each calibration by unchecking the “Use uploaded calibration values from MotoTune” setting in the calibration.

MotoHawk:Blocks:Probe

This MotoHawk® block provides a connection a connection to MotoTune, and allows run-time observation of probed values with the MotoTune tool. The Name Source field allows the name to be entered as a Literal, evaluated as a Matlab expression, or it may be inherited from the name of the input wire. If no name is supplied, (Undefined Name) will be displayed on the block.

MotoHawk:Blocks:Relative Override

This MotoHawk® block provides a connection to MotoTune, and allows run-time modification and observability of wire values with the MotoTune tool. The block contains an offset addition, which is zero by default, making it normally behave as a simple pass-through. While using MotoTune, the output value may be locked, preventing propagation from the input to output. Then the offset value may be changed. When the output has reached the desired value, the lock can be released, and the offset is permanently applied to the signal.