Learn how to start the network with RapidSetup.
- Warning
- Safety First
Kindly implement essential safety measures to safeguard both yourself and those around you. Feel free to reach out to us for tailored guidance on enhancing the security of your system.
- Precondition
- This guide assumes you have completed the all Setup
🔹 1. Connect your EtherCAT device to your PC
- Connect your EtherCAT device to your PC using an ethernet cable. One end should be connected to your device's EtherCAT IN port and the other end should be connected to your PC's NIC that was passed to INtime during the INtime installation guide.
🔹 2. Start the EtherCAT Network using RapidSetup
- In your RMP folder, open the RapidSetup tool.
RapidSetup will open to the MotionController RMP page. The Network State should be red UNINITIALIZED as shown in the image below:
Verify that the EtherCAT.xml file exists and it is found by RapidSetup.
If the EtherCAT.xml file is missing:
You should see a non-zero Node Count. (The node count should match the number of EtherCAT nodes available in your system/topology)
Click the GENERATE ENI FILE
button.
- Note
- Do not proceed with the guide until the EtherCAT.xml file has been created and found.
Click the START NETWORK
button.
After a few seconds, the Network State should change to green OPERATIONAL and the EtherCAT nodes on the network should populate in the project tree.
- If you do not get an OPERATIONAL state, try checking the following:
- Verify that the NIC (Network Interface Controller) is controlled by INtime. (See the Passing NIC control guide section_)
- Verify that the INtime Kernel "NodeA from the tray icon" is running.
- Hardware Nodes must be connected to the NIC which is controlled by INtime.
- The EtherCAT.xml file (your hardware-specific EtherCAT Topology) must be located in the
C:\RSI\X.X.XX
folder.
- Check that you are using one of the known compatible NIC hardware options. (See here)
- Close RapidSetup, Restart Node A, Open RapidSetup, and run
C:\RSI\X.X.XX\RMPNetwork.rta
. This will initialize the Network and display relevant error messages.
- Once an OPERATIONAL Network state is achieved and the connected nodes appear in the project tree.