Telemetry Station satellite telemetry platform logo
Calculate
Telemetry Station · BEAR Module familyPre-order inquiries open

BEAR Module 9704

Satellite connectivity for embedded systems, ready to integrate. An Iridium 9704 modem, power management and antenna options on one board, with open-source firmware and activation in about five minutes on Telemetry Station.

$259estimated target price per module, before add-ons
Ships from California, USASales target April 1, 2027 (tentative)
Request pre-orderView preliminary datasheet

In development at gate G1. Evaluation-kit dates are published once build and supply are confirmed. Pre-ordering is an inquiry only: no payment is taken. Telemetry Station activates any eligible Iridium modem, and the module works with any data service.

PWRVIN / GNDInput protectionEnergy storageRegulationSequencingIridium 9704Certus IMT modemJSPR over UARTANTPWRRDYBEAR-9704IMEI · S/N · QRENABLEBOOTEDTXDRXDTX_ACTWAKE_INWAKE_OUTHost header (UART 230400 8N1)

Iridium 9704 modem

Defined

Iridium Certus IMT modem. Messages up to 100,000 bytes over the Iridium network, controlled by the SDK through the JSON-based JSPR serial protocol.

Certus IMT100,000 byte messagesJSPR

Illustrative layout, not to scale. Dimensions, connector and pin positions are published with the Rev A datasheet.

Network
Iridium Certus 9704 (IMT)
Message size
Up to 100,000 bytes
Host link
UART 230400 8N1
Control lines
ENABLE + BOOTED
Host SDK
Portable C99, MIT, alpha
Sales target
April 2027, tentative
One board, one library

Satellite messaging without the hard parts.

Adding Iridium to a remote sensor is harder than the sensor. Sourcing a modem, surviving transmit bursts, sequencing power, qualifying an antenna and writing a driver are each places a project slips. The BEAR Module collapses them.

You needBEAR Module provides
A satellite modemIridium 9704 modem on the board
A supply that survives transmit burstsOn-board power management with energy storage (target)
Safe on and off sequencingOne ENABLE line and one BOOTED line
An antennaExternal Iridium antenna path; candidate qualification pending
A serial driverOpen-source Telemetry Station SDK, portable C99
A small, cheap message formatFree Payload Optimizer that generates your encoder
A plan, activation and your dataTelemetry Station: calculator, five-minute activation, 5-year storage

You supply a microcontroller and a power source. BEAR is in G1 design; power circuits and antenna configurations are not qualified. Module hardware and airtime are separate.

  • Open firmware

    MIT-licensed C99 SDK on GitHub. Read it, port it, ship it.

  • Designed for the whole workflow

    Payload, plan, activation and data share one IMEI-based flow.

  • Power handled for you

    Protection, regulation, burst energy and safe sequencing are module design goals; circuits and measured performance remain open.

  • Real engineers

    Pacific Gyre builds oceanographic instruments with the same stack.

  • Custom when you need it

    Sensors, firmware and full products designed and integrated for you.

  • Ships from California

    One source for hardware, activation and support.

Preliminary datasheet · P1

Specifications, signals and status.

Every value carries a status. Defined means the product-level design decision is made. Target is proposed design intent, not a guaranteed specification. Coming soon values are published with the Rev A datasheet after verification on hardware.

Overview

  • ModemIridium 9704 (Certus IMT)Defined
  • Message sizeUp to 100,000 bytes per messageDefined
  • Host interfaceVIN, GND, ENABLE, BOOTED, TXD, RXDDefined
  • Serial format230400 baud, 8N1, no flow controlDefined
  • Serial protocolJSPR (JSON), implemented by the SDKDefined
  • Host compatibilityHost-independent; ports validated individually, F169 firstDefined
  • Optional GNSSPosition and time option under evaluation; configuration and qualification pendingIn development
  • Power managementProtection, regulation, energy storage, sequencingIn development
  • LabelingPart number, serial, revision, IMEI, scannable codeTarget

Signals

SignalDirDescriptionRequiredSDK function
VINInMain supplyYesHost supply
GNDRefPower and signal returnYesn/a
ENABLEInHigh starts the module. Low starts shutdownYespower_start / power_stop
BOOTEDOutHigh when boot completes; SDK readiness follows the UART handshakeYesboot_ready
TXDOutSerial data to host (host RX)Yesserial_read
RXDInSerial data from host (host TX)Yesserial_write
TX_ACTIVEOutHigh while the modem transmitsOptionalNot used today
WAKE_INInReserved: host-controlled low-power wakeOptionalNot used today
WAKE_OUTOutReserved: wake the host on a modem eventOptionalNot used today
ANTRFIridium L-band antenna connectionYesn/a

Electrical

  • Absolute maximum supply voltagePublished at Rev AComing soon
  • Recommended supply voltage4.5 to 5.5 V, 5.0 V typical (proposed; not a released rating)Target
  • Logic levels3.3 V CMOS (proposed); 5 V tolerance not establishedTarget
  • Current, disabledPublished at Rev AComing soon
  • Current, idlePublished at Rev AComing soon
  • Current, transmit (peak, average)Published at Rev AComing soon
  • Brown-out ride-throughStored energy to finish a clean shutdownTarget

Timing

  • t_BOOT: ENABLE high to BOOTED highPublished at Rev A. SDK timeout default 30 sComing soon
  • t_DOWN: ENABLE low to BOOTED lowPublished at Rev A. SDK timeout default 30 sComing soon
  • t_VIN: supply stable to ENABLE allowedPublished at Rev AComing soon
  • t_UART: BOOTED high to first commandPublished at Rev AComing soon

RF

  • Frequency1616 to 1626.5 MHz (Iridium L-band)Defined
  • PolarizationRight-hand circularDefined
  • Impedance50 ohm nominal (proposed)Target
  • RF connectorPublished at Rev AComing soon
  • Maximum conducted output powerPublished at Rev AComing soon
  • Receive sensitivityPublished at Rev AComing soon
  • Antenna optionsExternal Iridium antenna options under review; approved configurations to followIn development
  • GNSS antennaAntenna configuration and RF qualification pendingIn development

Mechanical

  • Form factorBoard-level module with header-style host interfaceDefined
  • Dimensions and massPublished with the outline drawingComing soon
  • MountingBoard envelope, mounting and connector positions not approvedIn development
  • Operating temperature-40 to +85 °C (proposed)Target
  • Storage temperature and humidityPublished at Rev AComing soon
  • Vibration and shockPlanned against IEC 60068Coming soon
  • Ingress protectionBare board: none. Your enclosure sets the IP ratingDefined
  • Conformal coatingOption under evaluationComing soon

Compliance

  • Iridium approvalPlanned at gate G4 for each supported configurationComing soon
  • Regional approvalsMarkets under assessment: US, Canada, EU, UK, Australia and New Zealand. Scope confirmed with the test laboratory at G4Target
  • Certificates and approved antennasPublished as each approval is issuedComing soon
  • End-product obligationsDocumented with the issued module approvalsComing soon
  • RoHS and REACHDesign requirementsTarget
  • Manufacturing qualityIPC-A-610 Class 2, IPC J-STD-001, IPC-6012Target
  • Per-unit testAutomated functional test, power sequencing and UART loopbackTarget

Preliminary datasheet BEAR-DS-9704 P1. Engineering review is in progress; proposed supply ratings and board dimensions await verification. Specifications may change. Values marked Coming soon are published at Rev A. Directions are relative to the module.

Signal list (CSV)BOM template (CSV)
For embedded engineers

One UART, two control lines. Review before bring-up.

The host-independent design uses one UART at 230400 baud, two GPIO pins and a millisecond timer. Ports are validated individually. Logic thresholds, connector ratings and safe unpowered-host isolation remain open; review both sides before wiring. Do not connect 5 V logic directly.

Host connections

  • GPIO outputENABLEHold low until your supply is stable
  • GPIO inputBOOTEDDo not use the UART until high
  • UART TXRXDCross-over: your TX goes to module RXD
  • UART RXTXDYour RX comes from module TXD
  • GroundGNDCommon ground is required
  • SupplyVINUse reviewed supply limits; proposed ratings await verification

Worked example: MSP430F169 test bench

  • P1.0TS_F169_ENABLE outputENABLE
  • P1.1TS_F169_BOOTED inputBOOTED
  • P3.6 (UTXD1)USART1 transmitRXD
  • P3.7 (URXD1)USART1 receiveTXD
  • P3.4 (UTXD0)Bench checkout console, 115200 8N1; enabled in bench orderUSB-serial

Uses an external 8 MHz crystal on XT2. The internal oscillator is not accurate enough for 230400 baud. Pins are test-bench defaults you can override at compile time. The interface stays inactive unless crystal startup completes. The console uses P3.4 TX; P3.5 RX is not needed for checkout. Optional peripherals need a separately reviewed transport.

Power sequencing

ENABLE is the host output; BOOTED is the module response. BOOTED high allows UART setup, but messaging waits for the protocol handshake. During shutdown the SDK isolates UART, lowers ENABLE and confirms BOOTED low before reporting stopped. VIN remains under host control.

Hold inputs low. Before power, hold ENABLE low and keep the UART pins at high impedance or low to prevent back-powering. The host controls VIN; the SDK does not switch the supply.

SDK state: TS_OFF

VIN
Absent
ENABLE
Low
BOOTED
Low
UART
Isolated

This walkthrough shows a normal cycle, not a live device. Keep calling ts_bear_poll(). If boot times out while BOOTED is low, TS_FAULT_HOLD isolates UART and retains ENABLE; keep power applied and continue polling. A late BOOTED rise lets the SDK lower ENABLE and wait for BOOTED low. Do not cut power or reinitialize to bypass the hold; a stuck signal needs a reviewed hardware recovery procedure. A shutdown timeout is not confirmation that power may be removed.

Complete start-up and shutdown reference

Start-up

  1. Hold inputs low. Before power, hold ENABLE low and keep the UART pins at high impedance or low to prevent back-powering. The host controls VIN; the SDK does not switch the supply.
  2. Apply VIN. Apply a reviewed supply with ENABLE still low. Wait for it to be stable and confirm BOOTED is low. ts_bear_start() refuses to start while BOOTED is high.
  3. Drive ENABLE high. Call ts_bear_start(). The SDK isolates UART, then the platform raises ENABLE. The driver enters TS_BOOTING; BOOTED is still low.
  4. Wait for BOOTED. Keep polling in TS_BOOTING with ENABLE high and UART isolated. BOOTED stays low until the modem reports boot completion. The default boot timeout is 30 s; it is not permission to cut power.
  5. BOOTED high: start handshake. When polling observes BOOTED high, the SDK enables UART and queries apiVersion. It then selects the API and internal SIM as needed and checks or sets the active operational state. BOOTED high alone does not mean READY.
  6. Ready for messaging. Only after the protocol handshake succeeds does the SDK enter TS_READY and emit TS_EVENT_READY. The default configuration then queries the IMEI; let that query finish before sending or requesting shutdown.

Shutdown

  1. Request inactive state. Call ts_bear_shutdown() from TS_READY after outstanding queries and received messages are handled. A busy result means shutdown has not started. The SDK requests operationalState inactive and waits for acknowledgement, keeping ENABLE high and UART active.
  2. Isolate UART after acknowledgement. After a successful inactive-state reply, the SDK disables UART first. The F169 port makes its UART pins inputs. ENABLE is still high at this point; the next action occurs in the same SDK call.
  3. Drive ENABLE low. With UART already isolated, the platform lowers ENABLE. The SDK enters TS_POWERING_DOWN while BOOTED remains high.
  4. Wait for BOOTED low. Keep VIN applied and continue polling. BOOTED is still high while the modem shuts down. Do not remove power or start another cycle yet.
  5. Confirm BOOTED low. When polling observes BOOTED low, the SDK enters TS_OFF and emits TS_EVENT_STOPPED. UART is already isolated and ENABLE stays low. A timeout does not emit this confirmation.
  6. Remove VIN (optional). After TS_EVENT_STOPPED confirms shutdown with BOOTED low, the host may remove VIN. The SDK does not switch VIN itself. Keep module-facing pins at high impedance or low.

Bring-up checklist

  1. 1Review the preliminary wiring and power requirements first; supply ratings and connector details await verification.
  2. 2Connect the antenna. Never enable the module without an antenna or matched load.
  3. 3Build and run the SDK host tests to confirm your toolchain.
  4. 4Use the MSP430F169 bench order and CCS project, or implement the seven ts_platform_t callbacks for your reviewed host port.
  5. 5Check ts_bear_start() succeeds, then keep polling: ENABLE rises, BOOTED rises, UART starts, and the protocol handshake completes before TS_EVENT_READY.
  6. 6Read the IMEI from TS_EVENT_IMEI. The F169 checkout console reports diagnostics and calculator/activation links.
  7. 7Size your plan, activate with the IMEI, and freeze a bench order with the issued topic. Topic zero blocks sends.
  8. 8With reviewed hardware and a clear sky view, send an identified bench message and wait for TS_EVENT_MO_DELIVERED; satellite/backend validation is still pending.
  9. 9Handle pending queries and received messages, check ts_bear_shutdown() succeeds, then poll until TS_EVENT_STOPPED before removing power. A busy result or timeout is not shutdown confirmation.

Duty-cycled by design

The module is the largest load on a battery board, so keep it off between reports: start, send, confirm delivery, shut down. Use events, not fixed delays, because delivery time depends on satellite visibility.

ts_bear_poll(&bear);               /* every few ms: does all the work */
switch (ts_bear_state(&bear)) {
case TS_READY: /* send once, wait for TS_EVENT_MO_DELIVERED */ break;
case TS_OFF:   /* remove VIN only after STOPPED confirms shutdown */ break;
case TS_FAULT: /* report error; restart requires BOOTED low */ break;
case TS_FAULT_HOLD:
    /* report fault; keep polling, do not cut power or reinitialize */
    break;
default:       break;
}
Open-source firmware

The Telemetry Station SDK.

A portable C99 driver for the 9704, MIT licensed, with a hardware abstraction layer you implement in seven functions. It is not tied to the BEAR Module, so use it on any Iridium 9704 device.

View on GitHub (opens in a new tab)Open the Payload Optimizer
Language
Portable C99 host library, no heap, nonblocking
License
MIT
Status
Alpha; software validation documented, hardware validation pending
Reference port
TI MSP430F169; template for other MCUs
Testing
100% line and branch test coverage in software; not hardware qualification
Delivery
Reports accepted and delivered separately; never auto-resends

Design your message in the free Payload Optimizer, download the SDK export, and connect it in one file. The checked-in example already uses a generated Certus codec. The F169 checkout reports the IMEI and calculator/activation links.

SDK validation on BEAR Module engineering units is planned at gate G2.

Testing with third-party 9704 development hardware you already own? The repository includes an independent example (opens in a new tab) that sends its messages to Telemetry Station. That hardware is not a Pacific Gyre product, and the example is separate from the BEAR Module.

  • Flash-and-go bench checkout

    A CCS project and serial console guide connection checks, IMEI readout and delivery diagnostics on an external MSP430F169 host. You can run connection checks without an account; sending requires an activated topic. The example uses sample data for bench evaluation.

  • Generated payload codec

    The example uses a real Payload Optimizer export. Design your fields, download the C encoder and decoder, and connect them to the SDK. Keep the matching schema with your backend so readings decode consistently.

  • Optional GNSS integration

    An optional GNSS API supports time-bounded position acquisition through host-supplied transport and power callbacks. The default bench example does not acquire positions. Receiver, antenna and payload integration need separate review and validation.

  • Conservative fault recovery

    A boot timeout with BOOTED low holds ENABLE and isolates UART in TS_FAULT_HOLD. Keep polling; do not reinitialize to bypass the hold. A stuck signal needs reviewed hardware recovery and may consume power indefinitely. Timed-out messages have unknown delivery status and are never automatically resent.

F169 checkout guide
Development status · Updated November 3, 2026

Developed in the open, gate by gate.

BEAR Module 9704 follows standard hardware development gates with published exit criteria. We share what is done, what remains and how we will verify it, so you can plan your own program with confidence.

Target sales availability
April 1, 2027Tentative
Current stage
G1 · Design
Design review and validation in progress
Release checklist
7 of 42 complete

Tentative target, not a confirmed release date. Availability depends on hardware validation, applicable regulatory and Iridium approvals, and production readiness. Dates for the remaining milestones and evaluation kits are published once confirmed.

  1. Concept

    Product scope and architecture defined

    Complete

  2. G1Design

    Detailed hardware design and preliminary interface specifications

    In progress

  3. G2Engineering validation (EVT)

    BEAR Module engineering units demonstrated with the SDK

    Planned

  4. G3Design validation (DVT)

    Electrical, RF, environmental and host compatibility verified

    Planned

  5. G4Certification

    Applicable approvals for supported regions and configurations

    Planned

  6. G5Production validation (PVT)

    Production build, unit testing and traceability validated

    Planned

  7. G6General availability

    Orderable products, released documentation and customer support

    Tentative target: April 2027

Latest development progress

  • Hardware design in progress

    Schematic capture and PCB layout have started and are in review. The design is not yet fabrication-ready. G1 remains in progress; engineering validation and later gates are still planned.

  • SDK ready for bench evaluation

    The alpha SDK includes software tests with 100% line and branch coverage and a flash-and-go MSP430F169 checkout that reports each step on the serial console. Validation on BEAR hardware is pending and planned at G2. Software test coverage does not establish hardware qualification.

R&D and release checklist

Checked items are documented or available today. Unchecked items are the remaining release deliverables. A defined interface does not mean hardware testing is complete.

BEAR-RD-9704 Rev P2 (opens in a new tab)
Gate G0–G1

Product definition

In progress · 7 of 8
  • Iridium 9704 module and its remote sensing and OEM applications described in the product brief (done)
  • Host-independent architecture with an external customer MCU described (done)
  • Signal functions, 230400 baud 8N1 UART and ENABLE/BOOTED handshake defined (done)
  • Input protection, regulation, burst-energy storage and sequencing functions described (done)
  • Preliminary datasheet and requirements with verification methods published (done)
  • Portable C99 alpha SDK, simulated-modem tests and MSP430F169 reference port published (done)
  • Preliminary design inputs, BOM template and manufacturing overview published (done)
  • Launch configurations, supported regions and evaluation-kit contents finalized (remaining)
Gate G1

Detailed design

Remaining · 0 of 6
  • Input-voltage range, source requirements, burst-energy storage and protection finalized (remaining)
  • Host connector, pin assignments, logic thresholds and absolute ratings specified (remaining)
  • Antenna and RF configurations and integration constraints specified (remaining)
  • Dimensions, mounting, host footprint and thermal/environmental limits specified (remaining)
  • Component-level schematic, PCB layout and populated BOM completed (remaining)
  • Rev P2 preliminary datasheet with updated design targets (remaining)
Gate G2

Engineering validation

Remaining · 0 of 5
  • BEAR Module engineering units built and brought up (remaining)
  • Power rails, inrush, transmit bursts, thermal and power-loss behavior tested (remaining)
  • Sequencing, UART, IMEI readout, timing and disabled-state current tested (remaining)
  • SDK send, receive, delivery reporting and safe shutdown demonstrated on BEAR Module hardware (remaining)
  • End-to-end activation, payload delivery and decoding demonstrated (remaining)
Gate G3

Design validation

Remaining · 0 of 6
  • Electrical ratings, current, timing and thermal derating characterized (remaining)
  • RF performance verified for each supported antenna configuration (remaining)
  • Temperature, humidity, shock, vibration and reliability testing completed (remaining)
  • EMC, ESD, immunity and safety pre-compliance testing completed (remaining)
  • Host and SDK compatibility verified with tested platform and toolchain versions (remaining)
  • Requirements verified and representative field trials completed (remaining)
Gate G4

Certification and compliance

Remaining · 0 of 4
  • Standards and approval scope confirmed for each market and configuration (remaining)
  • Regulatory and Iridium approvals completed, with certificates and approved antennas (remaining)
  • Material compliance, labeling, country of origin and export information available (remaining)
  • Module approvals and end-product obligations documented for customers (remaining)
Gate G5

Production readiness

Remaining · 0 of 6
  • Production-intent pilot build with validated assembly quality, yield and test coverage (remaining)
  • Automated per-unit test validated, including sequencing, modem link and IMEI readout (remaining)
  • Serial and lot traceability linked to IMEI, revision and test results (remaining)
  • Production configuration matches the qualified design and approvals (remaining)
  • Packaging, labeling, production supply and fulfillment ready (remaining)
  • Released schematic, PCB source, fabrication files, BOM and mechanical models (remaining)
Gate G6

Customer release

Remaining · 0 of 7
  • Rev A datasheet with verified ratings, timing, pinout and mechanical data (remaining)
  • Tested Arduino, STM32 and Raspberry Pi quickstarts, sample decoders and test vectors (remaining)
  • SDK release baseline, compatibility and release notes (remaining)
  • Part numbers, kit contents, pricing, lead times and evaluation-kit dates (remaining)
  • Sales, support, lifecycle and change-notification terms (remaining)
  • Product status page and approved service-level terms (remaining)
  • Validation, approvals and production readiness complete; sales availability confirmed (remaining)

Inside the G1 design: functional architecture

The conceptual connections between the module's functional blocks, with the design inputs still open on each. Select a connection to see its function and what remains to be defined. This is design intent, not an electrical netlist or released specification.

Block connections (CSV) (opens in a new tab)Initial design basis (opens in a new tab)Gate exit criteria (opens in a new tab)
From sensor to insight, in 5 minutes

Plan and activate before the hardware arrives.

Every BEAR Module carries its IMEI, so you can size your plan and activate on Telemetry Station while your firmware is still in progress. The Telemetry Station workflow is not limited to the BEAR Module: any eligible Iridium modem with an IMEI works.

  1. Step 1

    Optimize

    Structure a compact payload and generate your encoder. Free.

    Payload Optimizer →
  2. Step 2

    Budget

    Enter bytes per message and messages per day to see your airtime in credits.

    Certus calculator →
  3. Step 3

    Activate

    Fund your account, enter the IMEI and your data is ready to access.

    Activate a device →

Messages are stored for up to 5 years at no extra cost, and you can monitor device locations and download raw telemetry in the dashboard or through the API.

Already own a modem?

Activate any eligible Iridium device on Telemetry Station.

The BEAR Module is a supporting product, not a requirement. If you already use one of these, or choose it instead, you can still activate it here for faster activation, better rates and easier data access.

Product and company names are trademarks of their respective owners and appear for compatibility information only. Eligibility is confirmed from the IMEI during activation.

Activate a Certus deviceActivate an SBD deviceHow activation works
Pre-order inquiry

Reserve your BEAR Module 9704.

Estimated target price $259 per module. Ships from California, USA. Tell us what you need and we will reply with pricing, lead time and shipping. No payment is taken.

Add-ons (estimates)

  • Iridium antenna
    External Iridium antenna option under review. Approved configurations and installation requirements will be confirmed after qualification.
    from $89
    Estimate, per unit
  • GNSS module
    Position and time option under evaluation. Receiver, antenna, power and host-interface details will be confirmed after review and validation.
    from $49
    Estimate, per unit
  • Microcontroller with firmware pre-flashed
    External reference host board running the SDK bench checkout. Topic zero skips sends; activated topic, reviewed wiring and application integration are required. Not a production sensor application.
    from $199
    Estimate, per unit; quoted by configuration

Order path

  • Evaluation (1 to 4 units)
    Bench testing with the SDK.
  • Pilot (5 to 99 units)
    Field trials with a stable configuration.
  • Production (100+ units)
    Volume pricing and lot traceability.

Part numbers: BEAR-9704-EVK (evaluation kit), BEAR-9704-xxx (production configurations). Each module ships in ESD-protective packaging with its IMEI on the label.

Add-ons
Custom engineering

Skip the build. We will engineer it with you.

Pacific Gyre designs oceanographic instruments with the same stack: embedded firmware, sensor integration, satellite communications and cloud infrastructure. We can design and integrate custom sensors, or build your whole product so you do not have to build in house.

Projects are quoted one by one. Tell us your measurement, power and deployment constraints and we will scope it with you.

Discuss a project

  • Custom sensor design and integration

    Select, interface and calibrate sensors for your measurement, then integrate them with the module.

  • Embedded firmware

    Microcontroller firmware for acquisition, power management and Iridium modem integration, built on the open SDK.

  • Full product builds

    From schematic to deployable instrument, with manufacturing partners, so you do not build in house.

  • Cloud data and integrations

    Iridium DirectIP, CloudConnect and Globalstar ingestion, redundant pipelines, APIs and dashboards on AWS and Azure.

  • Deployment support

    Firmware, connectivity and data integration support through your full R&D cycle.

Documentation

Everything an engineer and a buyer need.

Preliminary engineering documents are public and open source. The Rev A datasheet, schematics, layout, mechanical drawings and certificates are added here as each milestone is released.

Telemetry Station SDK on GitHub (opens in a new tab)Development status
FAQ

Questions buyers and engineers ask.

Is the BEAR Module 9704 available to buy today?

Not yet. The design is in gate G1. Our target for sales availability is April 1, 2027. That date is tentative, not confirmed, and depends on hardware validation, approvals and production readiness. Evaluation-kit dates are published once build and supply are confirmed. Pre-order inquiries are open and no payment is taken.

What will it cost?

The estimated target price is $259 per module. Antenna, GNSS and pre-flashed microcontroller add-ons are listed with estimates. Final pricing, lead times and terms are published at general availability and confirmed in your written quote.

Where does it ship from?

California, USA. Export classification (ECCN, HS code) is published with ordering information.

Do I have to use Telemetry Station with the module?

No. You can use the BEAR Module with other data services. The workflow we design, document and support end to end is Telemetry Station: size your plan in the calculator, activate with the IMEI, and your data is ready.

Can I activate a device that is not a BEAR Module?

Yes. Any eligible Iridium SBD or Certus modem with an IMEI can be activated on Telemetry Station. Eligibility is confirmed from the IMEI during activation.

Which microcontrollers work?

BEAR is designed to be host-independent: one UART at 230400 baud, two GPIO pins and a millisecond timer. MSP430F169 is the first external reference host, not an onboard MCU or a requirement. Other MCU ports are intended and must be validated individually; electrical limits and host isolation still require review.

Does the GNSS option include a receiver and antenna today?

The GNSS option is under evaluation, not a released configuration. Receiver, antenna, power and host-interface details will be published after review and validation. The SDK includes an optional GNSS API, but the default bench example does not acquire positions. Your application must explicitly encode any position fields in its payload.

Which Iridium antenna is planned?

External Iridium antenna options are under review. Approved antennas and installation requirements will be published as qualification is completed. GNSS support requires its own antenna review; an antenna approval does not establish BEAR system certification.

Do I need a Certus calculator or an SBD one?

The 9704 runs on Iridium Certus, so use the Certus calculator and the Certus activation flow.

Is the module certified?

Not yet. Iridium and regulatory approvals are planned at gate G4. Markets under assessment include the United States, Canada, the EU, the UK, Australia and New Zealand, and the exact scope is confirmed with the test laboratory. Certificates, approved antennas and any end-product obligations are published as approvals are issued.

Why are some specifications marked Coming soon?

We publish a value as final only once it is verified on real hardware. Defined values are product-level design decisions, Target values are proposed design intent, and Coming soon values are filled in as each gate completes. The development status section shows where the design is today.

Can I start before the module ships?

Yes. Start with the portable host SDK, simulated-modem demo, MSP430F169 bench checkout and generated Payload Optimizer codec. Validation on BEAR hardware is pending. If you already own an eligible Iridium modem, you can activate it on Telemetry Station today. The repository also includes a separate third-party 9704 example.

I am not an embedded engineer. Can I still use it?

Yes. Pacific Gyre can design the sensor, firmware and full instrument for you, or help your team through integration. Contact us with your measurement and deployment, and we will suggest the simplest path.

Is there a warranty?

No. The BEAR Module is an engineering component sold as-is, without a hardware warranty, and sales are final once a module ships. Pre-order inquiries take no payment, and release dates are estimates, not commitments. Testing and certifying your end product remain your responsibility. See our Terms & Conditions for full details.