Jump to content

Vende

Members
  • Posts

    19
  • Joined

  • Last visited

Posts posted by Vende

  1. Thanks, ShaunR, it is a good idea. It would be a good inspiration in the other parts of my projects. But it is not so easy. I need to control the loop, because I have got more conponents inside that are dependent on "i" of the loop. So I need several buttons for start, pause, pause and..., stop connected with the loop directly. I think it can be solved with Event Structure inside the loop, but I can not use it properly. Thanks

    To Neville D: No...

    First you will need to allow the time-out case to execute by wiring a value (say 100ms) to the blue icon in the top left hand corner. You will then have to use the state of the "Running" boolean to decide whether to increment the counter or not. You can use 2 shift rgisters (one for the state and once for the count).

    This is thesort of thing you will want to use for the counter.

  2. QUOTE (Neville D @ Feb 16 2009, 07:00 PM)

    Yes, select the camera, right-click and use the NI driver instead of the one supplied by the camera manufacturer. I have my cameras connected to a PXI-RT chassis, so I can't walk you through the exact steps, but thats what I have done in the past.

    Neville.

    Hi, thanks, but I cannot see it in MAX, only in Windows hardware overview. Or do you mean changing in there?

  3. QUOTE (rolfk @ Feb 16 2009, 10:05 AM)

    Well you usually get what you pay for. :rolleyes:

    So you want free and easy, if possible without any work from you? And of course bug free and perfect too?

    '

    I'm pretty sure you can't see it without at least NI-IMAQdx and the Firewire support installed (which is all part of the license required Vision Acquisition Software).

    So no it is not free, but yes I would call it very easy.

    Rolf Kalbermatter

    I ment for free = without any additional payment for individual camera drivers or developement tools, so without Pixelink SDK.

    I have NI-IMAQdx installed and I use an other camera via Firewire, no problem. But Pixelink camera A622 I can not really see! But I can see it in Windows Control pannel, in hardware overview.

  4. QUOTE (normandinf @ Feb 12 2009, 03:56 PM)

    In MAX, you have to change drivers. Pixelink cameras automatically install with the factory drivers and MAX doesn't recognize it. Change the settings in MAX and you'll be able to detect it.

    So does if I understand you well, it means I can not see this camera in MAX Interfaces and Devices and after change yes. How to do this change? I have not foud any possibility of drivers' change, only when a device is detected. Thanks!

  5. QUOTE (normandinf @ Feb 12 2009, 02:36 PM)

    It's a firewire camera, isn't it? You can use IMAQdx. It's all LabVIEW, but I wouldn't call it "free"...

    You are right, it was the first thing I have tried, but I can not find this camera in MAX so I asked about possibility to use it in Labview and its compatibility. How to continue in this case?

  6. QUOTE (normandinf @ Feb 10 2009, 05:04 PM)

    Pixelink SDK contains LabVIEW drivers. The learning curve is steep if you want to customize but once you get it, I found it efficient. (I used it with A742)

    The driver comes with a grabber program that you can use almost out of the box.

    Is there any easier way how to use Pixelink A622 in labview, without SDK and for free?

  7. Hi, I have a little problem with IMAQdx blocks and saving to AVI. I wanted to make a circuit for grabbing and saving to AVI from the example - Grab and Save to AVI.vi. It is allright, but I a need to replace IMAQ blocks with IMAQdx. When I do it, it looks well, the grabbing is functional, but there is a problem with saving to AVI. I cannot get Image Type property from IMAQdx first block, so an error occures - Invalid Image Type. When I connect an image type constant (Grayscale, RGB,...) to IMAQ Create block, the problem is the same! What to do with this? How to adjust left side correctly? Thanks.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.