U1514-87 and U0415-00 errors

[rezar1]

While activating my paddle shifters, I used JScan to run a test and it gave two errors. Not sure what they are or how to fix them. I do have Tazer installed so I am not sure if it’s related to that. Have you ever seen these and if so, what was the fix?

Sponsored

 

[Gvsukids]

While activating my paddle shifters, I used JScan to run a test and it gave two errors. Not sure what they are or how to fix them. I do have Tazer installed so I am not sure if it’s related to that. Have you ever seen these and if so, what was the fix?

You have paddle shifters on your Gladiator? That must be awesome!

 

[ShadowsPapa]

And I got this but a very thorough scan of all modules via AlfaOBD later showed up nothing, no errors from any module. My truck is running and operating just fine, so I don't know what's up. Errors imagined by jscan?

 

[sass JT]

was this during your process after the tazer or did you do the whole reset and two sleep cycles and it came up?

 

[rezar1]

was this during your process after the tazer or did you do the whole reset and two sleep cycles and it came up?

Honestly I don’t know. It was my first time running the test using JScan so I am not sure when it would have started. I had Tazer installed couple of months ago after I did the gearing.

Like Bill mentioned, I am not getting any errors/lights from the truck directly and everything seems fine. It just showed up on JScan.

 

[AshWill]

I have had the exact same issue since I have had my Taser mini, have you had any luck getting it to stay gone and if so how?!

 

[rezar1]

I have had the exact same issue since I have had my Taser mini, have you had any luck getting it to stay gone and if so how?!

Since i haven’t seen any warning lights on the dash, I haven’t checked to see if they are still there.

 

[AshWill]

So I unmarried my tazer and my check engine light came back on and it was a sensor (dealer said o2) just I’d pass it along

 

[Gvsukids]

I have the U1514-87 error code. I also have the triangles in my blind spot mirrors, until I restart the vehicle.

 

[MJRSC]

I’ve got the same 2 error codes pop up now after I re married my Tazer, brought truck in for TSB this morning.

No check engine lights or any issues at all, just seeing these codes when I check for them.

Any concern and any fix for it?

 

[ShadowsPapa]

I’ve got the same 2 error codes pop up now after I re married my Tazer, brought truck in for TSB this morning.

No check engine lights or any issues at all, just seeing these codes when I check for them.

Any concern and any fix for it?

Normally a communications issue - is everything plugged in nice and snugly?
Did you clear things and see how it goes?
I had a list of communications related errors similar to these - was resolved by the dealer checking and reseating the connections at the bus array behind the glove box. Common area for communications issues, and possibly you triggered something when removing and putting the tazer back (likely you reconnected to the security gateway module - could have been a communications issue there if things weren't 100% seated and connected).

 

[MJRSC]

Normally a communications issue - is everything plugged in nice and snugly?
Did you clear things and see how it goes?
I had a list of communications related errors similar to these - was resolved by the dealer checking and reseating the connections at the bus array behind the glove box. Common area for communications issues, and possibly you triggered something when removing and putting the tazer back (likely you reconnected to the security gateway module - could have been a communications issue there if things weren't 100% seated and connected).

I will pull it and check again. Seems pretty snug to me. One of my connectors, using an extension, is very, very snug maybe.

 

[MJRSC]

Normally a communications issue - is everything plugged in nice and snugly?
Did you clear things and see how it goes?
I had a list of communications related errors similar to these - was resolved by the dealer checking and reseating the connections at the bus array behind the glove box. Common area for communications issues, and possibly you triggered something when removing and putting the tazer back (likely you reconnected to the security gateway module - could have been a communications issue there if things weren't 100% seated and connected).

I wonder if I should order a new SGW extension and just give that a fresh shot.

 

[MJRSC]

I just installed the ECRI calibrator and got the exact same codes. Maybe something isn’t communicating since the security is bypassed.

The answer and consensus is those are codes from unplugging the SGW and that after a little time and cycling they’ll clear. I checked my connections because my SGW extension cable is a little gummed up, just let time pass and sure enough they were gone in the end.

 

[ShadowsPapa]

The answer and consensus is those are codes from unplugging the SGW and that after a little time and cycling they’ll clear. I checked my connections because my SGW extension cable is a little gummed up, just let time pass and sure enough they were gone in the end.

The connections and connectors in these things are crazy picky. But then, think about the really small voltages, the signals that go through how many connectors. Any bit of oxidation is a layer of insulation on that pin. Any bit of looseness at all is trouble.
I've never had the trouble with the extensions or the bypass, but that doesn't mean it can't or doesn't happen. Just that I've not personally experienced it.
However, I have experienced the CANbus/star connector issues and I'm not convinced I won't see them again. Some of it almost appears to be a timing thing. If I do things quickly, I'm more likely to see the issue. If I put seat belt on, press brake deliberately, press start, don't touch anything else until the cluster has done it's POST, then put it in gear, I'm typically fine.

I used to do the design, configurating and handle the specs for the computer systems used by CCC for their Series IV turbo compressor controls. This was in the 1990s. 386, new Pentium technology, VESA bus, PCI, you get the timing.......... anyway, in my testing and writing up the build procedures and test sequences, I found that if two of the cars were switched around in the slots, the PC wouldn't boot, it wouldn't even POST. Put the video car in first, it was fine but if the video car wasn't in the first VESA slot, no POST. I discussed the oddity with the com card, etc one of the EEs there and he said - timing, speed, one card got a signal a tiny fraction of a second before the other, time for the bus to fully power up. I called YMS engineers and chatted with their head engineer (they made the mother boards I used) and in the conversation he said "do you know what the most commonly used part of our company health plan is?
Uh, no, I don't....
He said the mental health coverage. Engineers almost always left or needed treatment for the stress. (I bet we talked for over an hour - he needed the break LOL)

Anyway, the point - these can't be too much different. It's a network, different than the LANs we all know, but it's still a network (think of it - all networks, LAN, WAN, whatever, is a communication area network so I'm not sure where the terms came from - likely some new journalist that needed to call the network something)
CAN is really a local area network and a local area network, like the one in your house, is a communication network passing information back and forth and the timing is critical, a missed bit means a corrupt bit of data, missed communication that was expected. But computers on a LAN retry and confirm receipt. CAN seems to simply freak out.
(Hootbro, help me outta this!)

Sponsored