I get ya just thinking what a super build it is but understand where you are going.
802SHO 2010 Build
- Thread starter 802SHO
- Start date
Disclaimer: Links on this page pointing to Amazon, eBay and other sites may include affiliate code. If you click them and make a purchase, we may earn a small commission.
I’m with you. And it seems inevitable but it’s like buying another used car. 12-15k. That’s around 4K just shipping the car back and forth. The complete wiring and all the hardware + tuning. It’s a massive undertaking and financial burden. It’s not really a matter of if…it’s when do I want to be out another 15k. And realistically not around the Holidays.
Realistic EMS Total for Your SHO
Low end (best case, minimal surprises): ~$17,500
Low end (best case, minimal surprises): ~$17,500
- Typical (with some options and a clean setup): ~$19,000–$21,000
- High end (all extras, display, extra logging, perfect install): $23k+
bpd1151
Lurking Around
Geezuz.
You and I BOTH need to start a GoFundme. LOL
Sent from my SM-S928U using Tapatalk
You and I BOTH need to start a GoFundme. LOL
Sent from my SM-S928U using Tapatalk
Hahaha! Well, usually estimates are free so maybe I can just get EMS to give me a “worst case scenario” estimate with shipping. I bet they have some sort of car hauler contacts. I say worst case bc that’s how life usually is. We are optimistic by design. Thinking something will go smoothly as we calculate time for a project when 9/10 it doesn’t go smoothly. Better to predict worse case and maybe get pleasantly surprised instead lol
Crazy. It's your money, though.
Honestly I’m inclined to step away I’ve been at it for a while. Has to be more to life than modifying my Ford Taurus
Not surprising. All this money invested but to make it really worth it need to spend another 24k? Spending more is the last thing I want to actually do. It gets tiring lol
bpd1151
Lurking Around
Welcome to the SHO platform my friend.
Even the SHO OG's will attest to this statement.
Sent from my SM-S928U using Tapatalk
The story doesn’t have to end. A pause though won’t hurt a thing if I need one.
So this is why I’m trying a new tuner with different software HpTuners. And I’ve challenged Brad and I am now about to get Brad 2.0. To me this is the right step. See what I can do with what I already got. There is a version of success with the OEM ECU, it’s just going to require work. Then move to MoTeC.
Yes PCMTec. I didn’t contact them directly but Unleashed Tuning Torrie did. He said my 2010 is not supported. I will say though, I found a report that PCMTec supports my Green Oak strategy …so there may be something there worth digging for, but direct contact with PCMTec.
Right now there’s hope. Brad back at it with a new rebuilt tune. Ryan Martin ready with HPtuners when I can unmarry my device and get a clean read and/or new strategy from Ford to give him.
Matt Robinson offered to take a crack at it and I’m going to let him. Time is dwindling away before the season ends. And I only drive it when it’s not raining. This entire last week the car sat and no rain at all all week. Now it’s about to rain every damn day next week.
No wipers or wiper motor is big reason why but also losing traction on logs bc it’s wet isn’t helpful.
Bronco2fan
SHO Member
Dude, I feel for you. I know you just want to get this thing done and run it down the track. We all want that for you too. But keep in mind what's realistically possible and go from there. Good luck.
the HP tuners are really nice units, when you see the software and the high capture rate they can tweak better. I will let the new tuner explain. their - HP - software is really nice.
Yeah even if still tuning in SCT I guess data logging in Hp you can see more of what the car is doing which can help make a better tune.
Look at this mega mind F. I am now a tech savvy detective. I am so over it right now.
Hello HP Tuners Team,
My name is Andrew Bullock. I have a 2010 Ford Taurus SHO (VIN: 1FAHP2KT6AG114990).
When I originally married my SCT X4 back in 2018, my PCM was running:
Recently, I updated my PCM using FORScan with the latest Ford calibration. My PCM now reports:
When attempting to read with my HP Tuners RTD4, I receive an “Unsupported” message. I understand SHO models from 2010–2019 are supported, but it appears my specific OS/revision (GUC / DMJKBL5) has not yet been mapped.
Vehicle Info:
Could you please add support for this calibration so I can complete a stock read and proceed with tuning?
Thank you for your help,
Andrew Bullock
I also want to note that I am using an RTD4 interface. When I attempt to read my PCM in VCM Editor Beta, the software immediately reports “Interface Unsupported.” It does not even retrieve my VIN or OS ID before failing.
This seems different from a normal “unsupported OS” case. It looks like the RTD4 interface itself may not currently support my application (2010 Ford Taurus SHO, PCM Calibration AU7A-14C204-GUC, Catch Code DMJKBL5, VIN 1FAHP2KT6AG114990).
Could you please confirm whether the RTD4 is intended to support 2010 SHO models? Or is this vehicle only supported with a full MPVI2/3 interface?
I feel like I am supporting myself at the moment thanks HPTuners.
Hello HP Tuners Team,
My name is Andrew Bullock. I have a 2010 Ford Taurus SHO (VIN: 1FAHP2KT6AG114990).
When I originally married my SCT X4 back in 2018, my PCM was running:
- Strategy/OS: Green Oak 2368K (older)
- Calibration Part ID: AU7A-14C204-GUB
- Catch Code: DMJKB52.H32
Recently, I updated my PCM using FORScan with the latest Ford calibration. My PCM now reports:
- Calibration Part ID: AU7A-14C204-GUC
- Catch Code: DMJKBL5
When attempting to read with my HP Tuners RTD4, I receive an “Unsupported” message. I understand SHO models from 2010–2019 are supported, but it appears my specific OS/revision (GUC / DMJKBL5) has not yet been mapped.
Vehicle Info:
- Year/Model: 2010 Ford Taurus SHO
- VIN: 1FAHP2KT6AG114990
- Current PCM Calibration: AU7A-14C204-GUC
- Catch Code: DMJKBL5
Could you please add support for this calibration so I can complete a stock read and proceed with tuning?
Thank you for your help,
Andrew Bullock
I also want to note that I am using an RTD4 interface. When I attempt to read my PCM in VCM Editor Beta, the software immediately reports “Interface Unsupported.” It does not even retrieve my VIN or OS ID before failing.
This seems different from a normal “unsupported OS” case. It looks like the RTD4 interface itself may not currently support my application (2010 Ford Taurus SHO, PCM Calibration AU7A-14C204-GUC, Catch Code DMJKBL5, VIN 1FAHP2KT6AG114990).
Could you please confirm whether the RTD4 is intended to support 2010 SHO models? Or is this vehicle only supported with a full MPVI2/3 interface?
I feel like I am supporting myself at the moment thanks HPTuners.
Like do I go back into forscan and flash my valve body to back to GUB? Will that even let me? Do I even need to go to Ford if HP doesn’t have the right configuration of operating system anyway for Green Oak with GUC? Bc that’s what Ford would leave me as. It’s almost like I essentially already have an update stock file.
One HP guru on FB immediately dismissed Forscan having any impact but has he tried with a 2010 with an update strategy ID? Bet your ass he hasn’t. HP will say it’s tune locked. No it’s not.
Didn’t think I’d have to out think Hp support on their own system. Matt Robinson said send me your info to my email and I’ll tune you in SCT. Email SENT
One HP guru on FB immediately dismissed Forscan having any impact but has he tried with a 2010 with an update strategy ID? Bet your ass he hasn’t. HP will say it’s tune locked. No it’s not.
Didn’t think I’d have to out think Hp support on their own system. Matt Robinson said send me your info to my email and I’ll tune you in SCT. Email SENT
Just trying to read a stock file shouldn’t take the complexity of building a pyramid ffs
Similar threads
