Ich habe soeben die neue Firmware aufgespielt. Hat natürlich alles geklappt.
Aber ich hab da eine Frage:
Die "Alte" Version, da stand im Broswer oben rechts:
FW 9.0 PCB 19.5/H1/E1 also PCB 19.5
Bei der neuen (V9.1):
FW 9.1 PCB 19.4/H1/E1 also PCB 19.4
Wieso ein "Downgrade" von PCB 19.5 auf PCB 19.4
und ein "Upgrade"
von V9.0 auf V9.1?

Hi folks,

The soldering iron has cooled down and I've what looks like a working BLUE 9.1  

So, first question, how do I rename my station from "Station XYZ" to something more meaningful - I can't find it on the BLUE Web interface or the lighteningmaps.org pages??? 

Chat soon.

Hi i'm putting up a red system with loop antennas (shielded)

Stuff seem to work ish but i get a really low signal. amplification don't seem to change from either pot or from controller

looking at noise floor on different amplifications.

32x32
   

1x1
   

leds on amp board light up as they should when using pot on amp board(disconnected from comtroller). controller also gets the amp level(if using controller and use pot checked) and shows right values on display.

could it be the mcu on the amp board thats faulty and don't sen the right data to the programmable amps. checked all solders under microscope and it looks perfect.

i have an oscilloscope so i can dive in and look at data and such.

any ideas?  saw some other forum post about a mcu on the amp board that had gone wrong and needed replacement. similar problems.

Station id 2265

Hi,

When I search, I do not see the lightning strikes on the map.

Still, the search works since the result indicates 228 impacts.

Look at the Screenshot below.

How to solve this problem?


Alexandre.

Hi all, 

I am posting here because I tried to get in touch with Blitzortung but didn’t manage. I am working for a company which owns and operates wind and solar farms. I am an operation supervisor there. I am looking for a solution to detect lightning around our assets in order to protect the people who intervene on the machines. I would thus need to access a real time lighting database. The goal is not to sell anything, only to create alerts to guarantee the safety of the workers on our sites.

Do you think that this use could be aligned with the policy of Blitzortung? We are open on the form (eventually and if it’s necessary to have access to the data we could develop an open platform of alerts using Blitzortung data), and on the way we can participate (from installing detectors to a financial participation).

Thank you for your answers!

The lines for streets and thunder fronts are very thick. I think they used to be (and should be) finer some time ago.

I noticed that some lightning strikes that are displayed on lower zoom levels disappear when zooming in.

browser: chrome 68.0.3440.84 (Offizieller Build) (64-Bit)

Google Maps wird nicht mehr akzeptiert. Es bedarf dringend eine Änderung z.B. auf openstreetmap oder das System kann eingestellt werden. Klingt hart, aber Fakt.

Hi there,

I recently noticed that I am no longer able to access historical lightning data by zooming into specific locations (in North America, for example). Is there a reason why this feature was removed (or has it been relocated)? It used to be that you could freely zoom in to a location of interest using Google Maps on Lightning Maps.org with the historical lightning data overlain based on the time frame specified, which couldn't exceed 12 hours. However, that seems to be no longer there, or I am perhaps just overlooking it. If it is still there, could you please show me how to get there (via link)?

Thanks, and I would appreciate any assistance.

~Trav.~ 

I am seeing one-hour gaps in the history at the same time every day on the Historical Maps. Run the map for 1 hour up to 00:55 and then up to 00:100 UTC on any of the dates below, or the current date. At 00:55, I see no white, yellow or light orange data (sferics within 20, 40 or 60 minutes). At 01:00, sferics for the past hour reappear along with new ones, which is evidence that the data was gathered but was and is somehow held back from the subsystem that underlies the Historical Maps.

It is clear from the regular clock times, calendar dates and global reach that this is some kind of service or developer issue and not a natural phenomenon.

My comment is that many users will be mystified or may misinterpret the data, like dusanfrode (see below), who said, "thunder stopped/slowed down at exact same time all over the world."

My questions are:
1. What was the reason for these data dropouts on the first day of each month, and the periods late October 2016 to late March 2017, and late October 2017 to now?
2. Why were they always at 00:00 (or 23:55) to 00:55 (or 01:00) UTC, and on the 1st of the months?
3. Does the community intend to accept for these to continue indefinitely?

I am a newly registered user. I have searched but found no reference to this specific topic in the Public Forums (one exception below). Apologies if there is an answer in another thread.

Detailed timeline of the occurrences:
The first date I can access the Overview Map is 06:00, 12 November 2015. Since that time, the phenomenon has taken place on the following dates, in the 55-minute or 1-hour period up to 00:55 or occasionally 01:00 UTC, worldwide:
1 July 2016
1 Aug 2016
1 Oct 2016

31 October 2016 to 26 March 2017
1 April 2017
1 May 2017
1 June 2017
1 July 2017
1 August 2017
1 September 2017
1 October 2017
30 Oct 2017 onwards to 29 July 2018 (today).

This was referenced in thread https://forum.blitzortung.org/showthread.php?tid=1672
"The hole [sic] world at the same time" started by dusanofrode.
DelandeC said then, "Unfortunately there has been a network outage in the datacenter yesterday."
Egon provided a GIF showing 2016-04-05 09:00 to 2016-05-05 09:00 UTC, which showed the outage at 2016-04-04 13:25 to 14:25.
The difference was that that was a one-off outage at an arbitrary time of day. Interesting, though, that it seems to have been 1 hour in length.h

read
The hole world at the same timeTh