I assume that the state equations you posted correspond to the linearization point for the "initial configuration" (see linearization options of the linearisation app of MapleSim).

If you choose a different linearization point (see yellow highlight below), the zeros disappear.

You might find more on the equation export here: help(DynamicSystems[Linearize])

(Update: I could not find a description on the option  "format=all")

If you are interesed in the nonlinear differential equations you can also use the equation extraction app of MapleSim.

Update2:

If you change the initial conditions of the angular velocity of the revolute joint R_1 to a non zero value you will get accelerating terms in the state equations also for the inital configuration.

So to answer your question: The inital accelation you see in the result window comes from the integration process that uses a linearized model having no "accelerating terms".

Couldn't you use the sampler component to discretize the continuous functions (signals in MapleSim, I assume) and use your working Modellica code?

The general problem I see is that MapleSim does not provide means/components that allow us to see/simulate into the future (e.g. there are no infinite impulse response filters). At which point in time (MapleSim simulation time) do you want to perform the convolution?

What you tried is basically correct. You should have added simply rad to omega1

omega1 := 2*f1*Pi*Unit('rad')

Note that the unit of rad is 1, which is the reason for the inconsistencies in your worksheet

Alternatively, as I would do it, the same without assignemt statement (":="), which requires re-execution of the whole document every time you change parameters.

Download Conversion_to_rad_per_s.mw

works in Maple 22.

At the first click you get: Waring computation interrupted. At the second click evaluation stops and Maple returns to ready (lower left corner)

If you are using a high resolution screen: Try adjusting the compatibility settings (High dpi) under the properties of maplew.exe (try different settings).

I have done this and Maple In and Output display excellent on a 4K screen (much better than Word and other office applications).

If you are still running a Maple 2020 version: Is the quality as bad? I noticed a difference between the current JDK Java platform and the earlier Java platform.

Note: In high res mode Maple 2022 menus are still a mix of low and high renderings. Changing the display within a session can also degrade the rendering of In and Output

Interesting question and topic!

Reading

help(tasks, simulating, advancedSimulationSettings)

I interpreted "plot events" equals 2000 events plotted.

But if you turn on: Solver Diagnostics you will find much more events. (Whatever such events might be?!?)

Zoom into the two plots to find the 40Hz

I would have expected that the "plot without plot events" would match the mean amplitude of the plot "with plot events".

If this your question/assumption: It seems not to be a sampling issue.

If you increase the number of plot point to 20000, plot 2 changes completely.

At this point would inspect the circuit for electronic modeling issues, which is beyond my field of expertise.

On a related topic, I stumbled across this question. You are correct in your assumption. A more realistic IK should alternate between the two solutions. However, with the input variables Tx and Ty, I don't see a simple switching condition as one can guess from the animation.
I would be interested in a better IK as well.

since it seems to work with an ideal opAmp: verify the opAmp parameters and/or set initial conditions of the opAmp

Others have answered your question implicitly by suggesting assumptions. An answer to your title could be: Because Maple does not know where to locate x^2+y^2 in the complex plane. Depending on where it is located the simplified result can differ in sign.
If x and y were imaginary for example, Maple could simplify to something that does not appear equal, such as:

In your example simplify with the option symbolic works as well (but assumptions are the safer way, seeQues_Mapleprime_symbolic.mw)

Download root_in_fraction.mw

For repeated use you could think of defining a function that makes live a bit easier and avoids nested commands with many parenthesis.

I have taken you inital question as an example in an unrealted question. 

Maybe such a construct can help in the future when no "one-liner" is at hand.

In case you don’t get better material, I can at least share my thoughts and experience about frames and flanges.

Since MapleSim is very easy to start without robotics background, there is the danger that flanges and frames are mixed up by wrong intuition.

The reason is that 3D multibody components orient to each other via (coordinate) frames. During assembly, when drawing a connection between 2 components frames match together as if they were true mechanical flanges with bolts and nuts.

Another reason for misleading intuition can be that the very important RBF component (rigid body frame) looks like a structural component with flanges at the ends.

In the attached example 2 strategies to build an assembly are shown. I prepared the example to better understand what frames in MapleSims provide (today I would call the “matching frame approach” rather “rotating frame approach”. Maybe the example helps understanding frames.

tasks,visualization,highlightingMultibodyPortsAxes (paste it in the help system) might also be useful to understand frames and inspect assemblies. You will also see that connecting components in 3D is actually done via ports and that these ports have axes of a (coordinate) frame that align to each other. So frames in my interpretation are a kind of 3D port to rigidly connect and orient components.

Flanges are more 1D interfaces/ports where you connect “something” that either constrains assemblies or transfers energy.

Good luck with your team!

Assembly_approaches.msim

I could fix your worksheet (see attached).

However, I agree that your worksheet should have worked. I expect the solve command to produce the same result as the isolate command. This observation should be investigated by an expert (I have send a software change request).

Maple Worksheet - Error

Failed to load the worksheet /maplenet/convert/zadanie_z_jednostakim_-_problem-_using_isolate.mw .

Download zadanie_z_jednostakim_-_problem-_using_isolate.mw

.

Alternatively, you can take advantage of Maples ability to handle equations.

In the attached example, no assignment statements “:=” are used for parameters. Instead, general analytic solutions are derived and parameters for a particular solution are defined as equations (as you would write it by hand).

Using this workstyle, no re-execution of the whole worksheet is required when parameters are changed. This is an advantage if the worksheet becomes large or if parameter studies are done. Also, numerical artifacts or missmatch of units, as in your case, are less likely to impact calculations and results.

Maple Worksheet - Error

Failed to load the worksheet /maplenet/convert/Answer_on_-_Solving_equation_with_units_problem.mw .
 

Download Answer_on_-_Solving_equation_with_units_problem.mw