<HTML><HEAD></HEAD>
<BODY dir=ltr>
<DIV dir=ltr>
<DIV style="FONT-FAMILY: 'Arial'; COLOR: #000000; FONT-SIZE: 10pt">
<DIV>Guten Morgen,</DIV>
<DIV>dein Zähler scheint gleich zu sein wie mein Siemens TD-3511.</DIV>
<DIV>Das Hauptproblem wird sein, das diese Zählerart zuerst einmal etwas
empfangen zu müssen.</DIV>
<DIV>Und sowas ist im VZLogger nicht drin.</DIV>
<DIV> </DIV>
<DIV>Gruß Michael</DIV>
<DIV
style="FONT-STYLE: normal; DISPLAY: inline; FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: small; FONT-WEIGHT: normal; TEXT-DECORATION: none">
<DIV style="FONT: 10pt tahoma">
<DIV> </DIV>
<DIV style="BACKGROUND: #f5f5f5">
<DIV style="font-color: black"><B>From:</B> <A title=mr.o@gmx.de
href="mailto:mr.o@gmx.de">Mister O</A> </DIV>
<DIV><B>Sent:</B> Friday, May 18, 2012 1:12 AM</DIV>
<DIV><B>To:</B> <A title=volkszaehler-users@lists.volkszaehler.org
href="mailto:volkszaehler-users@lists.volkszaehler.org">volkszaehler-users@lists.volkszaehler.org</A>
</DIV>
<DIV><B>Subject:</B> [vz-users] vzlogger mit IR-Schreib-Lesekopf an Elster
1440</DIV></DIV></DIV>
<DIV> </DIV></DIV>
<DIV
style="FONT-STYLE: normal; DISPLAY: inline; FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: small; FONT-WEIGHT: normal; TEXT-DECORATION: none">Hallo,
<DIV> </DIV>
<DIV>ich habe einen IR-Schreib-Lesekopf mit der USB-Erweiterung aufgebaut und
kann mit diesem dem Zähler Daten entlocken (sowohl über ein Terminal wie im Wiki
beschrieben als auch durch ein "<A href="http://init.pl"
target=_blank>init.pl</A>"-Tool aus dem KNX-User-Forum (<A
href="http://knx-user-forum.de/225383-post148.html"
target=_blank>http://knx-user-forum.de/225383-post148.html</A>)).</DIV>
<DIV> </DIV>
<DIV>Aber ich bekomme den vzlogger nicht dazu Daten /dev/ttyUSB1 auszulesen.
Meine Konfiguration sieht so aus:</DIV>
<DIV> </DIV>
<DIV>
<DIV>{</DIV>
<DIV>"retry" :
30,
/* how long to sleep between failed requests, in seconds */</DIV>
<DIV>"daemon":
true,
/* run periodically */</DIV>
<DIV>//"foreground" :
true, /* dont run in
background (prevents forking) */</DIV>
<DIV>"verbosity" :
10,
/* between 0 and 15 */</DIV>
<DIV>"log" : "/var/log/vzlogger.log",/* path to logfile, optional */</DIV>
<DIV> </DIV>
<DIV>"local" : {</DIV>
<DIV> "enabled" :
true, /* should we start the local HTTPd for
serving live readings? */</DIV>
<DIV> "port" :
8080, /* the TCP port for
the local HTTPd */</DIV>
<DIV> "index" :
true, /* should we provide a
index listing of available channels if no UUID was requested? */</DIV>
<DIV> "timeout" :
30, /* timeout for long polling
comet requests, 0 disables comet, in seconds */</DIV>
<DIV> "buffer" :
600 /* how long to buffer
readings for the local interface, in seconds */</DIV>
<DIV>},</DIV>
<DIV> </DIV>
<DIV>"meters" : [{</DIV>
<DIV> "enabled" :
true, /* disabled meters will be
ignored */</DIV>
<DIV> "protocol" :
"sml", /* see 'vzlogger -h' for list of available
protocols */</DIV>
<DIV> "device" : "/dev/ttyUSB1",</DIV>
<DIV> "channels": [{</DIV>
<DIV>
"uuid" : "xyz-uuid",</DIV>
<DIV>
"middleware" : "<A href="http://localhost/middleware.php"
target=_blank>http://localhost/middleware.php</A>",</DIV>
<DIV>
"identifier" : "power" /* Wirkleistung (Summe) */</DIV>
<DIV>
}, {</DIV>
<DIV>
"uuid" : "xyz-uuid",</DIV>
<DIV>
"middleware" : "<A href="http://localhost/middleware.php"
target=_blank>http://localhost/middleware.php</A>",</DIV>
<DIV>
"identifier" : "esy-counter-t1", /* Tagesstromverbrauch Tarif 1 */</DIV>
<DIV>
}, {</DIV>
<DIV>
"uuid" : "xyz-uuid",</DIV>
<DIV>
"middleware" : "<A href="http://localhost/middleware.php"
target=_blank>http://localhost/middleware.php</A>",</DIV>
<DIV>
"identifier" : "esy-counter-t2", /* Nachtstromverbrauch Tarif 2 */</DIV>
<DIV>
}, {</DIV>
<DIV>
"uuid" : "xyz-uuid",</DIV>
<DIV>
"middleware" : "<A href="http://localhost/middleware.php"
target=_blank>http://localhost/middleware.php</A>",</DIV>
<DIV>
"identifier" : "counter", /* Wirkleistung Total */</DIV>
<DIV>
}]</DIV>
<DIV> }</DIV></DIV>
<DIV>]}</DIV>
<DIV> </DIV>
<DIV>Wenn ich random als Protokoll einsetze, zeigt meine Middleware im Frontend
auch Daten an, mit sml nicht. </DIV>
<DIV>Im Log ist nur zu erkennen, dass der vzlogger wartet (Aufruf: vzlogger -c
/etc/vzlogger.conf -f -v 20):</DIV>
<DIV> </DIV>
<DIV>
<DIV>[May 18 01:02:36] Start parsing
configuration from /etc/vzlogger.conf</DIV>
<DIV>[May 18 01:02:36][mtr0] New meter initialized (protocol=sml)</DIV>
<DIV>[May 18 01:02:36][ch0] New channel initialized (uuid=...bd7f24
middleware=<A href="http://localhost/middleware.php"
target=_blank>http://localhost/middleware.php</A> id=counter)</DIV>
<DIV>[May 18 01:02:36][ch1] New channel initialized (uuid=...4ddf90
middleware=<A href="http://localhost/middleware.php"
target=_blank>http://localhost/middleware.php</A> id=esy-counter-t2)</DIV>
<DIV>[May 18 01:02:36][ch2] New channel initialized (uuid=...d8cc0a
middleware=<A href="http://localhost/middleware.php"
target=_blank>http://localhost/middleware.php</A> id=esy-counter-t1)</DIV>
<DIV>[May 18 01:02:36][ch3] New channel initialized (uuid=...0bdeef
middleware=<A href="http://localhost/middleware.php"
target=_blank>http://localhost/middleware.php</A> id=power)</DIV>
<DIV>[May 18 01:02:36] Opened logfile
/var/log/vzlogger.log</DIV>
<DIV>[May 18 01:02:36][mtr0] Meter connection established</DIV>
<DIV>[May 18 01:02:36][mtr0] Meter thread started</DIV>
<DIV>[May 18 01:02:36][ch0] Logging thread started</DIV>
<DIV>[May 18 01:02:36][ch1] Logging thread started</DIV>
<DIV>[May 18 01:02:36][ch2] Logging thread started</DIV>
<DIV>[May 18 01:02:36][ch3] Logging thread started</DIV>
<DIV>[May 18 01:02:36][http] Starting local interface HTTPd on port
8080</DIV></DIV>
<DIV> </DIV>
<DIV>Hat jemand eine Idee wie ich vzlogger zum Auslesen der Werte bewegen kann?
</DIV>
<DIV>Muss ich eventuell irgendwo den Port ttyUSB1 konfigurieren (300 Baud,
7E1)?</DIV>
<DIV> </DIV>
<DIV>Viele Grüße</DIV>
<DIV>Axel</DIV>
<DIV> </DIV></DIV></DIV></DIV></BODY></HTML>