Pelco Developer Network (PDN)

VideoXpert 3.0 SDK Installation

Where to Download installer and how to Install VxPRo SDK 3.0?

Please, there is no link to any proper installer of the SDK 3.0.

How a developer could have concurrently SDK2.x and SDK 3.x?

How is the process to get a license key for v3.x SDK?

Wrapper made for SDK2.x can be updated to SDK3.x by just copying new .dll and current Includes?

Reagards, Pablo.

Hello there, thank you for your post.

Many of your questions can be answered by exploring the site ... but I'll provide you with some links and information to help direct you:

Where to Download installer and how to Install VxPRo SDK 3.0?

Please navigate to the VideoXpert SDK page, and use the link to navigate to the VX SDK Download page. You will want to explore the Nuget download page and the GitHub Samples to explore which nuget package (set of DLLs) is right for your needs. There is no different VX SDK for connecting to a VideoXpert Pro system or VideoXpert Enterprise system -- it's the same VX SDK.

How a developer could have concurrently SDK2.x and SDK 3.x?

They shouldn't. This is strongly not recommended. VX SDK 3.X should be used with VX 3.X versions (and newer versions going forward). If you attempt to use older VX SDK versions to log into a newer VX system, the login requests will fail. Programmatically you can't get the version of VX prior to making calls to it using the SDK (SDK is needed to make the call to VX in the first place), so you should only use the SDK version that you need based on the VX system that you'll be connecting to. For this reason. I do not recommend attempting to concurrently use both SDK versions in a solution. You may need to have 2 separate versions or installers.

How is the process to get a license key for v3.x SDK?

Please reach out to contacts at Pelco Sales & Support, and they can communicate internally to departments in Pelco to obtain a license key.

Wrapper made for SDK2.x can be updated to SDK3.x by just copying new .dll and current Includes?

Unfortunately, no. There are code changes necessary, at the minimum to the login code used - a license string key must be provided using the new VX SDK when attempting to log in to a VideoXpert system. Depending on what other functionality that you're using, other additional updates may be necessary. I suggest exploring the changes by running Sample code and reading the PDF documentation.

Thank you for the answer.

As usual it's difficult to understand the strategic idea of Pelco about the SDK. v2.x version installs a VxSdk Key Generator that allows to directly create a Key that it isn't explained anywhere how should be used. But SDK 2.x works without it. v3.x has stated that requires a Key, and there is no mechanism to generate it, the only available old key Generator is not useful for it.

When in SDK 3.x page: http://pdn.pelco.com/content/videoxpert-sdk-related-downloads#sthash.U5kyB3pN.dpbs
If you click on VX SDK Use Cases, you are directed to code that seems to be v2.x, where the first example is not corresponding because it doesn't include the Key in loginInfo:

Login to a VideoXpert system
#include "VxSdk.h"
 
// Enter the VideoXpert login information
VxSdk::VxLoginInfo loginInfo;
VxSdk::Utilities::StrCopySafe(loginInfo.ipAddress, "192.168.1.1");
VxSdk::Utilities::StrCopySafe(loginInfo.username, "admin");
VxSdk::Utilities::StrCopySafe(loginInfo.password, "admin");
loginInfo.port = 443;
loginInfo.useSsl = true;
 
// Attempt to login to the system
VxSdk::IVxSystem* system = nullptr;
VxSdk::VxResult::Value result = VxSdk::VxSystemLogin(loginInfo, system);
 
if(result == VxSdk::VxResult::kOK) {
	// Successfully logged in
	// Delete system object
	system->Delete();
	system = nullptr;
}
else {
	// Unsuccessfully logged in
}

You should update the code example you give for users. The rest of it is correct or not? The "VxSDK v2.1 to v3.0.pdf" is only a comparison of headers, nothing else. It doesn't give any idea about what operative differences there are between versions.

Some time ago I downloaded from your site a "VideoXpertSDK-3.0.32-afb6e216.msi" that has some download problem because it doesn't install. It seemed to be "the real" installer of the SDK. Where is it nowadays? Do you currently consider the formal distribution of the SDK of a product the non-documented .dlls that the user has to browse in one example package?

It is incredible that as a vendor, Pelco forces its clients with needs of development to be code archaeologists... One spends more time trying to understand what Pelco conceptually did and where put the stuff, that developing the real software. And the great addition is that Pelco is never backwards compatible, excellent!

Thanks in advance. Regards, Pablo.