> For the complete documentation index, see [llms.txt](https://docs.ceruleansonar.com/c/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ceruleansonar.com/c/sonarview/installation/blueos.md).

# BlueOS

The SonarView BlueOS Extension is recommended on uncrewed vessels (USV, ROV) for a few key reasons:

* SonarView's server **always** has a solid connection to the sonar. Packets are never dropped, even if you lose communications with the vehicle.
* Your telemety radio or communication link will not be used for raw sonar data, leaving more bandwidth for piloting. This will increase the usable range of a wireless link. 
* Your settings will be preserved across different computers or mobile devices
* Remote access to sonars over the internet is possible in this configuration

1. Navigate to BlueOS Extension Store 

   <figure><img src="/files/4FQlF3a8v7iHAaJp7KJT" alt=""><figcaption></figcaption></figure>
2. Select SonarView, and click Install&#x20;

   <figure><img src="/files/ilv4jnLNn4gcuNGiHUjt" alt=""><figcaption></figcaption></figure>
3. The container will download and start automatically. It will appear in the left sidebar when the process completes&#x20;

   <figure><img src="/files/AvVsu9GltQPaNE0tULVF" alt=""><figcaption></figcaption></figure>
4. Opening SonarView via the left sidebar will open it within the BlueOS UI Frame. SonarView can also run in an independent browser window by navigating to <http://blueos.local:7077>

   <figure><img src="/files/oZeZ1sNjflnwMTnSsWuS" alt=""><figcaption></figcaption></figure>

Usage

SonarView on BlueOS differs from the desktop app&#x20;

###

### Additional Options

Some more options are available by navigating to the BlueOS Extensions tab, and selecting "Installed" on the top.&#x20;

<figure><img src="/files/f99mNUdXw6ixBNZQemEt" alt=""><figcaption></figcaption></figure>

**View Logs** can be helpful in diagnosing issues and sharing info with support.&#x20;

**Edit** allows you to manually choose a version of SonarView or change the path for the logging directory in the host OS. You can see all the available tags for SonarView [here](https://hub.docker.com/repository/docker/nicknothom/sonarview/tags).&#x20;

<figure><img src="/files/udTVQlbTYkTBwjHJBzZa" alt="" width="271"><figcaption></figcaption></figure>

**Defaults:**

Extension Identifier: `ceruleansonar.sonarview`

Docker image: `nicknothom/sonarview`

Docker tag: `1.13.15`

Original Settings / Custom Settings:&#x20;

```
{
  "HostConfig": {
    "NetworkMode": "host",
    "Binds": [
      "/usr/blueos/userdata/SonarView:/userdata"
    ]
  }
}
```

**Steps to allow the Omniscan 3D to work in BlueOS (1.5.0-beta.26 and 27)**

1. SonarView's web interface must be accessed directly, it will not load by clicking "SonarView" in the BlueOS menu.
2. SonarView runs on port 7077, so on a stock BlueOS instance SonarView can be accessed at <http://192.168.2.2:7077/> . If hostname resolution is working, then <http://blueos.local:7077/> may also work.