|
Post by triggerfish on Apr 2, 2019 10:35:56 GMT -8
!!!Frustrating!!! At first detecting lightning, now the flashes are like new-years firework overhere, but the GWP keeps insisting there is no lightning anywhere And lightning was what I wanted to see in the frist place I have no clue when it started getting deaf I can no see eny error in the loggin, so any suggestions on where to look for this deafness is more than welcome.
|
|
|
Post by SDL on Apr 2, 2019 12:05:40 GMT -8
OK. First things first. Do you have a simulator? If not, shut down GWP and run the testAS3935.py code to simplify things. Then see what is reporting.
There are a bunch of parameters that you can change. Could be either too noisy or gain set to low. Here is a video that talks about tuning:
BP
|
|
|
Post by triggerfish on Apr 5, 2019 2:15:08 GMT -8
Waiting for something that looks like lightning...
And waiting, and waiting, and waiting...
I do have the lightning simulator you sell. I have been firing that on a regular basis, without getting registered. Eventually set that to random automatic. I've been sparking batteries, using cell phones, dug up an old device know to cause massive em-interruptions, without anything getting noticed by the detector.
I have seen the video before, but I have no clue where to set he variables mentioned.
|
|
|
Post by SDL on Apr 5, 2019 8:58:43 GMT -8
Peter,
It never triggers? Not even saying it is detecting noise?
You should see the white LED flicker (it stays on until the Interrupt is read) when you have an interrupt.
The code for some of the variables John talks about is in testAS3935.py (and is similarly found in GroveWeatherPi.py) around line 62:
sensor.set_indoors(True) sensor.set_noise_floor(0) sensor.calibrate(tun_cap=0x0F)
|
|
|
Post by triggerfish on Apr 6, 2019 0:31:42 GMT -8
Peter, It never triggers? Not even saying it is detecting noise? You should see the white LED flicker (it stays on until the Interrupt is read) when you have an interrupt. The code for some of the variables John talks about is in testAS3935.py (and is similarly found in GroveWeatherPi.py) around line 62: sensor.set_indoors(True) sensor.set_noise_floor(0) sensor.calibrate(tun_cap=0x0F) Will have a look when I'm home again. Thanx so far.
|
|
|
Post by triggerfish on Apr 12, 2019 7:06:42 GMT -8
Peter, It never triggers? Not even saying it is detecting noise? You should see the white LED flicker (it stays on until the Interrupt is read) when you have an interrupt. The code for some of the variables John talks about is in testAS3935.py (and is similarly found in GroveWeatherPi.py) around line 62: sensor.set_indoors(True) sensor.set_noise_floor(0) sensor.calibrate(tun_cap=0x0F) Will have a look when I'm home again. Thanx so far.
Pfew... What white LED should I be seeing? The detection unit is encased inside the pillar and not visible to me.
I found the settings described. Floor was set to 0 and tun_cap to 0x0F, which as i understand are the "deafest" settings ? I set them to 3 and 2 and will let it run for a while. The simulator still is not detected. I seem to remember there also was a setting ignoring those signals, but I can not find that anymore.
|
|
|
Post by SDL on Apr 13, 2019 10:09:59 GMT -8
It's a White light on the Lightning Detector. When an interrupt has happened, the LED turns on until the processor clears it.
BP
|
|
|
Post by triggerfish on Apr 18, 2019 4:54:56 GMT -8
It's a White light on the Lightning Detector. When an interrupt has happened, the LED turns on until the processor clears it. BP Gonna get me a transparent sensorbox to replace the closed one. To be continued.
|
|
|
Post by triggerfish on May 22, 2019 12:50:45 GMT -8
My colleague printed a transparent hood which now shows me, the led i=on the detector burning permanently???
|
|
|
Post by doxidad on May 23, 2019 6:54:40 GMT -8
My colleague printed a transparent hood which now shows me, the led i=on the detector burning permanently??? That happens to me once in awhile. It's like the interrupt is never handled/missed by the Pi. Of course the only way to fix it is to restart the application.
|
|
|
Post by SDL on May 24, 2019 9:17:48 GMT -8
This is odd. I have never experienced this with our GWP systems and then run for months.
Is this custom software or out of box?
BP
|
|
|
Post by doxidad on May 28, 2019 4:47:04 GMT -8
This is odd. I have never experienced this with our GWP systems and then run for months. Is this custom software or out of box? BP This is out of the box GWP software. Doesn't happen frequently, but does happen.
|
|
|
Post by triggerfish on May 28, 2019 9:06:48 GMT -8
I only added a daily reset of the total rain, but the rest is out of the box.
|
|
|
Post by triggerfish on May 28, 2019 9:24:20 GMT -8
I only added a daily reset of the total rain, but the rest is out of the box. In the main loop of the program the following code resides:# process Interrupts from Lightning if (as3935Interrupt == True): Where, when and how is that boolean set?
|
|
|
Post by SDL on May 28, 2019 11:01:18 GMT -8
Hi Peter,
In GroveWeatherPi.py, there is an interrupt service routine that if called (by the interrupt on the pin coming from the ThunderBoard) it sets the flag which is then picked up later in the main loop.
def handle_as3935_interrupt(channel): global as3935Interrupt
print "as3935 Interrupt"
as3935Interrupt = True
# define Interrupt Pin for AS3935 as3935pin = 16
#GPIO.setup(as3935pin, GPIO.IN) GPIO.setup(as3935pin, GPIO.IN,pull_up_down=GPIO.PUD_DOWN) GPIO.add_event_detect(as3935pin, GPIO.RISING, callback=handle_as3935_interrupt)
|
|