01-13-2012 10:15 AM
We are attempting to calibrate a SCXI-1520 module. We have installed our Calibration Executive Version 3.2 software on a new computer and are receiving the error code 200452. The computer runs on XP, we have a Fluke 5700A calibrator and an HP 34401A DMM connected via a USB to GPIB connection. They both respond when tested manually. The computer has a PCI-6221 board installed for DAC that passes the self-calibration procedure. The test chassis and all other connection are the same as a year ago. We have verified all the connections between the calibrator, DMM and the test unit. This same setup worked fine a year ago with a different computer. Did we miss a setup some place?
01-16-2012 03:25 AM - edited 01-16-2012 03:28 AM
This doesn't sound like a Teststand related problem, are you sure you have posted to the correct forum?
Try reposting at the following location:
http://forums.ni.com/t5/Digital-Multimeters-DMMs-and/bd-p/80
01-17-2012 08:18 AM
Its not a TestStand problem but I couldn't find a Calibration Executive board to post to.
01-17-2012 10:47 AM
Try
http://forums.ni.com/t5/PXI/Calibrating-PCI-cards-using-Calibration-Executive/m-p/714709
I did a search for Calibration Executive and PXI board came up as a better location to get your question answered
01-17-2012 11:28 AM
Stro1rob,
We can try to get this moved to the appropriate forum (likely either SCXI or any Calibration forum in the future). In general with that kind of error message, the usual culprit is the configuration of the SCXI chassis and module in MAX itself. The chassis can show up under Legacy DAQ drivers as well as under DAQmx, so if the configuration isn't correct for the version of hardware and software you have, then the calibration procedure will throw errors because of the associated DAQ drivers with the 1520. The error message itself (200452) is usually associated with calling in to a function that isn't available for a given device or it's driver, so with SCXI equipment, that is usually being configured directly in MAX. Take a look at how and where your chassis is configured, then go ahead and delete the old listing and re-add/configure the chassis. That should get things back up and running.
01-17-2012 12:28 PM
That is what I have done. It is working now. I had to configure the SCXI chassis in both the Legacy and DAQmx to get it to communicate.