If you want to change the initial values for states of built in blocks, there will often be associated parameters that describe these initial values. Since these are inside components, you access these parameters by specifying the component name followed by a dot and then the parameter name, like so:

WSMSimulate[mmodel, {0, 10}, WSMParameterValues -> {"Variable_n.y_start" -> 2 10^15}]

I think you could potentially also make use of WSMInitialValues, but I would advice against it since many of these built in blocks have different ways that they can handle the initial state parameter. The integrator component has a parameter called initType that will change this behavior, and then you need to have specified it through the parameter, rather than enforcing the initial state with WSMInitialValue.

You can find a list of the parameters that you can change by highlighting the component in SystemModeler. Alternatively you can run:

WSMModelData["Integrator", "ParameterNames"]
[Out]: {k, y_start}

in Mathematica. (Note that the short hand name, "Integrator" will only work if there is only one component loaded with that name, else you will have to specify the full path "Modelica.Blocks.Continuous.Integrator")

You also mentioned gain, product and add, but since they have not states, their initial values cannot be set and rather are determined by the other states in your system. Their parameters, like the gain constant, can of course be set through Mathematica with WSMParameterValues.

I don't fully understand what you mean by connecting to a line, are you referring to the following?

The dot/junction point is there to signal that the value being transmitted through the connection is the same for all the connections extending from the junction point. It is automatically displayed when two connection lines that share a common port cross each other. The connections are still being made from each of the ports, not to the line itself.

Similarly, a gap is displayed when two connection lines that does not share a common port crosses each other, like so:

Regards, Patrik

No problem!

No, you can load the model directly from Mathematica using the Import function:

Import["PhotoConductor_Block.mo", "ModelicaModel"]

You need to have called Needs["WSMLink`"] before that so that "ModelicaModel" is a recognized format. You don't have to start SystemModeler though. Note that if you don't have the file in one of the folder specified in $Path (in Mathematica) you will have to give the absolute path to your model file, I omitted that in the expression above out of simplicity.

Don't hesitate if you encounter any problems later.

If you are interested, here is a quick video introduction to using SystemModeler with Mathematica: https://www.wolfram.com/training/videos/ENG022/ . More are available here: https://www.wolfram.com/training/courses/system-modeler/

Regards, Patrik

Hello Eduardo,

I am not able to reproduce your problem. What version of SystemModeler are you using? Would you be willing to share the model that you have tried, or could you show what Mathematica code you used to try and set the initial values of a block?

I used the following model in SystemModeler:

model Model1
  Real n(start = n0)"The electron";
  parameter Real n0=0;
equation
  der(n)=0;
end Model1;

And called:

WSMSimulate["Model1", {0, 10}, WSMInitialValues -> {"n" -> 2 10^15}]

In Mathematica, and I got the expected result. An alternative you could try is to change the parameter "n0" that you have set to correspond to the initial value of n. You can do this with the WSMParameterValues option:

WSMSimulate["Model1", {0, 10}, WSMParameterValues -> {"n0" -> 2 10^15}]

Regards, Patrik