NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Database, custom step types, ann XML report issues...All in one

TS3.0

Have a number of issues to do the above. I'll try and explain them in order. I'm sure there all linked, but can't figure out how...

The "Custom" Steps.....They are copies of the NI Numeric/Multiple Numeric tests, with a added post step to translate the error code into something meaningful.... No big deal.

XML Issue
When the report is generated the the Multiple numeric saves fine(See Multiple.txt, the step is of numeric type, all is well). However strange things happen in the Numeric test. see "Simple.txt" for a snipit of the result file. As you can see the "error code" contains the measurement. Why....?

Also in the XML the result seems to be reported as a normal step(like an action) and not a numeric test....


DATABASE Issues
Now when loggin to the standard DB that ships with TS, with the 1 change to the tables, to record our custom types in the DB. Everything works fine and is recorded untill the 1st instance of a skipped "Custom_MultipleNumericLimit Test" , at which point the DB (Microsoft Access) throws a wobbly(error message) and states that "No such col exsists". When the DB is looked at everything is recorded upto the point where a skipped Custom Step happend(and the error message). When the custom type is run normally(ie not skipped), the resutls are recorded fine, no problems.


Can't get my head around whats going on. I've check the property flags, and as far as I can tell every thing is in order for these custom steps(ie they look the same as the TestStand steps they are based on). It records fine in the XML.
0 Kudos
Message 1 of 4
(3,132 Views)
Hi

1. Regarding the XML issue can you please post a simple seq file which reproduces the problem using the none adapter.

Regards
Anand Jain
National Instruments
0 Kudos
Message 2 of 4
(3,127 Views)
I'll get one done in the nxt hour....
0 Kudos
Message 3 of 4
(3,121 Views)
Can you be more specific details about your database problem, specifically:
1) the changes that you made to the default schema
2) the changes that you made to the database tables
3) the entire error message text for the logging error
Scott Richardson
https://testeract.com
0 Kudos
Message 4 of 4
(3,100 Views)