B&G H5000 calibration
Dream team! Patrik Måneskiöld is the navigator on Blur, Johan Barne is a guru when it comes to instruments and data analytics, and Martin Gadman runs Happy Yachting and is the one who installed the instruments with me. We spent an afternoon getting the calibration sorted.
This article is a translation of this one from june 2018.
Above all, I wanted to get Johan’s input on the process, and the best practices he uses when racing with the pros in TP52. He helped us find sensible starting values, but the biggest lesson was another one:
Instruments and calibration are not something you do once, and then everything works. Some things are enough to do once, or maybe once when you are in a new place, but if you want to get the wind values to be reliable, you have to work on this continuously.
It’s the same as everything else in our sport.
There are probably those who put a tape on the jib sheet when you were out with the sailmaker, and do not change it because you are unsure. However, once you understand what happens when you adjust the jib cars, then it both becomes more fun and you’ll sail faster.
So it’s the same with calibration. You have to dare to adjust the values to make them work, and adjust back if it doesn’t. It isn’t dangerous.
The web interface on the H5000 is great for daring to do just that. No special software or difficult menu systems, but very straight forward.
Step one, and probably the most straightforward calibration, is the depth sounder. How far does the transducer sit under the waterline?
Step two, compass calibration, is also simple. Run the boat in a perfect circle at low speed. Find a spot with as little disturbance as possible. After each round of calibration, you get to know the numbers of the local magnetic field. Also, you can see the differences between different positions. We went from having it on the aft bulkhead to the forepeak. Not a big difference, but when you are fussy.
Step three, the log, took more time than expected. The sensor has a much smaller paddle wheel than the old Nexus sensor, and we have flush mounted it. It soon became clear that it showed far too little at low speeds, as the boundary layer have a considerable effect. After some tweaking, however, we managed to nail it through the table above. Prepare to spend some time getting this right.
There are a few different ways to do the calibration. What is difficult in Långedrag is that there is always a little current. However, some laps back and forth along the pier (and inside the harbor) made it possible to get good average values in Excel.
True wind is “the holy grail” when it comes to instruments. Getting TWD and TWS to work on every heading and not change in every tack requires a little job. Johan makes this adjustment many times in a race on TP52 Platoon. However, for amateurs like us, it might be enough to do it once in the morning before the race.
To get started we wanted to find proper basic settings, which looks very similar between different boats. Then adjust as it changes due to season and weather conditions. It is likely that these values will be decreased a little during the season.
After a couple of tacks, if you can see that TWD differs between tacks, then the rule is to:
If you are lifted from tack to tack, subtract half the difference.
If headed from tack to tack, add half the difference.
That is, if I have TWD 200 on starboard, but after the tack to port the TWD is 210, so it is perceived as a shift of 10 degrees. Then I should add 5 degrees to get TWD 205 on both tacks:
And yes, I have set up a cheat sheet :-)
There is also an auto function that we have not yet been able to try yet.
Here you adjust the difference between upwind and downwind, where you have to decrease the wind speed. We are almost done, and after we have analyzed more data, we’ll make the final adjustments. For now.
Leeway is a guessed factor. Can be measured in slightly different ways, but right now we think this is good enough.
The integration with Expedition is relatively straight forward. You either choose Hlink (serial over USB) or Websocket (over WiFi or network) which is the preferred method. Here you should be able to exchange all data, starting line, countdown and much more.
It is easy to set up which data you want to send to the H5000 to display on the mast or cockpit displays. H5000 automatically finds this data as USER, and everything comes up with the right labels, damping and more. Easy.
The H5000 provides a good overview of where data comes from. One often has several units that can give the same values. Here is a list of the data available in the system right now:
Aft Depth 2.570212 m
Air Temperature 29 °C
Altitude -2.2 m
Analogue Channel 1 0.092
Analogue Channel 2 0.087
Analogue Channel 3 0.092
Analogue Channel 4 0.092
Apparent Wind Angle -42.440735 °
Apparent Wind Speed 4.837355 kn
Average True Wind Direction 243.4 °M
Barometric Pressure 1015 mb
Bias Advantage 0.079
Bias Advantage BL 13.3
Blue Phase 1.68
Boat Speed 0 kn
Boat Speed Correction 0.00 kn
Bow Position Latitude 57°040.094′ N
Bow Position Longitude 011°050.708′ E
Commanded Rudder Angle 0 °
Corrected MWA -54 °
Corrected MWS 5.33
Course 288.6 °M
Course Over Ground 278.459473 °M
Dead Reckoning Bearing 356.6 °M
Dead Reckoning Distance 0.00 NM
Depth 2.570294 m
Depth Offset 0.4 m
Distance Behind Start Line 0.05 NM
Distance Behind Start Line (Boat Lengths) 8.23
Distance To Start Line 0.05 NM
Distance To Start Line (Boat Lengths) 8.23
Geoidal Seperation 0.02 NM
GPS Fix Type 3.00
GPS Position Latitude 57°040.093′ N
GPS Position Longitude 011°050.715′ E
Green Phase 4.53
HDOP 0.600
Heading 288.723145 °M
Heading Opposite Tack 203.8 °M
Heel -0.134003 °
Log 484.2 NM
Magnetic Variation 3 °
MARK TM 8.35
Measured Boat Speed 0.00 kn
Measured Boat Speed Port 0.00 kn
Measured Wind Angle -54 °
Measured Wind Speed 5.3 kn
MKBRG 270
MKRNG 28.2
NXTMKBRG 114
NXTMKTWA 133
Opposite Tack COG 044.8 °M
Opposite Tack Target Heading 203.4 °M
Optimum Wind Angle 1 °
Orig TWA -53.634
Orig TWD 247
Orig TWS 5.33
PDOP 1.00
Pitch Rate 0.0 °/sec
Polar Performance 0 %
Polar Speed 4.46 kn
POLBSP PC 0.000
Position Error 0.00 NM
Position Integrity 0.000
Position Quality 1.00
Race Timer 00:05:00 hrs
Rate of Turn 0.2 °/sec
Red Phase 1.28
Roll Rate 0.0 °/sec
Rudder Angle 1 °
Satellites in View 12.0
SDGPS Status 0.000
Sea Temperature 20.9 °C
Signed Leeway Angle 0 °
Signed Leeway Angle 0 °
Speed Over Ground 0 kn
Speed Through Water 0.00 kn
Start Line Bearing 195.2 °M
Start Line Bearing To Port 233.7 °M
Start Line Bearing To Starboard 338.8 °M
Start Line Bias -39 °
Start Line Distance To Port 0.08 NM
Start Line Distance To Port (Boat Lengths) 13.2
Start Line Distance To Starboard 0.08 NM
Start Line Distance To Starboard (Boat Lengths) 13.8
Start Line Port Position Latitude 57°040.052′ N
Start Line Port Position Longitude 011°050.586′ E
Start Line Starboard Position Latitude 57°040.172′ N
Start Line Starboard Position Longitude 011°050.661′ E
TARG BSPTARG BSP 4.66
Target Boat Speed 4.67 kn
Target TWA -43 °
Tide Rate 0.000001 kn
Tide Set 356.619537 °M
TM ON P 6.09
TM ON S 2.26
Trim -0.269562 °
Trip 1 Distance 0.00 NM
Trip 1 Speed Avg 0.00 kn
Trip 1 Speed Max 0.00 kn
Trip 1 Time 00:00:00 hrs
Trip 2 Distance 0.00 NM
Trip 2 Speed Avg 0.00 kn
Trip 2 Speed Max 0.00 kn
Trip 2 Time 00:00:00 hrs
True Wind Angle -42.395828 °
True Wind Direction 246.323425 °M
True Wind Speed 4.903689 kn
TWA Correction 8 °
TWS Correction -0.423
Uncorrected Log 1 0.00 NM
UTC Date Sun Jun 3 2018
UTC Time 09:40:35 hrs
VDOP 0.900
Velocity Made Good 0.00 kn
VMG Performance 0 %
Wind Angle to Mast -53 °
Wind Lift -6 °
Wind Phase 6 °
Ivan
May 24, 2019 @ 09:59
Very good article Patrick!
Rozgonyi Balázs
May 29, 2019 @ 01:33
if i may ask, why does True Wind calibration goes out of, well, calibration?
Johan Barne
May 29, 2019 @ 23:11
Dear Rozgonyi!
The wind calibration is needed due to that the wind is affected by the top of the rig (and some other minor items). That effect is different in different wind speeds and different wind angles. Therefore different wind calibration values is needed for every wind speed and angle.
However, wind speed is only measured at one height = the mast height. Depending on the weather and wind profile, the wind at other heights can variate for at a certain wind speed measured at mast height. The wind at other heights affect the flow at the top as well.
Subsequently, the wind calibration needs to be adjusted as conditions changes.
Torben Falholt
Jul 9, 2019 @ 13:16
Very interesting article. I am a little confused on how to Heel correction function works. The numbers in the table show’s what ? 0 Degree at 2,5 kn show a correction factor of 0.68 in the above table. What does this factor represent.
Also if I wanted to calibrate my boat – how would I be able to measure my speed with a heel of 20% degree ??
Torben Falholt
Jul 9, 2019 @ 19:14
I resign from this question. After upgrading the CPU to the latest software level – the calibration issue has changed – and this question is not on my agenda.
David Eastwood
Jul 19, 2019 @ 09:07
I find it’s helpful to log AWA/MWA and AWS/MWS – comparing these values post-fact is useful as it tells you whether your wind calibrations are about right. MWS/MWA are sort of checksums for the calibrations.
In H5000, AWA/AWS values are back-calculated from TWA/TWS whereas MWA/MWS are the raw values from the sensors. In a perfectly calibrated world, MWA=AWA and MWS=AWS. However, as the output variables are damped and the sensor data isn’t, you need to compare the values by logging them and loading to a spreadsheet over a time period and calculate averages.
On the water, you can eyeball AWA/AWS vs MWA/MWS in StripChart or the B&G Web interface to get a feel for any errors but it’s a bit imprecise.
To log MWA/MWS you need to be using the Websocket interface to Expedition, they aren’t available over HLink for some bizarre reason.
Peter Gustafsson
Jul 19, 2019 @ 11:41
Great tip David!
Andy Robertson
May 3, 2022 @ 01:09
David – upwind i have an average difference of .1 where MWS is lower than AWS – yet the TWS average is well lower. I know that it should be – but by feel the TWS is too low. This is also backed by the TWS was 15knts going into the top mark, 18knts on the reach and 21knts going into the run. The wind built a bit but not that much- so by intuition the TWS upwind is reading too low. But are you saying that if the MWS=AWS then a TWS adjustment is not required? or would i still look to add say +2 or 3 to the TWS upwind?
David Eastwood
Jul 22, 2019 @ 22:55
👍
Dave Nauber
Jun 19, 2022 @ 17:45
Maybe not the right place for this question, but when pinging the starting line, do the ends need to be pinged from a certain direction (i.e. mark at the bow, bow head to wind)? I would think mark at the bow from any direction should work if the offset from GPS to bow is entered correctly.
Peter Gustafsson
Jun 20, 2022 @ 07:56
I think this is taken care of by the software. That said, we try to be consistent with the “standard way” (i.e. mark at the bow, bow head to wind).
Also helps with traffic since everyone is pinging in a similar pattern 😃
Eric Petersen
Jun 26, 2022 @ 03:38
Can someone explain what the upwind angle and down angle numbers are for?
Upwind angle 165?
Down Angle 135, 140, etc.?
Peter Gustafsson
Jun 26, 2022 @ 18:57
Hi Eric, unsure about what you’re referring to?
Mario
Dec 8, 2023 @ 19:56
It is in the TWS calibration screenshot