Key Fob Battery Life after Update to latest firmware

[borski]

I feel as dumb as @borski thinks I am when I try to read this

I don’t think you’re dumb.

That’s why I respond to you

 

[Saksak]

Bumping this post as the name says "... Latest Firmware" and now we have 3.6.0

3.6.0 doesn't seem to have changed the fob battery consumption much even thought the range to car lighting up and range to car unlocking have changed for me by ~5 feet. So most of what I posted in post #35 still applies.

One thing I did notice but can't verify(because Ive updated) is that with 3.5.1 you needed to move the car about 10 feet to make the fob sleep in the car even with movement. Now it seems to be that you need to go at least 5mph, either forward or back. I tested to about 50ft going less and fob didn't sleep. Here's some data for those interested.

View attachment 39285
Time.........What's Happening
35.............Picked up fob.
35-210.....Lots going on of little consequence, getting within ~40ft, car waking, unlocking, opening, all unrelated to the current bumps seen and all high consumption regardless.
210...........~5mph backing out driveway(don't try this with wife).
210-515...Driving around block. Little bumps are the fob getting jiggled, then shutting down.
515...........Unlocking the door and getting out.
590...........60 seconds after putting the fob down.

Note the green Voltage line, the fob voltage drops like crazy when under load and recovers gradually when not. This is about a month into a battery from the visor.

Nice reverse engineering!

The voltage graph is interesting and probably normal. It’s only a 2% drop and most likely caused by internal resistance going up due to heat generated under load.

The new algorithm of the fob going to sleep based on speed makes a lot of sense. Could it be that old algorithm based on distance might have kept the fob asleep leading to cars not locking when walking away? The fob being kept asleep would explain a lot of fob problems.

 

[bicycleguy]

The new algorithm of the fob going to sleep based on speed makes a lot of sense. Could it be that old algorithm based on distance might have kept the fob asleep leading to cars not locking when walking away? The fob being kept asleep would explain a lot of fob problems.

Perhaps, except it definitely wakes up when you open a door.