hi All,
I read the string array[Out] from a VI & in the "SequenceFilePostResultListEntry"
write the various types (num, bool string array) to be saved as TDMS .
In this SaveTDMSFile.VI I write all the data thr' a Variant.
It works for all except String Array where I get the exception!!
thts the issue
You are correct, the script files and the Database Viewer application in 2014 still do not support default SQL delimiter syntax supported by specific DBMS SQL applications, but we would like to fix this in a future major release.
Hi I have multiple mdb files and would like to merge them into one file. All the tables are exactly the same. Is there a Labview vi that can do this? or can you assist?
The error occurs in the calling of the sequence "ProgramAssetData". The sequence is only called inside of a loop. The first call always works and all subsequent calls generate the "Run-Time Error" window. The retry option in the window always works. When I step through, the retry of the sequence call it goes to the first step in the sequence. A breakpoint on the first step of the called sequence does not occur until the "Retry" is executed.
Adding error handling to automatically retry and get around this problem seems like a "hack" and does not address the source of the problem. That could be a fix but I really do not like it as a long term solution.
It is related to Teststand when the database tick is enabled and results are store in the mdb file. When the mdb file reaches 1.5 gigs ....Teststand slows down when it trys to write new results to this file. So we have multiple mdb files that we would like to merge into one. So my questions was, if it could be done in Labview or can someone assist me with a solution, even if it is not in Labview.
Bruce,
I think at that point you would then be working with sub properties. So using the API to handle sub properties would be the best way. For instance the GetValString or GetValNum properties.
Hope this helps,
Are you perhaps accessing a sequence context from a thread other than the one the sequence is running in? If so, it's possible there is a race condition with the flow of the thread the sequence context belongs to and another thread trying to access that sequence context. Ideally you should access a sequence context only from the same logical thread as that sequence unless the execution is paused at a breakpoint.
Another possibility is perhaps there is a bug in ProgramAssetData with how the TestStand API is being used. The easiest way to determine this would be to step through the code in ProgramAssetData and see what it's doing and where in the code the problem might exist.
Hope this helps,
-Doug
Hello Jeroen,
I have been able to see what you are experiencing.
I think that the behavior you're seeing could be considered to be "expected behavior".
However, I do agree that it might not be completely clear when you start to work with the Property Loader Step (or by the explanation in the documentation).
As far as I have experienced (please correct me if I am wrong) you would be expected to either:
- Put Property Loader step directly into the Setup Step Group of the main VI before you load/call any other subsequences.
Then the Steps in your MainSequence their properties will get properly updated.
If you put it in a subsequence of the Step Group, then this is not by default the case. (based on my experience).
- I think that for what you are trying to accomplish it might be more useful to put your Property Loader Step in a PreUUTLoop Callback of your specific Sequence File.
Can you tell me if using a PreUUTLoop Callback could be a workable approach for your test sequence?
Or is there a specific reason why you want to use a subsequence?
I have attached a small example that illustrates the difference between both.
This example is based on a slimmed down version of your shared files.
The attached Code is provided As Is. It has not been tested or validated as a product, for use in a deployed application or system, or for use in hazardous environments. You assume all risks for use of the Code and use of the Code is subject to the Sample Code License Terms which can be found at:
http://www.ni.com/pdf/legal/us/sample_code_license_terms_020112.pdf
What exactly is the code doing that gives you this error? What API call is giving the error?
-Doug
Code is a statement step in the process model
(Post)Expression for statement is
Locals.FileGlobals.VariableName=#NoValidation(RunState.ProcessModelClient.Data.FileGlobalDefaults.VariableName)
(replace "VariableName" with actual name of variable) "VariableName" is instance of a type-def'd container (contains 2 booleans and a typedef'd container that itself contains 3 booleans)
(Yes we do have a locals.* container named "FileGlobals").
The goal here is we have some configuration settings stored as FileGlobals.* in the client sequence file (I realize there are some other ways we could do this, but we're kinda stuck with this architecture for now) and we are copying those values to locations in the process model so we don't need to keep referencing the client sequence FileGlobals.
Is it the labview vi where the exception occurs or in teststand? If it's the labview vi, can you reproduce the problem without teststand involved? If not, please explain in more detail as I'm not sure what you are doing. Also, what version of LabVIEW and TestStand are you using?
-Doug
Please correct the comment syntax too. The current one uses two forward slases ("//") -- of all the DBMS systems supported by TestStand, only Sybase supports this syntax. The most common syntax is two dashes ("--").
Hi JKSH,
Yes, we have noticed this too and when we fix this issue, we will update both the comment and the command delimiter characters to match the default values in the different DBMSs we support.
Hi Kilian,
Tank you for the answer. The Attachment is only a jpeg-File of the Operator-Interface with the error Message. I had already read the the link you mentioned, but I think I did not configure the Station Options correctly. Sorry!
But the second question, I mentioned: to unload all Sequences in the Testexec would also be interesting for me. Is there possibilty to Configure the Operatore-Interface, so that wenn the User closes it,all Sequence-Files will be closed too.
Thank you
Paul
Hi Kilian,
Tank you for the answer. The Attachment is only a jpeg-File of the Operator-Interface with the error Message. I had already read the the link you mentioned, but I think I did not configure the Station Options correctly. Sorry!
But the second question, I mentioned: to unload all Sequences in the Testexec would also be interesting for me. Is there possibilty to Configure the Operatore-Interface, so that wenn the User closes it,all Sequence-Files will be closed too.
Thank you
Paul
Exception is in Teststand.
the same vi works good for Num Array, Boolean Array input
when I give a String array Teststand brings this exception.
Hello All,
Creating a multiple numeric limit test in TestStand, and the expected values for 2 tests are stored in a single 5 byte HEX word local variable (imported from a file). For example, if the expected value word is "12345678AB", AB (the last byte) is the expected value for one test, while the 12345678 (the first bytes) applies to a second test.
In the past, I have used a seperate code module to split the word and inject the limits automatically into TestStand. However, in the case of a multiple limit test, I think it may be easier to just set the limit directly from the variable (if it can be done), as the path to get to the limit is much more complex.
So here is my question: What would the syntax be for the low limit expression field if I read in a 5 byte local variable, ignore 1 byte, and use the remaining bytes for the comparison? Please advise. Thanks.
GSinMN
I solved the problem. (I am new to Teststand and am working in code I did not write.) There was a bug in the "ProgramAssetData" sequence. There is a step that makes an Active X call to rename the next step using the Object reference "RunState.NextStep". The passed in parameter was using "Locals.name" which was set in the PreExpression. "name" was not defined as a local variable. My problem was that the error message only identified "Locals" as undefined in the calling of the sequence. It did not identify the line in the sequence where the variable was undefined. The other problem was that the first time the sequence "ProgramAssetData" was called, no error was generated. But then, "Retry" would work on all subsequent calls whjen the Run-Time error window appeared. Why "Retry" would work makes no sense to me. This all made it very difficult for someone new to Teststand to debug.