Access rain reset

  • 2
  • Problem
  • Updated 2 months ago
I'm still getting random resets of the rain total to zero on My Acurite. I've done all the troubleshooting procedures twice. I am running the old smart hub with a second 5/1 and that never resets.  This has been going on since I installed it a few months ago. Very frustrating that I keep getting no results except being told to do all the troubleshooting procedures over again. I've posted pictures of the graphs showing the resets in previous posts. HELP! 
Photo of tonyroman2

tonyroman2

  • 105 Posts
  • 10 Reply Likes

Posted 4 months ago

  • 2
Photo of tonyroman2

tonyroman2

  • 105 Posts
  • 10 Reply Likes
Help?
Photo of Gregory DiCarlo

Gregory DiCarlo

  • 145 Posts
  • 35 Reply Likes
The problem is on Acurite's side. They have not come up with a fix. Nothing you can do about it.
Photo of AcuRite Jennifer

AcuRite Jennifer

  • 11801 Posts
  • 536 Reply Likes
Hello tonyroman2,

Do you have the battery back up in the Access? What is the name brand of the batteries you are using? How often is this occurring? Can you provide us with specific dates as to when you received a reset of rain? We can see you have 2 Access devices on your account. Please specify which device this is happening on. Thank you.
Photo of Gregory DiCarlo

Gregory DiCarlo

  • 145 Posts
  • 35 Reply Likes
Instead of the canned response, how about the acknowledgement that there are problems with the Access and that Acurite is working on fixes for them, and when we can expect the problems to be fixed. You keep saying you are happy to help with these problems, but nothing has been fixed yet, and your canned responses hasn't helped anyone.   
Photo of caldixiechick48

caldixiechick48

  • 14 Posts
  • 1 Reply Like
I'm having he same issues. I just installed the new Access last night. It is talking to everything properly, but I'm getting random rain resets. I've got at least two today. This mirrors the same problem Acurite was having with the internet bridge last year when each new rain event triggered a reset. My display is reading correctly and all other readings on the MyAcurite app are correct except the rain totals. I've disconnected the bridge and am only using the Access. Is Acurite working on a resolution? And yes, I put 3 fresh Kirkland AA batteries that I checked on the meter prior to installing them. Please advise on a solution.
Photo of Tom Orsi

Tom Orsi

  • 32 Posts
  • 2 Reply Likes
Shame on me!!  I had the same problem with the smart hub, and it went on for months, with a bunch of canned unhelpful responses before the problem was finally fixed. I'm unable to contact the support phone number('experiencing system problems'--I'LL SAY!). Why was I stupid enough to fall for this again? Can we get real support on this, or do I need to wait for the dry season for accurate rain reporting?
Photo of AcuRite Rachell

AcuRite Rachell, Employee

  • 6284 Posts
  • 199 Reply Likes
Hello All,
We’ve had a small handful of users experiencing an issue like this, and our development team has identified a possible cause and are looking into it. We will make an announcement when we have more information.
Photo of Tom Orsi

Tom Orsi

  • 32 Posts
  • 2 Reply Likes
Today's rain reported by Access vs. SmartHub. We shouldn't have had to pay for this inaccuracy and the accompanying aggravation.
Photo of caldixiechick48

caldixiechick48

  • 14 Posts
  • 1 Reply Like
Looks like I’d better hook the smart hub back up until this is fixed. Thank you.
Photo of Jim Bensman

Jim Bensman

  • 3 Posts
  • 0 Reply Likes
Photo of Tom Orsi

Tom Orsi

  • 32 Posts
  • 2 Reply Likes
Is anybody home at acurite? It's unconscionable that you have resurrected a problem that you had about 16 months ago, but you can't solve it now.
Photo of Anthony

Anthony

  • 4 Posts
  • 0 Reply Likes
I just bought 2 of these access units for over 200 bucks and both are resetting before midnight this is ridiculous this has been going on forever way back to the backyard weather junk....are you ever going to get this fixed it’s pathetic your still selling these knowing you haven’t fixed this problem
Photo of Anthony

Anthony

  • 4 Posts
  • 0 Reply Likes
Photo of Tom Orsi

Tom Orsi

  • 32 Posts
  • 2 Reply Likes
I solved my problem. I sent the piece of junk back. Of course, I'm out the cost of shipping (both ways), but I decided it was time to cut my losses. Fortunately, I still have my 'SmartHub,' which had its problems in the past, but after months of waiting for bug fixes, it now gives me accurate information. They're no longer going support the Smarthub, which might mean that there will be no software updates. That's probably good news. It will take longer to screw things up.
(Edited)
Photo of Anthony

Anthony

  • 4 Posts
  • 0 Reply Likes
They can get everyone off their backs by simply changing the name to “my inacurite”
Photo of AcuRite Rachell

AcuRite Rachell, Employee

  • 6284 Posts
  • 199 Reply Likes
Hello All,

We started issuing the update on 4/9/18. This update will automatically be applied to any connected devices over the next few nights. This update will correct the rain resets that have been occurring on your account. Please let us know if you have any questions. Thank you.
Photo of David Pushee

David Pushee

  • 30 Posts
  • 0 Reply Likes
Rachell, what is the firmware version with the fix?  My Access lists firmware version 047, and continues to show rain resets that seem to occur between about 8:30pm and midnight.  Sometimes there will be 2 or more resets in that period.

I am convinced that in my case the problem relates to an internal clock running at super speed causing the unit to believe that midnight has happened up to 3 and a half hours early.   This screen grab from a WU chart of the last 7 days shows premature resets is almost all of the last week.



Note, I submitted a problem report about the over clocking issue with my Access unit over a month ago and have not heard any status as yet.  Everything that I send seems to get swallowed up in a black hole.  And yes, I have been through ALL of the troubleshooting questions already.  If anyone else wants to check this, the WU station id is KNHPLYMO5.
Photo of John Z

John Z

  • 894 Posts
  • 186 Reply Likes
Shawn, you might find this thead interesting:

https://support.acurite.com/acurite/t...
Photo of David Pushee

David Pushee

  • 30 Posts
  • 0 Reply Likes
Shawn, your symptoms seem to be exactly what I was seeing.   I never checked my router logs, so I can't say whether the access was frequently requesting an IP, but a too fast clock was evident, WU was getting correct data but Acurite was not. Premature rain resets happened as well but seemed to occur when the Access thought that midnight had come.
I was plagued by that for a couple of months until 2 weeks ago when I removed the router's IP reservation for my Access.  Since then, everything seems to be working well.  The only issues have been a couple of times where power and/or internet outages occurred and the Access failed to reconnect (flashing red) when I checked hours later.
I hate to mess with it since it seems to be working well, but I may test the use of a reserved IP a couple more times to see if the problem recurs.  I can't for the life of me understand why a reserved IP address would cause the clock to run too fast, but it does seem to be the case.

Note to Rachell: Yes, the Access has been working well for the past couple of weeks.
Photo of John Z

John Z

  • 894 Posts
  • 186 Reply Likes
David, thanks for chiming in here. Glad to see your fix is still holding. Still puzzled as to why! It is not out of the question that a firmware issue is at the root of this. I'm a hardware guy, so to me all problems are most likely hardware problems :-)
(Edited)
Photo of David Pushee

David Pushee

  • 30 Posts
  • 0 Reply Likes
John Z, (and Rachell - please pass this info on to engineers)

I'm putting my money on a firmware problem that may be somehow triggering a hardware problem.  I have confirmed that my Access unit does not play well with a DHCP "reserved" address, but I have no idea why that should ever be the case.  I use reserved addresses for several items on my LAN, never with ill effects - why is Access different?

For those who need to know full details, my router is a TP-Link Archer C9 Firmware Version: 3.17.0 Build 20161008 Rel.64225n, Hardware Version: ArcherC9 v1.  

The Access has been playing well for most of this month.  Today I decided to run a test.  Recently, the Access has been happily working on LAN IP address 192.168.0.105.  I logged on to the router and set it to reserve that same address for the Access and then at 4:27:36 pm I rebooted the router to put that reservation into effect.

At 4:32:48, the router got a DHCP request from the Access 24:C8:6E:0A:4A:F7.  The router replied with an offer of address 192.168.0.105 (the same one that the Access had been happily using previously.  Thus began a rapid fire exchange between the Access and router over repeated requests for an address.

At 4:37 (about 5 minutes after the first router log record showing the Access asking for an address, I checked in on the Access and it reported last update from sensors as over 5 minutes in the future.  I should note that it also reported the sensor connections as mediocre (not good as usual).

At 4:39, I logged in to the router, disabled the address reservation, and started the router reboot to put the change into effect. Once the outer and Access got up to speed again, I again checked the Access (again happily using the same IP address.  Over the next few minutes, the Access seemed to consistently run at 9 minutes ahead of the correct time.  

At 4:44, I restarted the Access (which caused it to reset the internal clock.  Now, at 7:04 pm, the Access continues to report correct time.

Following are two system logs from my router.  The first starts at the time that I rebooted the router to start the reserved address.  The second starts at the time that I rebooted the router to disable the reservation.


####################################################################
#        Archer_C9  System Log 
# Time = 2018-04-21 16:34:34 485s
# H-Ver = ArcherC9 v1 : S-Ver = 3.17.0 Build 20161008 Rel.64225n
# L = 192.168.0.1 : M = 255.255.255.0
# W1 = DHCP : W = 76.179.60.239 : M = 255.255.240.0 : G = 76.179.48.1
####################################################################

May 21 16:26:36 DHCP INFO    System started
May 21 16:26:37 DHCP      NOTICE DHCP server started
May 21 16:26:37 SECURITY  INFO    PPTP Passthrough enabled
May 21 16:26:37 SECURITY  INFO    L2TP Passthrough enabled
May 21 16:26:37 SECURITY  INFO    IPSEC Passthrough enabled
May 21 16:26:37 DHCP      INFO    dhcpc_ipc_data_rcv_router 763 : current network type = 0  
May 21 16:26:37 DHCP      INFO    DHCPC Send DISCOVER with request ip 0 and unicast flag 0
May 21 16:26:37 SECURITY  INFO    FTP ALG enabled
May 21 16:26:37 SECURITY  INFO    TFTP ALG enabled
May 21 16:26:37 DHCP      INFO    DHCPC Recv OFFER from server 39d0fe8e with ip ef3cb34c
May 21 16:26:37 SECURITY  INFO    H323 ALG enabled
May 21 16:26:37 DHCP      INFO    DHCPC Send REQUEST to server 39d0fe8e with request ip ef3cb34c
May 21 16:26:37 SECURITY  INFO    RTSP ALG enabled
May 21 16:26:38 DHCP      INFO    DHCPC Recv ACK from server 39d0fe8e with ip ef3cb34c lease time 48858
May 21 16:26:38 DHCP      INFO    DHCPC:GET ip:ef3cb34c mask:f0ffff gateway:130b34c dns1:3d2f12d1 dns2:3e2f12d1 static route:0
May 21 16:26:38 DHCP      INFO    dhcpc_ipc_data_rcv_router 763 : current network type = 0  
May 21 16:26:38 DHCP      NOTICE Dynamic IP(DHCP Client) obtained an IP successfully
May 21 16:26:46 DHCP      INFO    DHCPS:Recv REQUEST from 40:B4:CD:20:86:FF
May 21 16:26:46 DHCP      INFO    DHCPS:Send ACK to 192.168.0.101
May 21 16:26:48 DHCP      INFO    Send router solicitaion OK, trying to get default gateway.
May 21 16:26:49 DHCP      INFO    DHCPS:Recv DISCOVER from 34:64:A9:D7:E2:8E
May 21 16:26:49 DHCP      INFO    DHCPC perform a DHCP renew
May 21 16:26:49 DHCP      INFO    DHCPC Send REQUEST to server 39d0fe8e with request ip ef3cb34c
May 21 16:26:49 DHCP      INFO    DHCP6C get gateway  from ISP, RS sent count is 1.
May 21 16:26:49 OTHER      NOTICE DNS1 = , DNS2 = , gateway = fe80::201:5cff:fe81:6846
May 21 16:26:49 OTHER      NOTICE dnsConf is option domain-name-servers  ;
May 21 16:26:50 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.100
May 21 16:26:50 DHCP      INFO    DHCPS:Recv REQUEST from 34:64:A9:D7:E2:8E
May 21 16:26:50 DHCP      INFO    DHCPS:Send ACK to 192.168.0.100
May 21 16:26:50 DHCP      INFO    DHCPC Recv ACK from server 39d0fe8e with ip ef3cb34c lease time 48846
May 21 16:26:50 DHCP      INFO    DHCPC:GET ip:ef3cb34c mask:f0ffff gateway:130b34c dns1:3d2f12d1 dns2:3e2f12d1 static route:0
May 21 16:26:50 DHCP      INFO    DHCPS:Recv REQUEST from 9C:AD:97:CA:44:D7
May 21 16:26:50 DHCP      INFO    dhcpc_ipc_data_rcv_router 763 : current network type = 0  
May 21 16:26:50 DHCP      NOTICE Dynamic IP(DHCP Client) obtained an IP successfully
May 21 16:26:51 DHCP      INFO    DHCPS:Send ACK to 192.168.0.106
May 21 16:26:58 DHCP      INFO    DHCPS:Recv REQUEST from 40:B4:CD:20:86:FF
May 21 16:26:58 DHCP      INFO    DHCPS:Send ACK to 192.168.0.101
May 21 16:27:08 DHCP      INFO    DHCPS:Recv REQUEST from 9C:AD:97:CA:44:D7
May 21 16:27:08 DHCP      INFO    DHCPS:Send ACK to 192.168.0.106
May 21 16:27:51 DHCP      INFO    DHCPS:Recv REQUEST from 7C:B0:C2:C3:E3:12
May 21 16:27:52 DHCP      INFO    DHCPS:Send ACK to 192.168.0.110
May 21 16:29:04 DHCP      INFO    DHCPS:Recv DISCOVER from A0:C9:A0:CF:E2:D0
May 21 16:29:05 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.107
May 21 16:29:05 DHCP      INFO    DHCPS:Recv REQUEST from A0:C9:A0:CF:E2:D0
May 21 16:29:05 DHCP      INFO    DHCPS:Send ACK to 192.168.0.107
May 21 16:32:48 DHCP      INFO    DHCPS:Recv REQUEST from 24:C8:6E:0A:4A:F7
May 21 16:32:48 DHCP      INFO    DHCPS:Send ACK to 192.168.0.105
May 21 16:32:49 DHCP      INFO    DHCPS:Recv DISCOVER from 24:C8:6E:0A:4A:F7
May 21 16:32:50 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.105
May 21 16:32:50 DHCP      INFO    DHCPS:Recv REQUEST from 24:C8:6E:0A:4A:F7
May 21 16:32:50 DHCP      INFO    DHCPS:Send ACK to 192.168.0.105
May 21 16:32:50 DHCP      INFO    DHCPS:Recv REQUEST from 7C:B0:C2:C3:E3:12
May 21 16:32:50 DHCP      INFO    DHCPS:Send ACK to 192.168.0.110
May 21 16:32:52 DHCP      INFO    DHCPS:Recv DISCOVER from 24:C8:6E:0A:4A:F7
May 21 16:32:53 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.105
May 21 16:32:53 DHCP      INFO    DHCPS:Recv DISCOVER from 24:C8:6E:0A:4A:F7
May 21 16:32:54 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.105
May 21 16:32:54 DHCP      INFO    DHCPS:Recv REQUEST from 24:C8:6E:0A:4A:F7
May 21 16:32:54 DHCP      INFO    DHCPS:Send ACK to 192.168.0.105
May 21 16:32:54 DHCP      INFO    DHCPS:Recv REQUEST from 24:C8:6E:0A:4A:F7
May 21 16:32:54 DHCP      INFO    DHCPS:Send ACK to 192.168.0.105
May 21 16:32:57 DHCP      INFO    DHCPS:Recv DISCOVER from 24:C8:6E:0A:4A:F7
May 21 16:32:58 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.105
May 21 16:32:58 DHCP      INFO    DHCPS:Recv REQUEST from 24:C8:6E:0A:4A:F7
May 21 16:32:58 DHCP      INFO    DHCPS:Send ACK to 192.168.0.105
May 21 16:33:03 DHCP      INFO    DHCPS:Recv DISCOVER from 24:C8:6E:0A:4A:F7
May 21 16:33:04 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.105
May 21 16:33:04 DHCP      INFO    DHCPS:Recv REQUEST from 24:C8:6E:0A:4A:F7
May 21 16:33:04 DHCP      INFO    DHCPS:Send ACK to 192.168.0.105
May 21 16:33:07 DHCP      INFO    DHCPS:Recv DISCOVER from 24:C8:6E:0A:4A:F7
May 21 16:33:08 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.105
May 21 16:33:08 DHCP      INFO    DHCPS:Recv DISCOVER from 24:C8:6E:0A:4A:F7
May 21 16:33:09 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.105
May 21 16:33:09 DHCP      INFO    DHCPS:Recv REQUEST from 24:C8:6E:0A:4A:F7
May 21 16:33:09 DHCP      INFO    DHCPS:Send ACK to 192.168.0.105
May 21 16:33:09 DHCP      INFO    DHCPS:Recv REQUEST from 24:C8:6E:0A:4A:F7
May 21 16:33:09 DHCP      INFO    DHCPS:Send ACK to 192.168.0.105
May 21 16:33:11 DHCP      INFO    DHCPS:Recv DISCOVER from 24:C8:6E:0A:4A:F7
May 21 16:33:12 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.105
May 21 16:33:12 DHCP      INFO    DHCPS:Recv DISCOVER from 24:C8:6E:0A:4A:F7
May 21 16:33:13 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.105
May 21 16:33:13 DHCP      INFO    DHCPS:Recv REQUEST from 24:C8:6E:0A:4A:F7
May 21 16:33:13 DHCP      INFO    DHCPS:Send ACK to 192.168.0.105
May 21 16:33:13 DHCP      INFO    DHCPS:Recv REQUEST from 24:C8:6E:0A:4A:F7
May 21 16:33:13 DHCP      INFO    DHCPS:Send ACK to 192.168.0.105
May 21 16:33:16 DHCP      INFO    DHCPS:Recv DISCOVER from 24:C8:6E:0A:4A:F7
May 21 16:33:17 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.105
May 21 16:33:17 DHCP      INFO    DHCPS:Recv DISCOVER from 24:C8:6E:0A:4A:F7
May 21 16:33:18 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.105
May 21 16:33:18 DHCP      INFO    DHCPS:Recv REQUEST from 24:C8:6E:0A:4A:F7
May 21 16:33:18 DHCP      INFO    DHCPS:Send ACK to 192.168.0.105
May 21 16:33:18 DHCP      INFO    DHCPS:Recv REQUEST from 24:C8:6E:0A:4A:F7
May 21 16:33:18 DHCP      INFO    DHCPS:Send ACK to 192.168.0.105
May 21 16:33:23 DHCP      INFO    DHCPS:Recv DISCOVER from 24:C8:6E:0A:4A:F7
May 21 16:33:24 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.105
May 21 16:33:24 DHCP      INFO    DHCPS:Recv REQUEST from 24:C8:6E:0A:4A:F7
May 21 16:33:24 DHCP      INFO    DHCPS:Send ACK to 192.168.0.105
May 21 16:33:26 DHCP      INFO    DHCPS:Recv DISCOVER from 24:C8:6E:0A:4A:F7
May 21 16:33:27 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.105
May 21 16:33:27 DHCP      INFO    DHCPS:Recv REQUEST from 24:C8:6E:0A:4A:F7
May 21 16:33:27 DHCP      INFO    DHCPS:Send ACK to 192.168.0.105
May 21 16:33:30 DHCP      INFO    DHCPS:Recv DISCOVER from 24:C8:6E:0A:4A:F7
May 21 16:33:31 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.105
May 21 16:33:31 DHCP      INFO    DHCPS:Recv DISCOVER from 24:C8:6E:0A:4A:F7
May 21 16:33:32 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.105
May 21 16:33:32 DHCP      INFO    DHCPS:Recv REQUEST from 24:C8:6E:0A:4A:F7
May 21 16:33:32 DHCP      INFO    DHCPS:Send ACK to 192.168.0.105
May 21 16:33:32 DHCP      INFO    DHCPS:Recv REQUEST from 24:C8:6E:0A:4A:F7
May 21 16:33:32 DHCP      INFO    DHCPS:Send ACK to 192.168.0.105
May 21 16:33:35 DHCP      INFO    DHCPS:Recv DISCOVER from 24:C8:6E:0A:4A:F7
May 21 16:33:36 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.105
May 21 16:33:36 DHCP      INFO    DHCPS:Recv REQUEST from 24:C8:6E:0A:4A:F7
May 21 16:33:36 DHCP      INFO    DHCPS:Send ACK to 192.168.0.105
May 21 16:33:41 DHCP      INFO    DHCPS:Recv DISCOVER from 24:C8:6E:0A:4A:F7
May 21 16:33:42 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.105
May 21 16:33:42 DHCP      INFO    DHCPS:Recv REQUEST from 24:C8:6E:0A:4A:F7
May 21 16:33:42 DHCP      INFO    DHCPS:Send ACK to 192.168.0.105
May 21 16:33:44 DHCP      INFO    DHCPS:Recv DISCOVER from 24:C8:6E:0A:4A:F7
May 21 16:33:45 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.105
May 21 16:33:45 DHCP      INFO    DHCPS:Recv DISCOVER from 24:C8:6E:0A:4A:F7
May 21 16:33:46 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.105
May 21 16:33:46 DHCP      INFO    DHCPS:Recv REQUEST from 24:C8:6E:0A:4A:F7
May 21 16:33:46 DHCP      INFO    DHCPS:Send ACK to 192.168.0.105
May 21 16:33:46 DHCP      INFO    DHCPS:Recv REQUEST from 24:C8:6E:0A:4A:F7
May 21 16:33:46 DHCP      INFO    DHCPS:Send ACK to 192.168.0.105
May 21 16:33:49 DHCP      INFO    DHCPS:Recv DISCOVER from 24:C8:6E:0A:4A:F7
May 21 16:33:50 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.105
May 21 16:33:50 DHCP      INFO    DHCPS:Recv DISCOVER from 24:C8:6E:0A:4A:F7
May 21 16:33:51 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.105
May 21 16:33:51 DHCP      INFO    DHCPS:Recv REQUEST from 24:C8:6E:0A:4A:F7
May 21 16:33:51 DHCP      INFO    DHCPS:Send ACK to 192.168.0.105
May 21 16:33:51 DHCP      INFO    DHCPS:Recv REQUEST from 24:C8:6E:0A:4A:F7
May 21 16:33:51 DHCP      INFO    DHCPS:Send ACK to 192.168.0.105
May 21 16:33:56 DHCP      INFO    DHCPS:Recv DISCOVER from 24:C8:6E:0A:4A:F7
May 21 16:33:57 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.105
May 21 16:33:57 DHCP      INFO    DHCPS:Recv REQUEST from 24:C8:6E:0A:4A:F7
May 21 16:33:57 DHCP      INFO    DHCPS:Send ACK to 192.168.0.105
May 21 16:34:04 DHCP      INFO    DHCPS:Recv DISCOVER from 24:C8:6E:0A:4A:F7
May 21 16:34:05 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.105
May 21 16:34:05 DHCP      INFO    DHCPS:Recv REQUEST from 24:C8:6E:0A:4A:F7
May 21 16:34:05 DHCP      INFO    DHCPS:Send ACK to 192.168.0.105
May 21 16:34:07 DHCP      INFO    DHCPS:Recv DISCOVER from 24:C8:6E:0A:4A:F7
May 21 16:34:08 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.105
May 21 16:34:08 DHCP      INFO    DHCPS:Recv DISCOVER from 24:C8:6E:0A:4A:F7
May 21 16:34:09 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.105
May 21 16:34:09 DHCP      INFO    DHCPS:Recv REQUEST from 24:C8:6E:0A:4A:F7
May 21 16:34:09 DHCP      INFO    DHCPS:Send ACK to 192.168.0.105
May 21 16:34:09 DHCP      INFO    DHCPS:Recv REQUEST from 24:C8:6E:0A:4A:F7
May 21 16:34:09 DHCP      INFO    DHCPS:Send ACK to 192.168.0.105
May 21 16:34:14 DHCP      INFO    DHCPS:Recv DISCOVER from 24:C8:6E:0A:4A:F7
May 21 16:34:15 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.105
May 21 16:34:15 DHCP      INFO    DHCPS:Recv REQUEST from 24:C8:6E:0A:4A:F7
May 21 16:34:15 DHCP      INFO    DHCPS:Send ACK to 192.168.0.105
May 21 16:34:18 DHCP      INFO    DHCPS:Recv DISCOVER from 24:C8:6E:0A:4A:F7
May 21 16:34:19 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.105
May 21 16:34:19 DHCP      INFO    DHCPS:Recv REQUEST from 24:C8:6E:0A:4A:F7
May 21 16:34:19 DHCP      INFO    DHCPS:Send ACK to 192.168.0.105
May 21 16:34:21 DHCP      INFO    DHCPS:Recv DISCOVER from 24:C8:6E:0A:4A:F7
May 21 16:34:22 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.105
May 21 16:34:22 DHCP      INFO    DHCPS:Recv REQUEST from 24:C8:6E:0A:4A:F7
May 21 16:34:22 DHCP      INFO    DHCPS:Send ACK to 192.168.0.105
May 21 16:34:25 DHCP      INFO    DHCPS:Recv DISCOVER from 24:C8:6E:0A:4A:F7
May 21 16:34:26 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.105
May 21 16:34:26 DHCP      INFO    DHCPS:Recv DISCOVER from 24:C8:6E:0A:4A:F7
May 21 16:34:27 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.105
May 21 16:34:27 DHCP      INFO    DHCPS:Recv REQUEST from 24:C8:6E:0A:4A:F7
May 21 16:34:27 DHCP      INFO    DHCPS:Send ACK to 192.168.0.105
May 21 16:34:27 DHCP      INFO    DHCPS:Recv REQUEST from 24:C8:6E:0A:4A:F7
May 21 16:34:27 DHCP      INFO    DHCPS:Send ACK to 192.168.0.105
May 21 16:34:33 DHCP      INFO    DHCPS:Recv DISCOVER from 24:C8:6E:0A:4A:F7
May 21 16:34:34 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.105
May 21 16:34:34 DHCP      INFO    DHCPS:Recv REQUEST from 24:C8:6E:0A:4A:F7
May 21 16:34:34 DHCP      INFO    DHCPS:Send ACK to 192.168.0.105


####################################################################
#        Archer_C9  System Log 
# Time = 2018-04-21 19:08:11 8916s
# H-Ver = ArcherC9 v1 : S-Ver = 3.17.0 Build 20161008 Rel.64225n
# L = 192.168.0.1 : M = 255.255.255.0
# W1 = DHCP : W = 76.179.60.239 : M = 255.255.240.0 : G = 76.179.48.1
####################################################################

May 21 16:39:42 DHCP INFO    System started
May 21 16:39:43 DHCP      NOTICE DHCP server started
May 21 16:39:43 SECURITY  INFO    PPTP Passthrough enabled
May 21 16:39:43 SECURITY  INFO    L2TP Passthrough enabled
May 21 16:39:43 SECURITY  INFO    IPSEC Passthrough enabled
May 21 16:39:43 DHCP      INFO    dhcpc_ipc_data_rcv_router 763 : current network type = 0  
May 21 16:39:43 DHCP      INFO    DHCPC Send DISCOVER with request ip 0 and unicast flag 0
May 21 16:39:43 SECURITY  INFO    FTP ALG enabled
May 21 16:39:43 SECURITY  INFO    TFTP ALG enabled
May 21 16:39:43 DHCP      INFO    DHCPC Recv OFFER from server 39d0fe8e with ip ef3cb34c
May 21 16:39:43 SECURITY  INFO    H323 ALG enabled
May 21 16:39:43 DHCP      INFO    DHCPC Send REQUEST to server 39d0fe8e with request ip ef3cb34c
May 21 16:39:43 SECURITY  INFO    RTSP ALG enabled
May 21 16:39:44 DHCP      INFO    DHCPC Recv ACK from server 39d0fe8e with ip ef3cb34c lease time 48074
May 21 16:39:44 DHCP      INFO    DHCPC:GET ip:ef3cb34c mask:f0ffff gateway:130b34c dns1:3d2f12d1 dns2:3e2f12d1 static route:0
May 21 16:39:44 DHCP      INFO    dhcpc_ipc_data_rcv_router 763 : current network type = 0  
May 21 16:39:44 DHCP      NOTICE Dynamic IP(DHCP Client) obtained an IP successfully
May 21 16:39:47 DHCP      INFO    DHCPS:Recv DISCOVER from 24:C8:6E:0A:4A:F7
May 21 16:39:48 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.105
May 21 16:39:48 DHCP      INFO    DHCPS:Recv REQUEST from 24:C8:6E:0A:4A:F7
May 21 16:39:48 DHCP      INFO    DHCPS:Send ACK to 192.168.0.105
May 21 16:39:52 DHCP      INFO    DHCPS:Recv REQUEST from 40:B4:CD:20:86:FF
May 21 16:39:52 DHCP      INFO    DHCPS:Send ACK to 192.168.0.101
May 21 16:39:54 DHCP      INFO    DHCPS:Recv REQUEST from 9C:AD:97:CA:44:D7
May 21 16:39:54 DHCP      INFO    Send router solicitaion OK, trying to get default gateway.
May 21 16:39:55 DHCP      INFO    DHCPS:Send ACK to 192.168.0.106
May 21 16:39:55 DHCP      INFO    DHCPC perform a DHCP renew
May 21 16:39:55 DHCP      INFO    DHCPC Send REQUEST to server 39d0fe8e with request ip ef3cb34c
May 21 16:39:55 DHCP      INFO    DHCP6C get gateway  from ISP, RS sent count is 1.
May 21 16:39:55 OTHER      NOTICE DNS1 = , DNS2 = , gateway = fe80::201:5cff:fe81:6846
May 21 16:39:55 OTHER      NOTICE dnsConf is option domain-name-servers  ;
May 21 16:39:56 DHCP      INFO    DHCPC Recv ACK from server 39d0fe8e with ip ef3cb34c lease time 48062
May 21 16:39:56 DHCP      INFO    DHCPC:GET ip:ef3cb34c mask:f0ffff gateway:130b34c dns1:3d2f12d1 dns2:3e2f12d1 static route:0
May 21 16:39:56 DHCP      INFO    dhcpc_ipc_data_rcv_router 763 : current network type = 0  
May 21 16:39:56 DHCP      NOTICE Dynamic IP(DHCP Client) obtained an IP successfully
May 21 16:39:56 DHCP      INFO    DHCPS:Recv DISCOVER from 34:64:A9:D7:E2:8E
May 21 16:39:57 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.100
May 21 16:39:57 DHCP      INFO    DHCPS:Recv REQUEST from 34:64:A9:D7:E2:8E
May 21 16:39:57 DHCP      INFO    DHCPS:Send ACK to 192.168.0.100
May 21 16:40:04 DHCP      INFO    DHCPS:Recv REQUEST from 40:B4:CD:20:86:FF
May 21 16:40:04 DHCP      INFO    DHCPS:Send ACK to 192.168.0.101
May 21 16:40:11 DHCP      INFO    DHCPS:Recv REQUEST from 9C:AD:97:CA:44:D7
May 21 16:40:11 DHCP      INFO    DHCPS:Send ACK to 192.168.0.106
May 21 16:40:57 DHCP      INFO    DHCPS:Recv REQUEST from 7C:B0:C2:C3:E3:12
May 21 16:40:58 DHCP      INFO    DHCPS:Send ACK to 192.168.0.110
May 21 16:42:05 DHCP      INFO    DHCPS:Recv DISCOVER from A0:C9:A0:CF:E2:D0
May 21 16:42:06 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.107
May 21 16:42:06 DHCP      INFO    DHCPS:Recv REQUEST from A0:C9:A0:CF:E2:D0
May 21 16:42:06 DHCP      INFO    DHCPS:Send ACK to 192.168.0.107
May 21 16:44:51 DHCP      INFO    DHCPS:Recv DISCOVER from 24:C8:6E:0A:4A:F7
May 21 16:44:51 DHCP      INFO    DHCPS:Send OFFER with ip 192.168.0.105
May 21 16:44:51 DHCP      INFO    DHCPS:Recv REQUEST from 24:C8:6E:0A:4A:F7
May 21 16:44:51 DHCP      INFO    DHCPS:Send ACK to 192.168.0.105
May 21 16:45:57 DHCP      INFO    DHCPS:Recv REQUEST from 7C:B0:C2:C3:E3:12
May 21 16:45:57 DHCP      INFO    DHCPS:Send ACK to 192.168.0.110
May 21 17:05:04 DHCP      INFO    DHCPS:Recv REQUEST from 7C:B0:C2:C3:E3:12
May 21 17:05:04 DHCP      INFO    DHCPS:Send ACK to 192.168.0.110
May 21 17:10:05 DHCP      INFO    DHCPS:Recv REQUEST from 7C:B0:C2:C3:E3:12
Photo of John Z

John Z

  • 894 Posts
  • 186 Reply Likes
David, excellent observations.

Your comment about a firmware issue driving a hardware issue got me thinking and researching.

The crystal oscillator circuits used in real time clocks are often designed to run at extremely low power levels. This so that very long battery life is obtained. These micropower circuits are easily perturbed by electrical noise, though, and it is good practice to keep the wires to their crystal very short, and to use ground-plane and shielding techniques to further minimize pickup. I see no attempts along these lines on the Access board. Further, the crystal is very near the Ethernet port, a noise source.

Noise pickup will always have the effect of making the RTC run fast. Noise pulses will be counted as any other clock tick. Depending on the noise input, the clock may get a jog that kicks it forward, but holds there, or if the noise is more continuosly available, the clock will seem to run at an accelerated rate. I have seen both conditions reported here.

To me it is plausible that bursts of Ethernet activity may be contributing noise input to the clock, and hence the firmware-driving-hardware model for the problem. BTW, none of my three Access devices have exhibited this issue. Some particular combination of circuit parameters may be necessary to set this up.
(Edited)