08-04-2012 12:21 AM
Hello,
I am using an IDS uEye camera and accessing it through a direct show driver in vision acquisition software. I am receiving an windows kernel error when I try to open the camera for the first time from an application instance.
The same error occurs if I want to open the camera from MAX or running a LabVIEW code. The error does not pop up if I run the LabVIEW code as an built executable.
Error :
Translated : Entry point of a procedure ?initia.... could not be found in the noted dll.
I successfully duplicated this error on two clean windows7 installs with latest vision acquisition software.
Funny thing is that on a computer that is very messy (many perquisite driver installations), this error does not occur.
I would like to know, what software does LabVIEW and MAX call/use when opening cameras.
Snippet of the code, that produces the error:
All three IMAQdx functions do not return any labview runtime errors and otherwise everything works OK!
08-05-2012 07:50 PM
Hi,
That DLL is Intel's TBB (Threading Building Blocks) library. The NI Vision DLLs use those for some purposes. My hunch would be that some other software loaded into the LabVIEW process (likely the IDS drivers) has loaded a (different) copy as well and it is conflicting. You could look in your Windows\System32 (or SysWow64) directories for the DLLs with TBB in the name and compare them on the working vs non-working system.
Eric
08-06-2012 04:02 AM
Thanks for reply,
I allready tried to replace the "working machine" DLLs instead of those "not working so well machine" ones.
No success 😞
I will try to duplicate the Vision tbb.dll into system 32
08-07-2012
04:09 AM
- last edited on
04-01-2025
09:09 AM
by
Content Cleaner
Hello Bublina,
please try to install http://sine.ni.com/devzone/cda/epd/p/id/5030 software and also run procedure mentioned on http://digital.ni.com/public.nsf/websearch/3EB8C8AFC1593B4A8625712E0002869B?OpenDocument . If this does not help, do not hesitate to write a post.
Martin
08-07-2012 04:13 AM
Hi,
It is not an USB camera, the vision acquisition software supports direct show cameras directly without that software.
I am afraid this is no help for me.
08-08-2012 03:28 AM
Hi Bublina,
may a ask you are using DS API instead of direct LabVIEW interface that is available on vendor's web?
Ondřej
08-08-2012 03:35 AM - edited 08-08-2012 03:37 AM
You mean to ask me, to use their API instead of directshow ? If so, I will not.
There are several reasons:
1) Getting the snapshot is slower.
2) It costs whopping 33% of CPU time to grab 3 FPS from one camera (5MPix) due to the fact the DLL returns the data as flat array and I need to convert it into vision.
3) The DS Api is using a deprecated vision function - array2vision.
4) I cannot obtain a coloured picture (so far, might be caused by problem 3, I didnt look into it that much).
08-09-2012 04:46 AM
Hello Bublina,
try to use different directshow device from another vendor. If error will still appear, problem is in directshow driver.
Martin
08-11-2012 01:11 PM
@AECmartin wrote:
Hello Bublina,
try to use different directshow device from another vendor. If error will still appear, problem is in directshow driver.
Martin
Hi,
do you really think it is a driver problem, since this error does not occur in built executable and does not occur on different pc with different NI software (and other software, but same directshow driver) ?
Unfortunately, I do not have any other direct show devices to try it out.