This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| labview_embedded_programming_style_guide [2011/04/18 11:14] – ab | labview_embedded_programming_style_guide [2017/11/07 22:26] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 4: | Line 4: | ||
| ===== general design approach ===== | ===== general design approach ===== | ||
| * Only do small development steps at a time! \\ Remember, while working in FDM mode the code is executed on the PC and not on the target. Timing is different and VIs might execute different. | * Only do small development steps at a time! \\ Remember, while working in FDM mode the code is executed on the PC and not on the target. Timing is different and VIs might execute different. | ||
| - | * For this reason its absolutely crucial that only small pieces of code are developed in FDM mode, then compiled and tested in real time on the target | + | |
| * DO NOT use the LabVIEW " | * DO NOT use the LabVIEW " | ||
| ===== application programming ===== | ===== application programming ===== | ||
| - | * Use a single loop approach wherever possible. \\ Parallel loops are only suitable for loop times > 200ms and they introduce timing jitter of 50..150ms. | + | * Use a single loop approach wherever possible. \\ Parallel loops are suitable |
| * Do NOT use timed loops, use while loops instead | * Do NOT use timed loops, use while loops instead | ||
| * Do NOT use local variables | * Do NOT use local variables | ||