Author Topic: Hardware config in weewx.conf using wifi logger  (Read 428 times)

0 Members and 1 Guest are viewing this topic.

Offline cwuthenow

  • Member
  • *
  • Posts: 5
Hardware config in weewx.conf using wifi logger
« on: April 28, 2019, 02:05:13 AM »
Hi all,

I'm new to this forum and currently setting up my Davis Vantage Pro2 wireless (DAV-6323OV) using a Davis Weather Envoy 6316EU and the wifi logger (see https://www.manula.com/manuals/pws/davis-kb/1/en/topic/wifi-logger). The wifi logger is directly installed in the Envoy. Using the json functions of the wifi logger I can grab real time data but have issues to get the correct EU data formats. The wifi logger seems to upload US metrics. Of course I can convert the data by analysing the json file but I only get a low accuracy (as the json data only contain 2 digits and converting into EU metrics is quite unaccurate).

I'm struggeling to adapt the config to get weewx running and capture life data. When starting weewx it downloads the archived data perfectly and is inserting it into the configured mysql database. No worries on that.

Does anybody has a comparable config up and running and can help to config whether the weewx config or the wifi logger? I get the following errors in weewx:

Apr 28 08:03:17 nas weewx[7040]: vantage: LOOP try #1; error: vantage: Expected 99 characters; got zero instead
Apr 28 08:03:17 nas weewx[7040]: vantage: ip-write error: [Errno 32] Datenübergabe unterbrochen (broken pipe)
Apr 28 08:03:17 nas weewx[7040]: vantage: ip-write error: [Errno 32] Datenübergabe unterbrochen (broken pipe)
Apr 28 08:03:17 nas weewx[7040]: vantage: ip-write error: [Errno 32] Datenübergabe unterbrochen (broken pipe)
Apr 28 08:03:17 nas weewx[7040]: vantage: Unable to wake up console
Apr 28 08:03:17 nas weewx[7040]: vantage: LOOP try #2; error: Unable to wake up Vantage console
Apr 28 08:03:17 nas weewx[7040]: vantage: ip-write error: [Errno 32] Datenübergabe unterbrochen (broken pipe)
Apr 28 08:03:17 nas weewx[7040]: vantage: ip-write error: [Errno 32] Datenübergabe unterbrochen (broken pipe)
Apr 28 08:03:17 nas weewx[7040]: vantage: ip-write error: [Errno 32] Datenübergabe unterbrochen (broken pipe)
Apr 28 08:03:17 nas weewx[7040]: vantage: ip-write error: [Errno 32] Datenübergabe unterbrochen (broken pipe)
Apr 28 08:03:17 nas weewx[7040]: vantage: Unable to wake up console
Apr 28 08:03:17 nas weewx[7040]: vantage: LOOP try #3; error: Unable to wake up Vantage console
Apr 28 08:03:17 nas weewx[7040]: vantage: ip-write error: [Errno 32] Datenübergabe unterbrochen (broken pipe)
Apr 28 08:03:17 nas weewx[7040]: vantage: ip-write error: [Errno 32] Datenübergabe unterbrochen (broken pipe)
Apr 28 08:03:17 nas weewx[7040]: vantage: ip-write error: [Errno 32] Datenübergabe unterbrochen (broken pipe)
Apr 28 08:03:17 nas weewx[7040]: vantage: ip-write error: [Errno 32] Datenübergabe unterbrochen (broken pipe)
Apr 28 08:03:17 nas weewx[7040]: vantage: Unable to wake up console
Apr 28 08:03:17 nas weewx[7040]: vantage: LOOP try #4; error: Unable to wake up Vantage console
Apr 28 08:03:17 nas weewx[7040]: vantage: LOOP max tries (4) exceeded.
Apr 28 08:03:17 nas weewx[7040]: engine: Main loop exiting. Shutting engine down.
Apr 28 08:03:17 nas weewx[7040]: vantage: ip-write error: [Errno 32] Datenübergabe unterbrochen (broken pipe)
Apr 28 08:03:17 nas weewx[7040]: engine: Caught WeeWxIOError: Max tries exceeded while getting LOOP data.
Apr 28 08:03:17 nas weewx[7040]:     ****  Waiting 60 seconds then retrying...

weewx.conf is setup as follows:

[Vantage]
    # This section is for the Davis Vantage series of weather stations.
   
    # Connection type: serial or ethernet
    #  serial (the classic VantagePro)
    #  ethernet (the WeatherLinkIP or Serial-Ethernet bridge)
       type = ethernet
   
    # If the connection type is serial, a port must be specified:
    #   Debian, Ubuntu, Redhat, Fedora, and SuSE:
    #     /dev/ttyUSB0 is a common USB port name
    #     /dev/ttyS0   is a common serial port name
    #   BSD:
    #     /dev/cuaU0   is a common serial port name
    # port = /dev/ttyUSB0
   
    # If the connection type is ethernet, an IP Address/hostname is required:
       host = [wifiloggerip] --> changed for the post but correctly setup in the real file
   
    ######################################################
    # The rest of this section rarely needs any attention.
    # You can safely leave it "as is."
    ######################################################
   
    # Serial baud rate (usually 19200)
    baudrate = 19200
   
    # TCP port (when using the WeatherLinkIP)
    tcp_port = 22222
   
    # TCP send delay (when using the WeatherLinkIP):
    tcp_send_delay = 0.5
   
    # The id of your ISS station (usually 1). If you use a wind meter connected
    # to a anemometer transmitter kit, use its id
    iss_id = 1
   
    # How long to wait for a response from the station before giving up (in
    # seconds; must be greater than 2)
    timeout = 4
   
    # How long to wait before trying again (in seconds)
    wait_before_retry = 1.2
   
    # How many times to try before giving up:
    max_tries = 4
   
    # Vantage model Type: 1 = Vantage Pro; 2 = Vantage Pro2
    model_type = 2
   
    # The driver to use:
    driver = weewx.drivers.vantage

Thx for your support in advance, highly appreciated!
Carsten
« Last Edit: April 28, 2019, 02:09:06 AM by cwuthenow »

Offline pfletch101

  • Senior Contributor
  • ****
  • Posts: 295
    • Personal Website
Re: Hardware config in weewx.conf using wifi logger
« Reply #1 on: April 29, 2019, 10:56:14 AM »
This looks like the issue I had when I first set up my WiFiLogger with weewx, and my problem was in the WiFiLogger setup. On the WiFiLogger Setup|System page, check if 'TCP Port' is set as 'auto pause', which is the default. The settings on that page should look like the attached image.
Vantage Pro 2+ with WeatherLink - data incorporated in domestic energy production (PV) and use monitoring system.

Offline cwuthenow

  • Member
  • *
  • Posts: 5
Re: Hardware config in weewx.conf using wifi logger
« Reply #2 on: April 29, 2019, 01:23:34 PM »
Thx for your reply - little improvement after changing this setting and performing the updates. Still the wifi logger seems not to get data and throws a time out. Remember that the down load of the archive data is working smoothly. Any idea? From a logical perspective it seems a config issue from weewx as the overall download and therefor the network layer is working properly...

Here the detailled debug from syslog:

Apr 29 19:18:33 nas systemd[1]: Reloading LSB: weewx weather system.
Apr 29 19:18:33 nas weewx[8677]: engine: Received signal HUP. Initiating restart.
Apr 29 19:18:33 nas weewx[8677]: engine: Main loop exiting. Shutting engine down.
Apr 29 19:18:33 nas systemd[1]: Reloaded LSB: weewx weather system.
Apr 29 19:18:33 nas weewx[9072]: Reloading weewx weather system: weewx.
Apr 29 19:18:33 nas weewx[8677]: restx: Shut down Wunderground-PWS thread.
Apr 29 19:18:34 nas weewx[8677]: engine: Received signal HUP. Restarting.
Apr 29 19:18:34 nas weewx[8677]: engine: Using configuration file /etc/weewx/weewx.conf
Apr 29 19:18:34 nas weewx[8677]: engine: Debug is 1
Apr 29 19:18:34 nas weewx[8677]: engine: Initializing engine
Apr 29 19:18:34 nas weewx[8677]: engine: Loading station type Vantage (weewx.drivers.vantage)
Apr 29 19:18:34 nas weewx[8677]: vantage: Driver version is 3.1.1
Apr 29 19:18:34 nas weewx[8677]: vantage: Opened up ethernet host 192.168.1.97 on port 22222. timeout=10.0, tcp_send_delay=0.5
Apr 29 19:18:34 nas weewx[8677]: vantage: Gentle wake up of console successful
Apr 29 19:18:35 nas weewx[8677]: vantage: Hardware type is 16
Apr 29 19:18:37 nas weewx[8677]: vantage: ISS ID is 1
Apr 29 19:18:37 nas weewx[8677]: vantage: Hardware name: Vantage Pro2
Apr 29 19:18:37 nas weewx[8677]: engine: Loading service weewx.engine.StdTimeSynch
Apr 29 19:18:37 nas weewx[8677]: engine: Finished loading service weewx.engine.StdTimeSynch
Apr 29 19:18:37 nas weewx[8677]: engine: Loading service weewx.engine.StdConvert
Apr 29 19:18:37 nas weewx[8677]: engine: StdConvert target unit is 0x10
Apr 29 19:18:37 nas weewx[8677]: engine: Finished loading service weewx.engine.StdConvert
Apr 29 19:18:37 nas weewx[8677]: engine: Loading service weewx.engine.StdCalibrate
Apr 29 19:18:37 nas weewx[8677]: engine: Finished loading service weewx.engine.StdCalibrate
Apr 29 19:18:37 nas weewx[8677]: engine: Loading service weewx.engine.StdQC
Apr 29 19:18:37 nas weewx[8677]: engine: Finished loading service weewx.engine.StdQC
Apr 29 19:18:37 nas weewx[8677]: engine: Loading service weewx.wxservices.StdWXCalculate
Apr 29 19:18:37 nas weewx[8677]: wxcalculate: The following values will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, dewpoint=prefer_hardware, appTemp=prefer_hardware, rainRate=prefer_hardware, windrun=prefer_hardware, heatindex=prefer_hardware, maxSolarRad=prefer_hardware, humidex=prefer_hardware, pressure=prefer_hardware, inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, cloudbase=prefer_hardware
Apr 29 19:18:37 nas weewx[8677]: wxcalculate: The following algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Apr 29 19:18:37 nas weewx[8677]: engine: Finished loading service weewx.wxservices.StdWXCalculate
Apr 29 19:18:37 nas weewx[8677]: engine: Loading service weewx.engine.StdArchive
Apr 29 19:18:37 nas weewx[8677]: engine: Archive will use data binding wx_binding
Apr 29 19:18:37 nas weewx[8677]: engine: Record generation will be attempted in 'hardware'
Apr 29 19:18:37 nas weewx[8677]: engine: Using archive interval of 1800 seconds (specified by hardware)
Apr 29 19:18:37 nas weewx[8677]: engine: Use LOOP data in hi/low calculations: 1
Apr 29 19:18:37 nas weewx[8677]: manager: Daily summary version is 2.0
Apr 29 19:18:37 nas weewx[8677]: engine: Using binding 'wx_binding' to database 'weewx'
Apr 29 19:18:37 nas weewx[8677]: manager: Starting backfill of daily summaries
Apr 29 19:18:37 nas weewx[8677]: engine: Finished loading service weewx.engine.StdArchive
Apr 29 19:18:37 nas weewx[8677]: engine: Loading service weewx.restx.StdStationRegistry
Apr 29 19:18:37 nas weewx[8677]: restx: StationRegistry: Registration not requested.
Apr 29 19:18:37 nas weewx[8677]: engine: Finished loading service weewx.restx.StdStationRegistry
Apr 29 19:18:37 nas weewx[8677]: engine: Loading service weewx.restx.StdWunderground
Apr 29 19:18:37 nas weewx[8677]: restx: WU essentials: {}
Apr 29 19:18:37 nas weewx[8677]: restx: Wunderground-PWS: Data for station XXXXXX will be posted
Apr 29 19:18:37 nas weewx[8677]: engine: Finished loading service weewx.restx.StdWunderground
Apr 29 19:18:37 nas weewx[8677]: engine: Loading service weewx.restx.StdPWSweather
Apr 29 19:18:37 nas weewx[8677]: restx: PWSweather: Posting not enabled.
Apr 29 19:18:37 nas weewx[8677]: engine: Finished loading service weewx.restx.StdPWSweather
Apr 29 19:18:37 nas weewx[8677]: engine: Loading service weewx.restx.StdCWOP
Apr 29 19:18:37 nas weewx[8677]: restx: CWOP: Posting not enabled.
Apr 29 19:18:37 nas weewx[8677]: engine: Finished loading service weewx.restx.StdCWOP
Apr 29 19:18:37 nas weewx[8677]: engine: Loading service weewx.restx.StdWOW
Apr 29 19:18:37 nas weewx[8677]: restx: WOW: Posting not enabled.
Apr 29 19:18:37 nas weewx[8677]: engine: Finished loading service weewx.restx.StdWOW
Apr 29 19:18:37 nas weewx[8677]: engine: Loading service weewx.restx.StdAWEKAS
Apr 29 19:18:37 nas weewx[8677]: restx: AWEKAS: Posting not enabled.
Apr 29 19:18:37 nas weewx[8677]: engine: Finished loading service weewx.restx.StdAWEKAS
Apr 29 19:18:37 nas weewx[8677]: engine: Loading service weewx.engine.StdPrint
Apr 29 19:18:37 nas weewx[8677]: engine: Finished loading service weewx.engine.StdPrint
Apr 29 19:18:37 nas weewx[8677]: engine: Loading service weewx.engine.StdReport
Apr 29 19:18:37 nas weewx[8677]: engine: Finished loading service weewx.engine.StdReport
Apr 29 19:18:37 nas weewx[8677]: engine: Starting up weewx version 3.9.1
Apr 29 19:18:37 nas weewx[8677]: manager: Daily summary version is 2.0
Apr 29 19:18:38 nas weewx[8677]: vantage: Gentle wake up of console successful
Apr 29 19:18:38 nas weewx[8677]: engine: Clock error is 1.32 seconds (positive is fast)
Apr 29 19:18:38 nas weewx[8677]: vantage: Getting archive packets since 2019-04-29 19:00:00 CEST (1556557200)
Apr 29 19:18:39 nas weewx[8677]: vantage: Gentle wake up of console successful
Apr 29 19:18:40 nas weewx[8677]: vantage: Retrieving 0 page(s); starting index= 0
Apr 29 19:18:40 nas weewx[8677]: engine: Starting main packet loop.
Apr 29 19:18:40 nas weewx[8677]: vantage: Gentle wake up of console successful
Apr 29 19:18:41 nas weewx[8677]: vantage: Requesting 200 LOOP packets.
Apr 29 19:18:41 nas weewx[8677]: vantage: Gentle wake up of console successful
Apr 29 19:19:07 nas weewx[8677]: vantage: ip-read error: timed out
Apr 29 19:19:07 nas weewx[8677]: vantage: LOOP try #1; error: timed out
Apr 29 19:19:07 nas weewx[8677]: vantage: Requesting 200 LOOP packets.
Apr 29 19:19:07 nas weewx[8677]: vantage: Gentle wake up of console successful

Offline pfletch101

  • Senior Contributor
  • ****
  • Posts: 295
    • Personal Website
Re: Hardware config in weewx.conf using wifi logger
« Reply #3 on: April 29, 2019, 01:52:35 PM »
Your initial weewx error report was (AFAICR) identical to what I saw before I corrected the WiFiLogger settings. The new one is different to anything I have seen, and certainly does suggest that something else is going on (or not going on!). However, the weewx.conf settings you show in your initial post for your [Vantage] section are identical to mine. The only other setting in weewx.conf that could remotely be relevant would seem to be the socket_timeout setting in the general configuration section. Mine is set to 20 (which I think was the default); it might be worth your trying lengthening that.
Just one other thought: how old is your console? If weewx is trying to get LOOP2 packets out of a console that does not have the newer firmware that supports these, problems are likely!
Vantage Pro 2+ with WeatherLink - data incorporated in domestic energy production (PV) and use monitoring system.

Offline cwuthenow

  • Member
  • *
  • Posts: 5
Re: Hardware config in weewx.conf using wifi logger
« Reply #4 on: May 02, 2019, 12:12:57 AM »
Hi, short update. I tried to update the firmware as using 1.8 is most probably not working with the wifi logger. Unfortunately the version I flashed is not compatible with my hardware. I just received the confirmation from the Davis support. The Envoy is only beeping once after rebooting, meaning it does not recognize the wifi logger. The wifi logger shows that it is not able to connect to the station and cannot find one. So I ordered a new Envoy. Hopefully that solves the connection issue. Keep you updated. Most probably I will send the old station to Davis and ask them to flash it back to the working firmware then.

Offline johnd

  • Forecaster
  • *****
  • Posts: 3299
    • www.weatherstations.co.uk
Re: Hardware config in weewx.conf using wifi logger
« Reply #5 on: May 02, 2019, 03:56:58 AM »
Probably too late now, but what's the Mfg Code of your old Envoy? Assuming that it's not too ancient then it should be able to accept v1.90 firmware which is compatible with WFL and available from Davis support via email.
Prodata Weather Systems
Prodata's dedicated Davis EnviroMonitor website
UK Davis Premier Dealer - All Davis stations, accessories and spares
Littleport, Ely, Cambs UK

Offline cwuthenow

  • Member
  • *
  • Posts: 5
Re: Hardware config in weewx.conf using wifi logger
« Reply #6 on: May 04, 2019, 01:13:04 AM »
Hi, the manufacturing code of my Envoy 6316EU is A90108N104.

Cheers!


 

anything