Statecharts built with debug disabled can no longer be edited?

[pkovitz]

Hi. I am using the Statechart module with LabVIEW 2009. If I set the statechart code generation settings to disable debugging and then rebuild the statechart, I can no longer place functions or edit the wiring of Transition, Entry or Exit Actions. The configure statechart area behaves as if I were trying to edit the block diagram of a running VI; for example, if I click on a wire, the system creates a probe. If I turn debug back on and rebuild the statechart, I can edit the states again. For destkotp VIs, this is no big deal because I always have debugging enabled. For VIs that I want to run on the ARM Microcontroller target, this is a pain because once a statechart is added to the project, I have to make the target LabVIEW Mobile/Touch Panel/Embedded; that execution target automatically disables debugging and you can't turn it back on again. I have to edit the statechart outside of the project and save it back.

Is there some other setting in LabVIEW or in the Statechart module that I am not getting correct?

[OliviaC]

Was this somthing you only see in LabVIEW 2009? Had you been able to edit the states in previous versions?

[pkovitz]

I did not try to do it in previous versions. of LabVIEW.

[pkovitz]

I am attaching a project that displays this issue.

[OliviaC]

Hi pkovitz,

It looks like you have posted the same questions here and someone is already helping you on this. Please don't make duplicate posts. It's easier to share ideas on one thread instead of having the same topic spread across more than one.

[pkovitz]

I am sorry but, although both have to do with statechart debugging, the other post is a different problem. That post is specific to the ARM module and it has to do with whether the ARM module can build a statechart image that can be debugged (it cant'). This is different, and I believe it is a bug in the LabVIEW Statechart module. You don't need the ARM module to see the bug. Configure a statechart to disable debugging  and then try to edit an entry action, exit action, or transition action. You will find you cannot. I am new to this community, so if I should have posted this as part of the other thread, I will do so.

[aggieNick02]

Hi pkovitz,

You are right that this is a completely separate (and unrelated) issue, so a separate post is good.

This is a bug that was introduced in the LV 2009 Statechart Module. The workaround is exactly as you described. You are right that this is cumbersome to do when using statechart on embedded because you must generate code outside of the project.

I think you can minimize the amount of editing you must do outside of the project by doing the following when you encounter the problem:

1. Close your project and save whatever you need to save.
2. Open the statechart outside of project. Change target to desktop and enable debugging.
3. Generate code for statechart. Now change target to windows mobile/touchpanel/embedded and save your statechart. Close your statechart
4. Reopen your project. You should now be able to edit your guard/action VIs until the next time you generate code.

I realize this isn't the best solution/workaround, and I apologize for the issue and inconvenience. If you find this impedes your workflow too much, let us know and we can see if there are perhaps some better workarounds. We realize this can be a big inconvenience for our users so I assure you the bug is getting appropriate attention.

Thanks,

Nick