Subscribe: Machine Vision
http://forums.ni.com/rss/board?board.id=200
Added By: Feedage Forager Feedage Grade B rated
Language: English
Tags:
acquire images  basler  camera  card  file  frame grabber  gige  images  max  national instruments  slot  software  vision 
Rate this Feed
Rate this feedRate this feedRate this feedRate this feedRate this feed
Rate this feed 1 starRate this feed 2 starRate this feed 3 starRate this feed 4 starRate this feed 5 star

Comments (0)

Feed Details and Statistics Feed Statistics
Preview: Machine Vision

Machine Vision topics



Machine Vision topics



Published: Fri, 22 Sep 2017 19:04:21 GMT2017-09-22T19:04:21Z

 



VBAI is using single core

Fri, 22 Sep 2017 18:38:06 GMT2017-09-22T18:38:06Z

Hello,

I have searched this in the forums but could not find someone faced with this issue. I am running a match pattern step in VBAI. Since I am defining a large template, it needs large resources to be able to make calculations. But when I look at the task manager, application is only using %25 of the CPU. Because of that, it tooks so many time to make calculation, actually I could not be able to wait until the end but killed the process.

So, with another system, it can use %100 of CPU and that is what I need. Is it some kind of single core issue or something else, and how can I change it?




Support for Time of Flight camera by Basler

Thu, 21 Sep 2017 10:40:50 GMT2017-09-21T10:40:50Z

Hi,

Recently I have started working with tof640-20gm-850nm camera by Basler, and currently I have been using different C libraries to make it working. I was wondering if there will be any direct support for these types of cameras from National Instruments, which I haven't found any support for as of today.

 

Link to ToF camera: tof640-20gm-850nm

 

Best Regards

Avanti




Connecting to GigE camera on MAX through CVS-1458RT

Wed, 20 Sep 2017 20:34:53 GMT2017-09-20T20:34:53Z

In NI MAX, when I try to click on my GigE vision camera in Remote Systems ->NI-CVS-1458RT-xxxxxx -> Devices and Interfaces -> Network Devices -> cam0, I receive "Error 0xBFFF8004:  An exception occurred while trying to execute remote procedures."  I plugged my camera directly into my computer's ethernet port, and noticed that the IP address that was shown using the camera vendor's software was different from the IP address shown on NI MAX.  Has anyone else had a similar issue?




IMAQ display X-Control

Wed, 20 Sep 2017 18:03:28 GMT2017-09-20T18:03:28Z

Hello LV Vision Users/ NI Support,

I am trying to create a custom looking Image control. I decided to use a X-Control for IMAQ Display and I am having some trouble. When I use IMAQ reference inside a X-control it never gets updated, when I write to the indicator. Therefore, I was told by NI to use a Cluster and change the Boolean value each time you write to the image. Which seems to work, however the performance has slowed down significantly and I am wondering if anyone else know a better way to implement this. I have attached my code for reference. 

 

LV version 2017

Thanks,

Ruchi




Writing AVI files without NI Vision?

Wed, 13 Sep 2017 17:33:28 GMT2017-09-13T17:33:28Z

Is there a way to write an AVI file without using NI Vision. I have an application in which I'd like to do this, but have no need for any of the other features of NI Vision. 




Barcode grading and aperture

Wed, 13 Sep 2017 15:24:13 GMT2017-09-13T15:24:13Z

I am using the module IMAQ Read Barcode to grade the barcode quality from an camera image. This works perfectly fine. I am trying to get my grading results as close as possible to the results of a traditional verifier. A normal verifier works with an aperture which can be set to a value or aperture number. Many verifiers use a value in um.

 

The IMAQ Read Barcode module in Labview Vision has an aperture input, but I have no idea what this value represents... Is it in pixels or in ....?


Anybody any idea about this value?




NI-Industrial Communications for EtherNet/IP communication with NI Vision Builder AI

Wed, 13 Sep 2017 00:37:49 GMT2017-09-13T00:37:49Z

Note: Cross posted from NI-Industrial Communications

 

I have been trying to run an ethernetIP server (using vision builder AI  [VBAI]) along with the NI-Industrial Communications for EtherNet/IP VIs to talk to it. Unfortunately I am not successful and I am getting the CIP Status 0x5:

Error: -251723760

EthernetIP Tag Read STRING.vi;
Details: CIP Error - Extended status may be available
CIP Status: 0x5 (Invalid destination/class/instance/structure)

 

I would love to know what I am doing wrong.

 

FYI: I have tried to read other registers (that the one in the red box) with the same result. I must be overlooking something obvious here.

 

See the image below that describe my settings and the error:

 

(image) (image)




How does IMAQ classify process the image?

Tue, 12 Sep 2017 21:35:54 GMT2017-09-12T21:35:54Z

Hi, after I create the Classifier file by NI Classification Training Interface I used the function IMAQ Classify in order to classify object in an image, the image on the input of the function was a grayscale image. Finally the classification worked well, but I didn't understand how the function work. I didn't undestand if the image, that passes through in the function, is processed in order to obtain a thresholded image that stand out the object in order to achive all its features. And if that is right which value of threshold the function IMAQ Classify use to do it (maybe the value that I used in NI Classification Training Interface)?




pattern matching template information

Tue, 12 Sep 2017 07:42:21 GMT2017-09-12T07:42:21Z

I'am using the Labview Vision Assistant(VA) to recognize objects in a workshop for students. Recognize objects is done by the in the VA's Pattern Matching function. The pattern is matched by a template file on the computer, specified in the Template Path field of the Pattern Matching function. The Pattern Matching field specifies an absolute path. Porting the Labview project, including all VI's and template files to an other computer location causes the problem that the template files are not found. So, is there a workaround to use relative path's for the template files containing the match patterns.

 

Kind Regards,,

Gerard




Generate software triggers for a Basler USB camera from within a LabView VI

Mon, 11 Sep 2017 18:16:09 GMT2017-09-11T18:16:09Z

Dear all,

 

I'm writing acquisition software for a Basler USB camera (model #: Basler acA1920-155um). [Link to a programmer's manual below, though maybe not the most recent one]: http://mlab.no/blog/wp-content/uploads/2009/06/basler_pylon_prog_guide_and_api_ref.pdf


So far I've been successful acquiring images and setting camera attributes with IMAQdx in LabView. (To do this, I've been looking through the above manual and the NI-MAX XML file for the camera to get the attribute names and values, then using IMAQdx property nodes to set the attribute name and value.) When testing the camera in NI-MAX I'm able to generate software triggers for the camera with the 'Execute' button below (see screenshot below). The software triggers also work in the native Basler Pylon viewer program as well.


(image)

 

I'm not exactly sure what the 'Execute' button does (I guess it's a call to something in the Basler API), though perhaps there are some suggestions in the above manual.

Can you describe how to run the 'Execute software trigger' from within a LabView VI as well?

 

Thanks for your help!




synchronization of frame grabber and line scan camera

Mon, 11 Sep 2017 15:58:44 GMT2017-09-11T15:58:44Z

I have a problem of synchronize my frame grabber PcIe 1433 and line scan camera (Basler Sprint 2048-70km). I searched many old threads in this forum and get more confused.

 

Basically, what I am trying to do is generating a repeated pulse train (16kHz) and a ramp signal (goes up from -3v to +3v for 520 steps and goes down from +3v to -3v for another 20 steps) from the NI DAQ 6211. I need these two signals to be synced. The pulse train will be output and send to the frame grabber via SMB connector while the ramp signal will be sent to a physical scanner  (galvanometer) to drive the scanning.  The pulse train will be the trigger for each line of the camera and the frame grabber. My confusion here is how does the camera communicate with the frame grabber to know the exact trigger (pulse train) I have input from the SMB connector? If it is can be done from software perspective by setting the camera control line, I did so but my frame is keep rolling.

 

So I searched some old threads. Here's the one I believe trying to solve a very similar problem as I do.

https://forums.ni.com/t5/Machine-Vision/Trouble-Exporting-Basler-sprint-pixel-clock-to-PCI-1428/td-p/1961067

Basically, the person is asking how to pull out the pixel clock of the line scan camera to sync the frame grabber and the line scan camera. And one of the answer is and I am quoting here: ''I spoke to one of our developers for these boards and he indicated that it is not possible to route the pixel clock on third generation boards (1429/1430/1427/1433/1435 and later). He mentioned that an alternative you could consider is that the framegrabber can create a pulse up to 2MHz and export that on both RTSI and CC0. Hopefully that gives you a workaround".

 

so is that mean I don't need the DAQ 6211 to generate the pulse train as the trigger, the right way to do it is to use the 1433 itself to generate a pulse train and export the trigger through camera control line to sync the line scan camera ?

 

Any suggestions would be greatly appropriated!

 

 

 




Cast U64 RGB image to U32 RGB image

Fri, 08 Sep 2017 14:56:17 GMT2017-09-08T14:56:17Z

Hi All ,

I am trying to cast a U64 RGB image into a U32 RGB image. I have attached the VI and a sample image(U64 RGB).

I am facing 2 issues:

1) I am unable to see the U64 RGB image in the image indicator, though I can read the pixel values. Why is this happening? 

2) I am unable to cast it to a U32 RGB image.

Thank you for the help.

Regards

Aveo




Vision Builder: On transferring the vbai file from one machine to another, the file does not reflect the changes made.

Fri, 08 Sep 2017 14:35:45 GMT2017-09-08T14:35:45Z

1. xyz.vbai exists on machine 1.

2. I updated the file on machine 2 and renamed it abc.vbai.

3. When I copy pasted the file back to machine 1, the variable names and some of the steps did not reflect the changes that I made.

 

What should be the issue? Could it be using cached file from somewhere?




Auto export of trained ocr images from .abc file

Thu, 07 Sep 2017 11:25:45 GMT2017-09-07T11:25:45Z

Hello all,

 

I have an application in which i have to export the trained OCR images from .ABC file.

 

Please advice me the solutions.  

 

Regards ,

Vivek G.




GigE camera in NI MAX: Invalid Device Type

Mon, 04 Sep 2017 11:16:33 GMT2017-09-04T11:16:33Z

Hello,

 

I have a problem with my image acquisition system.

I am using an Allied Vision GC2450C gigE camera in combination with an Intel Gigabit CT Desktop Adapter network card. I have followed the installation instructions from the camera manufacturer and can succesfully acquire images from the camera via the manufacturer's software (Vimba). I have installed the national instruments Vision Acquisition software (including the NI GigE Vision driver), so I should be able to connect to the camera via LabView. The camera does show up in the NI-IMAQdx devices in NI MAX, but as soon as I try to open it, I get the error message: 'Error 0xBFF69007 - Invalid device type' (see screenshot).

 

Interestingly, I was previously able to acquire images from the exact same camera and the exact same network card in a different PC (which I need to replace for other reasons). The problem thus does not seem related to the camera and/or network card itself. I tried uninstalling and re-installing different versions LabView, NI Max, the network card drivers, Vimba, but to no success. I also tried searching for this error message, but I couldn't find anything helpful...

 

In other words, I was hoping that maybe anyone has any idea on how to tackle this problem. Thanks a lot in advance!




Camera sync with scanner problem

Sun, 03 Sep 2017 07:45:18 GMT2017-09-03T07:45:18Z

Hello again,

 

I'm working on a project that I have to sync image acquisition (line camera) with scanner. I think I'm doing it right but image is always randomly delayed, not synced. 

I set the camera to 'no trigger' mode, then move the scanner to the minimum position. Then set the camera to 'trigger' mode, and start the scanner with continuous sawtooth signal. I'm getting 1024 chunk of images at a time so, when I'm out of sync, I'm reading mix of first and second sawtooth signals.

What I see is, sometimes, the image acquisition starts half way up of the first sawtooth signal (it's very random and most of the time it's out of sync). Can someone please see my test VI and suggest if I'm doing anything wrong?

When I see the sequence on O-Scope, I see the DAQ signal goes to min, then starts the sawtooth. And the camera is in 'trigger' mode and waits until the sawtooth starts.

 

Much appreciated.




Can get GigE images from one NI 8234 card, but not the other

Fri, 25 Aug 2017 09:58:24 GMT2017-08-25T09:58:24Z

Hello,   I have a PXIe-based image acquisition system: Chassis: PXIe-1071 Controller: PXIe-8840 Slot 2: NI 8234 Slot 3: NI 8234 (initially not present) Slot 4: PXIe-6612   Software: LabVIEW + IMAQdx 2016 Cameras: Basler aca1600-60gc Initially, we only had 1x NI 8234 (in slot 2). Slot 3 was empty, and everything was working fine. Later on, we added another NI 8234 into slot 3. This was when trouble began.   When we first booted the PXI controller after inserting the new card, Windows automatically tried to install drivers, but failed:   Device Manager had trouble with the new card:        Notes: "Intel(R) PRO/1000 PT Dual Port Server Connection" #3 and #4 are the Ethernet ports from the new card (Slot 3). "National Instruments GigE Vision Adapter" and "National Instruments GigE Vision Adapter #2" are the Ethernet ports from the first card (Slot 2) The other "National Instruments GigE Vision Adapter" is the secondary Ethernet port on the PXIe-8840 controller. The IMAQdx Device Driver installer did this automatically. I was able to "fix" Device Manager's complaints by right-clicking the device icons and manually updating the drivers:   However, this does not seem enough. When I try to snap/grab images from a camera connected to the new card, I get this: (image taken from http://digital.ni.com/public.nsf/allkb/4D0ECFAA9AD9FF3E8625792600551A1E instead of my own screenshot)   Jumbo frames is enabled by default, and my firewall is completely disabled.   Here's what I've tried: Checked the network adapter settings in Windows Control Panel -> Network and Sharing Center -> Change Adapter Settings. As far as I can see, all 4 Ethernet ports on the 2 cards have identical settings. Checked the camera attributes, acquisition attributes, etc. in NI MAX. As far as I can see, all cameras are the same model, and all have the same settings. Swapped the cameras around. A camera plugged into the old card in Slot 2 can acquire images; when I moved it to the new card in Slot 3, it cannot acquire images. Swapped the cards around. The old card could acquire images in Slot 2; when I moved it to Slot 3, it could no longer acquire images. The new card was unable to acquire images in Slot 3; when I moved it to Slot 2, it gained the ability to acquire images. Uninstalled and reinstalled drivers: I ran the NI Device Drivers installer again, and opted to Remove the "National Instruments High Performance GigE Drivers". I rebooted, re-installed the High Performance Drivers, and then re-booted. In the end, the cards still behaved the same way.   I'm out of ideas at this point. What could the issue be?   Thanks in advance![...]



Interface type (Camera or framegrabber)

Thu, 24 Aug 2017 07:07:06 GMT2017-08-24T07:07:06Z

Hello All,

I have an application where my application supports both camera as well as Frame Grabber acquisition but in the functional part i need to differentiate whether the interface is camera or Frame Grabber

how to get this done?




calibration grid

Thu, 24 Aug 2017 04:55:39 GMT2017-08-24T04:55:39Z

Hi,

I want to do correct the image using calibration method. How many minimum dots should be in calibration grid?

If anybody knows please explain me.




Image blob 's max/min pixel location.

Tue, 22 Aug 2017 17:32:46 GMT2017-08-22T17:32:46Z

I have a raw image (U8) and a thresholded image. In the thresholded image, there are blobs, how do I find for each blob the max/min pixel value and its location XY in the raw image? Is there any fast, convenient vi or method available? I did not find any....all particle reports does not contain this information..