Aquiring wrong data from camera

2 views (last 30 days)
Greg on 23 Apr 2014
Edited: Walter Roberson on 24 Feb 2017
Configuration: Win7-64x, matlab r2013b, camera JAI-5000M-cxp6x2, grabber activesilicon Firebird
I am able to capture the video with other programs shipped with the camera and the grabber, so it seems that drivers are fine, devices are set up as they should.
imaqtool starts with errors, but still starts. I am able to start preview and able to 'log' data to memory and to export it to matlab workspace. But streaming and captured data is unrecognizable, as if sensor is read out partly, the image is some noise.
Any ideas?
  1 Comment
Greg on 24 Apr 2014
More over... Imaqtool crashes while attampting to run it at full sensor resolution: ( below is crash dump )
MATLAB crash file:C:\Users\iuiuy\AppData\Local\Temp\matlab_crash_dump.3900-1:
Access violation detected at Thu Apr 24 13:32:28 2014
Crash Decoding : Disabled
Default Encoding : windows-1252
MATLAB Architecture: win64
MATLAB Root : C:\Program Files\MATLAB\R2014a
MATLAB Version : (R2014a)
Operating System : Microsoft Windows 7 Ultimate
Processor ID : x86 Family 6 Model 45 Stepping 7, GenuineIntel
Virtual Machine : Java 1.7.0_11-b21 with Oracle Corporation Java HotSpot(TM) 64-Bit Server VM mixed mode
Window System : Version 6.1 (Build 7600)
Fault Count: 1
Abnormal termination:
Access violation
Register State (from fault):
RAX = 000000006f380000 RBX = 0000000000000217
RCX = 0000000013e8eee0 RDX = 000000005b4f1120
RSP = 000000012836fa48 RBP = 0000000000000a00
RSI = 0000000013e8e640 RDI = 000000006f37f760
R8 = 0000000000000a00 R9 = 000000000000000b
R10 = 0000000000000000 R11 = 0000000013e8e640
R12 = 00000000692b75b0 R13 = 0000000000000a00
R14 = 0000000000000000 R15 = 0000000000000000
RIP = 000000007048c010 EFL = 00010202
CS = 0033 FS = 0053 GS = 002b
Stack Trace (from fault):
[ 0] 0x000000007048c010 C:\Program Files\MATLAB\R2014a\bin\win64\MSVCR100.dll+00245776 memmove+00000176
[ 1] 0x000000001e0a16ee C:\Program Files\MATLAB\R2014a\bin\win64\tamimframe.dll+00071406 imaqframekit::MemoryLimiter::MemoryLimiter+00000254
[ 2] 0x000000001df9f7cf C:\Program Files\MATLAB\R2014a\toolbox\imaq\imaq\imaqmex.mexw64+00194511
[ 3] 0x000000001e1ae8ed C:\MATLAB\SupportPackages\R2014a\gentl\adaptor\win64\mwgentlimaq.dll+00190701
[ 4] 0x000000001e1c318c C:\MATLAB\SupportPackages\R2014a\gentl\adaptor\win64\mwgentlimaq.dll+00274828
[ 5] 0x000000001e1b4723 C:\MATLAB\SupportPackages\R2014a\gentl\adaptor\win64\mwgentlimaq.dll+00214819
[ 6] 0x0000000072674eb1 C:\Program Files\MATLAB\R2014a\bin\win64\boost_thread-vc100-mt-1_49.dll+00020145 boost::thread::~thread+00003009
[ 7] 0x0000000070471d9f C:\Program Files\MATLAB\R2014a\bin\win64\MSVCR100.dll+00138655 endthreadex+00000067
[ 8] 0x0000000070471e3b C:\Program Files\MATLAB\R2014a\bin\win64\MSVCR100.dll+00138811 endthreadex+00000223
[ 9] 0x0000000076e3f56d C:\Windows\system32\kernel32.dll+00128365 BaseThreadInitThunk+00000013
[ 10] 0x0000000076f73281 C:\Windows\SYSTEM32\ntdll.dll+00209537 RtlUserThreadStart+00000033

Sign in to comment.

Answers (1)

Walter Roberson
Walter Roberson on 24 Apr 2014
Did you specify the colorspace to return?
  1 Comment
Greg on 24 Apr 2014
Hi, Walter, thanks for reply. ColorSpace property was set by default as 'grayscale'. Now I've tried 2014 ver of Matlab just now, hoping some new features were added, since gentl is rather modern transport layer. In 2014 matlab preview starts (aquistion does not) but the screen is absolutely black. And it seems data logging doesnt occur and no export to workspace is available...

Sign in to comment.

Community Treasure Hunt

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

Start Hunting!

Translated by