Hi,
This follows from the issues I have been having with the Statechart module explained in this post form earlier this week, however as it is a separate problem, I thought it would be best to create a new post here.
Attached is an example project which replicates my issue. The project has a test VI which runs a statechart with a few dummy states, some of which call other sub-statecharts.
When the project file is opened and the test.vi is ran, LabVIEW freezes up entirely for about 20 seconds. This issue does not happen if the C-series module (Mod1) is removed from the project! There seems to be some strange correlation between the Statechart and the module, which makes any project that includes statecharts and C-series modules practically unusable.
Note that the above test uses some simple statecharts with little functionality. In an actual project I am developing, the statecharts are more complex, and LabVIEW freezes up entirely for a minute or longer, when any C-series modules are present.
If the test.vi is opened on its own from the file explorer (without opening the project), there is no problem. (Also probably worth mentioning that there is no problem if the statechart is not run at all in this project).
The mere existence of the C-series module in the same project as the statechart causes the issue. Same issue happens with similar hardware combinations (e.g. adding a NI 9476 on a cRIO 9038).
Note that I am not actually connected to the said RIO hardware. Is it possible the statechart is somehow trying to find/search these modules, hence delaying the execution?
I can't really debug the program as everything in LabVIEW becomes entirely unresponsive (even the memory profiler).
Does anyone have any ideas or experience with the Statechart module?
