Raspberry Pi, weewx, WH1081 - Problem with webpages being generated

Peter Hurn

unread,

Jan 8, 2014, 1:32:17 PM1/8/14

to weewx...@googlegroups.com

Hello,

I have studied the manual, then attempted to install and run weewx 2.5.1 on my Raspberry Pi which is running Raspbian 20/12/2013 (Debian) based on kernel 3.10, this is installed on a 4GB SD card to start with, clean image.

The Raspberry Pi is connected to a TV via HDMI and a powered hub which has a keyboard and the WH1081 receiver attached to it to stop any power dips to the Raspberry Pi.

I have also reset the WH1081 and removed the batteries so it's currently running from the USB power supply.

Before starting I checked the station was visible from the Raspberry Pi with a lsusb,

Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.

Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB

Bus 001 Device 006: ID 1941:8021 Dream Link WH1080 Weather Station / USB Missile Launcher

Bus 001 Device 005: ID 046d:c30a Logitech, Inc. iTouch Composite

I installed weewx following the "Installation using setup.py" under the default user "pi" and used sudo where prompted as the instructions seemed to suggest you wouldn't need to be logged in as root all the time with weewx creating the necessary folders when needed. i.e. public_html

# required packages:

sudo apt-get install python-configobj

sudo apt-get install python-cheetah

sudo apt-get install python-imaging

# required if hardware is serial or USB:

sudo apt-get install python-serial

sudo apt-get install python-usb

# required if using MySQL:

sudo apt-get install mysql-client

sudo apt-get install python-mysqldb

# optional for extended almanac information:

sudo apt-get install python-dev

sudo apt-get install python-pip

sudo pip install pyephem

# Decided to install apache2 at this point.

sudo apt-get install apache2

# Downloaded version 2.5.1 of weewx

wget http://downloads.sourceforge.net/project/weewx/weewx-2.5.1.tar.gz

tar -xvf weewx-2.5.1.tar.gz

cd weewx-2.5.1

./setup.py build

sudo ./setup.py install

# Change configuration options

sudo nano /home/weewx/weewx.conf

# Changed location name, lon, lat and station type to FineOffsetUSB

# Copied Apache settings

cd /home/weewx

sudo cp util/apache/conf.d/weewx.conf /etc/apache2/conf.d

sudo /etc/init.d/apache2 restart

# Set weewx to run as a service

cd /home/weewx

sudo cp util/init.d/weewx.debian /etc/init.d/weewx

sudo chmod +x /etc/init.d/weewx

sudo update-rc.d weewx defaults 98

sudo /etc/init.d/weewx start

#Check end of syslog for errors

sudo tail -f /var/log/syslog

Whilst I have had success with weewx reading the station receiver weewx hasn't created any public_html folder, Apache is running as I can navigate to the "It works!" page from a separate browser on a PC on the same network.

Follows is a snip from my syslog file with debug set to 1 in the /home/weewx.conf file.

Any help gratefully appreciated.

Peter.

Jan 8 18:26:25 raspberrypi shutdown[2285]: shutting down for system reboot

Jan 8 18:26:25 raspberrypi init: Switching to runlevel: 6

Jan 8 18:26:25 raspberrypi weewx[2163]: fousb: delay 1, pause 0.5

Jan 8 18:26:26 raspberrypi weewx[2163]: fousb: delay 1, pause 0.5

Jan 8 18:26:26 raspberrypi ifplugd(eth0)[1612]: Exiting.

Jan 8 18:26:26 raspberrypi weewx[2163]: fousb: delay 1, pause 0.5

Jan 8 18:26:27 raspberrypi weewx[2163]: fousb: delay 1, pause 0.5

Jan 8 18:26:27 raspberrypi weewx[2163]: wxengine: Received signal TERM.

Jan 8 18:26:27 raspberrypi weewx[2163]: wxengine: Terminating weewx version 2.5.1

Jan 8 18:26:27 raspberrypi ifplugd(lo)[1579]: Exiting.

Jan 8 18:26:27 raspberrypi ntpd[2093]: ntpd exiting on signal 15

Jan 8 18:26:39 raspberrypi kernel: imklog 5.8.11, log source = /proc/kmsg started.

Jan 8 18:26:39 raspberrypi rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="1829" x-info="http://www.rsyslog.com"] start

Jan 8 18:26:39 raspberrypi dhclient: Listening on LPF/eth0/b8:27:eb:cc:7a:90

Jan 8 18:26:39 raspberrypi ifplugd(eth0)[1610]: client: Listening on LPF/eth0/b8:27:eb:cc:7a:90

Jan 8 18:26:39 raspberrypi dhclient: Sending on LPF/eth0/b8:27:eb:cc:7a:90

Jan 8 18:26:39 raspberrypi ifplugd(eth0)[1610]: client: Sending on LPF/eth0/b8:27:eb:cc:7a:90

Jan 8 18:26:39 raspberrypi dhclient: Sending on Socket/fallback

Jan 8 18:26:39 raspberrypi ifplugd(eth0)[1610]: client: Sending on Socket/fallback

Jan 8 18:26:39 raspberrypi dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7

Jan 8 18:26:39 raspberrypi ifplugd(eth0)[1610]: client: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] Booting Linux on physical CPU 0x0

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] Initializing cgroup subsys cpu

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] Initializing cgroup subsys cpuacct

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] Linux version 3.10.24+ (dc4@dc4-arm-01) (gcc version 4.7.2 20120731 (prerelease) (crosstool-NG linaro-1.13.1+bzr2458 - Linaro GCC 2012.08) ) #614 PREEMPT Thu Dec 19 20:38:42 GMT 2013

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] CPU: ARMv6-compatible processor [410fb767] revision 7 (ARMv7), cr=00c5387d

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] Machine: BCM2708

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] cma: CMA: reserved 16 MiB at 0b000000

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] Memory policy: ECC disabled, Data cache writeback

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] On node 0 totalpages: 49152

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] free_area_init_node: node 0, pgdat c05cfd5c, node_mem_map c067d000

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] Normal zone: 384 pages used for memmap

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] Normal zone: 0 pages reserved

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] Normal zone: 49152 pages, LIFO batch:15

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] pcpu-alloc: [0] 0

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 48768

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] Kernel command line: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2708.boardrev=0x2 bcm2708.serial=0xb2cc7a90 smsc95xx.macaddr=B8:27:EB:CC:7A:90 sdhci-bcm2708.emmc_clock_freq=250000000 vc_mem.mem_base=0xec00000 vc_mem.mem_size=0x10000000 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] Memory: 192MB = 192MB total

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] Memory: 171756k/171756k available, 24852k reserved, 0K highmem

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] Virtual kernel memory layout:

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] vmalloc : 0xcc800000 - 0xff000000 ( 808 MB)

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] lowmem : 0xc0000000 - 0xcc000000 ( 192 MB)

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] .text : 0xc0008000 - 0xc0571798 (5542 kB)

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] .init : 0xc0572000 - 0xc0596324 ( 145 kB)

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] .data : 0xc0598000 - 0xc05d0870 ( 227 kB)

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] .bss : 0xc05d0870 - 0xc067c3e0 ( 687 kB)

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] Preemptible hierarchical RCU implementation.

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] NR_IRQS:330

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] sched_clock: 32 bits at 1000kHz, resolution 1000ns, wraps every 4294967ms

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] Switching to timer-based delay loop

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] Console: colour dummy device 80x30

Jan 8 18:26:39 raspberrypi kernel: [ 0.000000] console [tty1] enabled

Jan 8 18:26:39 raspberrypi kernel: [ 0.001160] Calibrating delay loop (skipped), value calculated using timer frequency.. 2.00 BogoMIPS (lpj=10000)

Jan 8 18:26:39 raspberrypi kernel: [ 0.001223] pid_max: default: 32768 minimum: 301

Jan 8 18:26:39 raspberrypi kernel: [ 0.001679] Mount-cache hash table entries: 512

Jan 8 18:26:39 raspberrypi kernel: [ 0.002470] Initializing cgroup subsys memory

Jan 8 18:26:39 raspberrypi kernel: [ 0.002579] Initializing cgroup subsys devices

Jan 8 18:26:39 raspberrypi kernel: [ 0.002620] Initializing cgroup subsys freezer

Jan 8 18:26:39 raspberrypi kernel: [ 0.002654] Initializing cgroup subsys blkio

Jan 8 18:26:39 raspberrypi kernel: [ 0.002813] CPU: Testing write buffer coherency: ok

Jan 8 18:26:39 raspberrypi kernel: [ 0.003293] Setting up static identity map for 0xc0405da8 - 0xc0405e04

Jan 8 18:26:39 raspberrypi kernel: [ 0.005119] devtmpfs: initialized

Jan 8 18:26:39 raspberrypi kernel: [ 0.019562] NET: Registered protocol family 16

Jan 8 18:26:39 raspberrypi kernel: [ 0.025489] DMA: preallocated 4096 KiB pool for atomic coherent allocations

Jan 8 18:26:39 raspberrypi kernel: [ 0.026592] bcm2708.uart_clock = 0

Jan 8 18:26:39 raspberrypi kernel: [ 0.028350] hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.

Jan 8 18:26:39 raspberrypi kernel: [ 0.028406] hw-breakpoint: maximum watchpoint size is 4 bytes.

Jan 8 18:26:39 raspberrypi kernel: [ 0.028443] mailbox: Broadcom VideoCore Mailbox driver

Jan 8 18:26:39 raspberrypi kernel: [ 0.028542] bcm2708_vcio: mailbox at f200b880

Jan 8 18:26:39 raspberrypi kernel: [ 0.028648] bcm_power: Broadcom power driver

Jan 8 18:26:39 raspberrypi kernel: [ 0.028689] bcm_power_open() -> 0

Jan 8 18:26:39 raspberrypi kernel: [ 0.028716] bcm_power_request(0, 8)

Jan 8 18:26:39 raspberrypi kernel: [ 0.529438] bcm_mailbox_read -> 00000080, 0

Jan 8 18:26:39 raspberrypi kernel: [ 0.529481] bcm_power_request -> 0

Jan 8 18:26:39 raspberrypi kernel: [ 0.529709] Serial: AMBA PL011 UART driver

Jan 8 18:26:39 raspberrypi kernel: [ 0.529881] dev:f1: ttyAMA0 at MMIO 0x20201000 (irq = 83) is a PL011 rev3

Jan 8 18:26:39 raspberrypi kernel: [ 0.871926] console [ttyAMA0] enabled

Jan 8 18:26:39 raspberrypi kernel: [ 0.897796] bio: create slab <bio-0> at 0

Jan 8 18:26:39 raspberrypi kernel: [ 0.903114] SCSI subsystem initialized

Jan 8 18:26:39 raspberrypi kernel: [ 0.907089] usbcore: registered new interface driver usbfs

Jan 8 18:26:39 raspberrypi kernel: [ 0.912795] usbcore: registered new interface driver hub

Jan 8 18:26:39 raspberrypi kernel: [ 0.918393] usbcore: registered new device driver usb

Jan 8 18:26:39 raspberrypi kernel: [ 0.924987] Switching to clocksource stc

Jan 8 18:26:39 raspberrypi kernel: [ 0.929318] FS-Cache: Loaded

Jan 8 18:26:39 raspberrypi kernel: [ 0.932491] CacheFiles: Loaded

Jan 8 18:26:39 raspberrypi kernel: [ 0.948360] NET: Registered protocol family 2

Jan 8 18:26:39 raspberrypi kernel: [ 0.953780] TCP established hash table entries: 2048 (order: 2, 16384 bytes)

Jan 8 18:26:39 raspberrypi kernel: [ 0.960997] TCP bind hash table entries: 2048 (order: 1, 8192 bytes)

Jan 8 18:26:39 raspberrypi kernel: [ 0.967403] TCP: Hash tables configured (established 2048 bind 2048)

Jan 8 18:26:39 raspberrypi kernel: [ 0.973875] TCP: reno registered

Jan 8 18:26:39 raspberrypi kernel: [ 0.977133] UDP hash table entries: 256 (order: 0, 4096 bytes)

Jan 8 18:26:39 raspberrypi kernel: [ 0.983040] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)

Jan 8 18:26:39 raspberrypi kernel: [ 0.989780] NET: Registered protocol family 1

Jan 8 18:26:39 raspberrypi kernel: [ 0.994708] RPC: Registered named UNIX socket transport module.

Jan 8 18:26:39 raspberrypi kernel: [ 1.000774] RPC: Registered udp transport module.

Jan 8 18:26:39 raspberrypi kernel: [ 1.005499] RPC: Registered tcp transport module.

Jan 8 18:26:39 raspberrypi kernel: [ 1.010250] RPC: Registered tcp NFSv4.1 backchannel transport module.

Jan 8 18:26:39 raspberrypi kernel: [ 1.017601] bcm2708_dma: DMA manager at f2007000

Jan 8 18:26:39 raspberrypi kernel: [ 1.022424] bcm2708_gpio: bcm2708_gpio_probe c05a5e50

Jan 8 18:26:39 raspberrypi kernel: [ 1.027876] vc-mem: phys_addr:0x00000000 mem_base=0x0ec00000 mem_size:0x10000000(256 MiB)

Jan 8 18:26:39 raspberrypi kernel: [ 1.037239] audit: initializing netlink socket (disabled)

Jan 8 18:26:39 raspberrypi kernel: [ 1.042920] type=2000 audit(0.890:1): initialized

Jan 8 18:26:39 raspberrypi kernel: [ 1.204696] VFS: Disk quotas dquot_6.5.2

Jan 8 18:26:39 raspberrypi kernel: [ 1.209084] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)

Jan 8 18:26:39 raspberrypi kernel: [ 1.217910] FS-Cache: Netfs 'nfs' registered for caching

Jan 8 18:26:39 raspberrypi kernel: [ 1.224652] NFS: Registering the id_resolver key type

Jan 8 18:26:39 raspberrypi kernel: [ 1.229948] Key type id_resolver registered

Jan 8 18:26:39 raspberrypi kernel: [ 1.234160] Key type id_legacy registered

Jan 8 18:26:39 raspberrypi kernel: [ 1.238907] msgmni has been set to 367

Jan 8 18:26:39 raspberrypi kernel: [ 1.244834] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)

Jan 8 18:26:39 raspberrypi kernel: [ 1.252690] io scheduler noop registered

Jan 8 18:26:39 raspberrypi kernel: [ 1.256650] io scheduler deadline registered (default)

Jan 8 18:26:39 raspberrypi kernel: [ 1.262240] io scheduler cfq registered

Jan 8 18:26:39 raspberrypi kernel: [ 1.267512] BCM2708FB: allocated DMA memory 4b400000

Jan 8 18:26:39 raspberrypi kernel: [ 1.272652] BCM2708FB: allocated DMA channel 0 @ f2007000

Jan 8 18:26:39 raspberrypi kernel: [ 1.313946] Console: switching to colour frame buffer device 228x61

Jan 8 18:26:39 raspberrypi kernel: [ 1.334578] uart-pl011 dev:f1: no DMA platform data

Jan 8 18:26:39 raspberrypi kernel: [ 1.339671] kgdb: Registered I/O driver kgdboc.

Jan 8 18:26:39 raspberrypi kernel: [ 1.344972] vc-cma: Videocore CMA driver

Jan 8 18:26:39 raspberrypi kernel: [ 1.349064] vc-cma: vc_cma_base = 0x00000000

Jan 8 18:26:39 raspberrypi kernel: [ 1.353861] vc-cma: vc_cma_size = 0x00000000 (0 MiB)

Jan 8 18:26:39 raspberrypi kernel: [ 1.359446] vc-cma: vc_cma_initial = 0x00000000 (0 MiB)

Jan 8 18:26:39 raspberrypi kernel: [ 1.374640] brd: module loaded

Jan 8 18:26:39 raspberrypi kernel: [ 1.383231] loop: module loaded

Jan 8 18:26:39 raspberrypi kernel: [ 1.386762] vchiq: vchiq_init_state: slot_zero = 0xcb000000, is_master = 0

Jan 8 18:26:39 raspberrypi kernel: [ 1.394890] Loading iSCSI transport class v2.0-870.

Jan 8 18:26:39 raspberrypi kernel: [ 1.401022] usbcore: registered new interface driver smsc95xx

Jan 8 18:26:39 raspberrypi kernel: [ 1.406980] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)

Jan 8 18:26:39 raspberrypi kernel: [ 1.613242] Core Release: 2.80a

Jan 8 18:26:39 raspberrypi kernel: [ 1.616497] Setting default values for core params

Jan 8 18:26:39 raspberrypi kernel: [ 1.621510] Finished setting default values for core params

Jan 8 18:26:39 raspberrypi kernel: [ 1.827265] Using Buffer DMA mode

Jan 8 18:26:39 raspberrypi kernel: [ 1.830704] Periodic Transfer Interrupt Enhancement - disabled

Jan 8 18:26:39 raspberrypi kernel: [ 1.836641] Multiprocessor Interrupt Enhancement - disabled

Jan 8 18:26:39 raspberrypi kernel: [ 1.842349] OTG VER PARAM: 0, OTG VER FLAG: 0

Jan 8 18:26:39 raspberrypi kernel: [ 1.846798] Dedicated Tx FIFOs mode

Jan 8 18:26:39 raspberrypi kernel: [ 1.850947] dwc_otg: Microframe scheduler enabled

Jan 8 18:26:39 raspberrypi kernel: [ 1.851186] dwc_otg bcm2708_usb: DWC OTG Controller

Jan 8 18:26:39 raspberrypi kernel: [ 1.856233] dwc_otg bcm2708_usb: new USB bus registered, assigned bus number 1

Jan 8 18:26:39 raspberrypi kernel: [ 1.863706] dwc_otg bcm2708_usb: irq 32, io mem 0x00000000

Jan 8 18:26:39 raspberrypi kernel: [ 1.869426] Init: Port Power? op_state=1

Jan 8 18:26:39 raspberrypi kernel: [ 1.873432] Init: Power Port (0)

Jan 8 18:26:39 raspberrypi kernel: [ 1.876857] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002

Jan 8 18:26:39 raspberrypi kernel: [ 1.888012] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1

Jan 8 18:26:39 raspberrypi kernel: [ 1.899505] usb usb1: Product: DWC OTG Controller

Jan 8 18:26:39 raspberrypi kernel: [ 1.908375] usb usb1: Manufacturer: Linux 3.10.24+ dwc_otg_hcd

Jan 8 18:26:39 raspberrypi kernel: [ 1.918414] usb usb1: SerialNumber: bcm2708_usb

Jan 8 18:26:39 raspberrypi kernel: [ 1.928005] hub 1-0:1.0: USB hub found

Jan 8 18:26:39 raspberrypi kernel: [ 1.936024] hub 1-0:1.0: 1 port detected

Jan 8 18:26:39 raspberrypi kernel: [ 1.944598] dwc_otg: FIQ enabled

Jan 8 18:26:39 raspberrypi kernel: [ 1.944620] dwc_otg: NAK holdoff enabled

Jan 8 18:26:39 raspberrypi kernel: [ 1.944632] dwc_otg: FIQ split fix enabled

Jan 8 18:26:39 raspberrypi kernel: [ 1.944654] Module dwc_common_port init

Jan 8 18:26:39 raspberrypi kernel: [ 1.945120] usbcore: registered new interface driver usb-storage

Jan 8 18:26:39 raspberrypi kernel: [ 1.955867] mousedev: PS/2 mouse device common for all mice

Jan 8 18:26:39 raspberrypi kernel: [ 1.966452] bcm2835-cpufreq: min=700000 max=700000 cur=700000

Jan 8 18:26:39 raspberrypi kernel: [ 1.976711] bcm2835-cpufreq: switching to governor powersave

Jan 8 18:26:39 raspberrypi kernel: [ 1.986724] bcm2835-cpufreq: switching to governor powersave

Jan 8 18:26:39 raspberrypi kernel: [ 1.996616] cpuidle: using governor ladder

Jan 8 18:26:39 raspberrypi kernel: [ 2.004715] cpuidle: using governor menu

Jan 8 18:26:39 raspberrypi kernel: [ 2.012793] sdhci: Secure Digital Host Controller Interface driver

Jan 8 18:26:39 raspberrypi kernel: [ 2.022964] sdhci: Copyright(c) Pierre Ossman

Jan 8 18:26:39 raspberrypi kernel: [ 2.031484] sdhci: Enable low-latency mode

Jan 8 18:26:39 raspberrypi kernel: [ 2.079024] mmc0: SDHCI controller on BCM2708_Arasan [platform] using platform's DMA

Jan 8 18:26:39 raspberrypi kernel: [ 2.091140] mmc0: BCM2708 SDHC host at 0x20300000 DMA 2 IRQ 77

Jan 8 18:26:39 raspberrypi kernel: [ 2.101395] sdhci-pltfm: SDHCI platform and OF driver helper

Jan 8 18:26:39 raspberrypi kernel: [ 2.113380] ledtrig-cpu: registered to indicate activity on CPUs

Jan 8 18:26:39 raspberrypi kernel: [ 2.130965] hidraw: raw HID events driver (C) Jiri Kosina

Jan 8 18:26:39 raspberrypi kernel: [ 2.140730] Indeed it is in host mode hprt0 = 00021501

Jan 8 18:26:39 raspberrypi kernel: [ 2.152460] usbcore: registered new interface driver usbhid

Jan 8 18:26:39 raspberrypi kernel: [ 2.169072] usbhid: USB HID core driver

Jan 8 18:26:39 raspberrypi kernel: [ 2.192742] TCP: cubic registered

Jan 8 18:26:39 raspberrypi kernel: [ 2.209003] Initializing XFRM netlink socket

Jan 8 18:26:39 raspberrypi kernel: [ 2.217420] NET: Registered protocol family 17

Jan 8 18:26:39 raspberrypi kernel: [ 2.240513] mmc0: new high speed SDHC card at address aaaa

Jan 8 18:26:39 raspberrypi kernel: [ 2.259183] Key type dns_resolver registered

Jan 8 18:26:39 raspberrypi kernel: [ 2.279086] mmcblk0: mmc0:aaaa SU04G 3.69 GiB

Jan 8 18:26:39 raspberrypi kernel: [ 2.268061] VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5

Jan 8 18:26:39 raspberrypi kernel: [ 2.306602] mmcblk0: p1 p2

Jan 8 18:26:39 raspberrypi kernel: [ 2.313937] registered taskstats version 1

Jan 8 18:26:39 raspberrypi kernel: [ 2.323460] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)

Jan 8 18:26:39 raspberrypi kernel: [ 2.356637] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)

Jan 8 18:26:39 raspberrypi kernel: [ 2.369562] VFS: Mounted root (ext4 filesystem) on device 179:2.

Jan 8 18:26:39 raspberrypi kernel: [ 2.381166] devtmpfs: mounted

Jan 8 18:26:39 raspberrypi kernel: [ 2.389084] Freeing unused kernel memory: 144K (c0572000 - c0596000)

Jan 8 18:26:39 raspberrypi kernel: [ 2.429101] usb 1-1: new high-speed USB device number 2 using dwc_otg

Jan 8 18:26:39 raspberrypi kernel: [ 2.440998] Indeed it is in host mode hprt0 = 00001101

Jan 8 18:26:39 raspberrypi kernel: [ 2.649576] usb 1-1: New USB device found, idVendor=0424, idProduct=9512

Jan 8 18:26:39 raspberrypi kernel: [ 2.661310] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0

Jan 8 18:26:39 raspberrypi kernel: [ 2.674184] hub 1-1:1.0: USB hub found

Jan 8 18:26:39 raspberrypi kernel: [ 2.684543] hub 1-1:1.0: 3 ports detected

Jan 8 18:26:39 raspberrypi kernel: [ 2.969441] usb 1-1.1: new high-speed USB device number 3 using dwc_otg

Jan 8 18:26:39 raspberrypi kernel: [ 3.089789] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00

Jan 8 18:26:39 raspberrypi kernel: [ 3.113297] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0

Jan 8 18:26:39 raspberrypi kernel: [ 3.133185] smsc95xx v1.0.4

Jan 8 18:26:39 raspberrypi kernel: [ 3.215005] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:cc:7a:90

Jan 8 18:26:39 raspberrypi kernel: [ 3.329350] usb 1-1.3: new high-speed USB device number 4 using dwc_otg

Jan 8 18:26:39 raspberrypi kernel: [ 3.440456] usb 1-1.3: New USB device found, idVendor=1a40, idProduct=0101

Jan 8 18:26:39 raspberrypi kernel: [ 3.464126] usb 1-1.3: New USB device strings: Mfr=0, Product=1, SerialNumber=0

Jan 8 18:26:39 raspberrypi kernel: [ 3.489234] usb 1-1.3: Product: USB 2.0 Hub

Jan 8 18:26:39 raspberrypi kernel: [ 3.509991] hub 1-1.3:1.0: USB hub found

Jan 8 18:26:39 raspberrypi kernel: [ 3.527472] hub 1-1.3:1.0: 4 ports detected

Jan 8 18:26:39 raspberrypi kernel: [ 3.829403] usb 1-1.3.3: new low-speed USB device number 5 using dwc_otg

Jan 8 18:26:39 raspberrypi kernel: [ 3.978299] usb 1-1.3.3: New USB device found, idVendor=1941, idProduct=8021

Jan 8 18:26:39 raspberrypi kernel: [ 3.996488] usb 1-1.3.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0

Jan 8 18:26:39 raspberrypi kernel: [ 4.046650] hid-generic 0003:1941:8021.0001: hiddev0,hidraw0: USB HID v1.00 Device [HID 1941:8021] on usb-bcm2708_usb-1.3.3/input0

Jan 8 18:26:39 raspberrypi kernel: [ 4.159454] usb 1-1.3.4: new low-speed USB device number 6 using dwc_otg

Jan 8 18:26:39 raspberrypi kernel: [ 4.302582] usb 1-1.3.4: New USB device found, idVendor=046d, idProduct=c30a

Jan 8 18:26:39 raspberrypi kernel: [ 4.335273] usb 1-1.3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0

Jan 8 18:26:39 raspberrypi kernel: [ 4.384467] usb 1-1.3.4: Product: Logitech USB Keyboard

Jan 8 18:26:39 raspberrypi kernel: [ 4.409210] usb 1-1.3.4: Manufacturer: Logitech

Jan 8 18:26:39 raspberrypi kernel: [ 5.243530] input: Logitech Logitech USB Keyboard as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3.4/1-1.3.4:1.0/input/input0

Jan 8 18:26:39 raspberrypi kernel: [ 5.457575] logitech 0003:046D:C30A.0002: input,hidraw1: USB HID v1.10 Keyboard [Logitech Logitech USB Keyboard] on usb-bcm2708_usb-1.3.4/input0

Jan 8 18:26:39 raspberrypi kernel: [ 5.731894] input: Logitech Logitech USB Keyboard as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3.4/1-1.3.4:1.1/input/input1

Jan 8 18:26:39 raspberrypi kernel: [ 5.881471] logitech 0003:046D:C30A.0003: input,hidraw2: USB HID v1.10 Mouse [Logitech Logitech USB Keyboard] on usb-bcm2708_usb-1.3.4/input1

Jan 8 18:26:39 raspberrypi kernel: [ 6.648607] bcm2708-i2s bcm2708-i2s.0: Failed to create debugfs directory

Jan 8 18:26:39 raspberrypi kernel: [ 10.442830] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)

Jan 8 18:26:39 raspberrypi kernel: [ 10.963284] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)

Jan 8 18:26:39 raspberrypi kernel: [ 16.975872] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

Jan 8 18:26:39 raspberrypi kernel: [ 20.233621] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup

Jan 8 18:26:39 raspberrypi kernel: [ 21.751213] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1

Jan 8 18:26:40 raspberrypi dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67

Jan 8 18:26:40 raspberrypi ifplugd(eth0)[1610]: client: DHCPREQUEST on eth0 to 255.255.255.255 port 67

Jan 8 18:26:40 raspberrypi dhclient: DHCPOFFER from 192.168.1.1

Jan 8 18:26:40 raspberrypi ifplugd(eth0)[1610]: client: DHCPOFFER from 192.168.1.1

Jan 8 18:26:40 raspberrypi dhclient: DHCPACK from 192.168.1.1

Jan 8 18:26:40 raspberrypi ifplugd(eth0)[1610]: client: DHCPACK from 192.168.1.1

Jan 8 18:26:40 raspberrypi dhclient: bound to 192.168.1.18 -- renewal in 107420 seconds.

Jan 8 18:26:40 raspberrypi ifplugd(eth0)[1610]: client: bound to 192.168.1.18 -- renewal in 107420 seconds.

Jan 8 18:26:41 raspberrypi ifplugd(eth0)[1610]: Program executed successfully.

Jan 8 18:26:42 raspberrypi /usr/sbin/cron[2037]: (CRON) INFO (pidfile fd = 3)

Jan 8 18:26:42 raspberrypi /usr/sbin/cron[2038]: (CRON) STARTUP (fork ok)

Jan 8 18:26:42 raspberrypi /usr/sbin/cron[2038]: (CRON) INFO (Running @reboot jobs)

Jan 8 18:26:42 raspberrypi kernel: [ 25.830158] Adding 102396k swap on /var/swap. Priority:-1 extents:1 across:102396k SSFS

Jan 8 18:26:43 raspberrypi ntpd[2085]: ntpd 4.2...@1.2349-o Fri May 18 20:30:57 UTC 2012 (1)

Jan 8 18:26:43 raspberrypi ntpd[2092]: proto: precision = 1.000 usec

Jan 8 18:26:43 raspberrypi ntpd[2092]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123

Jan 8 18:26:43 raspberrypi ntpd[2092]: Listen normally on 1 lo 127.0.0.1 UDP 123

Jan 8 18:26:43 raspberrypi ntpd[2092]: Listen normally on 2 eth0 192.168.1.18 UDP 123

Jan 8 18:26:43 raspberrypi ntpd[2092]: peers refreshed

Jan 8 18:26:43 raspberrypi ntpd[2092]: Listening on routing socket on fd #19 for interface updates

Jan 8 18:26:43 raspberrypi ntpd[2092]: restrict: error in address '::' on line 38. Ignoring...

Jan 8 18:26:43 raspberrypi ntpd[2092]: restrict: error in address '::1' on line 42. Ignoring...

Jan 8 18:26:45 raspberrypi weewx[2160]: wxengine: Initializing weewx version 2.5.1

Jan 8 18:26:45 raspberrypi weewx[2160]: wxengine: Using Python 2.7.3 (default, Jan 13 2013, 11:20:46) #012[GCC 4.6.3]

Jan 8 18:26:45 raspberrypi weewx[2160]: wxengine: pid file is /var/run/weewx.pid

Jan 8 18:26:46 raspberrypi weewx[2162]: wxengine: Using configuration file /home/weewx/weewx.conf

Jan 8 18:26:46 raspberrypi weewx[2162]: wxengine: Loading station type FineOffsetUSB (weewx.drivers.fousb)

Jan 8 18:26:46 raspberrypi weewx[2162]: fousb: driver version is 1.4

Jan 8 18:26:46 raspberrypi weewx[2162]: fousb: polling mode is PERIODIC

Jan 8 18:26:46 raspberrypi weewx[2162]: fousb: polling interval is 60

Jan 8 18:26:46 raspberrypi weewx[2162]: fousb: altitude is 213.36 meters

Jan 8 18:26:46 raspberrypi weewx[2162]: fousb: pressure offset is 0.0

Jan 8 18:26:46 raspberrypi weewx[2162]: fousb: found station on USB bus=001 device=005

Jan 8 18:26:46 raspberrypi weewx[2162]: wxengine: Loading service weewx.wxengine.StdTimeSynch

Jan 8 18:26:46 raspberrypi weewx[2162]: wxengine: Finished loading service weewx.wxengine.StdTimeSynch

Jan 8 18:26:46 raspberrypi weewx[2162]: wxengine: Loading service weewx.wxengine.StdConvert

Jan 8 18:26:46 raspberrypi weewx[2162]: wxengine: StdConvert target unit is 0x1

Jan 8 18:26:46 raspberrypi weewx[2162]: wxengine: Finished loading service weewx.wxengine.StdConvert

Jan 8 18:26:46 raspberrypi weewx[2162]: wxengine: Loading service weewx.wxengine.StdCalibrate

Jan 8 18:26:46 raspberrypi weewx[2162]: wxengine: Finished loading service weewx.wxengine.StdCalibrate

Jan 8 18:26:46 raspberrypi weewx[2162]: wxengine: Loading service weewx.wxengine.StdQC

Jan 8 18:26:46 raspberrypi weewx[2162]: wxengine: Finished loading service weewx.wxengine.StdQC

Jan 8 18:26:46 raspberrypi weewx[2162]: wxengine: Loading service weewx.wxengine.StdArchive

Jan 8 18:26:46 raspberrypi weewx[2162]: wxengine: Record generation will be attempted in 'hardware'

Jan 8 18:26:47 raspberrypi weewx[2162]: fousb: unstable read: blocks differ for ptr 0x000060

Jan 8 18:26:47 raspberrypi weewx[2162]: fousb: unrecognised magic number 00aa

Jan 8 18:26:47 raspberrypi weewx[2162]: wxengine: The archive interval in the configuration file (300) does not match the station hardware interval (1800).

Jan 8 18:26:47 raspberrypi weewx[2162]: wxengine: Using archive interval of 1800 seconds

Jan 8 18:26:47 raspberrypi weewx[2162]: wxengine: Use LOOP data in hi/low calculations: 1

Jan 8 18:26:48 raspberrypi weewx[2162]: wxengine: Using archive database: archive_sqlite

Jan 8 18:26:48 raspberrypi weewx[2162]: stats: Schema exists with 16 elements

Jan 8 18:26:48 raspberrypi weewx[2162]: stats: Backfilling stats database.

Jan 8 18:26:48 raspberrypi weewx[2162]: stats: stats database up to date.

Jan 8 18:26:48 raspberrypi weewx[2162]: wxengine: Using stats database: stats_sqlite

Jan 8 18:26:48 raspberrypi weewx[2162]: wxengine: Finished loading service weewx.wxengine.StdArchive

Jan 8 18:26:48 raspberrypi weewx[2162]: wxengine: Loading service weewx.wxengine.StdPrint

Jan 8 18:26:48 raspberrypi weewx[2162]: wxengine: Finished loading service weewx.wxengine.StdPrint

Jan 8 18:26:48 raspberrypi weewx[2162]: wxengine: Loading service weewx.wxengine.StdRESTful

Jan 8 18:26:48 raspberrypi weewx[2162]: wxengine: Data will not be posted to Wunderground

Jan 8 18:26:48 raspberrypi weewx[2162]: **** required parameter ''station'' is not specified

Jan 8 18:26:48 raspberrypi weewx[2162]: wxengine: Data will not be posted to PWSweather

Jan 8 18:26:48 raspberrypi weewx[2162]: **** required parameter ''station'' is not specified

Jan 8 18:26:48 raspberrypi weewx[2162]: wxengine: Data will not be posted to CWOP

Jan 8 18:26:48 raspberrypi weewx[2162]: **** required parameter ''station'' is not specified

Jan 8 18:26:48 raspberrypi weewx[2162]: wxengine: Data will not be posted to StationRegistry

Jan 8 18:26:48 raspberrypi weewx[2162]: **** required parameter ''register_this_station'' is not specified

Jan 8 18:26:48 raspberrypi weewx[2162]: wxengine: No RESTful upload sites. No need to start thread.

Jan 8 18:26:48 raspberrypi weewx[2162]: wxengine: Finished loading service weewx.wxengine.StdRESTful

Jan 8 18:26:48 raspberrypi weewx[2162]: wxengine: Loading service weewx.wxengine.StdReport

Jan 8 18:26:48 raspberrypi weewx[2162]: wxengine: Finished loading service weewx.wxengine.StdReport

Jan 8 18:26:48 raspberrypi weewx[2162]: wxengine: Starting up weewx version 2.5.1

Jan 8 18:26:48 raspberrypi weewx[2162]: wxengine: Station does not support reading the time

Jan 8 18:26:48 raspberrypi weewx[2162]: fousb: unstable read: blocks differ for ptr 0x000060

Jan 8 18:26:49 raspberrypi weewx[2162]: fousb: unstable read: blocks differ for ptr 0x000060

Jan 8 18:26:50 raspberrypi weewx[2162]: fousb: unstable read: blocks differ for ptr 0x000060

Jan 8 18:27:07 raspberrypi weewx[2162]: fousb: get_records failed: Connection timed out

Jan 8 18:27:15 raspberrypi dbus[2044]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper)

Jan 8 18:27:16 raspberrypi dbus[2044]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper)

Jan 8 18:27:16 raspberrypi polkitd[2252]: started daemon version 0.105 using authority implementation `local' version `0.105'

Jan 8 18:27:16 raspberrypi dbus[2044]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'

Jan 8 18:27:16 raspberrypi dbus[2044]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'

pi@raspberrypi ~ $

mwall

unread,

Jan 8, 2014, 3:43:45 PM1/8/14

to weewx...@googlegroups.com

peter,

the archive interval of your weather station is 30 minutes (1800 seconds - the factory default for fine offset stations).

in that configuration you will get data in weewx every 30 minutes.

you might want to change the archive interval to 5 minutes (see the 'configuring station hardware' section of the user guide).

m

drewmccal

unread,

Jan 8, 2014, 3:46:35 PM1/8/14

to weewx...@googlegroups.com

Hi,

I'm not an expert in the under workings of this software, but I run weewx on a Raspberry Pi too. I much prefer installing software as a .deb, and I think you'd save yourself lots of trouble having the package manager keep track of things. Maybe you have a reason for doing the python install? It looks to me that the error is on your weather station side. It doesn't look like weewx is able to get weather records from your station.

Next, it appears that /home/weewx/public_html/ is the folder that weewx dumps the files in, under a python install. Apache's default webserver folder is /var/www/. In a .deb install, Weewx defaults to putting the html report in /var/www/weewx. So if you want to change weewx to put the files in /var/www/weewx/, you'll need to change the 'HTML_ROOT' setting in weewx.conf.

Again, I'd double check that weewx is actually reading data from your station. Make sure it is generating files in the /home/weewx/public_html/ folder (You can't do that with a web browser). Also check to see if it's generating two database files in /home/weewx/archive.

I also suggest, as a more permanent solution, to have the database files and html files stored externally on a usb flashdrive, since SD cards are very volatile. I've already fried one SD card due to a power-outage. Eventually I'm going to be adding a Pi UPS (universal power supply) to my setup to keep things online more often, because I can't easily access my Pi to reset it. I live most of the year an hour away from my weather station.

Hope that helps.

Drew

mwall

unread,

Jan 8, 2014, 3:47:10 PM1/8/14

to weewx...@googlegroups.com

On Wednesday, January 8, 2014 1:32:17 PM UTC-5, Peter Hurn wrote:

Jan 8 18:27:07 raspberrypi weewx[2162]: fousb: get_records failed: Connection timed out

this is more troublesome - for some reason weewx was unable to communicate with your station. did you unplug the station usb at 18:27?

if this message shows up again, set debug=1 in weewx.conf then restart weewx to get more details about why.

m

Thomas Keffer

unread,

Jan 8, 2014, 7:23:48 PM1/8/14

to weewx-user

Weewx has to successfully generate an archive record before any reporting occurs, so it's premature to worry about whether or no public_html is being created.

And, yes, Apache expects things in /var/www, but Peter followed the necessary steps to make it look in public_html as well. No need to mess with HTML_ROOT.

Matthew is on the right track --- this is a connectivity problem.

-tk

--
You received this message because you are subscribed to the Google Groups "Weewx user's group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Andrew Milner

unread,

Jan 8, 2014, 11:20:07 PM1/8/14

to weewx...@googlegroups.com

Drew

Try the following:

1. Change to software archive generation

2. Set the station archive interval to 300

3. Change the polling interval to 53
4. Make sure that you are using one of the recognised USB powered hubs with a 3A power supply to connect your USB devices rather than relying on the Pi's USB ports - especially as you are running it would appear a lot of other USB and network devices

5. There would appear to be an awful lot of other activity going on on your poor RPi. Can you possibly shut down whatever else you have got running and see if weewx runs OK without all the other activity. I have found that network traffic in particular can have a detrimental effect on the stability of USB reads on the RPi, and have found that in general things work much better when the RPi is not overworked. The USB would appear to be a flakey part of the whole Pi setup, and network or cameras can kill the flakey 1080 USB connection at the drop of a hat.

Andrew

Peter Hurn

unread,

Jan 9, 2014, 1:26:58 PM1/9/14

to weewx...@googlegroups.com

Hi,

Thanks for reviewing the information, I will change that.

Kind regards,

Peter.

Peter Hurn

unread,

Jan 9, 2014, 1:31:43 PM1/9/14

to weewx...@googlegroups.com

Hi Drew,

Thank you for the information, I didnt really have a specific reason for the python install other than wanting to follow through the installation and understand the configuration

The weather station seems fine on its own and connecting to the PC application from Sandaysoft - Cumulus Weather Station Software

Hopefully changing the interval as mentioned above might help.

I have also reset the weather station, leaving it off for a couple of hours to clear anything.

Kind regards,

Peter.

Peter Hurn

unread,

Jan 9, 2014, 1:33:04 PM1/9/14

to weewx...@googlegroups.com

Hi,

Thanks for the reply, no I didn't unplug the weather station, I will add that debug.

Kind regards,

Peter.

Peter Hurn

unread,

Jan 9, 2014, 1:35:04 PM1/9/14

to weewx...@googlegroups.com

Hi,

Thanks for the reply, I'll concentrate on the connectivity and as you say once working hopefully Apache / weewx will run the appropriate jobs and take care of the rest, really looking forward to being able to publish the information either direct from the Raspberry Pi or more likely to an external site.

Kind regards,

Peter.

Peter Hurn

unread,

Jan 9, 2014, 1:39:17 PM1/9/14

to weewx...@googlegroups.com

Hi Andrew,

Thanks for the information, I will change those settings you mentioned and test, its a 2A powered USB hub so underpowered, a visit to Maplins sounds in order !

Only other USB device attached is a keyboard apart from the hub.

Im not sure what activity I can shut down its a clean install so shouldn't be running that much to be honest, any pointers gratefully received.

Only really using the network for NTP and SSH to the PI.

Kind regards,

Peter.

Peter Hurn

unread,

Jan 9, 2014, 2:15:21 PM1/9/14

to weewx...@googlegroups.com

Hi All,

Well it's not looking good, the station is refusing to reset the interval to 5 minutes.

Any ideas?

Kind regards,

Peter.

pi@raspberrypi ~ $ cd weewx-2.5.1

pi@raspberrypi ~/weewx-2.5.1 $ ls

bin docs merge_config.py README setup.py util

build LICENSE.txt PKG-INFO setup.cfg skins weewx.conf

pi@raspberrypi ~/weewx-2.5.1 $ sudo ./bin/wee_config_fousb --set-interval=5

Using configuration file /home/weewx/weewx.conf

Interval is 30

Set interval to 5 minutes (y/n)? y

Interval is now 30

pi@raspberrypi ~/weewx-2.5.1 $

mwall

unread,

Jan 9, 2014, 2:20:01 PM1/9/14

to weewx...@googlegroups.com

On Thursday, January 9, 2014 2:15:21 PM UTC-5, Peter Hurn wrote:

Hi All,

Well it's not looking good, the station is refusing to reset the interval to 5 minutes.

Any ideas?

were there any clues in the log file?

Peter Hurn

unread,

Jan 9, 2014, 4:17:45 PM1/9/14

to weewx...@googlegroups.com

Only this

Jan 9 21:14:28 raspberrypi weewx[2143]: wxengine: Caught unrecoverable exception in wxengine:

Jan 9 21:14:28 raspberrypi weewx[2143]: **** Connection timed out

Jan 9 21:14:28 raspberrypi weewx[2143]: **** Traceback (most recent call last):

Jan 9 21:14:28 raspberrypi weewx[2143]: **** File "/home/weewx/bin/weewx/wxengine.py", line 892, in main

Jan 9 21:14:28 raspberrypi weewx[2143]: **** engine = EngineClass(config_dict)

Jan 9 21:14:28 raspberrypi weewx[2143]: **** File "/home/weewx/bin/weewx/wxengine.py", line 70, in __init__

Jan 9 21:14:28 raspberrypi weewx[2143]: **** self.loadServices(config_dict)

Jan 9 21:14:28 raspberrypi weewx[2143]: **** File "/home/weewx/bin/weewx/wxengine.py", line 124, in loadServices

Jan 9 21:14:28 raspberrypi weewx[2143]: **** self.service_obj.append(weeutil.weeutil._get_object(svc)(self, config_dict))

Jan 9 21:14:28 raspberrypi weewx[2143]: **** File "/home/weewx/bin/weewx/wxengine.py", line 414, in __init__

Jan 9 21:14:28 raspberrypi weewx[2143]: **** if software_interval != self.engine.console.archive_interval:

Jan 9 21:14:28 raspberrypi weewx[2143]: **** File "/home/weewx/bin/weewx/drivers/fousb.py", line 771, in archive_interval

Jan 9 21:14:28 raspberrypi weewx[2143]: **** return self._archive_interval_minutes() * 60

Jan 9 21:14:28 raspberrypi weewx[2143]: **** File "/home/weewx/bin/weewx/drivers/fousb.py", line 775, in _archive_interval_minutes

Jan 9 21:14:28 raspberrypi weewx[2143]: **** self._archive_interval = self.get_fixed_block(['read_period'])

Jan 9 21:14:28 raspberrypi weewx[2143]: **** File "/home/weewx/bin/weewx/drivers/fousb.py", line 1412, in get_fixed_block

Jan 9 21:14:28 raspberrypi weewx[2143]: **** self._fixed_block = self._read_fixed_block()

Jan 9 21:14:28 raspberrypi weewx[2143]: **** File "/home/weewx/bin/weewx/drivers/fousb.py", line 1460, in _read_fixed_block

Jan 9 21:14:28 raspberrypi weewx[2143]: **** result += self._read_block(mempos)

Jan 9 21:14:28 raspberrypi weewx[2143]: **** File "/home/weewx/bin/weewx/drivers/fousb.py", line 1448, in _read_block

Jan 9 21:14:28 raspberrypi weewx[2143]: **** new_block = self._read_usb_block(ptr)

Jan 9 21:14:28 raspberrypi weewx[2143]: **** File "/home/weewx/bin/weewx/drivers/fousb.py", line 945, in _read_usb_block

Jan 9 21:14:28 raspberrypi weewx[2143]: **** int(self.timeout*1000))

Jan 9 21:14:28 raspberrypi weewx[2143]: **** USBError: Connection timed out

Jan 9 21:14:28 raspberrypi weewx[2143]: **** Exiting.

Jan 9 21:14:44 raspberrypi dbus[2034]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper)

Jan 9 21:14:44 raspberrypi dbus[2034]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper)

Jan 9 21:14:44 raspberrypi polkitd[2233]: started daemon version 0.105 using authority implementation `local' version `0.105'

Jan 9 21:14:44 raspberrypi dbus[2034]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'

Jan 9 21:14:44 raspberrypi dbus[2034]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'

Jan 9 21:15:35 raspberrypi wee_config_fousb[2261]: fousb: driver version is 1.4

Jan 9 21:15:35 raspberrypi wee_config_fousb[2261]: fousb: polling mode is PERIODIC

Jan 9 21:15:35 raspberrypi wee_config_fousb[2261]: fousb: polling interval is 60

Jan 9 21:15:35 raspberrypi wee_config_fousb[2261]: fousb: altitude is 213.36 meters

Jan 9 21:15:35 raspberrypi wee_config_fousb[2261]: fousb: pressure offset is 0.0

Jan 9 21:15:35 raspberrypi wee_config_fousb[2261]: fousb: found station on USB bus=001 device=004

mwall

unread,

Jan 9, 2014, 4:28:00 PM1/9/14

to weewx...@googlegroups.com

On Thursday, January 9, 2014 4:17:45 PM UTC-5, Peter Hurn wrote:

Jan 9 21:15:35 raspberrypi wee_config_fousb[2261]: fousb: driver version is 1.4
Jan 9 21:15:35 raspberrypi wee_config_fousb[2261]: fousb: polling mode is PERIODIC
Jan 9 21:15:35 raspberrypi wee_config_fousb[2261]: fousb: polling interval is 60
Jan 9 21:15:35 raspberrypi wee_config_fousb[2261]: fousb: altitude is 213.36 meters
Jan 9 21:15:35 raspberrypi wee_config_fousb[2261]: fousb: pressure offset is 0.0
Jan 9 21:15:35 raspberrypi wee_config_fousb[2261]: fousb: found station on USB bus=001 device=004

this is where you started running wee_config_fousb. the earlier stuff does not matter.

to get more details, set debug=1 in weewx.conf then run wee_config_fousb again.

what is on your usb? are you using a powered hub?

most likely it is a hardware problem, probably an underpowered bus.

if everything fails on the pi, even with a powered hub, then plug the station into a real computer and run wee_config_fousb from there. if that still fails, then it is quite likely that your console is defective.

m

Peter Hurn

unread,

Jan 9, 2014, 4:38:53 PM1/9/14

to weewx...@googlegroups.com

Hi,

Thanks the for reply, this is with debug = 1 in the weewx.conf file, which is located in the /home/weewx folder.

On this occasion I plugged the weather station directly into the Pi this time so no USB hub, and that's all that is connected to the PI, I SSH'd into the PI from a PC.

This happens even when the Pi is connected to the powered USB Hub which has a keyboard and the weather station attached.

As you suggest I'll run this on my PC and see what happens.

Peter

mwall

unread,

Jan 9, 2014, 4:51:30 PM1/9/14

to weewx...@googlegroups.com

peter,

just for laughs, post the output from this:

sudo wee_config_fousb --info

this might tell us more about your station's state...

m

Peter Hurn

unread,

Jan 9, 2014, 5:00:08 PM1/9/14

to weewx...@googlegroups.com

Here you go, seems fine to me....

I havnt bothered to reset the time and date on the weather station, it's been reset together with the pi that many times :)

pi@raspberrypi /home/weewx $ sudo ./bin/wee_config_fousb --info

Using configuration file /home/weewx/weewx.conf

Querying the station...

Fine Offset station settings:

local time: 2014.01.09 21:58:11 GMT

polling mode: PERIODIC

abs_pressure: 986.1

current_pos: 256

data_changed: 0

data_count: 1

date_time: 2010-01-01 12:01

hum_in_offset: 274

hum_out_offset: 257

id: 13395

lux_wm2_coeff: 0

magic_1: 0x80

magic_2: 0xaa

model: 58930

rain_coef: 55296

read_period: 30

rel_pressure: 1013.2

temp_in_offset: 4096

temp_out_offset: 0

timezone: 0

unknown_01: 0

unknown_18: 0

version: 0

wind_coef: 807

wind_mult: 0

max.abs_pressure.date: 2010-01-01 12:00

max.abs_pressure.val: 102.8

max.dewpoint.date: 2010-01-01 12:00

max.dewpoint.val: 1.6

max.hum_in.date: 2010-01-01 12:00

max.hum_in.val: 53

max.hum_out.date: 2010-01-01 12:00

max.hum_out.val: 86

max.illuminance.val: 0

max.rain.day.date: 2010-01-01 12:00

max.rain.day.val: 0

max.rain.hour.date: 2010-01-01 12:00

max.rain.hour.val: 0

max.rain.month.date: 2010-01-01 12:00

max.rain.month.val: 0

max.rain.total.date: 2010-01-01 12:00

max.rain.total.val: 0

max.rain.week.date: 2010-01-01 12:00

max.rain.week.val: 0

max.rel_pressure.date: 2010-01-01 12:00

max.rel_pressure.val: 576.4

max.temp_in.date: 2010-01-01 12:00

max.temp_in.val: 26.0

max.temp_out.date: 2010-01-01 12:00

max.temp_out.val: 3.8

max.uv.val: 0

max.wind_ave.date: 2010-01-01 12:00

max.wind_ave.val: 32.0

max.wind_gust.date: 2010-01-01 12:00

max.wind_gust.val: 0

max.windchill.date: 2010-01-01 12:00

max.windchill.val: 3.8

min.abs_pressure.date: 2010-01-01 12:00

min.abs_pressure.val: 986.1

min.dewpoint.date: 2010-01-01 12:00

min.dewpoint.val: 0.4

min.hum_in.date: 2010-01-01 12:00

min.hum_in.val: 49

min.hum_out.date: 2010-01-01 12:00

min.hum_out.val: 86

min.rel_pressure.date: 2010-01-01 12:00

min.rel_pressure.val: 137.6

min.temp_in.date: 2010-01-01 12:00

min.temp_in.val: 25.8

min.temp_out.date: 2010-01-01 12:00

min.temp_out.val: 3.8

min.windchill.date: 2010-01-01 12:00

min.windchill.val: 823.0

settings_1.pressure_inHg: False

settings_1.pressure_hPa: True

settings_1.temp_out_F: False

settings_1.pressure_mmHg: False

settings_1.rain_in: False

settings_1.temp_in_F: False

settings_1.bit4: False

settings_1.bit3: False

settings_2.wind_bft: False

settings_2.wind_mps: False

settings_2.wind_knot: False

settings_2.bit7: False

settings_2.bit6: False

settings_2.bit5: False

settings_2.wind_kmph: True

settings_2.wind_mph: False

display_1.wind_gust: False

display_1.show_day_name: False

display_1.show_year: True

display_1.time_scale_24: False

display_1.pressure_rel: False

display_1.alarm_time: False

display_1.date_mdy: False

display_1.clock_12hr: False

display_2.temp_out_temp: True

display_2.rain_hour: True

display_2.rain_month: False

display_2.rain_week: False

display_2.temp_out_chill: False

display_2.rain_day: False

display_2.temp_out_dew: False

display_2.rain_total: False

display_3.illuminance_fc: False

display_3.bit7: False

display_3.bit6: False

display_3.bit5: False

display_3.bit4: False

display_3.bit3: False

display_3.bit2: False

display_3.bit1: False

alarm.abs_pressure.hi: 1040.0

alarm.abs_pressure.lo: 960.0

alarm.dewpoint.hi: 10.0

alarm.dewpoint.lo: -10.0

alarm.hum_in.hi: 65

alarm.hum_in.lo: 35

alarm.hum_out.hi: 70

alarm.hum_out.lo: 45

alarm.illuminance: 0

alarm.rain.day: 150.0

alarm.rain.hour: 3.0

alarm.rel_pressure.hi: 1040.0

alarm.rel_pressure.lo: 960.0

alarm.temp_in.hi: 20.0

alarm.temp_in.lo: 0

alarm.temp_out.hi: 30.0

alarm.temp_out.lo: -10.0

alarm.time: 12:00

alarm.uv: 0

alarm.wind_ave.bft: 0

alarm.wind_ave.ms: 18.0

alarm.wind_dir: 0

alarm.wind_gust.bft: 0

alarm.wind_gust.ms: 10.4

alarm.windchill.hi: 20.0

alarm.windchill.lo: 0

alarm_1.hum_out_hi: False

alarm_1.hum_in_lo: False

alarm_1.hum_in_hi: False

alarm_1.hum_out_lo: False

alarm_1.time: False

alarm_1.bit3: False

alarm_1.wind_dir: False

alarm_1.bit0: False

alarm_2.wind_ave: False

alarm_2.wind_gust: False

alarm_2.rain_hour: False

alarm_2.pressure_rel_lo: False

alarm_2.pressure_abs_hi: False

alarm_2.rain_day: False

alarm_2.pressure_rel_hi: False

alarm_2.pressure_abs_lo: False

alarm_3.temp_out_hi: False

alarm_3.wind_chill_lo: False

alarm_3.dew_point_lo: False

alarm_3.temp_in_lo: False

alarm_3.wind_chill_hi: False

alarm_3.temp_in_hi: False

alarm_3.temp_out_lo: False

alarm_3.dew_point_hi: False

pi@raspberrypi /home/weewx $

mwall

unread,

Jan 9, 2014, 5:13:21 PM1/9/14

to weewx...@googlegroups.com

On Thursday, January 9, 2014 5:00:08 PM UTC-5, Peter Hurn wrote:

magic_1: 0x80
magic_2: 0xaa

you've got bad magic numbers. normally, these two should be 0x55 and 0xaa. having bad magic numbers does not mean your console won't work, but we see more sensor glitches and flaky behavior (e.g., set the interval to 5 then it randomly goes back to 30 sometime later) when the magic numbers are not 0x55 and 0xaa.

the values for model and id are odd as well.

it looks like your station is in a confused state.

how to fix it? power cycle the console. remove batteries and remove usb cable for a minute or two (you'll see when the capacitors have died off). then power on by first inserting batteries, then later usb (once the station is up and running).

one of our stations always has ok magic numbers. another station (a WS2080A purchased late 2013) often has bad magic numbers, and it periodically (every month or two?) changes its archive interval to 30, no matter what it was set to before.

perhaps someday someone could find the right hub and get a python version of hubctrl to work so we could do the power cycling from the computer...

m

Peter Hurn

unread,

Jan 9, 2014, 5:23:27 PM1/9/14

to weewx...@googlegroups.com

Thanks, despite a restart as you mentioned, which I have done a number of times in the past it looks like this console is not going to work for USB connectivity, odd as Cumulus has seemed to pick up the data (wonder if it will now).

Time to resign myself to the fact it can show the information on the LCD but if I want to publish the information it looks like an investment in a new weather station is in order...

Good to know it's not my IT skills at least ;)

Thank you all for your help.

mwall

unread,

Jan 10, 2014, 8:50:24 AM1/10/14

to weewx...@googlegroups.com

On Thursday, January 9, 2014 5:23:27 PM UTC-5, Peter Hurn wrote:

Thanks, despite a restart as you mentioned, which I have done a number of times in the past it looks like this console is not going to work for USB connectivity, odd as Cumulus has seemed to pick up the data (wonder if it will now).

Time to resign myself to the fact it can show the information on the LCD but if I want to publish the information it looks like an investment in a new weather station is in order...

peter,

does cumulus do catchup? when cumulus starts, dos it read records from the station's memory, or does it only read 'live' data from the station?

if you cannot get the interval to change, you could hack weewx so that it ignores the station memory and archive interval. then it would read live data from the station at whatever interval_interval is specified in weewx.conf. uploading to wunderground and everything else will work as usual.

to do this, change two lines of code in fousb.py:

def archive_interval(self):

becomes

def xxx_archive_interval(self):

and

def genArchiveRecords(self, since_ts):

becomes:

def xxx_genArchiveRecords(self, since_ts):

Andrew Milner

unread,

Jan 10, 2014, 9:22:56 AM1/10/14

to weewx...@googlegroups.com

When I used to use Cumulus I am pretty sure it used to catch up from the archive records in the console. Would be interesting to know what Peter's does now - hope he tries to find out!! As an aside to Matt - the new driver seems to be doing well. Yesterday I set my RPi to turbo - and started to get loads of failures on WU uploads. Increased the socket timeout and all seems to have stabilised now. I still have a hunch that there are more failures to get data the higher up the station's memory one is accessing. Don't ask me why, since it does not really make any sense unless the station scans forward from the start of the circular buffer for each read request - but I am going to change my daily monitoring routine to also log the pointer values for each day and see if I can get any form of correlation between odd events and pointer values.

mwall

unread,

Jan 10, 2014, 9:23:03 AM1/10/14

to weewx...@googlegroups.com

On Thursday, January 9, 2014 5:23:27 PM UTC-5, Peter Hurn wrote:

Thanks, despite a restart as you mentioned, which I have done a number of times in the past it looks like this console is not going to work for USB connectivity, odd as Cumulus has seemed to pick up the data (wonder if it will now).

peter,

could you try running the SetLogger.exe utility from sandaysoft (cumulus) to see whether that can modify the station's archive interval?

your station is rather unusual, so i'd like to learn from it if we can.

m

Peter Hurn

unread,

Jan 10, 2014, 4:18:38 PM1/10/14

to weewx...@googlegroups.com

Hi,

Thanks for the post, yes Cumulus used to do a catchup from the history on the weather station, only have a few hours of reading but could try it again to see what it makes of it.

Peter.

Peter Hurn

unread,

Jan 10, 2014, 4:19:04 PM1/10/14

to weewx...@googlegroups.com

I will give it a go and report back ....

Peter Hurn

unread,

Jan 10, 2014, 4:31:40 PM1/10/14

to weewx...@googlegroups.com

Ok so this doesnt look good, Cumulus shows an error light when connecting the weather station and this:

10/01/2014 21:22:05 : The station is not initialised

10/01/2014 21:22:05 : Byte 0 = 00 Byte 1 = AA

10/01/2014 21:22:05 : Try resetting the console

Cumulus in the past hasn't had a problem with this.

I downloaded SetLogger.exe v1.0 from Sandysoft and that crashes whilst trying to communicate with the station.

Snip from its crash log

executable : SetLogger.exe

exec. date/time : 2012-03-02 12:40

version : 1.0.0.0

compiled with : Delphi XE2

madExcept version : 3.0n

callstack crc : $4bc57bb0, $f7fabf85, $f7fabf85

exception number : 1

exception class : EControllerError

exception message : Device cannot be opened.

looking fairly terminal at this point :(

Looks like something I did has upset the station and I can't get it to reinitialise / reboot (battaries removed, disconnected from USB, left for a few hours), etc.

Anyone know if these things contain something that can be reflashed ?

Peter.

Peter Hurn

unread,

Jan 10, 2014, 4:58:21 PM1/10/14

to weewx...@googlegroups.com

This person seems to have experienced something similar

http://sandaysoft.com/forum/viewtopic.php?f=13&t=8780

Out of interest I downloaded fineoffset's own easyweather that came with the station, the latest is 7.7. it does read the station, but when i go to change the update frequency setting from 30 minutes to 5, It errors with "Try again".

Although it s recordered a maximum wind gust of 92.2km/h since i reset the weather station 14 minutes ago so i suspect something is awry.

It looks like the station can't update or write updates either to itself or from USB and isnt initialising correctly.

Peter.

Peter Hurn

unread,

Jan 10, 2014, 5:34:19 PM1/10/14

to weewx...@googlegroups.com

Hmm confirmation from Steve at Sandysoft..

The console firmware isn't upgradeable. It's possibly worth trying other methods of USB connection as from what I've read the problem is related to the USB chip in the station.

_________________
Steve
Sanday Weather

Peter Hurn

unread,

Jan 11, 2014, 11:13:48 AM1/11/14

to weewx...@googlegroups.com

Ok, so not one to be put of by duff hardware I have visited Maplin's this afternoon and returned with a new weather station, so ill configure and report back.

Thanks to everyone for their help.

Have a good weekend.

Kind regards,

Peter.

Peter Hurn

unread,

Jan 16, 2014, 5:36:05 AM1/16/14

to weewx...@googlegroups.com

All up and running first time, now customising the weather page display.

Reply all

Reply to author

Forward