09-29-2015 05:02 PM
What happens when you run in a non modified UI? Because the image of the one you posted is modified.
Also, what results do you see when you run the attached sequence file in the UI?
Also, what is the full expression that is throwing the error?
Regards,
09-29-2015 05:26 PM
I run the file you sent it works fine, no error occured.
I run my sequence in a non modified UI the same error still occured. i've also noticed that, in my sequence file the first place where the station globals are refered was in modeloptions step which did not generat the error, but when the main sequence called a subsequence that refered to the station globals is where the error occured.
The expression I used was this "
Parameters.CorrespondingChannel=StationGlobals.TesterProperties.NamesOfComPorts[Parameters.RunningStationNumber] "
Notice it's an array type. I had trouble with loading this array using property loader before but now it works fine.
Thanks a lot for your support so far.
09-29-2015 05:39 PM
Just to clarify. Everything works fine in Sequence Editor. Any UIs the error occurs?
Also, when you ran my sequence file did you see all the variables on the second popup? You can take those steps and put them in your sequence and see if they yield the same results. See Below: I believe your stationglobals are getting jacked by your property loader.
Also, what are passing on Parameters.RunningStationNumber?
Attached is another sequence file. Can you run it in the UI? Let me know what the message box says.
I'm thinking here that maybe your property loader is killing your stationglobals somehow. Another thing you could check is try running in the full-featured UI and when you get the error check the Break box on the error dialog. Then look through the variables at the StationGlobals and see if they are the same as what you thought they should be.
Regards,
09-29-2015 05:53 PM
Yes the sequence is attached.
09-29-2015 07:19 PM
Everything runs fine for me in all 3 of the Full-Featured UI, Simple UI (both LabVIEW) and the Sequence Editor. Also, I pointed your sequence file to the model that you sent. I'm not getting any errors when running with it in all 3 environments either.
I did manually create the stationglobal variables as per the image you posted earlier.
I'm having a really hard time believing that it only happens in one environment and not the other. That isn't how TestStand works at all. StationGlobals are global to the machine regardless of what you use to execute.
Are you sure you saved the StationGlobals file and rebooted both the UI and the Sequence Editor?
Maybe try deleting the variables and recreating them?
This is odd.
09-29-2015 07:28 PM
Hi I just quickly checked the first sequence you gave me, I found when I run it in Labview UI, the second message pop up only showed 1 station global. (when I run it in teststand sequence editor, it would show 5 station globals containers, or subproperties as you called it. 5 is correct.)
I think you are onto it, I tried to run the second file(Debug station global issue) you attached, the same kind of error occured when running "Top-Level.vi", and no error when running in Teststand Sequence editor. Please see the attached.
I have attached my sequence file with a previous post I replied to another person who tried to help. You can have a look at it as well.
To answer the question you asked: when I run my sequence in any Top-Level.vi in the Labview Labrary manager, it would generate the same error. But when I run the Labview executable it does not generate the error.
What I'm passing to the Parameters.runningStationnumber is "RunState.TestSockets.MyIndex". I passed it though a sequence call.
09-29-2015 07:35 PM
I have not saved the station globals file in anywhere, everytime I boot Teststand I can see the variables are remaining exactly the same as I left them last time so I thought I didn't need to explicitly save it... (Maybe is that a dumb thing to do?) I've encountered numerious problem since I started working with Teststand so far.
Do I need to save the station globals into the folder where I save the project? Also what's odd is that somehow only some of the station globals seem to be hard to find but not all.
Have you tried to run the sequence file I uploaded without pre creating the variables in the station global file and see if it loads from the property loader? Maybe that would help to recreat the error?
09-29-2015 07:49 PM
It won't load until i created the Globals. I get the same error. Once I created them in the Sequence Editor and saved them they worked fine in the UIs.
If there is an asterisk on the StationGlobals tab in the sequence editor then you need to save it. The StationGlobals can only reside in the Cfg folder. The Cfg folder is defined as the following on W7:
C:\ProgramData\National Instruments\<TestStand>\Cfg
You can change the location of the folder but all cfg files need to be in there. Typically you wouldn't change the location unless you knew what you were doing and had a good reason.
It will prompt you to save them once you close out TestStand if they aren't saved.
Are you POSITIVE it is the same machine. This just doesn't make sense.
Regards,
09-29-2015 08:34 PM
I really appreciate your persistance in helping me so far, 🙂 I noticed that the StationGlobals tab had an asterisk after I manually deleted the station globals and recreated them. This time I tried something different:
1. Open the sequence file in sequence file editor, delete the station globals i created, save the station global file, close the sequence file editor.
2. Reopen the sequence file editor, open station globals file, recreate the station globals I deleted, but I did not put any values into the stations globals. Save the station global file, and then close the sequence file editor.
3. Open the Labview Top-Level.vi, run the same sequence. The same error occured. So I closed the Labview vi.
4. Open the Teststand sequence file editor, open the station globals file, the values are not loaded into the station global file (The sequence I wrote should have used the property loader step to load the values into the station globals file in process set up step! but looks like it failed to do so when running in labview UI vi.)
5. I run the sequence in the Teststand Sequence file editor, the first time I do so with no values loaded in the station globals properties, I would get an error (Please see the attached file). I then terminate the excusion, rerun the file in Teststand sequence editor, everything will run smoothly, i check the station globals, all the station globals variables have been loaded with the correct value.
I think you mentioned something about the property loader killing the station globals, I think you might be right on this one. I will try run the sequence file without the property loading step and see what happens.
Oh and, if there's anything about this Teststand project that I'm sure of so far, that's I'm using the same machine to do all that's been mentioned above in this thread. 🙂
I know, it's very odd, I had some trouble with property loader step before as well, I think there might be something I'm not setting up right or a bug somewhere.
09-29-2015 09:17 PM
Hi I just run the sequence file in the full featured UI vi, the same problem occurs as expected. I chose the break option when error occured, I then checked the station globals, all my custom defined variables in the station global file are missing. I think you probablly expected this, so what does this mean then? Somehow Labview seem to have its own copy of station globals?
I had skipped the property loader step in the sequence file and run the sequence in both Teststand sequence editor and Labview Top-level.vi, the same occurs, so now I really really really don't know what to do...