When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
Recently installed X3 from 5 Star, and have been working with AutoEnginuity to try and get cylinders 9,10 to show up for misfire counters and injectors...
I now have these following error codes having to do with the Hybrid Electronic Cluster:
U1058, U1059, U1262, U1027. They dont show up on the SCT device, But they do show with AE tool. No actual problems with cluster noticed...
Anyone else with the SCT and AE notice any of this? Am I the only one?
Kind of irritating. Especially if I actually have a problem in this area in future huh.
Did the AutoEnginuity do this BEFORE uploading the 5-star custom tune to the PCM?
I see the AE does the "enhanced" stuff so you can read the cluster, ABS, GEM, etc. Which is exactly why the SCT doesn't pick those cluster codes up - it can't read cluster codes
Hey ! I got a reply ! Thank you ! Krewat- your the one I was hoping to hear from as well... Thought I remembered you had AE.
I dont believe the codes were there before the SCT. However, at the same time, I was working with Jay at AE to try and get cylinders 9,10 to show on the scan tool. We had no luck with this... He enabled a bunch of PID's trying to get it to show.
SCT looks like it cant read cluster codes? Thats one of the questions I had... Looks like it may be able to create them though huh Too cool I have an e-mail in to tech support at SCT on this. Will post back answer if anyone interested ?
Typically SCT pulls from the enhanced powertrain and the generic powertrain modules and that's about it.
If I remember correctly, U codes are typically communication bus codes, which usually means something isn't quite right with programming and/or interfacing of whatever modules are coming up.
The off the shelf tuners are really notorious for throwing U based codes. Atleast it's that way quite a bit in the diesel world, don't know how well that translates to the gasser world though.
I have an AutoTap - and I haven't really used it on my V10 much, since they didn't really show any want to even TRY to support it. I have the older "slow" AutoTap that they don't make software updates for anymore.
If I wanted to upgrade it, it was $X amount, and then if I wanted to read misfire counters (which my existing one can do for my '97 Cougar) for later models, it was another $X for the "enhanced" parameters.
I am looking into if the SCT X3 datalogging (LiveLink) can be used with custom PIDs to read the misfire counters, as I'm interested in doing that as well.
Yes- U1262 says communication bus error...
U1058,59 - Both say same thing...Invalid or missing data for transmission PRNDL.
U1027 - Invalid / missing data for engine RPM.
Starting to feel more and more like an SCT sorta' problem. Maybe they'll work with me on rectifying. Course this isnt a Mustang application and may not be viewed as important
Yes- U1262 says communication bus error...
U1058,59 - Both say same thing...Invalid or missing data for transmission PRNDL.
U1027 - Invalid / missing data for engine RPM.
Starting to feel more and more like an SCT sorta' problem.
Based on those codes, that would be my first guess as well. Unless you've had something done to your truck that required a new flash from the dealership. Some "i" insn't dotted and/or "t" isn't crossed.
Starting to feel more and more like an SCT sorta' problem. Maybe they'll work with me on rectifying. Course this isnt a Mustang application and may not be viewed as important
If you bought the X3 from Mike at 5-star, contact him directly about any issues. He's GREAT to work with and very responsive.
Krewat- I would be very interested to know what you find with the LiveLink... I downloaded that, but havent gone down that road yet. If I get to it before you, I'll post what I find...
I've been kind of disappointed with the AE. But I dont think its all their fault really. Truck is the heavy duty / non cal. version without EGR or post cat O2's etc. So only so much is available from PCM. But when software loads up and starts for AE, it shows ALL of the possible ford enhanced items... Even if its not part of this trucks system. I would prefer to only "see" what the connected vehicle has to "see".
. I would prefer to only "see" what the connected vehicle has to "see".
For the 6.0 that is something that I don't like with the actuation docking "station". That shows more stuff then I can actually do. However, for PIDs and the like, it just gives me only what I can actually manipulate. Unless that's something with your year model, I don't know. Or an issue with it being a gasser versus a diesel. I would hook it up to my 2010 and find out, but they don't have support for it outside of generic powertrain til November.
No re-flashes from dealer or anything... Positive the codes weren't there initially. Only code I ever had was the P1000 code, which never has gone away. Think its that HD calibrated out thing again... But somewhere between "try this" downloads from AE and the SCT install, these came up. 99% sure now its the SCT.
Not knocking AE by the way... He has tried. And for the price of the software and the limited capability of my trucks system
Krewat- I would be very interested to know what you find with the LiveLink... I downloaded that, but havent gone down that road yet. If I get to it before you, I'll post what I find...
I've been kind of disappointed with the AE. But I dont think its all their fault really. Truck is the heavy duty / non cal. version without EGR or post cat O2's etc. So only so much is available from PCM. But when software loads up and starts for AE, it shows ALL of the possible ford enhanced items... Even if its not part of this trucks system. I would prefer to only "see" what the connected vehicle has to "see".
I've used the Livelink for a bunch of things, including writing a script that can sample the data, and pull 0-60 times from it automatically, as long as you have speed logged (and it's accurate). Very nice to have
The Autotap I have is basically the same idea - it showed O2 sensors that I don't have (after the cat, for example), etc.
HOWEVER - the heavy-duty OBD-I setup we have for the V10 has EVERYTHING the OBD-II systems have, except they don't strictly COMPLY with the OBD-II standards for emissions. Meaning, some monitors never complete, etc.
You would think these scan tools would be able to take a "snapshot" of the system connected to, and load accordingly.
I have learned though... Always more to the "big picture" that we dont always know about or see
Krewat- I dont see the powerpoint you attached? It may be our firewall here at work or something. I'll look see later at home. I have read the OBD1 document a few times before... Thanks to you. I have learned much on here !
Thanks to both of you for the help / replies. I wiil post back what ever SCT tells me.
Just re-reading things... I did try Mike at 5-Star first. Sounds like he hadnt run into that before and didnt know. He did however get back to me right away ! Kudo's !