New VI Analyzer Test: Priorities of Timed Structures

[Norbert_B]

Timed structures require a priority for scheduling. Default priority level is 100 for each structure.

If that priority is not changed (one dedicated priority level per structure) it could lead to unexpected behavior like hangs.

Therefore i propose a new test for the VI Analyzer which tests for unique (static) priority levels in timed structures. If there are priority levels shared among several structures, the test shall fail.

The test shall also work within a whole project, so it shall not only check this within single VIs.

Norbert

[SteenSchmidt]

This is a very important thing to focus on, but it's quite hard to implement; Most often when I use timed structures it's in conjunction with reentrant VIs. VI Analyzer can't take into account how and when the different components (and thus timed structure instances) load.

Kudos anyway for bringing it up.

Additional stuff to consider for VI Analyzer, if a good way to implement such a test is devised:

- Unique names for all runtime instances of a timed structure (this is a REALLY bad bughole to wind up in).

- Surpassing the maximum supported number of simultaneous timed structures (120-ish it seems to be).

- Mixing of timed structure priorities with VI execution/thread priorities. In this vein I'd point you towards this idea as well.

Cheers,

Steen

[Darren]

Any idea that has received less than 2 kudos within 2 years after posting will be automatically declined.