03-01-2018 07:59 AM
Hi guys
We had software for a FLIR AX5 thermal camera that worked perfectly.
The camera started giving problems in the field and we had to replace it with a newer version with the latest firmware.
No I can't seem to communicate with the new camera.
MAX tells me that it's unable to get attribute.
Error 0xBFF69011
Anybody else had this problem and how did you solve it?
Thanks in advance.
03-02-2018
09:26 AM
- last edited on
12-20-2024
12:30 PM
by
Content Cleaner
Hi 1unidude,
Is this camera on the same system that was previously working?
When a GigE camera is first loaded in NI MAX, we try to pull the configuration information from the camera to store locally as the initial configuration file. If there's an attribute that cannot be read or is not valid, the error you are seeing can result.
1. What version of the IMAQdx driver are you using on that system?
2. Let's try clearing out all of the related camera files on that system. You can find these at the following location, and you want to delete the *.icd and XML files (in the XML folder) associated with the camera model you are using. Make sure to disconnect the camera before doing so. After deleting the files, reconnect to the camera in NI MAX which should regenerate the files.
<Users>\Public\Documents\National Instruments\NI-IMAQdx
3. If you haven't already, I would simply recommend checking everything in the following document. I don't know that it applies given that this worked in the past and only the camera changed, but it's worth checking.
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000YM6JCAW&l=en-US
03-07-2018 02:18 AM
Hi Charlie
Thanks for the valuable help.
The camera is still on the original system but I've also moved it onto a new system with a fresh installation.
Still no luck.
I can open the camera in LabVIEW using IMAQdx.open.camera and I can enumerate the attributes but if I try to get a image from the camera it gives me all sort of errors.
Operating System(OS) Windows 8 Home Edition
OS Version 6.02.9200
OS Info
Processor Intel(R) Core(TM) i3-6100U CPU @ 2.30GHz / Intel64 Family 6 Model 78 Stepping 3 / GenuineIntel / 2304 MHz
Number of Processors 4
Physical Memory 3,90 GB of RAM
Drive C:\ 800 GB of 930 GB free
National Instruments Software: Version:
CompactRIO 14.0.0
C Series Module Support 14.0.0
CVI 13.0.2
Real-Time 13.0.1
CVI AddOns LabWindows/CVI Shared AddOns
PID Toolkit 2.1.0
Profiler Toolkit 1.0.0
Real-Time Trace Viewer - CVI Support 14.0.0
Signal Processing Toolkit 7.0.2
SQL Toolkit 2.2.0
CVI Run-Time 13.0.2.278
NI-DAQmx Device Driver 14.0.0f0
NI-DAQmx ADE Support 14.0.0
NI-DAQmx MAX Configuration 14.0.0
DIAdem 2014 14.0.0.5641
NI-488.2 Runtime 14.0.0
NI-488.2 14.0.0
NI-IMAQ 14.0.0
Development Support 14.0.0 14.0.0
Runtime 14.0.0 14.0.0
NI-IMAQ I/O 14.0.0
Development Support 14.0.0 14.0.0
Runtime 14.0.0 14.0.0
Vision Common Resources 14.0.0
Image Processing and Machine Vision 14.0.0.49155
Image Services 14.0.0.49155
NI I/O Trace 14.0.0f0
IVI Compliance Package 14.0
LabVIEW 14.0.0
Advanced Signal Processing Toolkit 14.0.0
Analog Modulation 4.4
Control Design and Simulation Module 14.0.0
Database Connectivity Toolkit 14.0.0
DataFinder Toolkit 14.0.05640
Datalogging and Supervisory Control 14.0.0
Digital Filter Design Toolkit 14.0.0
Digital Modulation 4.4
FPGA 14.0.0
MathScript RT Module 14.0.0
NI SoftMotion 14.0.0
Real-Time 14.0.0
Real-Time Trace Viewer - LabVIEW 2014 Support 14.0.0
Report Generation Toolkit For Microsoft Office 14.0.0
Sound and Vibration Measurement Suite 14.0.0
Sound and Vibration Toolkit 14.0.0
Spectral Measurements 2.7
Statechart Module 14.0
Unit Test Framework Toolkit 14.0.0
VI Analyzer Toolkit 14.0.0
Vision Development Module 14.0.0
LabVIEW Run-Time 2010 SP1 10.0.1
LabVIEW Run-Time 2013 SP1 f3 (64-bit) 13.0.1
Measurement & Automation Explorer 14.0.0f0
Measurement Studio Visual Studio 2005 Support - See individual versions below.
DotNET
Common 12.0.20.258
Vision
Measurement Studio Visual Studio 2008 Support - See individual versions below.
DotNET
Common 13.0.35.190
Common (64-bit) 13.0.35.190
Vision
Measurement Studio Visual Studio 2010 Support - See individual versions below.
DotNET
Common 13.0.40.190
Common (64-bit) 13.0.40.190
NI-USI 14.0.0.5640
NI-IMAQdx 14.0.0
Development Support 14.0.0 14.0.0
Runtime 14.0.0 14.0.0
NI PXI Platform Services Configuration 14.0.0f0
NI PXI Platform Services Runtime 14.0.0f0
NI-RIO 14.0.0
NI R Series Multifunction RIO 14.0.0
NI FlexRIO 14.0.0f1
NI-PAL Software 14.0.0
NI-Serial Runtime 14.0.0f0
NI-Serial Configuration 14.0.0f0
NI SignalExpress 14.0
Switch Executive 3.6.0.49154
NI System Configuration 14.0.0f0
NI TestStand 2014 2014
NI TestStand Run-Time 2014 14.0.0.274
NI TestStand Sequence Editor 2014 14.0.0.274
NI TestStand 2014 (64-bit) 2014
NI TestStand Run-Time 2014 (64-bit) 14.0.0.274
NI TestStand Sequence Editor 2014 (64-bit) 14.0.0.274
NI-VISA 14.0
NiVisaServer.exe 14.0.0.49152
NIvisaic.exe 14.0.0.49152
NI-VISA Runtime 14.0
Vision Builder AI 13.1.0
Vision Development Module 14.0.0
Runtime Support 2014 14.0.0
Development Support 2014 14.0.0
Vision Assistant (32-bit) 14.0.0
LabVIEW Run-Time 2011 SP1 f5 11.0.1
LabVIEW Run-Time 2012 SP1 f9 12.0.1
LabVIEW Run-Time 2013 SP1 f3 13.0.1
LabVIEW Run-Time 2014 14.0.0
03-07-2018
02:30 PM
- last edited on
12-20-2024
12:31 PM
by
Content Cleaner
Hi 1unidude,
Are the errors on both computers the same? Or are you seeing completely different behavior?
For sharing software versions in the future, I would recommend just uploading an NI MAX report. It's much easier to read and keeps the discussion clear on the forums.
Did you try any of the steps I outlined in my previous post? I highly recommend going through the guide called out in my third suggestion if you tried a new computer. It might not have everything configured properly for GigE acquisition.
01-27-2025 02:22 PM
I had a similar experience with a Flir like yours. In my case it turned out that LV2017 was the last version supporting GeniCam x. The later LV versions do not look back and are GeniCam X+1, which is not compatible with the Camera firmware in GeniCam X. The good news is this is thoroughly confirmed by NI and the manufacturer. Hower there is no resolution that I am aware of. The manufacturer will not update the firmware, and NI can't fix the old Genicam version.
So, on a positive note, you don't have to troubleshoot any further. I am not aware of any fix since I reported the problem.
01-27-2025 02:47 PM - edited 01-27-2025 02:49 PM
I am using the A700 without issues. I dont think they are very different from the GigE perspective. You could install old firmware on the camera, aswell.
The only problem I can imagine is that your 'max packet size' is greater than 1500
01-28-2025 08:39 AM
I have an A35 I think. It's in the factory used for production. The camera works fine all day long. I do have the MTU size set to 9000 on the windows PC. My understanding/experience is that the performance would not be as fast with the 1500 bytes default setting. These are the manufacturer recommended settings for my configuration. The only problem I have is I can't get anything after 2017 to work with the camera.
NI worked with me for months to identify that LabVIEW 2018 and later implement the latest GeniCam standard. However backward compatibility with the previous GeniCam standard is not possible.
My understanding is that my camera is not going to get updates due to end of life status at Flir. I do have the latest firmware and have confirmed with them the current state of GeniCam for my camera does not implement the new updated standard.
01-28-2025 09:46 AM - edited 01-28-2025 10:15 AM
IMAQdx is nothing to worship. FLIR offers for sure a C library you could interface from LabVIEW by Call library node. And then there are the .NET interfacing options I never used.
In the end you only need the core core acquisition methods, since you can setup the complete camera using any Genicam Editor out there.