WasserGKuehlt
Well-Known Member
- Joined
- Sep 7, 2022
- Threads
- 5
- Messages
- 1,696
- Reaction score
- 1,909
- Location
- WA
- Vehicles
- 4CT, 996C2, MacanS
I thought I’d chime in with yet another opinion here. I’m not a hardware guy, but if I wanted to protect my product against tampering (or C my A against a claim), it would be trivial for me (==manufacturer) to detect a change: either of values, or of a module being replaced entirely.
As @whitex pointed out earlier, it’s really an issue of wanting to act on detecting a change, and also one of being able to detect it remotely (which, in this case, is not really important).
I’m not suggesting that this tune is visible necessarily to a dealer using a first-pass scanner, but let’s not pretend this is somehow write-only memory. Something has to act on that bit, and allow more current etc. (or however the power capping is implemented), and it should be obvious that those values (ie current, power) can be measured/recorded - that is, if the bit flip wasn’t audited in the first place.
Having said all that, I’ve already started the man-math calculations and planning on how to get this done - the upcoming IMSA race at Laguna Seca seems like a great opportunity to meet in person, and do proper A/B comparison (900mi drive each way should be plenty).
Lastly, Porsche did collect/record data on engine revs about ~20 years ago; I’m pretty sure they emit signals from all the car’s subsystems. I don’t necessarily think that not transmitting them to their backend is a sign of software weakness. Most of that data is noise most of the time, and a few outliers which may be interesting are perhaps nothing they haven’t seen in internal testing. I do see why such signals were essential for a new manufacturer trying new things (ie Tesla).
(edits for clarity)
As @whitex pointed out earlier, it’s really an issue of wanting to act on detecting a change, and also one of being able to detect it remotely (which, in this case, is not really important).
I’m not suggesting that this tune is visible necessarily to a dealer using a first-pass scanner, but let’s not pretend this is somehow write-only memory. Something has to act on that bit, and allow more current etc. (or however the power capping is implemented), and it should be obvious that those values (ie current, power) can be measured/recorded - that is, if the bit flip wasn’t audited in the first place.
Having said all that, I’ve already started the man-math calculations and planning on how to get this done - the upcoming IMSA race at Laguna Seca seems like a great opportunity to meet in person, and do proper A/B comparison (900mi drive each way should be plenty).
Lastly, Porsche did collect/record data on engine revs about ~20 years ago; I’m pretty sure they emit signals from all the car’s subsystems. I don’t necessarily think that not transmitting them to their backend is a sign of software weakness. Most of that data is noise most of the time, and a few outliers which may be interesting are perhaps nothing they haven’t seen in internal testing. I do see why such signals were essential for a new manufacturer trying new things (ie Tesla).
(edits for clarity)
Sponsored