i have some problems while passing control array as refernce to the sub vi and sub VI crashes not deterministically after few minutes

[hood1]

Hallo every body,
i have some questions when i am passing the refernces to the sub_VI

1)when i run the application, the blink indicator(in main VI) starts blinking. even in sub_vi for true case i set it true and for false case i set it false. why from begining of the execution it starts blinking?

2)the stop button i am using in main VI is too slow. when i press the stop button it takes too much time to stop the application. why?

3)the array control (amplitude, freq,total time taken )
i am creating references of array. then these references i am sending to for loop. where it will convert as scalr values and then these scalar values to the sub_vi. opposite to it i am getting the reference of scalar cycles value and i am buliding an array of these scalar cycles to show it in indicator. it seems not to be working properly. why?
for this exexution some times i get error 91.

4) sometimes in the begining i get error 1055. why?

5) my sub vi crashes not deterministically.some time times after 2 minutes. some times after 5 minutes. by crash i mean i dont get an error but on the oscilloscope i see not smooth sine signal, but some strange broken, unbroken, delayed(all together mixed signals). why?

thanks for the important suggestions.
Regards

[johnsold]

1) At some point the Blinking property gets set. Then the errors result in the program terminating. The property never gets reset. Setting a Property node in the main VI with Blinking = False prevents this.

2) You have 1 second Wait until next multiple delays in both the main and subVI loops. Depending upon which delays have executed when you push the Stop button it can take two seconds or more before all the loops execute again and note the Stop button.

3) The references are to arrays. (Time Taken, Amplitude, Cycles and Frequency) but you are connecting scalar values to the Values properties. Variant does not mean you can connect anything and it will convert to what you want. Once the Type has been set (when the control was created), the property node input matches that type.

4) 5) I never got this far so I cannot explain these errors. However, I suspect that once you fix the others, these will either be fixed also or the cause will become more apparent.

Lynn