N
We are facing an issue with Drager Polytron FX LEL Detector at our site.
Background Info:
Splash guards are also installed at these detectors to avoid splashing on the sensor. We have EDC (Ethylene Di chloride) & VCM (vinyl chloride monomer) in our atmosphere. The presence of these chemicals is at around 30-50 ppm all the time.
The DrägerSensor is a transducer for measuring the partial pressure of
combustible gases and vapors contained in ambient air. It uses the heat-of combustion principle.
Problem:
We have observed that a couple of these LEL Detectors go into the software menu and the Analog Output goes to its maintenance signal (forced to 3mA which is as per vendor documentation).
This happens in the field randomly when no job is being done on the Detector and we get to know about this problem as an alarm on our Control System since the value is forced to 3mA.
We suspect that it might be due to the movement of some magnetic tool and / or walkie talkie radio signal interference with the detector magnetic user input module. They are configured with a magnetic wand.
Have you had any similar complaints of Detectors going into Software Menu or taking magnetic inputs inadvertently in the field? If yes what are its causes and remedial steps to avoid this.
Background Info:
Splash guards are also installed at these detectors to avoid splashing on the sensor. We have EDC (Ethylene Di chloride) & VCM (vinyl chloride monomer) in our atmosphere. The presence of these chemicals is at around 30-50 ppm all the time.
The DrägerSensor is a transducer for measuring the partial pressure of
combustible gases and vapors contained in ambient air. It uses the heat-of combustion principle.
Problem:
We have observed that a couple of these LEL Detectors go into the software menu and the Analog Output goes to its maintenance signal (forced to 3mA which is as per vendor documentation).
This happens in the field randomly when no job is being done on the Detector and we get to know about this problem as an alarm on our Control System since the value is forced to 3mA.
We suspect that it might be due to the movement of some magnetic tool and / or walkie talkie radio signal interference with the detector magnetic user input module. They are configured with a magnetic wand.
Have you had any similar complaints of Detectors going into Software Menu or taking magnetic inputs inadvertently in the field? If yes what are its causes and remedial steps to avoid this.