Author Topic: AS3595 not Detecting Strikes  (Read 27030 times)

0 Members and 2 Guests are viewing this topic.

Offline Jumpin Joe

  • Forecaster
  • *****
  • Posts: 1023
    • Joe’s Weather
AS3595 not Detecting Strikes
« on: April 03, 2014, 07:17:34 AM »
My AS3935 is showing 0 strikes and we have lighting all around us. Anyone know what I can check?

Joe


Offline dfroula

  • Forecaster
  • *****
  • Posts: 543
Re: AS3595 not Detecting Strikes
« Reply #1 on: April 03, 2014, 09:12:44 AM »
Funny you should ask....I've been playing with the settings this morning with all the lightning in the Chicago area.

My theory is that setting disturber rejection settings low doesn't swamp the internals of the AS3935, since it has to analyze each event anyway. They just prevent an interrupt from being generated and swamping the controller with interrupts, unless "Ignore disturber" is on, which prevents disturbers from generating interrupts inside the chip.

Try these settings. Seems to be working better. I get about 10-15 disturbers/sec if I disable "Ignore disturbers", but leave "Ignore disturbers" checked to minimize load on the controller.

Check my results at: http://projectmf.homelinux.com/as3935_stats.html

Don


Offline dfroula

  • Forecaster
  • *****
  • Posts: 543
Re: AS3595 not Detecting Strikes
« Reply #2 on: April 03, 2014, 09:50:16 AM »
New discovery....

Setting the "Tune cap" parameter from "Auto" to the number printed on the anti-static bag in which the AS395 was shipped seems to greatly increase the number of detections. I think the cal routine runs periodically, based on the I2C logs I've examined. While it is calibrating, the interrupt line is used to send calibration frequencies to the controller. Lightning can't be detected during the cal process.

Oddly, I found the AS3935 was more sensitive to my piezo lighter test before I grounded the controller, although I think it was due to more interference being received. It is probably working better with actual lightning grounded.

Offline Jumpin Joe

  • Forecaster
  • *****
  • Posts: 1023
    • Joe’s Weather
Re: AS3595 not Detecting Strikes
« Reply #3 on: April 03, 2014, 05:24:13 PM »
Since getting my power supply back up, and restarting RED, the AS3935 decided it wanted to cooperate and started detecting.  \:D/

Offline dfroula

  • Forecaster
  • *****
  • Posts: 543
Re: AS3595 not Detecting Strikes
« Reply #4 on: May 05, 2014, 07:29:12 PM »
I discovered something interesting when a storm rolled through a week or so ago - the AS3935 board becomes completely deaf when the controller board is grounded!

I have my board grounded to the AC ground of the wall outlet through a modified 3-wire plug. This helps the performance of the ferrite antennas significantly. When I unplugged the ground, the AS3935 started happily detecting strikes immediately.

Right now, the shields are tied to the "-"  grounded terminals of the amplifier connections, which in turn are grounded to the controller through the shielded CAT5 cable.

I plan to separate the shield grounds from the grounded sides of the ferrite antennas in the antenna box and run a ground only to the shields, leaving the controller and amplifier ungrounded. This should provide the benefits of grounded shields without impacting the operation of the AS3935.

Odd a ground should stop the AS3935 from operating. Interferer levels are normal with the controller ground connected.

Regards,

Don

Offline 92merc

  • BismarckWeather.net
  • Forecaster
  • *****
  • Posts: 876
  • BismarckWeather.net
    • BismarckWeather.net
Re: AS3595 not Detecting Strikes
« Reply #5 on: May 06, 2014, 12:18:56 PM »
I'm still in the process of putting my system together.  I'm just waiting for my standoffs to arrive so I can mount my boards in the boxes I bought.

I'm mounting both boards in my attached garage where my main breaker panel is.  I was able to attach a ground wire to the house's main ground that goes to that panel.  I've already run a line up and over to where my boards are going to go.

I've also build my antenna's conduit system to include copper shielding.  I was planning on grounding both boards and the copper shielding to the ground wire.  Are you saying I probably shouldn't run a ground to the boards?
https://www.BismarckWeather.net
Davis VP2, Cumulus, WeatherDisplay, Blitzortung, Bloomsky, Saratoga Scripts, NOAA Stream via PI

Offline dfroula

  • Forecaster
  • *****
  • Posts: 543
Re: AS3595 not Detecting Strikes
« Reply #6 on: May 06, 2014, 01:06:04 PM »
All I can say with certainty is that tying the board ground terminal to AC ground makes the AS3935 completely insensitive to lightning strikes,  even directly overhead.

As I said, I plan to try grounding just the shields on the ferrites and leave the rest of the system without an explicit ground connection to see if it helps. I know the AS3935 happily detects lightning without the ground, to its maximum distance. I may be an issue with my AC ground, but with the ground connected the auto-noise floor gets set to maximum gain and the interferer level is low. That indicates noise is not getting coupled through the ground, I believe.

YMMV, so use whatever works best! I'd be interested in reports from others. I noticed that Joe's problem resolved when he changed the power supply. I'm guessing the new supply had its "-" lead isolated from AC ground.

Don

Offline 92merc

  • BismarckWeather.net
  • Forecaster
  • *****
  • Posts: 876
  • BismarckWeather.net
    • BismarckWeather.net
Re: AS3595 not Detecting Strikes
« Reply #7 on: May 06, 2014, 01:12:26 PM »
I'll start out by not grounding my boards.  But I bought grounding blocks and have a good main ground to my area.  So I can easily change what I want.

I decided to go a different route on my power supply.  With the new E-Boards coming out, I'm glad I did.  I just hope it's a "clean" power supply.

This unit has varying amperage available for the different USB ports.  But it has 5 ports on one brick. So that makes it easier for me.  Unless, it dies. 

http://www.amazon.com/gp/product/B00DVH62J2/ref=oh_details_o00_s00_i01?ie=UTF8&psc=1
https://www.BismarckWeather.net
Davis VP2, Cumulus, WeatherDisplay, Blitzortung, Bloomsky, Saratoga Scripts, NOAA Stream via PI

Offline dfroula

  • Forecaster
  • *****
  • Posts: 543
Re: AS3595 not Detecting Strikes
« Reply #8 on: May 11, 2014, 10:28:33 AM »
During local lightning activity I've tried many different settings to try to coax real strikes from the AS3935. I've tried enabling disturber detection and adjusting settings for a few disturbers/sec. No lightning detected, at any noise threshold/sensitivity/strike rejection settings.

The only way I get any "lightning" detections is by setting Signal Threshold and Spike Rejection both to zero. This results in a flood of disturbers, but also random lightning detections that don't seem correlated to actual lightning. Setting either or both of these settings back to non-zero values stops strike detection completely.

I though this may have been related to recent grounding of my system and change of a power supply. After experimenting with various grounding configurations, I'm convinced this is not the issue.

The AS3935 also no longer responds to my piezo "sparker", except to indicate a high noise floor, which triggers a noise threshold adjustment.

The detector used to work fine a few releases back. Puzzling.

I'll try again when storms roll through Chicago this afternoon.

Regards,

Don
WD9DMP

Offline Jumpin Joe

  • Forecaster
  • *****
  • Posts: 1023
    • Joe’s Weather
Re: AS3595 not Detecting Strikes
« Reply #9 on: May 11, 2014, 11:15:45 AM »
During local lightning activity I've tried many different settings to try to coax real strikes from the AS3935. I've tried enabling disturber detection and adjusting settings for a few disturbers/sec. No lightning detected, at any noise threshold/sensitivity/strike rejection settings.

The only way I get any "lightning" detections is by setting Signal Threshold and Spike Rejection both to zero. This results in a flood of disturbers, but also random lightning detections that don't seem correlated to actual lightning. Setting either or both of these settings back to non-zero values stops strike detection completely.

I though this may have been related to recent grounding of my system and change of a power supply. After experimenting with various grounding configurations, I'm convinced this is not the issue.

The AS3935 also no longer responds to my piezo "sparker", except to indicate a high noise floor, which triggers a noise threshold adjustment.

The detector used to work fine a few releases back. Puzzling.

I'll try again when storms roll through Chicago this afternoon.

Regards,

Don
WD9DMP

Don, mine is no longer detecting.  I will try changing my setting to zero and see if the corrects it. Confused as to why it has stopped.

Joe

Offline Jumpin Joe

  • Forecaster
  • *****
  • Posts: 1023
    • Joe’s Weather
Re: AS3595 not Detecting Strikes
« Reply #10 on: May 11, 2014, 11:36:01 AM »
During local lightning activity I've tried many different settings to try to coax real strikes from the AS3935. I've tried enabling disturber detection and adjusting settings for a few disturbers/sec. No lightning detected, at any noise threshold/sensitivity/strike rejection settings.

The only way I get any "lightning" detections is by setting Signal Threshold and Spike Rejection both to zero. This results in a flood of disturbers, but also random lightning detections that don't seem correlated to actual lightning. Setting either or both of these settings back to non-zero values stops strike detection completely.

I though this may have been related to recent grounding of my system and change of a power supply. After experimenting with various grounding configurations, I'm convinced this is not the issue.

The AS3935 also no longer responds to my piezo "sparker", except to indicate a high noise floor, which triggers a noise threshold adjustment.

The detector used to work fine a few releases back. Puzzling.

I'll try again when storms roll through Chicago this afternoon.

Regards,

Don
WD9DMP

Don, mine is no longer detecting.  I will try changing my setting to zero and see if the corrects it. Confused as to why it has stopped.

Joe

Just checked my status screen and discovered that the AS3935 detected one strike last night 2km away, nothing else. Very weird. Have the revisions Tobi has made caused the AS3935 to stop working?

Joe

Offline dfroula

  • Forecaster
  • *****
  • Posts: 543
Re: AS3595 not Detecting Strikes
« Reply #11 on: May 11, 2014, 12:13:51 PM »
I should mention, I also tried powering the module from +5vdc (from +3vdc), no change.

 I believe there is an internal voltage regulator in the chip that can be turned on/off with a register setting. I'm not sure how Tobi's code sets this up (I should look, as he posted a link to the code). I think I read somewhere there is a bug that affects detections relating to how the internal VR is configured.

 Don

Offline dfroula

  • Forecaster
  • *****
  • Posts: 543
Re: AS3595 not Detecting Strikes
« Reply #12 on: May 11, 2014, 12:18:07 PM »
Here's the VR bug reference. Not sure if this affects detections:

http://fll-freak.com/blog/?p=554

"The behaviour using I2C at address 0 is known to me and worked arround by using the address ADD0=ADD1=1 (Vdd). Testing this I have found another issue: If the voltage regulator is turned on, ADD0 and ADD1 must not be connected to Vdd (as described in the data sheet). If the voltage regulator is turned on and one of the address pins is set to the positive voltage supply (Vdd), the chip-intern voltage regulator will not be able to regulate the voltage. In my case the output regulated voltage was 4,3V instead of 3V as described in data sheet. I have contacted the AMS support with it and they confirmed this issue. They recommended to me to set the ADD0 and ADD1 pins to the voltage regulated supply (VREG). After connecting the address pins to VREG the regulated voltage became 3V =)."

Don
WD9DMP

Offline dfroula

  • Forecaster
  • *****
  • Posts: 543
Re: AS3595 not Detecting Strikes
« Reply #13 on: May 11, 2014, 01:24:56 PM »
New Beta 4 firmware just posted by Tobi that may correct the issue. See similar thread at blitzortung.org.

Regards,

Don
WD9DMP

Offline Jumpin Joe

  • Forecaster
  • *****
  • Posts: 1023
    • Joe’s Weather
Re: AS3595 not Detecting Strikes
« Reply #14 on: May 11, 2014, 06:00:05 PM »
New Beta 4 firmware just posted by Tobi that may correct the issue. See similar thread at blitzortung.org.

Regards,

Don
WD9DMP

I installed the update, no change. Still not detecting and storms are all around me.

Joe

Offline dfroula

  • Forecaster
  • *****
  • Posts: 543
Re: AS3595 not Detecting Strikes
« Reply #15 on: May 12, 2014, 10:11:54 AM »
Same here. No change with the new firmware.

I can get the AS3935 to report lightning by setting the "Signal Threshold" and "Strike Detection" to zero, but the report rate is independent of actual lightning activity. It triggers randomly, even with no lightning in the area.

The new firmware seemed to cause the web interface on the controller to hang after a while.

Regards,

Don
WD9DMP

Offline dfroula

  • Forecaster
  • *****
  • Posts: 543
Re: AS3595 not Detecting Strikes
« Reply #16 on: May 12, 2014, 10:19:31 AM »
Joe, I see from your posting on the blitzortung.org message boards that your AS3935 is now working.

What did you do to kick-start the board? I haven't tried a power-cycle on the system yet, but I will after I post this.

Best,

Don
WD9DMP

Offline Jumpin Joe

  • Forecaster
  • *****
  • Posts: 1023
    • Joe’s Weather
Re: AS3595 not Detecting Strikes
« Reply #17 on: May 12, 2014, 10:35:10 AM »
Joe, I see from your posting on the blitzortung.org message boards that your AS3935 is now working.

What did you do to kick-start the board? I haven't tried a power-cycle on the system yet, but I will after I post this.

Best,

Don
WD9DMP

Don,

Nothing!! It just started working. Not sure it is picking up all or most of the strikes. At least this is an improvement.  I still think it has to do with the update Tobi has made. Probably still needs a few more adjustments.

Good luck,

Joe

Offline dfroula

  • Forecaster
  • *****
  • Posts: 543
Re: AS3595 not Detecting Strikes
« Reply #18 on: May 13, 2014, 12:32:35 PM »
Well, after two rounds of severe storms here yesterday, my AS3935 recorded a total of 10 lightning strikes. I was using the settings in the attched image, which should have set things for the maximum sensitivity and minimum filtering for false strikes.

I'm at a loss to figure out why the AS3935 has suddenly become so unresponsive. Guess I'll put this issue on the back burner for now.

Regards,

Don WD9DMP

Offline Jumpin Joe

  • Forecaster
  • *****
  • Posts: 1023
    • Joe’s Weather
Re: AS3595 not Detecting Strikes
« Reply #19 on: May 14, 2014, 05:05:43 PM »
As I post this we are being hit very heavily by storms and the AS3935 has only picked up 2 hits. Since those two hits I have seen more lighting than I could count. Very disappointed.

Joe

Offline Dr Obbins

  • Forecaster
  • *****
  • Posts: 1148
Re: AS3595 not Detecting Strikes
« Reply #20 on: May 14, 2014, 09:39:08 PM »
I got one!
It picked up 1 strike about 10 minutes ago. However I don't recall seeing or hearing any lightning. :-k Its raining, but not storming here.

Offline miraculon

  • Sunrise Side Weather
  • Forecaster
  • *****
  • Posts: 3538
  • KE8DAF
    • Sunrise Side Weather in Rogers City MI USA
Re: AS3595 not Detecting Strikes
« Reply #21 on: May 28, 2014, 01:04:50 PM »
I found the new Acu-Rite Lightning Detector and posted it here http://www.wxforum.net/index.php?topic=22740.msg219002#msg219002

I sent a message to Rhino asking if it uses the AS3935 IC from AMS. Reading between the lines in the manual and the timing of it makes me think (and hope) that it uses the AS3935. If so, I plan on parking it next to my AS3935 board interfaced to RED to see how they compare.

Greg


Blitzortung Stations #706 and #1682
CoCoRaHS: MI-PI-1
CWOP: CW4114 and KE8DAF-13
WU: KMIROGER7
Amateur Radio Callsign: KE8DAF

Offline dfroula

  • Forecaster
  • *****
  • Posts: 543
Re: AS3595 not Detecting Strikes
« Reply #22 on: May 28, 2014, 01:09:21 PM »
Seeing only 3 lightning detections after a round of local storms last night, I grabbed an AS3935 and I2C log this morning, under clear-sky conditions.

It appears that the AS3935 is issuing a constant stream of interrupts. The debug log doesn't seem to give the register values, so I can't determine the type of interrupt. However, there is no lightning detected, "Ignore Disturbers" is checked, and the noise floor is stable. The AS3935 seems to be recalculating storm distance on every interrupt, which seems odd.

The stream of non-lightning interrupts could be masking lightning detections.

Log below:

Code: [Select]

2014-05-28 12:06:40  174317 | AS3935: Interrupt (1)
2014-05-28 12:06:40  174317 | I2C: -------
2014-05-28 12:06:40  174317 | I2C: Start Read from device 0x3, register 0x3, mask 0xf
2014-05-28 12:06:40  174317 | I2C: Select Transmit to device 0x6
2014-05-28 12:06:40  174317 | I2C: Send Register 0x3
2014-05-28 12:06:40  174317 | I2C: Transmitted (Read)
2014-05-28 12:06:40  174317 | I2C: Select Receive from device 0x7
2014-05-28 12:06:40  174317 | AS3935: Interrupt (0)
2014-05-28 12:06:40  174317 | I2C: Receiver-Mode
2014-05-28 12:06:40  174317 | I2C: Received 0x30
2014-05-28 12:06:40  174317 | AS3935: Interrupt register is 0x0, pending status 0, pin 0
2014-05-28 12:06:40  174317 | AS3935: Distance estimation recalculated
2014-05-28 12:06:40  174317 | AS3935: Interrupt (1)
2014-05-28 12:06:40  174317 | I2C: -------
2014-05-28 12:06:40  174317 | I2C: Start Read from device 0x3, register 0x3, mask 0xf
2014-05-28 12:06:40  174317 | I2C: Select Transmit to device 0x6
2014-05-28 12:06:40  174317 | I2C: Send Register 0x3
2014-05-28 12:06:40  174317 | I2C: Transmitted (Read)
2014-05-28 12:06:40  174317 | I2C: Select Receive from device 0x7
2014-05-28 12:06:40  174317 | AS3935: Interrupt (0)
2014-05-28 12:06:40  174317 | I2C: Receiver-Mode
2014-05-28 12:06:40  174317 | I2C: Received 0x30
2014-05-28 12:06:40  174317 | AS3935: Interrupt register is 0x0, pending status 0, pin 0
2014-05-28 12:06:40  174317 | AS3935: Distance estimation recalculated
2014-05-28 12:06:42  174319 | AS3935: Interrupt (1)
2014-05-28 12:06:42  174319 | I2C: -------
2014-05-28 12:06:42  174319 | I2C: Start Read from device 0x3, register 0x3, mask 0xf
2014-05-28 12:06:42  174319 | I2C: Select Transmit to device 0x6
2014-05-28 12:06:42  174319 | I2C: Send Register 0x3
2014-05-28 12:06:42  174319 | I2C: Transmitted (Read)
2014-05-28 12:06:42  174319 | I2C: Select Receive from device 0x7
2014-05-28 12:06:42  174319 | AS3935: Interrupt (0)
2014-05-28 12:06:42  174319 | I2C: Receiver-Mode
2014-05-28 12:06:42  174319 | I2C: Received 0x30
2014-05-28 12:06:42  174319 | AS3935: Interrupt register is 0x0, pending status 0, pin 0
2014-05-28 12:06:42  174319 | AS3935: Distance estimation recalculated
2014-05-28 12:06:42  174319 | AS3935: Interrupt (1)
2014-05-28 12:06:42  174319 | I2C: -------
2014-05-28 12:06:42  174319 | I2C: Start Read from device 0x3, register 0x3, mask 0xf
2014-05-28 12:06:42  174319 | I2C: Select Transmit to device 0x6
2014-05-28 12:06:42  174319 | I2C: Send Register 0x3
2014-05-28 12:06:42  174319 | I2C: Transmitted (Read)
2014-05-28 12:06:42  174319 | I2C: Select Receive from device 0x7
2014-05-28 12:06:42  174319 | AS3935: Interrupt (0)
2014-05-28 12:06:42  174319 | I2C: Receiver-Mode
2014-05-28 12:06:42  174319 | I2C: Received 0x30
2014-05-28 12:06:42  174319 | AS3935: Interrupt register is 0x0, pending status 0, pin 0
2014-05-28 12:06:42  174319 | AS3935: Distance estimation recalculated
2014-05-28 12:06:43  174320 | AS3935: Interrupt (1)
2014-05-28 12:06:43  174320 | I2C: -------
2014-05-28 12:06:43  174320 | I2C: Start Read from device 0x3, register 0x3, mask 0xf
2014-05-28 12:06:43  174320 | I2C: Select Transmit to device 0x6
2014-05-28 12:06:43  174320 | I2C: Send Register 0x3
2014-05-28 12:06:43  174320 | I2C: Transmitted (Read)
2014-05-28 12:06:43  174320 | I2C: Select Receive from device 0x7
2014-05-28 12:06:43  174320 | AS3935: Interrupt (0)
2014-05-28 12:06:43  174320 | I2C: Receiver-Mode
2014-05-28 12:06:43  174320 | I2C: Received 0x30
2014-05-28 12:06:43  174320 | AS3935: Interrupt register is 0x0, pending status 0, pin 0
2014-05-28 12:06:43  174320 | AS3935: Distance estimation recalculated
2014-05-28 12:06:43  174320 | AS3935: Interrupt (1)
2014-05-28 12:06:43  174320 | I2C: -------
2014-05-28 12:06:43  174320 | I2C: Start Read from device 0x3, register 0x3, mask 0xf
2014-05-28 12:06:43  174320 | I2C: Select Transmit to device 0x6
2014-05-28 12:06:43  174320 | I2C: Send Register 0x3
2014-05-28 12:06:43  174320 | I2C: Transmitted (Read)
2014-05-28 12:06:43  174320 | I2C: Select Receive from device 0x7
2014-05-28 12:06:43  174320 | AS3935: Interrupt (0)
2014-05-28 12:06:43  174320 | I2C: Receiver-Mode
2014-05-28 12:06:43  174320 | I2C: Received 0x30
2014-05-28 12:06:43  174320 | AS3935: Interrupt register is 0x0, pending status 0, pin 0
2014-05-28 12:06:43  174320 | AS3935: Distance estimation recalculated
2014-05-28 12:06:44  174321 | AS3935: Interrupt (1)
2014-05-28 12:06:44  174321 | I2C: -------
2014-05-28 12:06:44  174321 | I2C: Start Read from device 0x3, register 0x3, mask 0xf
2014-05-28 12:06:44  174321 | I2C: Select Transmit to device 0x6
2014-05-28 12:06:44  174321 | I2C: Send Register 0x3
2014-05-28 12:06:44  174321 | I2C: Transmitted (Read)
2014-05-28 12:06:44  174321 | I2C: Select Receive from device 0x7
2014-05-28 12:06:44  174321 | AS3935: Interrupt (0)
2014-05-28 12:06:44  174321 | I2C: Receiver-Mode
2014-05-28 12:06:44  174321 | I2C: Received 0x30
2014-05-28 12:06:44  174321 | AS3935: Interrupt register is 0x0, pending status 0, pin 0
2014-05-28 12:06:44  174321 | AS3935: Distance estimation recalculated
2014-05-28 12:06:44  174321 | AS3935: Interrupt (1)
2014-05-28 12:06:44  174321 | I2C: -------
2014-05-28 12:06:44  174321 | I2C: Start Read from device 0x3, register 0x3, mask 0xf
2014-05-28 12:06:44  174321 | I2C: Select Transmit to device 0x6
2014-05-28 12:06:44  174321 | I2C: Send Register 0x3
2014-05-28 12:06:44  174321 | I2C: Transmitted (Read)
2014-05-28 12:06:44  174321 | I2C: Select Receive from device 0x7
2014-05-28 12:06:44  174321 | AS3935: Interrupt (0)
2014-05-28 12:06:44  174321 | I2C: Receiver-Mode
2014-05-28 12:06:44  174321 | I2C: Received 0x30
2014-05-28 12:06:44  174321 | AS3935: Interrupt register is 0x0, pending status 0, pin 0
2014-05-28 12:06:44  174321 | AS3935: Distance estimation recalculated
2014-05-28 12:06:44  174321 | AS3935: Interrupt (1)
2014-05-28 12:06:44  174321 | I2C: -------
2014-05-28 12:06:44  174321 | I2C: Start Read from device 0x3, register 0x3, mask 0xf
2014-05-28 12:06:44  174321 | I2C: Select Transmit to device 0x6
2014-05-28 12:06:44  174321 | I2C: Send Register 0x3
2014-05-28 12:06:44  174321 | I2C: Transmitted (Read)
2014-05-28 12:06:44  174321 | I2C: Select Receive from device 0x7
2014-05-28 12:06:44  174321 | AS3935: Interrupt (0)
2014-05-28 12:06:44  174321 | I2C: Receiver-Mode
2014-05-28 12:06:44  174321 | I2C: Received 0x30
2014-05-28 12:06:44  174321 | AS3935: Interrupt register is 0x0, pending status 0, pin 0
2014-05-28 12:06:44  174321 | AS3935: Distance estimation recalculated
2014-05-28 12:06:45  174322 | AS3935: Interrupt (1)
2014-05-28 12:06:45  174322 | I2C: -------
2014-05-28 12:06:45  174322 | I2C: Start Read from device 0x3, register 0x3, mask 0xf
2014-05-28 12:06:45  174322 | I2C: Select Transmit to device 0x6
2014-05-28 12:06:45  174322 | I2C: Send Register 0x3
2014-05-28 12:06:45  174322 | I2C: Transmitted (Read)
2014-05-28 12:06:45  174322 | I2C: Select Receive from device 0x7
2014-05-28 12:06:45  174322 | AS3935: Interrupt (0)
2014-05-28 12:06:45  174322 | I2C: Receiver-Mode
2014-05-28 12:06:45  174322 | I2C: Received 0x30
2014-05-28 12:06:45  174322 | AS3935: Interrupt register is 0x0, pending status 0, pin 0
2014-05-28 12:06:45  174322 | AS3935: Distance estimation recalculated
2014-05-28 12:06:45  174322 | AS3935: Interrupt (1)
2014-05-28 12:06:45  174322 | I2C: -------
2014-05-28 12:06:45  174322 | I2C: Start Read from device 0x3, register 0x3, mask 0xf
2014-05-28 12:06:45  174322 | I2C: Select Transmit to device 0x6
2014-05-28 12:06:45  174322 | I2C: Send Register 0x3
2014-05-28 12:06:45  174322 | I2C: Transmitted (Read)
2014-05-28 12:06:45  174322 | I2C: Select Receive from device 0x7
2014-05-28 12:06:45  174322 | AS3935: Interrupt (0)
2014-05-28 12:06:45  174322 | I2C: Receiver-Mode
2014-05-28 12:06:45  174322 | I2C: Received 0x30
2014-05-28 12:06:45  174322 | AS3935: Interrupt register is 0x0, pending status 0, pin 0
2014-05-28 12:06:45  174322 | AS3935: Distance estimation recalculated
2014-05-28 12:06:46  174323 | AS3935: Interrupt (1)
2014-05-28 12:06:46  174323 | I2C: -------
2014-05-28 12:06:46  174323 | I2C: Start Read from device 0x3, register 0x3, mask 0xf
2014-05-28 12:06:46  174323 | I2C: Select Transmit to device 0x6
2014-05-28 12:06:46  174323 | I2C: Send Register 0x3
2014-05-28 12:06:46  174323 | I2C: Transmitted (Read)
2014-05-28 12:06:46  174323 | I2C: Select Receive from device 0x7
2014-05-28 12:06:46  174323 | AS3935: Interrupt (0)
2014-05-28 12:06:46  174323 | I2C: Receiver-Mode
2014-05-28 12:06:46  174323 | I2C: Received 0x30
2014-05-28 12:06:46  174323 | AS3935: Interrupt register is 0x0, pending status 0, pin 0
2014-05-28 12:06:46  174323 | AS3935: Distance estimation recalculated
2014-05-28 12:06:46  174323 | AS3935: Interrupt (1)
2014-05-28 12:06:46  174323 | I2C: -------
2014-05-28 12:06:46  174323 | I2C: Start Read from device 0x3, register 0x3, mask 0xf
2014-05-28 12:06:46  174323 | I2C: Select Transmit to device 0x6
2014-05-28 12:06:46  174323 | I2C: Send Register 0x3
2014-05-28 12:06:46  174323 | I2C: Transmitted (Read)
2014-05-28 12:06:46  174323 | I2C: Select Receive from device 0x7
2014-05-28 12:06:46  174323 | AS3935: Interrupt (0)
2014-05-28 12:06:46  174323 | I2C: Receiver-Mode
2014-05-28 12:06:46  174323 | I2C: Received 0x30
2014-05-28 12:06:46  174323 | AS3935: Interrupt register is 0x0, pending status 0, pin 0
2014-05-28 12:06:46  174323 | AS3935: Distance estimation recalculated
2014-05-28 12:06:47  174324 | AS3935: Interrupt (1)
2014-05-28 12:06:47  174324 | I2C: -------
2014-05-28 12:06:47  174324 | I2C: Start Read from device 0x3, register 0x3, mask 0xf
2014-05-28 12:06:47  174324 | I2C: Select Transmit to device 0x6
2014-05-28 12:06:47  174324 | I2C: Send Register 0x3
2014-05-28 12:06:47  174324 | I2C: Transmitted (Read)
2014-05-28 12:06:47  174324 | I2C: Select Receive from device 0x7
2014-05-28 12:06:47  174324 | AS3935: Interrupt (0)
2014-05-28 12:06:47  174324 | I2C: Receiver-Mode
2014-05-28 12:06:47  174324 | I2C: Received 0x30
2014-05-28 12:06:47  174324 | AS3935: Interrupt register is 0x0, pending status 0, pin 0
2014-05-28 12:06:47  174324 | AS3935: Distance estimation recalculated
2014-05-28 12:06:49  174326 | AS3935: Interrupt (1)
2014-05-28 12:06:49  174326 | I2C: -------
2014-05-28 12:06:49  174326 | I2C: Start Read from device 0x3, register 0x3, mask 0xf
2014-05-28 12:06:49  174326 | I2C: Select Transmit to device 0x6
2014-05-28 12:06:49  174326 | I2C: Send Register 0x3
2014-05-28 12:06:49  174326 | I2C: Transmitted (Read)
2014-05-28 12:06:49  174326 | I2C: Select Receive from device 0x7
2014-05-28 12:06:49  174326 | AS3935: Interrupt (0)
2014-05-28 12:06:49  174326 | I2C: Receiver-Mode
2014-05-28 12:06:49  174326 | I2C: Received 0x30
2014-05-28 12:06:49  174326 | AS3935: Interrupt register is 0x0, pending status 0, pin 0
2014-05-28 12:06:49  174326 | AS3935: Distance estimation recalculated
2014-05-28 12:06:49  174326 | AS3935: Interrupt (1)
2014-05-28 12:06:49  174326 | I2C: -------
2014-05-28 12:06:49  174326 | I2C: Start Read from device 0x3, register 0x3, mask 0xf
2014-05-28 12:06:49  174326 | I2C: Select Transmit to device 0x6
2014-05-28 12:06:49  174326 | I2C: Send Register 0x3
2014-05-28 12:06:49  174326 | I2C: Transmitted (Read)
2014-05-28 12:06:49  174326 | I2C: Select Receive from device 0x7
2014-05-28 12:06:49  174326 | AS3935: Interrupt (0)
2014-05-28 12:06:49  174326 | I2C: Receiver-Mode
2014-05-28 12:06:49  174326 | I2C: Received 0x30
2014-05-28 12:06:49  174326 | AS3935: Interrupt register is 0x0, pending status 0, pin 0
2014-05-28 12:06:49  174326 | AS3935: Distance estimation recalculated
2014-05-28 12:06:50  174327 | AS3935: Interrupt (1)
2014-05-28 12:06:50  174327 | I2C: -------
2014-05-28 12:06:50  174327 | I2C: Start Read from device 0x3, register 0x3, mask 0xf
2014-05-28 12:06:50  174327 | I2C: Select Transmit to device 0x6
2014-05-28 12:06:50  174327 | I2C: Send Register 0x3
2014-05-28 12:06:50  174327 | I2C: Transmitted (Read)
2014-05-28 12:06:50  174327 | I2C: Select Receive from device 0x7
2014-05-28 12:06:50  174327 | AS3935: Interrupt (0)
2014-05-28 12:06:50  174327 | I2C: Receiver-Mode
2014-05-28 12:06:50  174327 | I2C: Received 0x30
2014-05-28 12:06:50  174327 | AS3935: Interrupt register is 0x0, pending status 0, pin 0
2014-05-28 12:06:50  174327 | AS3935: Distance estimation recalculated
2014-05-28 12:06:50  174327 | AS3935: Interrupt (1)
2014-05-28 12:06:50  174327 | I2C: -------
2014-05-28 12:06:50  174327 | I2C: Start Read from device 0x3, register 0x3, mask 0xf
2014-05-28 12:06:50  174327 | I2C: Select Transmit to device 0x6
2014-05-28 12:06:50  174327 | I2C: Send Register 0x3
2014-05-28 12:06:50  174327 | I2C: Transmitted (Read)
2014-05-28 12:06:50  174327 | I2C: Select Receive from device 0x7
2014-05-28 12:06:50  174327 | AS3935: Interrupt (0)
2014-05-28 12:06:50  174327 | I2C: Receiver-Mode
2014-05-28 12:06:50  174327 | I2C: Received 0x30
2014-05-28 12:06:50  174327 | AS3935: Interrupt register is 0x0, pending status 0, pin 0
2014-05-28 12:06:50  174327 | AS3935: Distance estimation recalculated
2014-05-28 12:06:51  174328 | AS3935: Interrupt (1)
2014-05-28 12:06:51  174328 | I2C: -------
2014-05-28 12:06:51  174328 | I2C: Start Read from device 0x3, register 0x3, mask 0xf
2014-05-28 12:06:51  174328 | I2C: Select Transmit to device 0x6
2014-05-28 12:06:51  174328 | I2C: Send Register 0x3
2014-05-28 12:06:51  174328 | I2C: Transmitted (Read)
2014-05-28 12:06:51  174328 | I2C: Select Receive from device 0x7
2014-05-28 12:06:51  174328 | AS3935: Interrupt (0)
2014-05-28 12:06:51  174328 | I2C: Receiver-Mode
2014-05-28 12:06:51  174328 | I2C: Received 0x30
2014-05-28 12:06:51  174328 | AS3935: Interrupt register is 0x0, pending status 0, pin 0
2014-05-28 12:06:51  174328 | AS3935: Distance estimation recalculated
2014-05-28 12:06:52  174329 | AS3935: Interrupt (1)
2014-05-28 12:06:52  174329 | AS3935: Interrupt (0)
2014-05-28 12:06:52  174329 | AS3935: Interrupt register is 0x0, pending status 0, pin 0
2014-05-28 12:06:52  174329 | AS3935: Distance estimation recalculated
2014-05-28 12:06:53  174330 | AS3935: Interrupt (1)
2014-05-28 12:06:53  174330 | AS3935: Interrupt (0)
2014-05-28 12:06:53  174330 | AS3935: Interrupt register is 0x0, pending status 0, pin 0
2014-05-28 12:06:53  174330 | AS3935: Distance estimation recalculated
2014-05-28 12:06:54  174331 | AS3935: Interrupt (1)
2014-05-28 12:06:54  174331 | AS3935: Interrupt (0)
2014-05-28 12:06:54  174331 | AS3935: Interrupt register is 0x0, pending status 0, pin 0
2014-05-28 12:06:54  174331 | AS3935: Distance estimation recalculated
2014-05-28 12:06:54  174331 | AS3935: Interrupt (1)
2014-05-28 12:06:54  174331 | AS3935: Interrupt (0)
2014-05-28 12:06:54  174331 | AS3935: Interrupt register is 0x0, pending status 0, pin 0
2014-05-28 12:06:54  174331 | AS3935: Distance estimation recalculated
2014-05-28 12:06:55  174332 | AS3935: Interrupt (1)
2014-05-28 12:06:55  174332 | AS3935: Interrupt (0)
2014-05-28 12:06:55  174332 | AS3935: Interrupt register is 0x0, pending status 0, pin 0
2014-05-28 12:06:55  174332 | AS3935: Distance estimation recalculated
2014-05-28 12:06:55  174332 | AS3935: Interrupt (1)
2014-05-28 12:06:55  174332 | AS3935: Interrupt (0)
2014-05-28 12:06:55  174332 | AS3935: Interrupt register is 0x0, pending status 0, pin 0
2014-05-28 12:06:55  174332 | AS3935: Distance estimation recalculated
2014-05-28 12:06:57  174334 | AS3935: Interrupt (1)
2014-05-28 12:06:57  174334 | AS3935: Interrupt (0)
2014-05-28 12:06:57  174334 | AS3935: Interrupt register is 0x0, pending status 0, pin 0
2014-05-28 12:06:57  174334 | AS3935: Distance estimation recalculated
2014-05-28 12:06:58  174335 | AS3935: Interrupt (1)
2014-05-28 12:06:58  174335 | AS3935: Interrupt (0)
2014-05-28 12:06:58  174335 | AS3935: Interrupt register is 0x0, pending status 0, pin 0
2014-05-28 12:06:58  174335 | AS3935: Distance estimation recalculated
2014-05-28 12:06:58  174335 | AS3935: Interrupt (1)
2014-05-28 12:06:58  174335 | AS3935: Interrupt (0)
2014-05-28 12:06:58  174335 | AS3935: Interrupt register is 0x0, pending status 0, pin 0
2014-05-28 12:06:58  174335 | AS3935: Distance estimation recalculated
2014-05-28 12:06:58  174335 | AS3935: Interrupt (1)
2014-05-28 12:06:58  174335 | AS3935: Interrupt (0)
2014-05-28 12:06:58  174335 | AS3935: Interrupt register is 0x0, pending status 0, pin 0
2014-05-28 12:06:58  174335 | AS3935: Distance estimation recalculated
2014-05-28 12:06:59  174336 | AS3935: Interrupt (1)
2014-05-28 12:06:59  174336 | AS3935: Interrupt (0)
2014-05-28 12:06:59  174336 | AS3935: Interrupt register is 0x0, pending status 0, pin 0
2014-05-28 12:06:59  174336 | AS3935: Distance estimation recalculated
2014-05-28 12:06:59  174336 | AS3935: Interrupt (1)
2014-05-28 12:06:59  174336 | AS3935: Interrupt (0)
2014-05-28 12:06:59  174336 | AS3935: Interrupt register is 0x0, pending status 0, pin 0
2014-05-28 12:06:59  174336 | AS3935: Distance estimation recalculated
2014-05-28 12:07:01  174338 | AS3935: Interrupt (1)
2014-05-28 12:07:01  174338 | AS3935: Interrupt (0)
2014-05-28 12:07:01  174338 | AS3935: Interrupt register is 0x0, pending status 0, pin 0
2014-05-28 12:07:01  174338 | AS3935: Distance estimation recalculated
2014-05-28 12:07:01  174338 | AS3935: Write registers...
2014-05-28 12:07:01  174338 |
2014-05-28 12:07:01  174338 | === AS3935 ==========================================
2014-05-28 12:07:01  174338 | AS3935: Write registers...
2014-05-28 12:07:01  174338 | AS3935: Calibrate Antenna...
2014-05-28 12:07:01  174338 | AS3935: LCO TUN_CAP=0 => Frequency 511200Hz, Deviation 2.2
2014-05-28 12:07:01  174338 | AS3935: LCO TUN_CAP=1 => Frequency 507200Hz, Deviation 1.4
2014-05-28 12:07:01  174338 | AS3935: LCO TUN_CAP=2 => Frequency 504800Hz, Deviation 1.0
2014-05-28 12:07:01  174338 | AS3935: LCO TUN_CAP=3 => Frequency 503200Hz, Deviation 0.6
2014-05-28 12:07:01  174338 | AS3935: LCO TUN_CAP=4 => Frequency 501600Hz, Deviation 0.3
2014-05-28 12:07:01  174338 | AS3935: LCO TUN_CAP=5 => Frequency 500000Hz, Deviation 0.0
2014-05-28 12:07:01  174338 | AS3935: LCO TUN_CAP=6 => Frequency 498400Hz, Deviation -0.3
2014-05-28 12:07:01  174338 | AS3935: Stop, found best frequency before
2014-05-28 12:07:01  174338 | AS3935: Found best tune-cap=5 with frequency=500000Hz => deviation=0.0%
2014-05-28 12:07:01  174338 | AS3935: Calibrate RCO...
2014-05-28 12:07:01  174338 | AS3935: CALIB_RCO accepted
2014-05-28 12:07:01  174338 | AS3935: Frequency on SRCO is 1151850Hz
2014-05-28 12:07:01  174338 | AS3935: CALIB_RCO accepted
2014-05-28 12:07:01  174338 | AS3935: Frequency on TRCO is 32500Hz
2014-05-28 12:07:01  174338 | AS3935: Init IRQ...
2014-05-28 12:07:01  174338 | =====================================================

Don
WD9DMP

Offline dfroula

  • Forecaster
  • *****
  • Posts: 543
Re: AS3595 not Detecting Strikes
« Reply #23 on: June 03, 2014, 09:24:29 AM »
I had a few minor thunderstorms pass within 15 km of my location yesterday morning. Although I visually observed no lightning, I actual received a reasonable number of strikes (13) as the storm passed nearby. The distance calculations and energy data from the AS3935 actually looked reasonable, considering the distance and intensity of the storm.

I had been setting the "Noise Floor" to the minimum of 390/28 with the "Noise Auto Raise" feature enabled, on the theory that the Auto function would raise the noise floor detection as required. I had observed the "Noise Auto Raise" function operate correctly in the past, ordinarily setting the noise floor to 630/45 during clear skies. The Auto function slowly reduces the threshold over time as the actual noise floor decreases.

As we have discussed if, the actual noise floor is above the "Noise Floor" setting, the AS3935 disables lightning detection until the actual noise floor is reduced below the "Noise Floor" threshold. This is normal operation.

On the theory that the "Noise Auto Raise" was not setting the threshold high enough during storms to keep the AS3035 in the detection range, I had reset the "Noise Floor" threshold to 1340/95, while leaving "Noise Auto Raise" enabled. I believe this keeps the minimum "Noise Floor" set by "Noise Auto Raise" to this value.

This seemed to make a considerable difference in the number of detected strikes. I will continue to monitor during the next few storms, but it appears that the setting change has awoken my AS3935.

The attached image shows my current settings.

Best regards,

Don
WD9DMP
« Last Edit: June 03, 2014, 09:44:13 AM by dfroula »

Offline miraculon

  • Sunrise Side Weather
  • Forecaster
  • *****
  • Posts: 3538
  • KE8DAF
    • Sunrise Side Weather in Rogers City MI USA
Re: AS3595 not Detecting Strikes
« Reply #24 on: June 03, 2014, 02:54:14 PM »
I just received my Acu-Rite 02020 Lightning Detector and set a new record for voiding the warranty.
After confirming that it works, I disassembled it and confirmed that indeed it does have an AMS AS3935.
The sensing coil looks very similar to what is used in the Embedded Adventures and other development kit boards.
Here is a picture of the AS3935 lurking next to a glob-top chip (display driver?). The PCB connects to the display with a conductive rubber zebra strip.
I now have something to compare to the AS3935 interfaced to RED. It was pretty cheap, $32 from Amazon.
After re-assembly, it does still work.

With my BBQ sparker close by, it responds with a beep and an "UNABLE TO DETECT" "PLEASE RELOCATE", although I did get it to categorize a spark noise as lightning. You can toggle between "Indoor" and "Outdoor" mode by pressing the Light and Power buttons and holding for 5 seconds.

Interestingly, it shows "1 mi" for the distance on the noise, similar to the "1km" strikes that we see on RED. I'll post further results as they develop. (quiet for storms today, so no opportunities for a good test)

Greg H
« Last Edit: June 03, 2014, 03:00:20 PM by miraculon »


Blitzortung Stations #706 and #1682
CoCoRaHS: MI-PI-1
CWOP: CW4114 and KE8DAF-13
WU: KMIROGER7
Amateur Radio Callsign: KE8DAF