Expedition Navigation Software 
- rundazippa
- Contributor
Offline - Registered: 6/20/2019
- Posts: 7
Re: AWA reading to quickly
I believe I have fixed the problem, the AWA is reading "smooth" and much closer to exactly the same as the AWA from the H5000.
From the H5000 web socket interphase I selected for the H5000 to receive AWA from the CPU, it was set to receive from the MHU.
I also deselected the AWA/AWS PGN from the Actisence/NGT-1 settings menu.
It does seem that the NGT-1 will sometimes override the H5000 settings in expedition.
Is anyone aware of any drawbacks of having the H5000 receive AWA from the CPU and not the MHU?
- DuncanR
- Expert
Offline
- From: Up and down East Coast Aus
- Registered: 9/16/2015
- Posts: 470
Re: AWA reading to quickly
I didn't think of that, but with H5000 websocket and an Actisense both running, you have to be careful to get individual data items from only one source. The classic illustration of that is the jumpy track you see if you have two GPS inputs to Expedition ....
- Nick
- Moderator
Offline
- Registered: 9/16/2015
- Posts: 2,966
Re: AWA reading to quickly
Yes, you don't want any instrument data from the NGT-1, but the GPS is probably best sourced from the NGT-1, which is why you can turn that off for H5.
- JL
- Contributor
Offline
- Registered: 6/30/2019
- Posts: 8
Re: AWA reading to quickly
Reading AWA and AWS from the MHU by-passes the H5000's calculations of these data. B&G have a particular way of producing Apparent Wind data, which consists in back-calculating them after going through a first iteration based on what they call "Measured Wind " (MWA and MWS are accessible for display) to calculate True Wind. Once this is done, including all corrections to TWA and TWS, they back-calculated AWA and AWS.
In summary, you really should use the CPU's Apparent Wind data to rate full advantage of the H5000 system. This does require that you populate the correction tables properly, however.