Quantcast
Channel: Machine Vision topics
Viewing all 1267 articles
Browse latest View live

The picture output is not recorded properly

$
0
0

Hello,

I attached a vi where I tried to record a picture with the webcam, save it , then apply some analysis to detect the particles and their numbers. The original picture is saved properly, but it disappear from the front panel at the end of the vi run.

The second picture remains black and is saved as a black picture ( The vision assistant works well though and the particles count is correctly recorded).

In summary, it is a problem of plotting and saving the pictures.

Thanks,

Zied


Anyone implemented Spatial Frequency Response (SFR) as in ISO12233 using LabVIEW?

$
0
0

I'm exploring the feasibility of implementing an imaging system self-check routine that's at least somewhat compliant with ISO 12233. Has anyone done this and if so are they willing to share some code? Does anyone know of any plug-ins?

(I know there are commercial packages like Quick MTF available but I'd rather do this in LabVIEW.)

 

NI Vision assistant use IMAQ Find Circular Edge

$
0
0

in the IMAQ Find Circular Edge setup , have  a auto setup  button box ,when we create labview vi ,the vi do not have this fuction.why?where this fuction?

image acquisition from 2 cameras simultaneously and writing into AVI

$
0
0

Hi,

 

I have a setup with two (externally triggered) synchronized Basler cameras which continuously acquires images and streams onto the front panel simultaneously. I am using the IMAQdx VI library.  The goal is to write an AVI from these continuous image acquisition. But I dont want to make 2 separate video files from the two cameras. Instead, I would like to overlay the streams vertically/horizontally in one video file. So, for output, I would like to have one AVI (or any other format) file which shows the video from both camera next to each other. 

 

Can anyone please help me or give some ideas how to achieve this? If my question is not clear, please don't hesitate to clarify. 

 

Best,

Arka

Trouble with triggered image acquisition with Basler camera and frame grabber

$
0
0

Hi,

 

I am in need of synchronized image acquisition via frame grabber PCIE 1433. I have Basler  ACA2000-340km and I am trying to use IMAQ Vision Acquisition Software, version 17.5. I have read manuals of the camera and it seems to me that IMAQ misses some functionality for specifying trigger modes etc...I have connected the triggering signal to my camera's CC1 Line, configured as external (from another device - digital micromirror, Vialux), which generates some spatial patterns that I want to observe. I am using two independent programs to first wait for external trigger and grab a series of pictures and second to program the projection of two patterns to my digital micromirror. First pattern is blank- just clean image, the second shoud be mostly obscured by the square. Instead I sometimes get good image but sometimes I see something in between this two cases. I am sure I have right exposure time. I am sure trigger works well. See programs attached. Does anybody know how to repair this, please?

IMAQ Classify Contour Distances.VI

$
0
0

实验了一组数据,发现这个VI只能找最大值,有没有那种可以找到两组曲线距离的最大值与最小值的例子,比如一个水管,有的地方宽,有的地方窄,有的地方弯曲,有没有可以一次把宽度信息找出来,(水管表明凹凸不平,水管在一个平面内,但是路径无规律)

Linear Camera snap raw data don't match number of pixels

$
0
0

Hello, I have linear camera Teledyne Dalsa Linea 8k mono. I'm trying write program to line scan beam intensity profile with motion controller. So scheme is line scan -> step -> line scan -> step...etc. I used function "Get image data" because I'm interested with bytes value in each pixel. Problem is that I get about 32k array data. I know that there is limit with height in output image which is 2. That's not problem because I can reject half data or averege. In screen we can see that data is doubled, but why one line have 16k array elements?  

 

@edit: I forgot wrote that this is GigaE Camera

   

Is possible to modify camera acquisiton attributes during grab?

$
0
0

Hello, I'm working with IMAQdx , It's possible to modify camera attributes or acquisition attributes during the grab, or it's necessary to close the session , open it again and then modify those attributes?

My idea is to modify things like brightness and to see how the image changes let's say "in real time". 

Thanks.


Foscam IP Camera?

$
0
0

Hello

 

Sorry if this has been covered before?

I am using Vision Builder 2010 to look for detection of manufacturing parts. Prevoius we use u-eye usb cameras but we would like to use an IP camera instead. It is a Foscam FI9853EP HD POE IP Camera.

Could someone please tell me if this can be used with Vision Builder or is there a way around it? I may of read that only basler or axis cameras are only compatable?

Thank you

"NI Vision Development Module" with .NET C#

$
0
0

Hello,

 

I'm interested if new version of NI Vision Development Module is still able to be used within

.NET C# applications?

 

Best regards!

IMAQ dx with usb 2.0 camera, camera attributes disappear

$
0
0

Hello I'm working with a chinise USB 2.0 camera , brand is ELP, and it has an MI5100 Aptina sensor of 5MP, but it doesn't have a proprietary driver , it's a UVC camera, in attached picture you'll see the capture of device manager.

The problem is that programmatically and under MAX , in both ways some times is possible to access camera attributes and other times is not. 

Programmatically I use enumerate attributes from IMAQdx , to show which attributes are available from the camera. In attached VI you can see it. For example , you run the VI, and enumerate shows all camera attributes as brightness, gain, etc, stop the VI, next time you run camera attributes are gone , only acquisition attributes and status information are available. The same occurs for MAX, some times shows the camera attributes sometimes not. 

I saw the configuration files for the camera, from IMAQdx data folder, in the .icd file there are only acquisition attributes , no other information. If I add by text camera attributes to this .icd file , then maybe camera attributes will be allways available ?? The thing is that I don't know which format this text must have. In the attached .iid and .icd files.

Change fps in a Thorlabs DCC1645C camera

$
0
0
Hi,
I am working with a DCC1645C camera with Labview 2107 32bit running on Windows7 32bit NI IMAQdx version 17.0.
I need to change the camera fps in Labview. Using the software of Thorlabs I can control the camera and change its settings incloding the frame rate, pixel clock and exposure. 
 
previous post is irrelevant because the suggested solution using the camera attribute is failed. 
 
When I try to control the camera using the basic example in Labview:
 Vision acquisition-> NI Imaqdx->high-level->grab and attribute setup, 
It's failed to connect the camera frame rate values and the fame rate is stuck on 10 fps. 
When I try to connect the camera using NI-MAX, it also give me only the option of 10fps.
 
Thanks,
Matan

IMAQdx Error "Unable to set attribute" when changing AquisitionMode in GigE camera

$
0
0

I am working on a C# application using NI-IMAQdx for acquisition using a Basler acA 1600-20gm GigE camera (the camera specifics may or may not be relevant). My application needs to alternate between continuous acquisition mode (to simulate 'live' video) and a triggered Single Frame acquisition using Line 1 to trigger the camera.

 

When I attempt to change from Continuous Mode to Single Frame Triggered Mode, I get an "Unable to set attribute" error when trying to set the AcquisitionMode to SingleFrame from its current Continuous setting.

 

When changing from Continuous to Triggered I also change the TriggerMode from Off to On.

 

I have tried changing the order of setting the attributes (TriggerMode then AcquisitionMode and vice versa).

 

It is unclear whether this is a camera issue (i.e. is the camera in a state where it is unable to accept the attribute change), or an IMAQdx software issue.

 

Any thoughts or suggestions are appreciated.

 

Thanks,

--Dave

Use Basler Cameras Digital Output

$
0
0

hi everyone,

im trying to use digital output of Basler acA1920-uc cameras to switch off & on a LED.

i can select the output and see it's status but im can change it's value.

can anyone help me ?

thanks 

 

Grab directly on FPGA?

$
0
0

Hi,

 

The usual way on a cRIO is to perform image grab on the real-time CPU and transfer to FPGA through DMA FIFO.

 

Is there any way currently, or planned in future products (cRIO-904x or 905x), that will allow GigE grab directly on the FPGA, not involving the real-time CPU at all before we get data back from the FPGA?

 

Thanks for any insights!


Multiple cubes location detection with varying background texture

$
0
0

I want to location position of different color cubes in a given image. I have used CNN regression with VGG16 architecture whose accuracy is good enough. But while testing, predicted coordinates are having error from 0.3 to 20 cm. During training each sample consist of an image with 6 cubes of similar shape and different colours and label as 18 coordinates variables. Is there any other way to solve this problem? Sample images are

center_0.9464.jpg(x1, y1, z1, x2, y2, z2,....,x3, y3, z3)center_0.8084915.jpg(x1, y1, z1, x2, y2, z2,....,x3, y3, z3)

Triggering Basler Cameras From Software

$
0
0

Hi Everyone,

I want to use the Software trigger for basler cameras to take picture at a specific event.

the attached vi always give me a time out error and i don't understand the problem.

theoretically it should works, but maybe there is a parameter that i forget.

can anyone help me?

thanks

Does vision acquisition work with evaluation license?

$
0
0

I am currently using an evaluation version of Labview Pro 2018 (currently the 7-day default evaulation, not yet extended.)  Using the NI package manager, I installed NI-IMAQdx and the Vision Development Module (I don't think I should need the latter in any case).  They both show as installed in the package manager, and show up listed as Evaluation with 7 days remaining in the license manager.

 

Things are working at some level because I can get images off my camera using MAX. But in Labview itself, there is nothing in the Vision and Motion tree, and when I try to open a VI with IMAQ subVIs it can't find them.  I have the same issue with DAQmx.

 

Is this a problem for the evaluation versions, or with Labview 2018, or is there a secret handshake I need to perform? I'm not very inclined to shell out several $k for software when the evaluation doesn't even work.

Random “Get Image2.vi” timeout error -1074360293 during a GigE continuous acquisition

$
0
0

I have never posted on this forum before but I often leverage the information available here to minimize my learning curve. I have not been able to find any solution to the issue below so I decided its time for my first post. Some of the information below has been regurgitated form the posts of others on this forum

 

 At random time intervals ranging from once per hour, to once per 20 hours, I am having a “Get Image2.vi” timeout error -1074360293. This error is happening on multiple computers, in LabVIEW, in executables, in Max, and in the camera vendor provided software. I am running 4 different computers each with 2 cameras. The surprising thing is that 1 of the computers never has the error while the other 3 do. This is true even when I swap around the GigE cards, the cables, and the cameras. The PC without the error is ~2 years old and the 3 that are failing are newer Alienware 51 computers. I have been unable to make any sense of this information despite a significant effort.

 

I am using an Adlink GIE62 card with the Intel PRO chipset. The cameras are FLIR (formally Point Gray) BFLY-PGE-50S5M-C (5MP Sony CMOS).

 

Here is a list of all the things I have tried so far without success

 

  1. The software input value of “Get Image2” was changed from “Last New” to “Next”. This change made no noticeable, positive or negative impact to the primary issue but is presumed to be a minor, generic programing improvement. We will default to “Next” moving forward.
  2. GigE driver version was evaluated and was ruled out as the primary issue. Despite this fact, a significant amount of data does exist that proves a significant value add when using the NI “High-Performance Driver” instead of the Intel PRO/1000 default driver. In addition to reducing processor overhead, this driver eliminates the potential of windows firewall and other antivirus software from blocking video packets. This type of packet blocking can be intermittent, difficult to troubleshoot, and should be avoided by always using the NI “High-Performance Driver”.
  3. GigE cable quality was previously studied and has proven to offer value regarding EMI tolerance. Regarding the current issue, only the high-quality cables have been tested.
  4. Camera thermal variance was studied and ruled out as a contributing factor. In a short (~1 hour) test one camera was limited to 28°C with heatsinking and a second was elevated to 75°C using a heater. There was no noticeable performance difference between the two cameras. As a reference, a camera mounted in a CMS will typically level off ~45°C and a “floating” camera with no airflow (in a bag) will typically be ~65°C
  5. Camera settings
    • Firewall Traversal attribute is Enabled. (This is not believed to be relevant when using the NI “High-Performance Driver” but is good practice.
    • Camera Timeout values were not studied during this analysis, but it is believed that a value of ≥1000 will minimize the likelihood of false errors. This is important when the PC momentarily becomes distracted by other processes (like network communication) especially if the PC is in any form of hibernation. This includes when the processor has throttled down to save power (windows default).
    • Windows power management has been set to “performance mode” to prevent the CPU from “throttling down” or attempting to sleep in any way.
    • Jumbo Packet size is set to a value of 9000 to provide the best performance and minimize PC overhead.
    • Test Packet Enabled is set to disabled. This was studied and circumstantially ruled out as the primary cause of our camera crashing issue. Despite this fact, there is historical Forum data on the showing that having test packets enabled can cause the exact symptoms we are experiencing. This change is known to potentially cause a new error of 0xBFF60493 which is fixed by turning off the option to "Display images on remote monitor." (In MAX (Tools->NI Vision->Remote Image Options...)
    • Packet Resends Enabled is set to disabled. The supporting logic for this change was not directly found on the NI forum but instead was formulated from multiple separate pieces of information including:
      • Since image data packets are streamed using the UDP protocol, there is no protocol level handshaking to guarantee packet delivery. Therefore, the GigE Vision standard implements a packet recovery process to ensure that images have no missing data.
      • The GigE Vision header, which is part of the UDP packet, contains the image number, packet number, and timestamp. As packets arrive over the network, the driver transfers the image data within the packet to user memory. When the driver detects that a packet has arrived out of sequence (based on the packet number), it places the packet in kernel mode memory. All subsequent packets are placed in kernel memory until the missing packet arrives. If the missing packet does not arrive within a user-defined time, the driver transmits a resend request for that packet. The driver transfers the packets from kernel memory to user memory when all missing packets have arrived.
      • CPU Usage: Unlike other machine vision bus technologies, which can DMA images directly into memory, Gigabit Ethernet requires CPU usage for packet handling. This means that you are left will fewer CPU cycles to perform image analysis. While CPU usage can be mitigated to a certain extent by using the high-performance driver, it cannot be eliminated.
      • Latency: Because network packets can get lost, requiring resends and network packet handling is CPU dependent, there is a non-trivial latency between the time a camera captures an image and the time it appears in user memory.

 

I have attached a simplified version of code that creates the error and logs the error information to a file. As I said earlier, I don’t expect the code to be helpful since the issue also happens in Max and the camera vendor provided SDK software.

 

Despite all of the above, the issue persists and I have no idea what to try next.

If you have any insight or know of any ideas I can test, please reply.

Using CVS-1450, 2 Basler camera and Matlab

$
0
0

Hi everyone,

 

I am using a NI CVS-1450 with 2 Basler Cameras (firewire) to do a vision system for a robot (bin picking), as my master degree final work.

I am working with Matlab, but can't figure out how to see the image from cameras on Matlab. I need that to run a code that take snapshoots whenever I decide (in the code). I mean, I tested Matlab with IP cams (D-link cameras), and there is a comand in Matlab (ipcam) that recognize the cameras and I could create the objects in Matlab and preview what the cameras was seeing. But in my actual scenario, my cams (Basler) are connected to CVS-1450, and CVS is connected in my laptop with a crossover cable (network cable). I am able to see and setup the CVS system through the MAX application, so I know that it is working, but I don't know how to read my system with Matlab, which command I have to use, or what can I do to see the image through Matlab.

 

Please, if someone can help me, I will be thankfull forever.

 

 

Viewing all 1267 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>