Integration guidelines
This section describes the process of the controller integration. It covers important integration aspects of the typical components used in the end application with the motor inverter.
The section is divided into several categories covering phases of integration:
- Before purchase: Covers selection of the appropriate HW and FW of the controller.
- Integration: Describes important integration aspects of the controller.
- Typical wiring diagram: This shows the wiring diagram for the standard version of the controller together with a description of the main components.
- Commissioning: Describes basic steps for controller commissioning.
Before purchase
The motor controller is a configurable device. Defining proper Product variant (see chapter Product Overview of the corresponding controller) and selecting the appropriate FW application before purchasing is necessary.
Order lead time depends on the configuration. Variants other than default usually have a longer lead time.
Motor sensor selection
Electric motors with permanent magnets are manufactured with various rotor position sensor types. The controller supports only some of them and paying attention to its selection is necessary. Refer to the Motor sensors chapter for more details about various rotor position sensor types. Check Product overview of the selected controller for supported sensor types.
Driver algorithm selection
The controller can be equipped with two driver algorithms - BLDC and VECTOR. The correct algorithm depends mainly on the used motor and intended use case.
Each of the available algorithms has some advantages and disadvantages:
BLDC
| Pros | Cons |
|---|---|
| Simple | Usually lower efficiency |
| Suitable for applications where precise control is not required | Higher vibrations and noise |
VECTOR
| Pros | Cons |
|---|---|
| Efficient motor control | Requires higher computation power |
| Suitable for all kinds of applications | Driver settings fine-tuning may be required |
FW application
One of the two standard FW applications (LYNX or OPHION) must be selected before the purchase.
Generally, LYNX is more suitable for traction applications, because it has many useful features, settable by parametrization. OPHION on the other hand is simpler and is usually a good choice for general motor control applications.
Integration
Protective functions
The controller has several built-in functions to protect both itself and external components from dangerous states. Understanding these protections is crucial for successful controller integration.
In general, there are three protective mechanisms:
- Controller's diagnostics
- High-priority protective functions
- Low-priority protective functions
Controller's diagnostics
This mechanism aims to avoid damage to the controller. It is divided into two separate functions:
-
Initialization diagnostic: Runs at the start of the controller and checks operating conditions and status of the power stage. The power stage is not activated if there is any problem.
-
Run-time diagnostic: Continuously monitors phase currents and input voltage for dangerous states. If any of these variables overcome the hard-coded thresholds, the powerstage is immediately turned OFF.
In both states the power stage is disabled (MOSFETs are not driven) and the error word indicates the particular issue. The controller also preserves a log of the last error codes.
High-priority protective functions
This mechanism aims to avoid entering a dangerous state to the controller. The protections cover phase currents, input voltage, temperature, motor position sensor and internal analog-to-digital converter (ADC).
Some protections functions (currents, voltages, temperatures) cause a reduction of the output current. Position sensor and ADC error causes temporary disabling of the power stage until the system returns to normal values. Status of the high-priority limiter is indicated by the status word.
Low-priority protective functions
This mechanism aims to protect external components such as the battery and motor. Limiters cause a reduction of the phase current. Status of the low-priority limiter is indicated by the limiter word.
Water and dust protection
The device has been designed with safety measures to ensure effective protection against water and dust. Meeting the defined criteria for water and dust resistance depends on installing the mating signal connectors, proper installation of cables, and using the corresponding blanks on unused pins. We strongly recommend adhering to these measures to ensure an optimal level of protection for the device when used in various environments.
Water sensitive equipment - risk of damage to equipment
Cooling requirements
The controller is designed to be mounted on a surface (heatsink) capable of efficiently dissipating heat generated by the power stage. See product Thermal specification chapter for example heatsink thermal resistance calculation. To ensure sufficient heat dissipation, the used heat sink must have a thermal resistance equal to or lower than the value calculated for the given working conditions. Additionally, it is crucial to ensure that the contact area between the heat sink and the controller is sufficiently flat and clean before installation. To achieve optimal thermal parameters, the use of thermal conductivity paste is recommended.
The controller is designed to operate continuously at a heatsink temperature of up to 90 °C. It is essential to ensure that this temperature is not exceeded during operation in the end application under all operating conditions, thereby ensuring compliance with the declared parameters. If the heat sink temperature exceeds 90 °C, there is a gradual limitation of the output current up to the full limitation value at 100 °C. In case the heat sink temperature exceeds 90 °C during operation, it is recommended to improve cooling options, use a controller with a higher current load, or reduce the power parameters of the end application.
Operation at reduced power – risk of damage to equipment and/or malfunction
Exceeding the intended operating temperature leads to a reduction in maximum output power, potentially diminishing the motor controller's lifespan and causing operational malfunctions.
Reversed polarity protection
Bat+ and Bat- power inputs are not protected against reverse polarity. The power input for logic circuits operating with battery voltage is not protected against reverse polarity.
It is the integrator's responsibility to ensure proper protection against reverse polarity.
Orientation
Position the controller in a way that connectors are shielded from water splashes and dust.
General recommendations for designing signal and power cables
Signal cables
- Keep signal cables separate from power cables.
- When connecting to a PC, use galvanically isolated communication devices to prevent potential damage to the PC.
- Follow the recommended installation of connectors and their pins (according to the manufacturer's recommendations) to ensure reliable operation.
- If possible, avoid using power ground as a signal conductor.
- Consider options for routing signal cables to achieve the best EMC characteristics (emission, immunity to external electromagnetic fields).
- Route the motor sensor wires in a single bundle. When shielding of these wires is required, it should be connected only on one side of the cable (either controller side or motor sensors side).
Power cables
- The sizing of power cables is contingent upon the application loading profile. siliXcon recommends utilizing silicone insulation (SIFF) cables, taking advantage of their superior thermal rating (higher current capacity) compared to standard cables.
- Ensure that power cables are correctly installed and tightened to prevent overheating or burning of the power terminals/connectors.
- Properly shield all high-voltage cables.
EMC recommendations
- To minimize the risk of electromagnetic interference (EMC), it is advisable to ensure that the motor casing and controller cooler have a high-quality electrical connection (typically achieved through the structural frame). In case the structural frame is not electrically conductive, it is recommended to use a conductor (tinned litz wire) with a sufficient cross-section for electrical connection.
- Battery power cables should be run parallel to each other to minimize the loop area they collectively form.
- Motor power cables should be run parallel to each other to minimize the loop area they collectively form.
- It is recommended to attach motor cables as close as possible to the structural frame (or the cable connecting the controller cooler and the motor casing).
- For CAN communication wires (CANL and CANH), it is recommended to twist them along their entire length.
Typical wiring diagram
Incorrect wiring – risk of malfunction/damage to equipment
Typical wiring diagram for the particular controller is provided in the corresponding section of the documentation:
The integrator can modify the configuration of the diagram according to their needs and requirements. Creating the wiring diagram for the end application is the responsibility of the integrator. It may be also useful to check the controller powering and the motor sensors section of the documentation.
Configuring the motor controller for the application
Testing vehicle parameters – risk of personnel injury/damage to equipment
The OEM must thoroughly verify and validate all motor controller settings and functionalities before field use by an end user.
Throughout the parametrization process, it is crucial to exercise proper safety precautions during testing, as incorrect parameter values could compromise the safety-critical functions of the end application.
The OEM bears the responsibility to configure and set up the vehicle in accordance with applicable safety regulations.
Basic controller parametrization can be done with the help of motor identification chapter.
Commissioning the inverter in the prototype of a customer application may require complex parametrization and, if necessary, the development of a special application. For assistance in this case, please contact siliXcon customer support.
The controller supplied for OEM use may already have the final configuration loaded during the manufacturing process. However, it is recommended to perform a complete motor identification after integrating the controller into the end application.
The process of correctly configuring the controller in the end application is the responsibility of the integrator.