Skip to content

Changes and Fixed Issues in VisualApplets 3.2.0#

Connection to License Dongle#

  • Changed behavior of VisualApplets when connection to license dongle is lost: VisualApplets blocks user interaction but saving the current design is still possible. VisualApplets recovers from the blocked state when the license is established again. (8851)

Operators#

Scope#

  • The parametrization of operator Scope has been changed: The max. output image width is now independent of the max. input image width. Note that a configuration where the output image width is larger than the input image width can cause a slowdown of fetching input data. (9315)

Blob_Analysis_1D#

  • The simulation for operator Blob_Analysis_1D has been improved.
  • The documentation for operator Blob_Analysis_1D has been improved. (7604, 7710)

Blob_Analysis_1D#

  • The operator Blob_Analysis_1D has been enhanced and can handle empty frames now. (7711)

Blob_Analysis_2D#

  • The documentation for operator Blob_Analysis_2D has been improved. (7710)

RemovePixel#

  • The simulation of operator RemovePixel now allows variable line lengths and empty lines. (6707)
  • The maximum image width of the output link will be bigger by 1x parallelism if parameter FlushCondition is set to EoF. (6707)

Register#

  • The simulation of operator Register has been fixed. The simulation can now handle images with variable line lengths and/or empty lines. (In earlier versions: When the input image line was shorter than the input image width and the first 2 pixels in the following line were removed, the 2nd pixel in that line contained a wrong value in simulation. This has been fixed.) (9210)

SplitImage#

  • The simulation of operator SplitImage has been fixed. The simulation can now handle splitting images with variable line lengths and/or empty lines. The biggest line in each image defines the image width. (9212)

SampleDn#

  • The simulation of operator SampleDn has been fixed and works correctly now also with sampling factors 2n.

PixelReplicator#

  • Operator PixelReplicator has been fixed and works correctly again also in 0D format (image protocol VALT_IMAGE0D).

IntFieldParamReference#

  • Operator IntFieldParamReference now also handles references to unsigned integer (UINT) fields. (In earlier versions, an error message occurred at loading a design containing an instance of IntFieldParamReference with a reference to a UINT field. Fixed.) (9361)

StreamAnalyzer#

  • Calculation of DataRate in operator StreamAnalyzer works correctly now. (In earlier versions, when the data width of the input was more than 8 bit, a multiple of the pixel rate was displayed. This has been fixed.) (9328)
  • The measuring of IdleFraction works correctly now. Cycles during which no data is moved through the pipeline because it is blocked are not added to the idle count any more. (In earlier versions, operator Streamanalyzer provided a wrong IdleFraction. This has been fixed.) (9329)

DynamicROI:#

  • Operator DynamicROI outputs the correct line length again under all circumstances. (In versions 3.1.x, the operator output the wrong line length under specific circumstances. This has been fixed. (7722)

Parameters Library#

  • The error checking of referenced parameter names in formulas has been improved. (8279, 8970)

    For example, if you re-name a referenced module (and thus the reference parameters in the referencing module get undefined) you get an according warning message immediately.

Custom Operators#

  • The memory access of custom operators has been fixed. (9151)

eVA Designer#

  • In eVA Designer the list of available formats for an ImgIn or ImgOut operator could get inconsistent with the list of formats of the corresponding interface port when such a format was modified or removed. This has been fixed. When an eVA platform description is opened, possible format conflicts get resolved automatically. (9164)

Automatic Bandwidth Analysis#

For VisualApplets 3.2, the automatic Bandwidth analysis function has been de-activated. Due to a continuous expansion of the VisualApplets functionality (new operators, new hardware platforms, hardware-specific memory handling), the initially implemented bandwidth analysis function gradually ceased to deliver reliable results.

In practical applications, the throughput rate often depends on the actual image content and the timing. In VisualApplets' automatic bandwidth analysis, both these aspects had not been factored in.

As practice shows, the bandwidth is generally monitored and calculated by the developer during the design process. To support the developer in calculating, VisualApplets now displays the maximal data throughput rate for each link (optional display via on/off button).

User Library#

  • Creating a protected user library element which contains modules with a float field parameter works correctly now. (In earlier versions, this lead occasionally to a program crash. This has been fixed.) (9264)
  • Saving a protected user library element that contains integer field parameters with negative coefficients works correctly now. (In earlier versions, during saving of a protected user library element, negative coefficients of integer field parameters got lost (e.g., FIRoperatorNxM). This has been fixed.) (9252)
  • Saving an instantiated user library module that is located within a hierarchical box to a user library: Saving works correctly now also when the output of the module is connected to an output node of the hierarchical box and a simulation module is connected to that link. (In earlier versions, this could cause a crash of VisualApplets. Fixed.) (9246)

Miscellaneous#

Adding/Removing Module Ports#

  • Adding and removing ports of instantiated modules works correctly now. (In earlier versions, in some situations adding or removing ports of instantiated modules could cause a crash of VisualApplets. This has been fixed.) (9304)
  • The mechanism for propagating link parameter changes through the design has been improved. (8874)

Detection of Vivado Version#

  • VisualApplets now reliably detects the Vivado version. (In earlier versions, in some situations VisualApplets could not detect the Vivado version. In particular this happened when Vivado returned warning messages because of improper definition of environment variables. This has been fixed.) (9099)

Other Changes#

All other changes compared to the previous version of VisualApplets are listed in section New Features.

Back to top