[weewx-user] Re: V3.9.1

[Eelco F]

Op zaterdag 9 februari 2019 01:31:11 UTC+1 schreef mwall:
>
> On Friday, February 8, 2019 at 6:45:36 PM UTC-5, Eelco F wrote:
>>
>> dpkg: fout: --compare-versions verwacht drie argumenten:  
>>  
>>
>> So it's still running 3.8.2. Where is the error here?
>>
>>>
> did you remove the line 'version = ...' from your weewx.conf at some 
> point?  did you delete the weewx.conf.dist file at some point?
>
> please post the output from these two commands:
>
> grep version /etc/weewx/weewx.conf | sed -e 's/\s*version\s*=\s*//' | sed 
> -e 's/-.*//'
>
> and:
>
> grep version /etc/weewx/weewx.conf.dist | sed -e 's/\s*version\s*=\s*//' | 
> sed -e 's/-.*//'
>
> m
>

Dear matthew,

I did not remove the version number. However i tjink i found the issue, by 
the first of your commands, Iḿ using the crt extension, and i editited 
crt.py somewhat, so it will give me an output in the format I use to feed 
to canvas gauges. I put a comment in weewx.conf as a reminder to my self 
that said:

# Options for extension 'crt', remember that crt.py is a customized 
version!!

so your first command gave me the output:
3.8.2
# Options for extension 'crt', remember that crt.py is a customized 
version!!


I suppose the word "version" in my comment was picked up, by  
--compare-versions, I changed the comment to "remember CRT.py is cutomized" 
and now install is just running fine.
Many thanks for putting me in the right place to search. You guys are 
really doing a good job!

Eelco

-- 
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: V3.9.1

[Eelco F]

Oh, and i'm getting this error now from crt.py (v0.18)

Feb  9 00:25:12 weerstation weewx[32454]: crt: crt: Exception while 
handling data: unsupported operand type(s) for -: 'NoneType' and 'NoneType'
Feb  9 00:25:12 weerstation weewx[32454]: crt:  Traceback (most recent 
call last):
Feb  9 00:25:12 weerstation weewx[32454]: crt:    File 
"/usr/share/weewx/user/crt.py", line 456, in handle_data
Feb  9 00:25:12 weerstation weewx[32454]: crt:  data = 
self.calculate(event_data, dbm)
Feb  9 00:25:12 weerstation weewx[32454]: crt:    File 
"/usr/share/weewx/user/crt.py", line 647, in calculate
Feb  9 00:25:12 weerstation weewx[32454]: crt: 
 data['sunshine_hours'] = calc_daylight_hours(alm)
Feb  9 00:25:12 weerstation weewx[32454]: crt:    File 
"/usr/share/weewx/user/crt.py", line 285, in calc_daylight_hours
Feb  9 00:25:12 weerstation weewx[32454]: crt:  return (sunset - 
sunrise) / 3600.0
Feb  9 00:25:12 weerstation weewx[32454]: crt:  TypeError: unsupported 
operand type(s) for -: 'NoneType' and 'NoneType'


Op woensdag 6 februari 2019 14:40:34 UTC+1 schreef Thomas Keffer:
>
> Well, that was a record short release. We found a serious bug in v3.9.0 
> that could break skins that do not have fonts defined, such as cmon.
>
> So, we are releasing v3.9.1, found in the usual place 
> .
>
> -tk
>

-- 
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: V3.9.1

[Eelco F]

I just did an update on one of my weather stations through apt update and 
apt upgrade on ubuntu 16.04, I choose to keep the old version of weewx.conf
However it yields an error:
dpkg: fout: --compare-versions verwacht drie argumenten:   


This is in dutch, but it means:
dpkg:error: --compare-versions expects three arguments:  
 


Complete output (in dutch):

Instellen van weewx (3.9.1-1) ...

Configuratiebestand '/etc/weewx/weewx.conf'
 ==> Gewijzigd (door u of door een script) sinds de installatie.
 ==> Pakketdistributeur heeft een bijgewerkte versie gemaakt.
   Wat wilt u er aan doen ?  De volgende keuzes zijn mogelijk:
Y of I  : installeer de versie van de pakketbeheerder
N of O  : behoud de huidige geïnstalleerde versie
  D : toon de verschillen tussen de versies
  Z : start een shell om de situatie te onderzoeken
 De standaardactie is om uw huidige versie te behouden.
*** weewx.conf (Y/I/N/O/D/Z) [standaard=N] ? N
Nieuwe versie van configuratiebestand /etc/weewx/weewx.conf.dist wordt 
geïnstalleerd ...
Nieuwe versie van configuratiebestand 
/etc/weewx/logwatch/scripts/services/weewx wordt geïnstalleerd ...
Nieuwe versie van configuratiebestand /etc/weewx/skins/Rsync/skin.conf 
wordt geïnstalleerd ...
Nieuwe versie van configuratiebestand 
/etc/weewx/skins/Standard/index.html.tmpl wordt geïnstalleerd ...
Nieuwe versie van configuratiebestand /etc/weewx/skins/Standard/skin.conf 
wordt geïnstalleerd ...
Nieuwe versie van configuratiebestand /etc/weewx/skins/Ftp/skin.conf wordt 
geïnstalleerd ...
Nieuwe versie van configuratiebestand /etc/weewx/import/wu-example.conf 
wordt geïnstalleerd ...
Nieuwe versie van configuratiebestand 
/etc/weewx/import/cumulus-example.conf wordt geïnstalleerd ...
Nieuwe versie van configuratiebestand /etc/weewx/import/csv-example.conf 
wordt geïnstalleerd ...
dpkg: fout: --compare-versions verwacht drie argumenten:   


So it's still running 3.8.2. Where is the error here?

Regards,

Eelco


Op woensdag 6 februari 2019 14:40:34 UTC+1 schreef Thomas Keffer:
>
> Well, that was a record short release. We found a serious bug in v3.9.0 
> that could break skins that do not have fonts defined, such as cmon.
>
> So, we are releasing v3.9.1, found in the usual place 
> .
>
> -tk
>

-- 
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: wee_database --update fail

[Eelco F]

I once edited my database, when my rainmeter didn't function as it should. 
For testing, after cleaining it, I poored some water through it, an ended 
up with exceptionally high rain rates in my database...;) I deleted those 
manually afterwards. This might be  the cause. Furthermore, I once had a 
corrupted database, which I had to repair manually. The database goes back 
to 2014. But it appears to be solved, anyway.

As for the wind parameters. OK, I understand there is no "average" 
direction for max windSpeed, although there is such a thing as 
$current.windDir which is an average windDir over the archive interval, 
created by either hardware or software. Hardware in my case (Davis Vanatge 
Vue). I understand the wind data are a difficult matter, depending on 
definitions and hardware properties.

For now, I'll just leave my webpage as it is, reporting alltime high wind, 
by $alltime.wind.max and $alltime.wind.gustdir.

E

-- 
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: wee_database --update fail

[Eelco F]

Gary,

My station is an Vantage Vue with data logger. After the error I put back a 
backup of the the old database, that was created in the night, and weex 
updated it from the datalogger. So that's not a problem.
I did a dry run now, and it shows the same error.
I tried your solution, and it ran whithout issues. Thanx.


So, after this I now have archive_day_wind, archive_day_windSpeed, 
archive_day_windGust, archive_day_windGustDir, archive day_windDir.

In my overview I used to have a line: $alltime.wind.max 
($alltime.wind.gustdir) at $alltime.wind.maxtime.
This showed the alltime maxwind, the direction and the time.
 Now i would like to show alltime max windgust, maxwindgust dir, 
maxwindgusttime and maxwindSpeed, maxwindSpeed dir, maxwindSpeed time. But 
I don know how to get maxwindGust dir and max windSpeed dir.




Op vrijdag 17 maart 2017 10:27:51 UTC+1 schreef gjr80:
>
> Hi,
>
> Put simply --update will weight a number of daily summary fields according 
> to the interval used in the archive. Judging by the error trace provided 
> you appear to have daily summary records for days that have no records in 
> your archive. I think you have 2 options:
>
> - The quick fix is to run wee_database with --drop-daily followed by 
> --rebuild-daily to drop your daily summaries and then rebuild them from 
> your archive. The rebuild should fix the situation I indicated above and 
> you will not need to --update, the rebuild takes care of that. This 
> approach will result in some loss of granularity of the daily summary data 
> (eg max and min times) but otherwise it's non-destructive.
>
> - The alternative is to wait for Tom, he may have further insight, or he 
> may say do a --drop-daily followed by a --rebuild! Of course if your 
> station is offline you may be missing data if your station does not have 
> memory.
>
> I would also be interested to know if you did a wee_database --update 
> --dry-run beforehand, would like to know if the dry run missed the error.
>
> Gary
>
>

-- 
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] wee_database --update fail

[Eelco F]

After upgrading to 3.7.0 I tried to update the database becuase of the 
max_wind issues.

Running wee_database --update results in.

Using configuration file /etc/weewx/weewx.conf
Using database binding 'wx_binding', which is bound to database 
'archive_sqlite'
The update process does not affect archive data, but does alter the 
database.
Continue (y/n)? y
Preparing Interval Weighting Fix...
Daily summary tables are at version 1.0
Calculating interval weights...
Traceback (most recent call last):
  File "/usr/bin/wee_database", line 793, in 
main()
  File "/usr/bin/wee_database", line 165, in main
update(config_dict, db_binding, options)
  File "/usr/bin/wee_database", line 552, in update
weight_obj.run()
  File "/usr/share/weewx/weecfg/database.py", line 443, in run
self.do_fix(_next_day_to_patch_ts)
  File "/usr/share/weewx/weecfg/database.py", line 501, in do_fix
_weight = self.get_interval(_day_span) * 60
  File "/usr/share/weewx/weecfg/database.py", line 596, in get_interval
return _row[0]
TypeError: 'NoneType' object has no attribute '__getitem__'

restarting weewx doesn't work becuase the database update isn't finished.

could you help me out?

-- 
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: My reports do not run

[Eelco F]

Are you sure there is no error in the logs? I usually have clues in the 
logs if there were errors.
What system are ou running on?

If you installed via .deb or apt-get take a look here: 

https://groups.google.com/forum/#!topic/weewx-user/ydhQftFQ2Ys

-- 
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: cannot find "alltime"

[Eelco F]

Ah, very well. We're all human aren't we? ;)

Keep up the good work Tom, I really apreciate weewx and all your effort 
very much.

Op woensdag 15 maart 2017 16:05:45 UTC+1 schreef Tom Keffer:
>
> Why isn't the stats file included in the deb package? It's not an 
>> extension is it?
>>
>
> ​An oversight. It will be included in v3.7.1.
>
> -tk​
>

-- 
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: cannot find "alltime"

[Eelco F]

Oops, it should read: search_list_extensions = user.stats.MyStats, Iĺl try 
again

-- 
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: cannot find "alltime"

[Eelco F]

Allright, I did check  /usr/share/weewx/user but that isn't bin/user right? 
So I wasn't sure to where he was referring to. I know things are different 
for setup.py en deb install.

Originally there was no stats.py in /usr/share/weewx/user, after the 
upgrade to 3.7.0. So i copied it manually now from github to this directory 
as instructed.
my skin.conf now has this line:  search_list_extensions = user.stats.Mystats



I'm still having issues:
Mar 15 15:10:15 kwsweerstation weewx[13955]: reportengine: Caught 
unrecoverable exception in generator weewx.cheetahgenerator.CheetahGenerator
Mar 15 15:10:15 kwsweerstation weewx[13955]:   Module 
'user.stats' has no attribute 'Mystats' when searching for 
'user.stats.Mystats'
Mar 15 15:10:15 kwsweerstation weewx[13955]:   Traceback (most 
recent call last):
Mar 15 15:10:15 kwsweerstation weewx[13955]: File 
"/usr/share/weewx/weewx/reportengine.py", line 239, in run
Mar 15 15:10:15 kwsweerstation weewx[13955]:   obj.start()
Mar 15 15:10:15 kwsweerstation weewx[13955]: File 
"/usr/share/weewx/weewx/reportengine.py", line 273, in start
Mar 15 15:10:15 kwsweerstation weewx[13955]:   self.run()
Mar 15 15:10:15 kwsweerstation weewx[13955]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 154, in run
Mar 15 15:10:15 kwsweerstation weewx[13955]:  
 self.initExtensions(gen_dict[section_name])
Mar 15 15:10:15 kwsweerstation weewx[13955]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 196, in initExtensions
Mar 15 15:10:15 kwsweerstation weewx[13955]:   class_ = 
weeutil.weeutil._get_object(x)
Mar 15 15:10:15 kwsweerstation weewx[13955]: File 
"/usr/share/weewx/weeutil/weeutil.py", line 1140, in _get_object
Mar 15 15:10:15 kwsweerstation weewx[13955]:   raise 
AttributeError("Module '%s' has no attribute '%s' when searching for '%s'" 
% (mod.__name__, part, module_class))
Mar 15 15:10:15 kwsweerstation weewx[13955]:   AttributeError: 
Module 'user.stats' has no attribute 'Mystats' when searching for 
'user.stats.Mystats'
Mar 15 15:10:15 kwsweerstation weewx[13955]:   Generator 
terminated


-- 
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: cannot find "alltime"

[Eelco F]

Dear Gary,

I think this is the issue, thank you for pointing that out. Shouldn't the 
installer just take care of this?

However I'm afraid I don quite follow your references to the directories. 
There is no such directory as /bin/user on my systems. So where exactly 
should the stats.py reside on a ubuntu/debian system?

Eelco



Op woensdag 15 maart 2017 11:10:28 UTC+1 schreef gjr80:
>
> Ok, as far as I can tell the examples directory is not in the deb package 
> so anyone using apt-get or dpkg will not have an examples directory. You 
> can download the stats.py file directly from GitHub by typing the 
> following from the command line on your weeWX machine:
>
> $ wget https://
> raw.githubusercontent.com/weewx/weewx/master/examples/stats.py
>
> That will download stats.py to the current directory, you can then copy 
> it to the bin/user directory.
>
> Gary
>
> On Wednesday, 15 March 2017 19:54:00 UTC+10, gjr80 wrote:
>>
>> Hi Eelco and VM-83,
>>
>> I thought this had been answered but apparently not. WeeWX 3.7.0 saw the 
>> examples moved out of the bin directory and the xsearch.py SLE example 
>> was renamed stats.py. Similarly, the MyXSearch SLE was renamed MyStats 
>> (the MyXSearch SLE, now MyStats,provides the $alltime and $seven_day 
>> tags). Admittedly it was the 28th item in the change log included in the 
>> release 
>> post 
>> <https://groups.google.com/d/msg/weewx-user/RTLEf-8pZC8/_i7HmXsUAwAJ>:
>>
>> Moved examples out of bin directory.  Eliminated experimental directory.
>> Reinforce the use of user directory, eliminate use of examples directory.
>> Renamed xsearch.py to stats.py.
>>
>> To get things working again you will need to copy the file stats.py from 
>> the examples directory to your bin/user directory (the examples 
>> directory is now in /home/weewx for a setup.py install, not so sure 
>> about rpm or deb packages though). Also, in skin.conf the line:
>>
>> search_list_extensions = examples.xsearch.MyXSearch
>>
>> will need to be changed to:
>>
>> search_list_extensions = user.stats.MyStats
>>
>> This should restore the $alltime and $seven_day tags.
>>
>> Gary
>>
>> On Wednesday, 15 March 2017 19:17:52 UTC+10, Eelco F wrote:
>>>
>>> I'm having the same issue, as I posted in a separate post. Sorry, I 
>>> overlooked this thread.
>>>
>>> I have weewx running on ubuntu 16.04.2. I upgraded from 3.6.2 to 3.7.0. 
>>> I must say I always performed a manual update until 3.6.2. Now I added the 
>>> repository and upgraded by apt-get.
>>>
>>> after that, I got this:
>>>
>>> Mar 15 09:50:17 weerstation weewx[1446]: reportengine: Caught 
>>> unrecoverable exception in generator weewx.cheetahgenerator.CheetahGenerator
>>> Mar 15 09:50:17 weerstation weewx[1446]:   No module named 
>>> examples.xsearch
>>> Mar 15 09:50:17 weerstation weewx[1446]:   Traceback (most 
>>> recent call last):
>>> Mar 15 09:50:17 weerstation weewx[1446]: File 
>>> "/usr/share/weewx/weewx/reportengine.py", line 239, in run
>>> Mar 15 09:50:17 weerstation weewx[1446]:   obj.start()
>>> Mar 15 09:50:17 weerstation weewx[1446]: File 
>>> "/usr/share/weewx/weewx/reportengine.py", line 273, in start
>>> Mar 15 09:50:17 weerstation weewx[1446]:   self.run()
>>> Mar 15 09:50:17 weerstation weewx[1446]: File 
>>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 154, in run
>>> Mar 15 09:50:17 weerstation weewx[1446]:  
>>>  self.initExtensions(gen_dict[section_name])
>>> Mar 15 09:50:17 weerstation weewx[1446]: File 
>>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 196, in initExtensions
>>> Mar 15 09:50:17 weerstation weewx[1446]:   class_ = 
>>> weeutil.weeutil._get_object(x)
>>> Mar 15 09:50:17 weerstation weewx[1446]: File 
>>> "/usr/share/weewx/weeutil/weeutil.py", line 1132, in _get_object
>>> Mar 15 09:50:17 weerstation weewx[1446]:   mod = 
>>> __import__(module)
>>> Mar 15 09:50:17 weerstation weewx[1446]:   ImportError: No 
>>> module named examples.xsearch
>>> Mar 15 09:50:17 weerstation weewx[1446]:   Generator 
>>> terminated
>>> Mar 15 09:50:17 weerstation weewx[1446]: imagegenerator: Generated 11 
>>> images for StandardReport in 0.13 seconds
>>&g

Re: [weewx-user] Re: cannot find "alltime"

[Eelco F]

On a second system, I'm getting the same error after the update. After that 
i manually re-installed 3.7.0 by dpkg -i. The issue still persists.

-- 
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: cannot find "alltime"

[Eelco F]

I'm having the same issue, as I posted in a separate post. Sorry, I 
overlooked this thread.

I have weewx running on ubuntu 16.04.2. I upgraded from 3.6.2 to 3.7.0. I 
must say I always performed a manual update until 3.6.2. Now I added the 
repository and upgraded by apt-get.

after that, I got this:

Mar 15 09:50:17 weerstation weewx[1446]: reportengine: Caught unrecoverable 
exception in generator weewx.cheetahgenerator.CheetahGenerator
Mar 15 09:50:17 weerstation weewx[1446]:   No module named 
examples.xsearch
Mar 15 09:50:17 weerstation weewx[1446]:   Traceback (most 
recent call last):
Mar 15 09:50:17 weerstation weewx[1446]: File 
"/usr/share/weewx/weewx/reportengine.py", line 239, in run
Mar 15 09:50:17 weerstation weewx[1446]:   obj.start()
Mar 15 09:50:17 weerstation weewx[1446]: File 
"/usr/share/weewx/weewx/reportengine.py", line 273, in start
Mar 15 09:50:17 weerstation weewx[1446]:   self.run()
Mar 15 09:50:17 weerstation weewx[1446]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 154, in run
Mar 15 09:50:17 weerstation weewx[1446]:  
 self.initExtensions(gen_dict[section_name])
Mar 15 09:50:17 weerstation weewx[1446]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 196, in initExtensions
Mar 15 09:50:17 weerstation weewx[1446]:   class_ = 
weeutil.weeutil._get_object(x)
Mar 15 09:50:17 weerstation weewx[1446]: File 
"/usr/share/weewx/weeutil/weeutil.py", line 1132, in _get_object
Mar 15 09:50:17 weerstation weewx[1446]:   mod = 
__import__(module)
Mar 15 09:50:17 weerstation weewx[1446]:   ImportError: No 
module named examples.xsearch
Mar 15 09:50:17 weerstation weewx[1446]:   Generator terminated
Mar 15 09:50:17 weerstation weewx[1446]: imagegenerator: Generated 11 
images for StandardReport in 0.13 seconds


In my skin .conf there is this reference:
search_list_extensions = examples.xsearch.MyXSearch
I also tried to comment this out, it breaks things even further, as was 
said by TS.




Op zondag 12 maart 2017 11:50:47 UTC+1 schreef Erwin Heger:
>
> It won't solve itself by posting  several times ... 
>
> First answer the questions of matthew, afterwards we know a bit more and 
> can give better advise. 
>
> Erwin 
>
> > Am 12.03.2017 um 11:40 schrieb VM_83  >: 
> > 
> > First i made an update from V.3.6.2 to v.3.7.0 
> > 
> the skin cannot find the 'alltime' search list extension.  cannot say how 
> to fix it without knowing more about your configuration. 
>
> how did you do the upgrade?  what version of weewx were you running 
> before? 
>
> what's in the skin.conf for sofaskin? 
>
> what's in your weewx configuration file? 
>

-- 
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: error after update to 3.7.0

[Eelco F]

There is this reference in my skin.conf:

search_list_extensions = examples.xsearch.MyXSearch

if I comment this out, I even get some more errors:


cheetahgenerator: Generate failed with exception ''
Mar 15 10:00:17 weerstation weewx[1446]: cheetahgenerator:  Ignoring 
template /etc/weewx/skins/Aangepast/trend.html.tmpl
Mar 15 10:00:17 weerstation weewx[1446]: cheetahgenerator:  Reason: 
cannot find 'alltime'
Mar 15 10:00:17 weerstation weewx[1446]:   Traceback (most recent call 
last):
Mar 15 10:00:17 weerstation weewx[1446]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 329, in generate
Mar 15 10:00:17 weerstation weewx[1446]:   print >> _file, 
compiled_template
Mar 15 10:00:17 weerstation weewx[1446]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in 
__str__
Mar 15 10:00:17 weerstation weewx[1446]:   rc = getattr(self, 
mainMethName)()
Mar 15 10:00:17 weerstation weewx[1446]: File 
"_etc_weewx_skins_Aangepast_trend_html_tmpl.py", line 530, in respond
Mar 15 10:00:17 weerstation weewx[1446]:   NotFound: cannot find 
'alltime'
Mar 15 10:00:17 weerstation weewx[1446]: cheetahgenerator: Generate failed 
with exception ''
Mar 15 10:00:17 weerstation weewx[1446]: cheetahgenerator:  Ignoring 
template /etc/weewx/skins/Aangepast/smartphone/temp_outside.html.tmpl
Mar 15 10:00:17 weerstation weewx[1446]: cheetahgenerator:  Reason: 
cannot find 'seven_day'
Mar 15 10:00:17 weerstation weewx[1446]:   Traceback (most recent call 
last):
Mar 15 10:00:17 weerstation weewx[1446]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 329, in generate
Mar 15 10:00:17 weerstation weewx[1446]:   print >> _file, 
compiled_template
Mar 15 10:00:17 weerstation weewx[1446]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in 
__str__
Mar 15 10:00:17 weerstation weewx[1446]:   rc = getattr(self, 
mainMethName)()
Mar 15 10:00:17 weerstation weewx[1446]: File 
"_etc_weewx_skins_Aangepast_smartphone_temp_outside_html_tmpl.py", line 
125, in respond
Mar 15 10:00:17 weerstation weewx[1446]:   NotFound: cannot find 
'seven_day'
Mar 15 10:00:18 weerstation weewx[1446]: cheetahgenerator: Generate failed 
with exception ''
Mar 15 10:00:18 weerstation weewx[1446]: cheetahgenerator:  Ignoring 
template /etc/weewx/skins/Aangepast/week.html.tmpl
Mar 15 10:00:18 weerstation weewx[1446]: cheetahgenerator:  Reason: 
cannot find 'seven_day'
Mar 15 10:00:18 weerstation weewx[1446]:   Traceback (most recent call 
last):
Mar 15 10:00:18 weerstation weewx[1446]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 329, in generate
Mar 15 10:00:18 weerstation weewx[1446]:   print >> _file, 
compiled_template
Mar 15 10:00:18 weerstation weewx[1446]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in 
__str__
Mar 15 10:00:18 weerstation weewx[1446]:   rc = getattr(self, 
mainMethName)()
Mar 15 10:00:18 weerstation weewx[1446]: File 
"_etc_weewx_skins_Aangepast_week_html_tmpl.py", line 125, in respond
Mar 15 10:00:18 weerstation weewx[1446]:   NotFound: cannot find 
'seven_day'
Mar 15 10:00:18 weerstation weewx[1446]: cheetahgenerator: Generate failed 
with exception ''
Mar 15 10:00:18 weerstation weewx[1446]: cheetahgenerator:  Ignoring 
template /etc/weewx/skins/Aangepast/smartphone/wind.html.tmpl
Mar 15 10:00:18 weerstation weewx[1446]: cheetahgenerator:  Reason: 
cannot find 'seven_day'
Mar 15 10:00:18 weerstation weewx[1446]:   Traceback (most recent call 
last):
Mar 15 10:00:18 weerstation weewx[1446]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 329, in generate
Mar 15 10:00:18 weerstation weewx[1446]:   print >> _file, 
compiled_template
Mar 15 10:00:18 weerstation weewx[1446]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in 
__str__
Mar 15 10:00:18 weerstation weewx[1446]:   rc = getattr(self, 
mainMethName)()
Mar 15 10:00:18 weerstation weewx[1446]: File 
"_etc_weewx_skins_Aangepast_smartphone_wind_html_tmpl.py", line 127, in 
respond
Mar 15 10:00:18 weerstation weewx[1446]:   NotFound: cannot find 
'seven_day'

-- 
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: Current Windspeed in Beaufort ? Bft?

[Eelco F]

I do have a question on this.

I noticed that as of weewx 3.2 there is a beaufort calculation in 
Stdwxcalculate, right?

Now how do I get beaufort values in my reports? Until now I used javascript 
too, but it should be possible directly from weewx?

Ef

Op zondag 16 maart 2014 09:08:27 UTC+1 schreef Ronald Wildner:
>
> I am wondering if there is any hint to display current WindSpeed in 
> Beaufort !
> I used google and the search -function, but could not find anything 
> adequate ;-)
>

-- 
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: windgust period

[Eelco F]

Thnx Tom, for clarifying that.

Op zondag 5 februari 2017 20:45:24 UTC+1 schreef Tom Keffer:
>
> Depends on the hardware and the setting of record_generation.
>
> If record_generation=hardware, and the hardware emits it, then that value 
> is used.
>
> Otherwise, weewx calculates it as the average wind speed over the archive 
> interval.
>
> -tk
>
> On Sun, Feb 5, 2017 at 11:16 AM, Eelco F <valken...@gmail.com 
> > wrote:
>
>> In addition to this, how is the value of $current.windspeed defined? Is 
>> it a 10 minute average, as defined in determining beaufort windforce? Or is 
>> it just the latest measurement at the moment when creating the html pages.
>> If so, should I use $span(time_delta=600).windSpeed.avg.formatted to 
>> determine the 10 min average.
>> I'm afraid still a bit confused on how weewx works with the continuous 
>> variation of windspeeds.
>>
>> Op zaterdag 4 februari 2017 11:40:45 UTC+1 schreef Eelco F:
>>
>>> Hi Gary,
>>>
>>> Great, thanks a lot, that did the trick. I must have overlooked it in 
>>> the userguide ;)
>>>
>>> Eelco
>>>
>>> Op donderdag 2 februari 2017 12:11:54 UTC+1 schreef gjr80:
>>>>
>>>> Hi Eelco,
>>>>
>>>> Try tag $span <http://weewx.com/docs/customizing.htm#Tag_$span> with 
>>>> $hour_delta=1 or $time_delta=3600.
>>>>
>>>> Gary
>>>>
>>>> On Thursday, 2 February 2017 21:06:08 UTC+10, Eelco F wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> I'm struggling a bit with the windgust parameter. I would like to show 
>>>>> the maximum windgust in the past 60 minutes. However, it seems that when 
>>>>> I 
>>>>> use $hour.windGust.max.formatted I get the max value in the current clock 
>>>>> hour.
>>>>> So, assume it's 15.20 now, I get the value from the past 20 minutes. 
>>>>> If it's 15.40 I get the maxvalue in the past 40 minutes. Is that right?
>>>>>
>>>>> Is there an option to show the max.windgust in the past 60 minutes? So 
>>>>> if it's 15.20, weewx will look in the database from 14.20?
>>>>>
>>>>> thanks and regards,
>>>>>
>>>>> Eelco
>>>>>
>>>> -- 
>> 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] Re: windgust period

[Eelco F]

In addition to this, how is the value of $current.windspeed defined? Is it 
a 10 minute average, as defined in determining beaufort windforce? Or is it 
just the latest measurement at the moment when creating the html pages.
If so, should I use $span(time_delta=600).windSpeed.avg.formatted to 
determine the 10 min average.
I'm afraid still a bit confused on how weewx works with the continuous 
variation of windspeeds.

Op zaterdag 4 februari 2017 11:40:45 UTC+1 schreef Eelco F:
>
> Hi Gary,
>
> Great, thanks a lot, that did the trick. I must have overlooked it in the 
> userguide ;)
>
> Eelco
>
> Op donderdag 2 februari 2017 12:11:54 UTC+1 schreef gjr80:
>>
>> Hi Eelco,
>>
>> Try tag $span <http://weewx.com/docs/customizing.htm#Tag_$span> with 
>> $hour_delta=1 or $time_delta=3600.
>>
>> Gary
>>
>> On Thursday, 2 February 2017 21:06:08 UTC+10, Eelco F wrote:
>>>
>>> Hi,
>>>
>>> I'm struggling a bit with the windgust parameter. I would like to show 
>>> the maximum windgust in the past 60 minutes. However, it seems that when I 
>>> use $hour.windGust.max.formatted I get the max value in the current clock 
>>> hour.
>>> So, assume it's 15.20 now, I get the value from the past 20 minutes. If 
>>> it's 15.40 I get the maxvalue in the past 40 minutes. Is that right?
>>>
>>> Is there an option to show the max.windgust in the past 60 minutes? So 
>>> if it's 15.20, weewx will look in the database from 14.20?
>>>
>>> thanks and regards,
>>>
>>> Eelco
>>>
>>

-- 
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: windgust period

[Eelco F]

Hi Gary,

Great, thanks a lot, that did the trick. I must have overlooked it in the 
userguide ;)

Eelco

Op donderdag 2 februari 2017 12:11:54 UTC+1 schreef gjr80:
>
> Hi Eelco,
>
> Try tag $span <http://weewx.com/docs/customizing.htm#Tag_$span> with 
> $hour_delta=1 or $time_delta=3600.
>
> Gary
>
> On Thursday, 2 February 2017 21:06:08 UTC+10, Eelco F wrote:
>>
>> Hi,
>>
>> I'm struggling a bit with the windgust parameter. I would like to show 
>> the maximum windgust in the past 60 minutes. However, it seems that when I 
>> use $hour.windGust.max.formatted I get the max value in the current clock 
>> hour.
>> So, assume it's 15.20 now, I get the value from the past 20 minutes. If 
>> it's 15.40 I get the maxvalue in the past 40 minutes. Is that right?
>>
>> Is there an option to show the max.windgust in the past 60 minutes? So if 
>> it's 15.20, weewx will look in the database from 14.20?
>>
>> thanks and regards,
>>
>> Eelco
>>
>

-- 
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] windgust period

[Eelco F]

Hi,

I'm struggling a bit with the windgust parameter. I would like to show the 
maximum windgust in the past 60 minutes. However, it seems that when I use 
$hour.windGust.max.formatted I get the max value in the current clock hour.
So, assume it's 15.20 now, I get the value from the past 20 minutes. If 
it's 15.40 I get the maxvalue in the past 40 minutes. Is that right?

Is there an option to show the max.windgust in the past 60 minutes? So if 
it's 15.20, weewx will look in the database from 14.20?

thanks and regards,

Eelco

-- 
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: ultimeter setup troubles

[Eelco F]

I edited ultimeter.py

When restarting weewx, in the logs I find:

engine: Clock error is -60.29 seconds (positive is fast)
Jan 27 12:29:30 weatherstation weewx[13329]: engine: Starting main packet 
loop.

So I guess it reads the clock of the ultimeter 2100 now, which was a minute 
behind indeed. but itdoesn't seem to correct the time of the ultimeter 2100.

According to the manual of the ultimeter 2100, it should be possible to set 
time and date in modem mode.

MODEM MODE
In Modem Mode, the serial port is kept in a receive mode with no
data output. It will accept commands to send a Complete Record,
set time and date, set barometer correction, set wind direction
correction, set temperature and humidity offsets, and reset all long
term memory.

And from the website:

Input of a “greater-than” sign will cause the *ULTIMETER* 100/800/2000/2100 
to enter MODEM MODE.  A command consists of a “greater-than” sign followed 
by a capital letter (and then, in some cases, followed by numeric digits – 
see Command Syntax below).

Note:  this mode is not available on pre-2004 *ULTIMETER* 
50/100/500/700/800 (no data input capability).

The command header is >n where n=A-X.  The header is immediately followed 
by a number from zero to eight digits (all decimal numbers except barometer 
correction value), and ended by a CARRIAGE RETURN.

The following commands can be sent to the keyboard via the serial port:

COMMAND SYNTAX 

   - >A   Set Date and Time (decimal digits  = day of year, 
   
    = minute of day; Jan 1 = , Midnight = ) 

But when I see yor code, you figured this out long ago.

I'll just let it running and see if issues come up.

Eelco



Op donderdag 26 januari 2017 21:30:40 UTC+1 schreef Eelco F:
>
> Dear Matthew,
>
> Thank you for clearing this out. I'll just give it a try.
>
> Eelco
>
> Op maandag 23 januari 2017 23:08:19 UTC+1 schreef mwall:
>>
>> On Monday, January 23, 2017 at 4:56:56 PM UTC-5, Eelco F wrote:
>>>
>>> I'm afraid I don't understand your point completely. Are you saying that 
>>> the driver you posted keeps the time of the ultimeter up to date, and the 
>>> latest driver from Matthew doesn't?
>>>
>>
>> eelco,
>>
>> if you look at ultimeter.py, you will see two disabled functions:
>>
>> DISABLED_getTime
>>
>> DISABLED_setTime
>>
>> when the DISABLED_ is removed, the driver should keep the ultimeter time 
>> in sync with the computer time.
>>
>> we added the DISABLED_ some time ago because there were issues switching 
>> between logger mode and modem mode on steve's ultimeter.
>>
>> you could try it with your hardware - remove DISABLED_, then restart 
>> weewx.  watch the log over a day or two to see if weewx keeps the ultimeter 
>> clock in sync with the computer clock.
>>
>> m
>>
>

-- 
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: ultimeter setup troubles

[Eelco F]

Dear Matthew,

Thank you for clearing this out. I'll just give it a try.

Eelco

Op maandag 23 januari 2017 23:08:19 UTC+1 schreef mwall:
>
> On Monday, January 23, 2017 at 4:56:56 PM UTC-5, Eelco F wrote:
>>
>> I'm afraid I don't understand your point completely. Are you saying that 
>> the driver you posted keeps the time of the ultimeter up to date, and the 
>> latest driver from Matthew doesn't?
>>
>
> eelco,
>
> if you look at ultimeter.py, you will see two disabled functions:
>
> DISABLED_getTime
>
> DISABLED_setTime
>
> when the DISABLED_ is removed, the driver should keep the ultimeter time 
> in sync with the computer time.
>
> we added the DISABLED_ some time ago because there were issues switching 
> between logger mode and modem mode on steve's ultimeter.
>
> you could try it with your hardware - remove DISABLED_, then restart 
> weewx.  watch the log over a day or two to see if weewx keeps the ultimeter 
> clock in sync with the computer clock.
>
> m
>

-- 
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: ultimeter setup troubles

[Eelco F]

Thank you Steve,

I'm afraid I don't understand your point completely. Are you saying that 
the driver you posted keeps the time of the ultimeter up to date, and the 
latest driver from Matthew doesn't?

In the logs I see a mentioning of "station does not support time reading" 
or somesort. Has this anything to do with your comment?

Coud you please be a bit more specific on this?

Thanks a  lot,

E
Op donderdag 19 januari 2017 13:39:18 UTC+1 schreef Steve2Q:
>
> Eelco...glad to hear you have it working now. One thing to watch is the 
> time on the 2100 console itself. It should stay accurate  and if it doesn't 
> try the earlier driver version I posted 
>
> Steve 
>

-- 
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: ultimeter setup troubles

[Eelco F]

Ok, I did a rewiring of a new DB9 plug, according to the scheme on the site 
of peetbros. Now it works! So it was a wrong pinout on the DB9 plug.
A bit strange, since it came straight from the importer of peetbros 
equipment in our country. Maybe just a monday morning example ;)
Thanks for everybodys comments on this.

E

>
> So to put it all together, The time stamps are coming from the script 
> itself I assume, as they show up when the station isn't even connected. 
> When disconnecting the display from my computer, some buffer seems to be 
> dumped or something.
> There may some wiring problem? should I follow the DB9 to computer scheme? 
> (sounds logical).
>
>
> Op zaterdag 14 januari 2017 15:54:36 UTC+1 schreef mwall:
>>
>> just for fun, try ultimeter-0.17rc1.py
>>
>> it has write timeouts, so if the driver is unable to write (but able to 
>> read) this should be reflected in the log
>>
>>
>>

-- 
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: ultimeter setup troubles

[Eelco F]

Matthew,

Thank you for your effort! It's still kinda weird though, and I'm still 
stuck.


As for the wiring:

First I checked the modular cable with a network tester I have. All 6 pins 
are connected (but in reverse order on the other end, as is the color 
scheme in the RJ25 connector.)

I looked inside the modulair to db9 converter. Inside only three wires are 
connected, to pin 2, 3 and 5.

I had a look at the table 
here: http://www.peetbros.com/shop/custom.aspx?recid=6

It seems my pinout follows the DB-9 to TNC column. I don't quite understand 
what is meant by the difference between DB-9 to computer and DB9 to TNC 
colums, to be honest. Input and output are reversed, but why is it 
different for a terminal node controller?

Peet Bros seems to sell the same  item for both purposes: 
 http://www.peetbros.com/shop/item.aspx?itemid=64



However I connected everything again, and ran your version 0.17 directly.

On screen no output is shown, and in the logs only:   ultimeter: open 
serial port /dev/ttyS0 as before. No mentioning of write 
timeouts.


Then I pulled the modular cable out of the DB9 plug, while the python 
script was still running and to my surprise this showed up:

1484485968.77 6F 6F F6 F6 F6 F6 F6 F6 F6 F6 B6 56 F6 F6 F6 F6 F6 56 2B 2B 
2B FB DB 6B CB 2B 2B 2B 2B 2B 2B 2B 2B FB FB FB FB FB FB FB EB FB FB FB FB 
FB FB FB FB 6F 6F F6 F6 F6 F6 F6 F6 F6 F6 B6 56 F6 F6 F6 F6 F6 56 2B 2B 2B 
FB DB 6B CB 2B 2B 2B 2B 2B 2B 2B 2B FB FB FB FB FB FB FB EB FB FB FB FB FB 
FB FB FB 6F 6F F6 F6 F6 F6 F6 F6 F6 F6 B6 56 F6 F6 F6 F6 F6 56 2B 2B 2B FB 
DB 6B CB 2B 2B 2B 2B 2B 2B 2B 2B FB FB FB FB FB FB FB EB FB FB FB FB FB FB 
FB FB 6F 6F F6 F6 F6 F6 F6 F6 F6 F6 B6 56 F6 F6 F6 F6 F6 56 2B 2B 2B FB DB 
6B CB 2B 2B 2B 2B 2B 2B 2B 2B FB FB FB FB FB FB FB EB FB FB FB FB FB FB FB 
FB 6F 6F F6 F6 F6 F6 F6 F6 F6 F6 B6 56 F6 F6 F6 F6 F6 56 2B 2B 2B FB DB 6B 
CB 2B 2B 2B 2B 2B 2B 2B 2B FB FB FB FB FB FB FB EB FB FB FB FB FB FB FB FB 
6F 6F F6 F6 F6 F6 F6 F6 F6 F6 B6 56 F6 F6 F6 F6 F6 56 2B 2B 2B FB DB 6B CB 
2B 2B 2B 2B 2B 2B 2B 2B FB FB FB FB FB FB FB EB FB FB FB FB FB FB FB FB 6F 
6F F6 F6 F6 F6 F6 F6 F6 F6 B6 56 F6 F6 F6 F6 F6 56 2B 2B 2B FB DB 6B CB 2B 
2B 2B 2B 2B 2B 2B 2B FB FB FB FB FB FB FB EB FB FB FB FB FB FB FB FB 6F 6F 
F6 F6 F6 F6 F6 F6 F6 F6 B6 56 F6 F6 F6 F6 F6 56 2B 2B 2B FB DB 6B CB 2B 2B 
2B 2B 2B 2B 2B 2B FB FB FB FB FB FB FB EB FB FB FB FB FB FB FB FB 6F 6F F6 
F6 F6 F6 F6 F6 F6 F6 B6 56 F6 F6 F6 F6 F6 56 2B 2B 2B FB DB 6B CB 2B 2B 2B 
2B 2B 2B 2B 2B FB FB FB FB FB FB FB EB FB FB FB FB FB FB FB FB 6F 6F F6 F6 
F6 F6 F6 F6 F6 F6 B6 56

this is just a part of it. Afterwards it showed only timestamps again:

1484486084.15 
1484486087.15 
1484486090.15 
1484486093.16 

So to put it all together, The time stamps are coming from the script 
itself I assume, as they show up when the station isn't even connected. 
When disconnecting the display from my computer, some buffer seems to be 
dumped or something.
There may some wiring problem? should I follow the DB9 to computer scheme? 
(sounds logical).


Op zaterdag 14 januari 2017 15:54:36 UTC+1 schreef mwall:
>
> just for fun, try ultimeter-0.17rc1.py
>
> it has write timeouts, so if the driver is unable to write (but able to 
> read) this should be reflected in the log
>
>
>

-- 
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: ultimeter setup troubles

[Eelco F]

 I use a simple mini-itx board, with a regular com1 port, so no converter 
is used.

-- 
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: ultimeter setup troubles

[Eelco F]

Update:

Just running  PYTHONPATH=/usr/share/weewx python 
/usr/share/weewx/weewx/drivers/ultimeter.py  --port/dev/ttyS0

shows in syslog, only: Jan 14 09:49:03 server ultimeter[7532]: ultimeter: 
open serial port /dev/ttyS0   

literally in terminal:
1484383864.62 vV+++�ۛە��u���
1484383867.76 
1484383870.77 
1484383873.77 
1484383876.77 
1484383879.78 
1484383882.78 
1484383885.78 
1484383888.79 
1484383891.79 
1484383894.79 
1484383897.8 
1484383900.8 
1484383903.8 
1484383906.81 
1484383909.81 
1484383912.81 
1484383915.82 
1484383918.82 
1484383921.82 
1484383924.83 
1484383927.83 

These appear epoch time stamps to me. But no data?

-- 
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: ultimeter setup troubles

[Eelco F]

>
> Allright I did what Matthew suggested.
>

Display in modem mode by pressing clear an temperature.

connect via screen /dev/ttyS0 2400  --> it shows no output, I guess this is 
normal in modem mode. 

I typed I,--> no response.


So I put the display in datalogger mode, by pressing clear and the 
windmeter sign

It starts spitting out unreadable garbage in screen.


Then I did:
PYTHONPATH=/usr/share/weewx python 
/usr/share/weewx/weewx/drivers/ultimeter.py --port /dev/ttyS0 --debug

  Usage: ultimeter.py [options] [--help]

  ultimeter.py: error: no such option: --debug


So I did: 
PYTHONPATH=/usr/share/weewx python 
/usr/share/weewx/weewx/drivers/ultimeter.py --help

Usage: ultimeter.py [options] [--help]

Options:
  -h, --help   show this help message and exit
  --versiondisplay driver version
  --port=PORT  serial port to which the station is connected


There is no debug option?

-- 
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: ultimeter setup troubles

[Eelco F]

: The following algorithms 
will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Jan 13 22:23:01 server weewx[3348]: engine: Finished loading service 
weewx.wxservices.StdWXCalculate
Jan 13 22:23:01 server weewx[3348]: engine: Loading service 
weewx.engine.StdArchive
Jan 13 22:23:01 server weewx[3348]: engine: Archive will use data binding 
wx_binding
Jan 13 22:23:01 server weewx[3348]: engine: Record generation will be 
attempted in 'hardware'
Jan 13 22:23:01 server weewx[3348]: engine: Using archive interval of 300 
seconds (specified in weewx configuration)
Jan 13 22:23:01 server weewx[3348]: engine: Use LOOP data in hi/low 
calculations: 1
Jan 13 22:23:01 server weewx[3348]: engine: Using binding 'wx_binding' to 
database 'weewx.sdb'
Jan 13 22:23:01 server weewx[3348]: manager: Starting backfill of daily 
summaries
Jan 13 22:23:01 server weewx[3348]: manager: Daily summaries up to date
Jan 13 22:23:01 server weewx[3348]: engine: Finished loading service 
weewx.engine.StdArchive
Jan 13 22:23:01 server weewx[3348]: engine: Loading service 
weewx.restx.StdStationRegistry
Jan 13 22:23:01 server weewx[3348]: restx: StationRegistry: Registration 
not requested.
Jan 13 22:23:01 server weewx[3348]: engine: Finished loading service 
weewx.restx.StdStationRegistry
Jan 13 22:23:01 server weewx[3348]: engine: Loading service 
weewx.restx.StdWunderground
Jan 13 22:23:01 server weewx[3348]: restx: Wunderground: Posting not 
enabled.
Jan 13 22:23:01 server weewx[3348]: engine: Finished loading service 
weewx.restx.StdWunderground
Jan 13 22:23:01 server weewx[3348]: engine: Loading service 
weewx.restx.StdPWSweather
Jan 13 22:23:01 server weewx[3348]: restx: PWSweather: Posting not enabled.
Jan 13 22:23:01 server weewx[3348]: engine: Finished loading service 
weewx.restx.StdPWSweather
Jan 13 22:23:01 server weewx[3348]: engine: Loading service 
weewx.restx.StdCWOP
Jan 13 22:23:01 server weewx[3348]: restx: CWOP: Posting not enabled.
Jan 13 22:23:01 server weewx[3348]: engine: Finished loading service 
weewx.restx.StdCWOP
Jan 13 22:23:01 server weewx[3348]: engine: Loading service 
weewx.restx.StdWOW
Jan 13 22:23:01 server weewx[3348]: restx: WOW: Posting not enabled.
Jan 13 22:23:01 server weewx[3348]: engine: Finished loading service 
weewx.restx.StdWOW
Jan 13 22:23:01 server weewx[3348]: engine: Loading service 
weewx.restx.StdAWEKAS
Jan 13 22:23:01 server weewx[3348]: restx: AWEKAS: Posting not enabled.
Jan 13 22:23:01 server weewx[3348]: engine: Finished loading service 
weewx.restx.StdAWEKAS
Jan 13 22:23:01 server weewx[3348]: engine: Loading service 
weewx.engine.StdPrint
Jan 13 22:23:01 server weewx[3348]: engine: Finished loading service 
weewx.engine.StdPrint
Jan 13 22:23:01 server weewx[3348]: engine: Loading service 
weewx.engine.StdReport
Jan 13 22:23:01 server weewx[3348]: engine: Finished loading service 
weewx.engine.StdReport
Jan 13 22:23:01 server weewx[3348]: engine: Starting up weewx version 3.6.2
Jan 13 22:23:01 server weewx[3348]: engine: Station does not support 
reading the time
Jan 13 22:23:01 server weewx[3348]: engine: Starting main packet loop.
Jan 13 22:23:01 server weewx[3348]: ultimeter: set station to logger mode

Then it stops.

(I should point out that the anemometer unit is not connected to the 
junction box at the moment, only outside temperature, since the unit is 
installed elsewhere normally. Could this cause any troubles in data output?)


Op vrijdag 13 januari 2017 21:59:21 UTC+1 schreef mwall:
>
> On Friday, January 13, 2017 at 3:38:05 PM UTC-5, Eelco F wrote:
>>
>>
>> I just can get it to work. Am I missing some point here? 
>> Or should I put the ultimeter in modem mode device first so the driver 
>> can set the correct setting?
>>
>
> the drive will attempt to put the ultimeter in modem mode, so you should 
> not have to do that.
>  
>
>> any thoughts are appreciated.
>>
>
> enable additional debug logging like this:
>
> [Ultimeter]
> driver = weewx.drivers.ultimeter
> port = /dev/ttyS0
> debug_serial = 1
>
> then start weewx.  then check the log.
>
> m 
>

-- 
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] ultimeter setup troubles

[Eelco F]

Hi all,

I'm trying to setup my second weatherstation project (first was a Davis). 
This time it's an ultimeter 2100. weewx is 3.6.2-1
I connect the serial interface and put the ultimeter in datalogger mode. I 
ran weewx both directly, and as a service. weewx.conf is almost out of the 
box, except for the setiings for the ultimeter off course.
However, nothing shows up. I set debug =1 in weewx .conf, and the log shows 
the following:

Jan 13 20:51:36 server weewx[6536]: engine: Initializing weewx version 3.6.2
Jan 13 20:51:36 server weewx[6536]: engine: Using Python 2.7.12 (default, 
Nov 19 2016, 06:48:10) #012[GCC 5.4.0 20160609]
Jan 13 20:51:36 server weewx[6536]: engine: Platform 
Linux-4.4.0-57-generic-x86_64-with-Ubuntu-16.04-xenial
Jan 13 20:51:36 server weewx[6536]: engine: Using configuration file 
/etc/weewx/weewx.conf
Jan 13 20:51:36 server weewx[6536]: engine: Initializing engine
Jan 13 20:51:36 server weewx[6536]: engine: Loading station type Ultimeter 
(weewx.drivers.ultimeter)
Jan 13 20:51:36 server weewx[6536]: ultimeter: driver version is 0.16
Jan 13 20:51:36 server weewx[6536]: ultimeter: using serial port /dev/ttyS0
Jan 13 20:51:36 server weewx[6536]: ultimeter: open serial port /dev/ttyS0
Jan 13 20:51:36 server weewx[6536]: engine: Loading service 
weewx.engine.StdTimeSynch
Jan 13 20:51:36 server weewx[6536]: engine: Finished loading service 
weewx.engine.StdTimeSynch
Jan 13 20:51:36 server weewx[6536]: engine: Loading service 
weewx.engine.StdConvert
Jan 13 20:51:36 server weewx[6536]: engine: StdConvert target unit is 0x1
Jan 13 20:51:36 server weewx[6536]: engine: Finished loading service 
weewx.engine.StdConvert
Jan 13 20:51:36 server weewx[6536]: engine: Loading service 
weewx.engine.StdCalibrate
Jan 13 20:51:36 server weewx[6536]: engine: Finished loading service 
weewx.engine.StdCalibrate
Jan 13 20:51:36 server weewx[6536]: engine: Loading service 
weewx.engine.StdQC
Jan 13 20:51:36 server weewx[6536]: engine: Finished loading service 
weewx.engine.StdQC
Jan 13 20:51:36 server weewx[6536]: engine: Loading service 
weewx.wxservices.StdWXCalculate
Jan 13 20:51:36 server weewx[6536]: wxcalculate: The following values will 
be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, 
rainRate=prefer_hardware, windrun=prefer_hardware, 
heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
Jan 13 20:51:36 server weewx[6536]: wxcalculate: The following algorithms 
will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Jan 13 20:51:36 server weewx[6536]: engine: Finished loading service 
weewx.wxservices.StdWXCalculate
Jan 13 20:51:36 server weewx[6536]: engine: Loading service 
weewx.engine.StdArchive
Jan 13 20:51:36 server weewx[6536]: engine: Archive will use data binding 
wx_binding
Jan 13 20:51:36 server weewx[6536]: engine: Record generation will be 
attempted in 'hardware'
Jan 13 20:51:36 server weewx[6536]: engine: Using archive interval of 300 
seconds (specified in weewx configuration)
Jan 13 20:51:36 server weewx[6536]: engine: Use LOOP data in hi/low 
calculations: 1
Jan 13 20:51:36 server weewx[6536]: engine: Using binding 'wx_binding' to 
database 'weewx.sdb'
Jan 13 20:51:36 server weewx[6536]: manager: Starting backfill of daily 
summaries
Jan 13 20:51:36 server weewx[6536]: manager: Daily summaries up to date
Jan 13 20:51:36 server weewx[6536]: engine: Finished loading service 
weewx.engine.StdArchive
Jan 13 20:51:36 server weewx[6536]: engine: Loading service 
weewx.restx.StdStationRegistry
Jan 13 20:51:36 server weewx[6536]: restx: StationRegistry: Registration 
not requested.
Jan 13 20:51:36 server weewx[6536]: engine: Finished loading service 
weewx.restx.StdStationRegistry
Jan 13 20:51:36 server weewx[6536]: engine: Loading service 
weewx.restx.StdWunderground
Jan 13 20:51:36 server weewx[6536]: restx: Wunderground: Posting not 
enabled.
Jan 13 20:51:36 server weewx[6536]: engine: Finished loading service 
weewx.restx.StdWunderground
Jan 13 20:51:36 server weewx[6536]: engine: Loading service 
weewx.restx.StdPWSweather
Jan 13 20:51:36 server weewx[6536]: restx: PWSweather: Posting not enabled.
Jan 13 20:51:36 server weewx[6536]: engine: Finished loading service 
weewx.restx.StdPWSweather
Jan 13 20:51:36 server weewx[6536]: engine: Loading service 
weewx.restx.StdCWOP
Jan 13 20:51:36 server weewx[6536]: restx: CWOP: Posting not enabled.
Jan 13 20:51:36 server weewx[6536]: engine: Finished loading service 
weewx.restx.StdCWOP
Jan 13 20:51:36 server weewx[6536]: engine: Loading service 
weewx.restx.StdWOW
Jan 13 20:51:36 server weewx[6536]: restx: WOW: Posting not enabled.
Jan 13 20:51:36 server weewx[6536]: engine: Finished loading service 
weewx.restx.StdWOW
Jan 13 20:51:36 server weewx[6536]: engine: Loading service 
weewx.restx.StdAWEKAS
Jan 

[weewx-user] weewx, raspberry pi and sd cards - the lifetime for card

[Eelco F]

Well, I experienced the same issues running the system on a raspberry pi B. 
Every 3 Months or so, the sd cards just gave up. Corrupted files and file 
system, causing freezes. I had the whole system including swap, raspbian and 
weewx and Apache running on the sd card. No extra disks or sticks.
I ended up doing some calculation: weewx rewrites its database every 5 min, 
that is 12 times/h, 248 times/day, let's say 7500/month.
Apart from that it rewrites html files, images etc. at the same frequency. Also 
the operating system performs writes, in the log for example, and swap.
Adding this all up together, I think an sd card just wears out, after a few 
months. 
I replaced the raspberry by a secondhand HP thin client, for a few bucks at 
eBay. With a regular hdd.
It takes more power of course, but it's a lot faster too. It's running Ubuntu 
server, and is stable until now.

-- 
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.