Post by pkavanau on Aug 14, 2019 15:11:34 GMT -8
I just purchased a ThunderBoard, but no lightning simulator, so am trying to test it with the spark from a piezo butane lighter (the recommended method for a more primitive lightning detector I once had).
At about one foot distance, I get instances of "Interrupt reason= 0". Another post says this means false detect (but it's not one of the listed interrupts in the Interrupt Management section of the AS3935 Data Sheet). It seems reasonable that the spark wouldn't look like lightning to the ThunderBoard.
But if I farther decrease the distance, Python function read_i2c_block_data generates IOError 121 and the Interrupt reason is not available. Sometimes the unit even seems to become nonresponsive.
Is this error likely to occur in normal operation? Is the spark actually disturbing the logic of this board (the irony!)?
At about one foot distance, I get instances of "Interrupt reason= 0". Another post says this means false detect (but it's not one of the listed interrupts in the Interrupt Management section of the AS3935 Data Sheet). It seems reasonable that the spark wouldn't look like lightning to the ThunderBoard.
But if I farther decrease the distance, Python function read_i2c_block_data generates IOError 121 and the Interrupt reason is not available. Sometimes the unit even seems to become nonresponsive.
Is this error likely to occur in normal operation? Is the spark actually disturbing the logic of this board (the irony!)?
