Industrial IoT gateways. Customized around your equipment.
Build around your equipment and application: hardware, gateway software, integrated acquisition and control systems, and the cloud data path. Start with a standard platform or a project-specific design.
Choose the work your project needs. Existing product functions come first; adaptations are scoped against the selected hardware and firmware.
01
Hardware ODM
Develop the hardware configuration for your 4G/5G industrial router, edge gateway or LoRaWAN edge gateway.
Define interfaces, cellular region and bands, antennas, power and enclosure requirements. Review the sample design and test plan before repeat delivery.
Connect the data path. Define the control responsibility.
Cloud application development and ThingsBoard integration are project services. EDGELOR M2M manages users, device groups, online statistics and firmware; the separate remote tool provides authorized equipment access.
The heating terminal is a documented design example. Scenario images are visualizations; the browser demo uses sample data. Project results are established through agreed acceptance tests.
PROJECT DELIVERY
From requirements to repeatable delivery
01
Define the requirement
Agree interfaces, point lists, control responsibilities and the intended delivery scope.
Requirements + acceptance criteria
02
Configure the system
Select the host, communications, I/O, operator interface and cabinet arrangement.
Configuration + BOM + drawings
03
Validate the configuration
Exercise agreed interfaces and application behavior using the customer equipment or a suitable simulator.
Project test record + agreed exceptions
04
Prepare for repeat delivery
Tie the approved configuration, software and documents to a traceable build.
Configuration baseline + delivery documentation
PROJECT REVIEW
Send the essentials. Start the technical discussion.
A sketch, equipment list or existing specification is enough to start. Include the information below so we can assess the configuration and acceptance scope.
Points to read, permitted commands, reporting and behavior when the network returns.
Site & region
Installation country, cellular requirements, power, environment and enclosure constraints.
Quantity & delivery
Pilot quantity, repeat-order needs, project timing and required handover documents.
BEFORE THE PILOT
Questions worth settling early.
Can I start with a small batch?
Small-batch customization is part of the project approach. Quantity, engineering work, lead time and commercial terms are agreed after reviewing the requirement.
Does every gateway run Node-RED?
No. Node-RED is available on selected configurations. Confirm the exact model, firmware and required nodes in the matching documentation.
Can you adapt a device protocol?
Share the original protocol specification, request and response samples, and access to the device or a simulator. The device role and acceptance criteria need review before implementation.
How do we verify the pilot?
Check known readings, permitted commands and feedback, startup and network recovery. Agree configuration backups, wiring, software versions and acceptance records before repeat delivery.