Eelco and Matthew..I was away for a few days and did not see the additional
posts. As I made upgrades to Weewx or when a new driver was posted, I tried
them out. The reasons I rolled back to the particular one I am using are 1. The
console time would drift, and 2. Disregding the time issue I
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.
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
On Tuesday, January 24, 2017 at 4:27:54 PM UTC-5, Messy Potamia wrote:
>
> Matt I decided to try 0.17rc1, as downloaded from the link you posted
> above, here's what I got:
> Jan 24 15:20:09 RPI3 systemd[1]: Started LSB: weewx weather system.
> Jan 24 15:20:09 RPI3 weewx[7350]: ultimeter: driver
Matt I decided to try 0.17rc1, as downloaded from the link you posted
above, here's what I got:
Jan 24 15:20:09 RPI3 systemd[1]: Started LSB: weewx weather system.
Jan 24 15:20:09 RPI3 weewx[7350]: ultimeter: driver version is 0.17rc1
Jan 24 15:20:09 RPI3 weewx[7350]: ultimeter: using serial port
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,
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
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.
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
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
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
On Saturday, January 14, 2017 at 3:57:04 AM UTC-5, Eelco F wrote:
>
> I use a simple mini-itx board, with a regular com1 port, so no converter
> is used.
>
you can validate the wiring by sending commands from screen.
try putting the device in modem mode (just hit enter), then put it into
On Saturday, January 14, 2017 at 3:57:04 AM UTC-5, Eelco F wrote:
>
> I use a simple mini-itx board, with a regular com1 port, so no converter
> is used.
>
check your wiring. it looks like rx on the computer is ok, but tx is not.
i could add write timeouts to the ultimeter driver, but that
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
Might be nothing to do with the issue, but...
How are you connecting to the ultimeter?
In my weewx.conf I have: port = /dev/ttyUSB0
because I'm connecting via a usb socket using a pl2303
Are you using a PC or raspberry pi or what?
--
You received this message because you are subscribed to the
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
>
> 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
If you try what Matthew suggests and everything appears ok, may try a
different driver. There were several iterations of the Ultimeter driver,
and I had problems with the last one (it would not keep proper time on my
2100 console). I am not saying this will take care of your problem, as
Allright, thanx for your quick reply. This is what I got:
Jan 13 22:19:50 server weewx[3331]: * Starting weewx weather system weewx
Jan 13 22:19:51 server weewx[3344]: engine: Initializing weewx version 3.6.2
Jan 13 22:19:51 server weewx[3344]: engine: Using Python 2.7.12 (default,
Nov 19
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
20 matches
Mail list logo
