RK3506J Embedded Linux Gateway Development | Obeita
Delivered project. The completed hardware and software met the customer’s agreed requirements in testing. Specifications for a new project must be agreed separately.
Obeita delivered an RK3506J embedded Linux gateway project for a mixed-I/O integration requirement. Work progressed from customer requirements and contract confirmation through hardware and software design, physical testing and delivery of the agreed gateway implementation.
Bringing different signal types into one gateway
The documented architecture brings serial instruments, current-loop inputs and discrete I/O into a Linux-based device. Obeita’s development work addressed the agreed hardware and application scope. The distinctive engineering task was to connect each physical channel with a meaningful software definition so collection, configuration and status could refer to the same signals.
The interface plan includes RS485, RS232, 4–20 mA inputs and digital inputs/outputs. A terminal label or channel count is only part of that definition. Current-loop supply, grounding, scaling and isolation determine sensor connection, while a digital output needs an electrical drive specification appropriate to its load. Before connecting a two-wire 4–20 mA transmitter in a new installation, check whether loop power is provided, how current is measured and how grounds are referenced; the current range alone does not define the wiring.
Linux application and management structure
The RK3506J platform description combines Cortex-A7 processing with a Cortex-M0 direction. The documented Linux application scope includes serial collection, protocol adaptation and web configuration. Device overview, network settings, communication parameters and system status represent different parts of the management workflow.
That workflow also needs defined authentication, logging and recovery behavior where required by the application. The technical value lies in connecting the interface model with gateway operation, rather than treating a configuration screen as a complete management implementation.
Storage and display boundaries
TF/SD and USB Host provide documented storage and peripheral paths. Local display remains optional and depends on matching a panel and driver to the chosen build. Headless and display-equipped designs can share parameter definitions while retaining separate mechanical and power requirements. Local logging also needs explicit capacity limits and filesystem-recovery rules when included in a new scope.
Documented architecture and configuration
This table records the project’s documented architecture and selection boundaries. Options, variants and design inputs remain qualified as shown; their inclusion here is not an independent guarantee that every option formed part of the delivered configuration.
| Item | Configuration |
|---|---|
| SoC | Rockchip RK3506J |
| RS485 / RS232 | 4 × RS485; 2 × RS232 |
| Analog inputs | 2 × 4–20 mA design channels |
| Digital I/O | 2 inputs; 3 outputs |
| Storage / USB | TF/SD; USB Host |
| Management direction | Web configuration; optional local display |
Delivery and customer-requirement testing
Obeita delivered the agreed RK3506J gateway hardware and software following physical testing. The tested functions met the customer’s requirements. This completion statement applies to the project’s agreed configuration; it does not establish an analog-accuracy figure, isolation rating, output-load capacity or delivery of the optional local display.
For another mixed-I/O gateway, the channel list should include wiring and electrical requirements alongside protocol and software fields. That avoids treating connector availability as sufficient evidence of sensor or actuator compatibility.
Discuss a similar RK3506J gateway
Send Obeita a channel-by-channel I/O list, current-loop wiring, serial protocols and target Linux runtime. Add any local-display and logging needs so hardware, application behavior and physical testing can be scoped together.