INS Manager (Web and Desktop)

Configuration, monitoring and log analysis of Advanced Navigation Inertial Navigation System (INS) products is done using one of our INS Manager products, or directly via API calls:

  • INS Manager - Web provides a web user interface, accessed via a web browser, which connects via ethernet to a web server running on the INS.

  • INS Manager - Desktop is a java based desktop application, which connects to the INS via a serial or ethernet cable.

  • Direct API calls using Advanced Navigation Packet Protocol (Using ANPP) .

What’s the difference between Desktop and Web Interfaces?

INS Manager - Web and INS Manager - Desktop provide a very similar look-and-feel and offer most of the same features, but they are technically two different products. The following table summarizes the differences.

Feature INS Manager - Desktop INS Manager - Web
Availability All INSs (No Subsea) Most INSs with ethernet (Subsea)
Ease of installation Java desktop installation Zero installation, browser based
Connection Serial / Ethernet Ethernet (Wifi for Hydrus)
Majority of functions Good Good
High bandwidth data Good Network constrained
Download logs No Yes
Convert logs Yes No

Summary of differences between INS Manager and web interfaces.

Which products have hidden pages?

The interface dynamically hides pages that are not relevant to the connected INS.

Notably, products without an internal or externally connected GNSS receiver will not have access to GNSS specific pages.

Which products support Desktop and Web interfaces?

The following table describes which Advanced Navigation products support the INS Manager Desktop and Web interfaces.

Product INS Manager - Desktop? INS Manager - Web? Internal Logging?
Boreas 50/70/90 Yes Yes Yes
Certus / Certus Evo Yes Yes Yes
Certus Mini Yes No No
Motus Yes No No
GNSS Compass Yes Yes No
Hydrus No Yes (via WiFi) No
Subsonus No Yes No
Subsonus Tag No No (Uses mobile app + bluetooth) No
Legacy Products  
Spatial Yes No No
Spatial Dual Yes No No
Orientus Yes No No
Spatial FOG Yes No No
Spatial FOG Dual Yes No No

Products which support INS Manager and web interfaces.

Installing INS Manager - Desktop

This section is applicable to the desktop variant of INS Manager. Check if the web interface is easier for you.

Note: The INS Manager Desktop is only available for systems with x64 and ARM architectures.

Note: The older Java version 11 is required by INS Manager Desktop.

  • Install the latest version of Java 11 from Adoptium, selecting the correct operating system and architecture for your computer. Adoptium JRE 11 is the recommended Java installer to be used on all platforms.
  • Download INS Manager Desktop from the Advanced Navigation website.
  • Double click the INS Manager Desktop icon on your computer to start the application.
  • Connect to the INS, following instructions in the following section: Using INS Manager.

Troubleshooting

Symptom Likely Cause Resolution
The INS Manager Desktop application fails to launch or start. A 32-bit version of the Java Runtime Environment (JRE) is installed on a 64-bit operating system, causing an architecture mismatch execution failure. Uninstall the existing 32-bit Java version from your system and install a compatible 64-bit version.
Cannot view INS Manager - Web page (such as http://boreas.local ) for ethernet enabled units Active internet connectivity is unavailable. Verify the local network internet connection status and ensure routing endpoints are clear.
The INS Manager - Java Desktop fails to discover or list any connected network devices.
Active internet connectivity is unavailable. Verify the local network internet connection status and ensure routing endpoints are clear.
An explicit Inbound block configuration rule exists inside Windows Defender Firewall against INS Manager Desktop, or AdNav INS Studio or java.
Because Windows firewall priority rules dictate that an active "Block" action immediately supersedes an active "Allow" rule, all network discovery traffic (such as UDP multicast/broadcasts or TCP polling) is blocked.
  1. Open Windows Defender Firewall with Advanced Security on your laptop.
  2. Navigate to the Inbound Rules pane in the left-hand column.
  3. Locate the offending rule and change from "Block" to "Allow".
  4. Relaunch the application.
The INS Manager - Java Desktop cannot see the INS unit via a serial connection. Serial or USB communication settings (COM interface, wiring protocol, or data rate) are misconfigured or experiencing connectivity dropouts.
  • Ensure the physical RS232 / RS422 hardware switch toggle matches the required network configuration mode.
    The default hardware mode is RS422.
  • Verify the targeted COM port assignment. If ambiguous, cycle connection stability by unplugging and re-inserting the physical USB connector to re-initialize hardware handshake rules.
  • Confirm that the application data transmission baud rate configuration matches the source device transmission specification.
    The factory default is 115200 bps.
Data packet loss occurs when running the INS at very high data rates. High driver latency within the FTDI USB-to-serial communication pipeline leads to buffer overruns and dropped telemetry frames.

In the INS Manager's Advanced Settings, reduce the Latency Timer to 1 ms.