I have checked a couple of other units on line and they seem to have 0-10-20 ppb. Nobody has 7 except me. Is my unit defective?

Ken

Yes, it would be nice if the A3 had a switching power supply instead of just a 3-terminal regulator.
I checked today and the voltage actually appearing at the unit is about 21 volts – so well within the spec.

I would like to update this subject. After discarding the power supply and switching to POE, I got a nice run of some 46 hours – and then the A3 started re-booting again. However, this time it is distinctly different:

> the LAN activity does not stop (except for the 1 minute the reboot actually takes)
> the run times between reboots are random – see attachment (before it was like clockwork)

This is not desirable, but it is an improvement – since, at most, one data point is lost.

Looking around on the system, it seems others have this issue too. For example, #8200074 rebooted some 13 times in June, #82000110 rebooted some 15 times in the last two weeks of June, #82000112 rebooted about 26 times in June. #8200012E is interesting – it reboots every single day at 7 AM.

Its too soon to say what my situation will settle out to – it looks like it could be 10-20 times *per day* which seems a bit excessive.

I have the A3’s address in my router’s DMZ at the moment, to remove one variable. But that does not seem to have anything to do with the problem.

As mentioned previously – no other devices on my network are having this sort of problem AFAIK. A number of them are continuously reporting to some server, or other, like the A3 is doing.

If there is something I can check or test to help trouble-shoot, I would be happy t o do that.

Ken

PROBLEM SOLVED

As the problem manifested itself with loss of LAN (wired) communications, that is where I was focussing my attention.

In fact, the problem was the 9v/1A power supply included with the unit. I was using the included supply for my bench testing. It was never my intention to use the “wall wart” in the final installation.

Powering the A3 at 24 VDC from a POE splitter has resulted in the unit running for nearly and hour now without a hiccup. So I think the problem is solved.

My conclusion is that the tiny (1A) supply is simply inadequate and at the 11th minute the A3 was doing something that required an extra bit of power causing a momentary part-undervoltage condition.

Usually the micro can signal an undervoltage condition (typically in /var/log/syslog). A feature request could be the addition of such an alarm – usually many voltage “near misses” are seen before the one that actually impacts operation. That certainly would have saved me a *lot* of time.

Ken

OK – here is another hypothesis. It looks like the unit can send data to the community server even when I cannot access it locally. I think what could cause that is if DHCP renewal is not handled correctly. My router would take the unit out of the ARP table and it would seem to disappear from the LAN. But it is still on the network and able to send data (stream it anyway). However, when the server tries to send a message back to the A3, it would get ‘destination unreachable’ from the router. Eventually, not seeing something from the server, the A3 reboots. It gets the initial DHCP information correctly and carries on until the first DHCP renewal operation where it gets kicked out of the ARP table again … and repeat.

Is there some way to make the unit use a static IP?

Ken

I put the A3 address into the DMZ, but it is still doing the same thing.
The router is a Verizon G1100 “Quantum FiOS” that is quite common in the US. I really have no other place to try it.
I can send you the IP although I suspect you can find it from your end 😉

I note that the parameter “Autoreboot” is set to 0s – is that OK? Anything else I can check (or change)?

I am concerned that continual re-booting will eventually destroy some eeprom or similar …

Ken