Agricultural IoT Edge Gateway ODM Case Study: RK3568-Based Multi-Protocol Gateway Solution

Project Overview

Agricultural IoT systems often involve a wide range of field devices deployed across greenhouses, farmland, irrigation stations, and agricultural equipment facilities. These devices may come from different manufacturers and use various communication interfaces and protocols, making centralized data collection and management challenging.

To address these challenges, the project required a customized Agricultural IoT Edge Gateway capable of connecting heterogeneous field devices, converting communication protocols, aggregating operational data, and transmitting information to a centralized cloud platform.

KICKPI developed an embedded gateway solution based on the Rockchip RK3568 platform, with hardware and software customization capabilities designed around the customer’s communication, networking, and remote management requirements.

The solution was designed to support multiple industrial communication interfaces, flexible network connectivity, local data buffering, and remote device maintenance.

2. Product Definition and Key Requirements

Product Name: Agricultural IoT Edge Gateway

Core Platform: Rockchip RK3568

The gateway serves as an intermediate communication and processing unit between agricultural field devices and the cloud management platform.

Key Functional Requirements

Multi-Protocol Device Connectivity

• RS485 interfaces for connecting industrial sensors, meters, and controllers.
• Modbus RTU support for communication with agricultural equipment.
• CAN bus connectivity for compatible field devices.
• Expandable protocol adaptation for customer-specific devices.

Protocol Conversion and Data Processing

• Convert field device data into MQTT, HTTP, or customer-defined communication formats.
• Aggregate data from multiple connected devices.
• Normalize device data into a unified data model.
• Support configurable data collection and reporting intervals.

Flexible Network Connectivity

• Multiple Ethernet ports according to the target network topology.
• Optional Wi-Fi and 4G connectivity.
• Configurable WAN/LAN networking.
• Support for static IP, DHCP, VLAN, NAT, and firewall functions when required by the system design.

Local Data Management and Remote Maintenance

• Local data buffering during network interruptions.
• Automatic data retransmission after network recovery.
• Device status monitoring and communication diagnostics.
• System logs and fault reporting.
• Remote configuration and firmware updates.

3. Hardware Architecture Design

The RK3568 platform provides the computing foundation for protocol processing, data aggregation, and network communication.

The hardware architecture integrates field communication interfaces, processing resources, and network connectivity into a unified embedded gateway.

3.1 Main Hardware Components

Hardware Component	Function
RK3568 Processor	Main computing and protocol processing platform
DDR Memory	Runtime memory for Linux and gateway applications
eMMC Storage	Operating system, applications, and local data storage
RS485 Interface	Communication with industrial sensors and controllers
CAN Interface	Communication with CAN-compatible field devices
Ethernet	Wired network connectivity
Wi-Fi	Optional wireless communication
4G Module	Optional cellular network connectivity
Protection Circuits	Electrical protection and interface reliability

3.2 Multi-Ethernet Architecture Considerations

Multi-Ethernet connectivity is an important requirement for agricultural and industrial IoT gateways.

However, adding multiple RJ45 connectors does not automatically provide independent network interfaces. The actual hardware architecture must consider the processor’s available MAC resources, external PHY devices, Ethernet switch chips, and network isolation requirements.

During ODM development, the following design parameters need to be confirmed:

• Whether each Ethernet port requires an independent MAC interface.
• Whether ports share a hardware Ethernet switch.
• Whether WAN and LAN interfaces require hardware or software isolation.
• Whether VLAN configuration and independent IP subnets are required.
• Whether DHCP, static IP, NAT, firewall, and port mirroring are needed.
• Ethernet port speed and network topology requirements.

The final hardware configuration is determined by the customer’s application, networking architecture, and product cost targets.

4. Embedded Linux Software Development

Hardware integration is only one part of an agricultural IoT gateway. The software architecture must also ensure reliable communication between different field devices and the cloud platform.

KICKPI’s embedded software development focuses on protocol adaptation, data processing, network management, and remote maintenance.

4.1 Multi-Protocol Driver Integration

Different device manufacturers may implement communication protocols with different register addresses, byte orders, data types, measurement units, and communication timing requirements.

To address these differences, the gateway software needs a configurable protocol adaptation framework.

Key development tasks include:

• Device model and protocol configuration management.
• Modbus RTU register mapping and data parsing.
• Data type, byte order, and measurement unit conversion.
• Communication timeout and retry mechanisms.
• Exception code handling and offline device detection.
• Independent polling tasks to prevent one faulty device from blocking other communication processes.
• Protocol adaptation for additional customer-specific devices.

The system also needs to verify polling intervals and bus utilization when multiple devices operate on the same communication bus.

4.2 Unified Data Model and Cloud Communication

After collecting data from field devices, the gateway converts the information into a unified data structure.

The software architecture supports:

• Device identification and data mapping.
• Standardized data fields and measurement units.
• Configurable data reporting intervals.
• MQTT or HTTP-based communication.
• Customer-defined cloud API integration.
• Data buffering and retransmission mechanisms.

This architecture helps the cloud platform manage devices from different manufacturers through a consistent data interface.

4.3 Network Management and Remote Maintenance

For agricultural installations distributed across multiple locations, remote maintenance is essential.

The gateway can be configured to support:

• Ethernet, Wi-Fi, and 4G network management.
• Network connection status monitoring.
• Local system logs and fault records.
• Remote configuration.
• Firmware update mechanisms.
• Upgrade failure handling and recovery strategies.

These functions help reduce the need for on-site maintenance and simplify the management of distributed agricultural IoT devices.

5. Key ODM Development Challenges

Challenge 1: Multi-Protocol Integration and Unified Data Management

One of the main challenges is integrating field devices from different manufacturers into a unified communication system.

Even when devices use the same protocol, their register definitions, data formats, and communication parameters may differ.

The ODM development process must therefore go beyond basic protocol connectivity.

It requires a configurable device management framework that supports different device profiles, register mappings, communication parameters, and data conversion rules.

Communication exceptions must also be handled independently to prevent an offline or malfunctioning device from affecting the entire gateway.

Challenge 2: Multi-Ethernet Port and Network Topology Design

Agricultural IoT applications may require a network architecture such as 1 WAN + 3 LAN, allowing different equipment groups to connect through separate network interfaces.

The hardware and software design must work together to meet these requirements.

Key considerations include:

• MAC, PHY, and Ethernet switch chip selection.
• Independent network interfaces and IP subnet configuration.
• WAN/LAN separation and network isolation.
• VLAN and routing configuration.
• DHCP, NAT, and firewall implementation.
• Network reliability and recovery mechanisms.

The final design must be validated against the customer’s actual network topology rather than relying solely on the number of physical Ethernet connectors.

Challenge 3: Reliable Data Buffering and Network Recovery

Agricultural equipment is often deployed in outdoor or remote locations where network connectivity may be unstable.

The gateway must maintain local data collection during network interruptions and retransmit buffered information after the connection is restored.

The software design needs to consider:

• Local storage capacity.
• Data retention periods.
• Data timestamp management.
• Buffer overflow handling.
• Data retransmission order.
• Duplicate data prevention.
• Recovery behavior after unexpected power loss.

These requirements help maintain data continuity between field devices and the cloud platform.

Challenge 4: Long-Term System Stability and Remote Upgrades

An agricultural IoT gateway may operate continuously in unattended environments.

Therefore, system stability, service monitoring, and firmware recovery are important parts of the ODM development process.

The system should support service status monitoring, abnormal process recovery, system logs, remote firmware updates, and upgrade failure handling according to the customer’s requirements.

6. System Architecture

The overall system architecture consists of four functional layers:

Layer 1: Field Device Connectivity

RS485 sensors, Modbus RTU devices, CAN devices, and other agricultural equipment.

Layer 2: Interface Protection and Hardware Processing

Electrical protection circuits and the RK3568-based embedded hardware platform.

Layer 3: Embedded Linux and Gateway Applications

Protocol conversion, data aggregation, local caching, device management, and network configuration.

Layer 4: Cloud Platform Connectivity

Ethernet, Wi-Fi, or 4G communication to the centralized agricultural IoT management platform.

This architecture allows the gateway to serve as a communication bridge between heterogeneous agricultural devices and cloud-based management systems.

7. Project Acceptance and Validation

The customized gateway should be validated against agreed hardware and software specifications before mass production.

Test Item	Acceptance Criteria
Protocol Connectivity	All agreed devices and communication protocols complete integration testing.
Network Interfaces	Port quantity, speed, IP subnets, and isolation policies meet design specifications.
Data Forwarding	Data fields, formats, and reporting intervals comply with the interface documentation.
Offline Data Buffering	Data is stored for the agreed retention period and retransmitted after network recovery.
System Stability	No unexpected reboot or critical service termination during the agreed test period.
Remote Firmware Update	Successful upgrades, failure handling, and rollback behavior meet agreed requirements.
Fault Diagnostics	Device status, communication exceptions, and system logs can be queried.

Acceptance criteria should be defined during the requirement analysis stage to ensure that the final product meets the customer’s actual deployment requirements.

8. KICKPI Agricultural IoT Gateway ODM Capabilities

KICKPI provides embedded hardware and software customization services for industrial and IoT applications.

For agricultural IoT gateway projects, our engineering team can support:

• RK3568-based embedded motherboard customization.
• RS485, CAN, Ethernet, Wi-Fi, and 4G interface integration.
• Multi-Ethernet hardware architecture design.
• Embedded Linux BSP and driver development.
• Modbus RTU and customer-specific protocol integration.
• MQTT, HTTP, and cloud platform communication.
• Local data storage and offline retransmission.
• Remote device management and firmware upgrades.
• Prototype development, functional testing, and mass production support.

Our ODM development workflow covers the complete product development process:

Requirement Analysis → System Design → Hardware Design → Software Development → Prototype Testing → Mass Production Delivery

9. Develop Your Custom Agricultural IoT Gateway with KICKPI

Looking for an embedded hardware platform for agricultural monitoring, irrigation control, greenhouse automation, or industrial IoT connectivity?

KICKPI can help customize an RK3568-based gateway or develop a new embedded hardware solution according to your interface, communication, networking, and software requirements.

Whether your project requires RS485 Modbus RTU, CAN bus, multiple Ethernet ports, 4G connectivity, or customized Linux software, our team can work with you from initial requirements to prototype development and production.

Contact KICKPI to discuss your Agricultural IoT Gateway ODM project.