Sometimes cannot edit Value of LabVIEW module parameters

[Gregory]

Hi there,

I'm seeing a weird problem where I cannot edit parameters sent to a LabVIEW module. This only happens on certain steps, on other steps, with the exact same LV module, I have no problem. When I hover over the exclamation mark, it says " Unknown variable or property name ''. " (Screenshot attached). Does anyone know what might be the problem?

Thank you

[Gregory]

I want to add that I'm seeing a trend. The problem seems to happen when one of the values is a concatenation of strings (for DAQ channel names). For example, one of the values is Parameters.Chan1 + "," + Parameters.Chan2 . 

This worked in an older version of TestStand (3.5) and I just recently loaded it up in 2010. Is there a setting somewhere to allow me to at least edit the value?

Thank you,

[Gregory]

I am able to recreate the error now. The screenshot will show exactly what I see at each step, but here is how I recreate it.

1. Insert fresh module call

2. Add element to "RetrieveDataCtrls". In LabVIEW this is an array of cluster.

3. Reload the VI prototype, or click off then click back on the step, and all parameters are locked out.

[Anand_Jain]

Hi, 

Can you post the VI which shows the problem? You can delete all the content in the VI but keep the controls and indicators. 

Regards

Anand Jain

National Instruments

[Gregory]

Hi there, I'm finding it is related to having an array of waveforms inside the cluster. Attached is a sequence and VI showing the problem.

[t@nim@t0R]

It looks like it is trying to input an initialized array; can you click the pencil icon next to the type in the step settings? This removes the error. 

[Gregory]

Hi t@nim@t0R,

No, after reloading the VI prototype, the pencil eraser is also grayed out.

[t@nim@t0R]

Have you tried creating the custom data type as well to input the necessary parameters to the VI? 

[Gregory]

---

t@nim@t0R wrote:

Have you tried creating the custom data type as well to input the necessary parameters to the VI? 

---

Yes, the cluster is a custom datatype (the array of clusters is not). I found a workaround where I create a local variable which is my array of cluster, then set all the values of it in an statement step. Then when I call my VI I can just use my new local variable as the input and TestStand does not complain anymore!

[Teuch1]

Yes, the cluster is a custom datatype (the array of clusters is not). 

Hi,  opened the sequence file but couldn't see the custom datatype for the cluster in the sequence file? 

Something to look at, if it is indeed a testStand custom datatype being used..  have seen issues in the past with labview and teststand where label names in the testStand custom datatype don't match those from the labview cluster another issue seen is when the cluster controls are ordered differently to the custom datatypes. Both of these cases would cause issues.

Have also noticed that the step settings default check button is not available  so there is no default state available so you would need to initialise this input (as you have done with the local variable).. again this could be related to your custom datatype (property flags)..

I copied your labview control and added to the same VI and it all worked correctly, so hunch is its the custom data type that is causing the issue..