11-03-2025 09:53 PM
Dear NI Technical Support Team,
We have some technical questions regarding our FLIR-X8581HS-SLS camera and its filter-wheel control.
Currently, i use LabVIEW Imaq module to control the FLIR Camera, realize the rotate the filter wheel. but, there is a problem.
Specifically, we often need the filter wheel to rotate by +-90° to switch to the next/last filter. However, it constantly rotates an additional round (360 degrees) before reaching the desired destination, which significantly slows down our data acquisition. We notice that if we let it rotate by 180° (switching to the next-next filter) or more, the camera can approach the position directly. We feel this may be related to the auto-filter-recognition process.
We want to know how to have the filter wheel move directly to the destination for more efficient data acquisition. We would appreciate it if you could explain to us the filter wheel's behavior and how to avoid additional rotation.
i also quote the FLIR technology suppport team, the engineeri suggest me to use GenICam to control the FLIR Camera. he does not have the experience for control the FLIR Camera by LabVIEW.
i want to know how to use LabVIEW to call the GenlCam.
Because i think the GenlCam is a Camera protocol,including GigE、CameraLink、1394....., not a SDK or subfuction can be directly call by LabVIEW.
Thank you for your time and assistance. We look forward to your response.
11-04-2025 09:09 AM
a google search of "LabVIEW GenlCam" returns "A LabVIEW GenICam driver" on VIPM:
https://www.vipm.io/package/serenial_lib_g_industrial_camera/
11-04-2025 12:22 PM
Install Vision Acquisition Software to use GenICam parameters in LabVIEW. You can use all GenICam parameters from LabVIEW that that you can use feom NI Max after installing VAS.
11-05-2025 08:03 AM
@Quiztus2 wrote:
Install Vision Acquisition Software to use GenICam parameters in LabVIEW. You can use all GenICam parameters from LabVIEW that that you can use feom NI Max after installing VAS.
I agree with Quiztus2's observation. About 7-8 years ago, I tried programming a FLIR camera using low-level GenICam calls through VAS, but the particular camera (I don't remember the model) and my LabVIEW version (2016 or 2017, I think) didn't do the trick. A colleague took over the Project and did it in Visual Studio, instead.
Bob Schor
11-06-2025 03:26 AM
Thank you for your reply.
Actually, i have used the IMAQ module to control the FLIR Camera successfully. the program can finish the task of controlling filter wheel rotating and exposure.
but the filter wheel can not rotate sequentially, always rotate many position(must pass a complete filter wheel cycle before stop the position which i set the filter wheel).
i hope the filter wheel every time rotate one postion.
Can the NI Vision Acquisition Software realize this function?
Could you tell me what subVI can realize the fuction in labview?
thanks~
11-06-2025 03:28 AM
You need to find out which genicam attribute lets you do it sequentially.
11-06-2025 06:55 AM - edited 11-06-2025 06:58 AM
@Yuzn wrote:
Thank you for your reply.
Actually, i have used the IMAQ module to control the FLIR Camera successfully.
you are using imaqdx, which is besides imaq, also part of the vison acquistion software (vas) bundle
@Yuzn wrote:
i also quote the FLIR technology suppport team, the engineeri suggest me to use GenICam to control the FLIR Camera.
[...]
i hope the filter wheel every time rotate one postion.
Can the NI Vision Acquisition Software realize this function?
this is an oddly specific question, obviously we don't know the answear.
your observations - based on your trial and error experiment - suggest, there is a bug
can we be sure that the hardware is capable of doing this, when using low level genicam??
if, yes, then
You need to find out which genicam attribute lets you do it sequentially.
use chatgpt or perplexity or grok or copilot to narrow down further ...
made with grok.com, socall the following into question
The problem with unnecessary rotation (e.g., an extra 360° spin during 90° steps) is well-known: it is often caused by the automatic filter recognition system, which uses magnetic IDs on the filter holders. This system triggers a full scan when small angular movements (like 90°) are commanded, to re-verify all filter positions. In contrast, 180° steps (two positions apart) usually do not trigger this scan, as the system considers the target position "confident" due to the larger displacement.
This is derived directly from official FLIR documentation (no speculation — based on standard SDK and hardware behavior). Relevant references: