Leaderboard

Hi, The TestStand presentation I gave at NI Week 2015 regarding use of TestStand with the DQMH (Delacor Queued Message Handler) can be found here. I will be uploading the accompanying videos for the presentation during the course of the next day or so. What a shame that you can't move entirely to a TestStand based solution, it would be nice to implement a post step callback in the TestStand process model and then have the Step results captured without the developer of the client sequence having to have any knowledge of the storage mechanism. However as pointed out above , you will need LabVIEW based tests too. The LabVIEW based DQMH plays nicely with TestStand so it would not be difficult to create such a DQMH module (cloneable) to act as a "worker" using the UUT Serial Number as it's unique identifier. You could then have a results list object within this module that is populated by public API methods such as "Add Result" This worker could then periodically store results to a Local DB, XML file or whatever intermediate storage you require. SQLite is pretty lightweight as mentioned above. I'm not sure how you manage the replication of Local DB data to a central DB ? Do you use replication services ? One thing this "Results worker" could do is store the data in XML and then you could easily set up a SQL DTS job to bulk import complete results sets. I've spent a long time in test data management, there are many many ways to skin this particular cat ! EDIT: I forgot to say. The shipping examples that come with the DQMH Toolkit are duplicated in both LabVIEW AND TestStand. A video walkthrough of the TestStand examples can be found here

This post offers a solution (amongst others), which I should have tried before posting this. tldr: Set the "Legend: Plot Minimum" property to the number of plots in the graph. The property name and its documentation seem to suggest a solution to the opposite problem: The number of entries in the plot legend will never go below this value. That's what threw me off, because I was looking for something that would make sure the number of entries in the plot legend will never go above this value. As it turns out, this property node also has the effect of removing "unused" plot names when the number is set to the amount of plots in the graph. And in 2014 it also works with scroll bars in the legend without having to turn them off and on again. Delete Plot Names From Legend.vi

I do think its more than 5%, but from what you described I don't think you're in that X%. So...from a high level it sounds like what you want to do is spin up N workers, send them a UUT to work on, and then have the results recorded to disk. To be honest, I'm not sure why you need DVRs or any data sharing at all. Could you clarify? ->To me you'd have a QMH of some kind dealing out the work to your N workers (also qmhs) and then a QMH for logging which collects results from any of the N workers. You could do that with manually written QMHs, an API like AMC, a package like DQMH, or actor framework. Separating out worker functionality from logger functionality means (a) for those long running tests you could write intermediate results to a file without worrying about interfering with the test and (b) you can really really really easily switch it out for a database once you've decided you need to. As a side thought, it sounds like you are re-writing significant parts of teststand (parallel test sequencing, automatic database logging and report gen, etc.). The DQMH library mentioned above seems to be written to work pretty well with teststand (nice presentation at NI week and I believe its also posted on their community page). Just a thought. If I'm mistaken, or you can't use teststand for whatever reason the tools network does have a free sequencer which I think is pretty cool (although I do RT most of the time and never have a good chance to use this guy): http://sine.ni.com/nips/cds/view/p/lang/en/nid/212277. It looks like it could be a good fit for your workers.