kw123
New Member
Posts: 5
|
Post by kw123 on Jun 12, 2018 20:11:06 GMT -8
Have thunder board # 0240110317-01 . That should be preconfigured as i2c = 0x03.
I am struggling to get it running
It is on an RPI3, other sensors work fine on that RPI all removed for this.
Connected V3.3 ground SDA, SLC, int pin, Added 2 pull-up resistors (1.2k) for i2c sda and slc to +3.3V
The white led on the board is blinking - not regular on/off but sometimes -- I guess that means the front part is detecting some signals.
BUT No i2c visible with i2cdetect -y 1:
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
it seems that AD0 pin is connected to ground and AD1 is open (that should be i2c address x01) - with the default AD0 = AD1 = 1 they both should be connected to V3.3 for address 0x03?
Any advice?
Karl
ps I have different sensors running ~ 50 on 20 RPI = this is not my first board
|
|
kw123
New Member
Posts: 5
|
Post by kw123 on Jun 13, 2018 9:06:33 GMT -8
also tried w/o pull up and with 5.6K
Also added another sensor to i2c ( BME280 at 0x76). That works fine in parallel to thunderboard. So it is not the bus, not the resistors..
really at a lost what else I can do .
Karl
i2cdetect -y 1:
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- 76 -- <== this is the BME280
|
|
|
|
Post by SDL on Jun 15, 2018 11:25:02 GMT -8
The Raspberry pi does not detect address 0x02 using i2c detect. I'm not sure which Thunderboard you have. Would you post a close up picture? Then we can figure out what is going on.
Have you tried running the demo software? Does that pick up the Thunderboard?
|
|
kw123
New Member
Posts: 5
|
Post by kw123 on Jun 16, 2018 18:38:03 GMT -8
I bought another board . There was the option to connect SI to V+3.3 to enable i2c Then the I2c channel showed up at THAT board The thunder board does not have the option to enable/disable i2c. Anyway here board #0240110317-01 as posted It is not a question of using any software, if i2c does not show up NO software will do anything. here the pic: www.dropbox.com/s/hjeiqsshxrj4ge8/Screen%20Shot%202018-06-16%20at%2021.34.45.png?dl=1V+ -- V+ 3.3 gnd -- gnd sda -- sda slc -- slc int -- gpio17 + 2 resistors V+ to sla, sld - tried no resistor, 1.2k, 5k 10k thanks for the advice |
|
|
|
Post by SDL on Jun 16, 2018 18:46:38 GMT -8
OK, but here is the deal. The Raspberry Pi i2cdetect is not infallible. It sometimes will not pick up the AS3935 (it's got a few weird quirks) but the software we wrote (the Demo software for the Pi) will always pick it up if it was there.
Thank you for the picture. That board is programmed to turn up on 0x02. It is a reworked board. We had to do that in order to fix the detection of the board on the Raspberry Pi Zero.
So, given that, the i2cdetect will NOT pick up the ThunderBoard. Run the demo software to see if it is picked up.
Best,
BP
|
|
kw123
New Member
Posts: 5
|
Post by kw123 on Jun 17, 2018 9:17:22 GMT -8
OK, but here is the deal. The Raspberry Pi i2cdetect is not infallible. It sometimes will not pick up the AS3935 (it's got a few weird quirks) but the software we wrote (the Demo software for the Pi) will always pick it up if it was there. Thank you for the picture. That board is programmed to turn up on 0x02. It is a reworked board. We had to do that in order to fix the detection of the board on the Raspberry Pi Zero. So, given that, the i2cdetect will NOT pick up the ThunderBoard. Run the demo software to see if it is picked up. Best, BP with i2c = 2 it works Karl |
|
|
|
Post by SDL on Jun 17, 2018 12:13:12 GMT -8
Karl,
You Rock!!!!!
BP
|
|
|
|
Post by [email protected], Eirikur on Aug 26, 2018 11:52:14 GMT -8
I have the same recent thunder board type 0240110317-01 as the original poster.
I made a colossal goof and connected my Qwiic to Grove adapter cable to the left hand or "digital" connector instead of the I2C.
I'm now connected to the right hand connector, marked as I2C. I found no response to i2cdetect.
I think I might have fried the Thunder board.
By using the -a option to i2cdetect, I detect something at address 0x02 when the Thunder Board is plugged in, but not when it is disconnected. That's a positive sign, but the board does not work with the demo software, it's not detected.
I'm running the latest Raspbian on the latest Pi 3+ board. I do not see any LED lighting.
Is there hope? Do I just order a replacement board?
Thanks,
Eirikur
|
|
|
|
Post by SDL on Aug 26, 2018 13:16:55 GMT -8
Eirkur, Great use of the -a option. And while it is sad, I believe there is no hope and you have terminated your Thunder Board. We keep a box of death for such tragedies.  BP  |
|
