Calibration history File

[thumble]

Hello,

We would like to rebuild a "Calibration History.nivscalh" from a "HardwareCalibrationData.nivscal". Currently, we are able to retreive the calibration parameters on running projects using the .NET Gateway API, but we don't klnow the format specification to rebuild the Calibration History.nivscalh. In a perfectl world, If we also knew the format of HardwareCalibrationData.nivscal we could do the job offline (because we still download and keep the HardwareCalibrationData files in our software reference repository).

The reason of that is because we have a huge system with several separated veristand front-ends and many different people are working in // with their own copy of the projects. Some of them are performing the electrical calibrations, some other the mechanical or hydraulics calibrations. At the end the HardwareCalibrationData.nivscal is consistant but there is no single related Calibration History.

Regards,

[Jarrod_S.]

What version of veristand are you using?

[thumble]

Sorry, we're using VeriStand 2011 SP1 and LabVIEW 2011 SP1

Regards

[Jarrod_S.]

I have a utility that can read calibration history files. It currently can't write them, but you could probably edit it to do so. Unzip this and look at Example Cal.vi to get started.

[Jarrod_S.]

The reason I asked about the version is that VeriStand 2012 has some new features for more effectively handling scaling and calibration. Notably:

1. You can now create and apply scales in the system definition to scale channels to engineering units. The scales are stored in the system definition, so they are much more portable.

2. Run-time calibrations are stored in a human-readable (and writable) XML file linked to the VeriStand project, making it easier to track and apply calibrations.

[thumble]

Thanks for the replies,

Unfortunatly, we cannot update our system to VeriStand 2012 now, because it is about to be delivered, so we are still unable to read the binary format from the HardwareCalibrationData.nivscal file.

Regards,

[Mark.K]

Regarding the...

"Run-time calibrations are stored in a human-readable (and writable) XML file linked to the VeriStand project, making it easier to track and apply calibrations."

...

Since this is an XML file in the NIVS project, is it safe to assume that some generic channel calibration file can be automated via a custom LV application (perhaps) to populate or update the XML cal file?  Just curious if this has been done.  The goal is to take an input cal file and have an automated way to read it into NIVS.  Seems that the cal XML would make this possible.

[Jarrod_S.]

Yes, it is possible to script the calibration XML files. The format is pretty straightforward.