Obtain camera status for new cameras added to the system without reinitializing the 2018 R2 SDK.

MIP
, ,
1

The problem scenario is when using the SDK to receive camera status events, we are unable to obtain status changes from cameras that are recently added to the system. The only solution appears to be to reinitialize the SDK and resubscribe.

We don’t appear to be able receive camera events for new cameras. We would like to be able to receive status for cameras without interruption to existing hardware events for new cameras and their IO.

Is there something in the SDK that will allow us to subscribe to a camera that was added after detecting a configuration change?

2

Configuration updated sample might be interesting for you - https://doc.developer.milestonesys.com/html/index.html?base=samples/configupdate.html&tree=tree_search.html?search=configupdated

3

Thanks Rie. We have attempted to reload the configuration as it appears in the configuration updated sample.

The issue appears to be that once we have reloaded the configuration and we have identified the new camera, we still don’t receive any camera events for that GUID. It appears the code that watches for status change does not get refreshed. We have attempted to create a new SystemStatusMonitor to listen for CameraStateChanged events, but still don’t receive them for the new camera until after we have logged out and reinitialized the SDK.

This route is problematic because there becomes a small window that we may miss camera events every time we reload the configuration.

Is there something we are missing in the SDK to force the SystemStatusMonitor to refresh?

4

We are investigating currently and will be back with an update later.

5

New code has been implemented so that SystemStatusClient will automatically pick up newly added cameras. I verified the new code behavior with the SystemStatusClientConsole sample.

This change will be in the next release of the MIP SDK. MIP SDK 2020 R1 is expected to be released in February 2020.

6

Thanks for the update.

Is it possible to have this patched to the current release of 2017 R1?

Our customers have expressed a high urgency to resolve this as soon as possible with minimal chance for regression.

7

XProtect 2017 R1 is in its product life-cycle now under “Limited availability” and no fixes will be developed. See - https://www.milestonesys.com/support/resources/product-lifecycle/

Please note that for the issue you reported you do not require a new server version only a new MIP SDK.