Error Start/Stopping drawing control: Device is already capturing images
AnsweredHi there,
I am using the following device on a Windows 10 PC:
DeviceDisplayName Point Grey Research Grasshopper3 GS3-U3-41C6NIR
DeviceModelName Grasshopper3 GS3-U3-41C6NIR
DeviceID USB\VID_1E10&PID_3300&MI_00\6&1538D109&0&0000
DeviceType USB3Vision
DeviceVendorName Point Grey Research
DeviceInstanceId USB\VID_1E10&PID_3300&MI_00\6&1538D109&0&0000
DeviceCurrentSpeed SuperSpeed
DeviceAccessStatus OpenReadWrite
DeviceVersion FW:v2.15.3.00 FPGA:v2.02
DeviceDriverVersion PGRUSBCam3.sys : 2.7.3.249
As of this morning, I can no longer use the device through SpinView (2.3.0.77) or FlyCapture2 (2.13.3.61). While the device is listed in Spinview and in my PC Device Manager, it is not listed in FlyCap. I have tried disabling, restarting, and enabling the device as well as re-installing Spinview. One of two errors are consistently thrown:
Error Start/Stopping drawing control: Object reference not set to an instance of an object.
Error Start/Stopping drawing control: Device is already capturing images.
LOG_LEVEL_ERROR 11/28/2023 11:49:00 AM SpinnakerNETGUI SpinView.SpinView_WPF System.Exception: Device is already capturing images.
at SpinnakerNET.GUI.WPFControls.DXImageDrawingWindow.Start()
at SpinnakerNET.GUI.WPFControls.ImageDrawingControl.btn_Start_Click(Object sender, RoutedEventArgs e)
at SpinnakerNET.GUI.WPFControls.ImageDrawingControl.Start()
at SpinView.SpinView_WPF.OnCameraDoubleClicked(IManagedCamera cam, Boolean createStreamingWindow, Boolean startAcquisition)
Any troubleshooting help would be greatly appreciated! Thank you.
-
Official comment
Hello,
Thank you for your help!
There are no specific changes I could point to, as the problem actually started after not having used the camera for over a week. The only thing I could imagine would be if our IT department pushed an update during this time that I was unaware of.
I am using an older version due to separate machine vision tracking software (FicTrac) working better with older versions.
The problem also persisted when I plugged in a camera of the same model, as well as when I plugged the same camera into a different computer. However, I was able to download a more recent version of FlyCapture2, and use that to both update the Firmware and clear the memory channel on the camera. That appeared to resolve the problem. Unsure what triggered the problem in the first place. But at least it is resolved! -
Hi Matthew,
Could you recall any changes (especially software based) prior to initial observation of this issue?
Exception "Object reference not set to an instance of an object." mostly point to using wrong dll to open an application.Therefore, I would recommend to uninstall all spinnaker and flycapture sdks in this machine, and perform a fresh installation.
Is there any special reason using spinnaker 2.3.x version? If not, I would download and install latest sdk version from our website:https://www.flir.eu/products/spinnaker-sdk/?vertical=machine+vision&segment=iis
Regards,
Ifeanyi0 -
Hi Matthew,
I just wanted to make sure you saw my last email.
Please let us know if you have any questions about it.
Best Regards,
Ifeanyi
0
Please sign in to leave a comment.
Comments
3 comments