01-05-2011 08:27 AM
I posted this in the LabVIEW forum, but TestStand is involved so I thought this forum might be appropriate as well. Could TestStand be causing this problem, or simply be sensitive to something that's happening on my computer?
01-05-2011 09:17 AM
So was the KB any help to you.
Has there been any updates that have been run on your system that is affecting the NI-DMM?
01-06-2011 08:35 AM
@Ray Farmer wrote:
So was the KB any help to you.
I responded to the other post. I don't think it applies.
Has there been any updates that have been run on your system that is affecting the NI-DMM?
No. This ATE and another one just like it have been running for two years. Neither has received any NI upgrades and both get the same OS/network upgrades. Only this ATE has the problem. I keep wondering if there's something failing on the hard drive, but I don't know anything about that. It doesn't seem that I'd only get this one problem if hardware was dying.
01-06-2011 01:38 PM
Hi Jim,
Jeff's suggestion of attaching MAX technical reports for the two ATEs would be helpful. Upload them and I'll look into it for you.
Thanks,
01-07-2011 01:30 AM
Jim,
That's the problem with posting in two different areas.
If you haven't change any software and you haven't change any hardware and its been running fine for some time, then maybe your DMM device has an intermittent fault.
01-07-2011 05:45 AM
01-07-2011 05:58 AM
Quite, but you are saying that the software hasn't changed / updated. Therefore it's hardware or finger trouble (eg someones deleting files/ folders).
01-07-2011 06:05 AM
01-07-2011 10:43 AM
Hi Jim,
This sounds like a software issue so I think the best way to determine what exactly is wrong would be if you uploaded a MAX technical report. Ideally, one from the working computer and one from the one giving you problems
01-07-2011 02:36 PM
Hi Sean,
Here are the technical reports. The ATP file is from the ATE that is working, the two MTP files are from the ATE with the problem. I made one in the "broken" state and one after I "fixed" it by repairing the DMM installation. This problem has recurred twice since I first posted; something is getting worse.
Thank you,
Jim