Printable View
We implemented basically every version we can get our hands on. Unfortunately it's very difficult to get a comprehensive database of stock files. We implemented the read functionality for exactly this reason, expecting that unknown files would flood in and we can add support as quickly as possibleQuote:
Originally Posted by AtlasTuned
As of Beta 5.1.4634, I have not been able to read my stock tune yet, either 'read entire' or virtual. I see there's a new MG1CS055 hardware set for 2025+ Fords, which would be me, and is a new addition. Neither this nor MG1CS036 are working for me quite yet, however the fail code for MG1CS055 is that I'm 'Not Authorized', but I have 4 universal credits to spend on marrying MPVI3 to car.
OS of my 2025 GT PP is SR3A-14C204-AEC; has that been added to the mix yet?
Thanks!
Rob, is there anyway around writing entire with the Beta? Will "write calibration" be available in the future?. Write times right now for the MG1 on my F150 takes quite awhile right now. Just curious.
5.1.4636 still not reading ECU/downloading virtual for 2025 GT PP OS: SR3A-14C204-AEC
RR3A-14C204-LH not reading virtual or from PCM directly
2024 mustang gt 5.0 10r80
5.1.4636
So far Ive been able to read every single one that I was able to laid my hands on - today did 6th.
Any rhyme or reason to it? Automatics vs manuals? Trims? This is using the MG1CS036 hardware? Which beta version?Quote:
Originally Posted by veeefour
Have you got any manual 2024+ Mustang reads that you're willing to share?
Hang tight everyone, we made good progress today
in or out of the car VEE?
The "2025+ Ford" thing isn't meant to be taken 100% literally. The 2024 Mustang GT is an MG1CS036, the 2025 F150 is an MG1CS055, no real rhyme or reason. The unauthorized message is correct as we have not released this controller yet.Quote:
Originally Posted by Abilor
Just released VCM Suite beta 5.1.4648, let me know. We confirmed on a few cars but it's very difficult to tell if this is a 100% fix since the issue is seemingly random and inconsistent.
Hello. I also received check-sum error on Whippled 24 dark horse. RR3A-SEMWS2-ML. Latest Beta 5.1.4648 allowed to read. Prior versions would fail on the read.
Yep, we just need to add definition support for it. Send it via supportQuote:
Originally Posted by gerrygmendez2
Submitted #499970 Thank you!Quote:
Originally Posted by Rob@HPTuners
Not all Whipples are not in system yet still working on itQuote:
Originally Posted by gerrygmendez2
Mg1cs036 RR3A-14C204-AND read ok , with last uptade 5.1.4650 Beta, only checksun definition is missing, I've already sent it to support!Quote:
Originally Posted by Rob@HPTuners
5.1.4650 downloaded stock tune in under 5 minutes, but still failed checksum. Sent updates and logs to #499154 ticket. Thanks!
I know you guys already know this but just to clarify for anyone else reading. If you get to a checksum validation issue, that means that the PCM read successfully and generated a file. This is expected on any file that doesn't match our database (which is many of them because these cars are practically brand new). We'll continue updating the database as files come in.
A failed read in this context would be if the progress bar halts midway through the process and a file isn't generated. But it looks like this is more or less fixed at this point
Thanks Rob!!Quote:
Originally Posted by Rob@HPTuners
5.1.4654 able to read ECM file, but still fails checksum... OS: SR3A-14C204-AEC #499154
read the file well and now it's ok! thanks hptuner 5.1.4660 RR3A-14C204-AND
SR3A-14C204-AEC still a no-go with 5.1.4665. Wow, how many versions are there?
4,665 versions of beta. I recommend you open a support ticket if your .hpt file doesn't open.Quote:
Originally Posted by Abilor
Hehe, your guys are sick of my sh1t Bill! Ticket #499154. I've been sending .HPTs every time I fail checksum, and they informed me yesterday that once is enough, the engineer has it already, PLEASE STOP.Quote:
Originally Posted by Bill@HPTuners
Sorry, should have been more specific: how big a queue of S650 different types/OSes do your engineers still have to load? Feels like I'm at the end of the line.Quote:
Originally Posted by Bill@HPTuners
Your call will be answered in the order received..Quote:
Originally Posted by Abilor
(spoiler alert, this is HUGE news so it's going to take some time for the engineers to work their magic. I'm sure they'd appreciate a little grace and patience while they work through what has to be HUGE list of OS to code)
Yeah, you're not wrong. In the meantime, just accepted a Ford update, and update did not help, sadly. OS/Calibration ID changed from SR3A-14C204-AEC to SR3A-14C204-AED though.Quote:
Originally Posted by Justinjor
I am over here like a little kid at Christmas waiting for this support ticket to update. LOL
5.1.4673 allowed me to read my ECU finally; I was even able to load my previous OS after an OTA update, successfully writing stock map back to ECU as a sort of "Hello, World" exercise, and marry my credits to this MPVI3 and VIN. Thanks so much to engineering team!
Now on to learning how to tune S650s, lol...
Has anyone pulled a stock darkhorse file yet they can share?
fyi update to latest version and there tune in these thread
I pulled that one up, but thought it was listed as a GT so I wasn't sure. I did see a few points where it had more a smidge more timing than the GT I'm working on but it looked more like an update.
is it normal for it to ask me what hardware to select? It?s not auto filling what hardware lolQuote:
Originally Posted by Rob@HPTuners
It can happen, it depends on how the vehicle identifies and what we have in our databases. For an S650 Mustang GT, you can select MG1CS036. 24+ F150 is MG1CS055. If you're unsure there won't be any harm in trying both, only one will work successfullyQuote:
Originally Posted by Alex14SS