BODY WORN SYSTEM FIRMWARE RELEASE NOTE ====================================== Products affected: W100, W800 Release date: 2021-03-24 Release type: Production Firmware version: 10.4.0.3 Preceding release: 10.4.0.2 Languages: English, German, French, Spanish, Italian Compatibility: AXIS IP Utility 4.14 or above, AXIS Body Worn Assistant, AXIS Camera Station 5.33 or above, AXIS Case Insight, Milestone XProtect 2020 R1 + AXIS Optimizer Body Worn Extension 1.0.55 or above, Genetec Security Center 5.9.2.0 or above, Genetec Clearance, Google Chrome ------------------------------------------------------------------------------------------------------------------------- Corrections in 10.4.0.3 since 10.4.0.2 ======================================= * Solved: System controller not displayed correctly when docked causing a conflict. Corrections in 10.4.0.2 since 10.4.0.1 ======================================= * Solved: Daylight saving time causing recordings to be one hour off in regions that have switched to summertime. New features in 10.4.0.1 since 10.2.0.3 ======================================= * See "What's new in the latest release?" in the user manual. Other updates in 10.4.0.1 since 10.2.0.3 ======================================= * Improved graphical design in Body Worn Manager (BWM). * Indicate in BWM if a BWC is docked on another system controller in the system before it finishes offloading recording on the system controller it was docked on. * LEDs on the BWC pulse to show ongoing or progressing activity instead of flashing. * Information about who has reviewed a recording via Body Worn Assistant and when can be downloaded from Axis Case Insight when downloading the recording file. * Proxy server is no longer checked by default in setup wizard. * Performance of uploading recordings to Genetec Security Center is improved significantly. * Solved: Timestamp in BWS system report is one hour behind real time. * Solved: Sometimes the file transfer status shows a recording is still on the BWC although it's already transferred to the content destination. * Solved: Logging into an extension system controller in Chrome takes 2 tries every time. * Solved: Built-in help in BWM is not always available when system controller is offline. Corrections in 10.2.0.3 since 10.2.0.2 ======================================= * Improved system stability. * Body Worn Manager (BWM) provides information if a BWC has not finished offloading recording on one system controller before it's docked on another system controller in the same system. * Solved: Sometimes video clips shorter than 1 second could get stuck in the camera. * Solved: Sometimes cameras can lose connection to the system controller and be shown as locked in BWM temporarily. * Solved: When upgrading some early produced system controllers directly to 10.2.0.2, they may have problem to connect to the content destination. Corrections in 10.2.0.2 since 10.2.0.1 ======================================= * Solved: An unregistered BWC with older firmware shows up underneath "New" section in Body Worn Manager and then disappears during firmware upgrade until after the firmware is upgraded. If the end user "Add" the BWC before the firmware is upgraded, it needs to be done again after that. * Solved: In a large system with many cameras, sometimes BWCs fail to register when connected via extension system controllers to the main system controller. * Solved: In a large system with hundreds of users, sometimes Body Worn Manager (BWM) can become slow and unresponsive. New features in 10.2.0.1 since 10.1.0.1 ======================================= * Self-assign camera assignment: It lets the camera user assign and pick up any available body worn camera using an RFID tag. This feature allows different work shifts to share cameras. Self-assign camera assignment mode is accessed through the system setup wizard and is available after a system reset. The RFID reader required for this setup is External RFID Card Reader 125kHz + 13.56MHz with NFC (USB) provided by 2N. * Possibility to limit access to recordings in AXIS Body Worn Assistant. You can turn it on or off in the camera profile in Body Worn Manager (BWM). * Notification of new BWS features after a firmware upgrade. * Access to user manual and system reports during setup wizard. Corrections in 10.2.0.1 since 10.1.0.1 ======================================= * More informative feedback when configuring content destination. * Camera will shut down automatically at a high temperature (over 65 celsius) to prevent file corruption. * Solved: Sometimes extension system controller’s firmware is not upgraded until after a reboot. New features in 10.1.0.1 since 10.0.3.1 ======================================= * Support for mobile app AXIS Body Worn Assistant. * System configuration information is included in BWS system report. Corrections in 10.1.0.1 since 10.0.3.1 ======================================= * Further improvements in time sync between BWCs registered in the same system, allowing for synchronised playback on recordings from different BWCs. New features in 10.0.3.1 since 9.75.1.1 ==================================== * W800 with access to axis.com will get notification when a new firmware is available. * Improved time sync between BWCs registered in the same system, allowing for synchronised playback on recordings from different BWCs. Corrections in 10.0.3.1 since 9.75.1.1 ==================================== * "System reset" is now under "Support" menu to make it more visible in BWM. * In previous versions, the BWC did not always notify the end user in case of a malfunctioning recording capability. Now it gives an operation error, operation status led in amber, if this occurs. * During system setup wizard, when there is no NTP server in place and the user does not uncheck "NTP server" on the "Date and time" page, there is no error notification until the user arrives at the Summary page (The "Next" button is disabled and system setup can not be finished). Now it is required to set "Manual time" on the "Date and time" page in order to proceed. * Solved: If a BWC (or user) is removed from Body Worn Manager when there are recordings left on the BWC (assigned to the user), the recordings may not be transferred to the content destination. * Solved: Sometimes firmware upgrade fails during setup wizard and no immediate error message is given. * Solved: When using HTTPS to connect to Body Worn Manager and leaving the browser open on "Devices", Body Worn Manager will stop responding after a few days, although it is still possible to dock and undock BWCs as normal. The problem is gone after a reboot of the system controller. Corrections in 9.75.1.1 since 9.75.1 ==================================== * Corrected Axis critical vulnerability ACV-2020-100004. For more information please visit www.axis.com/support/product-security. Known limitations ====================== * When downgrading firmware, a system reset is required before the downgrade. * A camera user can only be paired with one holster sensor at a time. * Unholster detection is not available in Self-assign mode. * In Self-assign mode, if your system have multiple system controllers at different locations, you may be assigned a camera at another location. * In Self-assign mode, it is not possible to read RFID card data when BWM is opened in the embedded browser in ACS. * It is not possible to remove a camera if connection to content destination is broken. * Connection status on the content destination page under "Settings" is not refreshed automatically after a new connection file is uploaded. A page refresh solves the problem. * The list of BWCs in BWM are not always complete after firmware is upgraded in BWM. Sometimes only the BWCs that have not been upgraded are listed. A refresh on the page will solve the problem. * Recordings may not be transferred to the content destination if there is not enough licenses on the content destination. * If a BWC has not finished offloading recording on one system controller, it can't be used on another system controller in the same system until the offloading is finished. * When a BWC is undocked immediately after it is removed, the BWC can get stuck in the "unregistering in process" state in Body Worn Manager. The problem is gone when docking the BWC again and waiting for it to show underneath "New" section in Body Worn Manager. * If a BWC's license is deactivated in Genetec Clearance, it's not possible to remove it from BWM. Reactivating the license in Clearace will solve the issue. * When using Security Center as the content destination, if the time difference between system controller and Security Center is bigger than 15 seconds, a default user named by the camera's mac address is created. All recordings created with that BWC will be uploaded to the default user. * Putting BWC back to back against a radio device can cause black screen and a flickering image, which can take a while to recover. The same thing won't happen if they are placed side by side.