Getting crazy True and Apparent Wind Readings

[FuneSF]

(I posted this on Sailnet. But, activity seems to have disappeared on that site the past few months. Trying out CruiserForum today for the first time)

My AWS and TWS readings on my MFD sometimes show speeds of 600 to 700 kn. After an hour or two, it will revert back to the correct speeds. Does anyone have experience with this type of problem? Is it a software issue or likely due to the wind sensor or cabling? Everything has been working fine since I installed these a year ago. The problem just started this week. Turning everything on and off does not help. Also, going into the network menu on the MFD and refreshing devices does not help.

I will contact B&G next week. But, I figured I would post the problem on this forum and maybe get a solution.

MFD B&G Zues 3
B&G 508 Wind Sensor

Thanks.

[tkeithlu]

Welcome to the forum, FuneSF.

[mglonnro]

Originally Posted by FuneSF

(I posted this on Sailnet. But, activity seems to have disappeared on that site the past few months. Trying out CruiserForum today for the first time)

My AWS and TWS readings on my MFD sometimes show speeds of 600 to 700 kn. After an hour or two, it will revert back to the correct speeds. Does anyone have experience with this type of problem? Is it a software issue or likely due to the wind sensor or cabling? Everything has been working fine since I installed these a year ago. The problem just started this week. Turning everything on and off does not help. Also, going into the network menu on the MFD and refreshing devices does not help.

I will contact B&G next week. But, I figured I would post the problem on this forum and maybe get a solution.

MFD B&G Zues 3
B&G 508 Wind Sensor

Thanks.

I have the same setup but haven't seen _that_ specific problem. What I would do, though, to make sure where the wonky data comes from: find the 508 in the device list and check the actual raw data that it's outputting. I don't remember where to do that in the Zeus3 (I guess there should be a place), but in the Triton2 it looks like in the attached pic.

If the 508 is outputting 600 knots of wind then my best guess is that it is not the cables, but rather the 508's chip might be damaged. That's just a guess, though.

[FuneSF]

Thank you.

That was a helpful about checking where the data comes from. I did not know about that function.

I also noticed today that my COG figures are also all over the place. They are spinning around to all points of the compass. So, this problem is not isolated to the wind sending unit. It is most likely some type of software issue on the MFD. Hopefully, B&G will be able to provide a solution this week. Hopefully, I will not need to do a factory reset of everything.

[Scrimshaw4]

Have you checked the transducer that is providing boat speed? If you are using STW the paddle wheel me be getting obstructed due to growth then cleared as you travel. If using SOG then look at GPS source connection. JMHO

[guyrj33]

Originally Posted by FuneSF

Thank you.

That was a helpful about checking where the data comes from. I did not know about that function.

I also noticed today that my COG figures are also all over the place. They are spinning around to all points of the compass. So, this problem is not isolated to the wind sending unit. It is most likely some type of software issue on the MFD. Hopefully, B&G will be able to provide a solution this week. Hopefully, I will not need to do a factory reset of everything.

What is the data source of your COG reading, GPS?
Does your track show accurately on your ZEUS?
A Varying COG reading would cause True and Apparent wind calculations to vary.

[waterman46]

Originally Posted by guyrj33

What is the data source of your COG reading, GPS?
Does your track show accurately on your ZEUS?
A Varying COG reading would cause True and Apparent wind calculations to vary.

Apparent wind should not use any course or speed inputs, only the angle the vane is pointing and how fast the anemometer is spinning. If apparent wind is incorrect, then the problem is not with the COG, SOG or the GPS. It may be simply a bad connection, or the wind sensor or the MFD incorrectly processing that piece of data.

Ideally, a second device, either MFD or dedicated wind display could be used to isolate the problem w/o having to remove anything first.

[guyrj33]

Originally Posted by waterman46

Apparent wind should not use any course or speed inputs, only the angle the vane is pointing and how fast the anemometer is spinning. If apparent wind is incorrect, then the problem is not with the COG, SOG or the GPS. It may be simply a bad connection, or the wind sensor or the MFD incorrectly processing that piece of data.

Ideally, a second device, either MFD or dedicated wind display could be used to isolate the problem w/o having to remove anything first.

you're right apparent wind doesn't need COG or SOG etc.
I was thinking of True wind, which does need boat speed and direction information for the calculation.

[thunderhoof]

The problem could possibly be external interference injecting noise into the knotmeter pulse string. Does the occurrence of faulty data correlate with the use or speed of the engine? any particular radio or nav gear operating?
In any event I would go with the advice to check all connections and ground paths and make sure there are no breaks in the shield or other conductors.

[chasfgr]

Can be caused by the masthead movement in a seaway with light winds.


Most likely a connection, usually into the black-box which collects the raw data from all the instruments on an NMEA 2000 system.

[jlb]

Have you had any recent lightening strikes near by?

[crayiii]

I'm digging up an old thread but I'm having this same issue. I installed a new MHU and still have the problem. Did you ever find a solution?

[FuneSF]

When I had NMEA 2000 electronics installed, the installer placed the terminators at each end of the backbone line. This is the normal process. But, with the B&G 508 and 608 masthead sensors, the terminator for that side of the backbone is the sensor in the masthead. So, my NMEA 2000 network basically had three terminators installed.

Once it was rectified, the problem stopped.