So for the WH57, any further calculations are pointless. The referenced PR is for a Tempest, as far as I know, the Tempest reports every singly lightning detection as an event immediately, as an addition to the packet containing all the values every minute.
gjr80 schrieb am Mittwoch, 21. Juni 2023 um 23:41:53 UTC+2: > The issue is not whether the driver is 'dumb' or what the console does nor > over what period. The fact of the matter is that WH57 only provides the > distance of the last detected strike, not the average, not the sum nor any > other aggregate. That distance has no relationship whatsoever with any > earlier strikes so there is no value in weighting the reports distance > value. It is simply the distance of the last detected strike, nothing more. > > Gary > > On Wednesday, 21 June 2023 at 21:58:13 UTC+1 [email protected] > wrote: > >> Hi Gary, >> >> I think you know that by saying that your driver were "dump" I didn't >> want to discredit your work. 😉 - Just that the work is done by the console >> (or earlier in the chain). >> >> The WH57 provides only the number of strikes since the last reporting >> including the distance of that last strike. In an interval of 79 seconds >> which starts with the first detection. >> It's the console which does the counting and adds the EPOCH time stamp as >> the WH57 has no internal clock which is gauged against current real time. >> From there the API response from the console is number of strikes, time >> stamp of last strike, distance of last strike (which will be saved in the >> console after a thunderstorm until the next lightning detection). >> The number of strikes (strike count) is reset to zero by the console at >> midnight. That's why it keeps on sending, count 0, distance last strike, >> time stamp last strike after a day with lightnings and no new lightning >> detected past midnight. >> The detection, counting etc. is done by the AS3935 IC inside the WH57 ( >> https://www.sciosense.com/products/wireless-sensor-nodes/as3935-franklin-lightning-sensor-ic/ >> >> ). >> As for weighting, I don't see a reason for that either. >> >> Rainer >> On 21.06.2023 22:32, gjr80 wrote: >> >> I really don't see the point of trying to weight lightning strike >> distance from a WH57. In essence the WH57 reports three things; the number >> of lightning strike detected today, the time of the last detected lightning >> strike and the distance of the last lightning strike. This is clearly >> stated in the WH57 manual. The Ecowitt Gateway API is not so specific (it >> omits the word 'last'), but the API reports the same data as displayed by >> the Ecowitt's WSView Plus app so I think it is safe to assume the API >> reports time and distance of last strike. So if a given number of lightning >> strikes occur in a period the Ecowitt gateway driver and any connected >> console/app will only see time and distance data for the last detected >> strike, nothing for any earlier strikes. >> >> The referenced PR does not state what type of lighting detector is used, >> but the code looks suspiciously Ecowitt gateway driver'ish and for the >> reasons outlined above I really don't see any value in weighting light >> strike distance. >> >> Gary >> >> -- >> 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 [email protected]. >> >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/weewx-user/bcd2d06b-bfb6-48bd-b290-d8710a869ddan%40googlegroups.com >> >> <https://groups.google.com/d/msgid/weewx-user/bcd2d06b-bfb6-48bd-b290-d8710a869ddan%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/3bb1de25-6f92-4c1a-9cdc-d5c34f675354n%40googlegroups.com.
