Rainer, the WH57 sends lightning data as the lighning is detected, the console shows this data immediately. I observed this mutliple times:
You see the lightning out there, the LED of the WH57 flashes red, the counter on the console goes up, the distance is also updated. If there is a lightning just a few seconds later, the same game again. Even when polling the console API in an interval < 79s, you get the lightning data updates more frequently than 79s. Wait for the next storm and see. I have no doubt that with SDR you can receive these data, as it's sent by the WH57. Your information does not fit the observed reality. Whats true is that you need to store lightning data in a different format, to calculate a meaningful value for the archive record. Something like the count per interval and a kind of weighted average for the distance. It exists for the Tempest, which transmits lightning data using UDP as it detects a lightning. Apart from the other data which is transmitted in a constant interval. Rainer Lang schrieb am Montag, 3. Juni 2024 um 17:25:34 UTC+2: > "If there is a possibility to extract a singled detected lightning event > and > > it's data with standard devices, is another story. If so, I'd see the > point > > of doing so. At least the minimal distance and weighted average distance > > are interesting values to me. I doubt it is possible doing this with the > > "Ecowitt Gateway Driver", I have no idea if it is possible with the > > interceptor driver and a WH2551, it should be possible using SDR." > > what part of transmitting every 79 seconds has not been understood ? > And the 79 seconds start with the first detected discharge. > > Why would SDR receive more and more often ? Magic SDR ? > SDR is nothing else but a radio receiver as is a console. > Just by changing the console the sensor won't post faster. > > And it's not an Acurite chipset (maybe some Acurite device uses the same > chip); > it's an AS3935 - before starting wild speculations I would read the > specifications and see if the chip can be animated to provide data more > frequently. > Then you can try your luck modifying the sensor firmware if that's > possible and not limited by the chip itself ... > > And have a look what exactly the chip provides/can provide ... > check if it provides such things like minimal distance, weighted distance > etc. > Nice wishlist, but as far as I have understood the specifications, it > doesn't do that. > Admittedly, I'm not an expert here - somebody else may be able to extract > more information > > Google can be your friend - look up the AS3935 specifications/data sheet > etc. > > But as for the WH57 as manufactured, it will transmit every 79 seconds .... > > And it has nothing to do with the Ecowitt Gateway driver or any other > driver - you can have it poll every two seconds. > But it can get only what the console has available to send. And the > console only has what it receives from what was transmitted. > > Maybe it would be helpful to understand how weewx works ... > > Classically the data received from a driver or extension is collected in a > loop where data gets accumulated. > That doesn't seem to be what you want. You seem to want every single > data-item to be recorded separately. > Then you will also have to write the code which does this and save the > data in a way you can reuse it - i.e. write your own extension. > You'd probably need your own separate lightning database for that too. > In the typical way weewx works, collects and archives data that won't work > as far as I can see. > > By the way - if there are no more discharges within 79 seconds, your > request above will be fulfilled 😉 > > all the sensor related information could have been found and read in the > Ecowitt WiKi > https://meshka.eu/Ecowitt/dokuwiki > > On 02.06.2024 19:25, 'michael.k...@gmx.at' via weewx-user wrote: > > Probably the only way getting reasonable data is with SDR. > > michael.k...@gmx.at schrieb am Freitag, 25. August 2023 um 07:32:51 UTC+2: > >> My best guess is that the Sensor reports every 79s "Hello, I'm there" and >> every detected lightning on top of that, immediately. If you don't live at >> Catatumbo River mouth, this shouldn't drain the battery too much. Let's see >> if Rainer Lang knows more Details. >> >> Greg Troxel schrieb am Freitag, 25. August 2023 um 01:53:48 UTC+2: >> >>> "michael.k...@gmx.at" <michael.k...@gmx.at> writes: >>> >>> > I am just now in the middle of this Storm with stroboscopic-like >>> lightning >>> > flashing. >>> > >>> > I recognized my HP2551 is obviously showing lightning strikes in >>> realtime. >>> > Every one or the other second. >>> > >>> > Then I checked back in the manual and now disagree with gjr80, when he >>> > states: >>> > >>> > gjr80 schrieb am Mittwoch, 21. Juni 2023 um 22:32:42 UTC+2: >>> > >>> > 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. >>> > Gary >>> >>> This sounds very much like the chip that is in the Acurite 6045M >>> >>> > If there is a possibility to extract a singled detected lightning >>> event and >>> > it's data with standard devices, is another story. If so, I'd see the >>> point >>> > of doing so. At least the minimal distance and weighted average >>> distance >>> > are interesting values to me. I doubt it is possible doing this with >>> the >>> > "Ecowitt Gateway Driver", I have no idea if it is possible with the >>> > interceptor driver and a WH2551, it should be possible using SDR. >>> >>> Certainly it would be great to log the bits and study them. The 6045M >>> only transmits periodically, with a longer period without lightning and >>> then faster in 'active mode'. I suspect the chip reports immediately, >>> and there is a different radio in the WH57. There is no reason why it >>> couldn't be set up to send promptly, other than battery life. >>> >> -- > > 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 weewx-user+...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-user/437ddc4e-27e4-409c-952d-4555f8a855d7n%40googlegroups.com > > <https://groups.google.com/d/msgid/weewx-user/437ddc4e-27e4-409c-952d-4555f8a855d7n%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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/59dc1609-6909-471e-9e83-9b7036a58249n%40googlegroups.com.
