Understanding Loop Timing (FPGA Interface)
- Updated2025-10-09
- 3 minute(s) read
|
|
|
Do not use the Loop Timer function or the Wait function in a loop with an FPGA I/O Node that acquires data from one of these modules.
When you create a loop that reads data from one of these modules, make sure the loop does not execute slower than the data rate of the module. If the loop execution time is slower than the data rate, the FPGA I/O Node returns an overrun warning and continues to read data. The overrun warning means that the data the FPGA I/O Node returns is valid, but the function missed one or more data points since the last time it read data from the module.
The function returns the overrun warning when all of the following conditions are true:
- The module is in acquisition mode.
- An FPGA I/O Node that is acquiring data from the module executes at least once after you put the module in acquisition mode.
- The FPGA I/O Node did not read one or more data points since the previous time the function executed.
If the application acquires multiple buffers of data from the module and the timing relationship between them is not important, you can ignore the overrun warning returned with the first point of each buffer. Avoiding Overrun Warnings
To avoid overrun warnings, develop the FPGA VI to meet the following guidelines:
| Conditions | Guidelines |
|---|---|
| Your application acquires multiple buffers of data from a module with an internal master timebase. | If the timing relationship between the buffers is not important, you can ignore the overrun warning returned with the first point of each buffer. |
| You are reading from multiple modules with an internal master timebase in the same loop. |
|
| You are reading from a module with an internal master timebase and another analog input module in the same loop. |
|