Opened 11 years ago

Closed 10 years ago

#2475 closed defect (invalid)

FMU-export / bug at handover from top-level to low-level

Reported by: fixed-term.Sven.Baetzing@… Owned by: Adeel Asghar
Priority: high Milestone: 1.9.3
Component: OMEdit Version: 1.9.0Beta
Keywords: FMU Cc:

Description

Hello,

I am using the nighlty build of OMEdit.
While exporting a model in FMU no error accurs.
After importing I checked a few function and I detected a bug with the initialization.
Boolean parameter from the top-level arent handovered to the lower-level. These parameters normally indicate if the system should get initialized or not.
Manual set of the lower-level parameter doesnt work in this case aswell.

Exporting and importing after removing top level parameter fixed the problem, initialization works.
Please fix the handover problem because, nearly all of my models contains sublevels and removing top-level parameter and using the lowlevel parameter wont be the solution

Please find attached the used library and the exported FMU, which arent working as they should.

Sincerely yours, Sven Bätzing

Attachments (3)

DC_Mechlib_SB.mo (370.8 KB ) - added by fixed-term.Sven.Baetzing@… 11 years ago.
lib
CableReel.mo (2.9 KB ) - added by fixed-term.Sven.Baetzing@… 11 years ago.
mo file
DC_Mechlib_SB.2.mo (346.9 KB ) - added by fixed-term.sven.baetzing@… 11 years ago.
lib with initiliaze at top-level

Download all attachments as: .zip

Change History (8)

by fixed-term.Sven.Baetzing@…, 11 years ago

Attachment: DC_Mechlib_SB.mo added

lib

by fixed-term.Sven.Baetzing@…, 11 years ago

Attachment: CableReel.mo added

mo file

by fixed-term.sven.baetzing@…, 11 years ago

Attachment: DC_Mechlib_SB.2.mo added

lib with initiliaze at top-level

comment:1 by fixed-term.Sven.Baetzing@…, 11 years ago

On further tests i found out, that other parameter (non-initialization) can cause problems during the FMU-export aswell if they are hand overed from a lower-level to the top level.

comment:2 by Martin Sjölund, 10 years ago

Milestone: 1.9.11.9.2

This ticket was not closed for 1.9.1, which has now been released. It was batch modified for milestone 1.9.2 (but maybe an empty milestone was more appropriate; feel free to change it).

comment:3 by Adeel Asghar, 10 years ago

Can you test again with the latest nightly build? Several issues related to this one were fixed in last few months. This should work now.

comment:4 by Martin Sjölund, 10 years ago

Milestone: 1.9.21.9.3

Milestone changed to 1.9.3 since 1.9.2 was released.

comment:5 by Adeel Asghar, 10 years ago

Resolution: invalid
Status: newclosed
Note: See TracTickets for help on using tickets.