ORBCOMM is an important reference for industrial satellite IoT. The main distinction is between its OG2 VHF network and services using other satellite infrastructure; those choices lead to different terminals, RF designs and delivery expectations.
Reviewed October 30, 2026. Dates distinguish operating services, launch announcements and future plans. Published capacity figures describe their stated configuration; they are not guaranteed performance for every terminal.
Contents
- Executive Summary
- ORBCOMM Is More Than One Radio Network
- RF Context and Deployment Engineering
- Reference
Executive Summary
The table separates the service, orbit and technical distinctions used throughout this note.
Topic | Summary |
|---|---|
Primary application | Industrial telemetry and asset tracking |
OG2 | ORBCOMM VHF satellite network |
OGi | Inmarsat L-band modem path |
OGx | Service evolution from IsatData Pro, announced June 2024 |
ORBCOMM Is More Than One Radio Network
ORBCOMM is associated with a LEO messaging constellation, but its product portfolio also uses other satellite infrastructure. Identify the service behind the terminal before assigning an orbit, frequency band or performance expectation to the company name.
OG2 and industrial telemetry
The OG2 modem family connects to ORBCOMM's VHF network. Its intended applications include asset tracking and monitoring across transport, marine and industrial equipment. The related OGi modem uses the Inmarsat L-band network instead. [1]
A temperature report, vehicle position or equipment alarm can fit into a small message. That differs from providing an IP broadband connection to the asset. The application should define the payload, reporting interval and maximum acceptable age before selecting a modem or service.
For example, a refrigerated shipment can report temperature and battery state periodically. A threshold event may deserve a higher reporting priority. The operational value comes from receiving useful measurements in time, rather than from the nominal peak bit rate alone.
Why OGx is not simply another OG2 satellite generation
ORBCOMM introduced OGx in June 2024 as an evolution of its IsatData Pro service using existing satellite infrastructure. The announcement describes supported ST-series device upgrades and lower-power operation. It does not describe a replacement OG2 spacecraft constellation. [2]
Figure 1. Rows compare functional roles or dated states. Boxes are explanatory and are not a measured traffic trace.
Similar application interfaces can simplify product integration without making the radio hardware identical. The antenna, supply design, supported network and provisioning still matter. A product migration should therefore be checked against the named device and service, rather than inferred from a similar modem connector.
RF Context and Deployment Engineering
A useful ORBCOMM comparison separates the historical VHF constellation from the wider industrial IoT service portfolio. Frequency bands, terminal power and delivery behavior belong to the selected network, not to a single company-wide specification.
VHF messaging and L-band alternatives
The historical ORBCOMM satellite system uses portions of the 137–138 MHz downlink and 148–150.05 MHz uplink bands. Exact sub-band assignments and sharing conditions are narrower than these broad labels. They must be checked against the applicable authorization. [3]
At 150 MHz, a free-space quarter wavelength is approximately half a metre. This simple calculation explains why a small messaging board still needs attention to antenna placement and ground-plane design. The enclosure, vehicle body and nearby electronics can strongly affect the installed antenna.
Message delivery and power budget
A battery-powered installation needs more than a low sleep-current specification. Transmission bursts, receive windows, positioning and retries all consume energy. The application should distinguish a locally queued report from a report delivered to the remote system.
Design question | Why it matters |
|---|---|
Which network and modem? | OG2, OGi and OGx names do not identify the same RF path |
What message age is acceptable? | A periodic report and an urgent command have different requirements |
How is success acknowledged? | Radio acceptance and application processing are different stages |
What is the installed antenna environment? | Obstructions and nearby structures affect reception |
What is the burst power requirement? | A suitable average battery budget can still fail during transmission |
For deployment tests, log measurement time, modem-queue time and application-receipt time separately. This reveals whether delays come from the device, radio access or backend handling. Include sequence numbers and a policy for stale or duplicate messages. These are general telemetry design practices, not a guaranteed ORBCOMM latency specification.
No live OG2 spacecraft count is asserted here. Historical launch totals and early licensing designs cannot establish the number of healthy satellites today. The references support the architecture and service distinctions; procurement still needs a current coverage and product-support check.
Reference
Primary sources used for this note are listed below. Any limited source review is identified explicitly; general engineering explanations and illustrative calculations are not vendor performance measurements.
[1] OG2 and OGi modem datasheet : Indexed product-overview extract reviewed; the original PDF URL returned 404 during this review.
[2] ORBCOMM OGx announcement : June 18, 2024; service evolution and supported device upgrades.
[3] DA 19-1044 : Historical ORBCOMM spectrum context in paragraphs 6–14 and footnotes; this is the Swarm order, not an OG2 constellation grant.