05-07-2007 01:18 PM
05-08-2007 10:45 AM
Hi David,
Let me try to answer your questions in order.
1) Yes, DIAdem can execute any SQL query and retrieve the results into channels in the Data Portal for further analysis and reporting
2) Yes, any SQL query can be saved and recalled for later re-use. An SQL query is just ASCII text, after all.
3) The TDM format was created by NI but is open to external users. There is a file format description and a C++ API available.
4) If you are using the built-in TestStand data base logging features, then you will be logging to a 3rd party data base such as Oracle or Access, and there will be no need to export TDM files.
5) If you prefer to use TDM or ATML file export from TestStand, then you could leverage the DIAdem DataFinder data base, instead of (or in addition to) using a 3rd party data base such as Oracle or Access.
6) It is well known and absolutely true that Access data bases struggle to perform well when they get big. If you have lots of little *.mdb files this is not a problem, but if you have an enormous *.mdb file, you are asking for lots of headaches.
The simplest approach would be to log TDM or ATML files from TestStand and simply use the DIAdem DataFinder data base, or perhaps the DataFinder Server Edition, to grant you relational query access to your data. In this case there would be no effort needed to develop an SQL query interface or SQL query file format, as these already ship with DIAdem for the DataFinder. Further, the DataFinder is extremely flexible when it comes to adding new measurements and is self-configuring and self-maintaining.
If you prefer to choose a 3rd party data base for your data storage, then you would need to develop an SQL query interface in DIAdem consisting of VBScripts and custom SUDialogs, and you would need to create your own SQL query file format in order to re-use previous queries in a future DIAdem session. This is not a big deal, and I can send you examples of this for the TestStand default data base. NI will also support you through the creation of your own custom DIAdem interfaces for your particular 3rd party data base. You would, however, be on your own when it comes to creating the initial data base schema, expanding that schema as you needed to add new measurements, and maintaing that data base (which would probably involve working with your IT department).
Hope that Helps,
Brad Turpin
DIAdem Product Support Engineer
National Instruments
05-17-2007 09:41 AM
Brad,
You said, "The simplest approach would be to log TDM or ATML files from TestStand and simply use the DIAdem DataFinder data base, or perhaps the DataFinder Server Edition, to grant you relational query access to your data".
I'm wondering how this would be implemented. I asked a similar question in another thread. What I'm wondering is, can ALL the data be placed into an ATML format from within the LabVIEW tests themselves, outside of TestStand, so as to allow DIAdem to open/datamine the file after the test? From what I've seen, the few XML VIs available in LabVIEW (string pallette) have some serious limitations.
LabVIEW converts data to an established XML schema. Currently, you cannot create customized schemas, and you cannot control how LabVIEW tags each piece of data.
The predefined XML schema that LabVIEW uses is LVXMLSchema.xsd located in the labview\vi.lib\Utility directory.
05-18-2007 11:30 AM
05-18-2007 11:40 AM
05-22-2007 10:12 AM - edited 05-22-2007 10:12 AM
Message Edited by AEDavid on 05-22-2007 10:12 AM