This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Adding ONVIF/PSIA PTZ control to DM368 MT5 IPNC

Hardware: Leopardboard DM368 running Appro MT5 IPNC SDK V4.1

We need to add PTZ controls via ONVIF / PSIA interface. The code for ONVIF/PSIA is already in the SDK but there are no PTZ bits. Due to the level of complexity around ONVIF/PSIA I was wondering if anyone had experience of making changes/additions to the code and could offer any advice / experience on how's best to go about it.

With the amount of code present it's easy to imagine it could get very messy very quickly!

  • Hello,

    You can contact Silvan Labs (Third Party) who can help on this effort of PTZ implementation for ONVIF/PSIA

    Anyways, there is v5.1 released which is the latest, you might want to upgrade to this version

    Regards,

    Raghu

  • Hi Bob,

    You can mail me at nand (at) silvanlabs (dot) com. 

    Thanks,

    Nand

  • Are you saying that Silvanlabs developed/know about the ONVIF/PSIA stack that's in the IPNC reference design, or that if we give SilvanLabs a load of money they will sell us some other ONVIF/PSIA solution?

  • Hi Bob,

    The ONVIF stack in the IPNC reference design is developed by Silvan Labs. Currently the stack does not support PTZ features. If you want to extend the functionality to include PTZ, either you do it or you get it done by someone else (usually in exchange of money :) ). Since we have done most of it before, it will be easier to get it done by us.  That's all.

    Cheers,

    Nand

     

  • Hi Nand,

    If you are responsible for the ~300,000 lines of undocumented / uncommented ONVIF code in the SDK then I'm not in a hurry to buy your software, sorry.

    Also, this forum would be a rather poor place if all the answers were "pay someone else to solve your problem"... the idea of a forum is usually for people to help each other and share their knowledge.

    Now, I'm happy to do it myself, but given that the SDK includes much of the basic framework (BUT NO DOCUMENTATION) I was hoping to avoid duplication of effort by asking if those who had done it had any helpful advice. One of the reasons for spending $1000+ on an SDK was to speed up development and reduce the need to roll everything from scratch.