On Friday, 10 March 2017 21:58:21 UTC+10, Ruben Navarro Huedo wrote:
>
>
>
> In another vein: Have we some more information about clearing console
> datalogger from weewx
>
Well, it's nearly a month now, and I still cannot reply in the positive.
I have posted the command sequence to the devel
Hello wmr300 friends.
I want add a second wireless transmiter to my wmr300.
I will use :
One transmitter (Oregon *STC300)* using channel 1 for: Temp, Humid and Rain
Another transmitter (Also STC300) using channel 2 for: Wind
I need to read all this sensors like one only weather station.
WMR-300 con
This could be a GREAT new addon !
El viernes, 24 de febrero de 2017, 1:18:26 (UTC+1), Cameron D escribió:
>
> I have the captures of the windows software clearing the log, but have not
> yet had time to analyse them.
>
> On Friday, 24 February 2017 01:55:18 UTC+10, mwall wrote:
>>
>>
>> if the lo
I have the captures of the windows software clearing the log, but have not
yet had time to analyse them.
On Friday, 24 February 2017 01:55:18 UTC+10, mwall wrote:
>
>
> if the logger is full, then you will 'lose' data. apparently the wmr300
> logger must be cleared by punching buttons on the co
I understand.
Problem was logger is FULL.
El jueves, 23 de febrero de 2017, 16:55:18 (UTC+1), mwall escribió:
>
> On Thursday, February 23, 2017 at 10:47:22 AM UTC-5, Ruben Navarro Huedo
> wrote:
>>
>> Running now fine with last driver.
>> I has readed data from the datalogger from the wmr-300 i
On Thursday, February 23, 2017 at 10:47:22 AM UTC-5, Ruben Navarro Huedo
wrote:
>
> Running now fine with last driver.
> I has readed data from the datalogger from the wmr-300 installation.
> This is OK, but if i disconnect it some time (for example 30 minutes)
> after starting weewx it begins to
Running now fine with last driver.
I has readed data from the datalogger from the wmr-300 installation.
This is OK, but if i disconnect it some time (for example 30 minutes) after
starting weewx it begins to log real time data but looses these 30 minutes.
Is this Ok?
A lot of thank's
El jueves,
Excuse me it was an human error.
We didn't update driver.
After updating to last driver all is 100% fine.
Thank's a lot.
El jueves, 23 de febrero de 2017, 3:55:22 (UTC+1), Cameron D escribió:
>
>
>
> On Thursday, 23 February 2017 04:53:00 UTC+10, Ruben Navarro Huedo wrote:
>>
>>
>> My station
On Thursday, 23 February 2017 04:53:00 UTC+10, Ruben Navarro Huedo wrote:
>
>
> My stations has been running 40 days and data has nos been transfered to
> PC.
> It is connected to a raspberry pi
>
"nos"? did you mean "now" or "not"?
What is the logging interval set on the WRM300 console? at 1
On Wednesday, February 22, 2017 at 1:53:00 PM UTC-5, Ruben Navarro Huedo
wrote:
>
> A lot of thank's
>
> My stations has been running 40 days and data has nos been transfered to
> PC.
>
40 days?
which version of the wmr300 driver are you running?
> Weewx has detected ok wmr300 but it is re
A lot of thank's
My stations has been running 40 days and data has nos been transfered to PC.
It is connected to a raspberry pi3
Weewx has detected ok wmr300 but it is reading records.
I can only read on log: "reading records since *NA**
Is this ok?
how many time could it take?
Thank's a lot.
Hi m,
This last version works fine. Previous version as well.
I've found out the error is caused by a usb cable.
It is a usb 2.0 cable which works fine with other devices.
Quite strange.
Thank you for your support.
> On Sunday, February 12, 2017 at 7:53:50 PM UTC+1, mwall wrote:
>>
>> miguel
Hi mwall,
I have tested your last driver and It seems to work well.
Thanks.
El 15 feb. 2017 3:34 AM, "Cameron D" escribió:
> Hi MWall,
> The legacy pyusb interface used in the current wmr300 driver only talks to
> libusb0, as far as I can tell.
> Using the pyusb 1.0 interface I can specify whi
Hi MWall,
The legacy pyusb interface used in the current wmr300 driver only talks to
libusb0, as far as I can tell.
Using the pyusb 1.0 interface I can specify which version of libusb to use
or tell which one is called by default. I have put that code in my
"wmr300c" driver. I mainly use libusb
On Tuesday, February 14, 2017 at 8:08:15 PM UTC-5, Cameron D wrote:
>
> On Monday, 13 February 2017 03:26:27 UTC+10, Miguel Iniesta wrote:
>>
>> feb 12 18:20:39 raspberrypi weewx[4058]: wmr300: e.errno=None
>> e.strerror=None e.message=could not detach kernel driver from interface 0:
>> No data a
On Monday, 13 February 2017 03:26:27 UTC+10, Miguel Iniesta wrote:
>
>
> Hi m,
>
> This is the new error message (twice per second):
>
> weewx.service - LSB: weewx weather system
>Loaded: loaded (/etc/init.d/weewx)
>Active: active (running) since dom 2017-02-12 18:17:30 CET; 3min 10s ago
Hi m,
Don't have access to the station at weekdays. Hope I can do it next weekend.
Also on another computer to discard a raspi problem.
Thanks.
On Sunday, February 12, 2017 at 7:53:50 PM UTC+1, mwall wrote:
>
> miguel,
>
> please try the attached wmr300-0.18rc4.py
>
> m
>
>
--
You received t
On Sunday, February 12, 2017 at 12:26:27 PM UTC-5, Miguel Iniesta wrote:
>
> This is the new error message (twice per second):
>
> weewx.service - LSB: weewx weather system
>Loaded: loaded (/etc/init.d/weewx)
>Active: active (running) since dom 2017-02-12 18:17:30 CET; 3min 10s ago
> Proc
Hi m,
This is the new error message (twice per second):
weewx.service - LSB: weewx weather system
Loaded: loaded (/etc/init.d/weewx)
Active: active (running) since dom 2017-02-12 18:17:30 CET; 3min 10s ago
Process: 4043 ExecStart=/etc/init.d/weewx start (code=exited,
status=0/SUCCESS)
On Sunday, February 12, 2017 at 5:23:54 AM UTC-5, Miguel Iniesta wrote:
>
> Hi m,
>
> After that line, there is nothing else in the log related to weewx: No
> errors or any activity recorded.
> At that moment, there was just 5 hours of data to read because, as I could
> not find any error messa
Hi m,
After that line, there is nothing else in the log related to weewx: No
errors or any activity recorded.
At that moment, there was just 5 hours of data to read because, as I could
not find any error message, I thought it was a station problem so I deleted
the station's data log records.
A
On Saturday, February 11, 2017 at 1:46:27 PM UTC-5, Miguel Iniesta wrote:
>
> Hello,
>
> I am testing the new versions and unfortunately they do not work for me.
> No data from the station but also no error message it seems.
>
> Any help please?
>
miguel,
the portion of the log that you posted
I believe that I had the same problem the first time I tested that driver.
I solved it simply restarting raspbian.
El 11 feb. 2017 19:46, "Miguel Iniesta" escribió:
> Hello,
>
> I am testing the new versions and unfortunately they do not work for me.
> No data from the station but also no error
Hello,
I am testing the new versions and unfortunately they do not work for me.
No data from the station but also no error message it seems.
Any help please?
Thanks
Linux raspberrypi 4.4.38-v7+ #938
libusb-0.1-4:armhf 2:0.1.12-25
libusb-1.0-0:armhf 2:1.0.19-1
python-usb
0.18rc3 seems to work correctly.
Thank you very much mwall!!
El domingo, 5 de febrero de 2017, 15:35:34 (UTC+1), mwall escribió:
>
> the 0.18rc3 driver *should* handle the 'no data available' and 'no error'
> conditions properly for english, italian, german, french, and spanish
> locales.
>
>
>
> ii libusb-0.1-4:armhf 2:0.1.12-25
> armhfuserspace USB programming library
> ii libusb-1.0-0:armhf 2:1.0.19-1
>armhfuserspace USB programming library
> ii libusbmuxd2:ar
the 0.18rc3 driver *should* handle the 'no data available' and 'no error'
conditions properly for english, italian, german, french, and spanish
locales.
it does not yet handle timeouts properly. ideally it would recognize and
ignore timeouts on the initial communication, then recognize and fai
On Sunday, February 5, 2017 at 7:34:02 AM UTC-5, Alberto Sánchez wrote:
>
> Hi mwall,
>
> I am testing your new WMR300 drivers. 0,18rc2. It collects me data
> correctly but reports me this error:
>
> Feb 05 13:29:16 raspberrypi weewx[1369]: wmr300: e.errno=None
> e.strerror=None e.message=could n
Hi mwall,
I am testing your new WMR300 drivers. 0,18rc2. It collects me data
correctly but reports me this error:
Feb 05 13:29:16 raspberrypi weewx[1369]: wmr300: e.errno=None
e.strerror=None e.message=could not detach kernel driver from interface 0:
No data available repr=USBError('could not
Michael,
The code labelled wmr300c is my test driver to try to understand the
timeout issues. It should work with the "A" model as well as the euro
model hardware wmr300.
You can copy it in alongside the normal wmr300 driver and switch between
them by manually editing the config file. I have not
I get a timeout error.
On Dec 26, 2016 3:46 PM, "mwall" wrote:
>
>
> On Monday, December 26, 2016 at 3:08:20 PM UTC-5, Michael Nigbor wrote:
>>
>> I installed 3.6.2 today on Ubuntu (old HP laptop) attached to a WMR300a.
>> I am having the same problem described in this thread: no data from the
>
Hi Alberto,
OK - the comms errors would make sense to explain that.
If you are planning to erase and start again then a bottle of water
helps speed up the rainfall.
Or lift the raingauge top off and tip the rain buckets to and fro. That
way you can even count how much "rain" you have had.
Don't
Hi Cameron,
I have had erroneous rain readings (9000mm or even more), I think due to
communication failures and in some cases I found cobwebs in the rain gauge.
Because of this I think I have reached the limit. At the moment I am in
tests, as soon as the weather station works correctly I will er
Hi Alberto,
I have just checked my system after some rain and the database contents
look sensible. I can see rain increments of 0.01 and 0.02 (inches) in
my 1-minute sample interval.
The web page shows total rain as 6.6mm since midnight, which agrees with
the console.
I am using Weewx 3.6.2, but
On Tuesday, December 20, 2016 at 1:31:30 PM UTC-5, Alberto Sánchez wrote:
>
>
> In the rain counter of the console appeared "HHH mm". I just reset and has
> been zeroed.
>
>>
>>
this is typical behavior when the rain counter of the wmr300 has reached
its maximum value.
once it reaches maximum va
|Alberto
It is POSSIBLE that WU reports the time since the last reading change - but
I still do not see what is happening because you do NOT have rapid fire
enabled in the weewx.conf you posted.
Do you have multiple instances of weewx running by any chance - can you do
ps -A and check that wee
Thanks you very much both,
Andrew,
This is the data in the database
RainRate Rain
1482207600 0.0048387097 0
1482207900 0.04 0
1482208200 0.04 0
1482208500 0.0478787878 0
1482208800 0.0091428571 0
I have also seen what you comment on wunderground. I do not know what may
be
On Tuesday, December 20, 2016 at 1:35:14 AM UTC-5, Alberto Sánchez wrote:
>
> Hi mwall,
>
> It has rained tonight. The console has registered the rain and weewx has
> recorded the rain rate well but has not calculated the total rain. Example:
> Today's Rain 0.0 mm
> High Rain Rate 1.3 mm / hr at
Alberto - I do not fully understand your weather underground station. If I
watch your station for a while it looks as though there are two stations
reporting - the last reported time keeps jumping between two sequences eg
it can report last reported 10 secs ago, 15 secs ago, 8 minutes ago, 20
Hi mwall,
It has rained tonight. The console has registered the rain and weewx has
recorded the rain rate well but has not calculated the total rain. Example:
Today's Rain 0.0 mm
High Rain Rate 1.3 mm / hr at 05:19:22 AM
Weewx 3.6.1
Driver 0,15RC3
--
You received this message because you are
I wanted to say that "I no longer lose data" with the new location of the
console.
El 13 dic. 2016 8:38, "Alberto Sánchez" escribió:
> Hi mwall,
>
> Thanks for the information, I've changed the location of my console and I
> no longer date. I agree with you on reading barometer data.
>
> I only
I am noob with Raspberry and weewx, so I have done a clean installation of
raspbian (Jessie) and Weewx 3.6.1 with the same result:
pi@raspberrypi:~ $ sudo /etc/init.d/weewx status -l
● weewx.service - LSB: weewx weather system
Loaded: loaded (/etc/init.d/weewx)
Active: active (running) sin
I have tried with 0.10 driver but I have error too. The only driver that I
can use is 0.9.
0.10 driver error:
sudo /etc/init.d/weewx status -l
● weewx.service - LSB: weewx weather system
Loaded: loaded (/etc/init.d/weewx)
Active: active (running) since dom 2016-11-06 10:09:21 CET; 36s ag
pi@raspberrypi:~ $ dpkg -l | grep usb
ii libusb-0.1-4:armhf2:0.1.12-25
armhfuserspace USB programming library
ii libusb-1.0-0:armhf2:1.0.19-1
armhfuserspace USB programming libra
Hi Mwall,
Here my error, with Rasbian Jessy:
$ sudo /etc/init.d/weewx status -l
● weewx.service - LSB: weewx weather system
Loaded: loaded (/etc/init.d/weewx)
Active: active (running) since vie 2016-11-04 07:32:31 CET; 37s ago
Process: 19854 ExecStop=/etc/init.d/weewx stop (code=exited,
On Thursday, November 3, 2016 at 4:45:22 PM UTC-4, Alberto Sánchez wrote:
>
> Hi,
>
> I just test the new driver and I have the same Roland error. Thank you
> very much.
>
alberto, could you post the errors you get with the 0.15rc1 driver? thank
you!
--
You received this message because you
ii libusb-0.1-4:amd64
2:0.1.12-28 amd64userspace USB
programming library
ii libusb-1.0-0:amd64
2:1.0.20-1amd64userspace USB
programming library
hi python-us
Full output of dpkg -l | grep usb is attached for better reading.
Regards,
Roland
Am Donnerstag, 3. November 2016 21:37:56 UTC+1 schrieb mwall:
>
> On Thursday, November 3, 2016 at 1:07:53 PM UTC-4, Roland Ehle wrote:
>>
>> I gave it a try, but I had the following errors in the log with debug = 0
On Thursday, November 3, 2016 at 1:07:53 PM UTC-4, Roland Ehle wrote:
>
> I gave it a try, but I had the following errors in the log with debug = 0
>
> Nov 3 18:01:42 lin01 weewx[19698]: wmr300: usb failure: could not detach
> kernel driver from interface 0: Keine Daten verfügbar
> Nov 3 18:01:4
Hi,
I just test the new driver and I have the same Roland error. Thank you very
much.
--
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...@goog
On Thursday, November 3, 2016 at 4:17:43 PM UTC-4, Alberto Sánchez wrote:
>
> Thank you very much for your answer.
>
> I have tested the new driver and report me this error:
>
alberto, the DOCTYPE indicates that the wmr300.py file was not downloaded
properly. you must download the raw .py file.
Thank you very much for your answer.
I have tested the new driver and report me this error:
weewx.service - LSB: weewx weather system
Loaded: loaded (/etc/init.d/weewx)
Active: active (exited) since jue 2016-11-03 20:59:24 CET; 3s ago
Process: 14515 ExecStop=/etc/init.d/weewx stop (code
I gave it a try, but I had the following errors in the log with debug = 0
Nov 3 18:01:42 lin01 weewx[19698]: wmr300: usb failure: could not detach
kernel driver from interface 0: Keine Daten verfügbar
Nov 3 18:01:42 lin01 weewx[19698]: engine: Caught WeeWxIOError: could not
detach kernel drive
On Tuesday, November 1, 2016 at 4:49:24 PM UTC-4, Alberto Sánchez wrote:
>
> I have had the same problem and I have solve it with the same solution.
> Using 3.5.0 wmr 300 driver.
alberto, roland, and others,
please try the latest wmr300 driver (0.15rc1). it uses the usb
initialization logic f
Sorry in my case I use a raspberry pi 3 with raspbyan Jessy.
--
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 more opti
I have had the same problem and I have solve it with the same solution. Using
3.5.0 wmr 300 driver.
Thank you
--
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 wee
Thank you Matthew. After some more digging and testing I came to the
conclusion: It is not weewx itself that causes the issue, but the WMR300
driver for some reason. I downgraded to weewx 3.5.0 and everything worked
fine. After copying the WMR300 driver files I upgraded again to the latest
vers
On Thursday, October 27, 2016 at 1:12:29 PM UTC-7, Roland Ehle wrote:
>
> Downgrade to python-usb 0.4.3 did not change the behavior. Clean install
> of Ubuntu 14.04.5 followed by a clean install of weewx 3.6.1 did not change
> the behavior. No I took a brand new Raspberry, put weewx on it, but I
Downgrade to python-usb 0.4.3 did not change the behavior. Clean install of
Ubuntu 14.04.5 followed by a clean install of weewx 3.6.1 did not change
the behavior. No I took a brand new Raspberry, put weewx on it, but I have
exactly the same issue. In the past I was running my station on a Raspbe
On Tuesday, October 25, 2016 at 12:23:45 PM UTC-4, Roland Ehle wrote:
>
> Thanks for your response. If necessary I am willing to downgrade to ubuntu
> 14.04
>
> I am on Ubuntu 16.04 with Kernel 4.4.0-45-generic
> I have
> python-usb 1.0.0~b2
> libusb-1.0-0 1.0.20-1
> libusb-0.1-4 0.1.23-28
>
>
r
Here is the output of lsusb -v -d
root@lin01:~# lsusb -v -d 0fde:ca08
Bus 001 Device 006: ID 0fde:ca08 Oregon Scientific
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass0 (Defined at Interface level)
bDeviceSubClass
Thanks for your response. If necessary I am willing to downgrade to ubuntu
14.04
I am on Ubuntu 16.04 with Kernel 4.4.0-45-generic
I have
python-usb 1.0.0~b2
libusb-1.0-0 1.0.20-1
libusb-0.1-4 0.1.23-28
2016-10-25 2:38 GMT+02:00 mwall :
> On Monday, October 24, 2016 at 3:01:47 PM UTC-4, Roland E
62 matches
Mail list logo
