HYPACK
HYPACK is a professional hydrographic survey software suite developed by Xylem, used worldwide for planning, collecting, processing, and analyzing marine survey data. HYPACK includes a dedicated NTRIP Output (NTRIPOUT) driver that receives RTK corrections from an NTRIP caster like RTKdata.com and forwards them to the survey vessel's GNSS receiver over a network or serial connection, enabling centimeter-level positioning for bathymetric surveys, dredging operations, and marine construction.
Download / Purchase: HYPACK by Xylem (commercial license required — contact Xylem for pricing; lease options available)
Key capabilities
Platform
Windows (desktop/laptop aboard survey vessel)
Cost
Commercial license (contact Xylem for pricing). Lease options available with up to 85% of lease price applicable toward full purchase.
NTRIP support
Built-in NTRIPOUT driver — dedicated NTRIP client that forwards corrections to GPS receiver
NTRIP version
V1 and V2 (checkbox to advertise as NTRIP V2 client)
Correction delivery
Network (TCP/IP) or shared serial port with GPS driver
Mock location relay
Not applicable — HYPACK receives corrected positions from the GNSS receiver after corrections are applied
Typical use
Bathymetric surveys, dredging guidance, marine construction positioning
Requirements
Windows PC or tablet running HYPACK (current version recommended)
GNSS receiver capable of accepting RTCM3 corrections (e.g., Trimble, Hemisphere, u-blox, SBG, or integrated units like CEE HydroSystems CEESCOPE)
Internet connection on the survey vessel (cellular modem, Wi-Fi, or satellite link)
Network or serial connection between the HYPACK PC and the GNSS receiver
Active RTKdata.com account with RTK credentials
Don't have an RTKdata.com account yet? Start 30-day Free Trial or View Pricing
Step-by-step setup
Add the NTRIP Output driver in HYPACK Hardware
Open HYPACK and go to Preparation > Hardware (or Hardware Setup).
In the Hardware configuration window, click on your survey vessel.
Under the Devices tab, click Add Device.
From the driver list, select NTRIPOUT (the NTRIP Output driver).
If you do not see NTRIPOUT in the list, click Rescan Driver List to refresh available drivers.
The NTRIPOUT driver will be added to your hardware configuration.
The NTRIPOUT driver is a standalone driver dedicated to receiving NTRIP corrections and forwarding them to a GPS receiver. It replaces the older NTRIP tab that existed inside the GPS.DLL driver.
Configure the NTRIP connection settings
Double-click the NTRIPOUT driver to open its settings dialog.
Enter the NTRIP caster connection details:
Caster Address / Host:
rtk.rtkdata.comIP Fallback:
13.56.117.10Port:
2101Username / Password: From RTK Credentials in the internal dashboard (not website login)
Mountpoint (ALL CAPS):
AUTO
Caster Address / Host:
eu.rtkdata.comIP Fallback:
3.73.41.96Port:
2101Username / Password: From RTK Credentials in the internal dashboard (not website login)
Mountpoint (ALL CAPS):
AUTO
Caster Address / Host:
aus.rtkdata.comIP Fallback:
54.206.56.130Port:
2101Username / Password: From RTK Credentials in the internal dashboard (not website login)
Mountpoint (ALL CAPS):
AUTO
If available, check "Advertise as NTRIP Ver. 2 Client" to use the newer NTRIP V2 protocol (optional — RTKdata.com supports both V1 and V2).
Ensure the driver is configured to send GGA at 1 Hz — this is typically the default. RTKdata.com requires GGA to generate VRS corrections.
GGA output must be enabled at 1 Hz. Without GGA, RTKdata.com cannot determine your vessel's position and cannot compute corrections. The correction stream will not deliver usable data.
Configure the correction output to the GNSS receiver
The NTRIPOUT driver receives RTCM3 corrections from the caster and must forward them to your GNSS receiver. Configure the output path based on your hardware setup:
Option A: Network (TCP/IP) — most common for modern setups
In the NTRIPOUT driver settings, set the output connection to Network Client TCP.
Enter the GNSS receiver's IP address and the TCP port for corrections input.
Example for CEE HydroSystems CEESCOPE: IP
192.168.2.2, Port3001For other receivers, consult your receiver's documentation for the corrections input port.
Option B: Serial port — for receivers connected via RS-232
The NTRIPOUT driver can share the same serial port as the GPS.DLL driver (the NTRIP.DLL shares the serial port with GPS.DLL).
Set the COM port and baud rate to match your GNSS receiver's serial connection.
Start sequence matters. For network connections, the GNSS receiver must be powered on and have acquired a position before starting the NTRIP driver. If the TCP socket cannot connect, the correction stream will not start. Suggested workflow: (1) Power on receiver, (2) Wait for satellite acquisition, (3) Start HYPACK survey with NTRIP driver.
Verify RTK Fix in HYPACK
Start a survey session in HYPACK.
The NTRIPOUT driver connects to RTKdata.com and begins receiving RTCM3 corrections.
Monitor the GPS device status in the HYPACK status bar or the Survey window:
The GPS quality indicator should progress from Autonomous > DGPS > Float > Fix.
Once RTK Fix is achieved, the corrected position is used for all survey data collection.
Check the correction age in the GPS status display. It should remain below 5 seconds. If correction age climbs steadily, the NTRIP connection may be dropping — verify internet connectivity.
Vertical reference (heights)
Heights from RTKdata.com are ellipsoidal. For hydrographic surveys, you typically need heights referenced to a chart datum or local vertical datum. Use HYPACK's Tide or RTK Tide module to apply tidal corrections, or convert ellipsoidal heights to your required vertical datum using a geoid model or local benchmark.
Troubleshooting
NTRIPOUT driver not in device list
Driver DLL missing or not scanned
Click Rescan Driver List in Hardware setup. Ensure HYPACK installation is complete.
TCP connection to receiver fails
Receiver not powered or wrong IP/port
Verify the receiver is on and has acquired a position. Check IP address and TCP port in receiver documentation.
NTRIP connects but no corrections reach receiver
Output path misconfigured
Verify the TCP or serial output settings match the receiver's correction input port.
Stuck on Float
GGA not being sent or baseline too long
Confirm GGA is sent at 1 Hz. Check RTKdata coverage for your survey area.
Mountpoint error
Wrong capitalization
Type AUTO in ALL CAPS.
Corrections drop during survey
Vessel cellular signal lost
Use a cellular modem with external antenna mounted high on the vessel. Consider a marine-grade 4G/LTE router.
GPS quality oscillates between Fix and Float
Marginal sky view or multipath
Ensure the GNSS antenna is mounted with a clear 360-degree sky view above the vessel superstructure. Avoid mounting near radar or communication antennas.
Tips for best results
Internet at sea is the biggest challenge. Invest in a quality marine cellular modem with external antenna. For offshore work beyond cellular range, consider Starlink Maritime or Iridium-based solutions.
The NTRIPOUT driver is separate from the GPS driver. This is by design — NTRIPOUT handles the correction stream while GPS.DLL reads the corrected position from the receiver. They can share a serial port if needed.
Data usage is minimal. RTK corrections use approximately 5–10 kbit/s, which is negligible even on metered satellite connections.
Test the full chain dockside before going to the survey site. Verify NTRIP connection, correction delivery to the receiver, and RTK Fix — all while you still have reliable internet.
HYPACK version matters. The standalone NTRIPOUT driver replaced the older NTRIP functionality embedded in GPS.DLL. Ensure you are running a current version of HYPACK for the best NTRIP support.
Last updated
Was this helpful?