PART 01
EMC Series Bus Controller Introduction
The EMC series bus controller is an independent bus motion controller developed by Leadshine with independent intellectual property rights. It is designed based on the mainstream EtherCAT expansion bus and supports motion control of up to 64 axes. The main body supports backplane bus expansion, including different types of modules such as IO, AD/DA, and encoders, which is more convenient and efficient than general EtherCAT expansion. The EMC series controllers interact with PCs via network cables, and up to 254 EMC controllers can be networked to achieve distributed control.
Meanwhile, the EMC series also boasts powerful motion control capabilities. In addition to supporting various point-to-point motion planning modes such as T-type, S-type, and S plus, as well as common motion planning functions such as trajectory look-ahead, it also integrates a variety of industry control algorithms such as instruction caching, PSO spacing comparison, and two-dimensional pitch compensation, which are highly compatible with the common process requirements of industries such as 3C, semiconductor, laser, and dispensing.
The EMC series bus controllers are divided into the general-purpose point-to-point 3000 series and the high-end trajectory 5000 series. They are compatible with the original DMC series function interfaces, support multiple systems such as Windows/Linux/macOS, and are suitable for a wide variety of application scenarios.
PART 02
Introduction to Motion 4.2
01. Overview of Motion 4.2
Motion 4.2 software is a product debugging software developed by Leadshine based on the Windows platform. It supports debugging of control cards and EMC controllers, integrating product configuration, debugging, and status monitoring, which is helpful for functional familiarization and equipment debugging. The main interface of connecting an EMC-E5064 bus controller using Motion 4.2 is shown below:
02. Motion 4.2 Installation and Configuration Requirements
Motion 4.2 requires no installation; it can be used directly after decompression and is compatible with Windows XP and later 32-bit/64-bit Windows operating systems.
The minimum and recommended computer hardware requirements for Motion 4.2 are as follows:
After confirming the .NET 4.0 installation environment is complete, open the folder where the software is located and click the "Leadshine.DMC.IDE.exe" application icon to run it. The icon is shown below:
PART 03
Using EMC controller with Motion 4.2
01. Connection of EMC controller
(1) Preparation for connection
Before connecting, you need to connect the controller and PC with a network cable. Then, configure the PC's network port IP address and the controller's IP address to be on the same network segment (the controller's default IP address is 192.168.5.11), as shown in the image below:
After completing the above preparations, open Motion 4.2 normally. Motion 4.2 will automatically connect to the EMC controller using the IP address of the last connection (default is 192.168.5.11). After successfully connecting to the EMC series controller, the following interface will be displayed:
(2) Troubleshooting for connection failures
If the above EMC series controllers are not displayed, you need to check whether "Enable IP Connection" is selected, whether the PC's IP address matches the controller's IP address according to the above rules, and whether the Motion4.2 connection IP address matches the current controller IP address. The current Motion4.2 connection IP address can be confirmed through the connection settings interface, as shown in the following figure:
Once you have confirmed that everything is correct, you can click to refresh the list and reconnect.
(3) Motion4.2 connects multiple EMC controllers
Motion 4.2 supports simultaneous connection and debugging of multiple EMC controllers, effectively improving the efficiency of debugging multiple EMC bus controllers. By adding different connection numbers and IPs to connect multiple different EMC controllers, after configuring the connection IPs, there's no need to close the software. Simply click the refresh list (see image below), and Motion 4.2 will reconnect to the above IP list, as shown in the image below:
Multiple connections are shown in the following diagram:
(4) Modification of EMC controller IP
After successfully connecting to the EMC controller, right-click the corresponding EMC bus controller device, and in the function list that appears, click "Modify Communication Parameters," as shown in the following figure:
At this point, the corresponding IP settings interface will pop up. Fill in the desired IP address, click "Settings" and then "Confirm Restart Controller". Motion 4.2 will reconnect to the EMC using the newly modified IP address, as shown in the image below:
At this point, we are able to connect to the EMC bus controller normally using Motion 4.2.
02. Bus Configuration of EMC Series Bus Controllers
The EMC series controller is a control product designed based on the mainstream EtherCAT expansion bus, and also supports backplane bus expansion. Bus configuration is required before normal use. The specific configuration steps are as follows:
(1) Backplane bus configuration
When the controller is connected, Motion 4.2 will automatically scan the backplane bus, but will not download anything. At this time, the backplane bus will still be in an abnormal state, as shown in the figure below:
If there are no extended slave stations on the EtherCAT bus at this time, you can directly click "Download Configuration File" in the upper right corner. After resetting, the backplane bus will be in normal condition, as shown in the figure below:
At this point, the module resources extended by the backplane bus can operate normally.
(2) EtherCAT bus configuration
If both the backplane bus and the EtherCAT bus have extended slave stations, the EtherCAT bus can be configured directly after connecting to the controller, without the need for manual backplane bus configuration. The following is a detailed description of EtherCAT bus configuration.
First, right-click the EtherCAT bus master branch in the device tree, and then click "Scan Devices" in the displayed list to start an automatic scan, as shown in the image below:
The scan takes some time, which depends on the number and type of slave devices. After the scan is complete, the corresponding slave devices will be added to the EtherCAT bus master branch according to the actual connection order of the slave devices, and a prompt will appear to download the configuration file, as shown in the following figure:
At this point, both the backplane bus and EtherCAT bus configuration files have been successfully generated. Click "Yes" to download the configuration files. After the bus completes its reset, the EMC controller bus configuration is complete, and the corresponding bus status will display as normal, as shown in the following figure:
Motion 4.2 enables a fast and convenient bus configuration method, and can directly recognize mainstream EtherCAT slaves on the market, greatly reducing the time required for customers to configure extended networks during the debugging phase.
PART 04
EMC Series Bus Controller Error Diagnosis
01. Diagnosis of function execution exceptions
The EMC bus controller provides error returns and detailed error information for function execution. Error information can be found in the EMC controller user manual. Motion 4.2 also supports printing function execution status, as shown in the following figure:
When Motion 4.2 displays a function execution failure error code, clicking the corresponding error code will display the corresponding error information, as shown in the image below:
The EMC controller provides detailed function execution error codes and corresponding error code descriptions, improving the efficiency of troubleshooting customer function execution exceptions by more than 50%.
02
Bus status error diagnosis
The EMC series bus controllers are control products designed based on the mainstream EtherCAT bus. For EtherCAT bus status anomalies, the EMC series bus controllers also provide detailed error code classifications and information. On Motion 4.2, the bus status will be monitored and displayed in real time, as shown in the following figure:
When a bus error message appears, simply click on the corresponding error status to directly display the corresponding error information, as shown in the image below:
After a bus error occurs, we can find the specific problem node in the bus status information according to the bus error message, as shown in the following figure:
EtherCAT network anomalies are one of the most common problems with bus products. EMC controllers, when paired with Motion 4.2, provide bus diagnostic functions that can quickly and accurately identify problem nodes, greatly reducing downtime caused by bus network anomalies.
PART 05
Application scenarios
EMC series bus motion controllers can be applied to automation equipment in various industries. They are mainly targeted at industries such as 3C, basic electronics, special machine tools, and semiconductors.
That concludes our technical sharing on "EMC Series EtherCAT Bus Motion Controller (Part 2): Bus Configuration and Diagnosis". For more exciting content about EMC series bus controllers, please continue to follow the "Leica Control Technology" WeChat official account. Next time, we will share "EMC Series EtherCAT Bus Motion Controller (Part 3): IO Configuration and Zeroing".
