GW3000 Speicherzeitpunkte inkonsistent?

Für Geräte von froggit
Antworten
mitschke
Offline
Beiträge: 241
Registriert: 13 Jul 2023, 12:05
Hat sich bedankt: 10 mal
Danksagung erhalten: 23 mal

GW3000 Speicherzeitpunkte inkonsistent?

#1

Beitrag von mitschke »

Mir ist aufgefallen, dass die Speicherzeitpunkte der Einträge auf der SD-Karte "variabel" sind. bei einem 5-Minuten-Intervall kann es sein, dass die Eintrage mal um 11:51 - 11:56 - 12:01 sind, oder auch 11:48 - 11:53 -11:58. Das ist jetzt kein Riesenproblem, aber doch etwas inkonsistent und zumindest potenziell nach jedem Neustart des GW unterschiedlich.

Erwarten würde ich, dass die Speicherzeitpunkte konsistent sind, zumindest für Intervalle, die ganzzahlig durch 50 teilbar sind, das wären: 1, 2, 3, 4, 5, 6, 10, 12, 15, 20, 30. Bei einem 5-Minuten-Intervall also fix 11:45 - 11:50 - 11:55.

Wollte mal nachfragen, ob ich das alleine bin oder ob ein solcher Wunsch an Ecowitt auch anderen Leuten ein Anliegen wäre.
Benutzeravatar
Gyvate
Offline
Beiträge: 4381
Registriert: 10 Aug 2021, 23:41
Wohnort: Saarbrücken
Hat sich bedankt: 15 mal
Danksagung erhalten: 629 mal
Kontaktdaten:

Re: GW3000 Speicherzeitpunkte inkonsistent?

#2

Beitrag von Gyvate »

es gab dieses Problem früher, dass mal eine Minute übersprungen wurde, da in Sekunden gezählt wurde aber nur Stunden und Minuten angezeigt wurden. Da kam es zu Rundungsproblemen, und je nach Intervall fiel nach 30 Mal eine Minute aus. Das wurde aber mit einem Firmwareupgrade behoben. Ich sehe bei mir nur 2, 4, 6, 8, 0 als Minuten mit einem 2-Minuten Speicherintervall. Früher gab's da auch mal zeitweise 3. 5, 7, 9 bis beim nächsten Runden wieder in die ganzzahligen Minuten überging. Beim 1-minütigen Intervall sollte das überhaupt nicht auftreten und das EpochDatum sollte immer in 60er (x Intervallgröße) Schritten hochzählen.
Ich habe das jetzt mal mit meiner WS6210 verglichen, die in 5 Minutenschritten zählt. Dort kommt es ca. alle 140 Zeilen zu einem Sprung. Allerdings sind das das einmal 4 Minuten und dann geht's mit 5 Minuten weiter. Allerdings wird der EPOCH Zeitstempel konsequent um 300 (Sekunden) erhöht, auch beim nur 4er Sprung.
Allerdings kommt es kurzzeitig zu einer Erhöhung um eine Sekunde, die dann nach ein paar Zeilen wieder korrigiert wird.
siehe Datenauszug

Code: Alles auswählen

2025-12-01 10:42,1764582120,18.8,48,1.8,99,1.7,1.8,--,--,0.007,0.0,0.0,268,268,990.0,1025.5,0.90,0,5.40,4.91,100,0,0.0,1.1,0.0,3.5,0.0,4.0,0.0,657.2,0.0,0.0,0.0,0.0,0.0,0.0,0.0,755.3
2025-12-01 10:47,1764582420,18.8,48,1.9,99,1.8,1.9,--,--,0.007,0.0,0.0,268,267,990.2,1025.7,0.94,0,5.40,4.87,100,0,0.0,1.1,0.0,3.5,0.0,4.0,0.0,657.2,0.0,0.0,0.0,0.0,0.0,0.0,0.0,755.3
2025-12-01 10:52,1764582720,18.8,48,2.0,99,1.9,2.0,--,--,0.007,0.0,0.0,268,268,990.0,1025.5,1.08,0,5.41,4.91,100,0,0.0,1.1,0.0,3.5,0.0,4.0,0.0,657.2,0.0,0.0,0.0,0.0,0.0,0.0,0.0,755.3
2025-12-01 10:57,1764583020,18.8,48,2.1,99,2.0,2.1,--,--,0.007,0.0,0.0,267,267,990.0,1025.5,1.17,0,5.42,4.91,100,0,0.0,1.1,0.0,3.5,0.0,4.0,0.0,657.2,0.0,0.0,0.0,0.0,0.0,0.0,0.0,755.3
2025-12-01 11:02,1764583320,18.8,48,2.2,99,2.1,2.2,--,--,0.007,0.0,0.0,267,267,990.3,1025.8,1.07,0,5.41,4.89,100,0,0.0,0.6,0.0,0.0,0.0,4.0,0.0,657.2,0.0,0.0,0.0,0.0,0.0,0.0,0.0,755.3
2025-12-01 11:07,1764583621,18.8,48,2.3,99,2.2,2.3,--,--,0.007,0.0,0.0,267,267,990.2,1025.7,1.02,0,5.41,4.91,100,0,0.0,0.6,0.0,0.0,0.0,4.0,0.0,657.2,0.0,0.0,0.0,0.0,0.0,0.0,0.0,755.3
2025-12-01 11:12,1764583921,18.8,48,2.3,99,2.2,2.3,--,--,0.007,0.0,0.5,267,267,990.1,1025.5,1.08,0,5.40,4.93,100,0,0.0,0.6,0.0,0.0,0.0,4.0,0.0,657.2,0.0,0.0,0.0,0.0,0.0,0.0,0.0,755.3
2025-12-01 11:16,1764584161,18.8,48,2.4,99,2.3,2.4,--,--,0.007,0.0,0.0,267,267,989.9,1025.3,1.04,0,5.41,4.93,100,0,0.0,0.6,0.0,0.0,0.0,4.0,0.0,657.2,0.0,0.0,0.0,0.0,0.0,0.0,0.0,755.3
2025-12-01 11:21,1764584461,18.8,48,2.5,99,2.4,2.5,--,--,0.007,0.0,0.0,267,267,990.0,1025.4,0.96,0,5.41,4.89,100,0,0.0,0.6,0.0,0.0,0.0,4.0,0.0,657.2,0.0,0.0,0.0,0.0,0.0,0.0,0.0,755.3
2025-12-01 11:25,1764584701,18.8,48,2.6,99,2.5,2.6,--,--,0.007,0.0,0.0,267,267,989.8,1025.2,0.98,0,5.41,4.91,100,0,0.0,0.6,0.0,0.0,0.0,4.0,0.0,657.2,0.0,0.0,0.0,0.0,0.0,0.0,0.0,755.3
2025-12-01 11:30,1764585001,18.8,48,2.7,99,2.6,2.7,--,--,0.007,0.0,0.0,267,267,989.8,1025.2,0.95,0,5.41,4.92,100,0,0.0,0.6,0.0,0.0,0.0,4.0,0.0,657.2,0.0,0.0,0.0,0.0,0.0,0.0,0.0,755.3
2025-12-01 11:35,1764585301,18.8,48,2.8,99,2.7,2.8,--,--,0.007,0.0,0.0,267,267,989.6,1025.0,1.02,0,5.41,4.91,100,0,0.0,0.6,0.0,0.0,0.0,4.0,0.0,657.2,0.0,0.0,0.0,0.0,0.0,0.0,0.0,755.3
2025-12-01 11:40,1764585601,18.8,48,2.8,99,2.7,2.8,--,--,0.007,0.0,0.0,267,267,989.5,1024.9,0.92,0,5.41,4.89,100,0,0.0,0.6,0.0,0.0,0.0,4.0,0.0,657.2,0.0,0.0,0.0,0.0,0.0,0.0,0.0,755.3
2025-12-01 11:45,1764585901,18.8,48,3.0,99,2.9,3.0,--,--,0.008,0.0,0.0,267,267,989.7,1025.0,0.90,0,5.41,4.91,100,0,0.0,0.6,0.0,0.0,0.0,4.0,0.0,657.2,0.0,0.0,0.0,0.0,0.0,0.0,0.0,755.3
2025-12-01 11:50,1764586201,18.8,48,3.1,99,3.0,3.1,--,--,0.008,0.5,1.0,294,267,989.4,1024.7,1.11,0,5.40,4.91,100,0,0.0,0.6,0.0,0.0,0.0,4.0,0.0,657.2,0.0,0.0,0.0,0.0,0.0,0.0,0.0,755.3
2025-12-01 11:55,1764586501,18.8,48,3.1,99,3.0,3.1,--,--,0.008,0.1,0.5,304,300,989.2,1024.5,1.04,0,5.41,4.91,100,0,0.0,0.6,0.0,0.0,0.0,4.0,0.0,657.2,0.0,0.0,0.0,0.0,0.0,0.0,0.0,755.3
2025-12-01 11:58,1764586681,18.9,48,3.2,99,3.1,3.2,--,--,0.008,0.0,0.0,303,303,989.2,1024.5,0.88,0,5.41,4.91,100,0,0.0,0.6,0.0,0.0,0.0,4.0,0.0,657.2,0.0,0.0,0.0,0.0,0.0,0.0,0.0,755.3
2025-12-01 12:03,1764586981,18.8,48,3.4,99,3.3,3.4,--,--,0.008,0.0,0.0,303,303,989.2,1024.5,0.92,0,5.40,4.89,100,0,0.0,0.1,0.0,0.0,0.0,4.0,0.0,657.2,0.0,0.0,0.0,0.0,0.0,0.0,0.0,755.3
2025-12-01 12:08,1764587280,18.9,48,3.5,98,3.2,3.5,--,--,0.016,0.0,0.0,307,307,989.0,1024.2,1.05,0,5.41,4.93,100,0,0.0,0.1,0.0,0.0,0.0,4.0,0.0,657.2,0.0,0.0,0.0,0.0,0.0,0.0,0.0,755.3
2025-12-01 12:13,1764587581,18.9,48,3.6,98,3.3,3.6,--,--,0.016,0.0,0.0,307,306,989.0,1024.2,0.99,0,5.41,4.92,100,0,0.0,0.1,0.0,0.0,0.0,4.0,0.0,657.2,0.0,0.0,0.0,0.0,0.0,0.0,0.0,755.3
2025-12-01 12:18,1764587880,18.9,48,3.8,97,3.4,3.8,--,--,0.024,0.0,0.0,312,312,989.1,1024.3,1.30,0,5.41,4.92,100,0,0.0,0.1,0.0,0.0,0.0,4.0,0.0,657.2,0.0,0.0,0.0,0.0,0.0,0.0,0.0,755.3
2025-12-01 12:23,1764588180,18.9,48,3.9,96,3.3,3.9,--,--,0.032,0.2,1.0,11,304,989.0,1024.2,1.30,0,5.41,4.93,100,0,0.0,0.1,0.0,0.0,0.0,4.0,0.0,657.2,0.0,0.0,0.0,0.0,0.0,0.0,0.0,755.3
2025-12-01 12:28,1764588480,18.9,48,4.0,94,3.1,4.0,--,--,0.049,0.0,0.5,34,36,989.1,1024.3,1.31,0,5.40,4.91,100,0,0.0,0.1,0.0,0.0,0.0,4.0,0.0,657.2,0.0,0.0,0.0,0.0,0.0,0.0,0.0,755.3
2025-12-01 12:33,1764588780,18.9,48,4.2,94,3.3,4.2,--,--,0.049,0.0,0.0,35,35,988.7,1023.8,1.45,0,5.42,4.89,100,0,0.0,0.1,0.0,0.0,0.0,4.0,0.0,657.2,0.0,0.0,0.0,0.0,0.0,0.0,0.0,755.3
2025-12-01 12:38,1764589080,18.9,48,4.3,93,3.3,4.3,--,--,0.058,0.0,0.0,6,35,988.7,1023.8,1.48,0,5.41,4.91,100,0,0.0,0.1,0.0,0.0,0.0,4.0,0.0,657.2,0.0,0.0,0.0,0.0,0.0,0.0,0.0,755.3
2025-12-01 12:43,1764589380,18.9,48,4.5,92,3.3,4.5,--,--,0.067,0.0,0.0,346,9,988.6,1023.7,2.06,0,5.40,4.91,100,0,0.0,0.1,0.0,0.0,0.0,4.0,0.0,657.2,0.0,0.0,0.0,0.0,0.0,0.0,0.0,755.3
2025-12-01 12:48,1764589680,18.9,48,4.6,91,3.3,4.6,--,--,0.076,0.1,0.5,312,347,988.7,1023.8,1.86,0,5.41,4.92,100,0,0.0,0.1,0.0,0.0,0.0,4.0,0.0,657.2,0.0,0.0,0.0,0.0,0.0,0.0,0.0,755.3

beim GW3000 mit zwei Minuten gibt es bei mir keine Sprünge.
Ecowitt Konsolen und Sensoren
WS2320E, HP2553, HP3501, WN1910, WN1980, WN1820, WS3800, WS3910, WH2810,
GW1000, GW1100, GW1200, GW2000, GW3000, WH2650,WS6210,
WS68, WS69, WS80, WS85, WS90,
WN30, WH31[EP], WH32[EP], WN32P, WN34L, WN34S,WN34D, WN35, WH41, WH45, WH46D, WH51, WH55, WH57, LDS01
Meteobridge Pro, MB RPi (2), MB VM, Weewx v4, CumulusMX v3, CumulusMX v4
Barani MeteoShield Pro (G2 + G3), MetSpec Rad02, SIAP SMarTCELLino, Ambient SRS100LX
Personal Weather Tablet(PWT), FOSHKplugin, Dracal BAR20
Weather Landing page: http://meshka.eu
Ecowitt WiKi Englisch: http://meshka.eu/Ecowitt/dokuwiki
mitschke
Offline
Beiträge: 241
Registriert: 13 Jul 2023, 12:05
Hat sich bedankt: 10 mal
Danksagung erhalten: 23 mal

Re: GW3000 Speicherzeitpunkte inkonsistent?

#3

Beitrag von mitschke »

Ich habe ein 5-Minuten-Intervall und mir geht es nicht um die Sprünge, sondern, dass ein 5-Minuten-Intervall nicht ausschließlich auf 0 und 5 endet. Bisher hatte ich nur Geräte uns Software, die Intervalle so gestaltet hat.
Benutzeravatar
Gyvate
Offline
Beiträge: 4381
Registriert: 10 Aug 2021, 23:41
Wohnort: Saarbrücken
Hat sich bedankt: 15 mal
Danksagung erhalten: 629 mal
Kontaktdaten:

Re: GW3000 Speicherzeitpunkte inkonsistent?

#4

Beitrag von Gyvate »

Na ja, ich denke, dass das von dem Zeitpunkt abhängt, an dem die Aufzeichnung beginnt.
Du kannst den GW3000 ja mal 15 Sekunden vor der 5. Minute neu starten.
Er verhält sich nicht wie weewx, das immer die 5. Minute auswählt, wenn eine 300 Sekundenintervall gewählt wurde.
Ecowitt Konsolen und Sensoren
WS2320E, HP2553, HP3501, WN1910, WN1980, WN1820, WS3800, WS3910, WH2810,
GW1000, GW1100, GW1200, GW2000, GW3000, WH2650,WS6210,
WS68, WS69, WS80, WS85, WS90,
WN30, WH31[EP], WH32[EP], WN32P, WN34L, WN34S,WN34D, WN35, WH41, WH45, WH46D, WH51, WH55, WH57, LDS01
Meteobridge Pro, MB RPi (2), MB VM, Weewx v4, CumulusMX v3, CumulusMX v4
Barani MeteoShield Pro (G2 + G3), MetSpec Rad02, SIAP SMarTCELLino, Ambient SRS100LX
Personal Weather Tablet(PWT), FOSHKplugin, Dracal BAR20
Weather Landing page: http://meshka.eu
Ecowitt WiKi Englisch: http://meshka.eu/Ecowitt/dokuwiki
mitschke
Offline
Beiträge: 241
Registriert: 13 Jul 2023, 12:05
Hat sich bedankt: 10 mal
Danksagung erhalten: 23 mal

Re: GW3000 Speicherzeitpunkte inkonsistent?

#5

Beitrag von mitschke »

Ja genau darauf will ich hinaus. Bisher hat sich jedes Gerät so verhalten. Ich sag ja nicht, dass es falsch ist. Dennoch wird fixes Intervall sehr oft so interpretiert: die stündlichen Nachrichten gibt es zu jeder vollen Stunde, nicht etwa jeweils zu 57. Minute. Schaute ich auf diverse Webcams, die im 10-Minuten-Intervall Bilder liefern, so sind die Zeitstempel immer mit 0 am Ende, auf einer anderen Seite mit 15 Minuten Intervall, jeweils um 15, 30, 45, 00. Wetterseiten mit Radarbildern im 5-Minuten-Intervall liefern diese 0-5-0.

Abhängig von Startzeitpunkt alle x-Minuten ein Intervall zu beenden ist natürlich legitim, aber halt eher unüblich.
Antworten