Garbled image in MAX from GigE camera

[tst]

I'm trying to work with a GigE camera (first time doing vision, so be gentle) and I'm getting stuff like this:

This happens with all the formats I choose. The application from the vendor does return a correct image. The notes that came with the camera (a PixeLINK 761G) say it's not GigE compliant, but they are a year old and it does seem to mostly work in MAX. I'm trying to get answer from the vendor, but was just wondering if anyone had any idea.

Message Edited by tst on 03-09-2009 04:49 PM

[tst]

Some further details - I think this is a test image. The camera has a TestImageSelector field which was set to "IPEngineTestPattern". When I set it to "Off", I get a timeout. I tried the things suggested here (including disabling the firewall) but they did not help. The Ethernet card I'm using is a Gigabit Ethernet card, but it is not an Intel Pro/1000.

[BlueCheese]

tst,

That is indeed a test image coming from the camera. The fact that you can get that ok indicates there is no issue with receiving the GigE Vision data via IMAQdx so you shouldn't need to try any other steps along those lines. IMAQdx doesn't care if the camera is sending a test image or real image data; it all looks the same to it.

The timeout you are getting indicates the camera is simply not sending data from the sensor. This may be due to an incorrect triggering setting or some other settings on the camera. You may want to consult the camera vendor to see what attributes you may need to change to get it to work. The fact that the default settings seem to be set to send a test image seems a bit odd in the first place. Unfortunately all those attributes are completely controlled by the camera itself and since I have not used that particular camera I cannot guess what settings you may need to change.

The reason the application from the vendor can grab a real image is most likely because it uses a different protocol than the standard GigE Vision spec to access it.  Many cameras that have an older imaging front-end connected to a third-party GigE Vision backend (which I believe your camera likely is) work in this manner with the vendor-specific application sending encapsulated serial commands over Ethernet, something which the GigE Vision spec does not allow. When connected to a GigE Vision compliant application, the application instead sends register read/write commands which are translated on the third-party backend into serial commands. You may have some luck using the vendor's application to configure the camera and save the settings to the camera, then using it within IMAQdx.

Eric 

Message Edited by BlueCheese on 03-09-2009 10:39 AM

Message Edited by BlueCheese on 03-09-2009 10:40 AM

[tst]

---

This may be due to an incorrect triggering setting or some other settings on the camera.

...

Unfortunately all those attributes are completely controlled by the camera itself...

---

Thanks, both of these are educational points for someone who doesn't know the stuff yet.

---

The reason the application from the vendor can grab a real image is most likely because it uses a different protocol than the standard GigE Vision spec to access it.

---

That sounds quite likely. PixeLINK have an SDK, which is even supposed to have some wrapper VIs, which I haven't been able to find, as their site sucks in that respect. I won't be in the office tomorrow, but hopefully I should have answers by Wednesday, and even if not, you gave me some leads. I'll report back when I have an answer.

Message Edited by tst on 03-09-2009 08:20 PM

[tst]

OK, according to the response I got back from PixeLINK (through the seller), the camera's firmware is not GEV-compliant, which is kind of weird, since it does work partially. In any case, they said they're expecting to have a GEV-compliant firmware by the end of this month.

[logatto]

Hi tst, I have exactly the same problem with a PL-B781G. Did you fix It? News from PixeLINK?

Thanks a lot

[tst]

They have new firmware which worked for me. You should talk to them to get it too. I got it from the disributor, not from their site.

One thing to note was that the camera was set to a maximum resolution of 320x240. There are attributes you can change in MAX to change this. It appears under "PixeLINK features" or something similar in the tree.