Any examples for using with VB6?
Thanks,
Using CameraSDK with Visual Basic
Re: Using CameraSDK with Visual Basic
Unfortunately VB6 and VC6 are not supported. The problem here is that the Camera SDK is compiled with VC2005 and even though there are probably some tricks to make it work, we've only had reports of issues.
Is moving on to VB.Net out of the question?
Is moving on to VB.Net out of the question?
-
mikeincinci
- Posts: 22
- Joined: Tue Aug 14, 2007 7:26 am
Re: Using CameraSDK with Visual Basic
The main issue for us is that our established product using the r1 cameras doesn't work with the r2 cameras. Some of the features in the old SDK are missing from the new SDK. It will take a major rewrite of our code, in addition to learning a new programming environment.
Economically, we may be better off abandoning our investment in optitrack cameras than to expend the rewriting resources.
Does the "tracking tools" support 2D tracking of a single dot and can it be interfaced using VB6?
Economically, we may be better off abandoning our investment in optitrack cameras than to expend the rewriting resources.
Does the "tracking tools" support 2D tracking of a single dot and can it be interfaced using VB6?
-
mikeincinci
- Posts: 22
- Joined: Tue Aug 14, 2007 7:26 am
Re: Using CameraSDK with Visual Basic
Any possibility that the SDK can be accessed in LabView?
Mike
Mike
Re: Using CameraSDK with Visual Basic
[quote=MikeInCinci]Does the "tracking tools" support 2D tracking of a single dot and can it be interfaced using VB6? [/quote]
Tracking Tools can output marker coordinates via VRPN (network stream). This could easily be received by any VB6 app (using Winsock OCX for example).
You could also try to code the relevant part of the Camera SDK into your own ActiveX control and then import this OCX into VB6. Maybe the .net wrapper (see thread on these forums here) could help producing an OCX directly? Apart from that, are you really sure that there is no way of creating a DLL file, that could be called from VB6? I'm not sure about persistency of data, but I myself have called external DLLs from VB6 very often...
[quote=MikeInCinci]Any possibility that the SDK can be accessed in LabView?
[/quote]
You could either try to call your LabVIEW code from C++, i.e. make everything a complete C-app. See http://zone.ni.com/devzone/cda/tut/p/id/3517
Or, you could control LabVIEW via a VI Server, see here http://zone.ni.com/reference/en-XX/help ... vi_server/ and here http://digital.ni.com/public.nsf/allkb/ ... BC007384E9
However, this doesn't answer your question of the other way round -- how to access the camera SDK directly from LabVIEW. I'm not sure if that is possible (sorry, no expert of course). It should however be relativly easy to listen to the VRPN stream (created by Tracking Tools).
Tracking Tools can output marker coordinates via VRPN (network stream). This could easily be received by any VB6 app (using Winsock OCX for example).
You could also try to code the relevant part of the Camera SDK into your own ActiveX control and then import this OCX into VB6. Maybe the .net wrapper (see thread on these forums here) could help producing an OCX directly? Apart from that, are you really sure that there is no way of creating a DLL file, that could be called from VB6? I'm not sure about persistency of data, but I myself have called external DLLs from VB6 very often...
[quote=MikeInCinci]Any possibility that the SDK can be accessed in LabView?
[/quote]
You could either try to call your LabVIEW code from C++, i.e. make everything a complete C-app. See http://zone.ni.com/devzone/cda/tut/p/id/3517
Or, you could control LabVIEW via a VI Server, see here http://zone.ni.com/reference/en-XX/help ... vi_server/ and here http://digital.ni.com/public.nsf/allkb/ ... BC007384E9
However, this doesn't answer your question of the other way round -- how to access the camera SDK directly from LabVIEW. I'm not sure if that is possible (sorry, no expert of course). It should however be relativly easy to listen to the VRPN stream (created by Tracking Tools).