EC-C+DC 11.1 Application

Application Manual
DC/DC Converter
EC-C1200-450
Firmware version 11.1
Document version 1.0
CONFIDENTIAL
The content of this document is confidential and proprietary to Danfoss EDITRON Oy. The use of
information contained herein is restricted solely to the recipient. Use for any other purpose
without the written prior permission of Danfoss EDITRON Oy is expressly prohibited.
Classified as Business
EC-C1200-450 DC/DC CONVERTER – Application Manual
Table of Contents
1. Revision history .................................................................................................................................................... 3
2. Introduction .......................................................................................................................................................... 4
3. Command configuration ...................................................................................................................................... 5
3.1. Command sources ........................................................................................................................................ 5
3.2. Available commands ................................................................................................................................... 6
3.3. Converter limits ............................................................................................................................................. 7
3.3.1. High voltage side protections ........................................................................................................ 7
3.3.2. Low voltage side protections ......................................................................................................... 8
3.4. Dynamic limit validation........................................................................................................................... 10
3.4.1. Limit validity (coherence) checks ................................................................................................ 10
3.4.2. Validation against parameter limits ........................................................................................... 11
3.5. Command configurations ........................................................................................................................ 12
4. Application parameters ...................................................................................................................................... 13
4.1. Parameter group 5.50.3 Command configuration 1 ........................................................................ 13
4.4. Parameter group 5.50.6 Parameter inputs .......................................................................................... 15
4.5. Parameter group 5.50.7 Limit validation ............................................................................................. 15
4.6. Parameter group 5.50.8 Run command types ................................................................................... 16
5. Application signals ............................................................................................................................................. 17
5.1. Signal group 5.50.1 Used commands ................................................................................................... 17
5.2. Signal groups 5.50.2 – 5.50.5 Input sources........................................................................................ 17
5.3. Signal group 5.50.10 Statuses ................................................................................................................. 19
6. Diagnostic control with PowerUSER .................................................................................................................. 20
6.1. Diagnostic control example .................................................................................................................... 21
7. System application ............................................................................................................................................. 22
7.1. Available commands ................................................................................................................................. 22
7.2. Application parameters ............................................................................................................................ 22
7.2.1. Parameter group 1.50.1 General ................................................................................................. 22
7.2.2. Parameter group 1.50.3 Command configuration 1 ............................................................. 22
7.2.5. Parameter group 1.50.6 Parameter inputs ............................................................................... 23
7.3. Application signals ..................................................................................................................................... 24
7.3.1. Signal groups 1.50.1 – 1.50.5 Input sources ............................................................................. 24
7.3.2. Signal groups 1.50.10 – 1.50.20 Statuses .................................................................................. 25
8. Glossary ............................................................................................................................................................... 26
9. References ........................................................................................................................................................... 27
2 | © Danfoss | October 2021

1. Revision history
Revision Date Description

1.0 2021-10-29 First release.
October 2021 | © Danfoss | 3

2. Introduction
Application is a component in the software of the EC-C1200+DC converter. Its role is to connect the various user
interfaces to the functionalities implemented by the converter. The key functionality implemented by the EC-
C1200+DC converter is to convert DC voltage from one level to another, while ensuring the safety of operation with a
protection system. On the other hand, there are various ways that can be used to connect the converter to the system-
level control. There are two CAN ports in the EC-C1200+DC converter, several I/O lines, and a possibility to connect to
the converter with the PowerUSER diagnostic software. The application logic and its parameters define which of these
control methods are used to give commands, references, limits and the like to the control system and other converter
functionalities.
Figure 1 illustrates the role of the application by way of an example. On one hand, the application connects to the
DC/DC control and protection systems inside the converter, and, on the other hand, it connects to both the CAN bus
and the user I/O interface, which are further connected to a system-level electronic control unit (ECU) that decides
when the converter should be running, with which references and limits, and so forth.
DC/DC converter application

(DC-APP)
Control Protections CAN I/O
ECU
Figure 1. The application functions as the bridge between converter functionalities (e.g., control and protections) and the
user of the converter. The user of the converter in this example is the electronic control unit (ECU), which is connected to the
EC-C1200+DC converter over the CAN bus and user I/O lines.
This document describes the standard DC/DC converter application (DC-APP) of the EC-C1200+DC converter, its
internal logic, and parameterization. The document is intended to be used in conjunction with other EC-C1200+DC
documentation, such as the communication manual [1], the user I/O configuration manual [2], and the user guide [3].
Underlined text indicates a parameter, a signal, a parameter group, or a signal group. See section 8 for
glossary of terms.

3. Command configuration
The converter does not do anything unless commanded to. The commands include typically references to the DC/DC
control (such as HV voltage or LV current reference), which of these references to be used (the control mode), limits to
obey, and when to run and when to stop. These commands can come from multiple sources. This section describes
how the EC-C1200+DC converter can be configured to listen to the commands.
The following sections list the available command sources and available commands, detail the parameters that can be
used as command sources, and describe the command validation mechanisms implemented by the converter
software.
3.1. Command sources

The supported sources for the commands are
1) Diagnostic interface. The diagnostic interface refers to using the converter with the PowerUSER diagnostic
software. PowerUSER can be connected to the converter either over the dedicated diagnostic port (with serial
connection) or through the CAN bus. The diagnostic interface mechanism is the same regardless of the
electrical connection type. The diagnostic interface is typically used to take control of the converter when
commissioning the system or servicing/troubleshooting the converter or the system that it is form a part of.
2) CAN protocol stack 1. There are two physical CAN ports in the EC-C1200+DC converter. On top of the physical
layer (CAN 2.0B), a communication protocol stack is needed to define the contents of the CAN messages.
Details of the CAN protocols are given in the communication manual of the EC-C1200+DC converter [1]. All
communication protocols implement at least one instance of the protocol stack, and the command source
“CAN protocol stack 1” is always available. For the CANopen protocol, there are two instances of the protocol
stack that can be configured to the two CAN ports. In this case the command source “CAN protocol stack 2”
is also available. Separate CAN protocols for the two CAN ports (e.g., CANopen and SAE-J1939) are not
supported with the current firmware version.
3) CAN protocol stack 2. The second instance of the communication protocol stack, if implemented. See the
previous item.
4) User I/O interface. There are analog/digital inputs and outputs available in the EC-C1200+DC converter. Most
I/O lines can be used as digital I/O and analog inputs, but there may be restrictions as to the capabilities of
individual I/O lines. As the number of the I/O lines is rather small, not all available converter inputs and
outputs can be routed through the interface. Therefore, it is possible to select which I/O lines are connected
to which inputs and outputs. See [2] for more information.
5) Parameters. If a command to the converter does not have to be changed dynamically (i.e., when the converter
is running), it may be feasible to set the input to a constant value by using a parameter. An example would
be setting the LV voltage reference of a supercapacitor to a constant value with a parameter (the run
command could then come, e.g., from the user I/O interface).

3.2. Available commands

The preceding section described the sources for different commands. This section lists the commands available. The
source for each command can be selected from the options described in the preceding section by using parameters
as described in section 4. The available commands are listed in Table 1.
Table 1. Available commands.

Command name Description Notes
Request command Used to request that the control be For a detailed description of
transferred to the requesting command configurations, see
command configuration section 3.5.
Run command Command to start the DC/DC Requires a high level to keep
converter control running.
See section 4.6 for information how
to configure whether the run
command is level sensitive or edge
sensitive.
Control mode Selection of the used control mode The control mode can be changed
(reference type). The supported when the converter is running if the
control modes are source of the control mode is not
 LV current set to be the parameter.
 Power Parameters cannot be changed
 HV voltage when the application is running.
 LV voltage
LV voltage reference Reference for LV voltage
HV voltage reference Reference for HV voltage
LV current reference Reference for LV current Positive current direction is
from HV to LV.
Power reference Reference for the converter electrical Positive power direction is
power from HV to LV.
Power limits Limits for the converter electrical
power
Current limits Limits for LV current
LV voltage limits Limits for LV voltage
HV voltage limits Limits for HV voltage

3.3. Converter limits

The EC-C1200+DC converter can be configured to protect the equipment against excessively high voltages and high
powers on both the low voltage side (LV-side) and high voltage side (HV-side), as well as against the currents on LV-
side of the converter.
There are two types of voltage protection mechanisms: trips and limits. If the voltage goes higher than an overvoltage
protection trip level, the converter will activate a fault and stop the control. A limit is a threshold value that the converter
attempts to keep the corresponding value over or under. Power and LV-side current limits are given in terms of
direction of the current flow, i.e., from LV to HV or from HV to LV. Choosing and validating them is introduced in section
3.4. Setting the over- and undervoltage limits for both voltage sides is explained next.
3.3.1. High voltage side protections
The EC-C1200+DC converter can be configured to protect the equipment against excessively high voltage and to
protect the system against the effects of a too low voltage. These are referred to as the overvoltage and undervoltage
protections, respectively. Overvoltage on the HV-side is dangerous to the equipment, including the EC-C1200+DC
converter itself. Undervoltage is not in itself dangerous, but it may lead into excessively high currents, currents flowing
into the wrong direction, or other system-level problems.
There are multiple trip levels on the HV-side of the converter. The hardware overvoltage trip level is fixed and set at
1050 V. The parameter 1.2.1 DC link overvoltage trip level sets a user-configurable overvoltage trip level, 1.2.2 DC link
undervoltage trip level sets a user-configurable undervoltage trip level, and 5.1.1.3 Phase current trip level sets a user-
configurable overcurrent trip level. There are also two overvoltage limits and two undervoltage limits on the HV-side,
as shown in Figure 2.
UDC
1050 V Overvoltage HW trip level (not parameterizable)
1.2.1 DC link overvoltage trip level
5.1.4.2 HV overvoltage limit, full limitation*
5.1.4.3 HV overvoltage limit, begin limitation*
5.1.4.11 HV undervoltage limit, begin limitation*
5.1.4.12 HV undervoltage limit, full limitation*
1.2.2 DC link undervoltage trip level
0V
Figure 2. HV-side voltage trip level (red) and limit (yellow) parameters. Overvoltage and undervoltage limits are shown.
Voltage limits marked with asterisks (*) can be dynamic (i.e., come from CAN or I/O).
The overvoltage and undervoltage limits are threshold values between which the converter attempts to keep the
voltage by reducing the current. Linear undervoltage and overvoltage controllers reduce current from maximum
allowed current to zero according to values set by voltage begin limitation and full limitation parameters. This
mechanism is depicted in Figure 3 for the HV-side.

5.1.4.12 HV undervoltage limit, full limitation
I 5.1.4.11 HV undervoltage limit, begin limitation
HV to LV
U HV
LV to HV
5.1.4.2 HV overvoltage limit, full limitation
5.1.4.3 HV overvoltage limit, begin limitation
Maximum current HV to LV
Maximum current LV to HV
Figure 3. Linear HV-side undervoltage and overvoltage limits. The allowed current is limited linearly between the ramp
endpoint voltages.
3.3.2. Low voltage side protections

On the LV-side of the converter, there is one overvoltage trip level, 5.1.3.4 LV overvoltage trip level. There are also two
overvoltage limits and two undervoltage limits, as shown in Figure 4.
UDC
5.1.3.4 LV overvoltage trip level
5.1.3.2 LV overvoltage limit, full limitation*
5.1.3.3 LV overvoltage limit, begin limitation*
5.1.3.11 LV undervoltage limit, begin limitation*
5.1.3.12 LV undervoltage limit, full limitation*
0V
Figure 4. LV-side voltage trip level (red) and limit (yellow) parameters. Overvoltage and undervoltage limits are shown.
Voltage limits marked with asterisks (*) can be dynamic (i.e., come from CAN or I/O).
For the LV-side, the overvoltage and undervoltage mechanism is depicted in Figure 5.

5.1.3.3 LV overvoltage limit, begin limitation

I
5.1.3.2 LV overvoltage limit, full limitation
HV to LV
U LV
LV to HV
5.1.3.11 LV undervoltage limit, begin limitation
5.1.3.12 LV undervoltage limit, full limitation
Maximum current HV to LV
Maximum current LV to HV
Figure 5. Linear LV-side undervoltage and overvoltage limits. The allowed current is limited linearly between the ramp
endpoint voltages.

3.4. Dynamic limit validation

Dynamically given limits, such as those coming from the CAN bus, must pass through a number of checks to be taken
into use. First, the internal coherence of the limits is checked (e.g., maximum cannot be smaller than minimum).
Second, if the limits are internally coherent, their values are limited between the maxima and minima set by the
corresponding parameters in parameter group 5.1 Limits.
3.4.1. Limit validity (coherence) checks
The converter application checks the incoming dynamic limits for internal coherence (validity). The limit validity checks
performed by the application are the following for quantities with a minimum and a maximum:
1) Both the minimum and the maximum must have a valid value. Invalid values may result, e.g., from CAN bus
by exceeding the valid data range.
2) The maximum must be greater than or equal to the minimum.
If the limits are not valid, the converter will not start. To start the converter from CAN, by default a rising edge in the
run command is required (see section 4.6). If invalid limits are given, then a rising edge in run command, followed by
valid limits, the converter will not start. A rising edge in the run command together with valid limits are required.
If limits become invalid when the converter is already running, the converter will either trip or use the last valid limit
values. The behavior can be configured for each limit separately. The trip will specify the failed validation check in the
argument of the application fault.
Table 2 lists the fault arguments and the parameters that can be used to change the reaction of the converter to invalid
limit values.
Table 2. Application fault arguments.

Fault argument, hex (dec) Reason Parameter
0x1001 (4097) Current limits invalid 5.50.7.1 Trip on invalid current limits
0x1002 (4098) Power limits invalid 5.50.7.2 Trip on invalid power limits
0x1003 (4099) LV overvoltage limits invalid 5.50.7.3 Trip on invalid LV overvoltage limits
0x1004 (4100) LV undervoltage limits invalid 5.50.7.4 Trip on invalid LV undervoltage limits
0x1005 (4101) HV overvoltage limits invalid 5.50.7.5 Trip on invalid HV overvoltage limits
0x1006 (4102) HV undervoltage limits invalid 5.50.7.6 Trip on invalid HV undervoltage
limits
Undervoltage and overvoltage limit checks are

1) Correct order of the overvoltage and undervoltage protection ramp endpoints (overvoltage control full
reduction greater than or equal to begin reduction, undervoltage control full reduction smaller than or equal
to begin reduction)
2) Correct order of overvoltage and undervoltage limits relative to each other (overvoltage full reduction
greater than or equal to undervoltage full reduction)

3.4.2. Validation against parameter limits

After the internal coherence of the incoming dynamic limits has been checked, the limits are validated against the
parameter values of the corresponding limits. The parameter values represent the highest limits, and the dynamic
limits cannot expand the allowed range of operation. It should be noted that exceeding parameter limits will not raise
a fault.
For overvoltage and undervoltage controllers, the dynamic values must fall between the parameters Overvoltage limit,
full limitation and Undervoltage limit, full limitation. The overvoltage and undervoltage limits must have positive
values and the following rules apply
1) Overvoltage limit, begin limitation must be at least 5 V smaller than Overvoltage limit, full limitation. This sets
the maximum steepness of the linear overvoltage protection ramp. If given limits are too close to each other,
control will decrease Overvoltage limit, begin limitation so that 5 V difference is achieved.
2) Undervoltage limit, begin limitation must be at least 5 V greater than Undervoltage limit, full limitation limit.
This sets the maximum steepness of the linear undervoltage protection ramp. If given limits are too close to
each other, control will increase Undervoltage limit, begin limitation so that 5 V difference is achieved.
Exceeding parameter limits will not raise a fault.

3.5. Command configurations

The preceding sections discussed the available commands, conventions and limitations related to them, and available
command sources. There may be use cases where the source of a command needs to be changed when the converter
is running. To be able to do this, there are three configurable command configurations in the EC-C1200+DC application.
A command configuration is a parameterization for the sources of the commands. One command configuration is
active at a time, and the request command input is used to request the command to be transferred to the requesting
command configuration. Figure 6 illustrates the command configurations.
Command conf. 1 Command conf. 2 Command conf. 3

Request command source Request command source Request command source
Run command source Run command source Run command source
Control mode source Control mode source Control mode source
LV voltage reference source LV voltage reference source LV voltage reference source
HV voltage reference source HV voltage reference source HV voltage reference source
... ... ...
Figure 6. There are three user-configurable command configurations, and the sources for the commands can be configured
differently in the different command configurations. The “Request command” input is used to transfer command to a
command configuration. The … denotes that the lists continue downward.
Each command configuration has a priority. The priority works so that whenever a command configuration with a
higher priority (0 being the highest, 10 the lowest) than the currently active command configuration is requesting
control, the active command configuration will be changed to the requesting command configuration. In addition to
the three configurable command configurations, there is also a command configuration 0 that has been permanently
configured to have the highest priority so that it can always take control. This is used by the PowerUSER diagnostic
program to implement a diagnostic control place, which can always take control away from the CAN or I/O interface.

4. Application parameters
Parameters are used to configure the EC-C1200+DC application and to give constant inputs to it. Parameters are stored
to non-volatile memory so that they will not be lost when the converter is powered down. Parameters cannot be
modified when the converter is running.
4.1. Parameter group 5.50.3 Command configuration 1

This is the default command configuration of the EC-C1200+DC converter. The converter is parameterized by default
so that all references and the run command come from the CAN bus, but the control mode as well as all limits come
from the parameters. Table 3 lists the default value for command configuration 1.
Table 3. Command configuration 1.

ID Name Default value Notes
5.50.3.1 Priority 3
5.50.3.2 Request command source Parameter Always requests command by default.
5.50.3.3 Run command source CAN 1
5.50.3.4 Control mode source Parameter
5.50.3.5 LV voltage reference source CAN 1
5.50.3.6 HV voltage reference source CAN 1
5.50.3.7 LV current reference source CAN 1
5.50.3.8 HV current reference source CAN 1
5.50.3.9 Power reference source Parameter
5.50.3.10 Current limits source Parameter
5.50.3.11 Power limits source Parameter
5.50.3.12 LV overvoltage limits source Parameter
5.50.3.13 LV undervoltage limits source Parameter
5.50.3.14 HV overvoltage limits source Parameter
5.50.3.15 HV undervoltage limits source Parameter


Command configuration 2 is by default not parameterized in a meaningful way. It should be reconfigured if multiple
command configurations need to be used. Its priority is lower than that of command configuration 1, so that by default
the CAN interface is in control. Table 4 lists the default values for command configuration 2.

5.50.4.1 Priority 6 Lower than Configuration 1.
5.50.4.2 Request command source CAN 1 Does not get the command unless the priority
is made higher (smaller number) than
configuration 1.
5.50.4.3 Run command source Parameter
5.50.4.4 Control mode source Parameter
5.50.4.5 LV voltage reference source Parameter
5.50.4.6 HV voltage reference source Parameter
5.50.4.7 LV current reference source Parameter
5.50.4.8 HV current reference source Parameter
5.50.4.9 Power reference source Parameter
5.50.4.10 Current limits source Parameter
5.50.4.11 Power limits source Parameter
5.50.4.12 LV overvoltage limits source Parameter
5.50.4.13 LV undervoltage limits source Parameter
5.50.4.14 HV overvoltage limits source Parameter
5.50.4.15 HV undervoltage limits source Parameter

This command configuration is configured by default identically to command configuration 2, except that the priority
is lower and request command comes from CAN 2. Table 7 lists the default values for command configuration 3.

5.50.5.1 Priority 9
5.50.5.2 Request command source CAN 2
5.50.5.3 Run command source Parameter
… … … …

4.4. Parameter group 5.50.6 Parameter inputs

Table 6 lists the parameter inputs and their default values.
Table 6. Parameter inputs.

5.50.6.1 Request command TRUE Used to make command configurations
request command all the time.
5.50.6.2 Run command FALSE Can be used to implement an auto-starting
converter. This is not recommended in most
cases.
5.50.6.3 Control mode 0 0 – LV current
1 – Power
2 – HV voltage
3 – LV voltage
5.50.6.12 LV voltage reference 0V
5.50.6.13 HV voltage reference 0V
5.50.6.14 LV current reference 0A
5.50.6.15 Power reference 0 kW
4.5. Parameter group 5.50.7 Limit validation

These parameters are used to configure the behavior of the dynamic limit coherence checks. Limit validation
configuration default values are given in Table 7.
Table 7. Limit validation.

ID Name Default value
5.50.7.1 Trip on invalid current limits FALSE
5.50.7.2 Trip on invalid power limits FALSE
5.50.7.3 Trip on invalid LV overvoltage limits FALSE
5.50.7.4 Trip on invalid LV undervoltage limits FALSE
5.50.7.5 Trip on invalid HV overvoltage limits FALSE
5.50.7.6 Trip on invalid HV undervoltage limits FALSE

4.6. Parameter group 5.50.8 Run command types

Run command type parameters are used to configure run command input types, either level sensitive or rising edge
sensitive run command is used. TRUE indicates a rising edge is needed, and FALSE equals level sensitive run command.
The run command types are listed in Table 8.
Table 8. Run command types.

ID Name Default value
5.50.8.1 Diagnostic run command requires rising edge TRUE
5.50.8.2 CAN 1 run command requires rising edge TRUE
5.50.8.3 CAN 2 run command requires rising edge TRUE
5.50.8.4 I/O run command requires rising edge TRUE
5.50.8.5 Parameter run command requires rising edge FALSE

5. Application signals
The previous section described the parameters of the EC-C1200+DC application. Parameters are used primarily for
configuring the converter. Signals, on the other hand, are used to monitor the converter and to give dynamic inputs
(inputs that change when the converter is running) to the converter. Signals are not stored to non-volatile memory.
5.1. Signal group 5.50.1 Used commands

Used commands signal group can be used to monitor which inputs are being used by the application. The used
commands are given in Table 9.
Table 9. Used commands.

ID Name Notes
5.50.1.1 Active command configuration
5.50.1.2 Run command FALSE – Stop
TRUE – Run
5.50.1.3 Control mode 0 – LV current
1 – Power
2 – HV voltage
3 – LV voltage
5.50.1.10 HV voltage reference
5.50.1.11 LV voltage reference
5.50.1.13 LV current reference
5.50.1.14 Power reference
5.50.1.20 Power limit, HV to LV
5.50.1.21 Power limit, LV to HV
5.50.1.22 LV current limit, HV to LV
5.50.1.23 LV current limit, LV to HV
5.50.1.30 LV overvoltage limit, full limitation
5.50.1.31 LV overvoltage limit, begin limitation
5.50.1.32 LV undervoltage limit, begin limitation
5.50.1.40 HV overvoltage limit, full limitation
5.50.1.41 HV overvoltage limit, begin limitation
5.50.1.42 HV undervoltage limit, begin limitation
5.2. Signal groups 5.50.2 – 5.50.5 Input sources

Input sources signal groups contain signals for the different input sources. They contain the same signals as the group
5.50.1 but for one input source in each group. The signals in the group 5.50.1 show the value of the source in use.
The signal groups have been allocated to the different sources as shown in Table 10.

Table 10. Input sources.

Signal group Source Notes
5.50.2 Diagnostic For controlling the drive with PowerUSER
diagnostic program.
5.50.3 CAN 1 First CAN stack (both SAE-J1939 and CANopen).
5.50.4 CAN 2 Second CAN stack (only with CANopen).
5.50.5 I/O User I/O inputs can be connected to these
signals with the I/O-to-signal mapping feature.
For more information, refer to [2].
The signals within each group are according to Table 11.
Table 11. Signals in each input source. X denotes the signal group.
ID Name Notes
5.50.X.1 Request command FALSE – Do not request
TRUE – Request
5.50.X.2 Run command FALSE – Stop
TRUE – Run
5.50.X.3 Control mode 0 – LV current
1 – Power
2 – HV voltage
3 – LV voltage
5.50.X.10 HV voltage reference
5.50.X.11 LV voltage reference
5.50.X.13 LV current reference
5.50.X.14 Power reference
5.50.X.20 Power limit, HV to LV
5.50.X.21 Power limit, LV to HV
5.50.X.22 LV current limit, HV to LV
5.50.X.23 LV current limit, LV to HV
5.50.X.30 LV overvoltage limit, full limitation
5.50.X.31 LV overvoltage limit, begin limitation
5.50.X.32 LV undervoltage limit, begin limitation
5.50.X.33 LV undervoltage limit, full limitation
5.50.X.40 HV overvoltage limit, full limitation
5.50.X.41 HV overvoltage limit, begin limitation
5.50.X.42 HV undervoltage limit, begin limitation
5.50.X.43 HV undervoltage limit, full limitation

5.3. Signal group 5.50.10 Statuses

Status signals describe the application outputs, they are as shown in Table 12.
Table 12. Application outputs.

ID Name Notes
5.50.10.1 HV voltage
5.50.10.2 LV voltage
5.50.10.3 HV current
5.50.10.4 LV current
5.50.10.5 Power
5.50.10.10 Available LV current, HV to LV
5.50.10.11 Available LV current, LV to HV
5.50.10.40 Control status word See [1] for bit definitions.
5.50.10.60 Control limit word See [1] for bit definitions.
5.50.10.80 Control fault word See [1] for bit definitions.
5.50.10.100 Application status word See [1] for bit definitions.
5.50.10.120 Limit error word See [1] for bit definitions.

6. Diagnostic control with PowerUSER

The converter can be controlled locally using a combination of diagnostic and parameter command sources. The
default configuration for diagnostic control is given in Table 13, it cannot be changed.
Table 13. Default configuration for diagnostic control.

Name Source Notes
Priority 0 Highest priority.
Request command source Diagnostic 5.50.2.1 Request command
Run command source Diagnostic 5.50.2.2 Run command
Control mode source Diagnostic 5.50.2.3 Control mode
LV voltage reference source Diagnostic 5.50.2.11 LV voltage reference
HV voltage reference source Diagnostic 5.50.2.10 HV voltage reference
LV current reference source Diagnostic 5.50.2.13 LV current reference
Power reference source Diagnostic 5.50.2.14 Power reference
Current limits source Parameter 5.1.1.1 LV current limit, HV to LV
5.1.1.2 LV current limit, LV to HV
Power limits source Parameter 5.1.2.1 Power limit, HV to LV
5.1.2.2 Power limit, LV to HV
LV overvoltage limits source Parameter 5.1.3.2 LV overvoltage limit, full limitation
5.1.3.3 LV overvoltage limit. begin limitation
LV undervoltage limits source Parameter 5.1.3.11 LV undervoltage limit, begin limitation
HV overvoltage limits source Parameter 5.1.4.2 HV overvoltage limit, full limitation
5.1.4.3 HV overvoltage limit. begin limitation
HV undervoltage limits source Parameter 5.1.4.11 HV undervoltage limit, begin limitation
Since the priority of diagnostic control is 0, it can be requested over any currently active command configuration.
If the converter is running with, e.g., HV voltage limits coming from CAN 1 and diagnostic control is activated (by
requesting command with 5.50.2.1 Request command), the HV voltage limits used in diagnostic control will be those
stored in the HV voltage limit parameters and they may be different from those coming from CAN 1. Parameters cannot
be changed when the converter is running. Therefore, if the limit values in the parameters are not safe, the converter
must be stopped, and parameters changed before running with diagnostic control.
Control can be passed to the command configuration with the next-highest priority by writing FALSE to the signal
5.50.2.1 Request command.
All the limit values in PowerUSER diagnostic control come from parameters. The run command, the reference
values, or the control mode are not automatically initialized to the currently active values.
If the converter is configured so that a rising edge is required in the run command, a rising edge is required
from the active run command source for the converter to start.
Always make sure that the run command, the control mode, the reference corresponding to the selected
control mode, and the limits in the parameters are safe before requesting diagnostic control with PowerUSER.

6.1. Diagnostic control example

The converter is not modulating with command configuration 1 as the active configuration. The operator wants to
take control of the converter locally. When the operator sets the diagnostic signal for 5.50.2.1 Request command as
TRUE, the active command configuration changes to the diagnostic, sources changed can be seen in Table 14.
Table 14. Diagnostic control example sources.

Name Old value New value
Request command source Parameter Diagnostic
Run command source CAN 1 Diagnostic
Control mode source Parameter Diagnostic
LV voltage reference source CAN 1 Diagnostic
HV voltage reference source CAN 1 Diagnostic
LV current reference source CAN 1 Diagnostic
HV current reference source CAN 1 Diagnostic
Power reference source Parameter Parameter
Current limits source Parameter Parameter
Power limits source Parameter Parameter
LV overvoltage limits source Parameter Parameter
LV undervoltage limits source Parameter Parameter
HV overvoltage limits source Parameter Parameter
Limit sources do not change since they’re both coming from parameters, reference sources as well as run command
and control mode change to diagnostic. Now the converter uses the values set to the diagnostic signals. The converter
can now be controlled locally using run command, control mode and references in signal group 5.50.2.
Let’s say the operator wants to run the converter with LV voltage reference of 200 V. The operator sets the 5.50.2.3
Control mode to 3 (LV voltage), 5.50.2.11 LV voltage reference to 200 V and 5.50.2.2 Run command to TRUE. Now the
converter starts modulating and ramps the LV voltage reference to 200 V according to 5.4.2.1 LV voltage reference
ramp time and settles there.

7. System application
System application handles system-level operations not related to any specific control. This includes communicating
with subsystems such as protections, measurements, and the User I/O. The User I/O portion of system application is
discussed in [2].
The working principle is the same as in the DC/DC application. Command configurations are used to determine which
source is being listened to for each command.
7.1. Available commands

Commands available in the system application are presented in the Table 15.
Table 15. Available commands.

Command name Description
Request command Used to request that the control be transferred to the requesting
command configuration.
Clear faults Clear all active faults.
Contactor command Operate contactors in applicable devices.
Control switch command Select active control in supported software configurations.
Digital output 1 - 5 See [2] for more information.
7.2. Application parameters

The subsections below describe the parameter groups 1.50.X.
7.2.1. Parameter group 1.50.1 General
The general parameter group is given in Table 16.
Table 16. General parameters.

ID Command name Default value Notes
1.50.1.2 Fault word update period 100 ms
1.50.1.3 Digital I/O pin write mask 0 See [2] for more information.
7.2.2. Parameter group 1.50.3 Command configuration 1

The command configuration 1 is given in Table 17.

1.50.3.1 Priority 3 Higher number means lower priority.
1.50.3.2 Request command source Parameter
1.50.3.3 Contactor command source CAN 1
1.50.3.4 Control switch command CAN 1
source
1.50.3.5 Digital I/O pin write source Parameter
1.50.3.6 Clear faults source CAN 1



1.50.4.3 Contactor command source Parameter
1.50.4.4 Control switch command Parameter
source


1.50.5.3 Contactor command source Parameter
1.50.5.4 Control switch command Parameter
source
7.2.5. Parameter group 1.50.6 Parameter inputs

The default parameter inputs are given in Table 20.
Table 20. Parameter inputs.

1.50.6.1 Request command TRUE Used to make command configurations
request command all the time.
1.50.6.3 Contactor command Off
1.50.6.4 Control switch command 0
1.50.6.6 Digital output 1 FALSE

7.3. Application signals

The subsections below describe the signal groups 1.50.X.
7.3.1. Signal groups 1.50.1 – 1.50.5 Input sources
System application commands are listed in signal groups 1.50.1 – 1.50.5 which are
 1.50.1 Used commands

 1.50.2 Diagnostic commands
 1.50.3 CAN 1 commands
 1.50.4 CAN 2 commands
 1.50.5 I/O commands
Used commands group is given in Table 21.
Table 21. Used commands.

ID Name
1.50.1.1 Active command configuration
1.50.1.2 Clear faults
1.50.1.3 Contactor command

1.50.1.4 Control switch command
1.50.1.5 Digital output 1
The groups 1.50.2 – 1.50.5 have the same command signals but vary in group numbering, this is indicated with X in
Table 22.
Table 22. Commands available in each command source.

ID Name
1.50.X.1 Request command
1.50.X.2 Clear faults
1.50.X.3 Contactor command

1.50.X.4 Control switch command
1.50.X.5 Digital output 1
In addition to the commands, there are status signals available in groups 1.50.10 and 1.50.20. These are given in the
next section.

7.3.2. Signal groups 1.50.10 – 1.50.20 Statuses

System application output signals and CAN statuses are given in Table 23.
Table 23. Application outputs.

ID Name Description
1.50.10.1 Run status TRUE – Running
FALSE – Not running
1.50.10.2 Fault status TRUE – One or more faults active
FALSE – No faults active
1.50.10.3 Warning status TRUE – One or more warnings active
FALSE – No warnings active
1.50.10.4 Contactor status 0 – Off
1 – Precharge
2 – On
3 – Discharge
1.50.10.5 Control switch status The active control in supported software configurations.
1.50.10.10 Highest junction temperature
1.50.10.11 Maximum external temperature
1.50.10.12 Minimum external temperature
1.50.10.13 External temperature 1
1.50.10.18 External temperature fault word See [1] for bit definitions.
1.50.10.19 External temperature warning word See [1] for bit definitions.
1.50.10.20 External temperature status word See [1] for bit definitions.
1.50.10.40 Fault word 1 See [1] for bit definitions.
1.50.10.60 Fault word 2 See [1] for bit definitions.
1.50.10.80 Digital input 1
1.50.10.90 Analog input 1 voltage
1.50.20.1 CAN 1 signal status 0 – Invalid
1 – Valid
1.50.20.2 CAN 2 signal status 2 – Rx timeout

8. Glossary
Control mode. Determines which reference the converter is listening to.
Fault. A fault is activated as a response to an abnormal situation, such as a quantity going to dangerous level
(overcurrent, overvoltage, etc.) or some other safety-related problem (CAN timeout, etc.). Running the converter while
a fault is active is impossible.
Limit. A maximum or a minimum value for a quantity. The converter software tries to keep a quantity between its limits
by, for example, modifying the torque reference. Being at a limit is not considered an abnormal situation – it is not a
fault.
Parameter. A value which configures the behavior of the converter software. Parameters cannot be changed when
the converter is running.
Signal. A dynamic value representing the actual value of a quantity or a command to the converter.

9. References
[1] EC-C1200+DC Communication Manual. Firmware version 11.1, Document version 1.3.
[2] EC-C1200-450 User I/O Configuration Manual. Firmware version 11.1, Document version 1.0.
[3] EC-C1200-450 Electrical Converter User Guide. Document revision 0201.

About
Danfoss Power Solutions
Danfoss Power Solutions is a global manufacturer and supplier of high-quality hydraulic and electronic
components. We specialize in providing state-of-the-art technology and solutions that excel in the harsh
operating conditions of the mobile off-highway market as well as the marine sector. Building on our
extensive applications expertise, we work closely with you to ensure exceptional performance for a broad
range of applications. We help you and other customers around the world speed up system development,
reduce costs and bring vehicles and vessels to market faster.
We offer you expert worldwide support for ensuring the best possible solutions for outstanding
performance. And with an extensive network of Global Service Partners, we also provide you with
comprehensive global service for all of our components.
Danfoss Power Solutions - your strongest partner in mobile hydraulics and mobile electrification.
Products we offer:
 Bent Axis Motors  PLUS+1® joysticks and pedals
 DCV directional control valves  PLUS+1® sensors
 Electric converters  PLUS+1® software services, support, and training
 Electric machines  PLUS+1® software
 Hydrostatic motors  Position controls and sensors
 Hydrostatic pumps  PVG proportional valves
 Orbital motors  Steering components and systems
 PLUS+1® controllers  Telematics
 PLUS+1® displays
Go to www.danfoss.com for further product information.
Danfoss Power Solutions (US) Company Danfoss Power Solutions ApS

2800 East 13th Street Nordborgvej 81
Ames, IA 50010, USA DK-6430 Nordborg, Denmark
Phone: +1 515 239 6000 Phone: +45 7488 2222
Danfoss Power Solutions GmbH & Co. OHG Danfoss Power Solutions Trading
Krokamp 35 (Shanghai) Co. Ltd
D-24539 Neumünster, Germany Building #22, No. 1000 Jin Hai Rd
Phone: +49 4321 8710 Jin Qiao, Pudong New District
Shanghai, China 201206
Phone: +86 21 3418 5200
Danfoss can accept no responsibility for possible errors in catalogues, brochures, and other printed material. Danfoss reserves the right to alter its products without
notice. This also applies to products already on order provided that such alterations can be made without subsequential changes being necessary in specifications
already agreed.
All trademarks in this material are property of the respective companies. Danfoss and the Danfoss logotype are trademarks of Danfoss A/S. All rights reserved.

EC-C+DC 11.1 Application

Uploaded by

Document Informationclick to expand document information

Document Informationclick to expand document information

Copyright:

Available Formats

EC-C+DC 11.1 Application

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

EC-C+DC 11.1 Application

Uploaded by

Copyright:

Available Formats

Application Manual

Document version 1.0

2 | © Danfoss | October 2021

Revision Date Description

October 2021 | © Danfoss | 3

DC/DC converter application

Control Protections CAN I/O

4 | © Danfoss | October 2021

3.1. Command sources

October 2021 | © Danfoss | 5

3.2. Available commands

Table 1. Available commands.

6 | © Danfoss | October 2021

3.3. Converter limits

1050 V Overvoltage HW trip level (not parameterizable)

1.2.1 DC link overvoltage trip level

5.1.4.2 HV overvoltage limit, full limitation*

5.1.4.3 HV overvoltage limit, begin limitation*

5.1.4.11 HV undervoltage limit, begin limitation*

5.1.4.12 HV undervoltage limit, full limitation*

1.2.2 DC link undervoltage trip level

October 2021 | © Danfoss | 7

5.1.4.12 HV undervoltage limit, full limitation

I 5.1.4.11 HV undervoltage limit, begin limitation

5.1.4.2 HV overvoltage limit, full limitation

5.1.4.3 HV overvoltage limit, begin limitation

3.3.2. Low voltage side protections

5.1.3.4 LV overvoltage trip level

5.1.3.2 LV overvoltage limit, full limitation*

5.1.3.3 LV overvoltage limit, begin limitation*

5.1.3.11 LV undervoltage limit, begin limitation*

5.1.3.12 LV undervoltage limit, full limitation*

8 | © Danfoss | October 2021

5.1.3.3 LV overvoltage limit, begin limitation

5.1.3.11 LV undervoltage limit, begin limitation

5.1.3.12 LV undervoltage limit, full limitation

October 2021 | © Danfoss | 9

3.4. Dynamic limit validation

Table 2. Application fault arguments.

Undervoltage and overvoltage limit checks are

10 | © Danfoss | October 2021

3.4.2. Validation against parameter limits

Exceeding parameter limits will not raise a fault.

October 2021 | © Danfoss | 11

3.5. Command configurations

Command conf. 1 Command conf. 2 Command conf. 3

12 | © Danfoss | October 2021

4.1. Parameter group 5.50.3 Command configuration 1

Table 3. Command configuration 1.

October 2021 | © Danfoss | 13

4.2. Parameter group 5.50.4 Command configuration 2

Table 4. Command configuration 2.

4.3. Parameter group 5.50.5 Command configuration 3

Table 5. Command configuration 3.

14 | © Danfoss | October 2021

4.4. Parameter group 5.50.6 Parameter inputs

Table 6. Parameter inputs.