Re: SOLVED - Re: [weewx-user] Re: Dirty shutdown of my Fitlet, can't pull records from VantagePro2 data logger
Ah, now that's interesting. Thanks.
John
WB5THT
On 6/2/2019 11:48 AM, John wrote:
I seem to have found another solution, just disable weewx from
updating the console's clock. It is a setting in the weewx
configuration file.
On Sunday, June 2, 2019 at 8:55:45 AM UTC-5, John Canfield wrote:
Yes, it does have something to do with timestamps. Boy was I
chasing my tail for several days - bought a new Davis logger and
even bought the WiFi logger to try. I was on the verge of
rebuilding the entire Fitlet and then stumbled on a solution (a
blind chicken finds a piece of corn once in a while .)
My permanent (hopefully) 'fix' is I now have significantly more
UPS reserve minutes that should take me from about 60 minutes to
120-180 minutes.
John
WB5THT
On 6/1/2019 5:47 PM, John wrote:
I think I chased the same ghost a couple times. What I believe
the underlying problem is has to do with weewx incorrectly
changing the console's clock to an earlier time. The result is
that the console eventually appends a record to the datalogger
with an earlier timestamp than the previous record. Weewx
aborts reading the datalogger when it comes across the out of
order timestamp. Clearing the logger's memory, changing the
recording interval, etc ... gets around the problem, until it
happens again.
On Thursday, May 2, 2019 at 11:13:35 AM UTC-5, John Canfield wrote:
Finally. I've fiddled around so much with this my head is
spinning. weather.janeandjohn.org
<http://weather.janeandjohn.org> is current again. Hooray!
The short story:
- *the original Davis VP2 console is good*
- *the original Davis USB logger is good*
- did an upgrade to the latest weewx release
- I performed a sudo wee_database --update which caught my
webpage up to April 30, 2019
- restarted weewx and rebooted several times while trying
database commands (wee_database --drop-daily, sudo
wee_database --to=2019-05-02, sudo wee_device --set-interval=1)
- the magic seemed to be sudo wee_device --set-interval=1
which Tom said in another thread cleared the data logger (and
I rebooted again)
So apparently if the database gets screwed up as in not
current with the logger, you (at least me) can go off on a
tangent chasing an interface problem
John (WB5THT)
On Wednesday, May 1, 2019 at 2:34:32 PM UTC-5, John Canfield
wrote:
*This is driving me CRAZY!*
*
*
I thought I found the problem with a UPS monitor daemon
running (I had unplugged the USB cable from the
CyberPower box) - I stopped the process and set it to not
start at boot. Then it looked like weewx was talking to
the console but we had some kind of database problem
since I've been down for several days. It was updating my
web page with old data. Now I'm getting errors like it
can't talk to the logger. I did manage to do a logger
text dump but after fiddling around that won't work now.
I'm really frustrated and it's time to leave it alone and
come back later.
Sigh.
On Wednesday, May 1, 2019 at 12:23:23 PM UTC-5, vince wrote:
On Wednesday, May 1, 2019 at 10:21:15 AM UTC-7, John
Canfield wrote:
The enigma for me then is why does weewx report
the console woke up? A USB problem is the first
thing I thought of as well but the Fitlet does
report when ttyUSB0 is attached to a new port. G.
Thanks Vince, I need all of the help I can get
even though I'm not a weewx newbie - I was one of
Tom's beta testers with one of his first releases.
I think the minicom approach of trying to connect to
the console 'without' weewx is a good one, it's just
that the device might not match the one you're trying
to use.
Try disconnecting the usb then reconnecting it, then
use 'dmesg' to see what device it allocated.
--
You received this message because you are subscribed to a topic
in the Google Groups "weewx-user" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/weewx-user/-aw7xfmK7_4/unsubscribe
<https://groups.google.com/d/topic/weewx-user/-aw7xfmK7_4/unsubscribe>.
To unsubscribe from this group and all its topics, send an email
to weewx...@googlegroups.com .
To view this discussion on the web visit
https://groups.goog
Re: SOLVED - Re: [weewx-user] Re: Dirty shutdown of my Fitlet, can't pull records from VantagePro2 data logger
Yes, it does have something to do with timestamps. Boy was I chasing my
tail for several days - bought a new Davis logger and even bought the
WiFi logger to try. I was on the verge of rebuilding the entire Fitlet
and then stumbled on a solution (a blind chicken finds a piece of corn
once in a while .)
My permanent (hopefully) 'fix' is I now have significantly more UPS
reserve minutes that should take me from about 60 minutes to 120-180
minutes.
John
WB5THT
On 6/1/2019 5:47 PM, John wrote:
I think I chased the same ghost a couple times. What I believe the
underlying problem is has to do with weewx incorrectly changing the
console's clock to an earlier time. The result is that the console
eventually appends a record to the datalogger with an earlier
timestamp than the previous record. Weewx aborts reading the
datalogger when it comes across the out of order timestamp. Clearing
the logger's memory, changing the recording interval, etc ... gets
around the problem, until it happens again.
On Thursday, May 2, 2019 at 11:13:35 AM UTC-5, John Canfield wrote:
Finally. I've fiddled around so much with this my head is
spinning. weather.janeandjohn.org <http://weather.janeandjohn.org>
is current again. Hooray!
The short story:
- *the original Davis VP2 console is good*
- *the original Davis USB logger is good*
- did an upgrade to the latest weewx release
- I performed a sudo wee_database --update which caught my webpage
up to April 30, 2019
- restarted weewx and rebooted several times while trying database
commands (wee_database --drop-daily, sudo wee_database
--to=2019-05-02, sudo wee_device --set-interval=1)
- the magic seemed to be sudo wee_device --set-interval=1 which
Tom said in another thread cleared the data logger (and I rebooted
again)
So apparently if the database gets screwed up as in not current
with the logger, you (at least me) can go off on a tangent chasing
an interface problem
John (WB5THT)
On Wednesday, May 1, 2019 at 2:34:32 PM UTC-5, John Canfield wrote:
*This is driving me CRAZY!*
*
*
I thought I found the problem with a UPS monitor daemon
running (I had unplugged the USB cable from the CyberPower
box) - I stopped the process and set it to not start at boot.
Then it looked like weewx was talking to the console but we
had some kind of database problem since I've been down for
several days. It was updating my web page with old data. Now
I'm getting errors like it can't talk to the logger. I did
manage to do a logger text dump but after fiddling around that
won't work now. I'm really frustrated and it's time to leave
it alone and come back later.
Sigh.
On Wednesday, May 1, 2019 at 12:23:23 PM UTC-5, vince wrote:
On Wednesday, May 1, 2019 at 10:21:15 AM UTC-7, John
Canfield wrote:
The enigma for me then is why does weewx report the
console woke up? A USB problem is the first thing I
thought of as well but the Fitlet does report when
ttyUSB0 is attached to a new port. G.
Thanks Vince, I need all of the help I can get even
though I'm not a weewx newbie - I was one of Tom's
beta testers with one of his first releases.
I think the minicom approach of trying to connect to the
console 'without' weewx is a good one, it's just that the
device might not match the one you're trying to use.
Try disconnecting the usb then reconnecting it, then use
'dmesg' to see what device it allocated.
--
You received this message because you are subscribed to a topic in the
Google Groups "weewx-user" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/weewx-user/-aw7xfmK7_4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
weewx-user+unsubscr...@googlegroups.com
<mailto:weewx-user+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/7469e457-d7df-4b4e-bdb5-7fc11de81f7f%40googlegroups.com
<https://groups.google.com/d/msgid/weewx-user/7469e457-d7df-4b4e-bdb5-7fc11de81f7f%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/10c90cb3-4a2e-31ed-1456-42f5fe2d%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
SOLVED - Re: [weewx-user] Re: Dirty shutdown of my Fitlet, can't pull records from VantagePro2 data logger
Finally. I've fiddled around so much with this my head is spinning. weather.janeandjohn.org is current again. Hooray! The short story: - *the original Davis VP2 console is good* - *the original Davis USB logger is good* - did an upgrade to the latest weewx release - I performed a sudo wee_database --update which caught my webpage up to April 30, 2019 - restarted weewx and rebooted several times while trying database commands (wee_database --drop-daily, sudo wee_database --to=2019-05-02, sudo wee_device --set-interval=1) - the magic seemed to be sudo wee_device --set-interval=1 which Tom said in another thread cleared the data logger (and I rebooted again) So apparently if the database gets screwed up as in not current with the logger, you (at least me) can go off on a tangent chasing an interface problem John (WB5THT) On Wednesday, May 1, 2019 at 2:34:32 PM UTC-5, John Canfield wrote: > > *This is driving me CRAZY!* > > I thought I found the problem with a UPS monitor daemon running (I had > unplugged the USB cable from the CyberPower box) - I stopped the process > and set it to not start at boot. Then it looked like weewx was talking to > the console but we had some kind of database problem since I've been down > for several days. It was updating my web page with old data. Now I'm > getting errors like it can't talk to the logger. I did manage to do a > logger text dump but after fiddling around that won't work now. I'm really > frustrated and it's time to leave it alone and come back later. > > Sigh. > > On Wednesday, May 1, 2019 at 12:23:23 PM UTC-5, vince wrote: >> >> On Wednesday, May 1, 2019 at 10:21:15 AM UTC-7, John Canfield wrote: >>> >>> The enigma for me then is why does weewx report the console woke up? A >>> USB problem is the first thing I thought of as well but the Fitlet does >>> report when ttyUSB0 is attached to a new port. G. >>> >>> Thanks Vince, I need all of the help I can get even though I'm not a >>> weewx newbie - I was one of Tom's beta testers with one of his first >>> releases. >>> >>> >>> >> I think the minicom approach of trying to connect to the console >> 'without' weewx is a good one, it's just that the device might not match >> the one you're trying to use. >> >> Try disconnecting the usb then reconnecting it, then use 'dmesg' to see >> what device it allocated. >> > -- 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 options, visit https://groups.google.com/d/optout.
[weewx-user] Re: WU "capacity" issues, wunderfixer constantly finding missing records, et al
Ever since WU was sold it’s been going downhill. They dropped webcams a few months ago and then brought them back after a user uproar. I should look into an alternative. -- 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 options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Re: Dirty shutdown of my Fitlet, can't pull records from VantagePro2 data logger
*This is driving me CRAZY!* I thought I found the problem with a UPS monitor daemon running (I had unplugged the USB cable from the CyberPower box) - I stopped the process and set it to not start at boot. Then it looked like weewx was talking to the console but we had some kind of database problem since I've been down for several days. It was updating my web page with old data. Now I'm getting errors like it can't talk to the logger. I did manage to do a logger text dump but after fiddling around that won't work now. I'm really frustrated and it's time to leave it alone and come back later. Sigh. On Wednesday, May 1, 2019 at 12:23:23 PM UTC-5, vince wrote: > > On Wednesday, May 1, 2019 at 10:21:15 AM UTC-7, John Canfield wrote: >> >> The enigma for me then is why does weewx report the console woke up? A >> USB problem is the first thing I thought of as well but the Fitlet does >> report when ttyUSB0 is attached to a new port. G. >> >> Thanks Vince, I need all of the help I can get even though I'm not a >> weewx newbie - I was one of Tom's beta testers with one of his first >> releases. >> >> >> > I think the minicom approach of trying to connect to the console 'without' > weewx is a good one, it's just that the device might not match the one > you're trying to use. > > Try disconnecting the usb then reconnecting it, then use 'dmesg' to see > what device it allocated. > -- 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 options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Re: Dirty shutdown of my Fitlet, can't pull records from VantagePro2 data logger
The enigma for me then is why does weewx report the console woke up? A USB problem is the first thing I thought of as well but the Fitlet does report when ttyUSB0 is attached to a new port. G. Thanks Vince, I need all of the help I can get even though I'm not a weewx newbie - I was one of Tom's beta testers with one of his first releases. On Wednesday, May 1, 2019 at 12:05:28 PM UTC-5, vince wrote: > > On Wednesday, May 1, 2019 at 10:02:33 AM UTC-7, John Canfield wrote: >> >> Well that was no joy and I can't talk to the Davis console with minicom. >> I'm using the USB version of the logger, should have mentioned that before >> (and I did try a new USB logger). >> >>> >>> > Still sounds more like your usb device name changed or something along > those lines. > -- 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 options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Re: Dirty shutdown of my Fitlet, can't pull records from VantagePro2 data logger
Hi Tom,
Well that was no joy and I can't talk to the Davis console with minicom.
I'm using the USB version of the logger, should have mentioned that before
(and I did try a new USB logger). I'm thinking something in the file system
got corrupted with the unexpected shutdown. Maybe the next course of action
is to completely rebuild the Fitlet. Ugh.
John
john@beecreek ~ $ sudo wee_device --clear-memory
[sudo] password for john:
Using configuration file /etc/weewx/weewx.conf
Using Vantage driver version 3.0.9 (weewx.drivers.vantage)
Proceeding will erase old archive records.
Are you sure you wish to proceed (y/n)? y
Clearing the archive memory ...
Traceback (most recent call last):
File "/usr/bin/wee_device", line 54, in
main()
File "/usr/bin/wee_device", line 51, in main
device.configure(config_dict)
File "/usr/share/weewx/weewx/drivers/__init__.py", line 69, in configure
self.do_options(options, parser, config_dict, prompt)
File "/usr/share/weewx/weewx/drivers/vantage.py", line 1831, in do_options
self.clear_memory(station)
File "/usr/share/weewx/weewx/drivers/vantage.py", line 2092, in
clear_memory
station.clearLog()
File "/usr/share/weewx/weewx/drivers/vantage.py", line 1006, in clearLog
raise weewx.RetriesExceeded("While clearing log")
weewx.RetriesExceeded: While clearing log
On Wednesday, May 1, 2019 at 9:54:20 AM UTC-5, Thomas Keffer wrote:
>
> Hi, John
>
> It looks like you have two problems.
>
> 1. The message "vantage: Retrieving 93 page(s); starting index= 0",
> followed by no pages retrieved, suggests that the logger is corrupt. Try
> clearing
> it <http://weewx.com/docs/usersguide.htm#html_generated_but_not_updated>.
>
> 2. Some sort of (possibly intermittent) USB problem. I can't help you much
> on this one. It looks like you're using a serial-to-usb adapter. If you
> have another one around, try swapping.
>
> -tk
>
> On Wed, May 1, 2019 at 7:26 AM John Canfield > wrote:
>
>> *Just checked the kernel log and ttyUSB0 is reacting to me changing the
>> ports:*
>>
>> Apr 30 13:46:19 beecreek kernel: [16655.212235] usb 3-2: new full-speed
>> USB device number 2 using xhci_hcd
>> Apr 30 13:46:19 beecreek kernel: [16655.361518] usb 3-2: New USB device
>> found, idVendor=10c4, idProduct=ea61
>> Apr 30 13:46:19 beecreek kernel: [16655.361532] usb 3-2: New USB device
>> strings: Mfr=1, Product=2, SerialNumber=3
>> Apr 30 13:46:19 beecreek kernel: [16655.361540] usb 3-2: Product: CP2102
>> USB to UART Bridge Controller
>> Apr 30 13:46:19 beecreek kernel: [16655.361546] usb 3-2: Manufacturer:
>> Silicon Labs
>> Apr 30 13:46:19 beecreek kernel: [16655.361552] usb 3-2: SerialNumber:
>> 1255369079
>> Apr 30 13:46:19 beecreek kernel: [16655.367734] cp210x 3-2:1.0: cp210x
>> converter detected
>> Apr 30 13:46:19 beecreek kernel: [16655.368025] usb 3-2: cp210x converter
>> now attached to ttyUSB0
>> Apr 30 13:47:39 beecreek kernel: [16735.264504] usb 3-2: USB disconnect,
>> device number 2
>> Apr 30 13:47:39 beecreek kernel: [16735.266937] cp210x ttyUSB0: cp210x
>> converter now disconnected from ttyUSB0
>> Apr 30 13:47:39 beecreek kernel: [16735.266962] cp210x 3-2:1.0: device
>> disconnected
>> Apr 30 13:47:54 beecreek kernel: [16750.500795] usb 3-2: new full-speed
>> USB device number 3 using xhci_hcd
>> Apr 30 13:47:54 beecreek kernel: [16750.650118] usb 3-2: New USB device
>> found, idVendor=10c4, idProduct=ea60
>> Apr 30 13:47:54 beecreek kernel: [16750.650131] usb 3-2: New USB device
>> strings: Mfr=1, Product=2, SerialNumber=3
>> Apr 30 13:47:54 beecreek kernel: [16750.650139] usb 3-2: Product: CP2102
>> USB to UART Bridge Controller
>> Apr 30 13:47:54 beecreek kernel: [16750.650145] usb 3-2: Manufacturer:
>> Silicon Labs
>> Apr 30 13:47:54 beecreek kernel: [16750.650151] usb 3-2: SerialNumber:
>> 0001
>> Apr 30 13:47:54 beecreek kernel: [16750.656328] cp210x 3-2:1.0: cp210x
>> converter detected
>> Apr 30 13:47:54 beecreek kernel: [16750.657233] usb 3-2: cp210x converter
>> now attached to ttyUSB0
>> May 1 08:53:08 beecreek kernel: [85470.262589] ip_tables: (C) 2000-2006
>> Netfilter Core Team
>>
>> On Wednesday, May 1, 2019 at 9:17:58 AM UTC-5, John Canfield wrote:
>>>
>>> *We lost power a week ago and my UPS the Fitlet was on ran out of
>>> battery so we had a "pull the plug" situation on my weewx Linux Mint Fitlet
>>> (it's been running for two or three years fine). When power was restored I
>>> kept getting errors when we
[weewx-user] Re: Dirty shutdown of my Fitlet, can't pull records from VantagePro2 data logger
*Just checked the kernel log and ttyUSB0 is reacting to me changing the ports:* Apr 30 13:46:19 beecreek kernel: [16655.212235] usb 3-2: new full-speed USB device number 2 using xhci_hcd Apr 30 13:46:19 beecreek kernel: [16655.361518] usb 3-2: New USB device found, idVendor=10c4, idProduct=ea61 Apr 30 13:46:19 beecreek kernel: [16655.361532] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Apr 30 13:46:19 beecreek kernel: [16655.361540] usb 3-2: Product: CP2102 USB to UART Bridge Controller Apr 30 13:46:19 beecreek kernel: [16655.361546] usb 3-2: Manufacturer: Silicon Labs Apr 30 13:46:19 beecreek kernel: [16655.361552] usb 3-2: SerialNumber: 1255369079 Apr 30 13:46:19 beecreek kernel: [16655.367734] cp210x 3-2:1.0: cp210x converter detected Apr 30 13:46:19 beecreek kernel: [16655.368025] usb 3-2: cp210x converter now attached to ttyUSB0 Apr 30 13:47:39 beecreek kernel: [16735.264504] usb 3-2: USB disconnect, device number 2 Apr 30 13:47:39 beecreek kernel: [16735.266937] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 Apr 30 13:47:39 beecreek kernel: [16735.266962] cp210x 3-2:1.0: device disconnected Apr 30 13:47:54 beecreek kernel: [16750.500795] usb 3-2: new full-speed USB device number 3 using xhci_hcd Apr 30 13:47:54 beecreek kernel: [16750.650118] usb 3-2: New USB device found, idVendor=10c4, idProduct=ea60 Apr 30 13:47:54 beecreek kernel: [16750.650131] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Apr 30 13:47:54 beecreek kernel: [16750.650139] usb 3-2: Product: CP2102 USB to UART Bridge Controller Apr 30 13:47:54 beecreek kernel: [16750.650145] usb 3-2: Manufacturer: Silicon Labs Apr 30 13:47:54 beecreek kernel: [16750.650151] usb 3-2: SerialNumber: 0001 Apr 30 13:47:54 beecreek kernel: [16750.656328] cp210x 3-2:1.0: cp210x converter detected Apr 30 13:47:54 beecreek kernel: [16750.657233] usb 3-2: cp210x converter now attached to ttyUSB0 May 1 08:53:08 beecreek kernel: [85470.262589] ip_tables: (C) 2000-2006 Netfilter Core Team On Wednesday, May 1, 2019 at 9:17:58 AM UTC-5, John Canfield wrote: > > *We lost power a week ago and my UPS the Fitlet was on ran out of battery > so we had a "pull the plug" situation on my weewx Linux Mint Fitlet (it's > been running for two or three years fine). When power was restored I kept > getting errors when weewx tried to read the data logger in the VantagePro2. > It could wake up the console and then maybe pull a few records or lately > zero records and it gives up:* > > May 1 08:59:01 beecreek weewx[20103]: engine: Initializing weewx version > 3.6.2 > May 1 08:59:01 beecreek weewx[20103]: engine: Using Python 2.7.12 > (default, Nov 12 2018, 14: 36:49) #012[GCC 5.4.0 > 20160609] > May 1 08:59:01 beecreek weewx[20103]: engine: Platform > Linux-4.4.6-generic.fitlet-x86_64-wit > h-LinuxMint-18-sarah > May 1 08:59:01 beecreek weewx[20103]: engine: pid file is > /var/run/weewx.pid > May 1 08:59:01 beecreek weewx[20107]: engine: Using configuration file > /etc/weewx/weewx.conf > May 1 08:59:01 beecreek weewx[20107]: engine: Initializing engine > May 1 08:59:01 beecreek weewx[20107]: engine: Loading station type > Vantage (weewx.drivers.va ntage) > May 1 08:59:01 beecreek weewx[20107]: vantage: driver version is 3.0.9 > May 1 08:59:01 beecreek weewx[20090]:...done. > May 1 08:59:01 beecreek systemd[1]: Started LSB: weewx weather system. > May 1 08:59:01 beecreek weewx[20107]: vantage: Opened up serial port > /dev/ttyUSB0; baud 1920 0; timeout 5.00 > May 1 08:59:01 beecreek weewx[20107]: vantage: gentle wake up of console > successful > May 1 08:59:01 beecreek weewx[20107]: vantage: _setup; hardware type is 16 > May 1 08:59:01 beecreek weewx[20107]: engine: Loading service > weewx.engine.StdTimeSynch > May 1 08:59:01 beecreek weewx[20107]: engine: Finished loading service > weewx.engine.StdTimeS ynch > May 1 08:59:01 beecreek weewx[20107]: engine: Loading service > weewx.engine.StdConvert > May 1 08:59:01 beecreek weewx[20107]: engine: StdConvert target unit is > 0x1 > May 1 08:59:01 beecreek weewx[20107]: engine: Finished loading service > weewx.engine.StdConve rt > May 1 08:59:01 beecreek weewx[20107]: engine: Loading service > weewx.engine.StdCalibrate > May 1 08:59:01 beecreek weewx[20107]: engine: Finished loading service > weewx.engine.StdCalib rate > May 1 08:59:01 beecreek weewx[20107]: engine: Loading service > weewx.engine.StdQC > May 1 08:59:01 beecreek weewx[20107]: engine: Finished loading service > weewx.engine.StdQC > May 1 08:59:01 beecreek weewx[20107]: engine: Loading service > weewx.wxservices.StdWXCalculat
[weewx-user] Dirty shutdown of my Fitlet, can't pull records from VantagePro2 data logger
*We lost power a week ago and my UPS the Fitlet was on ran out of battery so we had a "pull the plug" situation on my weewx Linux Mint Fitlet (it's been running for two or three years fine). When power was restored I kept getting errors when weewx tried to read the data logger in the VantagePro2. It could wake up the console and then maybe pull a few records or lately zero records and it gives up:* May 1 08:59:01 beecreek weewx[20103]: engine: Initializing weewx version 3.6.2 May 1 08:59:01 beecreek weewx[20103]: engine: Using Python 2.7.12 (default, Nov 12 2018, 14: 36:49) #012[GCC 5.4.0 20160609] May 1 08:59:01 beecreek weewx[20103]: engine: Platform Linux-4.4.6-generic.fitlet-x86_64-wit h-LinuxMint-18-sarah May 1 08:59:01 beecreek weewx[20103]: engine: pid file is /var/run/weewx.pid May 1 08:59:01 beecreek weewx[20107]: engine: Using configuration file /etc/weewx/weewx.conf May 1 08:59:01 beecreek weewx[20107]: engine: Initializing engine May 1 08:59:01 beecreek weewx[20107]: engine: Loading station type Vantage (weewx.drivers.va ntage) May 1 08:59:01 beecreek weewx[20107]: vantage: driver version is 3.0.9 May 1 08:59:01 beecreek weewx[20090]:...done. May 1 08:59:01 beecreek systemd[1]: Started LSB: weewx weather system. May 1 08:59:01 beecreek weewx[20107]: vantage: Opened up serial port /dev/ttyUSB0; baud 1920 0; timeout 5.00 May 1 08:59:01 beecreek weewx[20107]: vantage: gentle wake up of console successful May 1 08:59:01 beecreek weewx[20107]: vantage: _setup; hardware type is 16 May 1 08:59:01 beecreek weewx[20107]: engine: Loading service weewx.engine.StdTimeSynch May 1 08:59:01 beecreek weewx[20107]: engine: Finished loading service weewx.engine.StdTimeS ynch May 1 08:59:01 beecreek weewx[20107]: engine: Loading service weewx.engine.StdConvert May 1 08:59:01 beecreek weewx[20107]: engine: StdConvert target unit is 0x1 May 1 08:59:01 beecreek weewx[20107]: engine: Finished loading service weewx.engine.StdConve rt May 1 08:59:01 beecreek weewx[20107]: engine: Loading service weewx.engine.StdCalibrate May 1 08:59:01 beecreek weewx[20107]: engine: Finished loading service weewx.engine.StdCalib rate May 1 08:59:01 beecreek weewx[20107]: engine: Loading service weewx.engine.StdQC May 1 08:59:01 beecreek weewx[20107]: engine: Finished loading service weewx.engine.StdQC May 1 08:59:01 beecreek weewx[20107]: engine: Loading service weewx.wxservices.StdWXCalculat e May 1 08:59:01 beecreek weewx[20107]: wxcalculate: The following values will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, dewpoint=prefer_hardware, appTemp=prefe r_hardware, rainRate=prefer_hardware, windrun=prefer_hardware, heatindex=prefer_hardware, max SolarRad=prefer_hardware, humidex=prefer_hardware, pressure=prefer_hardware, inDewpoint=prefe r_hardware, ET=prefer_hardware, altimeter=prefer_hardware, cloudbase=prefer_hardware May 1 08:59:01 beecreek weewx[20107]: wxcalculate: The following algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS May 1 08:59:01 beecreek weewx[20107]: engine: Finished loading service weewx.wxservices.StdW XCalculate May 1 08:59:01 beecreek weewx[20107]: engine: Loading service weewx.engine.StdArchive May 1 08:59:01 beecreek weewx[20107]: engine: Archive will use data binding wx_binding May 1 08:59:01 beecreek weewx[20107]: engine: Record generation will be attempted in 'hardwa re' May 1 08:59:01 beecreek weewx[20107]: engine: The archive interval in the configuration file (300) does not match the station hardware interval (600). May 1 08:59:01 beecreek weewx[20107]: engine: Using archive interval of 600 seconds (specifi ed by hardware) May 1 08:59:01 beecreek weewx[20107]: engine: Use LOOP data in hi/low calculations: 1 May 1 08:59:01 beecreek weewx[20107]: engine: Using binding 'wx_binding' to database 'weewx. sdb' May 1 08:59:01 beecreek weewx[20107]: manager: Starting backfill of daily summaries May 1 08:59:01 beecreek weewx[20107]: manager: Daily summaries up to date May 1 08:59:01 beecreek weewx[20107]: engine: Finished loading service weewx.engine.StdArchi ve May 1 08:59:01 beecreek weewx[20107]: engine: Loading service weewx.restx.StdStationRegistry May 1 08:59:01 beecreek weewx[20107]: restx: StationRegistry: Station will be registered. May 1 08:59:01 beecreek weewx[20107]: engine: Finished loading service weewx.restx.StdStatio nRegistry May 1 08:59:01 beecreek weewx[20107]: engine: Loading service weewx.restx.StdWunderground May 1 08:59:01 beecreek wee
Re: [weewx-user] #1 - Missing 20 days in monthly summary #2 - User guide error?
Ah-so. Thanks Tom. Any idea about the missing data? On Monday, March 13, 2017 at 4:27:21 PM UTC-5, Tom Keffer wrote: > > --rebuild-daily is the command used by later versions. Earlier versions > use --backfill-daily. > > -tk > > On Mon, Mar 13, 2017 at 1:26 PM, John Canfield > wrote: > >> weewx v3.6.2 on the new Fitlet, weewx 3.0.1 on the old FIT >> >> #1: I've just brought up weewx on another Fitlet (CompuLab fanless) and >> have it running okay. Poking around I discovered I'm missing Feb 1 to Feb >> 20 in the monthly summary. I copied over the weewx.sdb from the old FIT >> to the new Fitlet, I thought this was the entire database file? >> >> >> *(side note to TK - Tom, I've had that old FIT on-line for over seven >> years. Seven years ago I was having some trouble with it stopping due to >> the dropping USB port but the ferrite chokes on the Davis interface cable >> solved that problem) * >> #2: I discovered that the wee_database --rebuild-daily flag in the >> below user manual section isn't correct. *"wee_database: error: no such >> option: --rebuild-daily"* >> >> snip from the User Manual >> Rebuilding the daily summaries >> >> The wee_database utility can also be used to rebuild the daily >> summaries: >> >> wee_database weewx.conf --rebuild-daily >> -- snip -- >> >> John >> weather.janeandjohn.org >> >> -- >> 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+...@googlegroups.com . >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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 options, visit https://groups.google.com/d/optout.
[weewx-user] #1 - Missing 20 days in monthly summary #2 - User guide error?
weewx v3.6.2 on the new Fitlet, weewx 3.0.1 on the old FIT #1: I've just brought up weewx on another Fitlet (CompuLab fanless) and have it running okay. Poking around I discovered I'm missing Feb 1 to Feb 20 in the monthly summary. I copied over the weewx.sdb from the old FIT to the new Fitlet, I thought this was the entire database file? *(side note to TK - Tom, I've had that old FIT on-line for over seven years. Seven years ago I was having some trouble with it stopping due to the dropping USB port but the ferrite chokes on the Davis interface cable solved that problem) * #2: I discovered that the wee_database --rebuild-daily flag in the below user manual section isn't correct. *"wee_database: error: no such option: --rebuild-daily"* snip from the User Manual Rebuilding the daily summaries The wee_database utility can also be used to rebuild the daily summaries: wee_database weewx.conf --rebuild-daily -- snip -- John weather.janeandjohn.org -- 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 options, visit https://groups.google.com/d/optout.
Re: [weewx-user] Hardware discussion: Time to retire my faithful PC-Fit Slim from Compulab :(
Hey Tom,
Thanks for the link. When I get the new one in production I'll rebuild
the FIT - don't need all of the desktop stuff and X, that would really
simplify the install. That little guy should keep going for a long time.
I might replace the HDD with SDD, then no moving parts.
I think I have the Mint box ready to go, just need to get off my duff
and get it plugged in.
John
weather.janeandjohn.org
On 3/4/2017 9:53 AM, Thomas Keffer wrote:
Hi, John!
My Fit-PC is still going strong, after over 8 years of continual duty.
About 3 or 4 years ago, I reinstalled the operating system for reasons
I don't recall. Like you, I could not get a more modern version of
Ubuntu to work. Fortunately, Ubuntu has a repository of previously
released versions <http://old-releases.ubuntu.com/releases/>, so I
just reinstalled 8.04 ("Hardy Heron"), which works fine (32-bits, of
course).
The other trick is to install the "server" version, which is much
smaller and simpler, with fewer things to go wrong.
I'll bet there's still a few years of life left in that box of yours!
-tk
On Fri, Feb 24, 2017 at 10:04 AM, John Canfield
mailto:johnwcanfi...@gmail.com>> wrote:
Long time weewx user here, I think I was Tom's first or second
beta user (V 0.9). I started using hacked Linksys NSLU2s (aka
'slugs') but the flash memory would get corrupted after a few
months. Tom and I hooked up in a forum discussing the then new
PC-Fit Slims, a tiny fanless low-power PC which was a /perfect
/hardware platform for weewx. The PC-Fit's were expensive but
highly reliable. I think I've had this particular PC-Fit Slim
running for five or six years, one time I think a sector got
corrupted on its HDD and I had to rebuild the system.
Recently it wouldn't answer a heartbeat ping from my WebSwitch
(remote power controller) about once a week and the switch would
power cycle that outlet. This is very unusual, it would previously
run for months with no attention needed. I think for some reason
the network would go down and for a while I thought that it was
basically bricked. It finally came up and I thought I better
retire the box, rebuild it and keep it for a spare. The Ubuntu
version wasn't being supported any longer so that was another good
reason to rebuilt it.
The PC-Fit Slim's are long retired and Compulab has a new series
of boxes, after looking at less expensive alternatives I decided
to stick with Compulab. So in front of me as I type this is a
brand new unopened MintBox Mini Pro. AMD A10 Micro-6700T
microprocessor, 2Gb ram, 120Gb SSD. The box has the latest Linux
Mint pre-installed.
So we will have fun getting this guy set up and running. I've
never used Linux Mint but it's based on Debian and Ubuntu so there
shouldn't be any surprises.
John
WB5THT - weather.janeandjohn.org <http://weather.janeandjohn.org>,
CWOP EW0158
--
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
<mailto:weewx-user+unsubscr...@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout
<https://groups.google.com/d/optout>.
--
You received this message because you are subscribed to a topic in the
Google Groups "weewx-user" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/weewx-user/DTw0qsvz2uk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
weewx-user+unsubscr...@googlegroups.com
<mailto:weewx-user+unsubscr...@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.
--
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 options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Hardware discussion: Time to retire my faithful PC-Fit Slim from Compulab :(
Things haven't gone well from the startup splash dialogue. It asked for my name, name of the box, password; unfortunately I said ask for password on console. When it restarted I couldn't log in. I had it start in grub and then boot into a root shell and after poking around discovered my login was my first name in lower case and not my full name I previously entered. Then figuring out in desktop mode how to update the distro was a PITA. Then I had to reenter my password with each admin/settings dialog. Stupid desktop - takes five times longer to do any admin. On the plus side, it's a fast little box. On Friday, February 24, 2017 at 12:32:20 PM UTC-6, vince wrote: > > On Friday, February 24, 2017 at 7:04:33 AM UTC-8, John Canfield wrote: >> >> I've never used Linux Mint but it's based on Debian and Ubuntu so there >> shouldn't be any surprises. >> > > That made me laugh for some reason. > > Let us know how it goes, looks like a nice little box. > -- 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 options, visit https://groups.google.com/d/optout.
[weewx-user] Hardware discussion: Time to retire my faithful PC-Fit Slim from Compulab :(
Long time weewx user here, I think I was Tom's first or second beta user (V 0.9). I started using hacked Linksys NSLU2s (aka 'slugs') but the flash memory would get corrupted after a few months. Tom and I hooked up in a forum discussing the then new PC-Fit Slims, a tiny fanless low-power PC which was a *perfect *hardware platform for weewx. The PC-Fit's were expensive but highly reliable. I think I've had this particular PC-Fit Slim running for five or six years, one time I think a sector got corrupted on its HDD and I had to rebuild the system. Recently it wouldn't answer a heartbeat ping from my WebSwitch (remote power controller) about once a week and the switch would power cycle that outlet. This is very unusual, it would previously run for months with no attention needed. I think for some reason the network would go down and for a while I thought that it was basically bricked. It finally came up and I thought I better retire the box, rebuild it and keep it for a spare. The Ubuntu version wasn't being supported any longer so that was another good reason to rebuilt it. The PC-Fit Slim's are long retired and Compulab has a new series of boxes, after looking at less expensive alternatives I decided to stick with Compulab. So in front of me as I type this is a brand new unopened MintBox Mini Pro. AMD A10 Micro-6700T microprocessor, 2Gb ram, 120Gb SSD. The box has the latest Linux Mint pre-installed. So we will have fun getting this guy set up and running. I've never used Linux Mint but it's based on Debian and Ubuntu so there shouldn't be any surprises. John WB5THT - weather.janeandjohn.org, CWOP EW0158 -- 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 options, visit https://groups.google.com/d/optout.
