GigE Vision extended to sequencing

Similar Questions

• Do IMAQdx and NI GigE Vision 2.0 material support?

  Hello

  From my brief research, GigE Vision 2.0 has features very nice that I'm at the end which are not supported by previous GigE Vision 1.x standards:

  • Compression on the side of the camera
  
  
  • Timestamp and sync IEEE 1588 (PTP)

  OR those taking? If not, are there any plans to add support in the near future?

  Thank you!

  Hi again,

  Thanks for the extra frame.

  Assuming that your only using the camera is saving JPEG images on the disk, and you are concerned about the performance of the acquisition system, I think that an IP camera might be a better choice. These cameras acquire images compressed, so you can very well save the direct-to-disk with no extra charge. This will save time and bandwidth of the network processor. The bandwidth would be nice because you could probably just run 6 cameras in a gigabit switch and connect to a port on the PXI chassis instead of several 8234 ports. This is possible because not only if bandwidth is reduced, but the IP cameras can use TCP and sharing bandwidth much more enjoyable that can cameras GigE vision. To save the raw images on the disk, you can use the IMAQdx VI "Get Image Data", which is a JPEG file that you can save directly to an IP camera.

  Regarding the time stamp data, depends on the accuracy required. Since you recorded all the time after that image returned, is quite imprecise because it is not really correlate with the acquisition time. You might get a more exact time in two ways: record IMAQdx a CPU timestamp on receipt of driver that you can use (useful if the CPU is synchronized to GPS/NTP or similar) or you can use a timestamp saved in the image itself in the form of metadata (GigE Vision and IP cameras can do that). I think the Basler IP cameras can use NTP and testify to the time stamp for metadata EXIF JPEG images that you can extract. This mechanism is of course much more precise because it eliminates the delay/jitter of transmission at the time. If you have a few requirements of precision (microsec, milliseconds, seconds?), it would probably give a better idea of what your options are.

  I suggest you take a look at the range of cameras from Basler IP. You can not control the parameters of the image directly in the IMAQdx driver (you must use their web interface, or write additional HTTP code), but once you have the configured device it will keep these settings.

  http://www.baslerweb.com/en/products/network-cameras/IP-fixed-box-cameras

  It is likely that the cameras will be more expensive that some cheaper GigE Vision cameras can be, but I suspect that you could save enough on other system costs will in this way to make up for it. In my opinion, doing compression JPEG on-the-fly with 350 + MB/sec of camera raw data could be difficult, unless you had a tough multi-core system.

  Eric

• GigE Vision all-in-package

  Hello

  I am looking for a solution to a simple problem. I designed the camera IRLS, work GVCP, camera stream UDP packets on request from Max NOR, but these packets are not acknowledged as data and Timeout 0xBFF6901B mistake. Enclosed I send my UDP all-in-package. The same happens on my laptop and the industrial controller WITH Intel network interface. Firewall is still disabled. On what parameters NI Max decides, the current package is the data package? UDP Port?

  I put the 1 value in the XML of my camera and my camera should support All in transfer. Should I put elsewhere too?

  What should I check?

  Kind regards

  Linus

  Hi Linus,

  This feature is new to 2.0, GigE Vision and not yet supported by IMAQdx. By specifying, this mode is optional on both sides and the application software is needed to activate it (SCCFGx) until the device is allowed to use this mode. As IMAQdx never allows it, the camera is required to use the transmission of standard packages.

  Eric

• XML file for GigE Vision camera

  Hello

  I'm working on a model of GigE Vision camera. It should be very simple linescan camera. I put in place the necessary set of registers GigE Vision, can communicate with the camera in MAX. The problem is that I need creata this XML file for the camera. There is this here XML file:

  http://www.EMVA.org/CMS/upload/standards/GenICam_Downloads/SFNC_Reference_Version_2_0_0_Schema_1_1.x...

  What should I do with it? My first version of the camera will have 2 functions: turn on and off I'm confused, because the model xml file has many functions, I don't really have. Should I remove them? Or leave it inside with default values? That she needs a configuration minimum XML file?

  Kind regards

  Linus

  Hi Linus,

  If you look at the GigE Vision specification, you will see that there is a minimal subset of functionality that must be present for the camera be declared compliant. That's all what IMAQdx will need for the camera works fine. All other functions in the XML file that you downloaded are part of the SFNC (features Standard Naming Convention) defines the names/behavior for common characteristics that are often found on machine vision cameras. As a general rule, cameras implement a subset of these features. You should not let any features that are not implemented in the XML because it would be just confused because they would do nothing.

  Eric

• GigE vision on OR cRIO-9068

  Hello:

  We are planning a project in which we intend to use embedded vision and transformation of vision GigE cameras. Our client is interested in the cRIO-9068 embedded platform.

  The question is: is there support for GigE Vision on the cRIO-9068?

  I can't find a document that says, so I guess that no public support is granted. If this is the case, I would like to know why.  I think that the VxWorks targets do not GigE support, but this cRIO running Linux. From the outside, I think it would be possible to provide a GigE for Linux support.  The only devices that seem to favor GigE run Phar Lap ETS.

  Thanks in advance for your kind reply.

  Just to answer he question, the 9068 does not support GigE Vision. Layer MAC Ethernet embedded on the chip of architecting it uses does not meet the requirements of GigE Vision (similar to the old cRIOs VxWorks/PPC).

  The 9068 does support USB3 Vision cameras via its USB 2.0 port well and a lot of GigE Vision cameras have identical models in variants of the USB.

  Eric

• Connection of the GigE Vision camera

  Hello

  I develop a GigE Vision camera.

  I want to connect GigE Vision Camera to NIMAX.

  When you first connect GigE Vision camera, I can see the NOR-IMAQdx list devices. ("cam0:mycamera")

  When I click on "cam0:mycamera", a the IMAQ error has occurred.

  Error message is "cannot load the XML of the camera.

  Attached file is the package that was the problem.

  MAX OR send command "Read memory" to retrieve the device XML configuration file.

  (Package no. 11, 13: address 0x200, 0 x 400 memory read command)

  GigE Vision camera send response.

  (No. 12, 14 package: XML URL first choice, second choice of URL)

  I think the number of package 12 and 14 are erroneous data, but I can't find the point of evil.

  Advice me please on this issue.

  I would be greateful to receive the sample package.

  Thank you.

  Hi hkgige,

  These questions can be better adapted to the Committee mailing list GigE Vision standard, I suppose that your company would be a member to develop a device with the GigE Vision standard.

  However, I take a look at your track of package and I don't see anything that looks obviously incorrect. One of the reasons why the software could stop after reading the two URLS, is that he thinks he has already downloaded the file previously. These are cached in a directory on your local system (usually C:\Users\Public\Documents\National Instruments\NI-IMAQdx\Data\XML on Vista and Windows 7). Check if you have the XML file for your camera.

  The error you get usually indicates GenICam has some difficulty in parsing the XML of your camera. If you join the XML itself, I could see if this is the problem.

  Eric

• export the extend script sequence

  Hello

  I want to export the sequence include the video and the title to extend script for adobe first pro

  The PProPanel example is this.

  Samples/PProPanel to master · Adobe-CEP/Samples · GitHub

• Camera GigE of NI VBAI lost packets

  We run VBAI on a fast PC with an Intel Pro/1000 card and a switch GigE of jumbo-frame to a large number of Basler Ace GigE cameras.

  It is understandable that multiple cameras cannot transfer complete images to the PC to the full flow of 1000 MHz because of the limited bandwidth between the PC and the Switch simultaneously.

  A way around this is to strangle the maximum for each camera down data flow so that the sum is not greater than 1,000 MHz.

  However, this means that transfers images always take more time, even if only a single camera to enter service, a large part of the time.

  What is a fundamental limitation of GigE Vision, or are smart enough work as soon as possible of the GigE Vision cameras... via returns package loses casual?

  Nelson

  We have found a solution.

  The problem is that the cameras, switch, network card and VisionBuiilder cannot treat all cases where more than one camera sends images to VisionBuilder where the total of the rates of data for these cameras is never more than 1 GB of band bandwidth network card.

  (It would be nice if someone did a network switch that has a little more package buffer memeory...) 100 MB?... so that the images of the garbage does not have the occasional collision while allowing most of the captures operate at maximum speed.)

  Solution:

  (1) we have added 3 ports on network 1 Gb additional to our pc of mink.

  (2) in order to redistribute traffic camera in more than one network port, we assigned to each network adapter and corresponding cameras, to a different subnet.

  (3) we have lowered the rate of data for less urgent cameras.

  Even after the lowering of the data rates for multiple cameras in NOR-MAX up to 200 Mb/s such as lost packets should no longer be possible, we stil seen.

  After a detailed examination, we found that the stages of acquisition image VisionBuilder are not careful the data rates that you assign to NOR-MAX and always default to 1000 MB/s maximum rate, so saturated flow and lost packets.

  The solution to this problem proves to be explicitly set to the flow desired in each stage of the acquisition of Image VisionBuilder, using the attributes tab.  While you're there, you should also check other critical parameters, such as the packet size, are also correct and update if not.

  After you explicitly fix rates given in every stage of image acquisition, we ran a stress test of capture image that ran all the process of vision (several programs running at the same time) about 10 times faster than necessary and observed no lost in all packets.

  Problem solved.

• Connection to CVS GigE camera via a network switch

  It is a fundamental and very simple question!

  I intend to connect two GigE cameras to NI CVS-1458RT for an application of Imaging. When I tested the configuration in MAX, I realized that I can connect the cameras directly to the PoE ports, or alternatively, connect the cameras directly to the network switch and in both cases, connect the CVS to my network via its ethernet port. I was wondering if there is a benefit by connecting directly the VCA cameras, if I do not anticipate supply their Poe or if my switch has PoE Betacam.

  Thank you

  Usually, you always want your cameras on dedicated lines, or at least only sharing bandwidth with other devices. The mechanism of transport used by GigE Vision isn't really sharing good bandwidth with other devices. If you only share the bandwidth on a link given with other devices, you can throttle each take only a percentage of the total bandwidth. If you have devices without camera on the link, they don't usually have a mechanism to control the gap inter-frame limitation insofar as GigE vision made which would be necessary for properly sharing the bandwidth without remove the packages of bandwidth.

  If you end up sharing one of the ports for the operation and configuration of the CVS on the network, you will be at the risk of losing image data packets whenever the rest of the traffic is sent. Although there are mechanisms in place to return data, these add latency and jitter to your purchase.

  Eric

• External triggering of GigE camera

  Hi, I'm planning on using the camera triggers the entry to start capturing images but I'm not sure what I need to do in my c# application when a trigger has launched.

  -If the trigger is coming from the PLC, should I also send a trigger signal to the PC and keep the active trigger signal until the PC is the acquisition of the image?

  -Do I still need use the snap or enter functions in imaqdx to get the picture?

  -If the camera is connected directly to the external NETWORK card triggering she still great benefits? The camera in less than 5 meters from the PC.

  Thank you

  Cliff

  Normal 0 false false false fr X-NONE X-NONE / * Style Definitions * / table. MsoNormalTable {mso-style-name : « Table Normal » ; mso-tstyle-rowband-taille : 0 ; mso-tstyle-colband-taille : 0 ; mso-style-noshow:yes ; mso-style-priorité : 99 ; mso-style-qformat:yes ; mso-style-parent : » « ;" mso-rembourrage-alt : 0 à 5.4pt 0 à 5.4pt ; mso-para-marge-top : 0 ; mso-para-marge-droit : 0 ; mso-para-marge-bas : 10.0pt ; mso-para-marge-left : 0 ; ligne-hauteur : 115 % ; mso-pagination : widow-orphelin ; police-taille : 11.0pt ; famille de police : « Calibri », « sans-serif » ; mso-ascii-font-family : Calibri ; mso-ascii-theme-font : minor-latin ; mso-hansi-font-family : Calibri ; mso-hansi-theme-font : minor-latin ;}

  Hi riscoh,

  When you work with a GigE camera you are not anything on the computer triggering its self, only the camera.  When it is configured to trigger it will sit and wait for a trigger.  When he received the signal it will take an acquisition and send the information to the computer.  When you set up your support on the computer it is searched for images and brings them into the computer as they become available.  The example I'm pointing you will show you how to set up the camera by a trigger program.  It looks like it may be available only in Visual C.  As far as the documents relate to article after the release with a GigE camera Developer area described briefly.  Acquisition of cameras GigE Vision with Vision Acquisition Software-part II

• How to make a simultaneous wink of GigE cameras?

  I have 2 cameras of 780-54gm Basler Scout (monochrome GigE) I switch to 10 Hz. This pace is modest and the data rate that results is not particularly high. I would like to get images from two cameras of the same trigger pulse. I have an Intel Pro/1000 NIC and I use the driver NEITHER appears so as National Instruments GigE Vision adapter. When I use the Basler pylon Viewer (the software that comes with the camera), I see perfect images from two cameras at the same time at 10 Hz. This tells me that the network, map NETWORK and the drivers can handle the flow of data without problem. I have activated jumbo frames. When I try to acquire images in LabVIEW 8.6 with screws IMAQdx, however, that I meet problems. I can acquire every single camera, but I can't them both at the same time strictly. The images are taken through with horizontal black lines that appear and move erratically. I have attached a vi that shows the problem. I have set up and start the two acquisitions, then enter a while loop that reads images. If I do the sequential acquisition by starting and stop them inside the loop and ensuring that we stop before the other then I get quality images but they are not the same impulses to trigger, and start and stop of the acuisitions overload slows down things so that I can not get pictures of each trigger. My guess is that it is a problem with how LabVIEW is the memory management, resulting in corruption with simultaneous acquisition. Are there settings I can change to fix this problem? I've experimented with everything I knew (buffer numbers, etc.), but without success. Rich P.S. I posted this in the forum LabView a couple of days but got no response. Sorry if you see this twice.

  Richard,

  Looks like you just packet loss. You might associate a property node to request lost packages to confirm. The reason for that happening is that even if the way to two cameras data rate is less than the limit of the NETWORK card, each camera probably goes to the complete 1000Mbit bandwidth when it transfers each picture. When transfers of images overlap, sending you to 2000Mbit/s down a 1000Mbit pipe and lose packets.

  To resolve this issue, an easy way is to adjust the attributes of Acquisition-> Ethernet advanced-> attribute peak bandwidth used for both cameras 500Mbit. This should ensure that each camera never use more than half of the bandwidth. There are also other options such as sprawl of transfer times, but those who require more tuning you change other settings.

  I don't know why the Basler software shows this, although their lack of bandwidth might just be lower at the expense of additional latency to get the images.

  Hope this helps,
  Eric

• How to identify a GigE camera by IP address

  I have a system with 8 Basler Ace GigE cameras, all on static IP addresses on the same subnet.  I would like to be able to exchange any device with a new one that is configured to the same IP and my LabView RT running on an Exchange virtual server program automatically starts using the new camera.  The LabVIEW program already sets the settings in the camera, if I don't want the user to have to use MAX for any configuration of the camera.  I want to just the user to use the Basler IP configuration tool and the tool of Basler to focus the camera, then having my program discover the camera by its IP address.

  However, I have not found an IMAQdx tool that allows me to distinguish the cameras by its IP address.  The discovering Ethernet cameras VI has an address entry, but it is only a mask and cannot me narrowly find just a single camera on an IP address.  I have not found any camera property or an attribute that returns the IP address.

  So, if I have a bunch of cameras and want to identify who is who, by his IP address, how can I do?

  Hi Ken,

  The main identifier imaqdx uses to track/locate cameras is serial number, which is identical to its MAC address for GigE Vision cameras in IMAQdx. Unfortunately us don't really use IP address as any kind of ID to connect with a specific camera, because we assume that the IP address can be dynamic and flexible (makes it spec GigE Vision DHCP and link-local addressing a requirement standard and everything is designed to allow these cases to work well).

  That said, there is an attribute called 'CameraInformation::IPAddress' that you can query to see the IP address of the camera. The only downside is we do not currently provide this information via the Enumerate mechanism - you first need to query this property of the device. Your application might first browse the cameras and do a mapping of serial to IP addresses?

  Hope this helps,

  Eric

• Different behaviors in MAX vs LabVIEW when writing the attribute IMAQdx GigE

  Hi, I'm controlling a Dalsa GigE camera in LabVIEW RT using IMAQdx.  Apart from a few quirks with interface we are image acquisition without a lot of problems at the moment.

  However, there are one or two issues that are confusing.  In this case, it is possible to set a MAX attribute (an attribute of command that tells the device to perform the internal calibration), but when you set the attribute in LabVIEW, the error 0xBFF69010 (-1074360304) unable to create the attribute is thrown.  See the attached images.

  I check if the attribute is writable before making an entry.  It is, however, the write failed, and read the iswritable attribute and then returns false.  In MAX, I can write to this attribute with no problems.

  I have to set up/read/write in my LabVIEW code that makes MAX.  MAX writes all the attributes (based on the values in the XML file) when he opens the camera or he reads simply all the values of the camera.  When LabVIEW opens a reference camera does perform the same steps that what MAX - I'm trying to figure out what could be the difference between MAX and LabVIEW, which might be the cause of this behavior.

  Any help will be appreciated.

  AnthonV wrote:

  Hi, I'm controlling a Dalsa GigE camera in LabVIEW RT using IMAQdx.  Apart from a few quirks with interface we are image acquisition without a lot of problems at the moment.

  However, there are one or two issues that are confusing.  In this case, it is possible to set a MAX attribute (an attribute of command that tells the device to perform the internal calibration), but when you set the attribute in LabVIEW, the error 0xBFF69010 (-1074360304) unable to create the attribute is thrown.  See the attached images.

  I check if the attribute is writable before making an entry.  It is, however, the write failed, and read the iswritable attribute and then returns false.  In MAX, I can write to this attribute with no problems.

  I have to set up/read/write in my LabVIEW code that makes MAX.  MAX writes all the attributes (based on the values in the XML file) when he opens the camera or he reads simply all the values of the camera.  When LabVIEW opens a reference camera does perform the same steps that what MAX - I'm trying to figure out what could be the difference between MAX and LabVIEW, which might be the cause of this behavior.

  Any help will be appreciated.

  Hi AnthonV,

  "Weird" is a good way to describe the Spyder3 when it comes to the GigE Vision/GenICam interface (as opposed to the Dalsa driver that communicates using custom commands via ethernet camera series)...

  The Spyder3 has many questions focused on the calendar. It is possible that the time between the opening of the camera and the setting of this function is different by MAX vs your code in LabVIEW. In addition, there are some cases where MAX will be deletes the error to display. Ignoring the error indicated vs you see the feature to take effect in both cases?

  The base between MAX and LabVIEW behavior is the same. In both cases when you open the unit all parameters are responsible for our camera file that has the registered device settings. This file is created the first time that you open the unit and are updated every time you click on save to MAX or call an API function to save the settings. In any case, I know that the Spyder3 has various questions backup/restore the settings of our camera files.

  I suggest talking with Dalsa on the issues you are experiencing. They might be able to put up with a newer firmware that addresses some of these issues (we have worked with them in the past to identify several of them).

  Eric

• dual GigE card

  I need to use 2 cameras gigE on a system and am looking for a dual port card, is there a favorite one to work with windows 7 and imaqDX drivers to connect with 2 gige cameras.

  AVT/Prosilica, we recommend the Intel Pro/1000 PT Dual Port card.

  ... works well with both:

  b two separate GigE Vision cameras and also with

  (b) 2 - port cameras GAL (Group aggregation of links) as the GX Series

  Scott

• Netzauslastung einer GigE-Bildverarbeitungskamera

  ICH eine Kamera um Bilder über ein GigE camera use a den PC zu senden. ICH weiss, dass die Kamera, wenn Bilder www.crownaudio werden approx. 520 übertragen Mbps, also would Netzwerkauslastung EIB approx. 70% liegen, trotzdem seht die Netzwerkauslastung im Taskmanager von Windows auf 0%. Gegebenen falls steigt bei der Anbindung ein bischen evil sharp. Jetzt mein question, was wird bei im Geratemanger displaying Windows? Nur die LAN-ranges? Merk Warum nicht, das sleeps ein riesiger Verkehr stattfindet? HAB auch schon andere Programme versucht, die bei alle stay 0%.

  There are possibility, die Ubertragungsrate andersweitig zu observes temporary ein? If necessary. uber den Slot PCI indem die Karte-LAN slides?

  Danke

  Google translation (sorry, I don't speak German):

  cplenk wrote:
  I use a camera to transfer pictures on a GigE to PC camera to send it. I know that the camera when the images are sent approximately 520 Mbit / s, so if the use of the network to about 70%, always sees the use of the network in 0% Windows tasks Manager. If applicable, these increases during the connection a bit. Now my question is what is in Windows Device Manager is displayed? Only the LAN protocols? Why it is not strange that there is a huge movement takes place? Have already tried other programs, which remain at 0%.

  Is there a possibility, the current rate of transmission also recognize? possibly through the card slot PSP LAN is connected?

  Thank you

  Danke

  When you use the National Instruments High Performance network driver for your network card (you should see this under the device instead of the Intel Pro/1000 normal driver manager), GigE Vision traffic bypasses the network stack and went before the network stack process. This is why it does not appear in the Task Manager.

  Wenn Sie die National Instruments High Performance Netzwerk-Treiber für die Netzwerkkarte (should sharp unter dem Geräte-Manager of the Intel Pro/1000 Treiber normal statt), GigE Vision Verkehr umgeht den Netzwerk-und ist wieder vor der them Netzwerk-stack stack. Der ist Dies Grund, warum're nicht im Manager of tasks.

  Hope this helps,

  Eric