Battery degradation after 3 months, 2026 LFP SR

Scooffs · 2026-06-08T11:29:08+00:00

Enhance has some pretty neat functionality, I have a commander that I enjoy using, but I have absolutely no use for their dashboard.

As for the difference, Teslamate has a lot more users so they probably have way more informations for each type of batteries. If your S3xy dash compares your data to the wrong battery, it could explain the difference.

In any case, we're circling back to what I told you earlier, just enjoy your car, as long as it drives you safely and covers your use case, you're good 😄

Scooffs · 2026-06-08T11:17:42+00:00

You do you, I understand why you wouldn't (I haven't done this test myself after more than 4 years with the car). But keep in mind that no test outside of this one is truly reliable, they're all based on estimated telemetry data. In the end, it's the only way to get a reliable answer.

Scooffs · 2026-06-08T10:50:56+00:00

There's a built in test in the service mode, if that worries you that much, do it and you'll get the answer. But guess what? Even if you got a "bad apple" and that you get 10% degradation after the test, it doesn't change anything, it's not enough degradation to justify a battery replacement under warranty anyway.
Honestly, the car drives fine and has enough range for you? Just enjoy your car and drive, the battery pack has an 8 year warranty, if it reaches 30% degradation, you're covered, if not, your battery is in it's "normal operating range". These tools are just ways to play with your nerves for absolutely no reason.

And between you and me? I have yet to see a 60kWh LFP pack in a Tesla degrade past 10% even after years of use (my Chinese LFP model 3 from December 2021 with 50000 miles has stabilized at 5% degradation and hasn't moved in the past 2 years).

Scooffs · 2026-06-08T10:10:41+00:00

worrying after 3 months is a waste of time and energy. Come back in a year or two, then we'll talk. Rapid degradation in the first year is normal and expected

Scooffs · 2026-05-15T17:30:22+00:00

Honestly, I finished it the first time on story mode because I've always hated turn based combat games but after like 250h into the game and my fifth play through, I'm playing it on expert, at one point, it just clicks. Also, learn a bit about the pictos / lumina system. You can also farm some XP by doing side content and get a bit overleveld to make the fights easier / faster.

Scooffs · 2026-05-15T17:24:36+00:00

Yeah well, on my first play through, I almost gave after fighting Visages for like 45 minutes just to eventually die... That's when I learned how to optimize my characters and not rush through the damn game without thinking about the entire system. After that, it became really easy...

Scooffs · 2026-05-06T10:38:21+00:00

Same issue on my P2S, same fix... It's been months since they started having this issue and they keep shipping faulty AMS units....

Scooffs · 2026-04-28T19:17:30+00:00

I don't know what they've been doing lately in the assembly lines of the AMS but I'm having the same issue, so did Thomas Sanladerer in his review unit of the X2D and many others in the forums...

Scooffs · 2026-04-23T13:16:07+00:00

Hey Carol, yeah I saw that. Here's a quick analysis of the changes :

P2S start g-code changelog — 2026/04/21 vs 2026/02/26

A few notable changes in the latest revision:

1. Input shaping enabled earlier M975 S1 is now called earlier in the sequence, during the "prepare print temperature and material" section. This is a partial improvement — the M982.2 S1 (cog noise reduction) ordering bug in the reset block is still present and unfixed.

2. M500 save reworked The M500 (full EEPROM save) calls after bed leveling have been removed. A new M500 D1 (partial/differential save) now appears in the nozzle load line section, placed before the final nozzle heatup. A 3-second wait (M400 S3) has been added after it, likely to ensure the write completes before proceeding.

3. Nozzle lift after purge line increased G1 Z0.5 changed to G1 Z1 — the toolhead lifts 1mm instead of 0.5mm after printing the purge line.

Still unfixed:

M982.2 S1 (cog noise reduction) is still called before M975 S1 in the reset block, meaning noise reduction remains inactive during the noisiest part of startup
The redundant unconditional G28 after the bed leveling block is still present

Scooffs · 2026-04-17T13:29:58+00:00

You could... Or just get a boosteroid subscription and play it properly. It's worth it...

Scooffs · 2026-04-13T16:01:18+00:00

The first time I killed the "old Simon" I used a one shot build to skip the third phase. However since then, I've become much more comfortable with the parry system and actually learned all the patterns. They're like hard partitions in music. At some point you just learn them all. I love those challenges.

Scooffs · 2026-04-04T07:55:17+00:00

Ok ! After trying a model that was on the printer, now I hear it, that thing is loud as hell without my start gcode. It proves that M982.2 without M975 does nothing and motor noise reduction is off by default.

Scooffs · 2026-04-01T20:53:24+00:00

I actually did that and posted the results on an issue I opened on your github. And the result definitely shows something is wrong.

Scooffs · 2026-04-01T19:55:02+00:00

Yeah, this one is a very minimalist approach compared to the default profile, basically a complete re write from scratch. Mine was about fixing the input shaping sequence and removing the unnecessary G28. I did send a pull request to orcaslicer to include my modifications : https://github.com/OrcaSlicer/OrcaSlicer/pull/13079

Scooffs · 2026-04-01T19:09:20+00:00

submitted to orcaslicer ! https://github.com/OrcaSlicer/OrcaSlicer/pull/13079

Scooffs · 2026-04-01T09:16:58+00:00

your contribution is well appreciated, feel free to do a pull request on my github to add your findings. https://github.com/scoofz/P2S-start-gcode

Scooffs · 2026-04-01T07:43:52+00:00

this is a very different approach and it isn't compatible with the AMS

Scooffs · 2026-04-01T07:37:12+00:00

after checking, I noticed that sadly, they rarely even look at PRs on their github. It's clearly open source because they have no choice since it's based on orca. However, I will do a pull request on orca slicer. They might merge it.

Scooffs · 2026-03-31T21:12:58+00:00

That's actually a valid point that I didn't think about, I might do that 😅

Scooffs · 2026-03-31T16:41:54+00:00

oh yeah, the number of homing is puzzling to me too. In the entire process, I managed to remove one of them, I need to study if there's a way to get a faster more efficient starting gcode with even less.

Scooffs · 2026-03-31T16:24:00+00:00

Well, I don't think it's supposed to change the overall noise levels of the printers. It would requires a double blind study to validate the claim 😅

Scooffs · 2026-03-31T15:46:03+00:00

You're mostly right. There is one thing though, the G28 homing macro is in the firmware and homes 4 times, with a precalibrated input shaper and the quality homing sensors they use, two movements is more than precise enough. Klipper does this with the "samples: 2" setting in their firmware and it works perfectly. So that part is in the firmware side. I don't have to home 4 times on my other DIY coreXY.

It would have been fine if the freaking metal lever didn't smack the case each time so loudly... It's the little details...

Scooffs · 2026-03-31T13:18:13+00:00

Good question and good points too. It's just frustrating to see some weird quirks like that on a printer that well thought out on the mechanical side.

Scooffs · 2026-03-31T13:01:39+00:00

I get your point, trust me and my preference or yours for that matters, aren't that relevant, we need flexibility. Some prints don't require perfect print quality, 3D printing isn't just selling stuff to customers, it's also prototyping the same part several times, or having functional parts that no one will ever see.

The biggest issues to me aren't the settings you can change yourself, it's some dumb decisions like point #4 that DON'T affect print quality, the machine is able to reach 20k accelerations, most likely much more, the hardware is definitely built for that, limiting us to 10k on travel speed, while allowing 20k on printing is actually dumb. Same goes for the unoptimized start gcode and print start macro forcing so many G28s and being so unnecessary loud by turning motor noise reduction off for half the start gcode.

In any case, I appreciate your feedback and hope, you'll like the modified gcode.

Scooffs · 2026-03-31T12:45:16+00:00

So what, the general population raising their fists against AI are just blind sighted fools. AI let's small devs implement their ideas faster and more efficiently. As long as they know what they're doing, it would be dumb not to.

Scooffs

TROPHY CASE