MB Pro Red internal sensor issue **solved**

This section covers the Meteobridge PRO, NANO SD and Raspberry Pi units exclusively

Moderator: Mattk

Post Reply
MattL
Fresh Boarder
Fresh Boarder
Posts: 1
Joined: Sat Jul 02, 2016 1:42 pm

MB Pro Red internal sensor issue **solved**

Post by MattL »

My MB Pro Red has been running for around a month now but have noticed that every day, there are around 10-15 occasions grouped within a 1-2 hour period where thb0hum records 30% relative humidity which then has an impact on the computed dew point. Since rebooting MB yesterday, I have also seen individual readings from thb9temp and thb9hum randomly reported with values of -14.8C and 58% respectively.

Whilst the thb9 readings aren't so much of an issue for now, the data from thb0hum requires a significant amount of manual processing to remove the erroneous values.

Any thoughts would be appreciated.

User avatar
admin
Platinum Boarder
Platinum Boarder
Posts: 6631
Joined: Mon Oct 01, 2007 10:51 pm

Re: MB Pro Red internal sensor issue

Post by admin »

There is another user who reports that sometimes some false readings are showing up on the internal sensors. As I cannot reproduce on my rig (at least until now), I would like to login on yours. Can you please send remote login credentials to "info(at)meteobridge.com"?

WS Heinenoord
Junior Boarder
Junior Boarder
Posts: 22
Joined: Sun Dec 22, 2019 2:08 pm

Re: MB Pro Red internal sensor issue

Post by WS Heinenoord »

My new Pro Red board seems to suffer from same problem. Every day at random times thb0hum drops to "30", sometimes even lower, see attached screenshots.

MB Pro th0hum problem-1.PNG
MB Pro th0hum problem-1.PNG (22.58 KiB) Viewed 1114 times
MB Pro th0hum problem-2.PNG
MB Pro th0hum problem-2.PNG (24.3 KiB) Viewed 1114 times
MB Pro th0hum problem-3.PNG
MB Pro th0hum problem-3.PNG (23.82 KiB) Viewed 1114 times

The other board parameters like thb0temp, pressure don't show outliers. thb9hum doesn't show such drops, but it's absolute value cannot be humidity. It's more like a temperature range of values. It does not show any drop-puts like in thb0hum.
MB Pro th9hum.PNG
MB Pro th9hum.PNG (21.99 KiB) Viewed 1114 times

Is this a hardware issue? Or something in the software?
Like MattL is reporting it's rather laborious to get it right.
It should be noted that the internal barometer reading needs a correction of -4.20 mbar to line up with the 4 other electronic pressure chips I've running (Davis and BMP280).

Thanks for any help!

Tasboy
Fresh Boarder
Fresh Boarder
Posts: 1
Joined: Fri May 29, 2020 6:09 am

Re: MB Pro Red internal sensor issue

Post by Tasboy »

I'm new here - first message.

I am also having this problem.

WS Heinenoord
Junior Boarder
Junior Boarder
Posts: 22
Joined: Sun Dec 22, 2019 2:08 pm

Re: MB Pro Red internal sensor issue

Post by WS Heinenoord »

The problem with thb0hum continues to happen every day.

MB Pro th0hum problem-4.PNG
MB Pro th0hum problem-4.PNG (22.59 KiB) Viewed 831 times
Is there any sight on a solution by software?
Or should the hardware to be changed?

JohnsPro
Junior Boarder
Junior Boarder
Posts: 26
Joined: Sun Jan 13, 2019 9:19 pm
Location: Centeral New York USA

Re: MB Pro Red internal sensor issue

Post by JohnsPro »

Group,
It appears that I also have the same problem and it appears to have a cycle to it if you look over several days.
July_9.jpg
July_9.jpg (77.75 KiB) Viewed 792 times
July_8.jpg
July_8.jpg (80.48 KiB) Viewed 792 times
July_7.jpg
July_7.jpg (80.09 KiB) Viewed 792 times
July_6.jpg
July_6.jpg (81.06 KiB) Viewed 792 times
July_5.jpg
July_5.jpg (80.39 KiB) Viewed 792 times
Thank You John

WS Heinenoord
Junior Boarder
Junior Boarder
Posts: 22
Joined: Sun Dec 22, 2019 2:08 pm

Re: MB Pro Red internal sensor issue

Post by WS Heinenoord »

I contacted my MB supplier early this week because this irregular jump to 30% seemed a rare hardware problem to me.
He checked his MB contacts and came back there's a new software update since Feb 7 '21 available. See https://www.meteobridge.com/wiki/index.php/Forum
I ran the update and no re-occurrence since then.

Problem solved !
Thanks go to all contributing.

Post Reply