DAQmax - USB-6211

[Zuc_Lab]

Hi,

i know that the bottom right corner is reserved for errors cluster, but is this something problematic if i assign it to another kind of variable?

Best regards,

Zuc

[GerdW]

Hi Zuc,

---

@Zuc_Lab wrote:

is this something problematic if i assign it to another kind of variable?

---

As I wrote: in the first moment I missed the connection because of its highly unusual placement.

StyleGuide helps to create code readable to most users…

For TestStand the placement should be irrelevant as you assign your variable to those VI IOs…

[Zuc_Lab]

Hi,

You're right GerdW, sorry for that!

I discovered the issue! Even if i don't know the cause. In my sequence I call a vi which return to the sequence the container task_out for identifying the task of an NI USB-6211. When I close the task, I have observed that the associated container for is not filled with values, so going around in the sequence and in the vi I have found this setting in the sequence: the parameter TaskAnalogicGenerationParameter has only the [In] option, but I have never setted it like that.

Then by copying the same container from another subsequence where the vi works and the container receive the value, in the same tab I see that the TaskAnalogicGeneration has both the [In] and [Out] properties. Why? Where can I act to modify those things? Since I have done unintentionally, I was trying to understand it. Since in this second case everything works fine.

Best Regards,

Zuc

[GerdW]

Hi Zuc,

showing just images of the AdditionalResults settings doesn't help to configure your VI call in TestStand!

You need to show the settings on the Module tab where you connect the VI ConnPane to the TestStand variables…