Integracion de BWC Vipro

MIP
, , ,
1

351 / 5,000

I’m developing a project to integrate Vipro BWCs into the Milestone platform. These cameras have 3G/4G connectivity to transmit to a CMSServerV6 server. The CMSServerV6 server also has an API that manages all camera operations.

What recommendations can you give me to achieve this goal?

2

I recommend that you use the Driver Framework to develop a driver for the BWC.

https://doc.developer.milestonesys.com/mipsdk/index.html?base=gettingstarted%2Fintro_driverframework.html&tree=tree_1.html

https://doc.developer.milestonesys.com/mipsdk/index.html?base=samples%2FPluginSamples%2FDemoDriver%2FREADME.html&tree=tree_1.html

I guess that the driver could either enable communication directly with the BWC or the CMSServerV6 server. I don’t think I have sufficient information to evaluate what is possible or optimal.

I have an idea that in most BWC / Milestone integrations I have seen the video data is transferred when the BWC is docked after use, and then the edge retrieval functionality, that the driver framework also supports, is used.

I hope this is a starting point for you, note that my advise is very general not knowing the camera or the server you mention.

3

Dear greetingsI

am currently developing a driver for the integration of Vipro BWC into Xprotect VMS. We are in the deployment stage and wanted to know if there is any guide on where the compiled project files should be deployed so that the Xprotect Management Client can load them. I am referring specifically to the .dll and .def files.

4

The description of this is clearest in the documentation for the sample. I will quote it here:

To deploy the Demo Driver:

  • Stop the Recording Server Service
  • From project build output, copy the files DemoDriver.def and DemoDriver.dll (and DemoDriver.pdb if debugging) to %ProgramFiles%\Milestone\MIPDrivers\DemoDriver\.
  • Start the Recording Server Service

You should do the same for your driver plugin as here documented for the sample Demo Driver.

PS. For better understanding: It is not the Management Client that load the driver plugin, it is the Recording Server service. The Management Client Hardware Add Wizard get the information from the Recording Server