rlee171
New Member
Posts: 12
Raspberry Pi: Yes
|
Post by rlee171 on May 13, 2021 10:29:53 GMT -8
I am attempting to use a Thunder Board attached to a I2C 4 Channel Mux Extender as recommended. I have two questions.
1) One of the Grove connectors on the Thunder Board has the Interrupt. The opposite end of the cable has no where to plug into on the Mux board. I have been able to successfully insert a male jumper cable into the end of the grove connector for the interrupt. Should it go directly into pin 16 of the Pi as the code calls for or to the interrupt pin on the Mux board and from the Mux board to pin 16 of the Pi?
2) When I run the 'demo.py' code I receive: 'Thunder Board present at address 0x02' 'Waiting for Lightning - or at least something that looks like it'
Great, no errors!
The LED goes off at this point as expected. When I move the detector close to the Pi it turns back on indicating that a disturber or noise has been detected. However nothing is displayed in the terminal window to indicate this. Also the LED on the Mux board does not blink to indicate activity as it does when I have used other devices on the Mux board (I have everything else disconnected attempting to troubleshoot this issue).
Thinking that this is a demo code and the board has connectivity I attempted running the SDL_ThunderBoard_AS3935.py. No errors are displayed, but it just immediately goes back to a prompt indicating that the code is not running and the interupt LED on the Thunder Board is on continuously. With no errors to diagnose I am at a loss as to why the code doesn't run and the LED stays on. It does go off as I said only when running the demo code.
The GitHub page shows that the primary file was updated 6 months ago.
If someone would point me in the right direction it would be much appreciated.
Ralph
|
|
|
|
Post by SDL on May 13, 2021 10:48:31 GMT -8
Post a picture of your setup. The Interrupt line would go to a data port on the Raspberry Pi (Pi2Grover board).
I would say you don't have the interrupt set up. You would be much better off with a Pi2Grover board to connect all this in.
BP
|
|
rlee171
New Member
Posts: 12
Raspberry Pi: Yes
|
Post by rlee171 on May 13, 2021 11:53:20 GMT -8
I purchased the Mux from a recommendation on your website.
|
|
rlee171
New Member
Posts: 12
Raspberry Pi: Yes
|
Post by rlee171 on May 13, 2021 11:57:08 GMT -8
This is from the Thunder Board page.
|
|
|
|
Post by SDL on May 13, 2021 14:46:50 GMT -8
Correct. It will work, but we really recommend using the PI2Grover to get the wiring and levels right. Hard to say if you have wired it correctly from your pictures.
Check your wiring and voltage levels carefully. There should be no 5Vs anywhere in your system if you are using jumper cables. 5V will blow your Raspberry Pi Inputs.
BP
|
|
rlee171
New Member
Posts: 12
Raspberry Pi: Yes
|
Post by rlee171 on May 13, 2021 15:11:14 GMT -8
Every thing is running at 3.3 volts. I don't know what is not clear in the picture, the Mux is wired correctly with jumpers to the 3.3 V (pin 1) Ground (pin 6) SDA (pin 3) and SCL (pin 5) and the Interrupt (pin 16 as the code calls for). If there is another pin I should try for the Interrupt and change the code I am open to suggestions.
I suppose I should just order the PI2Grover as you suggest, however I humbly suggest you remove the link to the suggested 4 channel I2C mux reference and link on your Thunder Board page as that is why I purchased it in the first place.
Regards,
Ralph
|
|
|
|
Post by SDL on May 14, 2021 9:20:15 GMT -8
What does "sudo i2cdetect -y 1" show? That will tell you if the MUX is there. Then you can run the MUX test code to see what is on each of the mix segments.
BP
|
|
rlee171
New Member
Posts: 12
Raspberry Pi: Yes
|
Post by rlee171 on May 21, 2021 12:15:30 GMT -8
Post a picture of your setup. The Interrupt line would go to a data port on the Raspberry Pi (Pi2Grover board). I would say you don't have the interrupt set up. You would be much better off with a Pi2Grover board to connect all this in. BP BP,
I have received the Pi2Grover board. I have connected the I2C connector on the Thunder Board to an I2C input on the Grover board, and the Interrupt connector on the TB to D16/19 (and have also tried D13/D16)on the GB.
When I run demo.py I reveive the following.
pi@raspberrypi:~/SDL_Pi_ThunderBoard_AS3935 $ python demo.py
Thunder Board present at address 0x02
Thunder Board present at address 0x03
pi@raspberrypi:~/SDL_Pi_ThunderBoard_AS3935 $
Suggestions?
|
|
|
|
Post by SDL on May 23, 2021 5:43:44 GMT -8
Rlee,
What is really weird is that you are picking up the ThunderBoard at two different addresses. Please send a picture of your hookup.
I'm now starting to think you might have a bad ThunderBoard.
BP
|
|
rlee171
New Member
Posts: 12
Raspberry Pi: Yes
|
Post by rlee171 on May 23, 2021 11:00:45 GMT -8
BP, Here is a pic of how it is hooked up. The cables are off screen due to being 50cm in length as recommended.
|
|
