Source code of DemoDriverDevice

MIP
, , ,
1

Hi all.

I am trying to find source code of DemoDriverDevice in MIP SDK Driver Framework.

Where exactly, if possible, I can find the implementation?

Just to have the complete end-to-end sample to develop a custom Driver.

Thanks in advance.

BR.

2

Milestone has chosen not to publish this, it should be of little interest as you will always replace the demo device with something real, like a real camera which has its own specific communication form.

3

I can understand this choice. i’d have never asked for it if DFW platform has been well documented and explained.

Without wanting to argue, really, the assertion “Milestone is an open architecture” would let me think of an important support in using the SDK API.

However, let’s me say, I found a very gaunt and generic documentation and support even in the answers to the many questions that people asked in the forum.

Companies pay many licences and courses in order to use Milestone products however no important support has been provided in order to customize the infrastructure for specific aims. Milestone is becoming a de-facto standard in the VMS field and I think IoT, Lawful Interception and other fields are going to get as important as video surveillance stuff. In my case I don’t want to use commercial camera … I don’t need it. I want to develop my device and camera.

Unfortunately for some businesses, an open infrastructure is a mandatory requirement.

For example, I am doing a lot of efforts to understand the logic of the DriverSample, with no knowledge about how end-to-end communication works. In this way, maybe I will never be able to integrate new solutions.

But, I still hope technical support will be provided. :slight_smile:

Thanks a lot again,

BR.

4

Dear Lorenzo

Please be aware that the DemoDriverDevice is just a small application simulating a device made in order to make the DemoDriver more realistic.

The communication protocol between the device and the driver is very crude and has nothing as such to do with the DFW platform. Therefore we think that disclosing the ‘device’ code will just obscure the parts the DemoDriver was made to showcase, namely the usage of the DFW platform.

Regarding communication between a driver and a device that is entirely device dependent and thus any implementation we provided would without doubt not match any real device.

That said, we always stride to make our SDK and documentation better, so if there are specific parts you would like us to improve on please let us know.

And of course if you have specific questions regarding the DFW please don’t hesitate to post them on the forum and we will do our best to answer.

Best regards,

Peter Vergmann

Engineering Manager, MIP SDK & APIs team

5

Dear Peter,

thank you very much for you kind availability.

Of course, I’ll take advantage of your invitation to ask for specific technical topics.

Thanks again,

BR

Lorenzo.