ReliaGATE 10-14
Revision History
| Revision | Date | Notes |
|---|---|---|
| 0.1 | 10/06/2023 | First draft |
Overview
The ReliaGATE 10-14 is an industrial, highly secure Edge Gateway that is easy to program: it supports classic and visual programming and comes with a rich and expandable IoT programming Framework. It is open and supports all major Cloud providers and services. It is suitable for immediate deployment in most countries, thanks to carrier certified LTE with 2G/3G backup connectivity, with options to expand the geographic coverage to a truly global scale.
The ReliaGATE 10-14 offers best in class Cybersecurity: it leads the market with IEC 62443-4-1/-4-2 and PSA Level 1 certification; it is also compliant with California SB-327 password law. Protection starts at the hardware level, with full support for TPM 2.0, Secure Boot and an always-on physical antitampering monitor/logger that is active even when the system is removed from power. For most demanding customers, special production-only images can be configured with full hardware hardening (interface disabling) to further reduce the attack surface.
Based on the NXP i.MX 8M Mini Cortex-A53 quad core processor, with up to 4GB of RAM, up to 32GB of eMMC and a user-accessible microSD slot, the ReliaGATE 10-14 is a low power gateway suitable for lightly rugged use cases: it supports a 9 to 30VDC power supply with transient protection, Display Port video output, two protected and isolated RS-232/RS-422/RS-485 serial ports, two noise and surge protected USB ports, six optoisolated digital and two isolated analog interfaces. The ReliaGATE 10-14 features a wide range of connectivity capabilities: it integrates a carrier certified LTE Cat 1/4 cellular modem with dual SIM support, Wi-Fi, Bluetooth 5/BLE, and two Gigabit Ethernet ports; an internal GNSS provides precise geolocation capabilities. Expansion options allow adding extra features with side modules, such as the ReliaWAN 10-12, a Lora Gateway unit, or the ReliaIO 10-12, which provides analog input and more DI/O ports.
The ReliaGATE 10-14 comes with Everyware Software Framework (ESF), a commercial, enterprise-ready edition of Eclipse Kura, the open source Java/OSGi middleware for IoT Edge Gateways. Distributed and supported by Eurotech, ESF supports ready-to-use field protocols (including Modbus, OPC-UA, S7), MQTT connectivity, web-based visual data flow programming and deep configuration. ESF is also integrated with Everyware Cloud (EC), Eurotech IoT Integration Platform (separately available here), enabling advanced diagnostics, provisioning, and full remote device access and management.
Hardware Description
Datasheet
Standard Kit Contents
Depending on the order code, you will receive the ReliaGATE 10-14 ready to be powered on with no additional hardware. If you ordered a DevKit, you will also receive a Power Supply for your region, antennas for WiFi and Cellular connectivity and a Ethernet Cat 5 cable. Visit the product page for info on ordering codes.
Custom Configuration
Eurotech configuration management service allows fine tuning the ReliaGATE 10-14 to meet and exceed your project requirements; Examples of personalized configuration include customer branding (with logo and custom colors) and can go to deep customization with a range of options for project specific requirements (such as frame grabbers, choice of internal components, etc.): call us for more information on configuration management options.
Set up Your Development Environment
Operating System
Your ReliaGATE 10-14 runs Eurotech Everyware Linux
Tools Installation
The ReliaGATE 10-14 is distributed with the latest version of ESF already installed and ready to start. In order to develop and deploy applications on ESF, you can follow the dedicated guides here.
If you need to build your native applications on this target hardware, please contact us to receive the latest toolchain.
Additional References
Detailed documentation on the features provided by the available services running on the ReliaGATE 10-14 can be found in the ESF official documentation, here.
Set up Your Hardware
Top Side Overview
| Ref | Description |
|---|---|
| 1 | Serial Ports COM 0 and COM 1 connector (availability depends on product variant) |
| 2 | Digital IN/OUT and Analog IN connector (availability depends on product variant) |
| 3 | Antenna connector for 2.4 GHz/ 5 GHz Wi-Fi/ Bluetooth (availability depends on product variant) |
| 4 | Main antenna connector for the Internal Cellular Modem (availability depends on product variant) |
| 5 | Antenna connector for the Internal GNSS (availability depends on product variant) |
| 6 | Diversity antenna connector for the Internal Cellular Modem (availability depends on product variant) |
Bottom Side Overview
| Ref | Description |
|---|---|
| 1 | Power IN connector |
| 2 | DisplayPort connector (availability depends on product variant) |
| 3 | USB 0 connector |
| 4 | USB 1 connector |
| 5 | Ethernet ETH0 connector (availability depends on product variant) |
| 6 | Ethernet ETH1 connector |
LED indicators Overview
| Ref | Description | Color |
|---|---|---|
| 1 | USER1 (General Purpose) | Green |
| 2 | USER2 (General Purpose) | Green |
| 3 | USER3 (General Purpose) | Orange |
| 4 | USER4 (General Purpose) | Orange |
| 5 | CELL. Internal Cellular Modem activity (availability depends on product variant) | Green |
| 6 | POWER | Blue |
Setup Your AWS Account
Refer to the online AWS documentation at Set up your AWS Account. Follow the steps outlined in the sections below to create your account and a user and get started:
Pay special attention to the Notes.
Create Resources in AWS IoT
Refer to the online AWS documentation at Create AWS IoT Resources.
Follow the steps outlined in these sections to provision resources for your device:
Pay special attention to the Notes.
Install the AWS CLI
To install the AWS CLI on your host machine, refer to the instructions at Installing the AWS CLI v2. Installing the CLI is needed to complete the instructions in this guide.
Once you have installed AWS CLI, configure it as per the instructions in this online guide. Set the appropriate values for Access key ID, Secret access key, and AWS Region. You can set Output format to "json" if you prefer.
Alternatively, you can use the AWS CloudShell to send the same AWS CLI commands directly from your browser.
AWS IoT Greengrass pre-installation
Dependind on your order code, AWS IoT Greengrass might be already installed and ready to use on the system. In order to check for its availability, you can run
on the Linux shell.
If AWS IoT Greengrass is already present on your device, the command will output something similar to the following, otherwise you can proceed installing Greengrass according to the next steps.
systemctl status greengrass
● greengrass.service - Greengrass Core
Loaded: loaded (/etc/systemd/system/greengrass.service; enabled; vendor preset: enabled)
Active: active (running)
Install AWS IoT Greengrass
Download the AWS IoT Greengrass Core Software
If Greengrass has not been included in the SD card image, you can download the latest greengrass core software as follows:
Install the AWS IoT Greengrass Core Software
Unzip the AWS IoT Greengrass Core software to a folder on your device. Replace GGCoreInstall with the folder that you want to use:
Verify the version of the AWS IoT Greengrass Core software:
You will see the Greengrass version displayed - similar to:
Provide Your Credentials
Run the following commands to provide the credentials to the AWS IoT Greengrass Core software.
export AWS_ACCESS_KEY_ID=<the access key id for your account>
export AWS_SECRET_ACCESS_KEY=<the secret access key for your account>
Run the Installer
Run the installer as shown below. Modify the values as per your region, install directory and thing name.
Use the --provision true option to have the installer set up the "thing" and required policies for you. If you prefer to configure Greengrass manually, see the online guide.
sudo -E java -Droot="/greengrass/v2" -Dlog.store=FILE \
-jar ./GGCoreInstall/lib/Greengrass.jar \
--aws-region us-west-2 \
--thing-name thing-name \
--tes-role-name GreengrassV2TokenExchangeRole \
--tes-role-alias-name GreengrassCoreTokenExchangeRoleAlias \
--component-default-user ggc_user:ggc_group \
--provision true \
--setup-system-service true \
--deploy-dev-tools true
If all goes well, you will see the following output on the device console:
Successfully configured Nucleus with provisioned resource details!
Configured Nucleus to deploy aws.greengrass.Cli component
Successfully set up Nucleus as a system service
The local development tools (specified by the --deploy-dev-tools option) take some time to deploy. The following command can be used to check the status of this deployment:
When the status is SUCCEEDED, run the following command to verify that the Greengrass CLI is installed and runs on your device. Replace /greengrass/v2 with the path to the base folder on your device as needed.
Create a Hello World Component
In Greengrass v2, components can be created on the edge device and uploaded to the cloud, or vice versa.
Create the Component on Your Edge Device
Follow the instructions online under the section To create a Hello World component to create, deploy, test, update and manage a simple component on your device.
Upload the Hello World Component
Follow the instructions online at Upload your component to upload your component to the cloud, where it can be deployed to other devices as needed.
Debugging
The ReliaGATE 10-14 default development configuration is meant to be ease access to the system and debugging.
- Ethernet Port 1 (7) is configured as DCHP Server with a IPv4 address of 172.16.0.1.
- Ethernet Port 2 (8) is configured as DHCP Client.
SSH protocol is enabled on standard port TCP 22 with, with guest user access. Password is the serial number of the unit, which you can find on the product label. To access the system, run:
You can use the eth_journalctl command to access the aggregated logs of the system:
Use these links for detailed information on log management and debugging.
Depending on the order code used for your ReliaGATE 10-14, the system might already be set up for production environments. Refer to the ESF Security introduction to know more about framework execution modalities.
Troubleshooting
For any issue you might face when working with ESF, feel free to contact the awesome Eclipse Kura community here. Chances are the issue you are facing has already been solved!
For detailed documentation, browse the ESF documentation.
If you need support for IoT Greengrass, here it's a link to the FAQs.
And finally, should you need even more support, feel free to open a ticket on our ticketing system, here.