@mmcdara 

I can’t see a better way without referring to advanced statements like applyrule. Thank you!

 That what i get with 2023

As an alternative to dharr's answer, which does the fit in mA, you could divide values in Y by 1000 do get results in A which fit to C in muF.

The book is correct. See the plots in my reply to dharr below

@dharr Just a check that the data is in mA. I have never used units and fits so I stopped after checking that the parameters fit to the data. So maybe your tweak with mF is not required.

Download Mapleprimes_Question_Book_2_Paragraph_5.12_Question_5_with_units.mw

@Carl Love 

Maple provides so many solutions, that I rarely need to code (and test) procedures.

In case I have to pass a function I will not try it make work a you said. Thank you for bringing this to my attention.

As for Fortran, I do not mis goto but I have kept a few punch cards that I use as bookmarks for sentimental reasons. I will see if I can find a goto card as physical proof that those statements were in use ;-)

@Kitonum 
Also with my 2023 installation

@acer

This particular value for posint is worth an example in the detaled helppage of fslove.

Infinite thanks!

@dharr 

Thank you for your detialed answer.
It looks like that I have used by wrong intuition a calling sequence of RootOf that is not documented in help(RootOf).

There is one equation too much. You only have 5 unknowns

indets({fa[1], fa[2], fa[3], fa[4], fa[5], fa[6]});

                 {U[0], V[0], W[0], Z[0], r[0]}

@Thomas Richard 

All warnings are useful. At least I want to see them once.

This particular warning sometimes appears and sometimes in similar cases without masses it does not. In most of my cases it can be ignored.

If this warning can’t be reset by design and there are no GUI issues hiding menu items, my question has been answered.

In this case I find I find this tip from help(MapleSimUserGuide,Chapter02) misleading:

If warnings to be reset are labeled with a yellow triangle, I would expect that a warning labeled with a yellow triangle can be ignored as well.

Thank you for the clarification.

Your question and finding are worth being converted into a post. Could you share and example?

@Nicole Sharp 

Good to hear. If this is reproducible what you found out Maplesoft can have a look at it. Maybe there is a solution for mobile users.

This bug is older than 2023, I have it from time to time. Restarting always works, but that's not what you want do when you're in the middle of something.

One of my suspicions is that it happens when the display settings change. For example, when you disconnect an external monitor from a laptop. 

Another possibility is that it is related to the load on the system (applications running in parallel, number and history of mservers managed by the Maple GUI or the time and history since last logon). 

In both cases it is related to the operating system and may not be a programming bug, but something that depends on Microssoft and/or the OpenJDK platform.

Your observation (new to me) that it depends on maximising the GUI Window points rather to the first susspicion.

@acer
Yes, exactly!

@Maxie 

The model I have send to you must have changed its state when it was saved.

In the model I have send to you to make it simulate, try chaning the EC to:

This should assemble and allow you to inspect the model.

As I have said the model does not assemble correctly. You should fix this first.

4_fix-3.msim

Here is another good video https://www.youtube.com/watch?v=4c0dbvAMrAU on custom contact components. I would try to combine it with a classical analytical formula for beam deflection.

To start I would use the deflection for a "Simply Supported, Intermediate Load" as given here

https://mechanicalc.com/reference/beam-deflection-tables

(I cannot guarante if these formulas are correct.)