-17320; Unknown function or sequence name.

[Marc Miller]

"The status expression for the step '5.5.1.B Ignition Status Message, Ignition OFF' could not be evaluated.
Unknown function or sequence name '.'.
Error in call to expression function 'Evaluate'.
Error in argument 1, 'Step.DataSource == "Step.Result.Numeric" ? Step.Result.Numeric : (Step.Result.Numeric = Evaluate(Step.DataSource))', in call to the expression function 'CheckLimits'."

This error occurs on my new test station that I am building. At first I thought it was due to the "." in the test name and I upgraded to TS2.01 but it did not solve the problem. I also removed the "." and replaced it with underscores but I still get the error. Any ideas why? Here is some more info...

"-17320; Unknown function or sequence nam
e."

"Step '5.5.1.B Ignition Status Message, Ignition OFF' of sequence 'Power Up' in 'VLU Test Sequence.seq'"

Evlauation formula = "CheckLimits(Step.DataSource == "Step.Result.Numeric" ? Step.Result.Numeric : (Step.Result.Numeric = Evaluate(Step.DataSource)), step.limits.high, step.limits.low, step.comp)"

[SachaE]

Hi Marc,
can you explain a bit more what you're trying to acheive. Is this a custom step type, or is it one of the built in Numeric Limit check steps? (which matches the Status Expression you've given).
Can you post the offending sequence here?
Do other steps like this one work? Does this sequence / step work on another machine?
Using the above status expression on a non numeric limit step produces error 17306 where it tells you that it's looking for DataSource which doesn't exist.
I can't see why the "." in the step name could cause a problem. What happens if you simplify the expression (temporarily), i.e. set it to "Passed" or "Failed", and then work up from there?
Are you evaluating something under the DataSource of the step which could be causing a problem?

I get error 17320 if I try to put a bad item un the DataSource e.g. Test()
What is your Step.DataSource set to?

Thanks
Sacha

[RayFarmer]

Hi,

The problems is that your expression in the status expression cannot be evaluated.

There shouldn't be any " around the CheckLimits() function.

eg
CheckLimits(Step.DataSource == "Step.Result.Numeric" ? Step.Result.Numeric : (Step.Result.Numeric = Evaluate(Step.DataSource)), step.limits.high, step.limits.low, step.comp) when viewed from the Properties Dialog | Expression Tab

Regards
Ray Farmer

[Marc Miller]

This is the standard Numeric test type.
This sequence works on the other test stations I have deployd.
I have simplified the test name and removed the "."'s but I still get the same error.
DataSource is evaluating a global variable but I have used this global in steps prior to this one.

[Marc Miller]

I placed thoes qoutes there just for posting purposes so that you could tell what is directly pasted and what I typed.

[SachaE]

Very strange considering it works on other test stations - can you post the sequence snippet here so we can all have a dig through it?
It seems to me as though the DataSource is evaluating out to a "." but it has to be more than this, as you'd get a different error message of it was (unknown variable usually).
Have you deployed the same way for all the other test stations (with a engine installation) or are you deploying by hand (copying the files across on top of a debug / developer installation license?).
If you have a copy of the sequence editor on the target PC how about putting a break point at that step, and then creating a watch expression for Evaluate(Runstate.Sequence."FILL IN THE BLANK HERE".DataSource) and see what that comes out as.

S.

[Marc Miller]

Initialy I installed it the same way (with engine installation) but since then I have installed the full developer enviroment for the sequence editor and debugging. I have taken the sequence file and deleted all but the first 2 sequences out of it and attached it her for your viewing pleasure 🙂 I will try the break point and watch variable idea. Thanks.

[RayFarmer]

Hi,

the step in your step 5.5.1 BattIn.... hasn't got the Sequence Context enabled

Regards
Ray Farmer

[RayFarmer]

Hi,

What are you doing In the 5.5.1 step of you sequence?

Regards
Ray Farmer

[Marc Miller]

This VI does not require a Context Pointer.