Today’s new product is something we can’t weight to share! It’s one of the biggest capabilities we’ve added to the BlueROV2 yet!
The new BlueROV2 Heavy Configuration upgrades the BlueROV2 to have four vertical thrusters, providing some powerful new performance capabilities including six degree-of-freedom control, active stability control, and additional payload capacity! We’ve been planning this upgrade since before the BlueROV2 was originally launched, and because of that, every BlueROV2 that we’ve ever shipped has the mounting holes ready to upgrade to the BlueROV2 Heavy Configuration.
The four vertical thrusters are mounted on the outside of the frame and have a protective guard to prevent snagging on the tether or anything else. The void left by the original vertical thrusters is filled with an additional buoyancy foam block and fairing for additional stability while maintain a sleek design.
There’s a lot of cool things about this new configuration. It’s probably best explained by watching it in action. Check out the official new product video to see it in action!
The BlueROV2 Heavy Retrofit Kit includes everything you need to upgrade your existing or new BlueROV2 to the heavy configuration and we’ve got a clear set of instructions on how to do that.
The main components of the retrofit kit, the guards, foam, and fairings, are also available separately for anyone who’d like to upgrade piece by piece or wants to use them in another application. The BlueROV2 spare thrusters are also available separately. You can check out the parts below.
We’re excited to announce a new product today: the Thruster Commander! The Thruster Commander is a small control unit and accessories to make it as easy as possible to start using our thrusters. It’s the perfect test tool in the shop to get them up and running but it also has the capability to control multiple thrusters on a kayak, standup paddleboard, or just about any project you might have in mind!
Check out the new product video for a detailed explanation and to see it in action!
In addition to the control unit, the Thruster Commander includes two potentiometers and knobs that are used for input. There are two output channels and they can be controlled independently or they can be mixed together to provide smooth speed and steering control. Check out the new product video below for more information!
Happy Tuesday, friends! We’re excited to kick off 2018 with a couple additions to the Watertight Enclosure Series: optically clear domes for the 2″ Series and 3″ Series enclosures!
Dome shaped end caps can handle significantly more pressure for the same thickness as flat end caps. Both of these new domes are designed for extreme pressures – 900m for the 3″ Series and 1000+m for the 2″ Series! That means that these can both go just as deep or deeper than the 2″ Series Aluminum Tube and 3″ Series Aluminum Tube.
Domes are also ideal for use with cameras as they retain the original field of view of the camera compared to a flat end cap, which will reduce the field of view. These domes are both made from optically clear acrylic and won’t warp or distort your footage.
We’ve got one more new product to squeeze in for 2017! The new Fathom Slim Tether is a high performance tether cable designed specifically for ROVs and other subsea applications and optimized for light weight, high strength, and transportability. It is neutrally buoyant, has 300 lb breaking strength, and is embedded with water-blocking fibers to seal any leaks. The tether has a diameter of 4.0mm and is much slimmer than the vast majority of ROV tethers.
The tether carries one unshielded twisted pair (UTP) of 26AWG wire. The core of the cable contains Kevlar strands for strength and filler fibers for space filling. Both fibers are impregnated with waterblocking compound to block any leaks caused by nicks or rips in the cable. The high-visibility yellow polyurethane foam jacket resists abrasion and provides neutral buoyancy.
The BlueROV2 with a 100m Fathom Slim Tether.
This tether really shines when it comes to it’s size. It’s slim profile makes it ultra low-drag, making it ideal for deep dives, high current dives, and long distance dives where the drag from the tether is really noticeable. The size also makes it incredibly portable and easy to handle. A hundred meter tether weighs just 3 lb (1.4 kg) and can be managed by hand very easily.
Since the tether only has two wires, is can only be used for the primary communication of the BlueROV2. There are no spare twisted pairs when using this cable, which means that it is not compatible with the Water Linked Analog Locator and is not ideal for applications where you need extra tether pairs.
We’re excited to announce a new version of the Companion computer software is now available! This update adds a number of new features including a great new camera configuration page to adapt the camera settings to the underwater lighting conditions.
The update includes:
Display CPU and RAM usage statistics on the System page
Auto-detect and auto-connect to Water Linked Underwater GPS system
Add option to change the static ip address of the ROV on the Network page
Add support for Internet Explorer
Camera configuration page: easily configure camera and video stream settings
Lighting conditions underwater are quite different than above water. The light that penetrates the surface is absorbed at different rates depending on the color. Here’s a neat plot from NOAA Ocean Explorer showing how far different colors penetrate the water. As you can see, blue and green tend to go the furthest whereas red is absorbed almost immediately.
Credit: NOAA OceanExplorer
That changes the way that things look underwater. As you descend underwater, red will disappear from the image first, changing the overall color of the image. To truly correct that, you need to add the light back into the scene by illuminating it with lights.
The new camera page lets you adjust the color and lighting settings to cope with the color changes and make the camera view look more natural. With the ability to save different profiles, you can make a profile for shallow water, deep water, low visibility, good visibility, etc.
Please check out the forum post here that details the update process and the changes. If you have any feedback or results, feel free to share.
Hello everyone! Today we’re proud to announce an updated release of the BlueROV2’s core software, which includes ArduSub, Companion, QGroundControl. This is our second big software update, and this time it can be performed without opening the electronics enclosure!
Notable changes in this update are:
Ability to display camera tilt angle, lights level, tether turns and more in QGC
Allow selecting a custom image to display in the QGC ui in place of the ‘ArduSub’ logo
Many other various bugfixes, feature additions, and improvements, reference the release notes below for a comprehensive list of changes
We’ve done a lot of work to get this point and special credit goes to Jacob and Daniel, our primary Blue Robotics software developers. We strongly encourage all BlueROV2 users to upgrade to this newest software update. Please visit the full forum topic for update instructions.
Today we have a very special new product announcement. We’re partnering with Water Linked, a Norwegian company, and announcing the release of a revolutionarily low-cost Underwater GPS system. This new product, the Water Linked Underwater GPS Developer Kit combines a traditional GPS receiver and compass with an acoustic positioning system to provide positioning information underwater. We think this technology will be revolutionary to how we use ROVs.
We’re partnering with Water Linked as their first and only distributor for this system, and it will also be supported out of the box in ArduSub and the BlueROV2.
The Water Linked positioning uses something called Short Baseline (SBL) acoustic positioning. Basically, the ROV has locator beacon that sends out an acoustic pulse. Near the surface, there are four receiver hydrophones lowered into the water. The hydrophones listen for the pulse from the locator beacon and use difference in the time-of-arrival to each receiver to triangulate the ROV’s position. SBL systems, compared to the USBL systems more often used on ROVs, have the advantage of working well in shallow water and noisy acoustic environments, such as in a fish cage.
Once the position is known relative to the receivers, the global position can be found by adding that to the position obtained by a GPS receiver. The Water Linked Underwater GPS system does that part internally so that it can provide the actual global position of the ROV as it’s output.
Why It’s Important
The addition of position information when operating an ROV or other marine robotic vehicle is a big change. It means that photos from inspections can be geotagged, targets with known coordinates can be found easily, and ROV can even be programmed to do autonomous actions, such as holding position in a current or following a set of GPS waypoints.
The Water Linked Underwater GPS Developer Kit
Today were launching the Underwater GPS system in a kit that includes all of the required hardware. The software is in a functional state already, but will be improved quite a bit over the next few months. That includes the addition of a well-documented API, performance improvements, and added features. The system includes everything you need to get started – check out the individual product pages for more details, datasheets, and info.
Orders can be placed today but please note that the first systems won’t ship until about June 15th of this year.
Hello everyone, we’re pleased to announce that the ArduSub project has merged with ArduPilot! This is a momentous occasion for the ArduSub project, with our two main developers, Jacob and Rusty, both becoming members of the ArduPilot development team. ArduSub is the first new vehicle type since the addition of ArduBoat in 2011, and is the first to take the ArduPilot project underwater!
We’ve been looking forward to seeing this since the start of ArduSub!
There are many benefits of developing ArduSub further as a part of the ArduPilot project:
Our code will always be up to date with the latest library developments and bugfixes.
Our code will regularly undergo a thorough automated validation, including simulated dives and builds for multiple autopilot platforms.
Our build system will be automated, and the latest firmware binary will be automatically updated and made available for download on firmware.ardupilot.org.
Our documentation will be updated and migrated to the ArduPilot wiki, and our vehicle parameters will be documented and automatically updated when our code changes.
Our contributions to the code will also receive peer reviews from the world-class team of developers of the ArduPilot team.
Further, ArduSub development and the latest ArduSub code will now be found in the ArduPilot repository. ArduPilot and ArduSub are currently undergoing a rapid development process, and we expect to have a new stable release in April with some great new features and support for additional hardware!
Thanks for joining us on this development. If you’re interested in contributing to the ArduSub project, let us know!
ArduSub is the software at the heart of the BlueROV2. It’s based on the solid foundation of the ArduPilot code, which has been under development for years. ArduSub is open-source, fully featured, and growing rapidly.
Today we want to share some in-progress news that’s been in the works for a long time: we’re working on merging the ArduSub code into the main ArduPilot repository at github.com/ardupilot/ardupilot. What does mean? Well, up to this point, ArduSub has been developed in our own “branch” of the ArduPilot project. By merging into the main project, we’ll join the list of official ArduPilot vehicle types: ArduPlane, ArduCopter, and ArduRover. We’ll continue developing and maintain the code ourselves, but we’ll be assisted by the awesome developers at the ArduPilot organization. This is also allowed us to always be up to date with the latest features, improvements, and bugfixes contributed by the many maintainers.
For those of you interested in lots of details, here’s the text of the pull request, which explains a lot of the work we’ve done on ArduSub in the past year:
ArduSub has been in development for just over a year. In that time, we have come a long way. It started by simply copying the ArduCopter directory and poking around to see what we needed to change in order to make our vehicle move around underwater. Once we had accomplished that, and as we became accustomed to the extensive codebase, we progressed by increasing and improving functionality. We had our first stable release right at the end of 2016. We versioned the release as 3.4, in line with where we picked up from Copter. We are currently working on 3.5-dev.
We ship our BlueROV2 running ArduSub on a Pixhawk, and the response from professionals in the marine industry has been overwhelmingly positive. In addition to the BlueROV2, we’ve designed ArduSub to be very flexible, and we have DIY ROV users around the world with different ROV designs and motor configurations. ArduSub is thoroughly documented at ArduSub.com, and we have a very active ArduSub Gitter Channel.
From ArduCopter to ArduSub
The first hurdle was in figuring out how to make our vehicle actually move around underwater. The original development platform, the BlueROV1, has 6DOF, and while it can pitch and roll, it does not need to do so in order to translate in the x and y axes. Our solution was to subclass AP_MotorsMatrix with AP_Motors6DOF, overriding add_motor_raw to include the forward and lateral DOF that multicopters lack.
The second hurdle was acheiving the tantalizing prospect of holding depth with a positive or negatively buoyant vehicle. The onboard barometer is in a sealed compartment, and the pressure will obviously not correspond with altitude. The Bar30 pressure sensor, incorporates the MS5837 waterproof pressure sensor from Measurement Specialties, the same people who brought you the familiar MS5611. This sensor has almost exactly the same interface as the MS5611, which was a welcomed coincidence in the very early stages of development, when we were still learning how everything in ardupilot worked. We use the MS5611 driver to drive the external MS5837, and added a few members to the AP_Baro class in order to distinguish between an ‘air’ barometer and a ‘water’ barometer. Fortunately for us (and thanks to you guys), there was already support for multiple barometers and an option to set the primary barometer to use with the EKF. We also added a method to the EKF in order to internally set the baro_alt_noise parameter to a low value, because the pressure measurements underwater are very precise.
We have three supported flight modes, Manual (no stabilization), Stabilize, and Depth Hold. We have made progress in implementing more advanced position-enabled modes; we’ve even executed short missions in auto mode. We have also managed to create a working rudimentary model in SITL.
GPS receivers will not work underwater, so we have added an AP_GPS_MAVLINK class in order to support marine industry localization sensors. This class inherits AP_GPS_NMEA, and works by receiving raw NMEA sentence data from the telemetry connection in the form of the GPS_INJECT_DATA message. This was implemented before the AP_GPS_MAV type was added, and there is some overlap in terms of functionality. The advantage of AP_GPS_MAVLINK over AP_GPS_MAV is that the serial data (in the form of NMEA sentences) from a GPS system connected to a topside or companion computer can be sent directly over the MAVLink connection to the vehicle and parsed by the autopilot, with no need to parse the data at the origin before finally formatting the output as a GPS_INPUT MAVLink message. AP_GPS_MAVLINK also eliminates the requirement of reserving a UART for GPS input.
There are a few other minor additions to note:
The AP_JSButton library was added to handle joystick button mapping to various vehicle functions. – It is supported by QGC as well.
PosControl and Fence: added a minimum z limit in order to limit maximum depth
Added a leak detector library
Added a temperature sensor library
ArduSub is used in conjunction with a hard-wired telemetry connection over a tether. This connection is implemented via a RS422 interface directly to the autopilot, or via UDP with MAVProxy running on a companion computer. Pilot input is expected to come over MAVLink via MANUAL_CONTROL messages, and RC input is not supported because RC signals will not penetrate water. Support for ArduSub has been integrated into QGroundControl, and we continue to contribute to QGroundControl in order to improve support for ArduSub as well as other features common to all vehicles.
We have tested ArduSub primarily on the Pixhawk 1, but we have some users on other autopilots including the Navio2 and BBBmini.
Where We’re Headed
ArduSub is being actively developed with a full time developer and several contributors around the world. We plan to continue adding new features and improvements and it’s very important to us to stick with ArduPilot’s original goal of being open source and highly capable. We think that ArduSub is already more capable and extensible than most other ROV control systems.
Hello everyone! Our website was down for maintenance for a few hours last night. In that time, we migrated everything over to a new hosting service with the hope of improving the website speed. I want to share a few details about that for anyone who might be interested.
First of all, some parts of our site are hosted elsewhere already, and they work pretty well. The documentation is hosted on Github and the new forums are hosted by Discourse. You might have noticed that our main site and store has been painfully slow recently. Here’s a screenshot from Pingdom showing the loading time for the store page on our old host (Dreamhost):
21.80 seconds to load the page – only faster than 7% of websites!? Clearly we needed to figure out how to improve that. Last night, we migrated the website to Amazon Web Services (AWS). The results are pretty shocking:
As you can see, there’s an eightfold improvement in loading speed, making us faster than 60% of websites. While that could still be improved, it’s a massive difference from the old host. The website “Performance Grade” didn’t actually change much at at all, rising from 60 to 63. That’s because that score judges how efficiently the website is coded, not where it is hosted. That can be improved by adding features such as server side caching and browser caching. We’ll work on adding that in the future.
Everything seems to be working as it should on the migrated site, but please let us know if anything seems to be broken! If you find any issues, please let us know at email@example.com.