Migrate Rhapsody Developer to EUSIII

What is the difference?

Rhapsody Developer is the “full” version of Rhapsody, EUSIII (Embedded UML Studio III) is the Willert version. The only difference is that EUSIII does not have Animation, all other features are there. Also EUSIII has the Willert RXF as additional Framework.

No Animation? Is that bad?

Not really. Animation will only work with Windows on a PC as target environment (Or Linux or another really powerful platform) otherwise it is not possible/practical to use it. EUSIII has an alternative built-in solution called “Embedded UML target Debugger” that does the same but without using additional resources.


Yep. The Real-time eXecution Framework. The Willert Framework that allows you to generate Rhapsody code on even the smallest of targets without real-time violations or large use of resources. Comes with a built-in single-threaded RTOS or adapters for other RTOSes. Also included is the UML target Debugger that can write Sequence Diagrams and Timing Diagrams even from a small target environment.


Nope. Not necessary. You can keep using your existing installation. Since EUSIII is based on the Architect for Software you have to start that version.

  • Starting Rhapsody via a desktop icon. (Or via the start menu) Then you can open the properties of the shortcut and go to the tab “Shortcut” (Names are different in other languages) There you can add “-architect” to the “target” field. If it already says “-dev_ed” you have to remove that. You can add the -lang=C or -lang=C++ to start the correct language by default.
  • Starting Rhapsody by double-klick a Rhapsody Model. Now you have to look for the Rhapsody.ini file. This should be in the directory next to where your “Share” directory is. In that file there are 2 commands:

    You should change them that they say “Architect” and the correct language.

Install RXF

Not only does EUSIII come with the RXF, you really need it. Without an RXF the code generation will not work. So you must install one. It is not important which one but of course you should install one that you want to use. Installation is easy, just start the setup, answer the questions, check if there are no errors (When an error is given during installation it will NOT workl!!!)
When you have purchased EUSIII (Or just an RXF) you have access to the Willert Download Portal where you can download your RXF adapters for the Language (C or C++) the Compiler (Keil, IAR, GreenHills, Visual Studio and many more) and the RTOS (CMSIS, FreeRTOS, OORTX, µCOS, Linux and many more) that you want to use.


You either have received a dongle (with a license file) or just a license file (Floating License) You just install that as usual with Rhapsody,

So that’s it. Happy Modeling with Embedded UML Studio III

Walter van der Heiden (wvdheiden@willert.de)

7 thoughts on “Migrate Rhapsody Developer to EUSIII

  1. If one has Rhapsody Developer, can one use the RXF?
    There are clients that would benefit from the small footprint that RXF provides, but either have existing licenses or use animation to debug at the logic level (model level). Once debugged on Win, they want a new component using RXF for the target processor.


  2. Well, nice article but… I understand, the EUS III might be an alternative for very small targets. Any other reason to switch to your edition?

    You say, I must/ can start my Developer in Architect mode to run your RXF? Would not it be a suggestion, buying an Architect license and running it beside the Developer? For small target projects?

    And at least, is there an advantage using it on well powered devices?


    1. Hi Henry

      Thanks for asking.
      – You can just use your developer if you have one, no need to use architect. The usage of teh RXF is tied to using the profile and the stereotypes, not to a version of Rhapsody.
      – Using a second license is possible but not necesary. It is not a car where you could have a big truck and a small convertable to have 2 use-cases fulfilled (transportation and fun) Rhapsody will adapt itself to the situation by using the correct Framework for the job.
      – The RXF is absolute the best (Or actually the only serious ) posibility on small targets with high real-time requirements. But since it is very scalable the advantages are also great on even the laregst environments. Try it out, eval versions are on http://download.willert.de




  3. Like your blog but I think you are underplaying the value of animation in 2 ways. Firstly it works on any target that has the ability to send TCP messages and, even if your target hasn’t that feature, the value of reviewing and animated model is high in my experience.


    1. Hi Ian.

      Thanks for your reply! And thanks for reading and liking!
      You are right for larger systems. 99.9% of my users use small systems. And real-time systems. Animation can only be used to test some logic there (on a PC, not on target)
      Our UML target debugger is still useable there since it does not influence timing and is _really_ small but still gives you the insight need to debug on UML level.



Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.