Wincam Pro

0 views

Skip to first unread message

Muriel Pelley

unread,

Aug 3, 2024, 5:04:57 PM8/3/24

to consusyto

I am working on a large project and a few of the researchers would like beam profiling integrated into the system. I tried Spiricon and that is a non-starter. Now they are looking at a wincam with dataray software. Dataray is the name of the company. So first of all, yes I know they have an example on thier webpage, and yes I see the pretty PDF explaining interfacing to thier dataray software with labview. Thank you in advance for that. Has anyone got this stuff to actually work? The example is in labview 6. I followed through the PDF and created the other example program myself from scratch. Also I have used ActiveX before and made it work in most cases, though sometimes it is more trouble than it is worth.

has anyone used dataray successfully? Because I am having no luck. It does not produce errors. It runs, but just sits there and no images make it to the screen let alone the beam calculations that are the main purpose of the software.

I tried to look into this camera but want to make sure I'm finding the right one. Both of the WinCam models listed on this site look to be USB cameras. Is this a DirectShow compliant camera? This would determine whether the software they are providing is also a driver for the camera or whether it uses our IMAQ for USB driver. If it does use the IMAQ for USB driver, you will also need Vision Development Module etc in order to use that driver. Also, depending on which version of LabVIEW you're using, you may run into problems getting their software to work in a version more recent than LabVIEW 6. Have you contacted DataRay to see if they have more recent documentation or software for LabVIEW integration?

It is my understanding that their software works as the driver. That the images and graphs that would be presented are activeX objects, thus not requiring IMAQ. I have not tried using the canned LV Imaq USB driver. If I wanted to simply use it as a camera, I would just get something that plays nice with Labview like a Dalsa or basler. But the point of using this is that some people in the group want the beam profiling capabilities of the wincam softwear. I keep pleading with them to simply let me make my own beam diagnostics. But people get set in their ways are used to seeing a certain graph.

With Spiricon and dataray, they view the beam diagnostics software as their core competency. The camera acts as a software key. One wont operate without the other. They give an example in the manual on creating a wincam labview VI from scratch. I followed it through and it worked.

I could talk my coworkers in to letting me do this, if it wasn't for an old computer we have sitting around with an insanely complex VI on it that actually does have a working wincam. However the computer is old and the labview is 7.1 .

Right now I can't find someone who knows the password to that computer but we know at sometime in the past, someone had "a wincam" working with labview and when I get the password I'll look at his code. But the world has moved on since then. This is probably not even a USB wincam so its safe to say that there are software changes since then.

This looks like a dead end. It seems all of these beam diagnostic companies hate Labview. Which is a pity. In my opinion they are loosing market. They should make their stuff accessible to labview and use their cameras as a software key, then everyone is happy.

Yes, there are differences between LV 6 and 8.6, but a VI written in that previous version should open with 8.6 according to our compatibility chart listed here. I would say that the other computer that has working code is your best bet at this point. If you can get ahold of that, you should be able to upgrade the code to the most recent version of LabVIEW and proceed from there.

Well I got it working, you have to first start thier code then shut it off. Also there is a function called something like "start device" which is not used in thier example or in the LV manual where they walk you through writing a VI.It turns out that this is also critical. I wish I could get the thing to work without having to start their code whenever the computer is started up. But I guess that is a small price to pay.

This might be a quite different topic, but have you successfully tried to get the profile raw data for DataRay? I am specifically refering to the Beam'R or BeamMapC products. But I do think the iDataRay interface for WinCam D is much the same.

Anyway, here's the catch. I was calling this 'SaveCurrentData' invoke node from the GetData ActiveX, however it will just return the raw data of the 4 readings used to average the Xc (centroid X) value. I will not provide me information about the Y axes.

I am referring to automatically save the profile data same as when you right click the profile and get the data as attached (see 2.5.txt); however for the 'SaveCurrentData' method it will always return the values same as 3.10.txt (please see attached)