Problem using FLEX:V100r2 - no compatibility

[Matan]

Hello,

Our company has purchased new 10 X Naturalpoint new V100R2 cameras.
I try to use this camera with our application with both of drivers (1.3.037 or 1.3.034) but with no success
Camera readout screen is lighting but and\or application will crash or won�t response. (while successfully using retired V100 or C120 )
Do you have a better driver to use? One which support backwards compatibility? � (Please keep in mind it isn�t possible \ convenient to re-compile all our application version)

Our applications has several versions � and if I need to change our customer a camera to R2 � we will have a very problematic situation : to update source codes and compile this specific project (for every customer for every version).
Keep in mind that if I compile a version (which can be an old one) I must test it for the quality tests�

Please check and ask NaturalPoint R&D to support drivers with backwards compatibility.
Please ask them if they have a solution for our problem (I have just received 10 X R2 cameras)

My company SMART S has purchase approximately 60 cameras (FLEX:C120, FLEXV100, FLEX:V100R2)
In the future please update your customer when your product is going to be retired.
At the past FLEX:C120 was retired with no notification same with our current problem with FLEX:V100.

Regards
Mat

[VincentG]

Your aqpplication is built using the older SDK (not the 1.3.037 beta 1 software)?

[Matan]

Yes,
Building source code with 1.0.037 SDK - will work with V100r2 camera but won't work with old V100 camera.
Please keep in mind that this solution is problematic with our costumers and version support.
What does NaturalPoint solution for a customer which has an Arena system, rigd body and new tracking tool...with old V100 cameras and wants to upgrade all cameras to new V100r2 cameras?

Our applications has several versions � and if I need to change our customer a camera to R2 � we will have a very problematic situation : to update source codes and compile this specific project (for every customer for every version).
Keep in mind that if I compile a version (which can be an old one) I must test it for the quality tests�

Is there a way when customer gets anew V100r2 camera to update only NaturalPoint drivers so he will be able to use our application with new V100r2 camera ?

[VincentG]

If you recompile the application, with the newer SDK, it should still have support for the older cameras, as well as the newer hardware.

To use the new cameras, with the new drivers, you would have to recompile the application.

For a customer, with Arena/RB/TT, the Arena and Tracking Tools software need to be updated to the latest version, to allow use with the R2 cameras. You can use V100 and v100R2 cameras in a mixed enviroment. The RB software is not compatible with the R2 cameras.

[Matan]

Yes I understand.
But as I said this solution isn't comprehensive enough to our needs - Customers with different application and versions which meens that we need to compile and test (QA)all version and customers have.
It would have been much convenient if:
1) Your drivers would support backwards compatibility
2) To notify consumer enough time before you are retiring a camera (same happened at past with C120 camera)

Any way I would like to congratulate NaturalPoint on its widespread activities including: new cameras and hardware and enhancing its software (latest news letter).

[Birch]

Hello,

1) You should only need to compile against one version of the SDK (the latest) to get support for all current and previous cameras (V100R2, V100, C120, etc). If you are experiencing problems when using the latest SDK with V100 or C120 cameras please provide additional details.

* When does the crash occur? (application startup, camera startup, changing camera settings or camera frame delivery/access)

* If you have a code sample which demonstrates the crash you can send it to our support team for review (support AT naturalpoint.com).

2) If long term access to purchasing of a product is desired, we encourage you to contact our sales team (sales AT naturalpoint.com) while a product is still in production to discuss an arrangement. This helps us to be aware of your potential needs and factor them into our production forecasting.

[Matan]

This occur while camera start up:
Using driver 034 camera readout screen is lighting cyclic continuously
Using new driver (037) application will crash on start up or won�t start at all.

[Birch]

[quote=Mat]This occur while camera start up:
Using driver 034 camera readout screen is lighting cyclic continuously [/quote]

If you are seeing the issue only with V100R2s, it is because they require build 37 or higher of the OptiTrack SDK. They are not compatible with older versions of the SDK.


[quote=Mat]Using new driver (037) application will crash on start up or won�t start at all. [/quote]

It would be very helpful if you could send us a code sample which demonstrates the crash. It will make it much easier for us to investigate the issue you are having.

Note - if your application has not been re-compiled against the new OptiTrack SDK binaries, that must done before trying to use the newer version.

[Matan]

Thanks,
I know how to handle I could compile.
The issue is that we must avoid recompiling!
We will apprichiate to have a driver and a camera with supports backwods compatibility.

As you know:
Our applications has several versions � and if I need to change our customer a camera to R2 � we will have a very problematic situation : to update source codes and compile this specific project (for every customer for every version).
Keep in mind that if I compile a version (which can be an old one) I must test it for the quality tests.

If you have an old V100 camera I would like to reolace it with our new V100r2 cameras.

[Birch]

As you have noted, when a new SDK version is released sometimes its API is not binary compatible with previous versions of the API. Re-compiling is the way to solve this, the only update to source code required should be the OptiTrack.h file provided by our installer. We understand that it can be inconvenient.

We do provide hardware and API source code backwards compatibility when we release new versions of the SDK, however we cannot guarantee binary API backwards compatibility. New hardware cannot be used with SDK versions released before the hardware was created because the older SDK does not have an understanding of how to interact with the hardware.


If you would like to try an unsupported workaround you could copy the cameradll.dll file (+ the drivers folder) from a new OptiTrack SDK into and an older install of the OptiTrack SDK. This may allow older versions of the OptiTrack SDK to use newer cameras - however it may crash and new cameras may only work partially such as showing up with incorrect resolutions. If it did work for you, we would still advise against it since there would be no guarantee that future versions of the camera DLL would be usable in the same way.

If you have an old V100 camera I would like to reolace it with our new V100r2 cameras.

Do you mean that you would like to swap V100r2 cameras in exchange to get older V100 cameras? If so, please email support with the request and a reference to this thread.