Dumping the data recorded by an evaluation
While it seems I do a lot of scripting now, I am still a technician first and I write my procedures accordingly. So I have been playing with scripts that do error checking and even let technicians fix an "oops" that would normally crash a whole procedure, forcing it to be run all over again. In this instance, there is a calibration that uses shunts. The technician types in the value of the shunt when Met/Cal prompts them and uses that to Ohm's Law the rest of the measurements off a DMM. While it hasn't happened yet, I KNOW at some point I or another tech is going to mistype the value of a shunt. And if that happens, all readings are going to fail, there's no good way of going back, and even if I put a target before the step that prompts for the value of the shunt, the tech doesn't know if that was actually the issue. So here's my idea. While I was reading he manual, I found a MATH expression that checks to see if the previous evaluation step failed. This intrigues me. So, what if following the first evaluation step after the shunt value gets entered, if it fails, a dialog pops up showing the tech the value they entered for the shunt and asking of it is correct. If it's not correct, then have it jump back to the step before it's entry then run again. However, I can already see one potential issue. Back with I was still learning, I fell in love with DO/UNTIL until I discovered that evaluations that happen on the same step number start overwriting themselves. Somewhat. I would get what I believe is the first and last values, or perhaps the last two values. I am not sure exactly. Point is, data gets retained and not fully overwritten. Which brings me to the crux of my question: Can you dump the stored values of an evaluation that has already run? Also, another hairball question, this MATH function that checks to see if the last evaluation failed, is it possible to have one that checks all previous evaluations to see if one failed?
Please sign in to leave a comment.