17 hours ago, Pib said:

For those interested in the EV "Battery Management System (BMS)" (and of course the EV battery) below are a few Youtube videos from a "BMS Engineer." He focuses more on how the "BMS" manages the high voltage battery.....that is, how the "electronics manages the battery cell chemistry. We all too often get engrossed in battery cell chemistry (i.e., NMC, LFP, etc) while overlooking the all important BMS which manages, protects, controls charging... etc...etc...etc.

Below are some starter videos from his Youtube channel. https://www.youtube.com/@shayan_ev

yep, great videos. highly recommend to watch, our Atto 3:

• 91.3% OBD2 reports this calculated SOH guessing from Ah.

• 89% BYD engineer reported from the BYD BMS diagnosis tools.

I did some research, even thou I have a massive loss of battery health (11%) it should stabilize and slow down. LFP degradation mostly occurs the first few years and then stabilizes chemically.

Gemini suggest this for an LFP battery in Thailand heat for my case:

100% SOH (Brand New)

──> 0 – 50,000 km: 0-10% Loss ───> SEI Formation & Active Lithium Consumption

──> 50,000 – 100,000 km: 3-4% Loss ───> Diffusion Barrier Engaged; Plateau Phase (Projected SOH: ~88%)

──> 100,000 – 200,000 km: 2-3% Loss ───> Steady-State Plateau (Linear Aging) (Projected Exit SOH: ~84.5%)

At 200K the SOH should be around 80% after the so called "SEI Layer passivation barrier"

The SEI Layer Passivation Barrier

When a graphite anode is first exposed to liquid electrolyte during its early life, a violent, irreversible reduction reaction occurs. This forms the Solid Electrolyte Interphase (SEI) layer on the graphite surface.

• This layer is a double-edged sword: it permanently traps a massive volume of active lithium ions (Loss of Lithium Inventory / LLI), which causes the early 8% to 10% drop.

• However, once the SEI layer achieves a specific critical thickness and density, it becomes a highly effective physical insulator. It blocks electrons and solvent molecules from passing through, effectively shutting down the very reaction that created it.

Then there the "Degradation Knee"

In battery engineering, the ultimate failure point is called the degradation knee—the point where the flat plateau suddenly snaps, and degradation turns sharply downward into an uncontrollable linear plunge. This knee occurs when the internal resistance (Ri) rises so high that localized lithium plating begins, destroying the cell geometry.

For modern LFP chemistry, this knee is safely pushed deep past the 2,000 to 3,000 full cycle mark (equivalent to 1,000,000+ km) or roughly 15 to 20 years of calendar life.

Because your maximum retention target is strictly capped at 200,000 km, you are exiting the vehicle precisely at the sweet spot: right at the end of its long, stable plateau, and years before the chemistry faces any risk of hitting the degradation knee. Your batter

16 hours ago, matchar said:

The Max looks reasonably priced. Same price as the base MG 4 though.

wow 100K more for the Ultra.

The Snapdragon 8155 processor and 3 Radars are quite expensive it seems.

The Max FWD seems like a really good deal thou.

15 hours ago, Pib said:

Just for others listening in, I've had my 2023 Atto 3 setup for ReverSharger AutoCharge for over two years now....works great.....and I got my new Sealion 7 setup for ReverSharger AutoCharge a few days ago.

And over the last couple days I setup PTT EV Station Pluz AutoCharge for the Atto and Sealion also....works as advertised. Plug-in...within about a minute the charging starts automatically...no need to even open the app to get the charging going. But to stop the charging before reaching 100% a person does need to manually stop the charging on the app or stop button on the charger.....ditto if I was using the ReverSharger charging network.

HOWEVER, for those who haven't setup AutoCharge yet on ReverSharger or PTT EV Station Pluz I will point out that on the PTT EV Station Pluz AutoCharge app setup "after", repeat after you get the EV registered/accepted on the PTT app for Autocharge the EV will "not" automatically Autocharge unless changing an EV Information settings to "Enable Auto Charge" and also selecting "Auto Charge by Starting Charging Automatically When Plugged In...." because during the AutoCharge registration process it defaults to the AutoCharge not enabled and also "Semi-Auto Charge (Press Start Manually)" setting.

So, a person will need to change the PTT app setting like identified below. Otherwise a person might think the AutoCharge "registration" process did not setup properly although the app did show registration was successful. That's what happened to me....for a short while I couldn't figure out why the Autocharge did not work although I successfully registered for Autocharge. While it indeed was successful it just the "default" setting of AutoCharge Not Enabled and also the Autocharge setting of Semi-Automatic can make a person think it did not setup properly.

Now with the ReverSharger AutoCharge once you register there are no other Autocharge settings required....it simply starts automatically.

So on the PTT app once successfully "registering" for Autocharge you will need to change an EV Information setting to make it truly Autocharging.

After registering for AutoCharge you will need to change an EV Information setting to "Enable Auto Charge" and also select "AutoCharge Automatically...." to make the Autocharge truly automatic; otherwise, it will be in Semi-Auto mode and you'll need to manually press a button to start the charging....see below.

Thank you! thought the station I used for charging didnt support it, but it was this settings all the time.

now I feel so dumb 😅

8 hours ago, brfsa2 said:

yep, great videos. highly recommend to watch....

Yeap...this guy produces some really good EV BMS & HV battery videos....a good combination of layman and technical talk mixed at just the right portions. Here's a couple more I recommend (but he has so many good videos on his channel).

8 hours ago, brfsa2 said:

yep, great videos. highly recommend to watch, our Atto 3:

• 91.3% OBD2 reports this calculated SOH guessing from Ah.

• 89% BYD engineer reported from the BYD BMS diagnosis tools.

Did a western Bangkok to Cha-am and Hua Hin O&A 381km round trip today in my 2023 Atto 3 Extended Range (60.5KWH battery, WLTP range 420Km.....had the EV now for 2 years 8 months / 71,178Km. On this 381km trip I used 94% of SOC...extrapolating that to 100% gives a real world range of 405km. A little short of the WLTP rating of 420km, however, I maintained speeds in the 90 to 105kmh range for a good portion of the trip plus I had the A/C set to 22C. Got up to 110kmh a few times for some short distances....but traffic just too heavy to do 120kmh except for some very short distances. On the way back to Bangkok there was "very light" rain (sprinkling) pretty much the whole distance which allowed for cooler driving without increasing rolling resistance.

Since the WLTP protocol has the A/C turned off and uses average speeds slower (including slow city driving speeds) than what I drove at today I'm happy with the real-world range results today. If I had not exceeded 90kmh I'm pretty sure I would have got the WLTP 420Km rating....maybe even around 430km. In the past I've got up to 442Km real world range and exceeded the 420Km WLTP range numerous times "with conservative, ECO mode, not exceeding 90kmh"driving. But crank the speed up to around 110 to 120kmh for a good portion of a trip and the energy usage goes way up in comparison to energy usage at 90kmh....and of course the range decreases significantly.

Summary: today was an overcast, cool day for driving which surely helped power usage-wise....now if I had made this trip in the Mar thru Apr time frame which is the hottest, brightest part of the Thai year I expect my real world range would have been around 10% less primarily due to the battery cooling and A/C systems working harder/using more electrons to keep the heat down.

Edited June 18Jun 18 by Pib

18 minutes ago, Pib said:

Did a western Bangkok to Cha-am and Hua Hin O&A 381km round trip today in my 2023 Atto 3 Extended Range (60.5KWH battery, WLTP range 420Km.....had the EV now for 2 years 8 months / 71,178Km. On this 381km trip I used 94% of SOC...extrapolating that to 100% gives a real world range of 405km. A little short of the WLTP rating of 420km, however, I maintained speeds in the 90 to 105kmh range for a good portion of the trip plus I had the A/C set to 22C. Got up to 110kmh a few times for some short distances....but traffic just too heavy to do 120kmh except for some very short distances. On the way back to Bangkok there was "very light" rain (sprinkling) pretty much the whole distance which allowed for cooler driving without increasing rolling resistance.

Since the WLTP protocol has the A/C turned off and uses average speeds slower (including slow city driving speeds) than what I drove at today I'm happy with the real-world range results today. If I had not exceeded 90kmh I'm pretty sure I would have got the WLTP 420Km rating....maybe even around 430km. In the past I've got up to 442Km real world range and exceeded the 420Km WLTP range numerous times "with conservative, ECO mode, not exceeding 90kmh"driving. But crank the speed up to around 110 to 120kmh for a good portion of a trip and the energy usage goes way up in comparison to energy usage at 90kmh....and of course the range decreases significantly.

Summary: today was an overcast, cool day for driving which surely helped power usage-wise....now if I had made this trip in the Mar thru Apr time frame which is the hottest, brightest part of the Thai year I expect my real world range would have been around 10% less primarily due to the battery cooling and A/C systems working harder/using more electrons to keep the heat down.

wow, impressive!

which tires are you on? it has to be the 215/55 right?

I think you're 100% right saying the cool weather made a 10% difference.

Right now, here in the south, with so much rain every 2-3 days, weather is 24C in the early morning, not over 33C in the day, with most of the days overcast or raining.

The Atto 3 is behaving very well while DC fast charging, easily can do 82-88kW up to 60-65% and I have not yet seen the battery go over 39C even when the wife is driving it like she stole it!

During the summer it was just terrible.

On 6/17/2026 at 7:34 PM, JBChiangRai said:

I booked a charger myself today and it appears you book connector by name (A or B).

If someone books (say) A and arrives early and plugs into B because it’s available (I did this today). The system isn’t clever enough to realize they have arrived and used a different connector.

The system should be able to figure this one out.

One of the few times we reserved with EV Station Pulz, we plugged in early, different cable head than reserved, and it did send a msg, to ask if we'd like to stay on that cable, instead of reserved cable, which we did.

Not sure if that's changed, or it was an older or newer software charging cable.

2 minutes ago, brfsa2 said:

wow, impressive!

which tires are you on? it has to be the 215/55 right?

I think you're 100% right saying the cool weather made a 10% difference.

Right now, here in the south, with so much rain every 2-3 days, weather is 24C in the early morning, not over 33C in the day, with most of the days overcast or raining.

The Atto 3 is behaving very well while DC fast charging, easily can do 82-88kW up to 60-65% and I have not yet seen the battery go over 39C even when the wife is driving it like she stole it!

During the summer it was just terrible.

Yes...still using the original 215/55 18inch Atlas (Batman) tires....heck, I think they are going to make 100,000km before hitting the wear/replace nubs

Yes sir, the time of year can make a big difference in the Atto's charging curve...and surely many other EVs. Where I said in my above post the hottest, brightest part of the Thai year is Mar-Apr, well, I meant to say Mar-May. I've noticed during the "HOT, HUMID" Mar-May period the Atto KWH usage per 100km is significantly higher than the rest of the year....and that also impacts the Atto's DC Fast Charger charging curve as the BMS reduces the normal max charging rates to protect the HV battery. Like the Atto can normally get a 80-88KWH charging rate up to around 65% SOC, if the weather is really hot the BMS seems to roll that 80-88KWH upper SOC range back to around 40% SOC.

And then from 40% SOC to around 85% SOC the charging rate will be around 40-50KWH versus the normal 57KWH from 65% to 85% SOC. Now the 85% to 100% SOC charging rate of around 32KWH seems consistent whether the weather is really HOT or cool.

Yea, time of year can definitely impact driving range and DC Fast Charger charging curve (depends on how hot the weather gets)...and based on my experience with my Atto for 2 yrs 8 months the Mar-Apr-May months in Thailand are the toughest on range and DC charging rates.

Edited June 18Jun 18 by Pib

11 hours ago, Pib said:

Yes...still using the original 215/55 18inch Atlas (Batman) tires....heck, I think they are going to make 100,000km before hitting the wear/replace nubs

215/55 profile is great for EV range, I'm on 235/45, which reduces my range by 3-4%, but it does improve the handling by a lot. I got Dunlop sportmax 060+ Japan quite cheap from Lazada.

I also replace the atto 3 wipers, I got some from Lazada, they are super smooth and quiet, really amazing, I'm impressed, way better than stock from BYD when car was new. I wish I had done it before.
"Bosch Aerotwin"

On 5/19/2026 at 8:55 AM, Pib said:

brfsa2,

Thanks ....the OBD encryption explanation makes perfect senses as to why I can only read a couple of very basic data elements and the way CarScannerPro made their Connection File note code. And something that really disappoints me is I will not be able to snapshot "fresh from the factory" key OBD data like the battery's starting amp-hour capacity, SOH, etc., which gives the starting reference point which I can compared later data to.

And other SL7 owners regarding the software/entertainment system "software version" running on my brand new SL7, it's Ver 1.0.0. When picking-up the car yesterday I asked the dealership is Ver 1.0.0 the "latest" as a numbering of "1.0.0" sounds like the numbering given to the first/original release of software....like when the SL7 was released in late 2024/early 2025. Surely, there has been a OTA update since then I asked? Heck, my Atto has went thru multiple OTA releases since late 2023 when I got the Atto.

The dealership sales person and also an actual dealership technician told me face-to-face Ver 1.0.0 is the latest version and an OTA update for Thailand SL7's has never been released. The technician said the original/initial software was so good it hasn't needed any update for Thailand so far---I'm not sure I buying that explanation but that's what he said.

Anyway, below is a snapshot of a version check I did just a few minutes ago....it once again said I'm running the latest-and-greatest firmware. May I ask other Thailand SL7 owners what software version their SL7 reports?

On 5/19/2026 at 9:20 AM, motdaeng said:

a few months ago i got the only OTA since february 2025: V3.0.0 / 2507, see picture ...

the sl7 in europe already has V3.2.2 !!!

as usual, we in asia / australia are the last ones to get an OTA ...

as far as i know, carscanner never worked for the sl7. the update mentioned by brfsa2 is for the seal, so carscanner can be used again ...

On 5/19/2026 at 2:39 PM, motdaeng said:

@Pib i just found that on facebook ... have a look ...

https://www.facebook.com/share/p/18nLt5mSNZ/

Regarding the latest Thailand OTA for the Sealion 7, above was some earlier posts on the subject....like when I picked-up my SL7 a month ago it was showing the latest Version as V1.0.0 like this was the original version when the SL7 come out around 2 years ago. When I questioned my dealership about this...that is, "This can't be the latest update?" they just said they can not update it at their dealership service center since the car is brand new; however, I would receive an OTA update in 2 to 3 weeks from Rever.

This all sounded fishy to me....like" throwing a stick for a dog to chase but then the thrower has disappeared when the dog brings back the stick." 😀 Anyway, I left with my new SL7 and I've only noticed one probable software glitch since then and that is the car and BYD app will only connect/update around 50% of the time "after the car has been turned off for at least a few minutes...sometimes it takes hours before it will not connect"...it's like the car goes into a deep sleep. Googling shows lots of SL7 owners experience the same problem....not only in Thailand but in other countries....it probably some software issue. I've found some workarounds for this issue which work pretty well most of the time, but I won't bore anyone with those. Now with my Atto I rarely have this issue....I have connectivity north of 99% of the time even if the car has been turned off for days and days.

But as @motdaeng pointed out above apparently when a SL7 is brand new/just came from the factory (like mine) the software/OTA version will reflect V1.0.0 even through it may/"probably" has a much later version installed and that V1.0.0 readout will not change until a person does receive/installs an OTA. A person could actually have a later version but it just does not display properly where the "simple, layman" version number is shown. However, when looking at the "more detailed/geek" readout of what version I'm running it shows 51.1.4.2603210.1 which means OTA full release number is actually a 21 March 2026 release (fairly hot off the press) which is probably a layman/simple version number somewhere "between V3.0.0 but below V3.2.0" based on my googling. See below as to what my SL7 shows...still shows it as of this morning.

What my brand new SL7 shows...picked it up a month ago

However, my dealership salesperson sent me a LINE message yesterday/19 June saying an OTA is coming soon....didn't say more than that. I started googling and ended-up on a SL7 Thailand Facebook page where a person showed some pictures of the OTA they got the other day. It showed the OTA for Thailand being released right now is V3.2.0 (layman) / "51.1.4.2604130.1" (detailed/geek) which is a 13 Apr 2026 release. I did several update checks on my SL7 this morning to see if I could force/trigger an update but it just came back saying I had the latest update installed. But these updates are staggered...hopefully I'll get it over the coming weeks.

From a Thailand SL7 Facebook page...shows V3.2.0 OTA received a few days ago

Edited June 20Jun 20 by Pib

7 minutes ago, Pib said:

I've found some workarounds for this issue which work pretty well most of the time, but I won't bore anyone with those. Now with my Atto I rarely have this issue....I have connectivity north of 99% of the time even if the car has been turned off for days and days.

what was your workaround? Just curious.

The atto 3 seems to have a simpler but more stable operating system, it's been out for a very long time as well. the best update the atto3 got was the one that added dynamic range estimation, I cant understand how that car got QA passed having a fixed range display.

on the Atto3, one trick to hard reboot the whole system (poweroff doesnt reboot) is to press down the volume button and hold it. it worked for me one time I couldn't use bluetooth.

2 minutes ago, brfsa2 said:

what was your workaround? Just curious.

The atto 3 seems to have a simpler but more stable operating system, it's been out for a very long time as well. the best update the atto3 got was the one that added dynamic range estimation, I cant understand how that car got QA passed having a fixed range display.

on the Atto3, one trick to hard reboot the whole system (poweroff doesnt reboot) is to press down the volume button and hold it. it worked for me one time I couldn't use bluetooth.

Now the options/menu shown on the BYD App for the SL7 and Atto are "not" exactly the same as each car has different hardware/software capabilities, therefore, the app menu/settings will be somewhat different...vary between models..

Anyway, I found that if the BYD App gives that generic "weak network connection...." message when it can't fully (or at all) communicate with the car that if clicking the "Schedule" icon on the app (which deals with scheduling a charging session) and then enabling/disabling the setting that forces the app and SL7 to give a real time update....update everything to the current time whereas with no/partial connectivity it would show an earlier status...or maybe just not connect. This workaround worked the "great majority of the time" when I was not getting connectivity...getting that "weak network" BS message.

I also found that "sometimes" just pressing the flash headlights or beep horn icon or turn on A/c would force an update to the current time. But using the Schedule icon setting (which the Atto doen't have in the app) worked the "great majority of time" (not always...just the great majority of time).

And where I keep saying "no connectivity" I expect (guessing) the car and app are indeed connecting each and every time, HOWEVER, it the car's CANS/OBD2 system that's went to sleep (partially) to save low voltage battery power/usage when the car is turned off. And when the car SIM/Wifi communications circuit asks the CANS/OBD2 system for an updated status when the CANS/OBD2 does not give an answer (because it's asleep) then the SIM/Wifi circuit gives a response to the app that shows as a "weak network....." BS type message. However, if asking for an update like using the "Schedule" icon it somehow wakes up the CANS/OBD2 system to give an answer to the car SIM/Wifi circuit which in turns give a non-BS answer to the app.

And just of those who don't use the BYD app whenever you open the app or refresh after opening it's suppose to "update/show" the car current status "as of real time." Like below where I opened the app at 11:02am and the app updated to show the car's status as of 11:02am....as of real time. That's the way it's suppose to work.

However, if it doesn't update to the current time the Updated status will show an earlier date/time OR you'll get a Weak Network.... type message. Sometimes just refreshing the app page will force an update....sometimes you may not get an Updated status to real time but the icons like start A/C, flash lights, etc., will still work properly....but other times you just can't get the app and car to communicate with each other to do anything other than give a "Weak Network...." message and/or show a status from earlier. If you wanted to start the A/C to cool down the cabin before getting back to the car you were just SOL...but as soon as you started the car the car & app were on full talking terms again.

System version: 51.1.4.2507220.1

@Pib I've never had a weak network signal message. :)

33 minutes ago, carlyai said:

System version: 51.1.4.2507220.1

@Pib I've never had a weak network signal message. :)

What layman version is that 51 number. Is it Ver 3.0.0, etc?

12 hours ago, Pib said:

What layman version is that 51 number. Is it Ver 3.0.0, etc?

Couldn't find that Ver with my quick skim read check.

My system version # seems to be 2025.

My updates have mainly come from my visits to the BYD dealer. The mechanic hooks up his computer and updates my system. Last update was Google Maps and a heap of apps.

No idea how the OTA updates and the human updates differ but having had experience finding an intermittent computer fault in a Honda I know that the information displayed with the human interface is extensive. (Forget the name of the car interface bus...OBD or something like that...still have the tester).

4 hours ago, carlyai said:

Couldn't find that Ver with my quick skim read check.

My system version # seems to be 2025.

My updates have mainly come from my visits to the BYD dealer. The mechanic hooks up his computer and updates my system. Last update was Google Maps and a heap of apps.

No idea how the OTA updates and the human updates differ but having had experience finding an intermittent computer fault in a Honda I know that the information displayed with the human interface is extensive. (Forget the name of the car interface bus...OBD or something like that...still have the tester).

Go in Vehicle Settings (the little car icon), then press Version, and then press Upgrade.

After pressing Upgrade it will check to see if a later version is available OR say you have the latest version number of Version XYZ (the layman's version)....a window will popup in the middle of the screen giving this info. You may have to repeat the "press the Upgrade icon" action multiple times before you get one of above replies. Wait about 5 seconds between tries.

Normally on the SL7 I get a reply within just a couple of tries...sometimes the first try. BUT on my Atto 3 it can take numerous tries...even up to approx a dozen tries although it normally comes back with a reply after a half dozen tries.

The layman's version number (like V3.0.0) that will eventually appear (normally after several tries....maybe the 1st try if lucky) in the popup screen is not to be confused with the long number of approximately a dozen digits (the geek number for the version number) shown on the left hand side of the screen....this long number always appears when going to below menu area.

35 minutes ago, Pib said:

Go in Vehicle Settings (the little car icon), then press Version, and then press Upgrade.

After pressing Upgrade it will check to see if a later version is available OR say you have the latest version number of Version XYZ (the layman's version)....a window will popup in the middle of the screen giving this info. You may have to repeat the "press the Upgrade icon" action multiple times before you get one of above replies. Wait about 5 seconds between tries.

Normally on the SL7 I get a reply within just a couple of tries...sometimes the first try. BUT on my Atto 3 it can take numerous tries...even up to approx a dozen tries although it normally comes back with a reply after a half dozen tries.

The layman's version number (like V3.0.0) that will eventually appear (normally after several tries....maybe the 1st try if lucky) in the popup screen is not to be confused with the long number of approximately a dozen digits (the geek number for the version number) shown on the left hand side of the screen....this long number always appears when going to below menu area.

Thanks, didn't press enough. 555.

As per a video, I'm doing my Sunday 100% charge so will have a look at the version again later after 1400hr, should be fully charged.

19 hours ago, carlyai said:

Thanks, didn't press enough. 555.

As per a video, I'm doing my Sunday 100% charge so will have a look at the version again later after 1400hr, should be fully charged.

Did that yesterday but after many presses still says 'checking ..... ' then nothing. Will take the car out in the open today and try again. (There is a signal black spot about halfway down our soi which could be effecting the OTA).

2 hours ago, carlyai said:

Did that yesterday but after many presses still says 'checking ..... ' then nothing. Will take the car out in the open today and try again. (There is a signal black spot about halfway down our soi which could be effecting the OTA).

Keep trying...hopefully BYD will grace you with an answer soon....BYD cars and cloud servers are known for not being able to communicate properly 24/7....with a high reliability rate. Kinda like a website you can't reach 100% of the time but some percentage far south of 100%. 😁

If your BYD app and car communicate with each other OK (that is, you don't get the weak network type message) then "connectivity" is not the issue in not being able to complete the version update check if the app can talk to the car then the BYD software update servers should be also able to talk to the car.

And actually, even if getting the weak network signal based on my testing on my SL7 "and" Atto using mobile, Wifi, and Hotspot connections it does not necessary mean the app and car are not communicating. Instead, it just means the car heard the question from the app but just didn't give an answer for some reason. So, an unrelated response of weak network signal is given instead. It's like "Yes, I heard you but I'm not going to answer that question....maybe ask me another question and maybe I'll answer that particular question....OR, ask me the same question "numerous times/over and over" and I'll finally answer the question....OR, maybe I just continue to give a seemingly unrelated response (i.e., weak network) to any question you ask. It's kinda like the car/app simply can't respond with a "No" and instead gives a "beat around the bush" type answer.

Plus, if you park close to your home Wifi signal then the car and BYD servers/app can communicate with each other that way version needing a cell tower signal. Or, using your phone's Hotspot to connect to the car's Wifi circuit. Yea, a BYD vehicle has numerous ways for a communications signal to go back and forth but sometimes a person simply can't get any of those communications channels to work properly.

But hey, enough of my moaning about the app/the car talking to the BYD cloud...back to the OTA version check where the app is not even being used. When doing an version update check the car is just sending some info to BYD servers saying here's my identifying info and my current software version....Is my version the latest version?. If not, then please send me the latest version so I can upgrade.

If you do have the latest version then the version update check comes back and says such along with showing your current version number....OR, if you do not have the latest version "but" BYD servers have you in their queue to receive the update at a later date (i.e., a batch type release...just so many upgrades per day worldwide) then the BYD servers will still respond with a "you have the latest version."

Doing a simple version check shouldn't be this hard, but based on my person experience with my two BYD vehicles and what MANY others on social media have posted, OTA version checks/upgrades can sometimes be like hitting a brick wall....but for others it's always smooth sailing.

This morning while chauffeuring the wife and waiting for her while she ran into a food shop to grab some food I did a Version check on my 2023 Atto 3. Took 6 tries with waiting about 5-10 seconds between tries before it responded with the "version" answer of V1.10.1 (layman's name for the version) and the number I have installed as being the latest version.

Now, the geek version number consisting of the dozen or so digits appears immediately when going into the Version menu....even before pressing the Upgrade icon to do a version check. But since everyone on social media seems to always talk the layman's version number that long geek version number doesn't help a person a lot unless they know geek number so-in-so corresponds to layman's number so-in-so.

Anyway, based on my Atto 3 software version check this morning the latest version for Thailand Atto's is V1.10.1 dated 25 Mar 2025 (get the date from part of the geek version number). And if I remember right that actually installed around June 2025. Or at least that should be the latest version for a Thailand 2023 Atto 3....maybe later year model Thailand Atto 3's have a newer/different version number. Can't say as BYD does not publish a public master list of what the latest updates are.

2 hours ago, carlyai said:

Did that yesterday but after many presses still says 'checking ..... ' then nothing. Will take the car out in the open today and try again. (There is a signal black spot about halfway down our soi which could be effecting the OTA).

V3.0.0

to share a Car scanner tip i learned, I wanted to have a dashboard for power %, for example, when i use 80kw out of the 160kw motor i wanted to see 50% and as well record over a trip to see how mw and the wife drives. For fun. I have this spare phone i keep on the car to show this dashboard automatically.

You can do this way in CarScanner:

I named it power %.

And 160 is the value depending on eqch car max power

Edited June 22Jun 22 by brfsa2

From looking at what @motdaeng and @carlyai have posted regarding what their SL7 software version check reports and what I've found on Facebook and other social media sites the layman and geek version numbers are below:

Geek Version of :_____ Corresponds to Layman's version of:

51.1.4.25072220.1_____V3.0.0

51.1.4.26032101.1._____V3.1.1

Note: what came installed on my new SL7 I bought about a month ago in mid May 2026.

51.1.4.2604130.1_____ V3.2.0

Note: started being released/received in Thailand a few days ago according to Thailand SL7 Facebook pages where some folks posted snapshots of their OTA update install...and my dealership telling me late last week a new OTA is arriving Thailand.

In the geek version number, the date of release can be seen like where it shows 250722 (meaning 22 Jul 2025) located the middle part of the complete number. Now this date in the release number does not mean that's when BYD actually released/began pushing the OTA to the public as the actual release date is typically days to months later.

Edited June 22Jun 22 by Pib

1 hour ago, Pib said:

From looking at what @motdaeng and @carlyai have posted regarding what their SL7 software version check reports and what I've found on Facebook and other social media sites the layman and geek version numbers are below:

Geek Version of :_____ Corresponds to Layman's version of:

51.1.4.25072220.1_____V3.0.0

51.1.4.26032101.1._____V3.1.1

Note: what came installed on my new SL7 I bought about a month ago in mid May 2026.

51.1.4.2604130.1_____ V3.2.0

Note: started being released/received in Thailand a few days ago according to Thailand SL7 Facebook pages where some folks posted snapshots of their OTA update install...and my dealership telling me late last week a new OTA is arriving Thailand.

In the geek version number, the date of release can be seen like where it shows 250722 (meaning 22 Jul 2025) located the middle part of the complete number. Now this date in the release number does not mean that's when BYD actually released/began pushing the OTA to the public as the actual release date is typically days to months later.

I was curious and asked Gemini for a SL7 OS changelog:

51.1.4.25072220.1 ——— V3.0.0 / V3.0.1

• Compilation Date: July 22, 2025 (foundational factory baseline)

• Deployment Horizon: Q3/Q4 2025 (Initial Global Launch Baseline)

• Core Logic Infrastructure: Implemented initial optimization layers for the DiLink 100 platform running on the 6nm Qualcomm Snapdragon processor architecture.

• ADAS & Telemetry Integration: Established initial calibration curves for the DiPilot 14 Advanced Driver Assistance Systems (ADAS), managing baseline lane-keeping assistance (LKA) and adaptive cruise control (ACC) sensitivity logic.

• Localization Stacks: Embedded fundamental linguistic packs and regional maps for the standard integrated navigation engine.

51.1.4.26032101.1 ——— V3.1.1 (Iterative patch of V3.1.0)

• Compilation Date: March 21, 2026 (Baseline branch compiled late November 2025)

• Deployment Horizon: Spring 2026

• Objective: A performance optimization and communications subsystem refinement patch.

• Wireless Protocol Fixes: Refined Bluetooth pairing handshake protocols and optimized the internal packet routing for wireless Apple CarPlay and Android Auto projection layers to alleviate intermittent connection drops.

• Navigation Network Optimization: Resolved a memory leak in the local map navigation layer that previously led to degraded UI rendering speeds over continuous long-range routes.

• Chassis & DiPilot Tuning: Adjusted threshold filtering for the ADAS forward-facing cameras to reduce false-positive Automated Emergency Braking (AEB) interventions in dense urban conditions.

51.1.4.2604130.1 ——— V3.2.0 (Superseded by V3.2.2 revision)

• Compilation Date: April 13, 2026

• Deployment Horizon: May/June 2026

• Objective: A major feature introduction update targeting vehicle lifestyle management, diagnostic sub-systems, and localized thermal management behaviors.

• "Scene Mode" Expansion Suite:

  • Camping Mode: Implemented a persistent low-voltage DC-DC converter state to continuously power interior climate control systems, the primary infotainment stack, and exterior Vehicle-to-Load (V2L) output loops without triggering the vehicle's standard auto-shutdown timeouts.

  • Nap Mode: Configured a macroeconomic automation routine adjusting interior ambient lighting profiles, motorized seat ergonomics, and acoustic white-noise playback to facilitate rapid rest states.

    YouTube

• Trailer Control Module Sub-layers:

  • Added configuration settings for customized Trailer Weights within the driving dynamics configuration menu.

  • Integrated Trailer Monitoring Systems, enabling diagnostic lamp-failure alerts directly via the driver's instrument display panel if an open circuit or bulb failure is detected on the towed assembly.

• Microphone Peripherals Support: Added a local driver layer to support the hardware integration of official BYD wireless UHF karaoke microphones into the media stack.

• HVAC Defogging Adjustments: Modified the logic determining intake selection (recirculation vs. fresh outside air) during humidity-spike detection events to optimize front windshield clearing efficiency.

Next V3.2.3 (The next active deployment hitting the global fleet)

This is a minor iterative update targeting localized charging controls and safety interface behavior. The primary changes in this stack include:

• Manual AC Charging Current Throttle: Introduces a manual toggle within the charging menu allowing the user to limit the maximum AC current draw (e.g., throttling down from 16A/32A). This prevents overcurrent tripping on unstable or shared residential circuits.

• Integrated TuneIn Radio App: Native implementation of the TuneIn streaming platform directly within the BYD App Store, decoupling internet radio streaming from third-party mobile projection.

• Trailer Speed Limit Suppression: Removal of the rigid, hard-coded speed limit restrictions previously enforced when the trailer module wiring harness was engaged, shifting control to advisory alerts instead.

• Blind Spot Monitoring UI Calibration: Change of the Blind Spot Detection (BSD) active status icon geometry and color palette (shifting from yellow to green states) to reduce visual clutter on the cluster during high-density highway lane tracking.

• Audio Routing Optimizations: Patches a bug where the audio source prioritization engine would drop streaming playback (specifically targeting Spotify cache issues) upon sudden cellular baseband handovers.

  Source: https://www.reddit.com/r/BYD/comments/1u3ox84/byd_ota_update_via_app/

I think the Camping Mode for SL7 is an amazing feature to have if not already there.

Camping Mode: Implemented a persistent low-voltage DC-DC converter state to continuously power interior climate control systems, the primary infotainment stack, and exterior Vehicle-to-Load (V2L) output loops without triggering the vehicle's standard auto-shutdown timeouts.

as i have said several times before, i love my sealion 7 awd, but when it comes to software, byd still leaves a lot to be desired ...

i have had the car since february 2025. the first and only OTA update arrived at the end of september 2025, which installed 2507 V3.0.0.

a few weeks ago, i read that the service center could perform a software update, so i unfortunately had it done on june 12. there were hardly any noticeable improvements. still no camp mode, no google maps, no improvement on the map, and no other important useful new features ...

for me, this update was basically useless. it reset many of my settings and brought no real benefits. my current version now shows 2602 V1.0.0 !!! (back to field one?)

my advice: wait until you can install the official OTA update yourself in the car, rather than getting the service center involved. that's certainly how i will handle it in the future ...

My SL7 is 52.4.2507240.1

V3.0.0

Edited June 22Jun 22 by JBChiangRai

1 hour ago, motdaeng said:

when it comes to software, byd still leaves a lot to be desired ...

This is a reason some people choose Tesla over BYD, even with the high Tesla premium, many friends had Tesla, I know at least a dozen, they all praise the software how awesome it is, specially Sentry mode. All Teslas have it.

whereas most Chinese OEMs are gating software features, doing hardware reduction for exports, no LIDAR, and even suspension is not the same, ADAS very basic over here because of crappy basic chipset, they have to strip the support for local AI infrastructure present only in China and low latency.

Tesla maintains uniform core software and hardware across its entire fleet all over the world. That... is Amazing !

Me: would buy model 3 long range without a hesitaiton right now, with really good range .

Wife: hates the looks, a hard no, so fine then, she is the boss! get the IM5 :D

Edited June 22Jun 22 by brfsa2

1 hour ago, brfsa2 said:

This is a reason some people choose Tesla over BYD, even with the high Tesla premium, many friends had Tesla, I know at least a dozen, they all praise the software how awesome it is, specially Sentry mode. All Teslas have it.

whereas most Chinese OEMs are gating software features, doing hardware reduction for exports, no LIDAR, and even suspension is not the same, ADAS very basic over here because of crappy basic chipset, they have to strip the support for local AI infrastructure present only in China and low latency.

Tesla maintains uniform core software and hardware across its entire fleet all over the world. That... is Amazing !

Me: would buy model 3 long range without a hesitaiton right now, with really good range .

Wife: hates the looks, a hard no, so fine then, she is the boss! get the IM5 :D

Well done for not buying a Nazi Swasticar

0 to 1939 in 4 seconds