- Thread starter
- #1
Hi all — I recently purchased and applied a “91 daily” tune from 5Star Tuning on my 2022 Bronco Sport Badlands. I have just under 12K miles on it, and this vehicle is otherwise stock from a tuning perspective.
The programming was done with my SCT X4 that I originally bought for my 2016 F150 3.5 EB (I do something else for tuning there so not “married” to it any longer). Anyhow, I have not used it for tuning since then, and the handheld update took nearly 6H to complete (seems like a bottleneck on their end)! It did work, however — but there was some real doubt along the way! Something to note/prep if you go this route…
So, I was curious if anyone else has used 5Star Tuning on the 2.0 EB motor here for the Badlands. I saw old references to third-parties, but nothing current by a member. I’m particularly interested in data logging results with short and long-term fuel trim results (and related AFR), boost levels, and indicators of performance with the stock intercooler and turbo. Instrumented testing results would be nice too.
Since I was not able to find much on our current Bronco Sport Badlands platform, I was looking at some results from the Ford Focus 2.0 EB. I don’t know how similar these engines are, but at a high level they seem very similar (unclear on software differences). That is backed up by the fact that the guys at 5Star Tuning feel the same way about it (and betting they borrow heavily from that knowledge base).
Anyone else running these maps here? I also bought an “87 octane daily” map to go with my “91 octane daily” map, and it is pretty much their off-the-shelf tune with the exception of my request to deactivate traction control by default. I think they did it, but it does not toggle the dash “lamp” indicator as you might expect. I have asked Support about that and waiting to hear back…
I live in AZ in a mountain ranch environment and find myself deactivating traction control every time I start up. I’d also like to change GOAT modes by default, but that doesn’t seem possible quite yet (I could not find it in FORSCAN) and the 5Star guys don’t know either. Apparently Adam (on their team) has a Bronco of some kind and was also interested in doing that but has not found success yet.
My initial test drive with logging was interesting. It seems faster, but I didn’t record before/after results. I can hear more compressor bypass sounds now, that’s for sure. I only did a few pulls and saw 19 PSI before it became heat soaked. When warm, seems like it would pull about 15 PSI. What boost values are you seeing in stock trim? I see “1” for my current short and longterm fuel trim results, and I’m happy with that. I didn’t hear any pre-ignition and understand the factory strategy for knock detection remains in place.
If you have experiences here, I’d like to hear from you. Thanks!
Note: I’m just under 5K feet in terms of elevation, and ambient was about 75F during my test (~16% relative humidity)
*I have a PCV oil catch can on my 3.5EB F150 (model specific application) and would consider one here, but that is specifically called out as needing a revised tune and that surprises me. That might be a clue on differences with this implementation.
The programming was done with my SCT X4 that I originally bought for my 2016 F150 3.5 EB (I do something else for tuning there so not “married” to it any longer). Anyhow, I have not used it for tuning since then, and the handheld update took nearly 6H to complete (seems like a bottleneck on their end)! It did work, however — but there was some real doubt along the way! Something to note/prep if you go this route…
So, I was curious if anyone else has used 5Star Tuning on the 2.0 EB motor here for the Badlands. I saw old references to third-parties, but nothing current by a member. I’m particularly interested in data logging results with short and long-term fuel trim results (and related AFR), boost levels, and indicators of performance with the stock intercooler and turbo. Instrumented testing results would be nice too.
Since I was not able to find much on our current Bronco Sport Badlands platform, I was looking at some results from the Ford Focus 2.0 EB. I don’t know how similar these engines are, but at a high level they seem very similar (unclear on software differences). That is backed up by the fact that the guys at 5Star Tuning feel the same way about it (and betting they borrow heavily from that knowledge base).
Anyone else running these maps here? I also bought an “87 octane daily” map to go with my “91 octane daily” map, and it is pretty much their off-the-shelf tune with the exception of my request to deactivate traction control by default. I think they did it, but it does not toggle the dash “lamp” indicator as you might expect. I have asked Support about that and waiting to hear back…
I live in AZ in a mountain ranch environment and find myself deactivating traction control every time I start up. I’d also like to change GOAT modes by default, but that doesn’t seem possible quite yet (I could not find it in FORSCAN) and the 5Star guys don’t know either. Apparently Adam (on their team) has a Bronco of some kind and was also interested in doing that but has not found success yet.
My initial test drive with logging was interesting. It seems faster, but I didn’t record before/after results. I can hear more compressor bypass sounds now, that’s for sure. I only did a few pulls and saw 19 PSI before it became heat soaked. When warm, seems like it would pull about 15 PSI. What boost values are you seeing in stock trim? I see “1” for my current short and longterm fuel trim results, and I’m happy with that. I didn’t hear any pre-ignition and understand the factory strategy for knock detection remains in place.
If you have experiences here, I’d like to hear from you. Thanks!
Note: I’m just under 5K feet in terms of elevation, and ambient was about 75F during my test (~16% relative humidity)
*I have a PCV oil catch can on my 3.5EB F150 (model specific application) and would consider one here, but that is specifically called out as needing a revised tune and that surprises me. That might be a clue on differences with this implementation.
Sponsored
