Post by triggerfish on Jun 4, 2019 22:24:48 GMT -8
Wow!!!
Since the transparent hood was mounted, I could see the LED kept on, after triggering for the first time, without reporting lightning... The test program did not show anything either... This evening we had massive thunderstorms with lightning, so I stood outside looking at he box. On one of the pcb's inside (not sure which one) a LED blinked with each strike... So obviously the detector detects something... Browsing through the test code I found a pin assignment for the detector. It was assigned to 16... I randomly put in another number, without any result. Then I looked at the cable description in the instructions and found the detector was connected to the Pi2Grover / D13/D16 port... So I assigned 13 to the pin and ran the test... BINGO!!! Lighting was detected... So... Where did it all go wrong? Why is the software assuming pin 16 and the hardware is on pin 13?
Anyway... My system is detecting lightning now... I probably have to tune things again after changing values. I get a lot of Spurious interrupts, but between them, a lot of lightning!
Since the transparent hood was mounted, I could see the LED kept on, after triggering for the first time, without reporting lightning... The test program did not show anything either... This evening we had massive thunderstorms with lightning, so I stood outside looking at he box. On one of the pcb's inside (not sure which one) a LED blinked with each strike... So obviously the detector detects something... Browsing through the test code I found a pin assignment for the detector. It was assigned to 16... I randomly put in another number, without any result. Then I looked at the cable description in the instructions and found the detector was connected to the Pi2Grover / D13/D16 port... So I assigned 13 to the pin and ran the test... BINGO!!! Lighting was detected... So... Where did it all go wrong? Why is the software assuming pin 16 and the hardware is on pin 13?
Anyway... My system is detecting lightning now... I probably have to tune things again after changing values. I get a lot of Spurious interrupts, but between them, a lot of lightning!
pi@IBADHOEV14:~/SDL_Pi_GroveWeatherPi $ gwpgrep "Lightning Detected" | grep -v blynk
PHDEBUG Last Interrupt = 0x8: Lightning Detected 1km away. (21:54:46 - 2019/06/04)
PHDEBUG Last Interrupt = 0x8: Lightning Detected 1km away. (21:54:48 - 2019/06/04)
PHDEBUG Last Interrupt = 0x8: Lightning Detected 1km away. (21:54:53 - 2019/06/04)
PHDEBUG Last Interrupt = 0x8: Lightning Detected 1km away. (21:54:57 - 2019/06/04)
PHDEBUG Last Interrupt = 0x8: Lightning Detected 1km away. (21:55:00 - 2019/06/04)
PHDEBUG Last Interrupt = 0x8: Lightning Detected 1km away. (21:55:08 - 2019/06/04)
PHDEBUG Last Interrupt = 0x8: Lightning Detected 1km away. (21:55:21 - 2019/06/04)
PHDEBUG Last Interrupt = 0x8: Lightning Detected 1km away. (21:55:26 - 2019/06/04)
PHDEBUG Last Interrupt = 0x8: Lightning Detected 1km away. (21:55:31 - 2019/06/04)
PHDEBUG Last Interrupt = 0x8: Lightning Detected 1km away. (21:55:38 - 2019/06/04)
PHDEBUG Last Interrupt = 0x8: Lightning Detected 1km away. (21:55:40 - 2019/06/04)
PHDEBUG Last Interrupt = 0x8: Lightning Detected 1km away. (21:55:44 - 2019/06/04)
currentAs3935LastStatus = Lightning Detected 1km away. (21:55:44 - 2019/06/04)
PHDEBUG Last Interrupt = 0x8: Lightning Detected 1km away. (21:55:55 - 2019/06/04)
PHDEBUG Last Interrupt = 0x8: Lightning Detected 1km away. (21:55:59 - 2019/06/04)