BeaconMedaes dMED 7 Instruction Book page 47

Instruction book
3.3.2 Plant fault
Description
A fault has occurred which potentially leads to the system performing sub-optimal, and if left unattended
could result in pressure loss or a bad dew point.
Causes and remedies
This alarm can be caused by one of following causes:
1. Slave compressor(s) switched to local:
The Local/LAN switch is set to local. If there is no reason for it, switch it back to LAN control.
This is not a fault as such, but constitutes a situation which is sub-optimal. The central controller can't
control the compressor to ensure even wear or respond to the demand, based on pressure difference per
unit of time.
2. Slave compressor(s) switched to Emergency Forced Local:
A fault may have occurred whereby the system itself did not sustain the pressure at the required minimum.
Emergency forced local will start every compressor that is not in Local Stopped State automatically, based
on only one input: the compressor's local pressure transducer sensing a too low pressure level.
Please contact your customer contact. Once the cause is fixed and pressure is sufficient, the user can only
reset this warning by pressing the Escape button of each compressor. If not, the compressor will run
infinitely in this safety mode.
3. Slave compressor(s) generated alarm/failure:
Each alarm or failure generated on one of the compressors will automatically be transmitted to the central
controller and trigger the plant fault alarm. Consult the compressor overview screen for details on the
exact failure or alarm and on which compressor they occurred.
See the compressor manual for failure types and how to resolve them. Once all compressor alarms and
failures are resolved, the plant fault error will disappear automatically.
4. All slave compressors in load
There is a peak of high flow demand or the plant is not properly sizes resulting in all compressors being
required to deliver air. As this is an sub-optimal condition, an alarm is being generated. This alarm is
automatically reset once one or more compressors are stopped.
If the problem persists, contact BeaconMedeas.
5. No answer from the slave compressor(s):
Interrelated with the switched to forced local fault, this fault can cause the central controller not to find
the compressor controller. After resetting the Emergency Forced Local as indicated, also the following
procedure must be carried out (full access need to be obtained): go to Commands and press Reset
6. No communication:
Either the controller has no electrical supply or there is a CAN network error.
Taking into account the precautions of chapter
available to the controller and fix if necessary. If the voltage supply is adequate, check the software CAN
settings in both the compressor controllers and the ES-MED central controller (see previous chapters).
Verify that the CAN cables are correctly connected to the other cubicles. To do so, open the cubicle and
verify that the CAN cable is correctly connected between the cubicle back plate and the controller. If that
is the case, open the CAN connectors and verify that the wires are correctly connected.
Contact BeaconMedæs for further investigation.
After fixing the problem, the status should automatically reset. If it doesn't, press <Local> in the commands
screen of the central controller and select <ES Off> in the ES menu (see
Then select "On" again and press start in the commands menu. Alternatively, in the CAN menu, press
<CAN Off> and <On> again.
7. Dryer dew point alarm
2920 7099 70
Maintenance warnings, check that supply voltage is
Central controller operation).
45