Dezyne and Dezyne-IDE 2.13.3 released

October 05, 2021

We are delighted to announce Dezyne 2.13.3: The simulator function including system scope.

This replaces the simulation function that was moved from Dezyne Core in release 2.10 to Dezyne-IDE in release 2.11. The new simulator function provides a basic command-line interface in Dezyne Core and is now also integrated in the Dezyne-IDE.

The integrated Trace view of the simulator was rewritten in P5, using the new Dezyne-P5 project by Rob Wieringa which he developed as free software. The buttons for events that are outside the accepted behaviour are only greyed-out and can still be selected to inspect what happens if the event would occur.

The integrated System view was also rewritten in P5, removing the last dependency on third-party proprietary software.

Finally, verification and simulation can now be loosely integrated on the command-line and an experimental ASCII diagram is provided by dzn trace, i.e., running

    dzn verify examples/Alarm.dzn | dzn simulate Alarm.dzn \
      | dzn trace --format=diagram


error: illegal action performed in model Alarm
test/all/Alarm/Alarm.dzn:136:25: error: illegal
console             Alarm              sensor siren
  //                 //                 //     //
   .                  :                  .      . error: illegal
   .                  :                  .      .
   .                  :         triggered.      .
   .                  :<-----------------.      .
   .                  :                  .      .
   .          detected:                  .      .
   .<-----------------:                  .      .
   .                  :                  .      .
   .                  :turnon            .      .
   .                  :------------------------>.
(trail sensor.triggered console.detected siren.turnon <illegal>)

The documentation is available here:

We will evaluate your reports and track them via the Gitlab dezyne-issues project, see our guide to writing helpful bug reports.

What's next?

Extending the language with aspects like: implicit interface illegals, implicit temporary variables, implicit interface constraints. Releasing the Dezyne Core as free software.


Looking beyond the next releases we will introduce a new keyword defer to deprecate the use of async. Full blocking support. Hierarchical behaviors, module-specifications and data-interfaces. Support for Model Based Testing.

The Verum Team


Here are the binary downloads and a GPG detached signature[*]:
dezyne-2.13.3-x86_64-linux.tar.gz (70MB) (133MB)
dezyne-ide-2.13.3-x86_64-linux.tar.gz (85MB) (136MB)

Here are the GPG detached signatures[*]:

Here are the MD5 and SHA1 checksums:

0ac6eec9d18f0953a2641c08bee8b602  dezyne-2.13.3-x86_64-linux.tar.gz
fbf118cd0c640e15894c465820c6af5c  dezyne-ide-2.13.3-x86_64-linux.tar.gz
790d2db6ab0b79bfbb71ea2101bc9d574c1866fe  dezyne-2.13.3-x86_64-linux.tar.gz
6e5f100a500b73daf8e88abcb2eef30c9bc8a6a3  dezyne-ide-2.13.3-x86_64-linux.tar.gz

[*] Use a .sig file to verify that the corresponding file (without the .sig suffix) is intact. First, be sure to download both the .sig file and the corresponding tarball. Then, run a command like this:

gpg --verify dezyne-2.13.3-x86_64-linux.tar.gz.sig

If that command fails because you don't have the required public key, then run this command to import it:

gpg --keyserver \
  --recv-keys 1A858392E331EAFDB8C27FFBF3C1A0D9C1D65273 AD43109BE73D4891B77076862A611108640C1816

and rerun the gpg --verify command.

Get informed, get involved

Join #dezyne on



Changes in 2.13.3 since 2.13.2

Changes in 2.13.2 since 2.13.1

Changes in 2.13.1 since 2.13.0

Changes in 2.13.0 since 2.12.0

Dezyne Core

Changes in 2.13.3 since 2.13.2

Changes in 2.13.2 since 2.13.1

Changes in 2.13.1 since 2.13.0

Changes in 2.13.0 since 2.12.0

About Dezyne

In Dezyne, you define components and their interfaces through a familiar and compact C/Java like-language. The Dezyne language is targeted at the logic or event-driven behaviour of an application. The interfaces are the specification and the components are the implementation.

Dezyne automatically verifies semantic correctness of the logic behaviour and proves that the components correctly implement the interfaces. A user can simulate the behaviour to validate whether this is as intended. Diagrams and logical views are generated automatically from the language description. As a final step code can be generated in a number of standard programming languages.

Without having to rely on a process Dezyne automatically highlights problems areas, stimulates communication about these and enforces that components work together.

About Verum is a leading developer of software design tools to create, simulate, mathematically verify and automatically generate code for embedded and cyber-physical systems.

At Verum, we help our customers and partners solve the most challenging software issues of today and tomorrow. We support customers with our product Dezyne, a software engineering toolset that enables engineers to specify, design, validate and formally verify software components for embedded systems combined with consultancy services.