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
- >Addddmmmm Set Date and Time (decimal digits dddd = day of year,
mmmm = minute of day; Jan 1 = 0000, Midnight = 0000)
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
