MATLAB Answers

Issue with Device-Specific Properties with GigE camera

10 views (last 30 days)
KCRobot
KCRobot on 1 Nov 2016
Answered: Madhura Suresh on 10 Nov 2016
I am using the IMAQ toolbox to get video from a Prosilica GS650 GigE camera. I'm trying to use an external hardware trigger to get a certain number of frames of continuous acquisition. I think I should be able to do this by setting src.TriggerSelector to 'AcquisitionStart' and src.TriggerSource to 'FixedRate,' but this results in an error: 'The enumerated property should have contained the IMAQ value.' I can't find any documentation for this error message and I'd really appreciate any help with what it means and what I can do to get around it. Note: the list of device-specific properties in MATLAB doesn't match the names of those properties given in the manual for my camera, which has contributed to a lot of confusion over which property does what. It's very possible that I'm not using the right properties for what I'm trying to do, but if so I'm not sure how to figure out what the right ones are since the documentation doesn't match up.
Here's the list of properties in MATLAB:
Device Specific Properties:
AcquisitionFrameCount
AcquisitionFrameRateAbs
BalanceRatioAbs
BalanceRatioSelector:[ {Red} | Blue ]
BalanceWhiteAuto:[ {Off} | Continuous | Once ]
BalanceWhiteAutoAdjustTol
BalanceWhiteAutoRate
BandwidthControlMode:[ {StreamBytesPerSecond} | SCPD | Both ]
BinningHorizontal
BinningVertical
DSPSubregionBottom
DSPSubregionLeft
DSPSubregionRight
DSPSubregionTop
ExposureAuto:[ {Off} | Continuous | Once ]
ExposureAutoAdjustTol
ExposureAutoAlg:[ {Mean} | FitRange ]
ExposureAutoMax
ExposureAutoMin
ExposureAutoOutliers
ExposureAutoRate
ExposureAutoTarget
ExposureMode:[ {Timed} ]
ExposureTimeAbs
GainAuto:[ {Off} | Continuous | Once ]
GainAutoAdjustTol
GainAutoMax
GainAutoMin
GainAutoOutliers
GainAutoRate
GainAutoTarget
GainRaw
GainSelector:[ {All} ]
IrisAutoTarget
IrisMode:[ {Disabled} | Video | VideoOpen | VideoClosed ]
IrisVideoLevelMax
IrisVideoLevelMin
PacketDelay
PacketSize
StreamBytesPerSecond
StreamHoldEnable:[ {Off} | On ]
StrobeDelay
StrobeDuration
StrobeDurationMode:[ {Source} | Controlled ]
StrobeSource:[ {FrameTrigger} | AcquisitionTriggerReady | FrameTriggerReady | Exposing | FrameReadout | LineIn1 | LineIn2 ]
SyncOutLevels
SyncOutPolarity:[ {Normal} | Invert ]
SyncOutSelector:[ {SyncOut1} | SyncOut2 | SyncOut3 ]
SyncOutSource:[ {FrameTrigger} | GPO | AcquisitionTriggerReady | FrameTriggerReady | Exposing | FrameReadout | Imaging | Acquiring | LineIn1 | LineIn2 | Strobe1 ]
TriggerActivation:[ {RisingEdge} | FallingEdge | AnyEdge | LevelHigh | LevelLow ]
TriggerMode:[ {On} | Off ]
TriggerSelector:[ {FrameStart} | AcquisitionStart | AcquisitionEnd | AcquisitionRecord ]
TriggerSource:[ {Freerun} | Line1 | Line2 | FixedRate | Software ]

  0 Comments

Sign in to comment.

Answers (2)

Keerthana Chivukula
Keerthana Chivukula on 4 Nov 2016
To understand the issue better, try the following steps:
1. Is the 'TriggerType' property set to 'hardware'? 2. Try using 'propinfo' function to know more specific details about the properties that you are trying to set.Refer to the documentation link below: http://www.mathworks.com/help/imaq/use-advanced-property-support-in-the-gige-vision-and-genicam-gentl-interfaces.html#bu80mqi
3. How are you creating the object?(sample code could be helpful). You can also refer to the following documentation link to know the advantages of using gigecam object vs. videoinput object: http://www.mathworks.com/help/releases/R2016a/imaq/gige-vision-acquisition-gigecam-object-vs-videoinput-object-1.html

  0 Comments

Sign in to comment.


Madhura Suresh
Madhura Suresh on 10 Nov 2016
Hi KCRobot,
Have you tried using gigecam? That should match more closely with the GigE Vision standard.

  0 Comments

Sign in to comment.

Sign in to answer this question.