-17502: System Level Exception in Run Time

[logatto]

Hi, have an issue on the managment of IDS uEye cameras in TestStand 4.2.1.

When I use the LabView2009 development system everything work fine. When select the Runtime adapter I have a -17502: System Level Exception.

I create a debug test sequence that makes the following actions:

Open Camera

Close Camera

Open Camera

Close Camera

Open Camera

Close Camera

At the third Close Camera instruction I've got the -17502: System Level Exception. The dll and the VI that manages the camera does not return any kind of error, but when the VI is finish the execution  and return to TestStand the execution breaks with error.

I am using uEye32_39000 driver with Windows 7.

Do you have any ideas?

Thanks a lot.

[sonotk]

Have you tried stepping into the VI and Dll? Error may still be happening in calling code module but likely not properly reported back in TestStand. 

[Norbert_B]

In addition to sonotk's suggestion, i advise you to take a close look on the parameters of the modules. The exception error can be an indication of memory corruption due to buffer overflows. This can happen if you pass data to/from a code module using arrays/strings.

Since you are working with images, you are using arrays....

hope this helps,

Norbert

[logatto]

The dll and the VI does not return any error code. I will check the data passed to/from code mudule. But what is strange is that this happened only with run time. With development system everything works fine.

Thanks.

[logatto]

The dll and the VI does not return any error code. I will check the data passed to/from code mudule. But what is strange is that this happened only with run time. With development system everything works fine.

Thanks.

[Norbert_B]

Do you have a small test program written solely in LV where you can test if the camera interface runs in the RTE at all?

Another hint regarding the buffer overflow theorie:

Take a look into the TestStand debug options (Station Options >> Preferences)

Norbert

[logatto]

No, not solely in LV. I will do it.

Good hint, I will try it too.

Now the machine is in field to the customer then I have to wait his availability.

Thanks.

[pwaszkewitz · Accepted solution]

No idea, if this is related, but we had the problem with the uEye drivers that after a "CloseCamera" we would get an -17501 error in TestStand due to OLE marshalling problems.

IDS then included an option in the driver to switch of OLE initialization. With version 3.90, which you are using, this is now part of the official driver release.

Under the registry key:

  HKLM\SYSTEM\CurrentControlSet\services\ueye\Parameters

you need a REG_DWORD value CoInitializeMode. When this value is

  CoInitializeMode = 1:
 

then CoInitialize/CoUninitialize is only done when DirectDraw is enabled (in Halcon this is done with the is_SetDisplayMode() operator).

Regards

Peter

[logatto]

GREAT! GREAT! GREAT!

I created a REG_DWORD value CoInitializeMode =1 and it fixed the system level exception.

Thanks guys.