Can't connect Meteobridge Pro with Vantage Vue **solved**

[toholio]

I feel like I must be missing something obvious but I just can't get any data to be received from my Vantage Vue by my Meteobridge Pro red.

I have tried changing the ID used by the ISS and experimented with different placements of both the Meteobridge and ISS. I also tried adjusting the rx threshold to various values.

Here is the system log showing the startup and then failure to receive any data.

Code: Select all

oled (22.02.2022 01:22:22): process started.
setup  (22.02.2022 12:24:05): use UTC stamp 2022-02-22 01:24:05 (1 tries)
database (22.02.2022 12:24:14): process started.
database (22.02.2022 12:24:14): Content of RAM database restored.
database (22.02.2022 12:24:15): database sync done (17 tables, 0/103 writes).
wnetd  (22.02.2022 12:24:18): process started.
system (22.02.2022 12:24:18): start of logging process initiated.
wnetd  (22.02.2022 12:24:18): send data thread started (pid:2266 tid:2267)
logger (22.02.2022 12:24:18): databases connected. Update interval 3600 seconds.
logger (22.02.2022 12:24:18): data logger (version 5.2, build 14660) started.
logger (22.02.2022 12:24:19): connect station 0 (Meteostick Vantage via USB serial).
logger (22.02.2022 12:24:19): connect station 9 (System Data via Plug-in).
logger (22.02.2022 12:24:21): station 0 (Meteostick Vantage), transmitter 3 registered as ISS
logger (22.02.2022 12:24:21): station 0 (Meteostick Vantage), Meteostick Version 2.5.2
logger (22.02.2022 12:24:21): station 0 (Meteostick Vantage), debug off
logger (22.02.2022 12:24:21): station 0 (Meteostick Vantage), verbose off
logger (22.02.2022 12:24:21): station 0 (Meteostick Vantage), output raw (8 bytes)
logger (22.02.2022 12:24:21): station 0 (Meteostick Vantage), output raw (10 bytes)
logger (22.02.2022 12:24:21): station 0 (Meteostick Vantage), filter on
logger (22.02.2022 12:24:21): station 0 (Meteostick Vantage), rx threshold set to -90db
logger (22.02.2022 12:24:21): station 0 (Meteostick Vantage), listening to transmitter 3
logger (22.02.2022 12:24:21): station 0 (Meteostick Vantage), bandwidth narrow
logger (22.02.2022 12:24:21): station 0 (Meteostick Vantage), chip authentication failed: FE
logger (22.02.2022 12:24:21): station 0 (Meteostick Vantage), frequency band 915MHz (AU)
logger (22.02.2022 12:24:22): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (22.02.2022 12:24:22): services paused.
logger (22.02.2022 12:26:19): give up waiting for sensors after 120 secs.
logger (22.02.2022 12:26:19): services activated.

What should I look at next?

[toholio]

I just noticed that my log has the line:

Code: Select all

station 0 (Meteostick Vantage), chip authentication failed: FE

But other people's logs show something like:

Code: Select all

station 0 (Meteostick Vantage), chip authentication ok: 14

Could that be the issue? I can't find any information about what troubleshooting that might need.

[Mattk]

So what is the configuration? MBPro red via RF direct to ISS or Vue Re- transmit, MBPro red via cabled logger in Vue?

[toholio]

MBPro red via direct RF connection to Vantage Vue. Like so:

imghost

[Mattk]

Just to confirm then, you do have a Vue console receiving from the Vue ISS on Tx #3?

The Primary station settings basically appear ok apart from the Sensitivity, would try -80db

And just to confirm, this Vue ISS is actually an AU version?
What is the distance and obstacles between the MBPro red and Vue ISS?

[toholio]

Just to confirm then, you do have a Vue console receiving from the Vue ISS on Tx #3?

Yes. I have also tried other Tx#s including the default of 1. When I single press the button on the bottom of the ISS it blinks three times.

The Primary station settings basically appear ok apart from the Sensitivity, would try -80db

I have adjusted that to -80dB. I have also tried some other values earlier which didn't seem to make a difference.

Code: Select all

logger (22.02.2022 14:06:40): station 0 (Meteostick Vantage), transmitter 3 registered as ISS
logger (22.02.2022 14:06:40): station 0 (Meteostick Vantage), Meteostick Version 2.5.2
logger (22.02.2022 14:06:40): station 0 (Meteostick Vantage), debug off
logger (22.02.2022 14:06:40): station 0 (Meteostick Vantage), verbose off
logger (22.02.2022 14:06:40): station 0 (Meteostick Vantage), output raw (8 bytes)
logger (22.02.2022 14:06:40): station 0 (Meteostick Vantage), output raw (10 bytes)
logger (22.02.2022 14:06:40): station 0 (Meteostick Vantage), filter on
logger (22.02.2022 14:06:40): station 0 (Meteostick Vantage), rx threshold set to -80db
logger (22.02.2022 14:06:40): station 0 (Meteostick Vantage), listening to transmitter 3
logger (22.02.2022 14:06:40): station 0 (Meteostick Vantage), bandwidth narrow
logger (22.02.2022 14:06:40): station 0 (Meteostick Vantage), chip authentication failed: FE
logger (22.02.2022 14:06:40): station 0 (Meteostick Vantage), frequency band 915MHz (AU)

The "chip authentication failed" message is still in the logs, if that's important.

And just to confirm, this Vue ISS is actually an AU version?

Yes. The ISS unit and documentation have the AU stickers on them.

What is the distance and obstacles between the MBPro red and Vue ISS?

Right now they are in the same room. Earlier they were 10-20m apart through multiple walls.

[toholio]

I emailed support and Boris was able to log in remotely and get it working. The log now shows "station 0 (Meteostick Vantage), chip authentication ok: 14" and RF data is being received.

[Mattk]

What was the actual diagnosis?

[toholio]

What was the actual diagnosis?

I don't know. Presumably something related to the embedded Meteostick's configuration or firmware. Boris would need to explain.

[admin]

It was a not fully flashed RF board. This results into the error message "chip authentication failed: FE". I did reflash the RF board via remote login. So it was a flaw on my side when assembling/initializing the MB Pro. Lucky enough that it can be done remotely, so we avoided the hassle to ship forth and back from Germany to Australia including the customs complications.

Sorry for the hassle.