|
|
Post by jrwilling on Jul 27, 2019 12:46:58 GMT -8
While so far my unit is generally operating well, I am seeing a similar issue with lightning reporting. The unit will get in a "mood" and start sending alerts "Lightning Detected 1km away" every 30-60 seconds. Currently in the area, it is 90 degrees with clear skies. Radar maps show the closest possible storm activity over 150 miles away. So, what should I be looking for in order to correct this?
SkyWeather v039 BTW
|
|
|
|
Post by SDL on Jul 29, 2019 8:58:10 GMT -8
The Lightning sensor needs to be tuned to your local electromagnetic environment. Distrubers are everywhere!
There is some real science that needs to be done regarding the local sensor. To give you an idea on to do this process will be, take a look at John's talk about tuning the ThunderBoard.
BP
|
|
|
|
Post by jrwilling on Jul 30, 2019 9:56:41 GMT -8
Would be a more useful response if it actually addressed the SkyWeather unit rather than the stand along lightning detector. And presuming that users of the SkyWeather unit will just happen to have an Arduino lying about and want to pull their SkyWeather unit down and take it apart in order to accomplish this "tuning" is a bit of a stretch.
While I do not really want to jump on the bandwagon of KickStarter backers (of which I was one) lamenting the shortcomings of this product, the failure to provide an integrated method for tuning of a detector which is known to have issues in high noise environments seems like a rather gross oversight on someone's part. And using the excuse that the Raspberry PI OS is a difficult environment to provide such a facility in seems somewhat disingenuous when the entire SkyWeather product was designed around it's use.
The initial question might have been better answered with an indication of where in the SkyWeather code the detector is setup and the parameters could be adjusted rather that just pointing at a preexisting, largely unrelated video.
|
|
|
|
Post by SDL on Aug 2, 2019 14:02:08 GMT -8
Point taken. Tuning this unit is not easy. Tuning does not just mean setting the center frequency but the other parameters too.
We will produce a blog posting addressing this very question. The environments which people put these detectors in is all over the map and where you build it and put it are really two different tuning setups.
We provided a method in OurWeather for setting the tuning parameters and people have had less issues with that. We will add it into the config file for SkyWeather.
Thanks again!
BTW, about 70% of users seem to have no problem with the defaults, but we are still learning how to support this product in the jungle!
BP
|
|
|
|
Post by jrwilling on Aug 7, 2019 7:20:15 GMT -8
Thanks, that should help. I do note that in the new blog post the values for the "Indoor / Outdoor Selection" argument are not defined in the text. Taken at face value, on might expect that having the "Indoor" variable set to "1" (the default in the example given) indicates that the unit is operating in "Indoor" mode. Is this correct?
And then that changing the value to "0" would set the unit to "Outdoor" mode?
|
|
|
|
Post by jrwilling on Aug 7, 2019 7:34:40 GMT -8
Allowable values and their meanings for the "DisturberDetection" argument are not defined in the blog text either...
|
|
|
|
Post by Powderjockey on Aug 7, 2019 10:22:53 GMT -8
(11676.633600000001, 6301, 2097)
()
('Pi Camera Revision', u'ov5647')
('after bme680', True)
Traceback (most recent call last):
File "SkyWeather.py", line 637, in <module>
NoiseFloor = config.AS3935_Lightning_Config[0]
AttributeError: 'module' object has no attribute 'AS3935_Lightning_Config'After upgrading to version 042 I'm getting this error.
Nothing has changed in the box.
|
|
|
|
Post by jrwilling on Aug 7, 2019 10:52:22 GMT -8
After upgrading to version 042 I'm getting this error.
Nothing has changed in the box.
There are additional lines that have to be added to the conflocal.py file. Check the new README.md file. |
|
