Post by N8MDP on Aug 8, 2021 11:17:06 GMT -8
I have a Thunderboard as part of a total GroveWeatherPi system that I deployed two months ago. The system is deployed in my storage barn that gets cool and warm, sometimes hot these days. There is a window that is right next to the system to at least keep air coming into the barn. For the most part, it stays cool in the barn. Everything was working just fine until a few days ago. Now it appears that the Thunderboard is no longer recognized by the system. I run my variant of the GroveWeatherPi software but it always shows the detector is not present. I've run the the demo.py software and it comes back and says:
Traceback (most recent call last):
File "/home/pi/SDL_Pi_GroveWeatherPi/RaspberryPi-AS3935/demo.py", line 13, in <module>
sensor = RPi_AS3935(address=0x02, bus=1)
TypeError: 'module' object is not callable
On the GroveWeatherPi software, I get a remote I/O error around the code that executed:
###################################
# ad3935 Set up Lightning Detector
###################################
if (config.Lightning_Mode == True):
# switch to BUS1 - lightning detector is on Bus1
if (config.TCA9545_I2CMux_Present):
tca9545.write_control_register(TCA9545_CONFIG_BUS1)
as3935 = RPi_AS3935(address=0x02, bus=1)
try:
as3935.set_indoors(True)
config.AS3935_Present = True
print ("AS3935 Lightning Detector present")
The error occurs when the as3935.set_indoors(True) is executed
I tried an experiment attaching the I2C cable from the Thunderboard directly to the Pi2Grover board. The demo.py software throws the same error as above but the GroveWeatherPi software detects that the board is present. Normally the Thunderboard I2C is connected to the I2C 4-Channel Mux board connector J3 The Mux board has a grove cable connected from J2 to a I2C expander board and a cable from J1 to an I2C cable on the Pi2Grover board. This is why I attached the Thunderboard to the Pi2Grover board to see if maybe the Mux board may have gone bad.
So a couple of questions:
1. Can excessive heat in my barn damage the Thunderboard or the Mux board?
2. What are some other failure modes for the Thunderboard?
3. What can be done to determine if the board has indeed gone bad.
I'll continue to debug and reconnect the Thunderboard to the I2C Mux board to see if I can get it working.
An I2C detect -y 1 gives:
pi@raspberrypi:~ $ i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- 3c -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- 73 -- -- -- --
So at least the Mux board is being recognized.
I should mention that when I power up the RPi board, the white LED on the Thunderboard stays on and never goes off.
Thanks.
John
N8MDP
Traceback (most recent call last):
File "/home/pi/SDL_Pi_GroveWeatherPi/RaspberryPi-AS3935/demo.py", line 13, in <module>
sensor = RPi_AS3935(address=0x02, bus=1)
TypeError: 'module' object is not callable
On the GroveWeatherPi software, I get a remote I/O error around the code that executed:
###################################
# ad3935 Set up Lightning Detector
###################################
if (config.Lightning_Mode == True):
# switch to BUS1 - lightning detector is on Bus1
if (config.TCA9545_I2CMux_Present):
tca9545.write_control_register(TCA9545_CONFIG_BUS1)
as3935 = RPi_AS3935(address=0x02, bus=1)
try:
as3935.set_indoors(True)
config.AS3935_Present = True
print ("AS3935 Lightning Detector present")
The error occurs when the as3935.set_indoors(True) is executed
I tried an experiment attaching the I2C cable from the Thunderboard directly to the Pi2Grover board. The demo.py software throws the same error as above but the GroveWeatherPi software detects that the board is present. Normally the Thunderboard I2C is connected to the I2C 4-Channel Mux board connector J3 The Mux board has a grove cable connected from J2 to a I2C expander board and a cable from J1 to an I2C cable on the Pi2Grover board. This is why I attached the Thunderboard to the Pi2Grover board to see if maybe the Mux board may have gone bad.
So a couple of questions:
1. Can excessive heat in my barn damage the Thunderboard or the Mux board?
2. What are some other failure modes for the Thunderboard?
3. What can be done to determine if the board has indeed gone bad.
I'll continue to debug and reconnect the Thunderboard to the I2C Mux board to see if I can get it working.
An I2C detect -y 1 gives:
pi@raspberrypi:~ $ i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- 3c -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- 73 -- -- -- --
So at least the Mux board is being recognized.
I should mention that when I power up the RPi board, the white LED on the Thunderboard stays on and never goes off.
Thanks.
John
N8MDP