Hello,
my close friend sent me one of his stations (System Blue, ID 2891). Now I am the new owner, and the station is installed at a new location in another city.
At this new location, the station covers distant forest areas of Siberia that were previously not monitored.
One issue I have noticed: it seems that my station’s signals are not being taken into account by the server, even though it is shown as active on the map and clearly detects lightning strikes correctly.
I have also updated the station to FW 11.0b3.

user id = 2463
station id = 2891
region = Ozeania1, Asia1, Japan1, Japan2

Attached Files

Thumbnail(s)
           

I’ve spent the last couple weeks in Thailand, particularly Pattaya area And there seems to be a huge hole in detection over the Gulf of Thailand. Sitting on the beach looking west almost nightly, you can see cloud to cloud lightning Which could be very far because there is no sound But on the map, even 500 miles away there are no hits. Furthermore, almost daily there is cloud to ground strikes with no hit.

Hello everyone,
I am curious if placing the Blitzortung device in a dense urban area (many tall buildings, dense electrical system, strong interference) has a significant impact on the accuracy or sensitivity of lightning detection. Does the urban environment cause greater errors than placing the device in a rural or suburban area?
Has anyone on the forum tried to compare data between these two environments?

Hallo in die Runde,

ich bin vor ein paar Wochen von Oberhausen, NRW, Germany, in den Kreis Wesel umgezogen und finde an meinem neuen Wohnsitz keinen Ort, an dem ich mein System Blue (Station-ID 1504) platzieren kann ohne Störeinflüsse und den GPS-Empfang zu gewährleisten. Deshalb habe ich mich dazu entschlossen, meinen Blitzorter abzugeben. War eine schöne und nette Möglichkeit und Zeit und hat mich einiges gelehrt.

Die Station (Inbetriebnahme wohl 2016) ist in dem passenden Alu-Gehäuse. Die Ferrit-Stäbe sind auf einem Sperrholzbrett befestigt. Der GPS-Empfänger hat den Y2K-Bug, aber der wird durch die Firmware weggerechnet. Sie hat bis zur Rettung vor dem Hausentrümpler ihre Dienste getan, funktioniert also.

Ich würde Abholung bevorzugen, Versand in DE würde ich sonst mit 8,-- EUR veranschlagen. Vorstellungen zum Preis habe ich keine, ich setze aber mal zunächst 70,-- EUR VS (zzgl. Versand) an. Angebote bitte per PM und nicht hier im Thread.

Danke schon Mal
Thomas

Whenever I see a flash of lightning, I always start counting seconds until I hear thunder, to estimate distance.
Is this common among the Blitzliebhaber or Blitzenangsthaber here at Blitzortung?

I can now do this a different way with Blitzortung maps. I am staying temporarily in an area that has thunderstorms every afternoon: this is common in mountainous areas with summer monsoon rain. I'm working inside, and I can't see lightning flashes, but when I hear thunder, I open the dynamic map at Blitzortung.org, center my position in it, and then zoom in as close as possible.

On another screen, I bring up google maps, and measure the distance from the center of the Blitzortung dynamic map to its edges. With this distance in mind, I start to watch the lightning map. 

When I see new lightning strikes on the map, I start counting seconds, starting with the instantaneous delay I see on the map, until I hear thunder, and very often the time/distance corresponds well with that closest lightning strike that triggered the counting. I can often hear approximate azimuth when the thunder arrives, as well.

Sometimes I have to stop counting seconds when the time/distance would place the lightning strike off of the Blitzortung map.

Perhaps half the time there is thunder but no Blitzortung strike. I suspect that these are often IC (Inter-Cloud) strikes, which Blitzortung does not locate (for more reasons other than just their non-vertical polarization).

       
As the subject: the menus on the right side of the web map can't be used on Firefox (142.0.1 64-bit). 

On mouse-over, the menus open, but they close as soon as the mouse leaves the menu icon.

Hello, station 3212 here.

Could I kindly have my status updated to 'participant'?

I have been tuning over the past few weeks, and think I have things mostly dialed in. Things appear stable, but will continue to play with things.

I think the question I have for the moment is why the website only shows one antenna input when I have confirmed that the station appears to be participating in stroke location with either of the inputs disabled at the amplifier. Both inputs appear to be functioning fine with regard to signal detection on the local interface, detecting strokes, and uploading to the server.

I have attempted to search the forum, for solutions, but perhaps I will be able to glean more info after user enablement, as some posts appear to not be readable by my account in the current state.

Any insight?

Kind thanks, and happy to be participating!

Hi everyone,
I’ve recently set up my Blitzortung station, and it seems to be working fine overall, but I keep noticing that my station often shows “too many pulses” and gets flagged with poor signal quality on the LightningMaps status page.
A few things I’m unsure about:

• Is this usually caused by incorrect antenna placement (too much local noise), or could it be a configuration issue in the controller?
  
• Would adjusting the gain settings help reduce the number of invalid pulses without missing actual strikes?
  
• Is there a recommended way to identify the main source of local interference?
  

Hello

I moved my station and on blitzortung everything looks right but not on lightningmaps, wrong info and location. Something i need to do?

The station in question is  2718

Just stumbled on this card to use in a Home Assistant page.  It can be installed via HACS or manually
This is the GIT page : https://github.com/timmaurice/lovelace-b...me-ov-file

It will show the detections of your station on a little map and some counts