Page 1 of 1

New Meteobridge PRO has quit receiving data

Posted: Wed Dec 21, 2016 3:05 am
by bcrosby
I just got a Davis Vantage Pro2 and Meteobridge PRO up and running. Initially things went pretty well. There were occasional periods with no data but those became more frequent. In the past few hours, reception has stopped altogether. The Davis console is working fine. I have both the ISS and console set to ID=2 because I initially had an old Davis station on the premises. The Meteobridge PRO is also set to receive from Station #2. I have the display set to read RF signal strength . . . dashes all the way down. Any suggestions?

Re: New Meteobridge PRO has quit receiving data

Posted: Wed Dec 21, 2016 3:26 am
by bcrosby
Just to add to the intrigue, it just spontaneously started receiving a signal! DB signals are in the mid-60's. I did not report before that the ISS is approximately 70' from the Meteobridge PRO and sits with an unobstructed window view. Thanks!

Re: New Meteobridge PRO has quit receiving data

Posted: Wed Dec 21, 2016 4:37 am
by bcrosby
Another update! The unit has stopped again. This time I captured a section of the log file in the hope that will offer some insight. I await your response. Thanks!

oled (21.12.2016 00:23:18): process started.
database (20.12.2016 16:25:39): process started.
wnetd (20.12.2016 16:25:41): process started.
system (20.12.2016 16:25:41): start of logging process initiated.
logger (20.12.2016 16:25:41): databases connected. Update interval 3600 seconds.
logger (20.12.2016 16:25:41): Historical data loaded (0 records).
logger (20.12.2016 16:25:41): data logger (version 5.0t, build 10773) started.
logger (20.12.2016 16:25:44): connect station 0 (Meteostick Vantage via USB serial).
logger (20.12.2016 16:25:44): connect station 9 (System Data via Plug-in).
logger (20.12.2016 16:25:45): Meteostick Version 2.4
logger (20.12.2016 16:25:45): debug off
logger (20.12.2016 16:25:45): verbose off
logger (20.12.2016 16:25:45): output raw (8 bytes)
logger (20.12.2016 16:25:45): output raw (10 bytes)
logger (20.12.2016 16:25:45): filter on
logger (20.12.2016 16:25:45): rx threshold set to -90db
logger (20.12.2016 16:25:45): listening to transmitter
logger (20.12.2016 16:25:45): bandwidth narrow
logger (20.12.2016 16:25:46): chip authentication ok: 14
logger (20.12.2016 16:25:46): frequency band 915MHz (US)
database (20.12.2016 16:26:25): database sync done (66 tables, 0/6583 writes)
system (20.12.2016 16:26:34): stop of logging process initiated.
logger (20.12.2016 16:26:34): parent process received termination signal (15).
logger (20.12.2016 16:26:34): child process received termination signal (15).
system (20.12.2016 16:26:34): start of logging process initiated.
logger (20.12.2016 16:26:34): databases connected. Update interval 3600 seconds.
logger (20.12.2016 16:26:34): Historical data loaded (0 records).
logger (20.12.2016 16:26:34): data logger (version 5.0t, build 10773) started.
logger (20.12.2016 16:26:35): connect station 0 (Meteostick Vantage via USB serial).
logger (20.12.2016 16:26:35): connect station 9 (System Data via Plug-in).
logger (20.12.2016 16:26:35): transmitter 2 registered as ISS
logger (20.12.2016 16:26:35): Meteostick Version 2.4
logger (20.12.2016 16:26:35): debug off
logger (20.12.2016 16:26:35): verbose off
logger (20.12.2016 16:26:35): output raw (8 bytes)
logger (20.12.2016 16:26:35): output raw (10 bytes)
logger (20.12.2016 16:26:35): filter on
logger (20.12.2016 16:26:35): rx threshold set to -90db
logger (20.12.2016 16:26:35): listening to transmitter 2
logger (20.12.2016 16:26:35): bandwidth narrow
logger (20.12.2016 16:26:35): chip authentication ok: 14
logger (20.12.2016 16:26:35): frequency band 915MHz (US)
logger (20.12.2016 16:31:36): restart meteostick (302 secs no valid rf signal)
system (20.12.2016 16:34:13): stop of logging process initiated.
system (20.12.2016 16:34:33): start of logging process initiated.
logger (20.12.2016 16:34:33): databases connected. Update interval 3600 seconds.
logger (20.12.2016 16:34:33): Historical data loaded (0 records).
logger (20.12.2016 16:34:33): data logger (version 5.0t, build 10773) started.
logger (20.12.2016 16:34:33): connect station 0 (Meteostick Vantage via USB serial).
logger (20.12.2016 16:34:33): connect station 9 (System Data via Plug-in).
logger (20.12.2016 16:34:42): transmitter 2 registered as ISS
logger (20.12.2016 16:34:42): Meteostick Version 2.4
logger (20.12.2016 16:34:42): debug off
logger (20.12.2016 16:34:42): verbose off
logger (20.12.2016 16:34:43): output raw (8 bytes)
logger (20.12.2016 16:34:43): output raw (10 bytes)
logger (20.12.2016 16:34:43): filter on
logger (20.12.2016 16:34:43): rx threshold set to -90db
logger (20.12.2016 16:34:43): listening to transmitter 2
logger (20.12.2016 16:34:43): bandwidth narrow
logger (20.12.2016 16:34:43): chip authentication ok: 14
logger (20.12.2016 16:34:43): frequency band 915MHz (US)
logger (20.12.2016 16:39:44): restart meteostick (310 secs no valid rf signal)
logger (20.12.2016 16:44:45): restart meteostick (302 secs no valid rf signal)
logger (20.12.2016 16:49:47): restart meteostick (301 secs no valid rf signal)
logger (20.12.2016 16:54:48): restart meteostick (302 secs no valid rf signal)
logger (20.12.2016 16:59:50): restart meteostick (301 secs no valid rf signal)
logger (20.12.2016 17:04:52): restart meteostick (302 secs no valid rf signal)
logger (20.12.2016 17:09:53): restart meteostick (301 secs no valid rf signal)
logger (20.12.2016 17:12:50): wind0 data incomplete (missing outdoor temp for windchill)
logger (20.12.2016 17:12:58): wind0 data incomplete (missing outdoor temp for windchill)
logger (20.12.2016 17:13:06): wind0 data incomplete (missing outdoor temp for windchill)
logger (20.12.2016 17:13:14): wind0 data incomplete (missing outdoor temp for windchill)
logger (20.12.2016 17:13:24): wind0 data incomplete (missing outdoor temp for windchill)
logger (20.12.2016 18:18:20): unexpected 0 bytes.
logger (20.12.2016 18:18:20): station 0 (Meteostick Vantage), can't set attributes of device /dev/ttyMH to former values: Input/output error
logger (20.12.2016 18:18:20): disconnect station 0 (Meteostick Vantage): response without data
logger (20.12.2016 18:18:50): station 0 (Meteostick Vantage), can't open device /dev/ttyMH: No such file or directory
logger (20.12.2016 18:19:20): station 0 (Meteostick Vantage), can't open device /dev/ttyMH: No such file or directory
logger (20.12.2016 18:19:50): station 0 (Meteostick Vantage), can't open device /dev/ttyMH: No such file or directory
logger (20.12.2016 18:20:20): station 0 (Meteostick Vantage), can't open device /dev/ttyMH: No such file or directory
logger (20.12.2016 18:20:50): station 0 (Meteostick Vantage), can't open device /dev/ttyMH: No such file or directory
logger (20.12.2016 18:21:20): station 0 (Meteostick Vantage), can't open device /dev/ttyMH: No such file or directory
logger (20.12.2016 18:21:50): station 0 (Meteostick Vantage), can't open device /dev/ttyMH: No such file or directory
logger (20.12.2016 18:22:20): station 0 (Meteostick Vantage), can't open device /dev/ttyMH: No such file or directory
logger (20.12.2016 18:22:50): station 0 (Meteostick Vantage), can't open device /dev/ttyMH: No such file or directory
logger (20.12.2016 18:23:20): station 0 (Meteostick Vantage), can't open device /dev/ttyMH: No such file or directory
logger (20.12.2016 18:23:50): station 0 (Meteostick Vantage), can't open device /dev/ttyMH: No such file or directory
logger (20.12.2016 18:24:20): station 0 (Meteostick Vantage), can't open device /dev/ttyMH: No such file or directory
logger (20.12.2016 18:24:50): station 0 (Meteostick Vantage), can't open device /dev/ttyMH: No such file or directory
logger (20.12.2016 18:25:20): station 0 (Meteostick Vantage), can't open device /dev/ttyMH: No such file or directory
logger (20.12.2016 18:25:50): station 0 (Meteostick Vantage), can't open device /dev/ttyMH: No such file or directory
logger (20.12.2016 18:26:20): station 0 (Meteostick Vantage), can't open device /dev/ttyMH: No such file or directory
logger (20.12.2016 18:26:50): station 0 (Meteostick Vantage), can't open device /dev/ttyMH: No such file or directory
logger (20.12.2016 18:27:20): station 0 (Meteostick Vantage), can't open device /dev/ttyMH: No such file or directory
logger (20.12.2016 18:27:50): station 0 (Meteostick Vantage), can't open device /dev/ttyMH: No such file or directory
logger (20.12.2016 18:28:20): station 0 (Meteostick Vantage), can't open device /dev/ttyMH: No such file or directory

Re: New Meteobridge PRO has quit receiving data

Posted: Wed Dec 21, 2016 6:50 am
by bcrosby
Yet again, it started spontaneously and then a short time later quit. A restart yielded a "format failed" flag on the LED screen. A second restart was successful. What is going on?

Re: New Meteobridge PRO has quit receiving data

Posted: Thu Dec 22, 2016 6:35 am
by bcrosby
Another update! In just about 24 hours, I have had 10 breaks in service. They have run from 0:05 to 3:25. About half way through the time, I moved my station within about 25' of the Meteobridge PRO. That improved signal strength (45-48 DB) but didn't solve the breaks. Unless I hear something to change my mind on this forum by tomorrow, I will probably initiate a return. I'm disappointed, to say the least.

Re: New Meteobridge PRO has quit receiving data

Posted: Fri Dec 23, 2016 12:50 pm
by 1fcmrYpC2Nw8
You are not alone

I have had a lot of problems with my MB Pro. Here are a few:

Internal USB flash failed within a couple of months - replaced at my own expense

MB Pro failed to back up to external USB stick - fixed by admin

MB Pro fails to boot when external backup USB device inserted

MB Pro reboots randomly

MB Pro becomes unresponsive when WLAN or public Internet go down

My main reason for buying the MB Pro was to have a reliable device to provide a reliable local record of my data in case of Internet or other outages.

I am very disappointed

Re: New Meteobridge PRO has quit receiving data

Posted: Sat Dec 24, 2016 9:56 pm
by bcrosby
Thanks for the feedback. Not exactly what I was hoping to hear but it gives me some perspective on what's happening. I'm going to just let things be for the next couple of days and then figure out what my next step(s) will be. I really don't know how to take corrective action at the moment. Happy holidays!

Re: New Meteobridge PRO has quit receiving data

Posted: Sun Dec 25, 2016 2:23 pm
by admin
@bcrosby:
Can you please post output of "http://ip-of-your-meteobridge/cgi-bin/system.cgi?dmesg"?
I would like to check if there is something wrong with internal USB storage.

@1fcmrYpC2Nw8:
Sorry that it does not work well with your setup. What storage did you have installed on your own?

Re: New Meteobridge PRO has quit receiving data

Posted: Mon Dec 26, 2016 6:35 am
by bcrosby
Thanks for getting back to me. In the last day or so, I have continued experience many random dropouts. My station is about 25' from my console and Meteobridge PRO. The console is consistently receiving data. The Meteobridge PRO is not. Here's the last few lines from the Messages log. This is followed by the information you requested. I'll welcome any help you can offer me. Thanks!
-------------------------------------------------------------------------------------------------------------
logger (25.12.2016 03:53:15): restart meteostick (301 secs no valid rf signal)
logger (25.12.2016 03:58:17): restart meteostick (302 secs no valid rf signal)
logger (25.12.2016 04:03:18): restart meteostick (302 secs no valid rf signal)
logger (25.12.2016 04:08:20): restart meteostick (301 secs no valid rf signal)
logger (25.12.2016 04:13:22): restart meteostick (302 secs no valid rf signal)
logger (25.12.2016 04:18:23): restart meteostick (301 secs no valid rf signal)
logger (25.12.2016 04:23:25): restart meteostick (302 secs no valid rf signal)
logger (25.12.2016 11:47:37): restart meteostick (303 secs no valid rf signal)
logger (25.12.2016 11:52:38): restart meteostick (301 secs no valid rf signal)
logger (25.12.2016 11:57:40): restart meteostick (302 secs no valid rf signal)
logger (25.12.2016 14:20:45): restart meteostick (321 secs no valid rf signal)
logger (25.12.2016 15:16:47): restart meteostick (301 secs no valid rf signal)
logger (25.12.2016 15:21:49): restart meteostick (301 secs no valid rf signal)
logger (25.12.2016 15:26:51): restart meteostick (302 secs no valid rf signal)
-------------------------------------------------------------------------------------------------------------
command: dmesg
-------------
[ 0.000000] Linux version 3.10.49 (boris@mars) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r44550) ) #685 Thu Dec 17 00:17:35 CET 2015
[ 0.000000] MyLoader: sysp=7533b373, boardp=13f51777, parts=115715b1
[ 0.000000] bootconsole [early0] enabled
[ 0.000000] CPU revision is: 00019374 (MIPS 24Kc)
[ 0.000000] SoC: Atheros AR9330 rev 1
[ 0.000000] Clocks: CPU:400.000MHz, DDR:400.000MHz, AHB:200.000MHz, Ref:40.000MHz
[ 0.000000] Determined physical RAM map:
[ 0.000000] memory: 04000000 @ 00000000 (usable)
[ 0.000000] Initrd not found or empty - disabling initrd
[ 0.000000] Zone ranges:
[ 0.000000] Normal [mem 0x00000000-0x03ffffff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x00000000-0x03ffffff]
[ 0.000000] On node 0 totalpages: 16384
[ 0.000000] free_area_init_node: node 0, pgdat 803109b0, node_mem_map 81000000
[ 0.000000] Normal zone: 128 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 16384 pages, LIFO batch:3
[ 0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
[ 0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
[ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[ 0.000000] pcpu-alloc: [0] 0
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256
[ 0.000000] Kernel command line: board=CARAMBOLA2 console=ttyATH0,115200 mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,16000k(firmware),64k(art)ro rootfstype=squashfs,jffs2 noinitrd
[ 0.000000] PID hash table entries: 256 (order: -2, 1024 bytes)
[ 0.000000] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.000000] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Writing ErrCtl register=00000000
[ 0.000000] Readback ErrCtl register=00000000
[ 0.000000] Memory: 61272k/65536k available (2239k kernel code, 4264k reserved, 603k data, 228k init, 0k highmem)
[ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] NR_IRQS:51
[ 0.080000] Calibrating delay loop... 265.42 BogoMIPS (lpj=1327104)
[ 0.080000] pid_max: default: 32768 minimum: 301
[ 0.080000] Mount-cache hash table entries: 512
[ 0.090000] NET: Registered protocol family 16
[ 0.100000] MIPS: machine is 8devices Carambola2 board
[ 0.550000] bio: create slab <bio-0> at 0
[ 0.560000] Switching to clocksource MIPS
[ 0.570000] NET: Registered protocol family 2
[ 0.570000] TCP established hash table entries: 512 (order: 0, 4096 bytes)
[ 0.570000] TCP bind hash table entries: 512 (order: -1, 2048 bytes)
[ 0.580000] TCP: Hash tables configured (established 512 bind 512)
[ 0.580000] TCP: reno registered
[ 0.580000] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 0.590000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 0.600000] NET: Registered protocol family 1
[ 0.600000] PCI: CLS 0 bytes, default 32
[ 0.620000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.630000] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[ 0.640000] msgmni has been set to 119
[ 0.640000] io scheduler noop registered
[ 0.640000] io scheduler deadline registered (default)
[ 0.650000] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
[ 0.660000] ar933x-uart: ttyATH0 at MMIO 0x18020000 (irq = 11) is a AR933X UART
[ 0.660000] console [ttyATH0] enabled, bootconsole disabled
[ 0.680000] ath79-spi ath79-spi: master is unqueued, this is deprecated
[ 0.680000] m25p80 spi0.0: found w25q128, expected m25p80
[ 0.690000] m25p80 spi0.0: w25q128 (16384 Kbytes)
[ 0.690000] 4 cmdlinepart partitions found on MTD device spi0.0
[ 0.700000] Creating 4 MTD partitions on "spi0.0":
[ 0.700000] 0x000000000000-0x000000040000 : "u-boot"
[ 0.710000] 0x000000040000-0x000000050000 : "u-boot-env"
[ 0.720000] 0x000000050000-0x000000ff0000 : "firmware"
[ 0.740000] 2 uimage-fw partitions found on MTD device firmware
[ 0.740000] 0x000000050000-0x000000160000 : "kernel"
[ 0.750000] 0x000000160000-0x000000ff0000 : "rootfs"
[ 0.750000] mtd: device 4 (rootfs) set to be root filesystem
[ 0.760000] 1 squashfs-split partitions found on MTD device rootfs
[ 0.760000] 0x0000006d0000-0x000000ff0000 : "rootfs_data"
[ 0.770000] 0x000000ff0000-0x000001000000 : "art"
[ 0.790000] libphy: ag71xx_mdio: probed
[ 1.340000] ag71xx-mdio.1: Found an AR7240/AR9330 built-in switch
[ 2.380000] eth0: Atheros AG71xx at 0xba000000, irq 5, mode:GMII
[ 2.930000] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.1:04 [uid=004dd041, driver=Generic PHY]
[ 2.940000] eth1: Atheros AG71xx at 0xb9000000, irq 4, mode:MII
[ 2.950000] TCP: cubic registered
[ 2.950000] NET: Registered protocol family 17
[ 2.960000] 8021q: 802.1Q VLAN Support v1.8
[ 2.970000] VFS: Mounted root (squashfs filesystem) readonly on device 31:4.
[ 2.970000] Freeing unused kernel memory: 228K (80327000 - 80360000)
[ 6.790000] usbcore: registered new interface driver usbfs
[ 6.800000] usbcore: registered new interface driver hub
[ 6.800000] usbcore: registered new device driver usb
[ 6.860000] SCSI subsystem initialized
[ 6.870000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 6.880000] ehci-platform: EHCI generic platform driver
[ 6.880000] ehci-platform ehci-platform: EHCI Host Controller
[ 6.890000] ehci-platform ehci-platform: new USB bus registered, assigned bus number 1
[ 6.900000] ehci-platform ehci-platform: irq 3, io mem 0x1b000000
[ 6.920000] ehci-platform ehci-platform: USB 2.0 started, EHCI 1.00
[ 6.920000] hub 1-0:1.0: USB hub found
[ 6.920000] hub 1-0:1.0: 1 port detected
[ 6.930000] usbcore: registered new interface driver usb-storage
[ 7.360000] usb 1-1: new high-speed USB device number 2 using ehci-platform
[ 7.540000] hub 1-1:1.0: USB hub found
[ 7.550000] hub 1-1:1.0: 4 ports detected
[ 7.850000] usb 1-1.3: new full-speed USB device number 3 using ehci-platform
[ 8.070000] usb 1-1.4: new high-speed USB device number 4 using ehci-platform
[ 8.320000] usb-storage 1-1.4:1.0: USB Mass Storage device detected
[ 8.330000] scsi0 : usb-storage 1-1.4:1.0
[ 9.170000] eth0: link up (1000Mbps/Full duplex)
[ 9.720000] scsi 0:0:0:0: Direct-Access ATP NANODURA 1000 PQ: 0 ANSI: 4
[ 9.730000] sd 0:0:0:0: [sda] 1964032 512-byte logical blocks: (1.00 GB/959 MiB)
[ 9.740000] sd 0:0:0:0: [sda] Write Protect is off
[ 9.740000] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
[ 9.740000] sd 0:0:0:0: [sda] No Caching mode page found
[ 9.750000] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 9.760000] sd 0:0:0:0: [sda] No Caching mode page found
[ 9.760000] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 9.770000] sda: unknown partition table
[ 9.780000] sd 0:0:0:0: [sda] No Caching mode page found
[ 9.780000] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 9.790000] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 12.490000] jffs2: notice: (342) jffs2_build_xattr_subsystem: complete building xattr subsystem, 1 of xdatum (1 unchecked, 0 orphan) and 60 of xref (0 dead, 45 orphan) found.
[ 12.500000] block: attempting to load /tmp/jffs_cfg/upper/etc/config/fstab
[ 12.510000] block: unable to load configuration (fstab: Entry not found)
[ 12.520000] block: attempting to load /tmp/jffs_cfg/etc/config/fstab
[ 12.540000] block: extroot: not configured
[ 12.620000] jffs2: notice: (339) jffs2_build_xattr_subsystem: complete building xattr subsystem, 1 of xdatum (1 unchecked, 0 orphan) and 60 of xref (0 dead, 45 orphan) found.
[ 12.950000] block: attempting to load /tmp/jffs_cfg/upper/etc/config/fstab
[ 12.960000] block: unable to load configuration (fstab: Entry not found)
[ 12.970000] block: attempting to load /tmp/jffs_cfg/etc/config/fstab
[ 12.980000] block: extroot: not configured
[ 13.010000] eth0: link down
[ 18.480000] NET: Registered protocol family 10
[ 18.520000] nf_conntrack version 0.5.0 (960 buckets, 3840 max)
[ 18.530000] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 18.560000] hidraw: raw HID events driver (C) Jiri Kosina
[ 18.570000] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 18.580000] Loading modules backported from Linux version master-2014-05-22-0-gf2032ea
[ 18.590000] Backport generated by backports.git backports-20140320-37-g5c33da0
[ 18.600000] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 18.630000] usbcore: registered new interface driver usbhid
[ 18.640000] usbhid: USB HID core driver
[ 18.650000] usbcore: registered new interface driver usbserial
[ 18.660000] usbcore: registered new interface driver usbserial_generic
[ 18.670000] usbserial: USB Serial support registered for generic
[ 18.700000] xt_time: kernel timezone is -0000
[ 18.700000] usbcore: registered new interface driver cdc_ether
[ 18.740000] cfg80211: Calling CRDA to update world regulatory domain
[ 18.740000] cfg80211: World regulatory domain updated:
[ 18.750000] cfg80211: DFS Master region: unset
[ 18.750000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 18.760000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 18.770000] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 18.780000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[ 18.780000] cfg80211: (5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A, 2000 mBm), (N/A)
[ 18.790000] cfg80211: (5250000 KHz - 5330000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[ 18.800000] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[ 18.810000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[ 18.820000] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[ 18.840000] usbcore: registered new interface driver ch341
[ 18.840000] usbserial: USB Serial support registered for ch341-uart
[ 18.860000] usbcore: registered new interface driver cp210x
[ 18.860000] usbserial: USB Serial support registered for cp210x
[ 18.880000] usbcore: registered new interface driver ftdi_sio
[ 18.880000] usbserial: USB Serial support registered for FTDI USB Serial Device
[ 18.890000] ftdi_sio 1-1.3:1.0: FTDI USB Serial Device converter detected
[ 18.930000] usb 1-1.3: Detected FT232RL
[ 18.930000] usb 1-1.3: Number of endpoints 2
[ 18.930000] usb 1-1.3: Endpoint 1 MaxPacketSize 16384
[ 18.940000] usb 1-1.3: Endpoint 2 MaxPacketSize 16384
[ 18.940000] usb 1-1.3: Setting MaxPacketSize 64
[ 18.970000] usb 1-1.3: FTDI USB Serial Device converter now attached to ttyUSB0
[ 19.050000] usbcore: registered new interface driver pl2303
[ 19.050000] usbserial: USB Serial support registered for pl2303
[ 19.070000] PPP generic driver version 2.4.2
[ 19.080000] NET: Registered protocol family 24
[ 19.130000] usbcore: registered new interface driver option
[ 19.150000] usbserial: USB Serial support registered for GSM modem (1-port)
[ 19.200000] ath: EEPROM regdomain: 0x0
[ 19.200000] ath: EEPROM indicates default country code should be used
[ 19.200000] ath: doing EEPROM country->regdmn map search
[ 19.200000] ath: country maps to regdmn code: 0x3a
[ 19.200000] ath: Country alpha2 being used: US
[ 19.200000] ath: Regpair used: 0x3a
[ 19.220000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 19.220000] ieee80211 phy0: Atheros AR9330 Rev:1 mem=0xb8100000, irq=2
[ 19.230000] cfg80211: Calling CRDA for country: US
[ 19.230000] cfg80211: Regulatory domain changed to country: US
[ 19.240000] cfg80211: DFS Master region: FCC
[ 19.240000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 19.250000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
[ 19.260000] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 1700 mBm), (N/A)
[ 19.270000] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz), (N/A, 2300 mBm), (0 s)
[ 19.280000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A)
[ 19.290000] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
[ 19.400000] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[ 19.400000] ftdi_sio 1-1.3:1.0: device disconnected
[ 19.410000] ftdi_sio 1-1.3:1.0: FTDI USB Serial Device converter detected
[ 19.430000] usb 1-1.3: Detected FT232RL
[ 19.430000] usb 1-1.3: Number of endpoints 2
[ 19.430000] usb 1-1.3: Endpoint 1 MaxPacketSize 16384
[ 19.440000] usb 1-1.3: Endpoint 2 MaxPacketSize 16384
[ 19.440000] usb 1-1.3: Setting MaxPacketSize 64
[ 19.470000] usb 1-1.3: FTDI USB Serial Device converter now attached to ttyUSB0
[ 21.500000] i2c /dev entries driver
[ 21.520000] Custom GPIO-based I2C driver version 0.1.1
[ 21.530000] i2c-gpio i2c-gpio.0: using pins 20 (SDA) and 21 (SCL)
[ 34.760000] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 35.440000] eth0: link up (1000Mbps/Full duplex)
[ 35.440000] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 49.830000] EXT4-fs (sda): couldn't mount as ext3 due to feature incompatibilities
[ 49.840000] EXT4-fs (sda): couldn't mount as ext2 due to feature incompatibilities
[ 49.880000] EXT4-fs (sda): mounted filesystem with ordered data mode. Opts: (null)
[ 50.700000] EXT4-fs (sda): couldn't mount as ext3 due to feature incompatibilities
[ 50.700000] EXT4-fs (sda): couldn't mount as ext2 due to feature incompatibilities
[ 50.720000] EXT4-fs (sda): mounted filesystem with ordered data mode. Opts: (null)
[ 84.200000] EXT4-fs (sda): re-mounted. Opts: data=ordered,commit=60,max_batch_time=1000000,min_batch_time=1000000,errors=remount-ro
-------------

Re: New Meteobridge PRO has quit receiving data

Posted: Mon Dec 26, 2016 3:32 pm
by 1fcmrYpC2Nw8
@ADMIN

I installed ATP NanoDura USB storage as recommended by you

Re: New Meteobridge PRO has quit receiving data

Posted: Mon Jan 09, 2017 7:19 pm
by admin
@bcrosby: No indication of a USB storage related problem in your logs. As you have the ATP
stick and those never failed so far, I would like to rule that out...
My guess is that MB PRO does not get RF data from the sensors and by that resets USB
port again and again (to reboot RF module) and this might have caused the problem.
One of the resets has timed badly and by that the enumeration of the USBserial
device has been tricked. I will check the scripts why they don't detect and fix that.

Primary question however is, why don't you receive data. Can you please post your
Meteobridge RF settings? How far away are the sensors?