CVMWrite3DCalibrator error -2147483629

Programming Questions C++ API
1

Hi, I try to calibrate my AT C5. I use the code snippet from the documentation:
[Metric DLL Reference: 3D Calibration (https://help.commonvisionblox.com/NextGen/14.0/cvb/metric/d3/daf/group___calibration3_d.html#ga4c87d54d448c38fc9e59fd3c2a2bf5fc)
I fail to save the calibration to json. I use:

 const char* calibFile = "SICalibration.json";
    if (auto error = CVMWrite3DCalibrator(calib, calibFile))
         return error;

The error is = -2147483629

Is it possible to cast CVC3DCALIBRATOR calib to something more meaningful as a void*?

2

please find the used code,rangeImage and cfg to reproduce this error here zip

Further Information: Win 10 , C++17, Visual Studio

3

Hi @Quiztus,

so far I was able to run you code using CVB 14.00.002 on Win10 x64 and save the resulting calibration file as json and txt-file. Which CVB version did you use?
I will try to get more information on the error code. Do you have full write access on your drive where you want to write the file to?

Note that using the CVMetric.lib is part of the “old” CVB C-API. The assemblies for the new CVB C-API can be found at %CVB%\Lib\C\cvb in you CVB installation folder.

4

I tried it on two different machines x64 with the 13.04.005 CVB version. I also tried the C# Gui in the Tutorials folder.
Where do I get your CVB Version?

error
error1893×1036 83.1 KB

5

Hi @Quiztus,

the problem appears to be that you are currently not using a CVB Foundation license. This will prevent you from saving calibrators using CVB Metric. Actually you should get a message box that gives a hint on missing licenses:
grafik

You can get a free trial license valid for 30 days using the CVB License Manager to test the functionalities of the Foundation Package:

grafik
grafik843×424 25.8 KB

There is also the option to acquire full Node Locked licenses or a dongle.
CVB 14.00.002 can be downloaded here, but will not solve the licensing issue:

6

Very sad that the error message is not more meaningful in that context. This error took me days. The warning arises during calibration creation, which actually works…