RadiMation Application Note 153: Difference between revisions
(Created page with "= multi axis field probe corrections= == Introduction == This application note provides an overview of the functionality associated with the correction files for the field se...") |
No edit summary |
||
| Line 1: | Line 1: | ||
= | = Multi axis field probe corrections= | ||
== Introduction == | == Introduction == | ||
This application note provides an overview of the functionality associated with the correction files for the field sensor device driver. The correction files serve to correct measurements taken by the sensor. There are two types of correction files that can be added: multiplication (multiply) and offset. The type of correction file used in conjunction with the driver determines whether isotropic or axis-specific correction is applied to the sensor data. | This application note provides an overview of the functionality associated with the correction files for the field sensor device driver. The correction files serve to correct measurements taken by the sensor. There are two types of correction files that can be added: multiplication (multiply) and offset. The type of correction file used in conjunction with the driver determines whether isotropic or axis-specific correction is applied to the sensor data. | ||
== | == Types == | ||
'''Axis-Specific | '''Axis-Specific Corrections'''</br> | ||
To implement axis-specific corrections, the correction file must include columns labeled "X-axis correction," "Y-axis correction," and "Z-axis correction." These columns contain the correction values corresponding to the respective axes. | To implement axis-specific corrections, the correction file must include columns labeled "X-axis correction," "Y-axis correction," and "Z-axis correction." These columns contain the correction values corresponding to the respective axes. | ||
'''Isotropic | [[File:AxisSpecificCorrections.png]] | ||
For isotropic corrections, a single "correction" column can be added to the correction file. This column holds the correction values applicable to | |||
'''Isotropic Corrections'''</br> | |||
For isotropic corrections, a single "correction" column can be added to the correction file. This column holds the correction values applicable to the isotropic measurement result.</br> | |||
[[File:IsotropicCorrections.png]] | |||
</br> | </br> | ||
Refer to the manual for further details. | Refer to chapter 14 of the manual for further details regarding the different field sensor corrections. | ||
== Using multi axis field probe corrections== | == Using multi axis field probe corrections== | ||
'''Probe Supports Multi-Axis Measurements and has Axis-Specific Corrections'''</br> | |||
If the probe supports multi-axis measurements and axis-specific corrections are present in the correction file, the test will start successfully. The measured axis field values will be corrected using the axis-specific corrections. | |||
Probe Supports Multi-Axis Measurements and | '''Probe Supports Multi-Axis Measurements and has Isotropic Corrections'''</br> | ||
If the probe supports multi-axis measurements and | If the probe supports multi-axis measurements and isotropic corrections are present, the test will start successfully. The measured axis field values will be corrected using the isotropic correction. | ||
Probe Doesn't Support Multi-Axis Measurements but Has Axis-Specific Corrections | '''Probe Doesn't Support Multi-Axis Measurements but Has Axis-Specific Corrections'''</br> | ||
If the probe doesn't support multi-axis measurements but axis-specific corrections are present, an error will be generated. The error message will indicate that the probe cannot perform measurements with the current correction files. | If the probe doesn't support multi-axis measurements but axis-specific corrections are present, an error will be generated. The error message will indicate that the probe cannot perform measurements with the current correction files. | ||
Probe Doesn't Support Multi-Axis Measurements and | '''Probe Doesn't Support Multi-Axis Measurements and has Isotropic Corrections'''</br> | ||
If the probe lacks multi-axis measurement support and has isotropic corrections, the test will start successfully. The measured field will be isotropically corrected. | |||
== | ==Conclusion== | ||
Conclusion== | |||
The functionality of correction files in the field sensor device driver allows for precise measurement of sensor measurements. By incorporating axis-specific and isotropic correction options, the driver ensures accurate and context-appropriate data corrections. It's essential to consider the compatibility of the probe's measurement capabilities and the correction file contents to achieve successful measurements. This versatility enhances the usability of the field sensor device across various use cases. | The functionality of correction files in the field sensor device driver allows for precise measurement of sensor measurements. By incorporating axis-specific and isotropic correction options, the driver ensures accurate and context-appropriate data corrections. It's essential to consider the compatibility of the probe's measurement capabilities and the correction file contents to achieve successful measurements. This versatility enhances the usability of the field sensor device across various use cases. | ||
Revision as of 15:05, 7 August 2023
Multi axis field probe corrections
Introduction
This application note provides an overview of the functionality associated with the correction files for the field sensor device driver. The correction files serve to correct measurements taken by the sensor. There are two types of correction files that can be added: multiplication (multiply) and offset. The type of correction file used in conjunction with the driver determines whether isotropic or axis-specific correction is applied to the sensor data.
Types
Axis-Specific Corrections
To implement axis-specific corrections, the correction file must include columns labeled "X-axis correction," "Y-axis correction," and "Z-axis correction." These columns contain the correction values corresponding to the respective axes.
Isotropic Corrections
For isotropic corrections, a single "correction" column can be added to the correction file. This column holds the correction values applicable to the isotropic measurement result.
Refer to chapter 14 of the manual for further details regarding the different field sensor corrections.
Using multi axis field probe corrections
Probe Supports Multi-Axis Measurements and has Axis-Specific Corrections
If the probe supports multi-axis measurements and axis-specific corrections are present in the correction file, the test will start successfully. The measured axis field values will be corrected using the axis-specific corrections.
Probe Supports Multi-Axis Measurements and has Isotropic Corrections
If the probe supports multi-axis measurements and isotropic corrections are present, the test will start successfully. The measured axis field values will be corrected using the isotropic correction.
Probe Doesn't Support Multi-Axis Measurements but Has Axis-Specific Corrections
If the probe doesn't support multi-axis measurements but axis-specific corrections are present, an error will be generated. The error message will indicate that the probe cannot perform measurements with the current correction files.
Probe Doesn't Support Multi-Axis Measurements and has Isotropic Corrections
If the probe lacks multi-axis measurement support and has isotropic corrections, the test will start successfully. The measured field will be isotropically corrected.
Conclusion
The functionality of correction files in the field sensor device driver allows for precise measurement of sensor measurements. By incorporating axis-specific and isotropic correction options, the driver ensures accurate and context-appropriate data corrections. It's essential to consider the compatibility of the probe's measurement capabilities and the correction file contents to achieve successful measurements. This versatility enhances the usability of the field sensor device across various use cases.