Learn about Webel's comprehensive SysMLv2 Workshop Seminar course!
Webel now has a SysMLv2 Online Self-Study course with self-test Quizzes!
Learn about the Webel Q&A online self-testing system for SysML v2/v1

Cameo: SysML v2 Simulation plugin quick guide for Cameo 2026x Release1 [EXPERIMENTAL]

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
Policy level
Specification keywords
Keywords

Since late June 2026 the SysMLv2 Simulation plugin for Magic Cyber-Systems Engineer® (Cameo Systems Modeler®) is here! It requires also a licence for Magic Model Analyst® (Cameo Simulation Toolkit®).

It is strictly EXPERIMENTAL, and there's quite a lot that one could do with Magic Model Analyst® (Cameo Simulation Toolkit®) for SysMLv1 that one can't yet do for SysMLv2, but there's certainly already a lot that one can do.

Webel IT Australia is ahead of the pack, and is already including examples and videos on SysMLv2 simulation in the Webel SysMLv2 courses:

Some limitation of the current EXPERIMENTAL SysMLv2 Simulaton plugin

For a full list of restrictions visit the official documentation under External Links, the following just indicates some main things to be aware of:

  • Binding connectors are restricted to only work with primitive types and simple enumerations.
  • Only a limited range of simpler actions are available and only as state actions (entry, do, exit).
  • It seems not to be able to execute actions directly yet.
  • There doesn't seem to be support for full animation of flows yet (compare with Magic Model Analyst® (Cameo Simulation Toolkit®) for SysMLv1).
  • The very useful Time Series Chart only seems to work for Integer and Real values (not Boolean AFAICT).
  • The simulation does not check the direction of a directed Features (between ports).
GOTCHA: If you use Stop a simulation it will close the Time Series Chart which can be inconvenient if you have it nicely configured and placed as a docked window.

Some things to be mindful of

  • Use interface usages with interface definitions for all port-to-port connections.
  • For flows use flows within interface definitions.
  • You can only "run" (launch the Simulation windows) from a «part» usage (not a «part def»).

Some things known to work

  • An «item def» works fine for a payload including for transition accept triggers. It is not restricted to primitive attribute types.

See it in action!

Relates to
Related notes
Related notes (backlinks)
Related snippets (extracts)
Visit also
Visit also (backlinks)
External links