In the example that you are referring to, RunTimeDataType is a user-defined datatype, and it is the datatype of a parameter whose value is a function of multiple S-function parameters. This parameter does not appear on the block dialog at all, but is an internal run-time parameter that depends on other parameters. Simulink does not anything know about this parameter - it only holds the pointer for you, but you need to allocate, maintain and free the memory associated with the parameter data. All responsibility lies with you. I would say that this is a more advanced concept, and unless you need internal run-time parameters, you should simply use ssRegDlgParamAsRunTimeParam if you only want to use a dialog parameter as a run-time parameter.
However, in case you're still interested:
- The parameter (denoted as 'mass' throughout the code) is allocated and stored on the block in mdlSetWorkWidths - look at how the pointer 'mass' is allocated and cached on the block using ssSetRunTimeParamInfo.
- Since the parameter is a function of other dialog parameters, you need to update it every time the parameters change. Hence, you need to have code in mdlSetWorkWidths and in mdlProcessParameters to update the value of 'mass' based on the parameters.
- In mdlOutputs, you need to read the value, so you use (ssGetRunTimeParamInfo(S,0))->data to get the cached value and use it a required.
- Manually free the associated memory in mdlTerminate - you allocated it, so you need to free it as well.
And yes, your understanding of the call to calcMass is correct - I believe this function updates the cached value of 'mass' based on the values passed to it.
