Frame Drops When Using DFK-33UX264 with Hardware Trigger

[wkerspace]

Content:
Hello, I encountered an issue while using this project and would like to ask for advice:

Project: ic4-examples/cpp/qt6/high-speed-capture
Camera Model: DFK-33UX264
Operating System: Windows 10
Qt / Compiler Version: Qt 6.8.3, MSVC 2022

---

Issue Description

When using hardware trigger mode, the camera experiences frame drops.
Observed behavior:

• The trigger signal input is stable, but the number of frames received by the program is less than the actual trigger count.
• When using software trigger or free-run mode, no frame drops occur.
• Adjusting image size and frame rate settings partially improves the issue.

---

Points to Confirm

1. In this example project, is additional code modification required to avoid frame drops in hardware trigger mode?
2. Could this frame drop issue be a limitation of the driver / SDK, or is it caused by incorrect usage in my program?
3. Are there any recommended settings (e.g., buffer size, queue configuration, or other API parameters) to improve this issue?

Thank you for your assistance! 🙏

[TIS-Tim]

What is your trigger frequency?
Is it compatible with the other relevant settings? (ExposureTime, AcquisitionFrameRate, DeviceLinkThroughputLimit, IMXLowLatencyMode)
Do you see transmission errors when querying the Grabber's stream statistics?
Does the camera send FrameTriggerMissed events when you enable them?

[wkerspace]

From streamStatistics, it shows a device_transmission_error.

[TIS-Tim]

Just 1? Or 1 per image that you expect but do not receive?

[wkerspace]

The occurrence is not fixed — sometimes 15 triggers may result in just one dropped frame, and sometimes it might take 35 triggers before one happens.

[wkerspace]

I’m still quite new to the system, so I would like to clarify how I can verify if the trigger frequency is compatible with the other relevant settings (ExposureTime, AcquisitionFrameRate, DeviceLinkThroughputLimit, IMXLowLatencyMode).
Could you advise what is the recommended way to check this? For example, should I look into the SDK parameters, or is there a specific tool or diagnostic output that I can use to confirm compatibility?
I’d be happy to run some tests if you could point me to the correct steps.

[TIS-Tim]

Just run Grabber::deviceSaveState to save to store the camera configuration in a file and attach it here.

What is your trigger frequency?

Additionally: What kind of computer are you using? Are there possibly other USB devices connected to the same USB controller?

[wkerspace]

I am using manual triggering via a switch, so there is no fixed frequency.

Computer: Windows 10, Intel i7, 16GB RAM
Other USB devices: None connected to the same USB controller.

{
"device": {
"model_name": "DFK 33UX264",
"serial": "35024282",
"unique_name": "The Imaging Source Europe GmbH-ic4-gentl-u3v-35024282"
},
"driver_properties": {
"LinkCommandTimeout": 5000000.0
},
"properties": {
"AcquisitionBurstFrameCount": 1,
"AcquisitionFrameRate": 25.0,
"AutoFunctionsROIEnable": true,
"AutoFunctionsROIPreset": "AutoFunctionsROIPreset_Full",
"BalanceWhiteAuto": "Off",
"BalanceWhiteMode": "WhiteBalanceMode_GrayWorld",
"BlackLevel": 254.0,
"ExposureAuto": "Off",
"ExposureAutoHighlightReduction": false,
"ExposureAutoReference": 128,
"ExposureTime": 15000.0,
"GPOut": 0,
"Gain": 2.5,
"GainAuto": "Off",
"Gamma": 1.0,
"Height": 2048,
"Hue": -2.0,
"IMXLowLatencyTriggerMode": true,
"LUTEnable": false,
"PixelFormat": "BGR8",
"ReverseX": false,
"ReverseY": true,
"Saturation": 100.0,
"SoftwareTransformEnable": true,
"StrobeDelay": 0,
"StrobeEnable": "Off",
"StrobeOperation": "Exposure",
"StrobePolarity": "ActiveLow",
"TriggerActivation": "FallingEdge",
"TriggerDebouncer": 0.0,
"TriggerDelay": 3.1,
"TriggerDenoise": 800.0,
"TriggerMask": 0.0,
"TriggerMode": "On",
"TriggerSource": "Any",
"Width": 2448
}
}

[TIS-Tim]

This will probably go beyond the scope of ic4-examples; please create a support case at https://www.theimagingsource.com/company/contact/.