Known Issues

Container-Build

General

Issues with model path containing special characters

Screenshots and model linking will be missing for Simulink subsystem names containing back slashes or forward slashes. Model linking will be missing for Simulink subsystem or ASCET hierarchy names containing dots.

MATLAB Simulink

Simulink blocks with "Show Block Name" option set to "Auto" are always shown

For Simulink blocks when "Auto" mode is on, block names are always shown. This behavior might be different when compared to Simulink.

Display issues with Simulink Annotation blocks

Simulink Annotation blocks with rich text formatting might look a bit blurred or fuzzy in the documentation when the used text font is small or annotation block is generated without enabling rich text extraction option.For details refer Simulink rich text annotations as text When styling is applied for the text of Simulink annotation blocks, the displayed text might have different appearance. There are certain limitations in the rendering of the following stylings:

  • Right alignment of text

  • Table appearance

  • Hidden text due to overlapping whitespaces

PDF

PDF generation failure

Provide output directory name and path (-o option) case sensitive that is in sync with OS. If case insensitive, PDF generation fails.

Navigator

This section describes the set of known problems of the released version of EHANDBOOK-NAVIGATOR 12.4.

  • We identified an issue in EHANDBOOK-NAVIGATOR version 12.1.0 that affects containers or projects containing comments without content (EHANDBOOK containers). This issue can cause EHANDBOOK-NAVIGATOR’s change detection functionality to malfunction, rendering it unusable for these containers/projects. In such scenarios, neither continuing to use nor terminating EHANDBOOK-NAVIGATOR is possible. This issue was introduced in version 12.1.0 and has been resolved in the subsequent release, version 12.1.1.

  • In ASCET V6 based interactive models, EHANDBOOK-NAVIGATOR does not show "Start" and "History" states for state machines.

  • When "Invisible view" info is applied to a state, EHANDBOOK-NAVIGATOR does not show the transition attached to the state.

  • Formulas text is not selectable/searchable.

  • Combination of styled and normal text are not searchable in Local Search. Example: Search strings containing bold and normal text does not yield search results.

  • EHANDBOOK-NAVIGATOR will hang if connection to INCA is not cleared properly.

    • In such a case, follow the procedure for disconnecting from INCA as indicated in the User Guide document.

  • Highlighting of connected elements for larger number of ports requires more RAM and time.

  • EHANDBOOK-NAVIGATOR shows a different icon for group tables in comparison to ASCET.

  • Interaction with topics having large textual content might take more time (eg. ’Find in Current Tab’).

  • Variable icon is shown in label popup for "Service" type labels .

  • Signal flow highlighting is not propagated properly for "Self Class" block in collapsed state.

    • Trigger signal flow highlighting with "Self Class" block in expanded state.

  • When using Find in EHANDBOOK File(s) with term containing punctuation characters, scrolling and highlighting of search hit is not done. Ex: <LabelName.Number> (Ex: Opm.3)

    • Use local search post topic opening or open search hits found for parameter/variable type.

  • When label amendment for hierarchies is performed, the following issue may occur: Ex: Open interactive model might not get directed to the appropriate level in interactive model in some cases.

  • Annotated values and labels on interactive models could be overlayed by blocks in default layout.

    • Alternatively, switch to auto layout.

  • Rendering for some interactive blocks across different versions of Simulink might have a different representation. (Ex: The EHANDBOOK Container is generated using different versions of MATLAB).

  • Setting windows system scaling factor to greater than 100% might result in blurry text and images in textual documentation.

    • Alternatively, switch windows system scaling factor to 100% for all monitors.

  • When a text occurs multiple times in the same state model, Find in EHANDBOOK File(s) highlights all of them in a search hit.

  • Sometimes Navigate in action does not bring blocks to the focus area.

    • Alternatively, click Fit to View from the status toolbar to bring them to focus.

  • Usage of unsupported Simulink toolboxes might result in corrupted interactive models.

  • Usage of web fonts in EHANDBOOK container configured via commonltr.css file is not supported for EHANDBOOK Containers generated using versions older than 8.3.

  • In Simulink, Inport blocks can be duplicated to so-called InportShadow blocks. InportShadow blocks are not yet fully supported in EHANDBOOK. For example, the inner label (typically a number) is missing. Furthermore, no virtual connections are established, and highlighting dependencies is not supported.

  • When adjusting the size or switching editors in EHANDBOOK-NAVIGATOR, viewers can temporarily go black.

  • When EHANDBOOK-NAVIGATOR is connected to INCA for live measurement, there could be a significant performance degradation leading to unresponsive UI.

  • In an ASCET-DEVELOPER based interactive model, the State behavior text could overflow from the State block.

    • Alternatively switch to auto layout.

  • A screenshot based on ASCET-DEVELOPER state machine could get clipped if transitions of the state machine extend outside the state or region.

  • Auto-correction of duplicate groups, functions, measurements, and characteristics for A2L files with include statements is not supported.

  • Simulink models having Pixel Icon Units may not be rendered properly.

  • Dangling virtual connections might be visible in the interactive model in case of a minimized application window.

    • Alternatively, performing some navigation or re-layouting operations would fix the interactive model.

  • Visualization of Map graph in Label pop-ups might not work on a Windows 11-Virtual machine environment.

  • Self-loop connections in interactive models may sometimes overlap on other parts of the model.

  • For attachments, some icons in the Document Explorer might have a black background.

  • Expand icons in interactive models may not be clickable in default layout when other blocks/labels overlap.

    • Alternatively, blocks can be expanded using the context menu.

  • Model Explorer and Model Navigation Bar may show entries without labels when blocks do not have a name in the source model.

  • Focus may sometimes toggle between the label popup window and the main EHANDBOOK-NAVIGATOR window.

    • Alternatively, click on some part of the main EHANDBOOK-NAVIGATOR window.

  • When opening multiple model editors showing very large models EHANDBOOK-NAVIGATOR could stop working properly due to memory consumption.

    • Closing tabs can restore the application.

  • Subsystems which only contain static documentation text might be displayed wrongly.

    • In case the subsystem appears empty switch from auto layout to default layout.

  • Open model link might open the wrong location in case there are multiple blocks with the same name.

  • In case of Duplicate functions in the container, Bookmarking model will always open first function in the container and also bookmarks all function with same URI.

  • For Simulink blocks with mask images and icon transparency set to transparent the mask image might not be shown.

  • Comparing containers generated from an A2L is not supported and may lead to errors.

  • When subchapter have different names and marked as removed/added in compare tree, the content might be showing as modified.

  • When navigating interactive models using the model explorer or navigation bar, the zoom factor is kept, but the content might not be readable.

  • In the Code viewer, local search does not highlight all matching occurrences and therefore show lesser number of matches

  • When comparing containers, some compare tree nodes even when marked as modified may not show any difference when viewed in split-screeen viewer.