Overview

The Hawk Pro NTN is the direct replacement for the Hawk Pro. It is designed to be almost identical in form and function, at the same or similar price, with a small number of hardware changes users should be aware of before migrating. All sensor integrations, I/O cards, and existing firmware from the Hawk Pro are carried forward into the Hawk Pro NTN.

What Does "NTN" Mean?

NTN stands for Non-Terrestrial Networks — referring to satellite connectivity. The Hawk Pro NTN uses an upgraded modem (nRF9151) that is capable of NTN/satellite communication. However, NTN connectivity is not available at launch and will be enabled in a future firmware update once the appropriate firmware from Nordic Semiconductor becomes available. In the meantime, both devices connect via LTE-M/NB-IoT cellular networks as normal.

Key Differences at a Glance

Hardware Changes in Detail

Modem Upgrade (nRF9160 → nRF9151)

The modem has been upgraded from the nRF9160 to the nRF9151. This is the hardware change that enables future NTN/satellite connectivity. For current deployments using LTE-M or NB-IoT, the behaviour is functionally identical. No configuration changes are required when migrating existing devices to the new hardware.

Offline Record Storage Reduced

Offline flash storage has been reduced. The Hawk Pro NTN can store approximately 36,000 records offline, compared to ~80,000 on the Hawk Pro. For most deployments this remains more than sufficient — at a 30-minute sample interval, this still represents over two years of offline records. Users with very high-frequency sampling requirements or extended connectivity outages should review whether this capacity meets their needs.

Accelerometer Removed

The onboard accelerometer has been removed from the Hawk Pro NTN. Although the accelerometer chip was physically present on the Hawk Pro PCB, it was never supported in firmware — meaning it was never accessible or usable in any configuration. No users have ever been able to use it, and no one is impacted by its removal.

Magnetic Activation

The Hawk Pro NTN introduces magnetic activation accessible from outside the housing — a new feature not present on the original Hawk Pro at all. This makes it easy to activate or interact with the device without opening the enclosure.

Power Management Changes

Charge Rate Switch Replaced by Firmware Control

The Hawk Pro had a physical charge rate switch on the PCB. On the Hawk Pro NTN, this has been removed and charge rate is now controlled via a firmware system parameter instead. This simplifies the hardware and allows charge rate to be adjusted remotely without physical access to the device.

Automatic Vbatt / Vext Detection

Power source detection is now automatic on the Hawk Pro NTN. The device detects whether it is running from the internal battery (Vbatt) or an external voltage source (Vext) and manages the charging state accordingly — no manual Device Manager configuration required. On the Hawk Pro, this required manual setup to avoid unnecessary parasitic drain when using D Cell battery packs.

UVLO Simplified

The Under-Voltage Lockout (UVLO) behaviour has been simplified on the Hawk Pro NTN, reducing configuration complexity for power-sensitive deployments.

What Stays the Same

All sensor integrations, plug-in I/O cards, and existing firmware from the Hawk Pro are fully supported on the Hawk Pro NTN. The physical form factor, IP68 housing, battery options, and cellular connectivity are unchanged. Existing workflows, platform integrations, and Device Manager configurations carry over directly.

Migrating from Hawk Pro to Hawk Pro NTN

The Hawk Pro NTN is designed as a drop-in replacement. Before migrating, consider the following:

• Offline storage: If your deployment relies on storing more than ~36,000 records offline, you will need to adjust your sampling interval or upload frequency.
• Charge rate: The physical charge rate switch is no longer present — ensure you are comfortable managing this via firmware instead.
• NTN connectivity: NTN/satellite capability is not active at launch. No action is required, but it will be enabled via a future firmware update.