# Software Beta Test Release

**URL:** <https://discuss.bluerobotics.com/t/software-beta-test-release/6799>\
**Category:** QGroundControl\
**Tags:** ardusub, ping, sitl, simulate, beta-testing\
**Created:** [February 3, 2020, 8:11pm UTC](https://discuss.bluerobotics.com/t/software-beta-test-release/6799 "2020-02-03T20:11:45Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![patrickelectric](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/patrickelectric/32/2162_2.png) [@patrickelectric](https://discuss.bluerobotics.com/u/patrickelectric)\
**Post date:** [February 3, 2020, 8:11pm UTC](https://discuss.bluerobotics.com/t/software-beta-test-release/6799/1 "2020-02-03T20:11:45Z")

</div>

Hello again Blue Buddies! We are almost ready for a new round of software updates! 🔥 🔥

For the last couple of months we have been working hard to improve our software stability, reliability and performance. Now we invite you, our community, to help us to push the ocean boundaries even further with beta testing! 🌊🌊

# What should a Beta Tester do ?

1. Update software to the last beta test version available
2. Report any issue or reproducible bugs
3. Propose changes that could help you
4. Share your experiences and thoughts with the community

 ![](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/7/790a5b9585e6404e62e886ddf5f6b6dd33cd8e3a.png "horizontal line")

# Versions:

## Companion 0.0.19

- New MAVLink to REST API
  - Now it’s possible to fetch MAVLink information via the web API interface
  - Check: [http://192.168.2.2:4777/mavlink](http://192.168.2.2:4777/mavlink)
  - [Documentation here](https://github.com/bluerobotics/ardusub-gitbook/blob/a7eb98683eacee59b89d350015ba47c3e8e3b9cd/operators-manual/companion-web.md#mavlink-rest-api)

- New Ping-Viewer integration
  - Our lovely Ping-Viewer now has new capabilities and features!

- Fix Ping1D firmware update via Companion web interface
- Improve underwater GPS integration stability
- Navigator board support

**Check our [upgrade process here](https://www.ardusub.com/operators-manual/companion-web.html#git).**

> P.S: Remember to select tag 0.0.19  
> P.S 2: Remember to set the default parameters in [http://192.168.2.2:2770/mavproxy](http://192.168.2.2:2770/mavproxy) after the update

## ArduSub 4.0

 ![gifresized](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/c/c385135803f75bba4f6ee5f6e69be29156b33a3e.gif)

- Over **10000 new commits** (catching up with other vehicles **4.0** releases).
- The Real Time Operating System (RTOS) is now **ChibiOs** instead of **NuttX**.
- Added a new option for [**automatic** detection of the **thrusters directions**](https://github.com/mavlink/qgc-user-guide/blob/e65149b86e1a5eade705606ce8cb0a857ea3d76c/en/SetupView/Motors_ardusub.md), making **setup easier**.
- Heavy frames can now roll/tilt to arbitrary attitudes (even **upside down** ).
- **Depth Hold** is now working with arbitrary attitudes.
- **Depth Hold** and **Stabilize** modes now hold the attitude at which they were enabled.
- **Roll-Pitch toggle** mode now used the inputs as rate targets instead of position targets.
- In **Roll-Pitch Toggle** mode, the Center Mount button now levels the ROV.
- Support **depth setpoints** via **MAVlink** in **Depth-Hold** mode.
- Support **attitude setpoints** via **MAVlink** in **Depth-Hold** and **Stabilize** modes.
- Support for setting **MAVLink** message **intervals**.
- Navigator board support.
- Many improvements to **SITL** (Software In The Loop simulator for developers) so its behavior better resembles that of a real ROV.

Your browser does not support the video element.

Your browser does not support the video element.

To update, first back up your parameters by [saving them to a file in QGroundControl](https://docs.qgroundcontrol.com/en/SetupView/Parameters.html#tools), and then follow the instructions for [updating ArduSub via the Companion](http://www.ardusub.com/operators-manual/software-update.html#via-companion) clicking **Beta** instead of **Stable**.

Some of the beta features in ArduSub require a new version of QGC to use. For a better experience and to be able to use the Automatic thruster direction detection feature, use [**this build of QGC**](https://ci.appveyor.com/api/buildjobs/854u10xslgj1ynf5/artifacts/QGroundControl-installer.exe).

## Ping-Viewer t2.0.6

- New Ping360 chart rotation
  - Ping360 chart will be rotated with BlueROV body frame
  - **Check the video!**

- Decrease Ping360 scan time
- Improve Ping360 chart and A-Scan resolution
- Better hardware compatibility, lower CPU and GPU usage
- Save previous manual connection configurations
- Fix Ping360 detection with multiple network interfaces

**Download the [new version here](https://github.com/bluerobotics/ping-viewer/releases/tag/t2.0.6).**

Your browser does not support the video element.

## Ping1D 3.28

- New automatic baud rate feature
  - Ping1D will configure [automatically with different baud rates](https://en.wikipedia.org/wiki/Automatic_baud_rate_detection). The baudrate can be changed without changing the firmware on the device.
  - Default baudrate is 115200

- Add [distance-simple](https://docs.bluerobotics.com/ping-protocol/pingmessage-ping1d/#1211-distance_simple) message in continuous request

**Get our [beta firmware release here](https://s3.amazonaws.com/downloads.bluerobotics.com/Ping1D/Ping-V3.28_auto.hex).**

Follow our [upgrade firmware instructions here](https://docs.bluerobotics.com/ping-viewer/firmware-update/), remember to select manual update.

---

<div class="post-metadata">

**Author:** ![patrickelectric](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/patrickelectric/32/2162_2.png) [@patrickelectric](https://discuss.bluerobotics.com/u/patrickelectric)\
**Post date:** [February 10, 2020, 4:09pm UTC](https://discuss.bluerobotics.com/t/software-beta-test-release/6799/2 "2020-02-10T16:09:26Z")

</div>

Pinned globally on February 10, 2020, 4:09pm UTC



---

<div class="post-metadata">

**Author:** ![JeanBenoit](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/jeanbenoit/32/4689_2.png) [@JeanBenoit](https://discuss.bluerobotics.com/u/JeanBenoit)\
**Post date:** [February 10, 2020, 6:44pm UTC](https://discuss.bluerobotics.com/t/software-beta-test-release/6799/3 "2020-02-10T18:44:57Z")

</div>

Yes !!! Very good news, i’m ready for tests !! Thanks

---

<div class="post-metadata">

**Author:** ![matt\_bathyscope](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/matt_bathyscope/32/5004_2.png) [@matt\_bathyscope](https://discuss.bluerobotics.com/u/matt_bathyscope)\
**Post date:** [February 11, 2020, 12:09am UTC](https://discuss.bluerobotics.com/t/software-beta-test-release/6799/4 "2020-02-11T00:09:48Z")

</div>

Where can I learn more about the Navigator board? I’m coming up empty searching for it but the code suggests its a Linux replacement for the PixHawk with an onboard IMU and (internal) pressure sensor.

---

<div class="post-metadata">

**Author:** ![patrickelectric](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/patrickelectric/32/2162_2.png) [@patrickelectric](https://discuss.bluerobotics.com/u/patrickelectric)\
**Post date:** [February 11, 2020, 12:11am UTC](https://discuss.bluerobotics.com/t/software-beta-test-release/6799/5 "2020-02-11T00:11:26Z")

</div>

Hi Matt,

This is something that will be released in the near future 😉

---

<div class="post-metadata">

**Author:** ![JeanBenoit](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/jeanbenoit/32/4689_2.png) [@JeanBenoit](https://discuss.bluerobotics.com/u/JeanBenoit)\
**Post date:** [February 11, 2020, 7:25pm UTC](https://discuss.bluerobotics.com/t/software-beta-test-release/6799/6 "2020-02-11T19:25:36Z")

</div>

Hi Patrick,  
I followed the update in order as explained but after putting Companion in 0.0.19 where should I redefine the default parameters before updating Ardusub (and before QGC following the order indicated)?  
Thanks

---

<div class="post-metadata">

**Author:** ![patrickelectric](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/patrickelectric/32/2162_2.png) [@patrickelectric](https://discuss.bluerobotics.com/u/patrickelectric)\
**Post date:** [February 12, 2020, 2:07pm UTC](https://discuss.bluerobotics.com/t/software-beta-test-release/6799/7 "2020-02-12T14:07:32Z")

</div>

Hi @JeanBenoit,

In companion section:  
The parameters are the ones in [/mavproxy](http://192.168.2.2:2770/mavproxy).  
Sorry if the instructions were not clear, I just did a small update, let me know if you have any further questions.

In ArduSub section:  
You should follow the instructions under the videos. Saving the parameters with QGroundControl and following the instructions to flash the parameters via companion.

---

<div class="post-metadata">

**Author:** ![JeanBenoit](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/jeanbenoit/32/4689_2.png) [@JeanBenoit](https://discuss.bluerobotics.com/u/JeanBenoit)\
**Post date:** [February 12, 2020, 6:32pm UTC](https://discuss.bluerobotics.com/t/software-beta-test-release/6799/8 "2020-02-12T18:32:16Z")

</div>

Hi @patrickelectric  
Perfect, all the updates are done now (Compagnon, Ardusub, Ping1D). I will do the sea tests tomorrow !!  
For the moment I test in the workshop …

- The depth from Ping1D displayed in the values (Rangefinder meters) works ??  
-The depth maintained with respect to the bottom with Ping1D ??
- The overlay of the values on the video works only if it is recorded in MP4 (not in MKV despite the creation of the .ass file) with VLC.

In the parameters:  
FRAM:

 ![image](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/7/778b22fe8bd6ff88b8c9d2d62a5a6f67e14d518b.png)

TUNING:

 ![image](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/d/d79771442428942eef0aa14d03749d5d775da88c.png)

MOTORS: Automatic motor direction detection. Stop at first

 ![image](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/b/b4b762b1c82742086ee46f5725744ca19e322ab5.png)

This is what I see this evening at the workshop. What should I do before going to sea tomorrow ??  
Thanks for your advice  
Jean Benoit

---

<div class="post-metadata">

**Author:** ![williangalvani](https://avatars.discourse-cdn.com/v4/letter/w/6f9a4e/32.png) [@williangalvani](https://discuss.bluerobotics.com/u/williangalvani)\
**Post date:** [February 12, 2020, 7:53pm UTC](https://discuss.bluerobotics.com/t/software-beta-test-release/6799/9 "2020-02-12T19:53:00Z")

</div>

Hi @JeanBenoit,

Thank you for reporting the issues!

> [@JeanBenoit](#):
>
> The depth from Ping1D displayed in the values (Rangefinder meters) works ??  
> -The depth maintained with respect to the bottom with Ping1D ??

These are next in my list.

> [@JeanBenoit](#):
>
> The overlay of the values on the video works only if it is recorded in MP4 (not in MKV despite the creation of the .ass file) with VLC.

I’ll look into it.  
Just did. It seems to be due to some architectural changes that are happening in QGC in order to properly support some very requested new features.  
I opened an [issue](https://github.com/mavlink/qgroundcontrol/issues/8321) to track this.

> [@JeanBenoit](#):
>
> FRAM:

This one is harmless, I’m looking into it, but don’t worry about it.

> [@JeanBenoit](#):
>
> TUNING:

The tuning page was trying to display the older page for 3.5 due to a [typo](https://github.com/mavlink/qgroundcontrol/pull/8320) (oops).

> [@JeanBenoit](#):
>
> MOTORS: Automatic motor direction detection. Stop at first

The automatic motor detection expects the ROV to be in the water, without water it won’t move and the IMU readings won’t be in the valid range, and that is why it fails.

I’ll update the post once I get a new QGC build and ping you.

---

<div class="post-metadata">

**Author:** ![JeanBenoit](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/jeanbenoit/32/4689_2.png) [@JeanBenoit](https://discuss.bluerobotics.com/u/JeanBenoit)\
**Post date:** [February 13, 2020, 12:41pm UTC](https://discuss.bluerobotics.com/t/software-beta-test-release/6799/10 "2020-02-13T12:41:50Z")

</div>

hI @williangalvani,  
I can use the BR2 to work like this while waiting for your update or well I come back to the stable versions ??  
Thanks

---

<div class="post-metadata">

**Author:** ![williangalvani](https://avatars.discourse-cdn.com/v4/letter/w/6f9a4e/32.png) [@williangalvani](https://discuss.bluerobotics.com/u/williangalvani)\
**Post date:** [February 13, 2020, 2:21pm UTC](https://discuss.bluerobotics.com/t/software-beta-test-release/6799/11 "2020-02-13T14:21:36Z")

</div>

Hi @JeanBenoit,

I wouldn’t take the chance of finding new bugs while using it on a professional setting, but ultimately that is up to you.

---

<div class="post-metadata">

**Author:** ![JeanBenoit](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/jeanbenoit/32/4689_2.png) [@JeanBenoit](https://discuss.bluerobotics.com/u/JeanBenoit)\
**Post date:** [February 13, 2020, 7:28pm UTC](https://discuss.bluerobotics.com/t/software-beta-test-release/6799/12 "2020-02-13T19:28:01Z")

</div>

@williangalvani,  
It is a pleasure to participate in the evolution of BR !! I try at sea as quickly as possible.

---

<div class="post-metadata">

**Author:** ![EspReSso](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/espresso/32/5133_2.png) [@EspReSso](https://discuss.bluerobotics.com/u/EspReSso)\
**Post date:** [February 16, 2020, 8:13pm UTC](https://discuss.bluerobotics.com/t/software-beta-test-release/6799/13 "2020-02-16T20:13:07Z")

</div>

![t2.0.6-error](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/e/e2a4c56f594a1c3acc04ed250f99c1cb495c6a90.jpeg)  
t2.0.6 with PING360 only displaying a pink square.

(Windows 10 Pro, Intel(R) HD Graphics 3000, AMD Radeon HD 7400M Series)

---

<div class="post-metadata">

**Author:** ![EspReSso](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/espresso/32/5133_2.png) [@EspReSso](https://discuss.bluerobotics.com/u/EspReSso)\
**Post date:** [February 16, 2020, 8:48pm UTC](https://discuss.bluerobotics.com/t/software-beta-test-release/6799/14 "2020-02-16T20:48:31Z")

</div>

Companion updated to 0.0.19.  
Companion updating for Ping1D firmware (to 3.28) was successful.  
Companion updated for ArduSub to 4.0.0(beta) required a manual change of flash\_px4.py to /dev/ttyACM0, then worked fine.  
Updated to posted QGroundControl, all appear operational in dry test thus far.  
Ping t2.0.6 gives the pink square, (so did t2.0.5), presently utilizing 2.0.4 official.

How do we turn on the overlay in recording?  
Is audio still no functional?

---

<div class="post-metadata">

**Author:** ![patrickelectric](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/patrickelectric/32/2162_2.png) [@patrickelectric](https://discuss.bluerobotics.com/u/patrickelectric)\
**Post date:** [February 16, 2020, 9:58pm UTC](https://discuss.bluerobotics.com/t/software-beta-test-release/6799/15 "2020-02-16T21:58:00Z")

</div>

Hi @EspReSso,

Thanks for your tests! Can you please share [ping-viewer GUI log](https://docs.bluerobotics.com/ping-viewer/logging-and-user-files/#gui-logs) of your test ?

---

<div class="post-metadata">

**Author:** ![EspReSso](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/espresso/32/5133_2.png) [@EspReSso](https://discuss.bluerobotics.com/u/EspReSso)\
**Post date:** [February 16, 2020, 10:02pm UTC](https://discuss.bluerobotics.com/t/software-beta-test-release/6799/16 "2020-02-16T22:02:57Z")

</div>

Sure thing @patrickelectric  
I had noticed the same thing a while back when I tested t2.0.5

[20200216-165939704.txt](https://discuss.bluerobotics.com/uploads/short-url/9fwV3xx46TpHBW9lUEcn6CT7EN.txt) (526.3 KB)

---

<div class="post-metadata">

**Author:** ![williangalvani](https://avatars.discourse-cdn.com/v4/letter/w/6f9a4e/32.png) [@williangalvani](https://discuss.bluerobotics.com/u/williangalvani)\
**Post date:** [February 18, 2020, 1:02am UTC](https://discuss.bluerobotics.com/t/software-beta-test-release/6799/18 "2020-02-18T01:02:44Z")

</div>

> [@EspReSso](#):
>
> How do we turn on the overlay in recording?

If you have the .ass files, which should be created automatically by latest QGC builds, all you need is a player able to play them, such as VLC.  
There’s a better explanation [here](https://docs.qgroundcontrol.com/en/FlyView/VideoOverlay.html).  
(Note that there is currently an [issue with .mkv files](https://github.com/mavlink/qgroundcontrol/issues/8321))

> [@EspReSso](#):
>
> Is audio still no functional?

Audio will likely have to wait for the current rework of the whole video system.

---

<div class="post-metadata">

**Author:** ![EspReSso](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/espresso/32/5133_2.png) [@EspReSso](https://discuss.bluerobotics.com/u/EspReSso)\
**Post date:** [February 18, 2020, 1:18am UTC](https://discuss.bluerobotics.com/t/software-beta-test-release/6799/19 "2020-02-18T01:18:46Z")

</div>

@williangalvani  
I was previously using QGC 3.5.6 and now changed to the one posted in the link in this thread (which does not show a version), but do not have the .ass files, is there something that needs to be configured in settings? (presently set to mp4).

Update: suddenly today it is creating the .ass files, and working! No idea what changed but overlay working.

---

<div class="post-metadata">

**Author:** ![JeanBenoit](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/jeanbenoit/32/4689_2.png) [@JeanBenoit](https://discuss.bluerobotics.com/u/JeanBenoit)\
**Post date:** [February 18, 2020, 1:30pm UTC](https://discuss.bluerobotics.com/t/software-beta-test-release/6799/20 "2020-02-18T13:30:25Z")

</div>

Hi, I don’t know why but QGC beta no longer starts on my computer. I reinstalled it’s OK now but the clamp no longer works. I tried everything … I just went back to QGC 3.5.2, Companion 0.0.18 and Ardusub 3.5.4 and the clamp still doesn’t work … and I have a job to do in the port … I am disappointed.  
A word of advice ??(even if I know there are problems with the gripper,hope that the new version will arrive, i until yesterday evening everything was fine !!)

---

<div class="post-metadata">

**Author:** ![williangalvani](https://avatars.discourse-cdn.com/v4/letter/w/6f9a4e/32.png) [@williangalvani](https://discuss.bluerobotics.com/u/williangalvani)\
**Post date:** [February 18, 2020, 1:48pm UTC](https://discuss.bluerobotics.com/t/software-beta-test-release/6799/21 "2020-02-18T13:48:27Z")

</div>

Hi Jean,

Your parameters were probably reset when you went back to 3.5.4, If you saved the parameters, restore then.

Also check if the joystick buttons are mapped properly (`servo_[number]_[min/max]_momentary`) and then check in the QGC inspector tab if the appropriate servo value is changing in SERVO\_OUTPUT\_RAW (servo\_3 in joystick is channel 11 IIRC).

[Next page](https://discuss.bluerobotics.com/t/software-beta-test-release/6799.md?page=2)
