SDK for Integration & OEM support
Software Development Kit (SDK) and special tools for 3rd party integration are available for integrators and OEM partners to provide full flexibility over creating user-customized applications.
- Software integration- SDK based on Darim's hardware input sources
- Limitless integration possibilities
- Spider ActiveX SDK
- Spider Export SDK
- PTZ/Alarm plug-in (PTZA) SDK
- Spider File Storage (SPFS) SDK
For OEM Partners
Darim's significant manufacturing capabilities and broad application experience gives us a unique ability to tailor hardware solutions to satisfy demanding application requirements. Darim has developed custom hardware solutions for customers that have provided solutions for military, marine, traffic, public safety, process monitoring, and other applications.
Darim is also enabling its customers to incorporate the OEM products into a large number of products and market segments. VideoSpider OEM products are successfully utilized by third parties for developing products for the video surveillance and security market.
If you are interested in providing VideoSpider encoding cards, standalone multic-channel encoders and servers, and accessories to your customers on OEM basis, please contact info@darim.com or the regional office for more information.
Spider Software Development Kits (SDK)

To support OEM customers with programming experience, detailed SDKs are provided with guidance and examples on how to access, use, customize, and develop user-customized applications.
The latest SDK packages include:
Spider ActiveX SDK -- allows customers to create their own simple and sophisticated client software in fast and simple way for VideoSpider. The supplied documentation and samples VB, C#, C++ code illustrate remote camera control, live video monitoring, video storage management, playback of recorded video data and many other tasks commonly performed by client-side software in VideoSpider.
Spider Export SDK -- provides programmers with ability to obtain data directly from the VideoSpider Core service on the server side or SpiderClient software on the client in order to convert it into any desired format for later displaying, processing, sharing, etc.
PTZ/Alarm plug-in (PTZA) SDK -- enables SI/VAR customers to add support for their own PTZ controllers as well as Alarm sensor/Relay output interface modules. The goal of this SDK is to create a variety of custom plug-in modules for custom hardware connected to VideoSpider servers.
Spider File Storage (SPFS) SDK -- assists software developers in parsing the proprietary SpiderFile Storage (.SPFS) file format and the index file (.INFO) associated with it. This maybe required for the offline storage analysis, statistics, data extraction, conversion to different formats, etc.
Each of the SDK packages comes as a self-extracting ZIP archive containing all necessary documentation, C++ headers, sample C++ code and ready-to-compile project files for MicrosoftVisual Studio IDE. All of the above SDKs are available for self-study and evaluation at no additional cost.
SDK components for MPEG4 Encoding cards and Accessories Hardware
iSP4xx devices and SP416 SDK -- the libraries for interaction with the devices drivers set in the system; provide the user with uniform interface for using and controlling these encoding cards and devices.
Web-based video monitoring software (optional)
Since introduction of the iSpider.NEToption to the VideoSpider line of servers, the VideoSpider users have obtained a new opportunity to access their server systems through the Internet directly from the Internet Explorer web browser without any need to install and configure the Spider Client software. If you need to modify any of the pages provided by the iSpider.NET (for example, to perform localization into your languages), please refer to the users documentation provided with iSpider.NET installation package. The documentation explains the existing structure of the iSpider.NET default web site and lists all files which may be changed and replaced by users. Alternatively, OEM/SI customers may choose to develop their own Internet-enabled application software that would interact with iSpider.NET server via specially formed URL and HTTP protocol. Such an application would have to process the incoming control and image data in a fashion similar to the Internet Explorer and display result to the user.


