Change log of version 2.2.10.35

Upgrade information from installations earlier then 2.2.10.26

Based on the project experiences over the last decade, the internal runtime database of vimaccOA (named “vimacc Config”) has been general re-engineered for better runtime performance and system stability – also results in an overall improvement of the redundancy features of vimaccOA.

Reworking the IPC protocols of the “vimacc Config” harms, first time ever, the compatible with earlier versions of vimaccOA - NOT the compatible with any version of WinCC OA. Cause of this any upgrade of distributed vimaccOA installations, from versions earlier then 2.2.10.26, needs additional plannings to keep operations without any general downtime. Please contact the WinCC OA VIDEO experts you trust for further information and support (keyword “vimacc ConfigNG”).

Additional information regarding feature “Stream cloning”

The feature of “Stream cloning” (introduced in 2.2.10.30) needs an update of the internal feature lists in vimaccOA. Please contact support for further guidance for activation of this feature.

New Features (compared to 2.2.10.33)

  • none

Changelog (compared to 2.2.10.33)

VideoManager & Ctrl-Libraries:
  • Fixing issues with hiding members from base class in VO_Scenario and VO_Sequence.

  • Fix handling with object.device.name, regarding the used Display names in vimacc Workstation.

  • Fixing several stability and performance issues regarding the Display-DIST functionality.

vimacc-Core
  • Fixing some protocol issues with several ONVIF Devices, cause by different WSDL-Version.
  • Update of OpenSSL to 1.1.1v
  • Correction of version info for FFMPEG to 4.2.9 in vimacc About-Dialogs. FFMPEG-Version was updated in release 2.2.10.33.
  • Bosch implementation in AccVimaccInterface: FIXED stuck communication, potential crashes & ASSERT messages in log.
  • AccVimaccInterface: Fixing several crashes, when many device connections getting broken and having several retries.
  • Session handling: Fixing several issues with internal timers, which results in leaked objects, causing high CPU load in AccVimaccInterface.
  • Fixing issues in AccVimaccInterface for the provisioning of playback timelines (used in WinCC OA VIDEO through the VideoManager), reseting state when connection to AccVimaccServer is closed. Otherwise, session was not re-established and timeline info was no longer updated.
  • AccVimaccCommander: implemented support for disabling feature checks via OTP (One-Time-Password) useful during remote support
    1. Run AccVimaccCommander on the customer computer outside the Accellence AD domain and double click on the Accellence logo in the top right corner to open the SUPUS dialog.
    2. Run AccVimaccCommander on any computer that is member of the Accellence AD domain, double click on the Accellence logo in the top right corner, enter the SUPUS Challenge Code shown on the customer computer.
    3. On the customer computer, enter the SUPUS Response Code shown on the Accellence computer in order to disable the feature checks.