Opened 6 years ago

Last modified 3 years ago

#5465 assigned defect

Issue with locked-rotor Asynchronous Machine model

Reported by: Dietmar Winkler Owned by: Karim Adbdelhak
Priority: high Milestone:
Component: Run-time Version: v1.14.0-dev-nightly
Keywords: Cc: Andreas Heuermann

Description

I have a very simple test based on an MSL example:

model LockedRotorTest
  extends Modelica.Electrical.Machines.Examples.AsynchronousInductionMachines.AIMC_DOL(aimc(useSupport=true));
equation 
  connect(aimc.support, aimc.flange) annotation (Line(points={{0,-50},{0,-40}}, color={0,0,0}));
end LockedRotorTest;

It's basically an electrical machine that just got its rotor locked to the support.

In Dymola simulating 1 second takes about 0.1 seconds. Trying the same in OMEdit bascially locks the machine. I've now been waiting for more than one hour and the simulation still does not finish.

Is this simply a solver setting problem or more an underlying OMC problem?

Attachments (7)

LockedRotorTest.mo (266 bytes ) - added by Adeel Asghar 6 years ago.
script.mos (204 bytes ) - added by Adeel Asghar 6 years ago.
LockedRotorTest.2.mo (313 bytes ) - added by Dietmar Winkler 6 years ago.
LockedRotorTest.2.png (156.3 KB ) - added by Adeel Asghar 6 years ago.
Dymola.png (28.3 KB ) - added by Dietmar Winkler 6 years ago.
OM500.png (32.8 KB ) - added by Dietmar Winkler 6 years ago.
OM5000.png (31.8 KB ) - added by Dietmar Winkler 6 years ago.

Download all attachments as: .zip

Change History (19)

comment:1 by Dietmar Winkler, 6 years ago

Btw, instead of locking it down one can provide a extremely slow speed on the shaft (e.g., 1e-6) and OMC behaves again.

by Adeel Asghar, 6 years ago

Attachment: LockedRotorTest.mo added

by Adeel Asghar, 6 years ago

Attachment: script.mos added

comment:2 by Adeel Asghar, 6 years ago

This seems to work fine both from CLI and OMEdit. Maybe you are using some special flags. Post your omeditcommunication.log file.

comment:3 by Dietmar Winkler, 6 years ago

My example model had one important modification missing. The machine needs to be connected in star. I've attached the corrected version which will then make OMC fail.

by Dietmar Winkler, 6 years ago

Attachment: LockedRotorTest.2.mo added

by Adeel Asghar, 6 years ago

Attachment: LockedRotorTest.2.png added

comment:4 by Adeel Asghar, 6 years ago

Cc: Karim Adbdelhak added

Well I get several simulation error messages but at least the simulation finished rather fast.

comment:5 by Dietmar Winkler, 6 years ago

Yes, after I got a new nightly build again it now also simulates quite fast but with errors and wrong results.

comment:6 by Adeel Asghar, 6 years ago

Cc: Andreas Heuermann added; Karim Adbdelhak removed
Component: OMEditRun-time
Owner: changed from Adeel Asghar to Karim Adbdelhak
Status: newassigned

Then its up to the solver guys.

comment:7 by Francesco Casella, 6 years ago

Summary: Simple example test locks up OMCIssue with locked-rotor Asynchronous Machine model

@dietmarw, could you provide some indication of where the results are wrong? E.g., you may attach the result file produced by Dymola with some additional comment.

comment:8 by Dietmar Winkler, 6 years ago

With Dymola you get for currentQuasiRMSSensor.I:


for 500 and 5000 steps.

With OMC you get with 500 steps:


and with 5000 steps:


I hope this helps.

Last edited 6 years ago by Dietmar Winkler (previous) (diff)

by Dietmar Winkler, 6 years ago

Attachment: Dymola.png added

by Dietmar Winkler, 6 years ago

Attachment: OM500.png added

by Dietmar Winkler, 6 years ago

Attachment: OM5000.png added

comment:9 by Francesco Casella, 5 years ago

Milestone: 1.14.01.16.0

Releasing 1.14.0 which is stable and has many improvements w.r.t. 1.13.2. This issue is rescheduled to 1.16.0

comment:10 by Francesco Casella, 4 years ago

Milestone: 1.16.01.17.0

Retargeted to 1.17.0 after 1.16.0 release

comment:11 by Francesco Casella, 4 years ago

Milestone: 1.17.01.18.0

Retargeted to 1.18.0 because of 1.17.0 timed release.

comment:12 by Francesco Casella, 3 years ago

Milestone: 1.18.0

Ticket retargeted after milestone closed

Note: See TracTickets for help on using tickets.