How-to
Interface an EFC5610 drive with a ctrlX CORE over EtherCAT
Short answer
The EFC5610 runs from a ctrlX CORE over EtherCAT once E8.00 = 1 and H3.40 = EC are set and the drive is rebooted, the ESI is installed, and the xFC01 device is scanned and downloaded. Command it with the Rexroth Mode decimals (128 activate, 129 run forward) and a frequency word scaled at 0.01 Hz per count, so 50.00 Hz is 5000 counts.
On this page
- What the drive expects on the wire
- Prepare the Multi-Ethernet card on the drive
- Configure the EtherCAT master and install the ESI
- Rexroth Mode or CiA402 Velocity Mode
- Map the drive into the PLC program
- Worked example: commanding 50.00 Hz on the EFC5610
- Prove the link end to end
- When the drive will not run
- Questions asked
The EFC5610 answers a ctrlX CORE over EtherCAT with two integers: a control word and a frequency command scaled at 0.01 Hz per count, so 1234 commands 12.34 Hz and a 50.00 Hz target is 5000 counts. Everything else — the E8.00 and H3.40 card parameters, the ESI profile and the licensed ctrlX OS apps — only carries those words to the drive. Set the drive side first, then the master, then the PLC, and prove the link by writing the words directly before moving to library blocks.
What the drive expects on the wire #
A wrong control word or an unscaled frequency raises no network fault: the slave stays online and the drive stands still or creeps. Fix these two quantities before touching PLC logic.
| Control word (decimal) | Meaning |
|---|---|
| 128 | Activation |
| 129 | Run forward |
| 133 | Run reverse |
| 136 | Decelerate and stop |
| 160 | Clear error |
| 384 | Stop, freewheel |
The frequency command counts 0.01 Hz per count. Each word in the table contains 128 (129 = 128 + 1, 136 = 128 + 8), so treat the decimals as whole commands and take any per-bit meaning from the Multi-Ethernet card manual before combining bits yourself.
Prepare the Multi-Ethernet card on the drive #
Confirm the power and motor wiring against the EFC x610 operating instructions before energizing; these steps assume a safely wired drive.
- Fit the Multi-Ethernet module and its card holder; the base converter communicates on RS485 and has no EtherCAT port without the option.
- Connect IndraWorks Ds to the converter.
- Set E8.00 to 1 (Extension Card): run and frequency commands move from the keypad to the bus card.
- Set H3.40 to EC (EtherCAT).
- Reboot the drive; the protocol selection takes effect only after the restart.
With E8.00 = 1 the display no longer issues the run command or the frequency reference. Return the parameter to its original value before testing local operation again.
Configure the EtherCAT master and install the ESI #
- On the ctrlX CORE, confirm the ctrlX OS - EtherCAT Master app is installed and licensed.
- Add a new EtherCAT Master and select the physical EtherCAT port cabled to the drive.
- Open ctrlX I/O Engineering and create a new project.
- Download the device description files for the Multi-Ethernet card from the ctrlX OS store.
- Install the ESI under Tools -> Device Repository -> Install; Rexroth Mode and CiA402 Velocity Mode appear in the repository.
- In the device tree, right-click ethercatmaster and select scan for devices.
- Add the xFC01 device to the project.
- Click Download to transfer the fieldbus configuration to the ctrlX CORE.
After the download the drive's data is published in the ctrlX CORE Data Layer and available to PLC programs in real time. A scan that finds nothing points at the drive-side parameters, the cabling or the master port — not at the PLC program.
Rexroth Mode or CiA402 Velocity Mode #
| Criterion | Rexroth Mode | CiA402 Velocity Mode |
|---|---|---|
| Control word | Drive-specific decimals listed above | CiA 402 state-machine sequence |
| Parameter access | Simplified, drive-specific | CiA 402 objects |
| Code reuse across vendors | Low | High |
CiA 402 standardizes the drive state machine that its control word must walk through, which is what makes running CiA 402 CANopen drives from an S7-1500 through a gateway portable across vendors.
Pick Rexroth Mode when the EFC5610 is the only drive family on this controller: the decimal control word and the CXA_DriveUtil blocks are written against it. Pick CiA402 Velocity Mode only when one PLC program must command CiA 402 drives from several vendors. The profile fixes the process data layout, so choose it per drive before scanning; the rest of this article assumes Rexroth Mode.
Map the drive into the PLC program #
- Confirm the ctrlX OS - PLC app is installed and licensed.
- Start ctrlX PLC Engineering, create a project and select the real-time data sources.
- Select the EFC data from the EtherCAT master instance.
- Commission by writing the control word and frequency command variables directly; you own the sequencing and the status interpretation.
- Move production logic to the library blocks: add CXA_DriveUtil (FreqConv) and CXA_EthercatMaster through the Library Manager. Example_MB_ECATCoEFreqConv is the reference project, mapped to visualization elements for an interface that runs from a computer or on a ctrlX HMI.
Once mapped, the drive is ordinary cyclic I/O to the program — the same exchange as controlling a PROFINET servo drive with cyclic telegram data, where the telegram words are all the logic sees.
Worked example: commanding 50.00 Hz on the EFC5610 #
Inputs: a target output frequency of 50.00 Hz from the process setpoint, and the scale of 0.01 Hz per count from the frequency command definition in the EFC x610 Multi-Ethernet documentation, where 1234 commands 12.34 Hz.
Rule in words: the written count equals the target frequency divided by the value of one count.
Arithmetic:
- 50.00 Hz ÷ 0.01 Hz per count = 5000 counts
- Check: 5000 counts × 0.01 Hz per count = 50.00 Hz
- Failure mode: writing 50 gives 50 × 0.01 Hz = 0.50 Hz
Result: 5000 counts.
Decision: write hertz × 100 into the frequency command integer — 5000 for a 50.00 Hz setpoint, 1234 when you want the documented check value. Any raw write under 100 counts commands less than 1.00 Hz, and a drive creeping at exactly one hundredth of the setpoint means the integer went out unscaled.
Prove the link end to end #
- xFC01 is listed under the master and reports online after the download.
- The EFC data points appear in the ctrlX CORE Data Layer.
- Drive stopped, write 1234 and confirm the frequency reference follows the documented scale.
- Write 160 to clear any latched error, 128 to activate, set the frequency, then 129 to run forward (133 for reverse); the output ramps toward the reference.
- Write 136 and confirm a decelerated stop; run again and write 384 to confirm a freewheel stop.
Confirm the exact transition order in the Multi-Ethernet card manual before automating the sequence.
When the drive will not run #
| Symptom | Likely cause | Fix |
|---|---|---|
| Scan finds no device | H3.40 not EC, no reboot after the change, wrong master port | Correct the parameters and port, reboot, rescan |
| Slave online, run word ignored | E8.00 not 1, or an error is latched | Set E8.00 = 1; write 160 first |
| Drive runs at a fraction of the setpoint | Frequency written without the × 100 scale | Write hertz × 100 |
| Master or PLC app will not start | App missing or not licensed | Install and license the ctrlX OS apps |
| No EFC data in the Data Layer | Fieldbus configuration not downloaded | Download in ctrlX I/O Engineering |
| Control word behaves oddly | CiA402 profile selected but Rexroth decimals written | Re-select the profile and download again |
Questions asked
Why does the drive creep at 0.50 Hz when I command 50?
The frequency command counts 0.01 Hz each, so a raw write of 50 commands 0.50 Hz and anything below 100 counts is under 1.00 Hz. Multiply hertz by 100 before writing: 50.00 Hz × 100 = 5000 counts. Verify the path with the documented pair, 1234 for 12.34 Hz, before blaming the network, because a scale error raises no fault.
Rexroth Mode or CiA402 Velocity Mode: which profile do I install?
Choose by what else the controller has to command, as covered in the profile section above: the 128/129/133/136/160/384 control word and the CXA_DriveUtil function blocks are written against Rexroth Mode, while CiA402 Velocity Mode follows the standard CiA 402 state machine and lets one PLC program command drives from several vendors. The profile fixes the process data layout, so select it per drive before scanning.
The EtherCAT scan finds no device. What do I check first?
Check the drive side before the engineering tool: H3.40 must read EC and the drive must have been rebooted after the change, E8.00 must be 1, and the master must sit on the physical EtherCAT port that is actually cabled to the converter. The ESI must already be installed in the device repository, because the scan has to match the found slave to a profile.
The slave is online but the drive ignores my run command. Why?
Two usual causes: E8.00 is not 1, so the keypad still owns the run command and frequency reference, or an error is latched. Send 160 to clear the error, then 128 to activate, then 129. While E8.00 = 1 the display no longer issues commands, so return that parameter before testing local operation.
Do both ctrlX OS apps need licenses to commission?
Yes, each where its step runs: the ctrlX OS - EtherCAT Master app must be installed and licensed before you add the master and download the fieldbus configuration, and the ctrlX OS - PLC app must be installed and licensed before the PLC project goes online. Drive-side parameter changes in IndraWorks Ds need neither.
What is the difference between control word 136 and 384?
136 decelerates the motor on the drive's ramp to a standstill; 384 stops by freewheeling, dropping the output and letting the load coast. Use 136 for normal process stops and reserve 384 for cases where coasting is acceptable, never as the routine stop for a load that must stop predictably.