Moved: No more data... **solved**

[alehman]

I installed my MeteobridgePro at a new site on 2/18 and have not been able to make it work since then. It seemed to work briefly, until I rebooted it in the afternoon and since then there has been no data. Version Control was set to "use installed version", but I had updated it on 2/17.

Today I re-enabled updates and rebooted. It is currently on Feb 22 2018, build 12015 and is still not receiving data. I'm using the Davis Vantage Pro2 ISS. Any suggestions would be most appreciated.

[Mattk]

MB, MBPro (Red or Black)? Davis logger type? Ethernet or other?

[alehman]

Hello,
I am new to this forum. I posted here yesterday but my post seems to be gone today.

I have MeteobridgePro that I am setting up at a new location. After it initially worked for a few hours, it stopped receiving data. This was on 2/18/2018. I am using a Davis Vantage Pro2 ISS.

I was wondering if this might have to do with the software issue discussed in this thread. It was initially configured with automatic firmware updates disabled. Yesterday I re-enabled automatic updates and re-booted. The current firmware version is reported as Feb 22 2018, build 12015. The problem persists with this version.

Last few messages:
logger (23.02.2018 05:57:06): services paused.
logger (23.02.2018 05:57:33): can't open device /dev/ttyMH: No such file or directory
logger (23.02.2018 05:58:33): message above repeats 2 times.
logger (23.02.2018 05:59:03): give up waiting for sensors after 120 secs.
logger (23.02.2018 05:59:03): services activated.
logger (23.02.2018 05:59:03): can't open device /dev/ttyMH: No such file or directory
logger (23.02.2018 14:44:33): message above repeats 1051 times.

Also, it reports:
WAN IP: No Internet Access Provider:

I am logged in remotely so there obviously is connectivity. The FTP test passes. Data appears be being uploaded via FTP and MySQL, but it is all zeros, including the internal sensors.

Any suggestions would be most appreciated.
Thanks,
Alan

[Mattk]

The software issue in the original thread posted in had to do with the WS600 driver which should not be affecting a VP2? How are you connecting to the VP2? Does this issue exist if you roll back the version?

[alehman]

I tried reverting to 3.5, but I get the same result.

I'm using wireless with an external antenna. The displayed signal strength was about -58dBm. I set the receiver sensitivity to 65, then tried changing to 75.

This is an MBPro Red.

[Mattk]

Ok just to confirm then, you have "use internal RF receiver" box checked (top left of Station Tab, "RF Module Vantage" radio button on, your country freq etc is correct to match your ISS ID#, would set RF Sens to -80db, and the next box to the right should be "Direct"

And you Station# ID matches your ISS# and is set to "Integrated Sensor Suite (ISS)'

[alehman]

I re-checked all settings and they seem correct as you described. I changed the sensitivity to -80, and will see if anything changes in the behavior. Keep in mind - it did work for a short while, then stopped abruptly after I left the facility.

Thanks,
Alan

[Mattk]

Ok so how far away it is between the MBPro and the ISS? Is there also a Davis console to check to see/check if the ISS is transmitting?

[alehman]

No console. It's about 50 feet. I'm using a remote antenna outdoors because the MBPro is inside a metal building. It shows the signal strength is -58dB.

[Mattk]

Have you tried or re-tried the original RF antenna and compare the signal strength. I'm getting -67db over 30 feet and nothing blocking, this is with FW 3.5, will check if 3.6 changes that

[Mattk]

Alan,

Have taken a MBPro up to FW3.6 (Feb 24) and have no problems using Davis via RF. Distance is only around 30 feet through block wall @ -65db. May need to check what the ISS is doing, can you take the MB outside the building and test closer to the ISS? Have you double checked the ISS ID# and country freq match up?

[alehman]

Thanks for the suggestions Matt. This is a somewhat remote site so I have trying everything I can think of before going back. I will return soon and try your ideas.

[alehman]

I was able to confirm the station # using a photo I took before I left. The unit was purchased in the U.S. so I assume it is on the U.S. (915 MHz) band. Since the last reboot, it is now showing a valid WAN IP address.

An unrelated question - where does the MBPro get the system time?

The messages log now shows:

system (24.02.2018 23:20:56): stop of logging process initiated.
system (24.02.2018 23:21:03): start of logging process initiated.
logger (24.02.2018 23:21:03): databases connected. Update interval 3600 seconds.
logger (24.02.2018 23:21:03): historical data loaded (0 records).
logger (24.02.2018 23:21:03): data logger (version 5.0x, build 11957) started.
logger (24.02.2018 23:21:04): connect station 0 (Meteostick Vantage via USB serial).
logger (24.02.2018 23:21:04): connect station 9 (System Data via Plug-in).
logger (24.02.2018 23:21:07): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (24.02.2018 23:21:07): services paused.
logger (24.02.2018 23:21:13): transmitter 2 registered as ISS
logger (24.02.2018 23:21:13): Meteostick Version 2.5.1
logger (24.02.2018 23:21:13): debug off
logger (24.02.2018 23:21:13): verbose off
logger (24.02.2018 23:21:13): output raw (8 bytes)
logger (24.02.2018 23:21:13): output raw (10 bytes)
logger (24.02.2018 23:21:13): filter on
logger (24.02.2018 23:21:13): rx threshold set to -65db
logger (24.02.2018 23:21:13): listening to transmitter 2
logger (24.02.2018 23:21:13): bandwidth narrow
logger (24.02.2018 23:21:14): chip authentication ok: 14
logger (24.02.2018 23:21:14): frequency band 915MHz (US)
logger (24.02.2018 23:21:23): MeteoStick Version 2.5.1 (Jul 20 2016 09:14:19), Free RAM 698, SN: EE061A6A52124800
logger (24.02.2018 23:21:23): License Information:
logger (24.02.2018 23:21:23): MeteoStick (c) 2014-2016 by smartbedded.com
logger (24.02.2018 23:21:23): Meteostick Version 2.5.1
logger (24.02.2018 23:23:04): give up waiting for sensors after 120 secs.
logger (24.02.2018 23:23:04): services activated.
logger (24.02.2018 23:31:53): child process received timeout signal (14).
logger (24.02.2018 23:31:53): disconnect station 0 (Meteostick Vantage): exit

[admin]

@alehman: Hi, can you please give me a remote login? Please send credentials to "info(at)meteobridge.com".

[alehman]

Thanks. Sorry for the delay responding. The problem was found to be a loose connection on the cable to the remote antenna. Once that was corrected, the problem resolved and seems to be working properly. Apologies for the "wild goose chase"!