What’s new in 25.7

To make it easier to work in the main tools of Engee - technical computing environment and model building editor, we have created a separate module for graphs and visualisation from command line . Now graphs of different tools will not "mix" and will be easier and clearer to work with.

In May release we have completely replaced the text cell editor in interactive scripts . It has become much more functional and friendly. We have now implemented support for all new cell element types when exporting an interactive script to PDF and html. The same applies to post generation in Community. These beautiful elements will decorate not only Engee scripts, but also your automated reports and posts for colleagues and the Community!

If you set a variable using the const function, such a variable will become a global constant and its value will not be changed or cleared in the module Variables using the "broomstick" It can be cleared only by restarting the Julia kernel. We have added a special field in the corresponding menu, in which constants will be marked and you will understand, by what method it is necessary to clear these or those values.

We have added new object models - PID controllers in parallel form Pid and in standard form PidStd, as well as a new function pidtune. PID controllers can be either continuous or discrete. It is now even easier to study the dynamic behaviour of control systems.

The pidtune function allows you to tune PID controllers in parallel and standard forms of linear system models. For better tuning, you can specify the desired cut-off frequency as well as a strategy for selecting the parameters of the controller based on the performance requirement.

Previously we implemented the ability to add a signal to a chart by simply dragging the record icon from the model canvas, but now you can use this familiar action to create a new chart anywhere you like, or create a new tab in the Signals field right away!

Implemented the ability to change the location of not only the transition endpoint, but also the start point. Now you can customise your state diagrams even more beautifully and make them more readable.

To improve the efficiency of working with state diagrams, we have extended the capabilities of debugging for finite automata. You will now be able to display the values of variables at each debugger step in the signal table, and signals that have changed since the previous step will be highlighted. In addition, it is now possible to edit the values of output signals and local variables while pausing at a breakpoint.

We have added explicit bus support on inputs and outputs of link models. The output signal type is set in the link model output block settings (it is also required to define bus signal types there) and you will have access to all bus features - selection of the desired signal, etc.

Now all software control commands for actions on an open model in the editor are immediately reflected in the interface on the canvas. Additional synchronisation settings are no longer required.

Now you can display the block settings card in a separate window and fix it in the interface. This is done in the context menu by pressing the PCM key. It will be opened at any level of model nesting, and you will be able to adjust parameters of the block at any time.

Until now, Engee could only calculate classical steady-state modes in which all derivatives of the state variables of the physical part of the model are zero. We now support a special algorithm for linear physical networks that analyses the harmonic components of the solution in a special way, which allows us to find a steady-state sinusoidal regime - that is, one in which the components of the solution either remain constant or are harmonic oscillations with constant amplitude and frequency.

We note separately that physical networks with simultaneously represented in the model sources of harmonic oscillations at different frequencies are supported. The most obvious application for the new functional is in electrical engineering and power engineering, but nothing prevents its use with mechanical, thermal and various heterogeneous physical networks as long as they remain linear.

Exponenta CITM operates in the wireless industry and develops high-end IP cores (blocks) for wireless systems that provide reliable and efficient data transmission in a variety of environments.

To debug IP cores as part of your systems and algorithms in Engee, we implement their integration as blocks for the Engee simulation environment. The corresponding category in block library will now be available for you. The library will be gradually expanded, the first cores available are OFDMex and PC-CFRex.

Recall that custom library of Engee blocks can contain any blocks you like - from standard libraries or your own blocks implemented with masks. Also, as of late, these libraries can be nested and layered. Sometimes there are various specific errors when adding them. Therefore, so that you don’t miss such events we have implemented and added to diagnostic window the corresponding information messages.

The external API in Engee now supports execution of long-running commands via the /external/command/eval method. This allows you to trigger the execution of a long-running command, get its identifier, and periodically poll the execution status.

More information about the external API is available in the documentation: External software interface for accessing Engee.

Atomic Subsystems are now supported for Verilog code generation. In the generated code, an Atomic Subsystem becomes an independent Verilog module in a separate file:

The easiest way to verify generated Verilog code is through automatic block generation C Function, as described in documentation. For advanced users, the Icarus HDL simulator, which uses a different verification mechanism, is now available at the Engee command line. Look for demonstrations of working with Icarus/iverilog in the community.

Support Package for RITM The must be synchronised with the Engee version being used. Now in case of version mismatch (e.g. the support package is installed via engee.com and RITM is used in a closed loop Engee of another version) the model cannot be run on RITM. Contact tech support to get the support package for RITM for offline installation.