Pleora NTx Mini module and imaqtool

7 views (last 30 days)
Andrei Tunea
Andrei Tunea on 13 Oct 2011
Hi there!
I am trying to acquire images from a custom designed GigE camera with the MATLAB image acquisition toolbox. The camera uses a Pleora NTx Mini Module for the gige connectivity.
The connection goes well, after recognizing the camera, the pixel types are listed but there is a problem with the resolution. In the default Pleora software i set the resolution to, say, 640x480. It all works well, i get a perfect live image.
But the imaqtool shows some weird values for the resolution 16376x16383. Also i can't change the Width and Height. The values for resolution are read-only.
Is this a problem of the Pleora module? Of the xml file it delivers to matlab, when the videoinput object is created?
for any ideas -> thanks in advance, Andrei
  2 Comments
Andrei Tunea
Andrei Tunea on 14 Oct 2011
Hi! Just in case someone else has the same problem:
Problem solved (or at least half-solved). The guys from Pleora said: The imaqtool is reading the "SensorWidth" and "SensorHeight" parameters from the xml file.
To set those, you need another software tool called AutoGEV, also from Pleora(that's why "half-solved").
Greetings,
andrei
gerard ditaranto
gerard ditaranto on 17 Oct 2011
if you set the image size with AutoGEV can matlab acquire images? I have a similar problem, i can get genicam to work, national instruments "measurement and automation" explore to work. matlab imaqtool will recognize i have it attached but fails to preview the image, it thinks the size is as you stated when it is really 1024x768

Sign in to comment.

Answers (2)

Geoff Roddick
Geoff Roddick on 19 Oct 2011
Andrei & Gerard,
The default for our IPengines is to present the largest possible sensor in the XML file. This allows our customers to get going quickly as they can then change the height and width fields to match what the sensor actually is. For our OEM camera developers we have our AutoGEV tool as Andrei has mentioned which allows you to customize the XML file. One of the first entries that is customized is the sensor size to reflect the actual size in the camera. (for further information see: http://www.pleora.com/our-products/iport-video-transmitters/autogev-xml-development-tool ).
If you need a quick fix Pleora can provide you with a temporary version of the firmware which can reduce the sensor size in the XML file. Please contact Pleora through the support case you already have open (or e-mail support at Pleora) to request this firmware.
Geoff Pleora Technologies
  1 Comment
Andrei Tunea
Andrei Tunea on 20 Oct 2011
Hi Geoff!
Thank you for your answer. I will request the temporary firmware later today.
Andrei

Sign in to comment.


Mark Jones
Mark Jones on 19 Oct 2011
Hi,
There is one thing that you should do:
Ensure that Width.Max is correct at all times (and the same for Height).
And there is another additional thing that is completely optional (as WidthMax/HeightMax are not required features):
Ensure that WidthMax is defined as the maximum width allowed for Width with OffsetX of 0 (and the same for HeightMax)
For more details, see Figure 4-1:
SensorWidth is read, but that is not required to be defined.
Mark
  1 Comment
Andrei Tunea
Andrei Tunea on 20 Oct 2011
Hi Mark!
Do you mean setting the ROIPosition parameter from [0 0 16376 16383] to [0 0 640 480]?
This doesn't work, I get the error:
"gige: The frame size has changed from 16376x16383 to 640x480 during the acquisition. Ensure that you are not attempting to
perform a sequenced acquisition with a varying region of interest (ROI)."
The thing is: I did not change the ROIPosition during the acquisition.
I will try what Geoff recommended, and also to change the SensorWidth and SensorHeight with AutoGEV and then post the results.
Andrei

Sign in to comment.

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!