It is completely passive. My X has never sleep (even before) but my kids 3 sleeps a lot (rem: it is on both our cars). @AlanSubie4Life could confirm it doesn't affect his 3's sleep. He has a variety of post on it (3) when I bought and used the device before my Ohmmu.
It’s rated at 1mW or less or so as I recall, so no, it has no effect. [EDIT: actually less than 12mW, correction below…but that still does not matter]
Yes. Thanks. It was from memory: I meant 1 mW, but clearly it is less than about 12mW. In any case, of no consequence either way.Correct ... although I think you meant mA. Production Description on the Amazon link:
They are swapping out to V4 SLOWLY to check for errors before too deep into and exchange program. Contact them about timing for exchange.
Just installed the module. It the latest software/firmware you can select frequency for downloading data and to set to 24 hours. If there was any issues interfering with vehicle sleep cycles (and I doubt there is since it connects direct to battery). Cool little gadget.
I removed my 51R AGM (no issues or warnings) and replaced with the AtlasBX and connected the battery monitor to build a baseline if data. I have an Ohmmu V4 coming and I wanted a baseline of data before installing the Ohmmu. I can then watch the plots and see if any messages generated along with either voltage of rate of change triggering events.I think the smoother graphs are a result of the car deciding not to charge the 12V battery because the voltage is high (13.1-13.3V). Yesterday it started charging after I parked the car, and the voltage dropped down to 12.93V (~25% SoC). Then when it stopped charging, it threw the soft VCFRONT_a180 error (as always occurs on the falling edge after charging stops), the voltage was at 13.35V, and was at 13.3V in the morning for my weekday commute. I'm pretty sure it's not the BMC because Braille swears against them
Given it happens on the falling edges, it must be something about the rate of change. The level at which it happens can be anywhere from 13.8V or 14.1V all the way down to 13.1-13.3V.
FYI, Some have seen high phone battery usage and here is the post of what I did (I turn off automation and do it manually). Whatever works best for you. HTH!
teslamotorsclub.com
Absolutely no worries. These alerts aren't even popping up on the main display. They can only be found if you go into Service/Notifications. Worse case if you got one of the Amber alerts and it was the one that said the 12v failed and to schedule service for replacement it would just mean no further software updates would happen until you did a hard reset. In fact, that is what I'm trying to determine right now with how long I can go before I get one of those. No matter what though it won't leave you stranded.
When the voltage dipped to 12.85, what was the high right before 14? I had a dip similar with the AtlasBX battery that went from 13.81 down to 12.69 then within a couple seconds went to 12.93. The time spent at 12.85 ws only a second or 2. Your graph showed a fall off then sitting at 13 then dropping before snap back. Looking for rate of change or time at various voltages for clue for the VCFront errors.
Before the dip to 12.85: the high was at 13.95 for 1hr, then 13.56 for 12min before going back to 13.95 for 2min, then down to 13.05 for 12min, then up to 13.12 for 10min.
The transient response may be correct. More data will tell. So far my plot looks yours between 1000 and 1500 (I only have a half day data so far. The wave pattern 2015 through 2225 on 7/10 and 1600 through 1805 on 7/11 has not appeared yet on my plot. What version software are you running?
I'm on 2022.16.3. Overall, it looks to me that the charging behavior has improved in that it's not overcharging as much, and the charging kicks back in when the 12V lithium is at a typical "time to recharge" SoC.
Here is 24 hours of my charging. Again right now its the AtlasBX but the wave form is different but consistent with spikes to charge. When I install the Ohmmu in a few days I will compare. Running 2022.12.3.20 the latest FSDBeta but still over a month behind your revision.
Good information. The one consistency is the inconsistency of charging profiles.
What I notice is the baseline charge level. For example, on mine is started at 14.1 (fully charged Lead Acid AtlasBX) reduced to 13.88 then after charging spikes to 14.02 it would settle at about 12.87 steady state. Even today short spikes to 14.16 then back down to 12.82-12.87 steady state. In your case, if not mistaken the battery was removed and tested then reinstalled. It started at 13.1 approx. and with several waves to 14.2 (approx) then after throwing several soft errors the voltage stabilized at 13.1 for long periods, tried two more charge curves to about 14 tossed more errors (soft ones) now has finally stabilized at 13.1 steady state with charging increases to 14 as needed then falling back to 13.1 steady state. I have a thesis but I want to see if any more errors soft or hard are generated on your car along with the data I collect on mine next week switching to the Ohmmu. For now I like the charging profile you now have. Let's see if it remains.
