Solution
This issue is caused by channel-expanded tasks and how FlexLogger internally rewinds the read buffer after reading the first sample. NI has filed a bug for this issue and plans to release a fix future release of FlexLogger.
Workaround: Prevent Channel Expansion
Channel expansion occurs when:
- Multiple modules of the same type are in the same chassis
- All channels are configured with the same sample rate
To avoid this, configure each PXIe-4339 module with slightly different sample rates:
- Slow: 255 Hz
- Medium: 256 Hz
- Fast: 257 Hz
This allows up to three PXIe-4339 modules in the same chassis to operate without channel expansion. Even though the sample rates differ, synchronization can still be achieved using a start trigger and shared reference clock.
Note: Channel expansion does not occur across chassis. Identical sample rates can be used for modules in different chassis without issue.