LabVIEW
Interfacing Phantom v611 High Speed Camera with LabView Using Phantom SDK
https://phantomhighspeed.my.site.com/PhantomCommunity/s/article/Phantom-SDK-MATLAB-LABVIEW-Access
Did you request that SDK already? Did you read the documentation that came with it? What are your problems?
I, and with me most probably everybody else here on this forum, do not have your camera nor the SDK available. This makes it impossible to give you any specific advice.
Your best bet is to contact the manufacturer and ask them for some tutorials about using their hardware with LabVIEW. Independent if that is fruitful or not, you should start going through some LabVIEW tutorials to learn the basics of LabVIEW and then start doing your experiments after reading the SDK documentation. If you then run into problems you can post them here with sample code (images are usually only remotely helpful). On the top of this forum you have several links about learning resources for LabVIEW.
Before you can run, you have to start learning to walk, and image acquisition is for sure not the easiest of thing you could try to do in any programming language, including LabVIEW. But you need to be able to program in a programming language before you can try to do even moderately complex things in it.
@Geometry wrote:
Hello Rolf,
I have got the SDK and read the document. I am new to LabView hence I am finding it difficult to get my way around it. I have done the installation but I am not able to get the camera preview in LabView. Any help would be much appreciated. Thank you.
Regards,
Evans
I'm probably one rare user who have had Phatom cams in my hands last year and these cams was successfully integrated into LabVIEW. Not exactly your model, but the v2640, this one:
But in my particular case it was not required to have "preview" on the LabVIEW side at all, the only control part was implemented. The multiple Phantom cameras was synchronized (TTL frames pulse train and 24V trigger) with hardware triggering delivered from cRIO 9054 equipped with NI 9401 and NI 9472 Modules (20K FPS was required).
The SDK is just wrapper to PhCon.dll. What I would like to recommend is — at the first get camera fully working with PCC (Phantom Camera Control) Software. Then using SDK try to init cam (starting with PhGetCameraCount) and start/stop acquisition (PhRecordCine) like you did with PCC manually. As far as I remember you will need to setup partition (PhSetPartitions) before recording. Some examples are provided, for me was more easy to take a look into C++/C# samples rather than read docs. Phantom's Technical support also works quite well, for example, I got troubles to obtain temperature of the cams (this function was not wrapped to SubVI) and engineers pointed me to appropriate DLL function. You might get some troubles with preview — I did this attempt just for fun, but this wasn't stable enough, caused sporadical exception. But I was lucky, because this was out of scope — this camera have two Ethernet connections - 1G and 10G, and can be controlled from one interface (slow 1G), but recorded images (sines) can be obtained from other one (fast 10G) using PCC Software. PCC Software can be run simultaneously with LabVIEW App side by side, so theoretically if you have troubles with preview, then PCC Software will show it for you (on the other hand I'm not sure if your model have two Ethernet or just single). Anyway, without LabVIEW experience "full integration" could be complicated and painful, because for elegant and fast solution I will recommend to use IMAQ and integration third party cam into LabVIEW/VDM is really not the best choice for the first "beginner" project.
@Andrey_Dmitriev wrote:
Anyway, without LabVIEW experience "full integration" could be complicated and painful, because for elegant and fast solution I will recommend to use IMAQ and integration third party cam into LabVIEW/VDM is really not the best choice for the first "beginner" project.
It's one of the rather advanced tasks you can attempt to do in any software. That's the power of the, now almost non-existent, NI vision hardware products. They were ready made and "just" worked without having to deal with trying to interface to DLL APIs and the like and mix and matching camera image formats to your favorite software's supported image formats. Even small format differences can end up giving you a lot of work and doing that on the C programming level, while fast, is very error and crash prone.
