Solution
Calibration information is not a supported feature on cRIO modules. However, the CompactRIOs with DAQmx (currently 904x and 905x) are exceptions. If the module is in Real-Time CPU (aka Real-Time (NI-DAQmx) mode), you can obtain the calibration data that the module supports.
Calibration metadata is provided by the NI‑DAQmx driver, so these calibration fields are populated only when the DAQmx driver exposes them. When a C Series module or a device is in NI‑DAQmx mode, then NI MAX, System Configuration API, and DAQmx property nodes can query those attributes and show them.
But when you switch the same hardware to FPGA/RIO mode, the device is now owned by the NI‑RIO/FPGA stack and not DAQmx. In this mode, DAQmx properties are not available, NI MAX or System Configuration API won’t show DAQmx-provided calibration fields, and DAQmx calls for those attributes will fail. usually it will cause errors like Error -2147220623 or Error -2147467263.
You can run the Calibration Audit example (Open Help>> Find Examples in LabVIEW and navigate to Hardware Input and Output>>System configuration) with a little bit of modification to see the supported and not supported features of the specified devices. Please see the following example image and the needed change to see the whole list of supported and not supported hardware you have:
