Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
en:support:faq [2018/10/14 18:10]
gerbold [Why do we need a GPS?]
en:support:faq [2018/11/09 02:13] (current)
rbeerster Correct server minor typos
Line 74: Line 74:
 ===== How do I access the system interface? ===== ===== How do I access the system interface? =====
  
-Check whether the host name blitzortung is known in your network: in a shell use the command 'ping blitzortung'​. If thgis works, type into your web-browser http://​blitzortung/​. As an alternative check your router to identify the IP address of the blitzortung controller.+Check whether the host name blitzortung is known in your network: in a shell use the command 'ping blitzortung'​. If this works, type into your web-browser http://​blitzortung/​. As an alternative check your router to identify the IP address of the blitzortung controller.
  
 ===== How to configure for the very first time? ===== ===== How to configure for the very first time? =====
Line 81: Line 81:
  
 First, put the station in Manual Mode..,. Automatic will drive the gains up and down, and you can cycle in and out of interference.\\ First, put the station in Manual Mode..,. Automatic will drive the gains up and down, and you can cycle in and out of interference.\\
-Make Sure your antennas and amp are NOT near noise sources.... ​ Make sure you have a good power supplly... +Make Sure your antennas and amp are NOT near noise sources.... ​ Make sure you have a good power supply... 
  
 then...\\ then...\\
Line 90: Line 90:
 We've two types of junk we're looking at... "​always there",​ and "​Sporadic"​...\\ We've two types of junk we're looking at... "​always there",​ and "​Sporadic"​...\\
 Now, the "​always"​\\ Now, the "​always"​\\
-adjust thresholds first, then / or gain for that channel so that the '​always'​ noise DOES NOT trigger a signal...and apply / save.  Try to accomodate ​gains so that you can keep the standard threshold at 100MV if possible. ​ You may then adjust it later on a specific channel... ​ Now your '​ambient'​ always present sources shouldn['​t trigger anything... Call this Baseline #1\\+adjust thresholds first, then / or gain for that channel so that the '​always'​ noise DOES NOT trigger a signal...and apply / save.  Try to accommodate ​gains so that you can keep the standard threshold at 100MV if possible. ​ You may then adjust it later on a specific channel... ​ Now your '​ambient'​ always present sources shouldn['​t trigger anything... Call this Baseline #1\\
 Then...\\ Then...\\
-**Ideally**,​ you want to operate so that the WORST sporadic interference doesn'​t trigger a signal. You're still in absolute manual, ​withf the optional filters off.  That should put you into '​ambient'​ operation Baseline #2... while doing this, keep your threshold at least twice what the ambient 'noise grass' (no signal) level may be.+**Ideally**,​ you want to operate so that the WORST sporadic interference doesn'​t trigger a signal. You're still in absolute manual, ​with the optional filters off.  That should put you into '​ambient'​ operation Baseline #2... while doing this, keep your threshold at least twice what the ambient 'noise grass' (no signal) level may be.
  
 If you have an obvious noise source at , say 150kHZ, you could adjust the optional filter to cut off at about 130-140 kHz... you'd monitor each channel, for a period of time, diurnally, weekends, etc... and gradually fine tune these settings.... ​ Now, what you determine this week, may change in July... or November... simply because the total environment changes... If you have an obvious noise source at , say 150kHZ, you could adjust the optional filter to cut off at about 130-140 kHz... you'd monitor each channel, for a period of time, diurnally, weekends, etc... and gradually fine tune these settings.... ​ Now, what you determine this week, may change in July... or November... simply because the total environment changes...
Line 334: Line 334:
 ===== What are these funny wiggles before/​after my signals? ===== ===== What are these funny wiggles before/​after my signals? =====
  
-Compression ​artefacts.\\ +Compression ​artifacts.\\ 
-In order to save bandwidth the analog signal is (optionally) compressed before ​sendig ​it to the Blitzortung server. This compression is lossy. The server "​restores"​ the noise as a certain number of samples with a min and max level as zigzag.+In order to save bandwidth the analog signal is (optionally) compressed before ​sending ​it to the Blitzortung server. This compression is lossy. The server "​restores"​ the noise as a certain number of samples with a min and max level as zigzag.
  
 If the data compression is enabled... you won't see it on your local signals page, but it is often visible on your station signals page on the server, if the feature is being '​shown'​... it looks like a series of 'hash marks' or '​interference'​ obscuring portions of you '​server'​ displayed signal... that data is 'not used'. If the data compression is enabled... you won't see it on your local signals page, but it is often visible on your station signals page on the server, if the feature is being '​shown'​... it looks like a series of 'hash marks' or '​interference'​ obscuring portions of you '​server'​ displayed signal... that data is 'not used'.
Line 376: Line 376:
 to time to improve the system and to add new features. If you have own suggestions,​ then you are to time to improve the system and to add new features. If you have own suggestions,​ then you are
 welcome to tell us about them, so we could integrate them in the next release. SMD versions of the welcome to tell us about them, so we could integrate them in the next release. SMD versions of the
-PCBs are available with System ​BLue.+PCBs are available with System ​Blue.
  
 ===== Is it possible to build such a hardware with RaspberryPi,​ Arduino or similar? ===== ===== Is it possible to build such a hardware with RaspberryPi,​ Arduino or similar? =====