Chinese
Spanish
Russian
Portuguese
French
German
Indonesian
Thai
Vietnamese
Arabic
Italian
Turkish
Polish
Japanese
Buying radar level gauges becomes unnecessarily risky when the quotation and site sheet use the same numbers for different quantities. A distance written in millimetres can be read as metres; a process pressure can lose its reference basis; a level output can be mistaken for distance. These errors should be resolved on paper before equipment reaches the tank.
Check the quantity before converting the unit
Confirm whether each dimension is tank height, antenna-to-bottom distance, maximum measuring distance or usable level span. Only then convert units. A correct conversion of the wrong dimension still gives the supplier an incorrect selection requirement.
For example, 1,200 mm is 1.2 m, not a 1,200 m requirement. Likewise, 0.25 MPa equals 2.5 bar, but that numerical conversion does not identify gauge or absolute pressure. These are unit examples, not operating recommendations. Ask the process owner to state the pressure basis and temperature together.
Buying radar level gauges: reconcile the order sheet
| Field | Question to close |
|---|---|
| Length | What are the units, reference plane and physical endpoints of this dimension? |
| Pressure | Is the value gauge or absolute, and does it cover vacuum and operating temperature? |
| Signal | Does increasing output mean increasing level or increasing distance? |
| Percent | Is the percentage based on height, selected output span or calculated volume? |
The METRAVON MV-RD902 provides a concrete example: its 0.3-30 m listed interval describes measurement distance. It should not be copied into the PLC as a 30 m level span without the vessel reference and required endpoints. Its published pressure and temperature options also need confirmation as one selected assembly.
Write one agreed value in the final order
Where several documents differ, keep a short discrepancy list showing the original entries and the approved correction. Give the supplier one controlling specification revision. Do not leave both values in separate attachments with a note to "use the latest" when their issue dates or scope differ.
For the output, state two physical examples: the known process condition at the lower endpoint and at the upper endpoint. Include the host's intended units. This makes reversed distance-versus-level scaling easier to spot than a bare request for 4-20 mA. The range-setting guide explains how those endpoints relate to the physical datum.
On receipt, compare the order acknowledgement, nameplate and configuration record with that final sheet. A changed output version or connection requires review, even when the family model number remains the same. Keep proposed substitutions separate until their effect is accepted.
Quotation questions
Q1. Should every supplier use our preferred units?
It helps comparison, but a clearly labelled conversion is acceptable. Retain the original value and its basis where pressure, temperature or a reference dimension could be misunderstood. Do not remove qualifying notes during spreadsheet consolidation.
Q2. Can a larger quoted range be accepted without further checks?
No. Review the usable near distance and antenna assembly too. More far-range capacity does not prove that the required high-level position or existing nozzle remains suitable.
Summary
Resolve meaning, units and direction before approving a radar order. Send the reconciled specification with the tank section so METRAVON can quote against one unambiguous requirement.
