Quantcast
Channel: NI TestStand topics
Viewing all articles
Browse latest Browse all 6524

Referencing a Parameter being passed out of a Sequence Call

$
0
0

Background:  I'm creating a ProcessModel for our test engineers, and I want to allow them to make their own custom (ambient/chamber/etc) temperature gathering code, so I'm writing that as a callback sequence, which ends up being a Sequence Call Step.  This temperature info is passed out of the sequence as a parameters and then stored in the Parameters.UUT.AdditionalData container of the calling sequence.  I've already created the property by using the insertifmissing property option of SetValString in a previous step.  I don't want to pass the whole Parameters.UUT container as that would give the developing engineers access to the whole container, and I want to limit the scope of the Sequence.

 

Things I've tried:

I've verified that the data is succesfully being passed out of the Sequence by using a local variable.  I can then use a Statement to do Parameters.UUT.AdditionalData.Temperature=Locals.Temporary, where Locals.Temporary is the value for the Temperature Parameter being passed out of the Sequence Call.  However, if I skip the local variable, and set Parameters.UUT.AdditionalData.Temperature as the value being passed out of the sequence call, it gets populated with "...".  This behavior is repeated if I use Parameters.UUT.AdditionalData.Temperature=Step.Module.ActualArgs.Temperature.UserData in the post expression of the sequence call

 

Can someone point out the mistake I'm making, or the piece of information I'm missing?

 

Thanks in advance,

Seth


Viewing all articles
Browse latest Browse all 6524

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>