Version 14.1 (March 2026)

Importing comments to new containers

  • Comments can be added to EHANDBOOK containers to enrich the documentation.

  • Comments can be imported to other containers. The import ensures that no comment gets lost, even though the containers might have changed.

Container-Build

HTML Container Report

A new HTML-based log report is generated by default after container creation, providing a comprehensive view of container information, health metrics, and detailed logs. It enables easy analysis of errors, warnings, broken images, and affected documentation units with search and filtering capabilities.

For details please refer HTML Container Report section.

Introduced support for exposing the Constant value of Simulink Constant blocks as a mask parameter in EHANDBOOK. With the mask parameter name set to Value, the block becomes interactive, allowing users to view the configured value in a label popup and search for it.

Support for MATLAB 2025b Models in EHB

EHB now supports models created with MATLAB 2025b. As part of this update, compatibility with applications and toolbox has been verified, rendering behavior for new blocks has been validated, and mask image generation scripts have been updated accordingly. New blocks introduced in MATLAB 2024b and 2025b have been analyzed and are being supported to ensure improved integration with EHB.

Current limitations:

The following blocks are currently not supported:

  • For 2024b

    • simulink/Matrix Operations/Array Processing Subsystem

    • simulink/Matrix Operations/Expand Scalar

    • simulink/Matrix Operations/Pixel Processing Subsystem

    • simulink/Signal Routing/Variant End

    • simulink/Signal Routing/Variant Start

  • For 2025b

    • simulink/User Defined Functions/Python Code

Support for Removing Broken Images in Directory-Based Products

Extended support for hiding/removing broken images to directory-based products, enabling consistent behavior across product types using -DremoveBrokenImageForViewName in .ini file.

Improved Function Instance Naming for C-Code

Updated the naming convention for multiple calls to the same function within a C-Code model. Previously, repeated function calls were numbered using parentheses (for example, setClearTopologyError (3)), which could resemble function calls with arguments in C code.

This enhancement introduces a clearer naming format using underscores (for example, setClearTopologyError_3), following the pattern <function_name>_<count> to improve readability and avoid ambiguity.