With the advent of Industry 4.0 era, IoT technology is changing our production and life style at an unprecedented speed. This article gives you a cross-platform industrial IoT gateway solution developed based on .NET 6.
The Industrial Internet of Things (IIoT) has become the link between the physical and digital worlds. And in this network, the Industrial IoT gateway is like an intelligent traffic cop, directing the busy data traffic between devices and cloud-based systems.
Next, this article describes how this solution works, what benefits it provides, and how it can be easily integrated into existing production environments.
What is an Industrial IoT Gateway?
An Industrial IoT Gateway (IIoT Gateway) is a hardware device or software program that acts as a bridge between local devices (e.g., PLCs, barcode scanners, robots, CNC machines, customized host computers, etc.) and cloud-based systems (e.g., IoT platforms, SCADA systems, MES systems, etc.).
All data flowing from the device to the cloud, and data sent from the cloud to the device, is transmitted through the IoT gateway, as shown in the following figure:
Projects
The IoTGateway IoT gateway solution is built in .NET 6 and supports cross-platform deployment.
With an intuitive visual configuration interface, you can easily connect to a wide range of devices and systems (e.g. PLCs, barcode scanners, CNC machines, serial devices, host computers, OPC Server, OPC UA Server, MQTT Server, etc.) for bi-directional data communication with ThingsBoard, IoTSharp, or your own IoT platforms (MES, SCADA).
Provides easy driver development interface, and also supports edge computing function to provide powerful support for data processing and analysis.
Project Features
southward
- Support Siemens PLC, Mitsubishi PLC, Modbus, Omron PLC, OPCUA, OPCDA, ABPLC, MT Machine Tools, Fanuc CNC
- Driver Support Extensions
- Supports device data writing
- Support for change uploads and timed archiving
northward
- thingsboard, iotsharp third-party platforms
- Telemetry, attribute upload
- RPC reverse control
service
- Built-in Mqtt service (1888,1888/mqtt), support websocker-mqtt, direct connection to your MES, SCADA and so on.
- Built-in OpcUA (://localhost:62541/Quickstarts/ReferenceServer), your device can also communicate with other devices through OPCUA
- Built-in ModbusSlave (analog device), port 503
Demonstration effect
- Websocker Refresh Free
- 3D Digital Twin Demo
- Support access to web-based configuration projects
Project Guide
protocol conversion
Easily connect to any of your devices and systems (e.g. PLC, Sweeper Gun, CNC, Database, Serial Devices, Supervisor, OPC Server, OPC UA Server, Mqtt Server, etc.) through visual configuration.
cloud connection
Built-in Mqtt server, OPCUA server, easy to interact with MES, SCADA data. Support IoTSharp, ThingsBoard and other private cloud platforms. Support RPC commands, reverse data writing.
hardware-enhanced
Cortex-A72, 1.5GHz ARM v8 64-bit CPU; emmc, 4G Full Netcom, Wi-Fi, 232, 485, HDMI, SD Card Expansion, Multi-Network Ports, Multi-USB, Bluetooth 5.0, ADC, Relay, Buzzer, IO; Current 9-36V DC Wide Voltage Input.
Enterprise Edition
vue front-end, time-series database, full-volume acquisition driver, rules engine, low-code reporting, web configuration, etc.
(computer) file
The documentation includes information on basic, advanced, and advanced, as well as hardware.
Gateway Selection
Hardware gateways are carriers of software, and open source gateway projects can run on the
- Any CPU architecture, e.g. Arm, Arm64, Armv6, X64, X86, LoongArch64 Most systems, e.g. win7-win11, ubuntu, debian, openwrt, etc.
- The linux system isn't limited to the hardware devices I provided.
However, the Open Source Gateway Project makes optimized adaptations for hardware gateways such as
- Performance monitoring: cpu, memory, disk and other host indicators monitoring
- Hardware interaction: analog acquisition, relay control, IO, etc.
- Virtual LAN: through vpn technology, build cloud LAN, realize off-site networking of multiple gateway devices, realize collaborative acquisition and control of device data; support gateway lower level non-networked device transmission, remote debugging, remote upgrade plc, etc.
- Virtual Remote Serial Port: With the ability of serial port pass-through, you can pass through the remote serial device to the developer's local machine; the developer can complete the development and debugging of the remote gateway serial device locally.
- Network, Firewall, Routing: Support scanning WiFi through the web, configure network interface to modify IP, etc.; configure firewall and routing rules through the web.
- Web Terminal: Access the terminal through the web, no need for hdmi and network cable anymore!
- Web file transfer: support uploading and downloading files to the gateway via web
Online Experience
1. Access address
Username: admin Password:
2、Home page
3. Acquisition Configuration
4. Gateway Configuration
Project Address
GitHub：/iioter/iotgateway
Gitee：/iioter/iotgateway
Document Address:
If you found this article helpful, why not support it with a like? Your support is what keeps me motivated to continue sharing my knowledge. Feel free to leave a comment if you have any questions or need further help.
You can also join WeChat[DotNet Technician] community to share ideas and grow with other tech-loving peers!Excellence is a habit, so feel free to leave a comment and learn!
