REVO DPU series

Important remarks:

  • The REVO DPU only works with REVEX or REVO C units with the DPU version for the input.
  • Please select the DPU input option when ordering a REVEX or REVO C that has to work with the REVO DPU power synchronization unit.
  • Communication port 1 (MB1) will only be for proprietary protocol, no modbus, in case of DPU input option.
Choose DPU input option for REVEX / REVO C if it has to work with REVO DPU power synchronization unit
When ordering REVEX or REVO C: select DPU input option
  • load type: all
    • 1 phase: 
      • resistive
      • short wave infrared (IR) lamps
      • transformer primary side coupled with:
        • resistive
        • MoSi2 heaters
        • SiC
        • UV lamp
      • MoSi2
      • SiC
    • 2 phase:
      • resistive with 3 phase star without neutral connection
      • resistive with 3 phase delta connection
      • short wave infrared (IR) lamps with 3 phase star connection
      • short wave infrared (IR) lamps with 3 phase delta connection
      • MoSi2 (extended version only)
    • 3 phase:
      • resistive with 3 phase star with neutral
      • resistive with 3 phase star or delta connection
      • short wave infrared (IR) lamps with 3 phase star connection with neutral
      • short wave infrared (IR) lamps with 3 phase delta or star connection
      • 3 phase transformer coupled with resistive load
      • 3 phase transformer coupled with cold resistance (MoSi2)
  • maximum load current: depending on the connected REVEX (30-280A) or REVO C (30-2100A)
  • maximum load voltage: depending on the connected REVEX (480Vac or 600Vac) or REVO C (480Vac, 600Vac or 690Vac)
  • power control input: read by REVO DPU from temperature controllers or PLC/DCS system over fieldbus communication interface
  • current measurement inputs: read by REVO DPU from connected REVEX or REVO C units via proprietary CD Automation high speed communication interface (2-wire RS-485 communication port 1)
  • power control outputs: written by REVO DPU to connected REVEX or REVO C units via proprietary CD Automation high speed communication interface (2-wire RS-485 communication port 1)
  • firing modes:
    • only full cycle -> burst fire with a minimum number of pulses of 2 (single cycle)
    • when phase-angle REVEX or REVO C units are connected: possible to select a dynamic or static turn-on control percentage to suit the type of connected load (see explanation pictures below):
      • dynamic: the conduction angle is identical to the number of burst packets generated
      • static: the conduction angle is independent of the number of burst packets generated
  • feedback of power/current/voltage: depending on the connected REVEX or REVO C unit
  • MODBUS RTU RS-485 and MODBUS TCP ethernet interface
  • fuses: inside REVEX or REVO C units
  • heater break alarm: managed autonomously, load configuration data inherited from REVO DPU
  • thyristor short circuit alarm: managed autonomously, load configuration data inherited from REVO DPU
  • Optional
    • 2nd redundant REVO DPU possible for extra reliable solution (see below)
    • ProfiNET and MODBUS TCP interface
    • ProfiBUS and MODBUS TCP interface
    • Ethernet/IP and MODBUS TCP interface
    • REVO KPC SCADA/HMI screen. Up to 24 slaves can be connected

– REVO Multichannel power controller series catalog
– REVO DPU series catalog
– Siemens PLC connectivity via TIA portal

Click here to request a quotation for the REVO DPU.

Example of REVO DPU using 24 3 phase channels with REVO C or REVEX 2 phase 30A units

Click the picture for an enlarged view.

Example of REVO DPU using 24 channels with REVO C 2 phase / 3 phase units up to 2100A

Click the picture for an enlarged view.

Firing modes

The firing mode is only full cycle -> burst fire with a minimum number of pulses of 2 (single cycle).

When phase angle REVEX or REVO C units are connected, it is possible to select a dynamic or static turn-on percentage value to suit the type of connected load.

  • dynamic: the conduction angle is identical to the number of burst packets generated
  • static: the conduction angle is independent of the number of burst packets generated
Reference: 25% (burst fire) - phase angle 100%
Reference: 25% (burst fire) - phase angle 50%

Click the picture for an enlarged view.

Static firing

Reference: 25% (burst fire) at 100% switch-on phase angle means that the REVO DPU will generate:

  • 25 packets (for 25%) switched on. At 100% full conduction phase angle (100% full sine wave)
  • 75 packets switched off
Static firing

Reference: 25% (burst fire) at 50% switch-on phase angle means that the REVO DPU will generate:

  • 25 packets (for 25%) switched on. At 50% conduction phase (50% or half sine wave)
  • 75 packets switched off
Reference: 25% (burst fire) - phase angle 25%
Reference: 75% (burst fire) - phase angle 75%

Click the picture for an enlarged view.

Dynamic firing

Reference: 25% (burst fire) at 25% switch-on phase angle means that the REVO DPU will generate:

  • 25 packets (for 25%) switched on. At 25% conduction phase angle (25% or 1/4 of sine wave)
  • 75 packets switched off
Dynamic firing

Reference: 75% (burst fire) at 75% switch-on phase angle means that the REVO DPU will generate:

  • 75 packets (for 75%) switched on. At 75% conduction phase angle (75% or 3/4 of sine wave)
  • 25 packets switched off

REVO DPU redundancy

  • The REVO DPU can be redundant so, in case of a malfunction, a second REVO DPU can take control of the system to ensure correct operation.
  • The  second REVO DPU is connected in parallel to the first and both must be connected via the front communication port. In doing so, the primary REVO DPU will share configuration and process information with the secondary REVO DPU, which will continuously monitor the operation of the primary and be ready to take over if there is a communication failure to the REVO C – REVEX drives.
  • The PLC will take care of duplicating the data in case of a fieldbus so as to guarantee a ready take-over in the event of a malfunction of the primary.
  • The REVO DPU primary and secondary have different firmware so a primary will always be a primary.
  • If the primary has an issue, the secondary will take over
  • if the primary is reconnected (correctly functioning again), the secondary will leave the field to the primary and return to monitoring its proper functioning.

Click the picture for an enlarged view.