[vz-users] D0 / S0 Erfassung am ACE3000

Stefan stefan at stinkes.de
Sun Jan 4 00:24:27 CET 2015


Hallo,

ich habe meinen Zähler mal per S0 abgefragt. Er liest auch - allerdings 
verstehe ich die Ergebnisse nicht ganz.

Aber zuerst die Details:

Itron ACE3000 Typ 260-C20D-R1-Z
Typschlüssel:
2 = Mode 2 - Simulation eines Ferrariszählers mit Rücklaufsperre
0 = Genauigkeitsklasse 2
R1 = Eintarif Zählwerk
Z = Ohne Impulsausgang

Impulslänge an IR-LED ist 2ms.

Im .conf habe ich diese Angaben gemacht:

{
   "retry" : 30, /* how long to sleep between failed requests, in seconds */
   "daemon": true, /* run as server */
   "verbosity" : 15, /* between 0 and 15 */
   "log" : "/var/log/vzlogger.log", /* path to logfile, optional */

   "local" : {
     "enabled" : true, /* should we start the local HTTPd for serving 
live readings? */
     "port" : 8080, /* the TCP port for the local HTTPd */
     "index" : true, /* should we provide a index listing of available 
channels if no UUID was requested? */
     "timeout" : 30, /* timeout for long polling comet requests, 0 
disables comet, in seconds */
     "buffer" : 600 /* how long to buffer readings for the local 
interface, in seconds */
   },

   "meters" : [{
/* Itron ACE3000 Typ 260 */
     "enabled" : true, /* disabled meters will be ignored */
     "skip": false, // if enabled, errors when opening meter will lead 
to meter being ignored
     "protocol": "s0",
     "device" : "/dev/usb-ir-lesekopf0",
/*    "parity": "7E1",*/
/*    "baudrate": 300,*/
     "aggtime": 30, // aggregate all signals and give one update to 
middleware every 300 seconds
     "aggfixedinterval": true, // round all timestamps to middleware to 
nearest aggtime
     "channels": [{
         "identifier": "Impulse", // s0 meter knows "Impulse" and "Power"
         "uuid": "125483f0-xxxx-yyyy-zzzz-a905819afcfd",
         "middleware": "http:MyURL/middleware.php",
         "aggmode": "SUM" // add all s0 intervals in the aggregation
         }]
     }
]}

Hier ein typische Auszug aus dem Logfile

[Jan 03 19:49:01]       Opened logfile /var/log/vzlogger.log
[Jan 03 19:49:01][]     ===> Start meters
[Jan 03 19:49:01][mtr0] Meter connection established
[Jan 03 19:49:01][mtr0] Meter thread started
[Jan 03 19:49:01][mtr0] Meter is opened. Starting channels.
[Jan 03 19:49:01][chn0] Logging thread started
[Jan 03 19:49:01][http] Starting local interface HTTPd on port 8080
[Jan 03 19:49:01][]     Startup done.
[Jan 03 19:49:01][chn0] Start logging thread for volkszaehler-api. 
Running as daemon: yes
[Jan 03 19:49:01][chn0] Using default volkszaehler api.
[Jan 03 19:49:01][mtr0] Number of readers: 2
[Jan 03 19:49:01][mtr0] Config.daemon: 1
[Jan 03 19:49:01][mtr0] Config.local: 1
[Jan 03 19:49:03][s0]   Reading S0 - n=2 power=3735.063426
[Jan 03 19:49:03][mtr0] Got 2 new readings from meter:
[Jan 03 19:49:03][mtr0] Reading: id=Power/StringItentifier: 
value=3735.06 ts=1420310943.427
[Jan 03 19:49:03][mtr0] Reading: id=Impulse/StringItentifier: value=2.00 
ts=1420310943.427
[Jan 03 19:49:03][chn0] Adding reading to queue (value=2.00 
ts=1420310943.427)

Was mich neben den Werten irritiert sind die zwei Wertereihen die 
ausgelesen werden. In der Konfiguration ist doch eindeutig mit 
"identifier": "Impulse" gesetzt. Der angehangene Screenshot zeigt die 
zwei S0-Datenreihen im Vergleich zur D0-Messung.


Grüße

Stefan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Frontend Screenshot.PNG
Type: image/png
Size: 70387 bytes
Desc: not available
URL: <http://demo.volkszaehler.org/pipermail/volkszaehler-users/attachments/20150104/3407e9db/attachment-0001.png>


More information about the volkszaehler-users mailing list