Capability · connectivity
Ethernet connectivity for secure remote asset monitoring
Ethernet is the wired path on a field gateway — the cable that keeps compounds, towers and cabinets online when cellular alone is not the whole answer. TrackSyte® folds that into secure remote asset monitoring: one gateway, CAN, Modbus, Ethernet, LTE — into one monitoring stack. Neo 2 ships with Ethernet fitted, alongside RS485, CAN, 12V, Bluetooth and cellular IoT, so wired site devices can reach TrackSyte® Portal over MQTT / API.
GNSS is fitted as standard on Neo 2 — a full-constellation GPS/GNSS receiver that can support tracking and GPS-related functions. This page is Ethernet as a gateway-to-Portal monitoring path for site assets — not industrial VPN, PLC remote-access or machine-builder service-desk positioning. Hub dual-Ethernet and family depth live on Hardware & integrations with reciprocal links — not as a denial of Neo 2.
What Ethernet means on a field gateway
On site, Ethernet is the reliable wired link inside a compound, tower trailer or industrial cabinet. Where a switch, NVR edge, power cabinet or controller already speaks Ethernet, a field gateway can use that path to bring status into the same monitoring stack that also covers serial buses and cellular backhaul.
Site teams care because wired reliability reduces “is it the SIM or the asset?” ambiguity. Hire desks and ops get a stable path for assets that live on shore power or compound networks — without pretending every remote trailer has a cable. For UK temporary and construction compounds, Ethernet is often the preferred path when the kit sits inside a cabinet or on a powered trailer with a network already present.
We keep the language practical. This is not a brochure for every industrial Ethernet standard variant, and we do not paste Hub comparison tables wholesale from hardware-integrations. The point for buyers is simpler: if the site has a wired path, Neo 2 can use Ethernet into TrackSyte’s monitoring stack.
What Neo 2 supports
Locked truth: Neo 2 is fitted with Ethernet (wired backhaul / device path), together with CAN, Modbus, GPIO and RS485 in, and LTE-M / NB-IoT out into TrackSyte® Portal via MQTT / API. Neo 2 also ships with a 12V supply, Bluetooth, and GNSS as standard — a full-constellation GPS/GNSS receiver that can support tracking and GPS-related functions.
RS485 is on Neo 2, not Hub-only. Pair Ethernet with RS485 / Modbus and CAN bus when the asset stack needs serial or plant networks as well as a wired backhaul. For Hub dual-Ethernet behaviour and broader family options, see Hardware & integrations — without treating Hub as the exclusive Ethernet or RS485 story. Canonical hardware detail: Neo 2.
- Ethernet — yes, fitted on Neo 2 (wired backhaul / device path)
- Also in / fitted: CAN · Modbus · GPIO · RS485 · 12V · Bluetooth
- Cellular: LTE-M · NB-IoT — pair with Ethernet; see cellular IoT
- GNSS fitted as standard — full-constellation GPS/GNSS that can support tracking and GPS-related functions
- Into Portal: MQTT / API
Where Ethernet shows up on site
CCTV and security towers. Mobile and temporary towers often have an Ethernet edge inside the trailer. See CCTV tower monitoring for the sector story; this page stays on the interface.
PID and perimeter sites. Fixed and temporary intrusion stacks frequently use wired cabinets. See PID monitoring.
Temporary power cabinets. Generators, hybrids and BESS compounds often sit in Ethernet-reachable cabinets. See hybrid and temporary power.
Construction compounds. Main-contractor compounds with shore network or trailer Ethernet feed mixed fleets. Light cross-link: construction fleet monitoring; plant CAN depth remains on construction equipment telematics.
- CCTV and security towers — Ethernet edge common
- PID / perimeter wired cabinets
- Temporary power / hybrid / BESS cabinets
- Construction compounds with shore or trailer Ethernet
Into TrackSyte Portal
Ethernet traffic joins the same secure remote asset monitoring path as other Neo 2 interfaces: into TrackSyte® Portal over MQTT / API. For developer and integration detail see the API integration. Ops still get the Portal view; engineering teams get a clear data path without a separate product brand.
Secure data-path language stays honest: authentication, TLS, certificates and MQTT. No invented ISO, SOC or compliance badges. Cornwall HQ and company context live on About for EEAT without stretching this capability page into a corporate brochure.
FAQs
Is Ethernet available on Neo 2?
Yes. Neo 2 is fitted with Ethernet connectivity, alongside CAN, Modbus, GPIO, RS485, LTE-M / NB-IoT, 12V supply, Bluetooth and GNSS as standard.
Does Hub also support Ethernet?
Yes. Hub dual-Ethernet and family depth live on /hardware-integrations — without treating Hub as the exclusive Ethernet or RS485 story. RS485 is on Neo 2 as well.
Does Neo 2 include GPS / GNSS as well as Ethernet?
Yes. GNSS is fitted as standard on Neo 2: a full-constellation receiver that can support tracking and GPS-related functions, alongside Ethernet and the gateway monitoring stack.
When should I choose Ethernet vs cellular?
Choose by site constraint. Wired compounds and towers with network often prefer Ethernet; remote or temporary sites often need LTE-M / NB-IoT. Neo 2 supports both paths into Portal — see /capabilities/cellular-iot.
Is this an industrial VPN or PLC remote-access product?
No. Ethernet here is a wired monitoring path on a multi-protocol field gateway into TrackSyte® Portal for secure remote asset monitoring — towers, power, pumps and plant. It is not industrial VPN, OPC-UA factory remote access or a machine-builder service desk.
Explore Ethernet connectivity on Neo 2
If your site assets already have a wired path and you want that status in a secure remote monitoring stack, book a demo. We will map Neo 2 Ethernet alongside cellular, RS485 and CAN where relevant, and show Portal. Bring a cabinet or tower shape if you can; we map interfaces honestly.