Rubix Compute: Overview
Hardware Overview
Power Supply Requirements
Power Supply Wiring
The Nube-iO Rubix Compute Gateway Controller is powered by a 24v AC or DC power supply on the `24 AC/DC POWER` terminals as shown below.
Wiring Diagram:
Mounting
The Rubix Compute 5 is designed to be mounted on electrical DIN rail. It can be mounted vertically or horizontally. The controller should always be
mounted in a location such that it will not experience very high or low temperatures, liquids
or high humidity.
Controller Connection and Discovery
In order to connect to and interact with a Rubix Compute controller it must be connected to a network via Ethernet cable. The best way to connect to the Rubix Compute is via a router. Alternatively, the Rubix Compute Controller can be connected directly to a PC via ethernet (Note: you will be unable to download / update apps if you connect directly to a laptop).
To add a Nube-iO Rubix Compute Gateway Controller to a network, an ethernet cable must be connected to one of the Ethernet ports on the controller; generally this will be using the ETH-2 port. The other end of the Ethernet cable should be connected (directly or indirectly) to the Network Router.
Connecting via a router
When connecting to the Rubix Compute controller via a network router, ethernet port ETH-2 should be used (at default network settings). Once connected via an ethernet cable, find the automatically assigned IP Address by using the router’s admin user interface; or by running an IP/Port Scanning Software (Port Scanner - Wikipedia).
When you think you have found the correct IP Address, try running a PING check on that IP Address; If successful, unplug the Rubix Compute controller, and re-run a PING check to see that the PING check now fails. Then reconnect your Rubix Compute controller.
Direct connection to PC
When connecting a Rubix Compute controller directly to a PC via an ethernet cable, ethernet port ETH-1 should be used (at default network settings). Ensure that the PC has self-assigned a static IP Address in the same subnet range as the Rubix Compute (default 192.168.15.xxx)
Once connected, and the PC IP Address is configured, try running a PING check on the Rubix Compute IP Address (default: 192.168.15.10).
This method is not recommended as it is quite difficult to provide the Rubix Compute Controller an internet connection when connected directly to a PC. It is always recommended to connect via a network router.
Note: There cannot be identical IP addresses on the same network
Controller Access and Login
The Rubix Compute's IP is configured via the Rubix Platform's browser based user interface. It can be accessed on any supported web browser (Chrome, Firefox, Safari, Internet Explorer, ...) by entering the IP Address, and Port Number [1414] in the browser's URL address bar. This will take you to the Rubix Platform login page.
The URL Address should take the following form:
<IP Address> : <Port Number>
(For example 192.168.15.10:1414)
Enter the following credentials:
Username: admin
Password: N00BWires
If successful, you will be taken to the controller's platform.
Changing the Rubix Compute's IP address
- Click into Service (Step 1) --> Networking Tab (Step 2).
- Enter the IP that you want to change the device to and click 'save' (Step 3).
- To set the Rubix Compute to DHCP, toggle the switch over to 'DHCP' and click 'save' (Step 4).
- Click into the 'Host Info' tab (Step 5) and toggle the 'reboot' switch for the changes to take place (Step 6)
Lora Device Settings
Use the following ports to set up and add the LoRa devices onto the Rubix Platform:
| Device Type | LoRa Port selection on Rubix Platform |
| Wireless sensors - Droplets & Micro Edge | /data/socat/loRa1 |
| Rubix iO-16 in Wireless Mode | /data/socat/serialBridge1 |
| Rubix iO-16 in 485 Mode | /dev/ttyAMA0 |
Modbus RS485 Network (Wired Network)
The Rubix Compute 5 has 2 x 485 ports which allows the device to act as a Modbus Server. The connector is terminated and installed as shown below.
Use the following ports when setting up Modbus devices on the Rubix Platform:
| Device Type | Port selection on Rubix Platform |
| 485-1 | /dev/ttyUSB0 or /dev/ttyRS485-1 |
| 485-2 | /dev/ttyAMA0 or /dev/ttyRS485-2 |
When networking multiple Modbus devices (such as a Rubix iO16 on a RS485 network, each device can be connected in a `Daisy Chain`. Controllers that are connected between 2 other controllers will have 2 wires (one from the previous controller and one from the next controller) in the same terminal. Ensure A/+ and B/- wires are kept consistent for all controllers on the network.
Note: Modbus settings on the gateway controller must match those set on the connected IO Modules. All devices on a Modbus network must have the same Modbus network settings.RS485 Network Wiring
When wiring an RS485 network a single shielded twisted pair (STP) cable should be used. The twisted pair cable cancels out interference and ensures that the 2 conductors are at the same lengths. Having a ground shield on the twisted pair cable further provides protection to interference on the RS485 network.
Related Articles
Rubix CE: Overview
Rubix Computer Edition (CE - Overview) Rubix Platform CE is Nube iO's new desktop software designed for offline programming and product management. Built to be fast, lightweight and portable, it allows users and technicians to configure and modify ...Rubix Compute: Installation and User Manual
Please download the document attached below.Rubix Compute: Datasheet
Please download the document attached below.Connecting to the Rubix Compute
Connecting to the Rubix Compute Controller is easy! If you have a Rubix Compute 5 (RC5) and you are plugging straight into your laptop, plug your ethernet cable into the first port of the controller and set your laptop to the .15 subnet (for example: ...Rubix Compute: Network Connection and Discovery
This article explains the best practices in how to connect Rubix Compute device to a network, and how to locate Rubix Compute device on the network. Network Connection and Discovery In order to connect to and interact with a Rubix Compute controller ...