About sanX

  1. Overview In this article, a ctrlX CORE X3 as a Profinet Controller will be configured to connect with a ctrlX COREplus X3 that will be a Profinet Device. To be able to establish the connection between both, the CoDeSys Profinet library will be used in both devices. This configuration can also be done between two ctrlX CORE X3 or between two ctrlX COREplus X3. 2. Prerequisites ctrlX PLC app ctrlX WORKS PLC Engineering CoDeSys Fieldbus libraries 3. ctrlX CORE X3 (PN-Controller) configuration Note: Before starting with the configuration it is required to install the CoDeSys Fieldbus libraries. Please follow the steps shown here: Manual - CODESYS Fieldbus communication packages for ctrlX CORE. 1. Configure IP address: First, in the ctrlX CORE web interface, go to the “Settings” menu "Connectivity" Select the "eth1" connecion Select "IPv4"  Write the desired IP address. NOTE: To avoid conflicts with the web interface IP address (192.168.1.1) an IP address of the type 192.168.2.X will be written. In this case: 192.168.2.12. To configure the subnet mask, the /24 is added Save configuration 2. Configure PLC program A new project is created: First, select a ctrlX CORE template -> Provide a project name -> Press “Ok” A new project tree will be created. Add drivers to the project: Right click over “Device” and select “Add Device” 1. Extend the Profinet IO section and select Ethernet adapter -> 2. Press “Add Device” Now the Ethernet node should be visible in the Device tree Communicate to the ctrlX CORE Right click over "Device" -> "Communication settings" -> Enter ctrlX CORE IP Address -> Test connection by pressing over the "Run" button -> Press “Ok” Configure Ethernet Node First, double click over "Ethernet" -> 2. Press “Browse” -> 3. Select "eth1" where the previously configured IP address should be visible -> 4. Press “Ok” Add PN Controller Right click over “Ethernet” -> "Add device" Select PN-Controller in the Profinet IO Master section Press “Add device” Change priorities. Double click over "Profinet_communicationTask" -> Include a priority of 37 as a recommendation For the "Profinet_IOTask" the same steps are followed: Double click over "Profinet_IOTask" -> Include a priority of 30 as a recommendation Configure PN Controller Double click over "PN_Controller" -> Provide a PN-Controller station name (By default the name will be controller) -> Configure Slave IP Parameters Add Profinet device Right click over "PN_Controller" -> "Add Device" Expand the I/O folder -> CODESYS PLC -> Select CODESYS PROFINET Device "Add device" Configure PN-Device: Double click over CODESYS_Profinet_Device Give the station name configured in the PN Device Write the configured IP address in the PN Device (In this case, 192.168.2.13) NOTE: Notice that PN-Controller and PN-Device have the same IP 192.168.2.X type. Otherwise, it would not work. Add IO to read the sent values: Right click over "CODESYS_Profinet_Device" -> "Add device" Select "Output 8bit" because this will be the type of data sent from the PN-Controller to the PN-Device Press “Add device” NOTE: If the PN-Device is already configured and connected, there is other way to add the Profinet Device to the project. Login to the ctrlX CORE NOTE: You can also run the program, but it is not required to scan the profinet devices Once the PLC program has been transferred to the ctrlX CORE: Right click over “PN_Controller” -> "Scan Devices" In the case it has not scanned the devices -> "Scan Devices" The device should appear with its outputs Copy al the devices to object The PN-Device should appear in the device tree Troubleshooting: In the case, the PN-Controller is not able to scan the PN-Device, reset cold the PLC program in the PN-Device. Write little program to send data: Double click over "PLC_PRG" in the device tree Define the variables Write the program Map the program variable with the output: Double click over "Output_8Bit" Select the PNIO Module I/O Mapping tab Double click over the USINT type variable Look for the counter variable and select it Press “Ok” Once everything has been configured, the following window should appear: Before testing the PLC program, it is required to configure the PN-Device. Keep the window open because later it will be used to check the sent values. 4. ctrlX COREplus X3 (PN-Device) configuration 1. Configure IP address First, in the ctrlX CORE web interface, go to the “Settings" menu "Connectivity" Select the "eth1" connection Select "IPv4" Write the desired IP address. NOTE: To avoid conflicts with the web interface IP address (192.168.1.2) an IP address of the type 192.168.2.X will be written. In this case: 192.168.2.13 because the defined IP address by the PN-Controller was this one. To configure the subnet mask, the /24 is added Save configuration IMPORTANT: Write an IP address different to the one configured in the PN-Controller NOTE: This step is not mandatory because with the configuration performed in the PLC program, it will be enough. In this case it would create a dynamic IP address. 2. Configure PLC program A new project is created: First, select a ctrlX CORE template -> Provide a project name -> Press “Ok” A new project tree will be created. Add drivers to the project: Right click over “Device” and select “Add Device” 1. Extend the Profinet IO section and select "Ethernet" -> 2. Press “Add Device” Now the Ethernet node should be visible in the Device tree Communicate to the ctrlX CORE: Right click over "Device" -> "Communication settings" Enter ctrlX CORE IP Address Test connection by pressing the Run button Press “Ok” Configure Ethernet Node: First, double click over "Ethernet" Press “Browse” Select "eth1" where the previously configured IP address should be visible Press “Ok” NOTE: In the case, the IP address was not configured in the ctrlX CORE web interface, select also the eth1 option, but the IP address will be 0.0.0.0. Later, it is required to fill the following spaces: Write the PN-Device address defined in the PN-Controller (192.168.2.13) and write the subnet mask. When following these last steps in the eth1 connectivity overview, a dynamic IP address will be visible: Otherwise, this would be the overview: Add PN Device Right click over “Ethernet” -> "Add device" Select "CODESYS Profinet Device" Press "Add device" Change priorities. Double click over "Profinet_communicationTask" -> Include a priority of 37 as a recommendation For the "Profinet_IOTask" the same steps are followed: Double click over "Profinet_IOTask" -> Include a priority of 30 as a recommendation Configure PN Device: Double click over "CODESYS_Profinet_Device" Change to “Use project parameters” Write the previously defined station name for the PN_Device. In this case PN_Device-plus_X3 Add Output Right click over "CODESYS_Profinet_Device" -> "Add device" Select "Output 8bit" Press “Add device” NOTE: To be able to read the sent values from the PN-Controller to the PN Device it is required to write a line of code in the PLC_PRG as follows: The IB1 value is the output address of the output which can be found as follows:   5. Testing NOTE: To be able to use the PLC programs in both ctrlX COREs, it is required to be in “Running” mode From the ctrlX COREplus X3 side, the PLC program is transferred to ctrlX CORE. Press the “login” button and later the “Run” button From the ctrlX CORE X3 side, the PLC program is transferred by following the same step as for the ctrlX COREplus X3. Once executed: in the device tree the symbols shown in the following image should be visible. As seen in the previous figure, the output values are not updated and to be able to see them, it is required to perform the following steps: 1. Unlog and select the “Enabled 2 (always in bus cycle task)" option. Once done this, log again and check if the values are updated. As it can be seen, now the values are updated. In the case, they still do not appear, perform a reset origin and try again From the ctrlX CORE X3 side, perform the same steps and check how all the data is sent. 6. Related Links PROFINET - CONNECT CTRLX CORE X3 WITH INDRADRIVE PROFINET - READ PROFINET DEVICE APP VALUES FROM CTRLX PLC ENGINEERING PROFINET - CONNECT CTRLX COREPLUS X3 WITH INDRACONTROL XM21 PROFINET - CTRLX COREPLUS X3 WITH INDRACONTROL XM21 PROFINET - CONNECT CTRLX CORE X3 WITH CTRLX COREPLUS X3 WITH FIELDBUS LIBRARIES ... View more

1. Overview In this article, it will be shown how to connect two ctrlX CORE's using the PROFINET Device app and the CoDeSys fieldbus libaries. The ctrlX CORE X3 will act as PN-Controller and it will be configured using the PLC Engineering program. On the other hand, the ctrlX COREplus X3 will use the PROFINET Device App. Additionally, it is important to note that in the ctrlX COREplus X3, the Profinet port will be used, but in the ctrlX CORE X3, the Ethernet port (XF51) will be used. CoDeSys Fieldbus libraries The CoDeSys libraries have the biggest flexibility configuring the Profinet connection. It is possible to completely configure a Profinet Device and a Profinet Controller (Master). It is possible to define the PN-Controller parameters and also the PN-Device attached to it. Additionally, all exhanged data is available in the PLC program. In the case the user wants to read the PLC data in the Data Layer, it is also possible to define some global variables to read the values of interest. On the other hand, the configuration process is much longer and complicated due to the amount of aspects required to take into account. Additionally, it is required to have the PLC Engineering program. Otherwise, it is not possible to perform the configuration in the ctrlX CORE web interface. PROFINET Device app The PROFINET Device app has the advantage to be easily configurable. In a few clicks it is possible to configure the connection and have an idea of the connection state. Additionally, no external programs are required. With the ctrlX CORE web interface it is possible to configure the connection and to read the values from the Data Layer. On the contrary, with the PROFINET Device app it is not possible to configure a PN-Controller and it is limited to a PN-Device. As for establishing a Profinet connection, it is required to have a Profinet controller and a Profinet device, it is not possible to connect two ctrlX COREs using the app.  2. Prerequisites PLC Engineering program ctrlX PLC app PROFINET Device app CoDeSys Fieldbus libraries 3. ctrlX CORE X3 (PN-Controller) configuration Note: Before starting with the configuration it is required to install the CoDeSys Fieldbus libraries. Please follow the steps shown here: Manual - CODESYS Fieldbus communication packages for ctrlX CORE. In the case the user has access to the collaboration room, download the packages from this link. 1. Open ctrlX PLC Engineering program and create a new project Create a new project Select ctrlX CORE template Provide a name Press "Ok" to close the window 2. Communicate to the ctrlX CORE X3 Right click over "Device" Select "Communication settings" Enter the ctrlX CORE X3 IP address Press the "Run" button Press "Ok" to close the window 3. Add ethernet node Right click over "Device" Select "Add device" In the Profinet IO tree, select "Ethernet" and press "Add device" 4. Configure Ethernet node First it is required to define a static IP address in the ctrlX CORE web interface Go to the ctrlX CORE web interface and go to "Settings" Press "Connectivity" Select the "eth1" connection Go to the "IPv4" tab Enter the IP address we want to define. In this case 192.168.2.12 and to provide the subnet mask enter /24 which is the 255.255.255.0 subnet mask Press "Save" to keep the configuration Now, we return back to the ctrlX PLC Engineering program and perform the following steps: Double click over "Ethernet" In the general tab, press "Browse" Select the eth1 connection which should have the previously defined IP address Press "Ok" and the window will be closed 5. Add Profinet Controller Right click over "Ethernet" Select "Add Device" In the Profinet IO Master tree, select PN-Controller and press "Add device" 6. Change priorities Double click over "Profinet_communicationTask" -> Include a priority of 37 as a recommendation For the "Profinet_IOTask" the same steps are followed: Double click over "Profinet_IOTask" -> Include a priority of 30 as a recommendation 7. Add ctrlX COREplus X3 repository In "Tools" -> Select "Device Repository" Press "Install" button Select the .xml file to import it Now a new device should appear in the PLCs section 8. Add ctrlX CORE to the device tree Right click over "PN_Controller" Select "Add device" In the PLCs -> ctrlX CORE section, select "ctrX CORE" and press "Add device" 9. Configure ctrlX CORE node Right click over "producer" Select "Plug Device" Double click over "module_out"  With the window still open, double click over "consumer"  Doube click over "module_in" and close the window 10. Add input and output Right click over "producer" Select "Add device" In the Profinet IO -> Profinet IO Submodule -> consumer -> byte, select "byte_128_out", and press "Add device" Add input Without having closed the previus window, double click over "consumer". Otherwise, Right click over "consumer" -> "Add device" Select "byte_128_in" Press "Add device" 4. ctrlX COREplus X3 (PN-Device) configuration 1. First, the ctrlX CORE will be connected to the Engineering computer and the CtrlX Works program will be started. 2. Install PROFINET device app. Access Bosch Rexroth in the following link To perform this step, it is recommended to follow the instructions shown in the following article. The app is installed. In the ctrlX CORE web interface the “Settings” menu is clicked -> Access “Apps” -> Change to “Service mode” because otherwise it will not be possible to install the app, and the “Install from file” button is clicked. A new window will be opened where the previously downloaded file is selected. 3. Add PROFINET device: Access the PROFINET device app Check that the ctrlX CORE is in “Service” mode (Otherwise it will give an error as shown in the figure) “Add PROFINET device” Error that appears in the case the PROFINET device is added in “Operating” mode 4. Add PROFINET device 5. Configure PROFINET device: Click the pencil button Select template (this has to be chosen in function of sent data from the connected device to the ctrlX CORE) Save configuration 5. Testing 1. Run the PROFINET Device app  As the PLC program is still not running in the other ctrlX CORE, the state will be "Safe-OP" 2. Go to the ctrlX PLC Engineering program and login to transfer the PLC program to the ctrlX CORE Accept the message 3. Run the PLC program Check that both devices are connected by seeing the following symbol in the PLC program Check in the ctrlX COREplus X3 that the state has changed Note: If the user wants to test if the device sends data, it is possible to write a little program and later read the values in the Data Layer. All these procedures can be found in the other sections of this article. 6. Related Links PROFINET - CONNECT CTRLX CORE X3 WITH INDRADRIVE PROFINET - READ PROFINET DEVICE APP VALUES FROM CTRLX PLC ENGINEERING PROFINET - CONNECT CTRLX COREPLUS X3 WITH INDRACONTROL XM21 PROFINET - CTRLX CORE X3 WITH CTRLX COREPLUS X3 PROFINET - CTRLX COREPLUS X3 WITH INDRACONTROL XM21 ... View more

Overview In this article, it will be shown how to send data from the Raspberry Pi to the ctrlX CORE with the use of Node-RED. Random data will be generated in the Raspberry Pi with a “random” node and it will be named as “Temperature”. This data will be send with one communication protocol and read from the ctrlX CORE. In this tutorial, two ways will be shown: With MQTT broker or TCP. The Node-RED app will be used to simplify the communication and data acquisition between both devices, and in the case the user wants to make more complex uses, it is a very convenient platform. On the other hand, the Mosquitto MQTT Broker acts like an intermediate between devices that send and collect data. Devices that send data are called “Publishers” and devices that collect and read the data are called “Subscribers”. Subscribers can decide which data they want to read in the case there are many publishers. In this case the ctrlX CORE will act as a Subscriber and the Raspberry Pi as a Publisher. Finally, TCP (Transmission Control Protocol) is the worldwide most used protocol and establishes the communication between a client and a server. It is used for reliable and accurate communication purposes, but it is slower than other protocols such as MQTT. Basically, it breaks the message in packets to avoid resending the entire message again in case of transmission failure and in destination the packets are reassembled. In this case, the Raspberry Pi will act as client and the ctrlX CORE as server. Prerequisites Cedalo - Eclipse Mosquitto MQTT Broker App  ctrlX CORE - Node-RED App  Raspberry Pi - Node-RED  MQTT Broker connection The MQTT broker has the advantage to be faster and more reliable, but it is required to have a license to be able to install it in the ctrlX CORE and the configuration process is longer. Step 1: ctrlX CORE configuration 1. First, ctrlX CORE will be connected to the Engineering computer and the ctrlX WORKS program will be started.  2. Now, the Node-RED and the Mosquitto apps will be installed. Firstly, it is required to download both apps from the ctrlX Store. To perform these steps, it is recommended to follow the instructions shown in this article.  3. The apps are installed. In the ctrlX CORE web interface the “Settings” menu es clicked ->  Access “Apps” -> Change to “Service mode” because otherwise, it will not be possible to install the apps, and the “Install from file” button is clicked. A new window will be opened where the previously downloaded files are selected. Once installed, the apps will be visible as shown in the previous figure. 4. Mosquitto app configuration Access the ctrlX CORE homepage, select "Mosquitto" and press "Management Center"  In the new window, press over the "Clients" Create new clients. In this part, the clients that will be connected to the broker are defined. A MQTT client is any device that runs a MQTT library and connects to an MQTT broker over a network. In this case, the MQTT Broker is the Mosquitto MQTT Broker App installed in the ctrlX CORE. On the other hand, the clients will be the Raspberry Pi where the MQTT libraries will also be installed, and the ctrlX CORE where with Node-RED another client will be defined.  First, the Raspberry Pi client will be defined with the following configuration: Username: tutorialmqtt Password: tutorialmqtt Client ID: tutorialmqtt Text name: tutorialmqtt Once the client is defined, it is required to define a role. In this case, a “client” role will be used. Second, the Node-RED client that will later be defined in the ctrlX CORE is also defined: Username: nodered Password: nodered Client ID: nodered Text name: nodered As done for the Rapsberry Pi client, a "client" role is defined The clients window should look as follows: NOTE: In the Roles section it is possible to read the roles description. When the clients are connected, in the main section it will be possible to see if they are connected or not. Once everything is configured, an example will be shown. Step 2: Raspberry Pi configuration Once everything has been configured from the ctrlX CORE side, the Raspberry Pi needs to also be configured. 1. Install the Node-RED app in Raspberry Pi. To perform this step, it is possible to follow the guidelines of the Official Node-RED webpage  First, make sure that the system is updated sudo apt update && sudo apt upgrade To download and install the app, write the following command, and follow all the steps: bash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered) 2. Start Node-RED and configure MQTT. It is possible to open the Node-RED web interface from the icon shown in the following figure or from the applications Menu -> Programming -> Node-RED When the Node-RED app is started, a Node-RED interface is available. This interface is reachable with an IP-address. This IP-address is visible as shown in the next figure when opening the Node-RED app. Now it is necessary to add nodes to configure our system as desired. Theses nodes can be added from the left bar, and we can design a similar system as shown in the images below. In this case, an “inject” node will be added with the purpose to add values in an interval of time. On the other hand, a “debug” node will be added to be able to see the messages sent to the ctrlX CORE. Additionally, a “random” node is also added with the objective to generate a random value in a predefined range. Finally, a “mqtt out” node is used to send the messages to ctrlX CORE. All these nodes are connected as shown below. The inject node generates a signal every “X” second, and activates the random node. Each time the random node is activated, this node generates a random value and sends it to the “debug” and “mqtt out” nodes. The “debug” node gives the value in the debug tab on the right side of the interface and the “mqtt out” node sends the value to the MQTT broker.  To configure the random node, it is just needed to double click over it, and define the range of the random values. The default configuration is between 1 and 10 and once decided which interval we want, click over the “Done” button. To configure the inject node, double click over the node and the default configuration is “timestamp”. If we want to send messages in a time interval, we can select “interval” next to the “Repeat” icon, and select every how many seconds we want to send a message. Now it is required to configure the MQTT node: Double click over the mqtt node In the Server tab: “Add new mqtt-broker” Give a name to the Node Enter in the Server configuration In the server configuration window, it is needed to fill the following blank spaces: Server: Introduce the ctrlX CORE IP address Port: Usually, the default port is 1883 and it is needed to change to 8883 Protocol: Select MQTT V3.1.1 Client ID: Introduce the previously defined client ID in the Mosquitto app in the ctrlX CORE Security: Enter in the Menu shown in the figure below and enter the previously defined credentials in the Mosquitto app in ctrlX CORE. 6  Use TLS: Check the space and select the pencil to enter in the TLS configuration window. There, it is just required to uncheck “Verify server certificate” and click “Update” in the top right corner. Once everything has been configured, click on the right top corner on “Add”, and a similar window as shown below should appear. In “Topic” we just write the desired name and click over “Done”. The window will be closed, and in the node, a blue dot will be visible because it is required to deploy. For this purpose, just click over “Deploy” in the top right corner of the interface. Once deployed, the “Connected” status should be visible in the configured node. On the right bar, the debug menu is visible and from there it is possible to see all the sent values thanks to the use of the “Debug” node. Step 3: Connection check and final configuration 1. Now we can return back to ctrlX CORE, and check that there is a new client in the Cedalo Mosquitto App. 2. In the Topic Tree section, we can check the received values in ctrlX CORE. As the “Temperature” topic was given in the Raspberry Pi, this is the name seen in the Topic Tree. Once we have checked that all the values are being received by the broker, we can subscribe to it to get the values in the ctrlX CORE Node-RED app. 3. In the ctrlX CORE web interface, access the Node-Red App. A new window will be opened, and now a similar process as done in the Node-RED app in the Raspberry Pi will be followed:  Insert a “MQTT in” and “debug” nodes from the nodes bar. The result should be as follows. Configure the “MQTT in” node by double clicking over it and fill the blank spaces as shown in the next figure. Server: Click over the pencil and enter the values shown in the next figure. NOTE: In "Security" introduce the credentials defined for Node-RED for the ctrlX CORE and not the ones defined for the Raspberry Pi. Otherwise, they would not be able to connect at the same time because the broker only accepts one connection per client. On the other hand, activate the TLS configuration as performed in the Raspberry Pi configuration, and do not forget to uncheck “Verify server certificate” in the TLS configuration menu. Action: Subscribe to single topic Topic: “Temperature” as it is what was defined in the Raspberry Pi. It is very important to write here the same topic because otherwise it will not be possible to read the values coming from the Raspberry Pi. QoS: Defines the quality of the connection Output: We leave as it is per default Name: We can give any name 4. Once everything has been configured click over “Update” and “Deploy” to check if the node is able to subscribe to the MQTT broker. 5. By clicking over the debug menu, it will be possible to see the values sent from the Raspberry Pi. Note: As now there are two additional clients connected to the Broker, it we return back to the MQTT Broker App in the ctrlX CORE, the following will be visible: TCP connection The TCP configuration is much easier because everything is already integrated, and it is just needed to introduce the configuration parameters in both devices. Step 1: Raspberry Pi configuration As explained in the MQTT Broker case, it is required to install the Node-RED app. 1. Install the Node-RED app in Raspberry Pi. To perform this step, it is possible to follow the guidelines of the Official Node-RED webpage  To download and install the app, write the following command, and follow all the steps: bash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered) 2. Start Node-RED and configure TCP. It is possible to open the Node-RED web interface from the icon shown in the following figure or from the applications Mneu -> Programming -> Node-RED When the Node-RED app is started, a Node-RED interface is available. This interface is reachable with an IP-address. This IP-address is visible as shown in the next figure when opening the Node-RED app. In this case, an inject node will be added with the purpose to add values in an interval of time. On the other hand, a debug node will be added to be able to see the messages sent to the ctrlX CORE. Additionally, a random node is also added with the objective to generate a random value in a predefined range. Finally, a TCP out node is used to send the messages to ctrlX CORE. All these nodes are connected as shown below. Note: The TCP out node can be found in the Network section as shown in the following image. To configure the random node, it is just needed to double click over it and define the range of the random values. The default configuration is between 1 and 10 and once decided which interval we want, click over the “Done” button. To configure the inject node, double click over the node and the default configuration is “timestamp”. If we want to send messages in a time interval, we can select “interval” next to the “Repeat” icon and select every how many seconds we want to send a message. Once all the nodes have been added, TCP can be configured. For this purpose, double click over the “TCP out” node and it is just required to configure what is shown below. The port can be chosen as desired and in the “at host” space, it is just required to write the ctrlX CORE’s IP address. When finished, click over “Done”. Finally, in the TCP node, a blue dot will be visible because it is required to deploy. For this purpose, just click over “Deploy” in the top right corner of the interface and the Raspberry should connect to the ctrlX CORE. If everything is correct, the “Connected” status should be visible as shown below. Note: In the case TCP has still not been configured in the ctrlX CORE, it will not be able to connect and the “Disconnected” status will be shown. Step 2: ctrlX CORE configuration 1. First, ctrlX CORE will be connected to the Engineering computer and the ctrlX WORKS program will be started. 2. Now, the Node-RED will be installed. Firstly, it is required to download the app from the Bosch Rexroth store. To perform this step, it is recommended to follow the intructions shown in the following article. 3. The app is installed. In the ctrlX CORE web interface the “Settings” menu es clicked ->  Access “Apps” -> Change to “Service mode” because otherwise it will not be possible to install the app, and the “Install from file” button is clicked. A new window will be opened where the previously downloaded file is selected. Once installed, the app will be visible as shown in the previous figure. 4. Node-RED app access. Click over the Node-RED section as shown and click on “Flow editor”. 5. Insert the TCP in and debug nodes and connect them. 6. Configure the TCP in node as shown below. Include the port used in the Raspberry Pi and select how we want the data to be received. Close the window by clicking over “Done”. 7. Click over “Deploy” and check that there is one connection as shown below. 8. Check the received values in the right tab. ... View more

Introduction In this tutorial, it will be shown how to connect a ctrlX CORE with a Raspberry Pi using the Slave port (XF51). It will be necessary to make some configurations in both devices. Firstly, the ctrlX CORE will be configured and secondly the Raspberry Pi. Configuration 1. ctrlX CORE Configuration Firstly, it is required to connect the ctrlX CORE with the Engineering computer. For this purpose, it is just needed to follow the steps shown in the article: ctrlX CORE and Computer Connection.  Once successfully connected to the engineering computer, it is possible to configure the ctrlX CORE to be able to connect to the Raspberry Pi. 1. Go to "Settings"   2. Press "Connectivity" 3. Access the "eth1" interface 4. In the "IPv4" section, write the desired static IP address. For this article, the used IP address will be: 180.254.3.1/24. Important to add /24 because otherwise it will not be possible to assign this IP address.  Note: /24 provides the subnest mask 255.255.255.0. In the “IPv6”, “Routing” and “Security” sections it is not required to perform any change. 5. Activate IP forwarding 6. Once everything has been configured, click over "Save", as shown in the previous figure. After a few seconds, in the top of the configuration interface, a message with "Network changes applied successfully" will appear confirming that the configuration has been correctly saved. 7. Finally, it is important to check that for the eth0 interface, IP forwarding is also enabled. Otherwise, enable it, and click over "Save". 2. Raspberry Pi Configuration Note: For this process, it will be assumed that the Raspberry Pi has been completely set up. Additionally, it will be assumed that there is access to the desktop interface with a screen. Otherwise, it will be required to perform all the configuration per terminal commands. 1. Connect the Raspberry Pi with an ethernet cable through the slave port in ctrlX CORE (XF51 port). 2. Access to network settings. Right click over the symbol shown in the following image and click over "Wireless and Wired Network Settings". 3. In the Network Preferences window, the eth0 interface is selected and the following steps are followed to configure the static IP address: Uncheck “Automatically configure empty options” “Disable IPv6” can either be checked or not. “IPv4 Address”: An IP address that needs to have 180.254.3.X as a mandatory requirement, and the last number can be anyone that is not 1 (or the one configured in the ctrlX CORE) “IPv6 Address”: Nothing is needed to be entered In “Router” the IP address defined in the eth0 interface (in the CtrlX CORE) needs to be inserted. In this case: 180.254.3.1 “DNS Servers”: Nothing is needed to be added “DNS Search”: Nothing is required to add Once, the gaps have been filled, press "Apply", and close the window. NOTE: To finish the configuration, it is required to unplug and plug the Ethernet cable again to establish the connection with the defined static IP address. Testing 1. Raspberry Pi Testing In the case we would like to test the connection, we can open the terminal in the Raspberry Pi and write the following command: ping <IP address>. In the case the Raspberry Pi is correctly configured, there should appear messages like in the shown image. 2. Engineering computer connection test In the case we want to test the connection from the engineering computer we have to follow the following steps: 1. Open terminal with administrator rights 2. Write the command: route add 180.254.0.0 mask 255.255.0.0 192.168.1.1 After executing this command, the message “OK!” should appear. 3. Test connection with ctrlX CORE. The ping command is used: ping 192.168.1.1 If the Ping statistics show that 4 messages were send, 4 were received and 0 lost it means that the connection has been successful. 4. Test connection with Raspberry Pi. Here it is needed to enter the IPv4 address defined in the Raspberry Pi. The ping command is used: ping 180.254.3.10   ... View more