4 hours sounds familiar. I used to work in network engineering and polled equipment via SNMP for statistics. Some counters were measured at high resolutions that would hit their max after just a few hours of runtime.
Take an unsigned 32-bit integer or uint32_t
. It has a maximum value of 4,294,967,295
. That may seem like a lot, but if you had an FPGA that took measurements and provided a timestamp as ticks since boot for each message it sends back, you’d hit the maximum value after just a few hours.
For example, imagine that they had a low-power FPGA running at 1MHz which increases the tick counter on every cycle. This would cause the counter to increase by 1,000,000 every second. You’d hit the max in just under 4,295 seconds, or roughly 71 minutes. To get closer to 4 hours we’d reduce the frequency by 4 to get 250KHz.
All of this is speculative. Could be that it’s not from a value failing to update but just a divide-by-zero error somewhere. Interested to see what the public is able to uncover as the core problem.
I was talking to a Tesla owner about this and they argued that if the window is electric then there’s no difference making the door electric. They couldn’t understand that the door itself can be operated independently of the rest of the vehicle.
Making windows electric causes a safety tradeoff. You get ease of operation while losing the ability to open the window in the event of an accident (where power cannot be supplied). However you can still unlock and open the door manually as an alternative escape option. This also applies in non-accident scenarios (dead battery).
Making doors electric is nothing more than a safety risk. From the inside you might have access to a manual release latch, but some doors require you to unscrew things first. Any emergency situation where you need to exit as soon as possible and the power is lost almost guarantees that you’ll be unable to safely escape.