Hyperion S0 Zähler

Antworten
Jacke
Beiträge: 14
Registriert: Freitag 11. November 2016, 04:05

Hyperion S0 Zähler

Beitrag von Jacke » Sonntag 19. Februar 2017, 21:58

Hallo ich versuche nun seid 2 Tagen einen S0 Zähler einzubinden. Mit dem Testprogramm kommen die Impulse rein. In den CSV datein sind leider nur 0,014 kwh geloggt als ob er nur loggt wenn genau zu dem Zeitpunkt des Loggens ein Imp kommt habe schon mit logintervall und pollintervall gespielt ohne erfolg.

Code: Alles auswählen

02:10:00:011 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 02:10:00 CET 2017
02:55:00:012 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 02:55:00 CET 2017
05:05:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 05:05:00 CET 2017
07:55:00:011 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 07:55:00 CET 2017
08:00:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 08:00:00 CET 2017
08:05:00:016 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 08:05:00 CET 2017
08:10:00:012 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 08:10:00 CET 2017
08:15:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 08:15:00 CET 2017
08:20:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 08:20:00 CET 2017
08:25:00:009 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 08:25:00 CET 2017
08:30:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 08:30:00 CET 2017
08:35:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 08:35:00 CET 2017
08:40:00:011 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 08:40:00 CET 2017
08:45:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 08:45:00 CET 2017
08:50:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 08:50:00 CET 2017
08:55:00:011 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 08:55:00 CET 2017
09:00:00:011 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 09:00:00 CET 2017
09:05:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 09:05:00 CET 2017
09:10:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 09:10:00 CET 2017
09:15:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 09:15:00 CET 2017
09:20:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 09:20:00 CET 2017
09:25:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 09:25:00 CET 2017
09:30:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 09:30:00 CET 2017
09:35:00:011 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 09:35:00 CET 2017
09:40:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 09:40:00 CET 2017
09:45:00:011 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 09:45:00 CET 2017
09:50:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 09:50:00 CET 2017
09:55:00:011 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 09:55:00 CET 2017
10:00:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 10:00:00 CET 2017
10:05:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 10:05:00 CET 2017
10:10:00:012 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 10:10:00 CET 2017
10:15:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 10:15:00 CET 2017
10:20:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 10:20:00 CET 2017
10:25:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 10:25:00 CET 2017
10:30:00:011 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 10:30:00 CET 2017
10:35:00:011 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 10:35:00 CET 2017
10:40:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 10:40:00 CET 2017
10:45:00:011 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 10:45:00 CET 2017
10:50:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 10:50:00 CET 2017
10:55:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 10:55:00 CET 2017
11:00:00:011 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 11:00:00 CET 2017
11:05:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 11:05:00 CET 2017
11:10:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 11:10:00 CET 2017
11:15:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 11:15:00 CET 2017
11:20:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 11:20:00 CET 2017
11:25:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 11:25:00 CET 2017
11:30:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 11:30:00 CET 2017
11:35:00:009 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 11:35:00 CET 2017
11:40:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 11:40:00 CET 2017
11:45:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 11:45:00 CET 2017
11:50:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 11:50:00 CET 2017
11:55:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 11:55:00 CET 2017
12:00:00:011 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 12:00:00 CET 2017
12:05:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 12:05:00 CET 2017
12:10:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 12:10:00 CET 2017
12:15:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 12:15:00 CET 2017
12:20:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 12:20:00 CET 2017
12:25:00:011 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 12:25:00 CET 2017
12:30:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 12:30:00 CET 2017
12:35:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 12:35:00 CET 2017
12:40:00:011 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 12:40:00 CET 2017
12:45:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 12:45:00 CET 2017
12:50:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 12:50:00 CET 2017
12:55:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 12:55:00 CET 2017
13:00:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 13:00:00 CET 2017
13:05:00:011 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 13:05:00 CET 2017
13:10:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 13:10:00 CET 2017
13:15:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 13:15:00 CET 2017
13:20:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 13:20:00 CET 2017
13:25:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 13:25:00 CET 2017
13:30:00:009 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 13:30:00 CET 2017
13:35:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 13:35:00 CET 2017
13:40:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 13:40:00 CET 2017
13:45:00:011 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 13:45:00 CET 2017
13:50:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 13:50:00 CET 2017
13:55:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 13:55:00 CET 2017
14:00:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 14:00:00 CET 2017
14:05:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 14:05:00 CET 2017
14:10:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 14:10:00 CET 2017
14:15:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 14:15:00 CET 2017
14:20:00:048 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 14:20:00 CET 2017
14:25:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 14:25:00 CET 2017
14:30:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 14:30:00 CET 2017
14:35:00:011 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 14:35:00 CET 2017
14:40:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 14:40:00 CET 2017
14:45:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 14:45:00 CET 2017
14:50:00:011 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 14:50:00 CET 2017
14:55:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 14:55:00 CET 2017
15:00:00:067 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 15:00:00 CET 2017
15:05:00:009 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 15:05:00 CET 2017
15:10:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 15:10:00 CET 2017
15:15:00:011 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 15:15:00 CET 2017
15:20:00:011 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 15:20:00 CET 2017
15:25:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 15:25:00 CET 2017
15:30:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 15:30:00 CET 2017
15:35:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 15:35:00 CET 2017
15:40:00:009 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 15:40:00 CET 2017
15:45:00:011 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 15:45:00 CET 2017
15:50:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 15:50:00 CET 2017
15:55:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 15:55:00 CET 2017
16:00:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 16:00:00 CET 2017
16:05:00:011 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 16:05:00 CET 2017
16:10:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 16:10:00 CET 2017
16:15:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 16:15:00 CET 2017
16:20:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 16:20:00 CET 2017
16:25:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 16:25:00 CET 2017
16:30:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 16:30:00 CET 2017
16:35:00:009 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 16:35:00 CET 2017
16:40:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 16:40:00 CET 2017
16:45:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 16:45:00 CET 2017
16:50:00:009 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 16:50:00 CET 2017
16:55:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 16:55:00 CET 2017
17:00:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 17:00:00 CET 2017
17:05:00:011 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 17:05:00 CET 2017
17:10:00:011 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 17:10:00 CET 2017
17:15:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 17:15:00 CET 2017
17:20:00:010 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 17:20:00 CET 2017
18:45:00:011 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 18:45:00 CET 2017
20:02:20:490 - INFO - ch.rse.pv.hyperion.Hyperion - Version: 0.5.3
20:02:22:127 - INFO - ch.rse.pv.hyperion.d.a - Initialisiere Logger...
20:02:22:136 - INFO - ch.rse.pv.hyperion.d.a - Poll-Interval: 30s
20:02:22:474 - INFO - ch.rse.pv.hyperion.d.a - Log-Interval: 300s
20:02:22:532 - INFO - ch.rse.pv.hyperion.b.a.c.a - Type='Kostal'; Host='192.168.1.36'; Port='81', RS485='255'
20:02:22:843 - INFO - ch.rse.pv.hyperion.b.a.d.a - Type='S0'
20:02:24:072 - INFO - ch.rse.pv.hyperion.g.a - Initialisiere Port /dev/ttyUSB0
20:05:00:147 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 20:05:00 CET 2017
21:11:11:779 - INFO - ch.rse.pv.hyperion.Hyperion - Version: 0.5.3
21:11:13:446 - INFO - ch.rse.pv.hyperion.d.a - Initialisiere Logger...
21:11:13:451 - INFO - ch.rse.pv.hyperion.d.a - Poll-Interval: 30s
21:11:13:793 - INFO - ch.rse.pv.hyperion.d.a - Log-Interval: 300s
21:11:13:854 - INFO - ch.rse.pv.hyperion.b.a.c.a - Type='Kostal'; Host='192.168.1.36'; Port='81', RS485='255'
21:11:14:012 - INFO - ch.rse.pv.hyperion.b.a.d.a - Type='S0'
21:11:15:193 - INFO - ch.rse.pv.hyperion.g.a - Initialisiere Port /dev/ttyUSB0
21:15:00:078 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 21:15:00 CET 2017
21:30:55:275 - INFO - ch.rse.pv.hyperion.Hyperion - Version: 0.5.3
21:30:56:870 - INFO - ch.rse.pv.hyperion.d.a - Initialisiere Logger...
21:30:56:875 - INFO - ch.rse.pv.hyperion.d.a - Poll-Interval: 30s
21:30:57:238 - INFO - ch.rse.pv.hyperion.d.a - Log-Interval: Direkt
21:30:57:342 - INFO - ch.rse.pv.hyperion.b.a.c.a - Type='Kostal'; Host='192.168.1.36'; Port='81', RS485='255'
21:30:57:598 - INFO - ch.rse.pv.hyperion.b.a.d.a - Type='S0'
21:30:58:751 - INFO - ch.rse.pv.hyperion.g.a - Initialisiere Port /dev/ttyUSB0
21:32:07:698 - INFO - ch.rse.pv.hyperion.d.a - read data from inverter and write to log at Sun Feb 19 21:32:00 CET 2017
21:32:07:703 - INFO - ch.rse.pv.hyperion.d.a - read data from inverter and write to log at Sun Feb 19 21:32:00 CET 2017
21:32:30:014 - INFO - ch.rse.pv.hyperion.d.a - read data from inverter and write to log at Sun Feb 19 21:32:30 CET 2017
21:33:00:017 - INFO - ch.rse.pv.hyperion.d.a - read data from inverter and write to log at Sun Feb 19 21:33:00 CET 2017
21:33:30:029 - INFO - ch.rse.pv.hyperion.d.a - read data from inverter and write to log at Sun Feb 19 21:33:30 CET 2017
21:34:00:016 - INFO - ch.rse.pv.hyperion.d.a - read data from inverter and write to log at Sun Feb 19 21:34:00 CET 2017
21:34:30:014 - INFO - ch.rse.pv.hyperion.d.a - read data from inverter and write to log at Sun Feb 19 21:34:30 CET 2017
21:35:00:015 - INFO - ch.rse.pv.hyperion.d.a - read data from inverter and write to log at Sun Feb 19 21:35:00 CET 2017
21:35:30:015 - INFO - ch.rse.pv.hyperion.d.a - read data from inverter and write to log at Sun Feb 19 21:35:30 CET 2017
21:36:00:015 - INFO - ch.rse.pv.hyperion.d.a - read data from inverter and write to log at Sun Feb 19 21:36:00 CET 2017
21:36:30:014 - INFO - ch.rse.pv.hyperion.d.a - read data from inverter and write to log at Sun Feb 19 21:36:30 CET 2017
21:37:00:013 - INFO - ch.rse.pv.hyperion.d.a - read data from inverter and write to log at Sun Feb 19 21:37:00 CET 2017
21:37:30:022 - INFO - ch.rse.pv.hyperion.d.a - read data from inverter and write to log at Sun Feb 19 21:37:30 CET 2017
21:38:00:020 - INFO - ch.rse.pv.hyperion.d.a - read data from inverter and write to log at Sun Feb 19 21:38:00 CET 2017
21:38:30:016 - INFO - ch.rse.pv.hyperion.d.a - read data from inverter and write to log at Sun Feb 19 21:38:30 CET 2017
21:39:00:061 - INFO - ch.rse.pv.hyperion.d.a - read data from inverter and write to log at Sun Feb 19 21:39:00 CET 2017
21:39:30:012 - INFO - ch.rse.pv.hyperion.d.a - read data from inverter and write to log at Sun Feb 19 21:39:30 CET 2017
21:40:00:012 - INFO - ch.rse.pv.hyperion.d.a - read data from inverter and write to log at Sun Feb 19 21:40:00 CET 2017
21:40:30:011 - INFO - ch.rse.pv.hyperion.d.a - read data from inverter and write to log at Sun Feb 19 21:40:30 CET 2017
21:41:00:010 - INFO - ch.rse.pv.hyperion.d.a - read data from inverter and write to log at Sun Feb 19 21:41:00 CET 2017
21:41:30:011 - INFO - ch.rse.pv.hyperion.d.a - read data from inverter and write to log at Sun Feb 19 21:41:30 CET 2017
21:42:00:016 - INFO - ch.rse.pv.hyperion.d.a - read data from inverter and write to log at Sun Feb 19 21:42:00 CET 2017
21:42:30:020 - INFO - ch.rse.pv.hyperion.d.a - read data from inverter and write to log at Sun Feb 19 21:42:30 CET 2017
21:43:00:019 - INFO - ch.rse.pv.hyperion.d.a - read data from inverter and write to log at Sun Feb 19 21:43:00 CET 2017
21:43:30:014 - INFO - ch.rse.pv.hyperion.d.a - read data from inverter and write to log at Sun Feb 19 21:43:30 CET 2017
21:44:00:014 - INFO - ch.rse.pv.hyperion.d.a - read data from inverter and write to log at Sun Feb 19 21:44:00 CET 2017
21:44:30:011 - INFO - ch.rse.pv.hyperion.d.a - read data from inverter and write to log at Sun Feb 19 21:44:30 CET 2017
21:45:00:013 - INFO - ch.rse.pv.hyperion.d.a - read data from inverter and write to log at Sun Feb 19 21:45:00 CET 2017
21:45:30:011 - INFO - ch.rse.pv.hyperion.d.a - read data from inverter and write to log at Sun Feb 19 21:45:30 CET 2017
21:46:00:014 - INFO - ch.rse.pv.hyperion.d.a - read data from inverter and write to log at Sun Feb 19 21:46:00 CET 2017
21:47:44:523 - INFO - ch.rse.pv.hyperion.Hyperion - Version: 0.5.3
21:47:46:150 - INFO - ch.rse.pv.hyperion.d.a - Initialisiere Logger...
21:47:46:532 - INFO - ch.rse.pv.hyperion.d.a - Poll-Interval: 5s
21:47:46:543 - INFO - ch.rse.pv.hyperion.d.a - Log-Interval: 60s
21:47:46:611 - INFO - ch.rse.pv.hyperion.b.a.c.a - Type='Kostal'; Host='192.168.1.36'; Port='81', RS485='255'
21:47:46:767 - INFO - ch.rse.pv.hyperion.b.a.d.a - Type='S0'
21:47:48:012 - INFO - ch.rse.pv.hyperion.g.a - Initialisiere Port /dev/ttyUSB0
21:48:00:066 - INFO - ch.rse.pv.hyperion.d.a - do logging at Sun Feb 19 21:48:00 CET 2017

Code: Alles auswählen

<?xml version="1.0" encoding="ISO-8859-1" ?>
<configuration>
  <logger>
    <loginterval>1</loginterval>
    <pollinterval>5</pollinterval>
   
    <inverter type="kostal">
      <host>192.168.1.36</host>
      <port>81</port>
      <address>255</address>
      <power>4850</power>
    </inverter>
	
	<inverter type="S0-IN">
		<name>My S0-Device</name>
		<power>1234</power>
		<impulserate>1000</impulserate>
		<port>/dev/ttyUSB0</port>
		<rs232Config>
		<receiveTimeout>1</receiveTimeout>
		<rts>true</rts>
		</rs232Config>
	</inverter>

	
	<processor type="pvoutput">
	<apikey>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</apikey>
	<systemid>XXXXX</systemid>
		<writer type="http-post">
			<url>http://pvoutput.org/service/r2</url>
		</writer>
	</processor>
				
	<processor type="solarAnalyzer">
		<writer type="file">
			<path>/home/pi/hyperion/SolarAnalyzer</path>
		</writer>
	</processor>
        
    <processor type="csv">
		<writer type="file">
			<path>/home/pi/hyperion/CSV</path>
		</writer>
    </processor>
		
  </logger>
 
	
</configuration>
Jemand schonmal das Problem gehabt.

Roland
Beiträge: 214
Registriert: Montag 29. Oktober 2012, 18:19

Re: Hyperion S0 Zähler

Beitrag von Roland » Mittwoch 22. Februar 2017, 14:11

Hallo Jacke

Was sagt denn das Testprogramm? Wie oft kommen die Impulse? Stimmt die Impulsrate von 1000?
Poll- und Logintervall wird dir beim S0 nichts nützen. Der zählt intern die Impulse. Die Werte geben dann nur vor, wie oft der Zählstand abgeholt respektive geloggt wird. Das hat keinen Einfluss auf den Zählstand selber.

Der Logger schreibt noch eine Datei S0_xx.dat. Ist die da? Wie verändert sich diese über die Zeit?

Jacke
Beiträge: 14
Registriert: Freitag 11. November 2016, 04:05

Re: Hyperion S0 Zähler

Beitrag von Jacke » Donnerstag 23. Februar 2017, 11:35

1000 Imp sind richtig. Impulse kommen alle 2-3 Stunden rein. Habe nochmal das Testprogramm gestartet bekomme nun immer

Code: Alles auswählen

RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyUSB0: Die Datei existiert bereits
RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyUSB0: Die Datei existiert bereits
RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..ttyUSB0: Die Datei existiert bereits
gnu.io.NoSuchPortException
        at gnu.io.CommPortIdentifier.getPortIdentifier(CommPortIdentifier.java:273)
        at ch.rse.pv.hyperion.g.a.a(RS232Tester:93)
        at ch.rse.pv.hyperion.RS232Tester.a(RS232Tester:12)
        at ch.rse.pv.hyperion.RS232Tester.main(RS232Tester:29)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:601)
        at org.eclipse.jdt.internal.jarinjarloader.JarRsrcLoader.main(RS232Tester:58)
Ich hatte das schonmal beim einrichten, war dann aber weg und das Programm lieferte alle 5sek. einen Impuls.
Habe mal versucht dem Gerät einen Allgemein gültigen namen zu geben. Scheitere daran allerdings. Kann es sein das ich keine Treiber habe?

Roland
Beiträge: 214
Registriert: Montag 29. Oktober 2012, 18:19

Re: Hyperion S0 Zähler

Beitrag von Roland » Donnerstag 23. Februar 2017, 11:56

Irgendwas scheint deinen Com-Port zu blockieren. Hast du hyperion und das Testprogramm gleichzeitig gestartet?

Jacke
Beiträge: 14
Registriert: Freitag 11. November 2016, 04:05

Re: Hyperion S0 Zähler

Beitrag von Jacke » Donnerstag 23. Februar 2017, 17:59

Mist das stimmt versuche es nochmal

Jacke
Beiträge: 14
Registriert: Freitag 11. November 2016, 04:05

Re: Hyperion S0 Zähler

Beitrag von Jacke » Samstag 25. Februar 2017, 15:55

Habe ich gemacht ich bekomme immer ein Impuls und dann Ende

Code: Alles auswählen

pi@raspberrypi ~/hyperion $ sudo java -jar RS232Tester_0.5.0.jar /dev/ttyUSB0 rs232_settings.properties
15:46:18,196  INFO ch.rse.pv.hyperion.g.a - Initialisiere Port /dev/ttyUSB0
Device on Port /dev/ttyUSB0 started.
S0-Data received.
^Cpi@raspberrypi ~/hyperion $ ^C
pi@raspberrypi ~/hyperion $ sudo java -jar RS232Tester_0.5.0.jar /dev/ttyUSB0 rs232_settings.properties
RXTX Warning:  Removing stale lock file. /var/lock/LCK..ttyUSB0
15:47:26,758  INFO ch.rse.pv.hyperion.g.a - Initialisiere Port /dev/ttyUSB0
Device on Port /dev/ttyUSB0 started.
S0-Data received.
S0-Data received.
^[[A^Cpi@raspberrypi ~/hyperion $ sudo java -jar RS232Tester_0.5.0.jar /dev/ttyUSB0 rs232_setproperties
RXTX Warning:  Removing stale lock file. /var/lock/LCK..ttyUSB0
15:47:53,356  INFO ch.rse.pv.hyperion.g.a - Initialisiere Port /dev/ttyUSB0
Device on Port /dev/ttyUSB0 started.
S0-Data received.
^Cpi@raspberrypi ~/hyperion $ sudo java -jar RS232Tester_0.5.0.jar /dev/ttyUSB0 rs232_settingproperties
RXTX Warning:  Removing stale lock file. /var/lock/LCK..ttyUSB0
15:48:15,618  INFO ch.rse.pv.hyperion.g.a - Initialisiere Port /dev/ttyUSB0
Device on Port /dev/ttyUSB0 started.
S0-Data received.
^Cpi@raspberrypi ~/hyperion $ sudo rm -f /var/lock/LCK..ttyUSB0
pi@raspberrypi ~/hyperion $ sudo rm -f /var/lock/LCK..ttyUSB0
pi@raspberrypi ~/hyperion $ sudo java -jar RS232Tester_0.5.0.jar /dev/ttyUSB0 rs232_settings.properties
15:51:09,728  INFO ch.rse.pv.hyperion.g.a - Initialisiere Port /dev/ttyUSB0
Device on Port /dev/ttyUSB0 started.
S0-Data received.
^Cpi@raspberrypi ~/hyperion $ sundo nano rs232_settings.properties
-bash: sundo: Kommando nicht gefunden.
pi@raspberrypi ~/hyperion $ sudo nano rs232_settings.properties
pi@raspberrypi ~/hyperion $ sudo nano rs232_settings.properties
pi@raspberrypi ~/hyperion $ sudo java -jar RS232Tester_0.5.0.jar /dev/ttyUSB0 rs232_settings.properties
RXTX Warning:  Removing stale lock file. /var/lock/LCK..ttyUSB0
15:52:52,586  INFO ch.rse.pv.hyperion.g.a - Initialisiere Port /dev/ttyUSB0
Device on Port /dev/ttyUSB0 started.
S0-Data received.
Gruß Nils

Roland
Beiträge: 214
Registriert: Montag 29. Oktober 2012, 18:19

Re: Hyperion S0 Zähler

Beitrag von Roland » Montag 27. Februar 2017, 15:32

Du startest ja auch alle paar Sekunden die Applikation neu.
Da kamen doch innerhalb 30s zwei Impulse an:
RXTX Warning: Removing stale lock file. /var/lock/LCK..ttyUSB0
15:47:26,758 INFO ch.rse.pv.hyperion.g.a - Initialisiere Port /dev/ttyUSB0
Device on Port /dev/ttyUSB0 started.
S0-Data received.
S0-Data received.
^[[A^Cpi@raspberrypi ~/hyperion $ sudo java -jar RS232Tester_0.5.0.jar /dev/ttyUSB0 rs232_setproperties
RXTX Warning: Removing stale lock file. /var/lock/LCK..ttyUSB0
15:47:53,356 INFO ch.rse.pv.hyperion.g.a - Initialisiere Port /dev/ttyUSB0
Was ist deine Erwartung? Wie oft sollten die Impulse deiner Meinung nach kommen?

Jacke
Beiträge: 14
Registriert: Freitag 11. November 2016, 04:05

Re: Hyperion S0 Zähler

Beitrag von Jacke » Donnerstag 2. März 2017, 22:36

Alle 7sek. mindestens. Habe ca 500W Grundlast. Zu der Zeit lief noch zusätzlich die Spülmaschinen.
Es kommen ja Signale aber viel zu selten. Habe den Teiler auf 1000 und in einem Tag steigt der Zähler um 0,012 kWh.

Antworten