General Information
Current node value:
{
“Command”: null,
“Parameters”: null,
“PersistentParameters”: false,
“Result”: {
“ErrorSymbol”: “UEyeApiException”,
“ErrorText”: “UEye API error 3 (An attempt to initialize or select the camera failed (no camera connected or initialization error).) at </uEye/src/uEyeCamera.cpp:1544>.”,
“Execute”: {
“Command”: “UpdateFirmware”,
“Parameters”: {
“Camera”: “Allow”,
“Cameras”: [
“182187”
],
“OpenMP”: {
“Dynamic”: 1
},
“Projector”: “Allow”,
“Threads”: 10
}
}
},
“Status”: {
“LatestMessage”: “Update firmware for camera ‘182187’…”,
“Messages”: [
“Update firmware for camera ‘182187’…”
],
“Progress”: null,
“Time”: 4.587699999999999889
}
}
Problem / Question
Just started the device again after about a month, before it worked fine.
It detects a UI524xTE-M, even though it is a 3D camera…
Do you have an idea what to do here?
Hi,
unfortunately that error is a generic one from the uEye API that just happens sometimes. Have you tried it multiple times? Sometimes, it just fixes itself.
If not, can you please try to open the “IDS Camera Manager” application (should have been installed with the uEye driver), select your camera from the list and click on “Upload starter firmware”.
The detection as the wrong model is due to the wrong firmware. What you see in the list is the underlying IDS camera. The fact that this is an N-series camera is stored in its EEPROM, which the NxLib cannot read until the camera works.
Hi Daniel,
Thanks for your reply. Sadly I did not manage to get in running on my PC.
Another PC is running it fine, so its not due to the camera or its EEPROM settings.
Reinstalling the full Ensenso SDK 4.1.1033 doesn’t help either. Any idea what it might be locally on my PC?
You can try to reinstall the uEye driver as well. Please use the recommended version from our download page.
Uploading the starter firmware from the IDS Camera Manager worked or did it show any error?
Thank you for your help Daniel. Reinstalling the uEye driver worked.
Then the new firmware version for the N35 camera was available and updating fixed it.
