操作系统

更正了在为 VF 输入 "启用 "使用 VA 变量时内存区域计算中的错误。

错误描述：在使用 VA 变量作为 "启用 "数据源的读码器配置中，错误地用其他输入的值覆盖了值；出现了各种组合，例如，"Alignment "的值被写入 "NumSearchMax "或 "TestExecute "被写入 "Timeout"。错误发生在 mapp Vision 人机界面应用程序中。不排除在其他将输入 "启用 "与 VA 变量相连的视觉功能中也会出现类似情况。

纠错：内存分配错误已得到纠正。

解决方法：如果视觉功能输入 "启用 "使用了 VA 输入，则不会出现该错误。

损坏的 VP 存档可能会妨碍摄像机的成功运行。

错误描述：如果损坏的 VP 存档从控制器传输到摄像机，则摄像机将保持状态 "0x0200 0000"，并在日志中记录错误 -1045168088 "任务 4 中的内部错误，错误代码：9." 记录在日志中。

错误更正：在操作系统中实现了对损坏的 VP 存档的处理，从而可以无问题地处理不完整的数据。

解决方法：没有已知的解决方法。

核心

在配置步骤处于活动状态时过早退出 mapp Vision HMI 应用程序可能导致无法访问摄像机。

错误描述：如果配置不利，执行视觉功能或教入模型等配置步骤可能需要更长的时间。如果在此状态下尝试通过刷新浏览器返回功能强大的 mapp Vision HMI 应用程序，则可能无法加载图像。

纠错：现在，当过早退出 mapp Vision HMI 应用程序时，视觉组件内部也会等待尚未完成的配置步骤的执行。在此期间，mapp Vision HMI 应用程序无法重新连接到视觉组件。

解决方法：由于每个配置步骤总是已完成，因此应等待完成。

功能

设置超时时错误信息充斥机器视觉日志

错误描述：如果应用程序在视觉功能（如读码器、匹配或 OCR）的循环超时输入上使用设定值触发图像处理，则可能导致机器视觉日志出现"-1044530232：视觉功能'{VisionFunctionInstanceName}'，在执行 VF 时发生超时 "的错误信息。

错误纠正：该错误信息不提供任何明显的附加值，现在已不再发出。

解决方法：无解决方法。

帮助

在大型 POWERLINK 网络中，摄像机操作系统更新时间过长

错误描述：如果摄像机所在的 POWERLINK 网络中站数相对较多，导致周期时间较长，则由于可用的异步带宽较低，摄像机操作系统的任何更新都可能需要相对较长的时间。这一点在自动化帮助中没有充分说明。

纠错：更新了 mapp Vision 自动化帮助中的 "摄像机更新 "部分，以更清楚地指出这种情况并描述可能的解决方法。

解决方法：要更新摄像机操作系统，首先将模块连接到另一个异步带宽更高的较小的 POWERLINK 网络。更新完成后，摄像机模块就可以重新在实际网络中使用了。

图像宽度和水平偏移的四舍五入行为

错误描述：如果图像采集配置的图像宽度或水平偏移值（ImageWidth、ImageOffsetX 或 LineWidth、LineOffsetX（带活动线条传感器））不能被 32 整除，则由于技术原因会四舍五入为 32 的倍数。这在自动化帮助中没有充分说明。

纠错：在 mapp Vision 的自动化帮助中更新了图像采集的参数说明，并添加了常见问题部分 "图像部分 - 参数调整"。

解决方法：始终将值配置为 32 的倍数。

使用 NetTime 正确触发图像采集

错误描述：如果使用 NetTime 触发图像采集，且未考虑摄像机或外部光源模块的最小响应时间（取决于 POWERLINK 网络拓扑结构和各种网络设置），则可能会出现曝光不正确的情况。自动化帮助》中对这一复杂主题的描述不够充分。

错误更正：mapp Vision 的自动化帮助中的 "使用 NetTime 触发图像采集 "部分添加了有关 PLK 文档的信息和 "输入和输出数据的定时 "小节。此外，"经过验证的简单公式 "部分还为用户提供了在常用 POWERLINK 设置下最小响应时间的简单计算说明。

解决方法：无解决方法。

人机界面

短暂退出并重新打开 mapp Vision HMI 应用程序并不总是重置所有值。

错误描述：在 mapp Vision HMI 应用程序中短暂退出并重新打开视觉组件页面后，所有先前设置的临时设置并不总是如预期那样被丢弃。

错误纠正：由于改进了内部流程，在这种情况下，活动机器 VA 现在总是重置为上次保存的版本。这也会影响 FlashColor 等强制值。

解决方法：在 mapp Vision HMI 应用程序中退出视觉组件页面后，首先等待相关的清理过程（日志信息），然后再重新打开相同的视觉组件页面。

操作系统

使用 3.5 和 5.3 百万像素摄像头和最高质量级别时出现 JPEG 编码器错误

错误描述：如果在 350 万或 530 万像素摄像机上使用高于 85 质量级别的编码过程，则摄像机上的 JPEG 编码器可能会触发故障事件。

错误纠正：由于进行了内部修正，JPEG 编码器现在可以处理所有质量级别，即使在使用 350 万或 500 万像素摄像机时也不会出现问题。

解决方法：向相机索取 JPEG 质量级别低于 85 的压缩图像，或不使用 JPEG 压缩。

Operating system

Error in the memory area calculation when using a VA variable for VF input "Enable" has been corrected.

Error description: In Code Reader configurations with a VA variable as the data source for "Enable", values were mistakenly overwritten with values from other inputs; various combinations occurred, for example the value of "Alignment" was written to "NumSearchMax" or "TestExecute" to "Timeout". The error occurred in the mapp Vision HMI application. It cannot be ruled out that similar effects may also occur in other vision functions that have input "Enable" linked to a VA variable.

Error correction: The error assigning memory has been corrected.

Workaround: The error does not occur if a VA input is used for the vision function input "Enable".

A damaged VP archive could prevent the successful operation of the camera.

Error description: If a corrupted VP archive is transferred from the controller to the camera, the camera remains at status "0x0200 0000" and error -1045168088 "Internal error in job 4, error code: 9." is entered in the logbook.

Error correction: Handling for corrupted VP archives has been implemented in the operating system, which allows for problem-free handling of incomplete data.

Workaround: There is no known workaround.

Core

Exiting the mapp Vision HMI application prematurely while a configuration step is active could result in the camera becoming inaccessible.

Error description: If the configuration is unfavorable, a configuration step such as executing the vision function or teaching-in a model may take longer. If an attempt was made in this state to return to a functional mapp Vision HMI application with a browser refresh, it was possible that no image could then be loaded.

Error correction: The vision component now internally also waits for execution of a configuration step that has not yet been completed when exiting the mapp Vision HMI application prematurely. The mapp Vision HMI application cannot reconnect to a vision component during this time.

Workaround: Since each configuration step is always completed, completion should be waited for.

Functions

Flooding of the machine vision logbook with error messages when a timeout is set

Error description: If applications triggered image processing with a set value on the cyclic Timeout input of a vision function (e.g. Code Reader, Matching or OCR), this could result in flooding of the machine vision logbook with "-1044530232: Vision function '{VisionFunctionInstanceName}', a timeout occurred during VF execution" error messages.

Error correction: The error message, which does not provide any noticeable added value, is now no longer issued.

Workaround: No workaround available.

Help

Lengthy update of the camera operating system in a large POWERLINK network

Error description: If a camera is located in a POWERLINK network with a relatively large number of stations and a resulting high cycle time, any update of the camera operating system may take a relatively long time due to the low available asynchronous bandwidth. This was not sufficiently described in Automation Help.

Error correction: Section "Camera update" in Automation Help for mapp Vision has been updated to more clearly point out this situation and to describe possible workarounds.

Workaround: To update the camera operating system, first connect the module to another, smaller POWERLINK network with higher asynchronous bandwidth. After the update is completed, the camera module can be used in the actual network again.

Rounding behavior for image width and horizontal offset

Error description: If image acquisition is configured with values for image width or horizontal offset (ImageWidth, ImageOffsetX or LineWidth, LineOffsetX with active line sensor) that are not divisible by 32, rounding to multiples of 32 occurs for technical reasons. This was not sufficiently described in Automation Help.

Error correction: The parameter descriptions for image acquisition have been updated in Automation Help for mapp Vision, and FAQ section "Image section - Parameter adjustments" has been added.

Workaround: Always configure the values as multiples of 32.

Triggering image acquisition correctly with NetTime

Error description: Incorrect exposures may occur if image acquisition is triggered with NetTime and the minimum response times of cameras or external light modules that depend on the POWERLINK network topology and various network settings are not taken into account. This complex topic was not sufficiently described in Automation Help.

Error correction: Information about PLK documentation and subsection "Timing of input and output data" have been added to section "Triggering image acquisition with NetTime" in Automation Help for mapp Vision. Section "Proven simple formulas" also provides the user with simple calculation instructions for the minimum response times with common POWERLINK settings.

Workaround: No workaround available.

HMI

Briefly exiting and reopening the mapp Vision HMI application did not always reset all values.

Error description: After briefly exiting and reopening the vision component page in the mapp Vision HMI application, all previously set temporary settings were not always discarded as expected.

Error correction: Due to improved internal processes, the active machine VA is now always reset to the last saved version in this situation. This also affects forced values such as FlashColor.

Workaround: After exiting the vision component page in the mapp Vision HMI application, first wait for the associated cleanup process (logbook messages) before reopening the same vision component page.

Operating system

JPEG encoder errors with 3.5 & 5.3 MP cameras and highest quality levels

Error description: The JPEG encoder on the camera could trigger a fault event if quality levels of the encoding process above 85 were used on 3.5 or 5 megapixel cameras.

Error correction: Due to internal corrections, the JPEG encoder now handles all quality levels without problems, even with 3.5 or 5 megapixel cameras.

Workaround: Request a compressed image with JPEG quality level less than 85 from the camera or do not use JPEG compression.