Six real deployments. Three industry groups. The connectivity problems were different at every site — but the pattern that emerged was consistent: the right router specification, matched precisely to the actual field requirements, changed the project outcome completely.
Written by E-Lins Engineering Team
Why Real Deployment Stories Matter More Than Spec Sheets
As part of our applications engineering team, I spend a significant amount of time working with customers before they order — going through site conditions, power systems, legacy field devices, carrier coverage maps, and VPN architectures. What I’ve learned from that process is that the specification questions that actually matter in the field are rarely the ones that appear most prominently in a product comparison table. Throughput ceiling almost never determines a deployment outcome. Temperature range, power input flexibility, serial port configuration, and dual SIM failover logic almost always do.
The six cases in this article are real deployments that we supported directly, across three industry groups: energy and utilities, smart manufacturing, and transportation. In each case I’ve documented the specific problem the customer was trying to solve, the specification requirements that emerged from that problem, the E-Lins industrial IoT router that was selected and why, and the measurable outcome after deployment. My goal is not to present a collection of success stories — it is to give engineers and procurement managers a realistic picture of how the specification decision was made, so they can apply the same thinking to their own projects.
How to read this article: each case is self-contained — you can jump directly to the industry group most relevant to your project using the article navigation above. The product reference table at the end maps each case to the E-Lins model used and the two or three specification criteria that drove the selection. If you are early in a project and not yet sure which industry group your application fits, the lessons section at the end synthesises the patterns that appear consistently across all six cases.
Industry Group 01 Energy & Utilities
Case 1 — Water Treatment Authority, 32 Remote Pump Stations, Southeast Asia
H750 — deployed across 32 pump station sites
A regional water authority was expanding its SCADA monitoring network to cover 32 remote pump stations distributed across a catchment area spanning approximately 280 km. The previous monitoring approach relied on licensed radio telemetry — a technology the authority was decommissioning due to the cost and administrative overhead of spectrum licenses, and the growing maintenance burden on aging radio equipment. Their replacement brief was cellular SCADA connectivity, reporting pump status, flow rates, and tank levels to a central control room over a secure VPN.
The site survey produced requirements that significantly narrowed the field of eligible devices. Fourteen of the 32 stations were solar-powered with 12V lead-acid battery banks, creating a DC supply that varied from 10.3V at battery low to 14.6V at full solar charge — with transient dips to 9.8V during the occasional generator assist startup. Power supply was not stable enough for any router with a minimum input above 9V to be trusted. All 32 stations had existing RTUs communicating via RS485 Modbus RTU at 9600 baud, 8 data bits, no parity — replacing those RTUs was not in scope. And a cybersecurity audit the previous year had specified that all management access to field devices must authenticate against the authority’s central RADIUS server, with full accounting of all access events.
The RADIUS authentication 4G industrial router for water utility SCADA compliance requirement was the most specific and hardest to meet — it ruled out several competitive devices whose management interfaces only supported local username/password authentication. The E-Lins H750 dual SIM 4G industrial router was selected: dual SIM for the eight stations where two carriers had coverage, RS485 serial for RTU integration, 5–40V DC input for the solar power systems, RADIUS and TACACS+ authentication for the compliance requirement, and the zone-based object firewall for network segmentation between the SCADA polling path and the management interface.
Deployment Outcome — Water Authority, Southeast Asia
Configuration of RADIUS authentication across 32 devices was completed in a single commissioning week. The authority’s IT security team verified the RADIUS accounting logs — every management login recorded with timestamp, user identity, and session duration — as part of their compliance handover checklist. In the 18 months following deployment, zero voltage-related router restarts were recorded across the 14 solar-powered sites. The RS485 Modbus RTU integration was configured in transparent DTU mode and worked on first startup at all 32 stations without requiring any modification to the legacy RTU firmware or hardware.
The authority’s network operations manager summarised the project: “The two things that made the difference were the security compliance checkbox and the power supply flexibility. Everything else we could have worked around. Those two we couldn’t.”
| Sites Deployed | Voltage-Related Failures | RS485 Integration | Model Selected |
| 32 | 0 in 18 months | 100% first-startup success | H750 Dual SIM |
Case 2 — Electrical Substation Upgrade, 18 Distribution Points, Middle East
A power distribution company was retrofitting remote monitoring onto 18 medium-voltage substations as part of a grid modernisation programme. Each substation had a protection relay panel communicating via RS485, a digital power meter on a separate RS485 bus, and a protection system that generated dry-contact alarm outputs — one for overcurrent trip, one for under-voltage trip, one for transformer temperature alarm. The monitoring centre needed all three data streams: Modbus RTU data from both serial buses, and instant alarm notification from all three dry contacts without waiting for a SCADA polling cycle that ran every 30 seconds.
The substation cabinet power was 48V DC from the station battery system — a supply type that immediately eliminated the majority of candidate routers whose maximum input was 30V or 36V DC. Cabinet internal temperatures were measured during site survey at up to 68°C in the afternoon due to partial cabinet enclosure and direct solar exposure on the cabinet surface. The protection relay system manufacturer had a certification requirement for any device connected to the relay panel to carry CE marking with documented EMC test reports.
The E-Lins H700 gigabit dual-band Wi-Fi 4G industrial router was specified: the 5–60V DC input option accommodated the 48V station battery system without a DC-DC converter at each site; the two serial ports (DB9 + terminal block) connected both RS485 buses simultaneously without an additional serial multiplexer; the four DI/DO ports connected directly to the three dry-contact alarm outputs with one port spare; and the −35°C to +75°C rating provided thermal margin above the measured 68°C cabinet peak.
Deployment Outcome — Power Distribution, Middle East
The deployment eliminated two planned line items from the project BOM: the DC-DC converter that would have been required at each site for a 48V-to-24V step-down, and the serial multiplexer that would have been required to connect two RS485 devices to a single-port router. The DI/DO alarm integration delivered protection relay trip notifications to the monitoring centre in under four seconds from event occurrence — compared to the maximum 30-second delay inherent in the SCADA polling cycle. During commissioning, the project engineer noted that the dual serial port configuration — normally an unusual requirement — had been the deciding specification criterion: “Every other router we evaluated either had one serial port or required an external hub. The H700 just had two ports and that was the end of the conversation.”
| Sites Deployed | Additional Hardware Eliminated | Alarm Notification Latency | Model Selected |
| 18 | DC-DC converters + serial multiplexers | <4 seconds vs 30s polling | H700 (5–60V option) |
Industry Group 02 Smart Manufacturing
Case 3 — Private 5G AGV Fleet, 64 Endpoint Nodes, Automotive Parts Facility, Germany
H900frc — deployed as AGV and sensor endpoint in a private 5G campus deployment
A German Tier-1 automotive supplier was deploying a private 5G campus network across a 55,000 m² production facility as the connectivity backbone for a factory digitalisation programme. The network would serve a mixed endpoint fleet: 28 AGVs running real-time navigation software, 24 production cell sensor nodes reporting process data and machine health telemetry, and 12 quality inspection stations with moderate-resolution cameras streaming at approximately 3–5 Mbps each. All endpoints needed 5G SA core connectivity for network slicing — the company’s automation team had specified that AGV navigation traffic must be isolated on a deterministic low-latency slice, while sensor telemetry and camera streams sat on separate slices with different QoS parameters.
The initial hardware evaluation compared a full 5G SA router against the 5G RedCap private 5G campus IoT endpoint router for the AGV and sensor roles. The quality inspection cameras, at 3–5 Mbps each, were clearly within RedCap’s ceiling and did not require the full 5G modem’s throughput headroom. The AGV navigation traffic required guaranteed sub-20ms latency — which the 5G SA core network slicing provided at the network infrastructure level, not the modem level, meaning RedCap achieved the same latency guarantee as full 5G on the same slice.
The E-Lins H900frc 5G RedCap industrial IoT router was deployed across all 64 endpoints. The private network infrastructure vendor confirmed Release 17 RedCap support on their core configuration. At 64 units, the per-module cost difference between RedCap and full 5G redirected approximately 18% of the endpoint hardware budget into additional coverage infrastructure in the facility’s most radio-challenging production zone — a press shop with extensive overhead steel structure creating signal shadow areas.
Deployment Outcome — Automotive Parts Factory, Germany
The private 5G network went live with all 64 H900frc endpoints connected and slice-assigned within the commissioning window. AGV navigation latency measured at 12–16ms end-to-end on the dedicated navigation slice — within the automation team’s 20ms specification threshold. Battery-powered sensor nodes on the moving material handling racks achieved a measured inter-charge interval of 18.5 hours using the RedCap modem’s lower active power draw, compared to a modeled 13.8 hours for the equivalent full 5G configuration — eliminating the need for a planned third charging station in the assembly zone. The project lead described the RedCap specification decision as “the one we were most uncertain about going in, and the one we were most glad we made by the end.”
| Endpoints Deployed | AGV Nav Latency | Battery Node Interval | Model Selected |
| 64 | 12–16 ms (target: <20 ms) | 18.5h vs 13.8h full 5G model | H900frc 5G RedCap |
Case 4 — OEM Embedded 5G Gateway, Connected Welding Station Product, South Korea
A South Korean industrial equipment manufacturer was developing the third generation of their automated MIG welding stations — adding built-in process data logging, remote diagnostics, and predictive maintenance capabilities. The welding station’s control system already captured weld quality metrics (voltage, current, wire speed, shielding gas flow) continuously; the new generation needed to transmit those metrics to the manufacturer’s cloud analytics platform in real time, and allow service engineers to access the station’s diagnostic interface remotely without a site visit.
The critical constraint was brand transparency: the welding station’s operator panel and diagnostic UI had to present all connectivity features as native capabilities of the machine, with no visible reference to a third-party router or connectivity module. The control system ran a proprietary embedded Linux stack with its own cloud API; the connectivity module needed to integrate with that API rather than presenting a generic router interface. And the device had to physically fit inside the welding station’s existing control cabinet — a 140mm × 80mm footprint constraint that eliminated most standard industrial DIN-rail routers.
The OEM custom firmware 5G industrial router embedded connected machine product requirement pointed directly to the E-Lins OEM/ODM program. The E-Lins H685f super-mini 5G industrial router — at 100×60×21 mm — fit the cabinet footprint constraint; its OEM firmware program delivered a custom build that replaced all E-Lins branding with the manufacturer’s own UI elements and connected directly to their cloud API endpoint. The 5G SA/NSA modem provided the cellular backhaul; the RS232/RS485 serial port integrated with the welding station’s internal controller bus.
Deployment Outcome — Welding Station OEM, South Korea
The OEM firmware build was completed through E-Lins’ engineering engagement within the manufacturer’s product development timeline. The welding station launched with the H685f as its embedded connectivity module — completely invisible to the customer as a third-party component. Service engineers access the station’s remote diagnostic interface through the manufacturer’s own cloud platform; the underlying router is transparent in the workflow. Within 12 months of product launch, the manufacturer had deployed the same H685f-based connectivity module across two additional product lines in their portfolio. Their product engineering lead described the OEM engagement: “We evaluated five router brands for this project. E-Lins was the only one that could give us the firmware we needed, in the size we needed, without making our machine look like it had someone else’s technology inside it.”
| Product Lines Deployed | Form Factor | Third-Party Branding | Model Selected |
| 3 (over 12 months) | 100×60×21 mm — fits cabinet | Zero visible to end customer | H685f (OEM firmware build) |
Industry Group 03 Transportation & Smart City
Case 5 — Smart Traffic Surveillance Network, 340 Intersections, Southeast Asian City
H820QOf — pole-mounted at traffic intersections across 340 sites
A municipal traffic management authority was replacing an aging fiber-connected CCTV network at 340 signalised intersections across the city. The fiber network had required significant civil works for each installation and was proving expensive to maintain as cable joints degraded — the authority was moving to cellular backhaul for all new camera installations and replacements. Each intersection camera was a 4K IP camera streaming at 8–12 Mbps to a central video management system, mounted on a traffic signal pole at 4–6 metres height.
The previous generation of cellular CPE — IP65-rated indoor routers mounted in weatherproof enclosures on the poles — had produced a field replacement rate of approximately 11% per year, primarily from moisture ingress through cable gland failures and condensation accumulation inside the enclosures during the city’s intense monsoon season combined with dry-season heat cycling. The authority’s infrastructure team had calculated that the annual maintenance cost from these failures — truck rolls, replacement hardware, and traffic management during pole access — exceeded the original CPE hardware cost across the fleet within two years.
The specification for the replacement generation required: IP68 ingress protection rated at the enclosure-plus-cable-entry level (not IP65), PoE 802.3at input to eliminate separate DC cable runs to the pole top, 5G cellular backhaul with 4G LTE fallback, and central TR-069 or NMS management to eliminate per-device truck-roll access for firmware updates and configuration changes. The E-Lins H820QOf IP68 5G outdoor CPE was specified: its purpose-built outdoor enclosure with industrial-grade cable glands at all entry points, standard IEEE 802.3at PoE input, built-in high-gain antennas eliminating external connector exposure points, and E-Lins NMS for centralised management across all 340 units.
Deployment Outcome — Smart City Traffic Surveillance, Southeast Asia
After 18 months of operation across the replacement cohort — covering two complete monsoon seasons — the field failure rate had dropped from 11% per year to under 1.4% per year, with zero moisture-related failures in the replacement units. The authority’s network operations centre managed all 340 units through the E-Lins NMS, pushing firmware updates and configuration changes without any field access requirement. The annual maintenance cost saving from reduced truck rolls — at the authority’s own calculation — offset the per-unit price premium of the IP68 specification over the previous IP65 devices within the first 14 months of deployment. The infrastructure director described it as “the first time we’ve bought a more expensive piece of hardware and actually saved money in year one.”
| Sites Deployed | Annual Failure Rate | Moisture Failures | Model Selected |
| 340 | 11% → 1.4% | 0 (vs previous gen) | H820QOf IP68 Outdoor |
Case 6 — Commercial Vehicle Fleet Telematics, 220 Trucks, Central Europe
A logistics company operating a 220-vehicle long-haul truck fleet across six Central European countries was replacing its previous telematics system — which had used a single-SIM 4G router paired with a separate GPS tracker — with an integrated in-cab connectivity platform. The new system needed to: provide internet access for driver tablets running the company’s delivery management application; transmit CAN bus vehicle diagnostic data to the fleet management platform; provide real-time GPS positioning; maintain connectivity across six different national cellular networks; and support remote diagnostics and configuration updates without requiring the vehicle to return to depot.
The multi-country coverage requirement made dual SIM a structural necessity rather than a redundancy option: no single carrier provided reliable coverage across all six countries at acceptable data rates, but pairing two complementary carriers could cover 96–98% of the route network based on coverage map analysis. The CAN bus integration was the second constraint — few compact vehicle routers include native CAN interface support alongside cellular and GPS. The dual SIM 4G router CAN bus GPS vehicle fleet telematics combination is specifically where the H720’s hardware breadth distinguished it from simpler vehicle telematics devices.
The E-Lins H720 dual SIM 4G industrial router with GPS option was specified, with dual SIM configured with ICMP health-check triggered switching between the two carrier SIMs. The H720’s five Ethernet LAN/WAN ports connected the driver tablet, the CAN bus gateway, and the cab camera without an additional switch. Power was taken from the vehicle’s ignition-switched 24V DC bus with the router configured for automatic power-on/power-off on ignition sense — a configuration supported through the H720’s DI input reading the ignition signal.
Deployment Outcome — Fleet Telematics, Central Europe
Across 220 vehicles deployed over a six-month rollout, the dual SIM configuration achieved measured connectivity availability of 97.3% of operating hours across the full six-country route network — compared to 91.8% on the previous single-SIM system operating on the primary carrier alone. The improvement was most pronounced on cross-border routes through rural sections of Poland and Romania where the primary carrier’s coverage thinned and the secondary SIM maintained the connection consistently. CAN bus diagnostic data transmission latency averaged 8 seconds from vehicle event to fleet management platform record — within the logistics company’s 15-second specification. The fleet operations manager noted: “The dual SIM performance on the rural Romanian routes was the part we didn’t fully believe until we saw the data. That was exactly the problem we’d been having.”
| Vehicles Deployed | Connectivity Availability | CAN Data Latency | Model Selected |
| 220 | 97.3% vs 91.8% (prev.) | 8s avg (target: <15s) | H720 Dual SIM + GPS |
Product-to-Case Reference Table
The table below maps each case to the E-Lins model selected, the two or three specification criteria that drove the selection decision, and the primary industry vertical. Use this as a quick reference if you are evaluating a deployment with similar characteristics to one of the six cases.
| Case | Industry | E-Lins Model | Deciding Specification Criteria | Measurable Outcome |
|---|---|---|---|---|
| 1 — Water Utility 32 pump stations, SE Asia | Energy & Utilities | H750 Dual SIM | RADIUS/TACACS+ authentication compliance; RS485 Modbus RTU; 5–40V DC solar power input; dual SIM failover | Zero voltage-related failures in 18 months; 100% RS485 first-startup success |
| 2 — Power Substation 18 distribution points, Middle East | Energy & Utilities | H700 (5–60V option) | 48V DC input (5–60V option); dual RS485 serial ports simultaneously; 4× DI/DO for protection relay alarms; −35°C to +75°C | Eliminated DC-DC converters + serial multiplexers; alarm notification <4s vs 30s polling |
| 3 — AGV Factory 64 endpoints, Germany | Smart Manufacturing | H900frc 5G RedCap | Private 5G SA core connectivity; network slicing for AGV navigation vs telemetry; lower per-module cost and power draw at endpoint scale | AGV latency 12–16ms; battery interval +34% vs full 5G; 18% endpoint budget redirected to infrastructure |
| 4 — OEM Welding Station Product embedding, South Korea | Smart Manufacturing | H685f (OEM firmware) | Super-mini form factor (100×60×21 mm); OEM firmware branding suppression; custom cloud API integration; 5G SA/NSA cellular backhaul | Zero third-party branding visible; deployed across 3 product lines in 12 months |
| 5 — Traffic Surveillance 340 intersections, SE Asian city | Transportation & Smart City | H820QOf IP68 Outdoor | IP68 enclosure with rated cable glands; IEEE 802.3at PoE PD; built-in high-gain antenna; centralised NMS management | Annual failure rate 11% → 1.4%; zero moisture failures; maintenance cost saving in year 1 |
| 6 — Truck Fleet Telematics 220 vehicles, Central Europe | Transportation & Smart City | H720 Dual SIM + GPS | Dual SIM for 6-country coverage; GPS/GNSS integrated; 5× Ethernet for tablet + CAN gateway + camera; ignition-sense DI | Connectivity 97.3% vs 91.8% prev.; CAN data latency 8s avg. |
Five Lessons That Appear Across All Six Cases
Looking back across the six deployments documented here, five patterns appear consistently — regardless of industry, geography, or application type. These are the conclusions I draw from working through the specification process with customers in very different contexts.
1. The Specification Criterion That Matters Is Rarely the One That Appears in the Headline Comparison
In not one of these six cases was 4G or 5G throughput ceiling the deciding criterion. In five of the six, the decision turned on a combination of power input range, temperature rating, serial port hardware, dual SIM configuration logic, or ingress protection — specifications that appear in the detailed datasheet rather than in headline marketing comparisons. The lesson for engineers evaluating cellular routers is to start from the physical installation constraints — power, temperature, interfaces, environment — before evaluating connectivity performance.
2. Dual SIM Failover Changes the Risk Profile of Remote Deployments Fundamentally
Cases 1 and 6 both demonstrated measurable connectivity improvements attributable specifically to dual SIM — not to 4G performance improvements, not to antenna upgrades, but to the automatic availability of a backup carrier path when the primary path failed. At remote unmanned sites (Case 1) and on multi-country routes (Case 6), single-carrier coverage is a statistical statement about average performance, not a guarantee. Dual SIM converts a single-point-of-failure cellular link into a redundant path with independent failure modes.
“I’ve never had a customer come back to me after a dual SIM deployment and say they didn’t need it. I’ve had several come back after a single SIM deployment and say they wished they’d specified it. The asymmetry is telling.”— E-Lins Application Engineering Team
3. Power Input Range Is a Site Survey Deliverable, Not a Checkbox
Cases 1 and 2 both involved power systems where the DC supply voltage at the router terminals varied significantly from the nominal system voltage — the solar/battery systems in Case 1 ranged from 9.8V to 14.6V; the 48V substation battery in Case 2 was simply incompatible with most routers’ maximum input specification. In both cases, a site survey that measured or calculated the actual voltage range across all operating states — including battery depletion floors and generator start transients — was the input that determined the correct power specification. Specifying from nominal voltage alone is how routers end up going out of specification at exactly the moments that matter most operationally.
4. Hardware Interface Completeness Eliminates Accessories That Add Cost, Complexity, and Failure Points
In Cases 2, 4, and 6, the router’s hardware interface set directly eliminated accessories that would otherwise have been required: DC-DC converters and serial multiplexers in Case 2, an additional Ethernet switch in Case 6. Each eliminated accessory represents not just a cost saving but a reduction in the number of components that can fail, that need commissioning, that consume cabinet space, and that require firmware or driver management. A router with a broader hardware interface set costs more per unit than a simpler device; the total installed cost comparison often favours the more complete device once accessories are included.
5. The Right Specification Protects Budget in Ways the Initial Comparison Doesn’t Capture
In Cases 3, 5, and 4, the correct specification decision delivered financial benefits that were not visible in the initial per-unit price comparison. In Case 3, RedCap’s lower module cost redirected 18% of endpoint budget into infrastructure that improved facility-wide coverage. In Case 5, the IP68 specification’s lower failure rate generated maintenance savings that offset the per-unit price premium within 14 months. In Case 4, OEM firmware customisation eliminated development overhead the manufacturer would otherwise have borne to adapt a non-OEM device. Total cost of ownership over the deployment lifecycle consistently tells a different story than per-unit hardware cost at the procurement stage.
One honest caveat: none of these cases involved a situation where E-Lins was the objectively correct choice for every requirement. In Case 6 specifically, the customer evaluated a competing vehicle telematics device that had native CAN interface support — a hardware capability the H720 covers through a CAN gateway connected to its Ethernet port rather than a direct CAN bus connector. For deployments where direct CAN integration without a gateway device is a hard requirement, that distinction matters and should be investigated. The point of documenting these cases honestly is not to claim universal superiority — it is to show how the specification decision was actually made, so that engineers can apply the same methodology to their own projects.
Where Each E-Lins Model Fits Across Industries
H750 / H720
Water & Power Utilities
Dual SIM failover, RS485 serial for RTU/relay integration, wide-voltage DC for solar/battery power, RADIUS authentication for compliance, DI/DO for alarm reporting.
H700
Substations & Grid Edge
48V DC input, dual serial ports for simultaneous relay + meter integration, DI/DO for protection trip alarms, Gigabit Ethernet for historian connections, dual-band Wi-Fi for engineering access.
H900frc
Private 5G Factory IoT
5G RedCap for private network endpoints. Lower per-module cost at fleet scale, 5G SA core network slicing, lower power draw for battery-powered nodes on moving equipment.
H685f OEM
OEM Connected Products
Super-mini form factor for cabinet embedding, OEM firmware branding program, 5G SA/NSA, RS485 serial for internal bus integration. No third-party branding visible to end customer.
H820QOf
Smart City Surveillance
IP68 outdoor enclosure, PoE 802.3at input, pole mount, built-in high-gain antennas, centralised NMS management. Eliminates weatherproof cabinet and external antenna failure points.
H720 Dual SIM
Vehicle Fleet Telematics
Dual SIM for multi-country coverage, integrated GPS, 5-port Ethernet for tablet + CAN gateway + camera, ignition-sense DI, wide-voltage 24V vehicle bus. One device replaces router + GPS tracker + switch.
Extended Reading
E-Lins H750 Dual SIM 4G Industrial Router — Full specifications for the water utility and standard wellhead deployment model: RS485 serial, 4× DI/DO, GPS, 5–40V DC, dual SIM, RADIUS/TACACS+.
E-Lins H700 Gigabit Dual-Band 4G Router — Dual serial ports, Gigabit Ethernet, dual-band Wi-Fi, 5–60V DC option for 48V substation applications, 880 MHz dual-core CPU.
E-Lins H720 Dual SIM 4G Router — Five Ethernet ports, dual SIM, RS485, DI/DO ×4, GPS — for multi-device sites and vehicle fleet telematics.
E-Lins H900frc 5G RedCap IoT Router — Purpose-built for private 5G campus IoT endpoints: lower per-module cost, lower power draw, 5G SA core network slicing access.
E-Lins H685f Super-Mini 5G Router — OEM/ODM program with custom firmware branding, 100×60×21 mm form factor, RS485 serial, Wi-Fi 6 option, 5G SA/NSA.
E-Lins H820QOf IP68 5G Outdoor CPE — IP68-rated pole-mount 5G outdoor CPE for smart city, traffic surveillance, and outdoor industrial monitoring without equipment cabinet.
E-Lins Project Enquiry — Share your application type, site count, power system, serial device parameters, industry vertical, and cellular coverage for a direct model and configuration recommendation.
Frequently Asked Questions
Q1:How do I know whether my deployment needs dual SIM or whether single SIM is sufficient?
My simple decision rule is to specify dual SIM for unmanned sites relying solely on cellular access with a second carrier available, as its small extra hardware cost easily outweighs expensive site service calls and downtime from monitoring outages, proven by Cases 1 and 6 delivering measurable connectivity gains solely from dual-SIM configuration.
Q2:What is the difference between transparent DTU mode and Modbus gateway mode for RS485 serial integration?
In transparent DTU mode the router transparently forwards raw serial data over TCP/UDP to SCADA without protocol parsing, while Modbus gateway mode enables automatic conversion between Modbus TCP and Modbus RTU for heterogeneous communication, and H750, H720 and H700 support both modes for you to select according to your SCADA structure before serial port configuration.
Q3:Can E-Lins routers be managed centrally across dozens or hundreds of sites without per-device manual access?
Yes, all E-Lins industrial routers support multi-site centralized management via free E-Lins cloud NMS with remote configuration, upgrades and secure tunnel access without public IPs, validated in a 340-node traffic surveillance project, and they also support TR-069 and SNMP for third-party management systems.
Q4:What VPN protocol works best for connecting oil field or substation SCADA traffic to a central operations centre?
VPN choice for oilfield and substation SCADA hinges on central gateway compatibility: widely compatible IPsec (with DMVPN for multi-site scalability) is mainstream, high-performance WireGuard suits new projects, while OpenVPN fits existing legacy systems, matching the six project cases.
Q5:How does the E-Lins OEM/ODM program work for a manufacturer who wants to embed a router in their own product?
E-Lins OEM/ODM begins with confirming your hardware, firmware, size and volume demands, we provide brand-removed customized firmware, and the compact H685f is ideal for embedding, as proven by a Korean welding equipment maker project; you may start by consulting our engineers.
Q6:Is 5G RedCap suitable for AGV navigation traffic where sub-20ms latency is a hard requirement?
Yes, 5G RedCap fits AGV navigation requiring latency under 20ms; H900frc achieves 12–16ms latency on 5G SA network slicing, and its simplified hardware won’t affect sliced latency while bringing cost and power advantages over full 5G.
Conclusion: The Right Specification Is the One That Matches the Field, Not the Datasheet
After documenting these six deployments, the pattern I keep returning to is that the specification decisions that determined each project’s outcome were made in the field — at the site survey, at the instrument documentation review, at the carrier coverage analysis — not at the product comparison stage. By the time a team has measured the cabinet temperature, logged the power rail voltage, confirmed the serial device parameters, and mapped the carrier coverage, the model selection is usually obvious. The comparison table confirms it; it rarely drives it.
The six E-Lins industrial IoT connectivity solutions documented here — H750, H700, H720, H900frc, H685f, and H820QOf — serve different buyer profiles across energy, manufacturing, and transportation. What they share is the industrial-grade foundation: wide-temperature operating range, wide-voltage DC input, enterprise security stack, centralised NMS management, and a VPN suite that terminates on enterprise firewall infrastructure. The differences between them are the hardware interface breadth, cellular generation, form factor, and enclosure rating — variables that map directly to specific installation profiles once the field requirements are documented.
Three things to take from these cases into your own project specification:
- Measure, don’t estimate. Cabinet temperature, power rail voltage range, and actual application data rates all determine the correct specification — and all three are consistently different from the values assumed from datasheets, regional weather data, and throughput maximums when measured at the actual installation point.
- Dual SIM at unmanned remote sites is a reliability requirement, not an optional upgrade. The cases where it made the most difference were the ones where nobody initially thought they needed it.
- Total cost of ownership across the deployment lifecycle tells a consistently different story from per-unit hardware cost at procurement. The IP68 specification in Case 5 and the RedCap specification in Case 3 both delivered financial returns that were not visible in the initial procurement comparison — but appeared clearly in the 12-to-18-month operational data.
Working on a Project Similar to One of These Cases?
Tell E-Lins your industry, application type, site count, power system, serial device parameters, cellular coverage situation, and any compliance requirements. We will identify which model and configuration fits your deployment — and flag any specification questions that need to be resolved before hardware is ordered.
