iPM 200 generator module
® Vetaphone March 2021 3401201GB
The rotation sensor is not in correct position at the roll-end
(max. 1mm), or it is defective.
In connection with exchange of roll-covering the roll can have
been turned around, that the roll-end with the metal knobs is
not placed in the same end as the sensor.
An error occurred while trying to charge the internal capacitors
Take note that this error is allowed 3 timers within 1 second
Reset error and wait 10 seconds and try again
Internal inter-lock missing.
Check Inter-lock switches connected to X5 pin 27 & 28
NB: Can be used for safety and doors see electrical diagram
See also E-12
Blocking input signal
missing
Check X5 pin 9 is connected to gnd.
Customer inter-lock missing
Check Inter-lock switches connected to X3 pin 1 & 2
The inter-lock input is typically connected in series with door
switches, check that all doors etc. are closed
Warning: Mains Power was
removed while generator
was ON
The power supply charge-up error (E-10) has occurred more
than 3 times in a row.
Generator defect. Contact support department
Communication error
between master and slave
generator
The generator has lost contact with the master generator
during discharge. This can occur if the generator is in a noisy
environment. If the generator or the cable is too close to the
discharge this could cause this error.
Power board not present:
(In Firmware versions prior to
5.20 this error can mean several
things.
Please contact support
department for help)
Generator defect. Contact support department.
Power board are in Boot
mode
(Only exists in Firmware version
5.20 and up)
Upload PU Firmware if possible or contact support department.
Internal PFC Error
(Only exists in Firmware version
5.20 and up)
Generator defect. Contact support department
The measured voltage on the primary side of the transformer is
too high. The generator has been shut down to prevent further
damage.
This error can occur due to high surge or burst pulses on the
mains supply lines.
Reset the error and wait 10 seconds and try again.
If the error persists, contact the support department