Book a Demo

Author Topic: RealSignalOutElement vs RealOutSignalElement  (Read 3892 times)

Martin_Bohring

  • EA Novice
  • *
  • Posts: 12
  • Karma: +5/-2
    • View Profile
RealSignalOutElement vs RealOutSignalElement
« on: April 17, 2021, 02:06:43 am »
Hello all,
Since I need to do resource, data rate, bandwidth calculations I resorted the simulation capabilities of EA.
Could have done those in Excel, but I try to follow are more MBSEesque Appraoch here.

So recently started to work with the OMG SysPhys Profile, because it has been added to EA 15.2 1554 in August 2020.
(Thanks Sparx for a move in the right direction)
After several updates I assumed the support to be in a mature state.

When following the Guidance in "Simulation with Precision" Tutorial from Sparx the Model Wizard is used to add some needed definitions.
You get 2 packages with value type and interface block definitions that are alos defined within the OMG SysPhys Profile spec.

And here comes the kicker:
Those names do not match.

The OMG naming scheme is "RealSignalOutElement" and the wizard gives me "RealOutSignalElement".

I can still performing those simulations because the Interface Block type names are not significant here.
(the applied stereotypes drive the code generation for OpenModelica)

I still consider it a bug.



qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: RealSignalOutElement vs RealOutSignalElement
« Reply #1 on: April 17, 2021, 02:28:57 am »
I have no clue, but typos are something not uncommon in EA. Some were (and are) lurking around ever since (did not check the former Britsh Generalisation vs. the now valid American z-variant). Send a bug report (bottom right this page) and see what happens.

q.