@jalal Explain how you want it animated. Provide that here.

Please don't submit a separate Question thread for this.

If this Post is supposed to serve as an example of good practice then the first example (A) would be better -- and also far more clear -- as,

restart;
with(ScientificConstants):

GetValue(Constant(g));

                       9.80665

instead of its current (and muddled) form, ie.

restart;
with(ScientificConstants):

ScientificConstants:-GetValue(Constant(g))

                       9.80665

Also, the Help page with Topic UsingPackages could be improved in several ways. It's an important usage page for new users, and ought to be a paragon of lucidity and helpfulness.

- It should utilize the colon-dash syntax, eg. P:-E, and not the square-bracketed, indexed syntax, P[E], in its early examples. The latter form is inferior because it can sometimes need the extra safety of having the index-name to be uneval-quoted like P['E'] (as mentioned later in that very page!). In fact the indexed form can sometimes need to be P[':-E'], which appears silly since P:-E is safer and simpler.

It's not helpful or sensible for that Help page to first describe examples using the inferior P[E] form, and only in a later paragraph mention that the P:-E form is more recommended.

The indexed form like P[E] should only appear in a very late paragraph on that Help page, on account of there being a relatively small number of old packages not converted to work with the recommended colon-dash P:-E form.

- That Help page is too verbose and abstract. A few sensible, concrete (actual) examples would be better and more understandable that all that abstract talk of some PackageName. New users shouldn't have to decode all that, including the abstract PackageName['command'](arguments).

- After the basic examples of short and long form have been demonstrated with nice clean, clear, and concrete examples then a couple of examples of the (underdocumented!) uses and use syntax would be relevant and completely apropos. For example,

restart;
use ScientificConstants in
  GetValue(Constant(g));
end use;
                    9.80665

restart;
G := proc()
  uses ScientificConstants;
  GetValue(Constant(g));
end proc:

G();
                    9.80665

And, to be helpful to the programmer:

restart;
use SC=ScientificConstants in
  SC:-GetValue(SC:-Constant(g));
end use;
                    9.80665

restart;
F := proc()
  uses SC=ScientificConstants;
  SC:-GetValue(SC:-Constant(g));
end proc:

F();
                    9.80665

How many roots do you need to find?

Please stop posting duplicates and close followups of this in separate Question threads.

Instead, please put your followup queries or additional details here.

@hisabt How is this any different from what Tom answered, earlier?

@Tamour_Zubair The problem with downloading is caused by the presence of the # special character in your file's name.

I fixed the link of such an example in another Question, yesterday. I don't want to make that a habit. Perhaps you could use another filename.

@tomleslie I've fixed the link.

I forgot to remove the WRAPPER keyword from the define_external calls in one of those attachments. Could you please remove it, or download the now-edited first attachment in this Answer?

But since Control & Info are not structs then the WRAPPER option is not needed, and may be removed. And wrapperless external-calling doesn't need to compile anything, so hopefully that fixes that worksheet for you.

Where did the attachment go?

It is poor etiquette to include only an image of your expression, so that others can only test by retyping the supposed expression.

Instead, please be polite and upload and attach your actual worksheet that contains the expression. You can use the green up-arrow in the Mapleprimes editor for that.

Ensure that all other parameters have numeric values. What is the numeric value of Ea? Of F? Of Rrt? Is "PI" a mispelling of "Pi"? etc.

Also, if you have candidate ranges for the solving-variables then now is a good time to share such information.

Please don't put followup queries for this example in separate Question threads. Instead, just add it here. Eg. what happens at (0,0)?

@ContrapuntoBrowniano You marked your Question as "Maple 2018", and that is not the same as Maple 18.

Maple 18 was released in the year 2014. The Maple version naming scheme changed in the year 2015, to have the version number match the release year.

I will submit a report.

Download problem_etian2_rep.mw

@Chorux Sorry, I left in reference to another list I'd made. That should now be corrected, above.

Also, the code snippet $nops(L) may get rejected by the 2D parser, so I changed it to $1..nops(L) which should work in both 1D and 2D input modes.

@Rouben Rostamian  I saw it on the Help page in Maple 2022.0 for Topic plots:-display.

     redraw : boolean; specifies whether to allow redrawing of static
     2-D plots by combining the original plot calls into a single call
     rather than just displaying them together

I happened to have previously observed a (rare, hopefully, and now reported) case in which that new (default of) redraw=true caused a slowdown. So I was lucky to have had a little head start here.

Mentally I lump it in with explicitly adding the old defaulf of adaptive=true option for plot, that can help avoid some new slowdowns due to the adaptive=geometric in Maple 2022.0. Hopefully these things will be ironed out in 2022.1.