LLY Ficm

[kidturbo]

Post 501. How to figure TDC on the reluctor wheel.

Found the Pico tool app on old PC, only to discover the saved dyno recorded files were saved on flash drive E: which could be any one of a dozen I've long lost.

Did some Google searching, found a video of how to align the cam gear with timing marks. Clearly shows the reluctor gap no where near our pickup when piston at TDC. However it did show the cam reluctor, and the single low gap on it, lines up perfectly with our pickup hole location. Finally something makes sense.

Also found an old scope capture from LMM bench testing did some counting, and my guesstimate a few pages back [lb7 scope capture] of 15 teeth after TDC to start of crank big gap, matches up.

Still gonna go uncover that lmm in other room and verify, but my $$ say 15 teeth after #1 TDC is our winner...

Sent from my SM-S901U using Tapatalk

 

[kidturbo]

When this thread gets far enough along or comes to it's conclusion, would it be possible to distille the important data to another sticky or at the top of the thread? It's already beginning to become a long read with many more pages of data likely to be added. One or more of us will have to run back through from the beginning and note the post # and we can copy those over.

Sticky My Ass. When we get done, I plan to hack this sever and personally delete the whole thread... lol

Sent from my SM-S901U using Tapatalk

 

[kidturbo]

IT'S ALIVE !!



Still need to add a POTs to the Baro and Map lines, but I did get ECM firing on all cylinders with no FICM attached. Now to tidy up this mess and get rest of the tools attached so we can bring the FICM up on the lines..

BTW. Still haven't figured out how these Kodiak power up and run with no suposed BCM. Took a while, even busted open the fuse block to figure out, but the PCM relays seem to be powered from a Pink wire out of the ECM. Typically in GM wiring, Pink wires supply power To the ECM and other modules like our FICM from the PTR. I'm missing something, but it runs..

 

[kidturbo]

Could use a hand verifying some throttle pedal values on a running truck. While these look reasonable to me, and they sweep fine, the ECM has codes set for all 3 APP signals showing Out Of Range errors. Cleared codes, but they keep coming back.

Pinout looks correct, wire colors all matched up. Believe these used same assembly for the LLY and LB7 if I recall. But she doesn't seem to respond to pedal inputs..

P1125 Accelerator Pedal Position (APP) System Current IgnFail, FF, Fail, Curr
P2122 Accelerator Pedal Position (APP) Sensor 1 Circuit Low Voltage Current IgnFail, FF, Fail, Curr
P2123 Accelerator Pedal Position (APP) Sensor 1 Circuit High Voltage History IgnFail, FF, Fail
P2127 Accelerator Pedal Position (APP) Sensor 2 Circuit Low Voltage History IgnFail, FF, Fail
P2128 Accelerator Pedal Position (APP) Sensor 2 Circuit High Voltage Current IgnFail, FF, Fail, Curr
P2132 Accelerator Pedal Position (APP) Sensor 3 Circuit Low Voltage History IgnFail, FF, Fail

 

[DAVe3283]

It looks like the pedal is supposed to stop at much lower voltages. Maybe the Kodiak pedal is different than the one you have?

Sent from my FlashScan V2 using Tapatalk
View attachment 117879

 

[1FastBrick]

It looks like the pedal is supposed to stop at much lower voltages. Maybe the Kodiak pedal is different than the one you have?

Sent from my FlashScan V2 using Tapatalk
View attachment 117879

It's possible... The sensor and pigtail I sent him were from a 2003, 2500HD truck in the wrecking yard. On those they seem to be the same from LB7 to LLY.

 

[1FastBrick]

View attachment 117878

Could use a hand verifying some throttle pedal values on a running truck. While these look reasonable to me, and they sweep fine, the ECM has codes set for all 3 APP signals showing Out Of Range errors. Cleared codes, but they keep coming back.

Pinout looks correct, wire colors all matched up. Believe these used same assembly for the LLY and LB7 if I recall. But she doesn't seem to respond to pedal inputs..

P1125 Accelerator Pedal Position (APP) System Current IgnFail, FF, Fail, Curr
P2122 Accelerator Pedal Position (APP) Sensor 1 Circuit Low Voltage Current IgnFail, FF, Fail, Curr
P2123 Accelerator Pedal Position (APP) Sensor 1 Circuit High Voltage History IgnFail, FF, Fail
P2127 Accelerator Pedal Position (APP) Sensor 2 Circuit Low Voltage History IgnFail, FF, Fail
P2128 Accelerator Pedal Position (APP) Sensor 2 Circuit High Voltage Current IgnFail, FF, Fail, Curr
P2132 Accelerator Pedal Position (APP) Sensor 3 Circuit Low Voltage History IgnFail, FF, Fail

let me see what the diagnostics say. Maybe they will give us a value to work with and it's just an adjustment?

 

[1FastBrick]

View attachment 117878

Could use a hand verifying some throttle pedal values on a running truck. While these look reasonable to me, and they sweep fine, the ECM has codes set for all 3 APP signals showing Out Of Range errors. Cleared codes, but they keep coming back.

Pinout looks correct, wire colors all matched up. Believe these used same assembly for the LLY and LB7 if I recall. But she doesn't seem to respond to pedal inputs..

P1125 Accelerator Pedal Position (APP) System Current IgnFail, FF, Fail, Curr
P2122 Accelerator Pedal Position (APP) Sensor 1 Circuit Low Voltage Current IgnFail, FF, Fail, Curr
P2123 Accelerator Pedal Position (APP) Sensor 1 Circuit High Voltage History IgnFail, FF, Fail
P2127 Accelerator Pedal Position (APP) Sensor 2 Circuit Low Voltage History IgnFail, FF, Fail
P2128 Accelerator Pedal Position (APP) Sensor 2 Circuit High Voltage Current IgnFail, FF, Fail, Curr
P2132 Accelerator Pedal Position (APP) Sensor 3 Circuit Low Voltage History IgnFail, FF, Fail

They do give this chart in all the diagnostic tree's for each code. Ironically most of those codes are listed as LLY. Not sure why.

 

[2004LB7]

Ken, if we have to add an Arduino module to the FUCM board to do this 90° crank delay, how hard would it be to program two pins to connect up the J1939 comm wires so it can send an "all is good" message to the ECM? Would you only need to send one message at startup or is there some kind of continuous checks going on?

 

[kidturbo]

Dang that scaling does look way off.
When I was sorting the wires, I noted a couple of the 5v and Lo Ref lines listed in pinout for the APP circuits, were actually going to the engine bail connector for MAP or Baro sensors. Reason I left those out of the loop for first test. But that doesn't explain those ramp limits being way off. I somewhat recall scale being adjustable in tune file on my LLY. Guess I'll crack open some old old files..

@2004LB7 I plan to map out the comms and get a sense of what's actually required to make the ECM happy. Then yes I think we can use same Arduino type board to handle both tasks fairly easily. So far I can only say the ECM is unhappy without anyone else to talk too.

U1800 Lost Communications With Fuel Injector Control Module (FICM) Current EPA-Pend, IgnFail, IgnPass, Fail, NotPass, Curr
U2104 CAN Bus Reset Counter Overrun Current EPA-Pend, IgnFail, IgnPass, Fail, NotPass, Curr
U2106 Lost CAN Communications With Transmission Control System Current EPA-Pend, IgnFail, IgnPass, Fail, NotPass, Curr

 

[darkness]

I don’t know how the j1939 codes work, but I do know the medium duty trucks come with a j1939 port parked right next to the obd2 port. Maybe those take place of the bcm?

 

[1FastBrick]

Ken, What does the PCM show as the Vehicle ID?

Not that the information on the repair side is always 100% correct. But I am just curious. on the LB7 side like in a 2003 the list stops at P1683 which is funny because it shows a P2610 in one of the optional multi codes

 

[kidturbo]

I don’t know how the j1939 codes work, but I do know the medium duty trucks come with a j1939 port parked right next to the obd2 port. Maybe those take place of the bcm?

I'm beginning to wonder the same. Need to pull up the Ignition Switch schematics and work backwards from there. All models had J1939, but 2500-3500 never ran it inside the cab. Standard J1939 diagnostics uses a 6 or 9 pin round connector. Distinctly different from a DLC16.

Have things hotwired for now. And VATS seems to be staying inactive for the moment. So if can sort this throttle, I think I can make it idle at least so we can scope out our Command and Control firing structure to crankshaft relation.

 

[kidturbo]

Ken, What does the PCM show as the Vehicle ID?

Not that the information on the repair side is always 100% correct. But I am just curious. on the LB7 side like in a 2003 the list stops at P1683 which is funny because it shows a P2610 in one of the optional multi codes

View attachment 117897

Here is what pops up.. This Reman ECM looks to have a slight Identity Crisis.

Description E54 LB7 Duramax ECM
VIN 00Mx00#00000F0$00
Serial Number H00000200000
Hardware Number 3730569214
Calibration ID 33556536
BCC ý½|
Security Seed $7FFF

Operating System 15189044 ($CE65)
Engine Operation 15189053 ($4382)
Engine Diagnostics 15100899 ($E6EE)
Fuel System 15076353 ($3817)
System 15076385 ($F587)
Speedometer 15076393 ($55DE)

 

[Cougar281]

Although I'd think from the FICM perspective, there shouldn't be a difference between a LB7 pickup and a medium duty, I have a LB7 ECM laying around here somewhere that I could loan into the effort, and/or I could blow the dust and cobwebs off my old SPS setup and reprogram your ECM with a truck cal...

Sent from my Pixel 7 using Tapatalk

 

[kidturbo]

@2004LB7 that 90deg offset / delay confirmed by 3rd party. Has actually been manipulated on the ECM side previously for racing use. So we are gonna need to build that it into FUCM design specs if adhering to a direct plug-N-play replacement model.

As for the LB7 to LLY mod. Odds improving on a possible software solution.

 

[2004LB7]

@2004LB7 I plan to map out the comms and get a sense of what's actually required to make the ECM happy. Then yes I think we can use same Arduino type board to handle both tasks fairly easily. So far I can only say the ECM is unhappy without anyone else to talk too.

U1800 Lost Communications With Fuel Injector Control Module (FICM) Current EPA-Pend, IgnFail, IgnPass, Fail, NotPass, Curr
U2104 CAN Bus Reset Counter Overrun Current EPA-Pend, IgnFail, IgnPass, Fail, NotPass, Curr
U2106 Lost CAN Communications With Transmission Control System Current EPA-Pend, IgnFail, IgnPass, Fail, NotPass, Curr

Well the good thing is the code is updatable. We can always run some of those programming line out to some of the unused pins on the connector

I was doing a little reading on reliability for critical systems and it was recommended to run without a bootloader and program the code directly without going through the USB. Power glitches, spikes or random errors can cause the processor to jump around the code and if it lands on a code for erasing the program, or eliminating the 90° delay we could have issues with injecting the fuel way too early. Without a bootloader the processor has no means of altering the code even during the glitches

 

[2004LB7]

@2004LB7 that 90deg offset / delay confirmed by 3rd party. Has actually been manipulated on the ECM side previously for racing use. So we are gonna need to build that it into FUCM design specs if adhering to a direct plug-N-play replacement model.

As for the LB7 to LLY mod. Odds improving on a possible software solution.

I've already drawn up the new schematics for adding the Arduino to the FUCM. I've also included a toggle to switch between the LB7 or the LLY commend signals. It's actually pretty easy using a NAND, 12v and 5v regulator, and a switch or jumper to select between the two. If the software side doesn't work due to hardware differences we can always make a little add on module to put inside the corrects the signal

 

[kidturbo]

Although I'd think from the FICM perspective, there shouldn't be a difference between a LB7 pickup and a medium duty, I have a LB7 ECM laying around here somewhere that I could loan into the effort, and/or I could blow the dust and cobwebs off my old SPS setup and reprogram your ECM with a truck cal...

Sent from my Pixel 7 using Tapatalk

I'd certainly be down with a second LB7 unit for comparison, or even reflashing this one. Have an MDI on my bench I keep moving out of the way..

Right after I yank this tune file, then search for my old post in 11-12 when I sorted similar APPS issue out on the LLY boat. Am certain it's a been there done that thing. Or I'm having Matrix deja vu black cat visions. You guy are making me light neurons that were long considered bunt out..

 

[1FastBrick]

Here is what pops up.. This Reman ECM looks to have a slight Identity Crisis.

Description E54 LB7 Duramax ECM
VIN 00Mx00#00000F0$00
Serial Number H00000200000
Hardware Number 3730569214
Calibration ID 33556536
BCC ý½|
Security Seed $7FFF

Operating System 15189044 ($CE65)
Engine Operation 15189053 ($4382)
Engine Diagnostics 15100899 ($E6EE)
Fuel System 15076353 ($3817)
System 15076385 ($F587)
Speedometer 15076393 ($55DE)

So it doesn't even show a valid VIn... Interesting.

I think I recall these PCM's having issues with stuff like that.

I guess I could try searching the OS and see if we get any hits for a specific year or anything.