For me very stable too.
In my case with the driver wmr300-v19rc6+f3.py, i have not tested X driver.
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
for me it has been very stable
El martes, 6 de noviembre de 2018, 7:59:53 (UTC+1), Alberto Sánchez
escribió:
>
> I am testing with kernel 4.4.50, the last Cameron's driver and weewx 3.8.2.
>
> I will inform if i have problems or not.
>
> Thanks for your support Cameron.
>
>
--
You
I am testing with kernel 4.4.50, the last Cameron's driver and weewx 3.8.2.
I will inform if i have problems or not.
Thanks for your support Cameron.
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop
Around 10 days uptime now.
I must conclude wmr300x driver is 100x100 stable with 4.4.* kernel.
Kernels later than 4.4 loses connection with wmr300 after some time.
El viernes, 26 de octubre de 2018, 18:44:04 (UTC+2), Ruben Navarro Huedo
escribió:
>
> 7 days now with wmr300x and 4.4.50 kernel.
7 days now with wmr300x and 4.4.50 kernel.
Let's continue testing.
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to weewx-user+unsubscr...@googlegroups.com.
For
4 days uptime with wmr300x driver and kernel 4.4.50
Going up.
El miércoles, 17 de octubre de 2018, 18:06:45 (UTC+2), Ruben Navarro Huedo
escribió:
>
> ok...i will do.
> Now testing 4.4 kernel with x driver.
>
> El miércoles, 17 de octubre de 2018, 2:02:36 (UTC+2), Cameron D escribió:
>>
>>
ok...i will do.
Now testing 4.4 kernel with x driver.
El miércoles, 17 de octubre de 2018, 2:02:36 (UTC+2), Cameron D escribió:
>
> There is a possibilty we are looking at two separate problems related to
> kernel version, but if it is the same cause then the libusb0 code hangs the
> kernel,
There is a possibilty we are looking at two separate problems related to
kernel version, but if it is the same cause then the libusb0 code hangs the
kernel, while the libusb1 code only causes the usb code to block access.
But is it only the wrm300 that is blocked, or all USB?
I think part of
1 Yes
2 Yes with no result.
3 Raspberry was perfectly running. I could ssh on it but impossible recover
USB connection with WMR300 without rebooting.
Testing now with 4.4.50 kernel.
El martes, 16 de octubre de 2018, 5:10:03 (UTC+2), Cameron D escribió:
>
> Sad.
> So the unresolved questions
Sad.
So the unresolved questions are:
1. was the wmr300 console still displaying the USB symbol after it
stopped?
2. did you try unplug/reinsert the usb cable?
3. was the kernel totally unresponsive - even after unplugging USB?
could you even ping it?
Cameron.
On Tuesday, 16
bad news :-(
After 7 days weewx lost connection with wmr300x and i had to reboot my
raspberry.
Going now to kernel 4.4 and driver wmr300x.
El domingo, 14 de octubre de 2018, 16:47:44 (UTC+2), Ruben Navarro Huedo
escribió:
>
> 6 days uptime using and going up:
>
> RASPBERRY PI ZERO W
> WMR300
>
6 days uptime using and going up:
RASPBERRY PI ZERO W
WMR300
KERNEL 4.14.70
WMR300X DRIVER
WEEWX 3.8.2
This is my highest uptime with 4.14 kernel.
El sábado, 13 de octubre de 2018, 0:46:49 (UTC+2), Ruben Navarro Huedo
escribió:
>
> Testing wmr300x driver with kernel 4.14.70
>
> 4 days uptime
Testing wmr300x driver with kernel 4.14.70
4 days uptime and going up.
In my first attempt with this driver and 4.14 kernel I lost connection with the
console 48 hours after starting.
I don't know what changed since the first attempt.
I continue testing...
--
You received this message
So what we have so far is:
*No Problem:*
*Vantage:* uses standard serial over USB kernel code (ttyusb)
*fousb*: uses PyUSB/libusb0; write via control channel; read uses
interruptRead() but only after control msg to request each packet
*Hangs:*
*WMR300*: uses PyUSB/libusb0; write via data
I will try it this weekend.
I will tell you the results.
El jueves, 4 de octubre de 2018, 17:55:04 (UTC+2), Andrew Milner escribió:
>
> For what I is worth I have never seen this on my RPi with either vantage
> driver or fousb driver with any kernel, and always update/upgrade every six
>
For what I is worth I have never seen this on my RPi with either vantage
driver or fousb driver with any kernel, and always update/upgrade every six
months or so.
On Thursday, 4 October 2018 18:30:02 UTC+3, Cameron D wrote:
>
> An issue has emerged where some systems, initially WMR300 and
16 matches
Mail list logo
