Hi Fellas it's been awhile

[Infidel67]

!!!!Solved!!!
I had been gone for awhile, Health, Family Life you know the thing.
Good morning yall and of course I have a problem, I have not yet finished my Tune with Jannetty, WOT tune is still missing. while I was working with the faulty OBD2 port and finally fixed it I'm getting some codes and I think I'm in Limp Mode, car was driving good all of the sudden at an intersection it dropped power, rough idling traction lights etc. I'm getting these codes now.
I pulled the cylinder 1 spark out and checked.
Any Ideas?

[1JEWLDSSRS]

Hey, welcome back! One thing to check first off if you got a bunch of lights on your dash, is your battery health, and your charging system. When they go bad they cause the car to do some really weird stuff!!

[acutron42]

I hope all is ok with you & welcome back! What did your obd2 repair entail. Here is a good video on that. +1 on Wayne's post.

[Infidel67]

Originally Posted by acutron42

I hope all is ok with you & welcome back! What did your obd2 repair entail. Here is a good video on that. +1 on Wayne's post.

Thanks Bud
All I got left is P0301 keep coming up, I swapped coils, plugs and wires from Cylinder 2 to 1. it's not overheating, pressure stays around 30 psi.
Checked the oil for water, Radiator for bubbles, some white smoke coming out of the pipes smelling rich, it happend all of the sudden when I stopped at a intersection, I was driving normal, lost power, rough Idling, lights coming on Traction etc. I kept looking and found the MAP sensor was completely disconnected from the hose, the sensor looked oily inside.
I got the Banks gauge installed plus I got the HP Tuner but I don't know what I'm looking for. And I'm not driving it.

Hey Wayne

[Aqua Blue RS/SS]

Glad to have you back dude! Hope all is well on the life side of things.

[acutron42]

So basically no change with the swap then & #1 is still missing? You can try cleaning the maf just for the heck of it as it is easy but it's just a hail mary. We have seen stranger things work here though. There have been recent posts also on faulty maf wiring worth looking up. I can post the coil wire diagram if you need it.

[Infidel67]

Originally Posted by Aqua Blue RS/SS

Glad to have you back dude! Hope all is well on the life side of things.

Good to see ya Bro

Originally Posted by acutron42

So basically no change with the swap then & #1 is still missing? You can try cleaning the maf just for the heck of it as it is easy but it's just a hail mary. We have seen stranger things work here though. There have been recent posts also on faulty maf wiring worth looking up. I can post the coil wire diagram if you need it.

Actually there is a change, I just bought a new MAP sensor... lights stayed off, but codes still showing even after I cleared them. Since it's a new MAP I guess I have to change some things? also here are two pics with logging in Idle and the new codes.
Please tell me that it isn't too bad

[acutron42]

Something looks off with your accelerator position @ 19.6% with only 830 rpm. Here are my idle readings a few weeks ago @ 1040 rpm's. Maybe someone can touch on this.

[Infidel67]

There is a bunch missing from what was there before.....I uploaded the pics side by side?

[Infidel67]

So I believe I have a faulty module, or short some sort.
If anyone has a Diagram/schematic from all the modules that would help me narrowing it down.
I found a good video to test the basic com's between modules.
let me know what you think please.

[acutron42]

Have you verified 60 ohms across pins 6 & 14 yet.

[SlowLS1]

Welcome back bro!

Since you have HP tuners, have you logged misfires for Cylinder 1?

Any change the ODB2 issues is related to you can bus issue?

Send me your email address and I can send you a PDF that has wiring schematics.

Brian

[acutron42]

Infidel67,

Here is some info I pulled from Alldata. You might want to try disconnecting your battery for awhile, reconnect it & then reflash your tune with the battery on a charger.

* Sometimes, while diagnosing a specific customer concern or after a repair, you may notice a history U-code present. However, there is no associated "current" or "active" status. Loss-of-communication U-codes such as these can set for a variety of reasons. Many times, they are transparent to the vehicle operator and technician, and/or have no associated symptoms. Eventually, they will erase themselves automatically after a number of fault-free ignition cycles. This condition would most likely be attributed to one of these scenarios:

- A device on the data communication circuit was disconnected while the communication circuit is awake.

- Power to one or more devices was interrupted during diagnosis.

- A low battery condition was present, so some devices stop communicating when battery voltage drops below a certain threshold.

- Battery power was restored to the vehicle and devices on the communication circuit did not all re-initialize at the same time.

- If a loss-of-communication U-code appears in history for no apparent reason, it is most likely associated with one of the scenarios above. These are all temporary conditions and should never be interpreted as an intermittent fault, causing you to replace a part.

* Do not replace a device reporting a U code. The U code identifies which device needs to be diagnosed for a communication issue.

* Communication may be available between some devices and the scan tool with one or more GMLAN serial data systems inoperative. This condition is due to those devices using multiple serial data communication systems.

* An open in the DLC ground circuit terminal 5 will allow the scan tool to operate but not communicate with the vehicle.

[Infidel67]

Originally Posted by acutron42

Have you verified 60 ohms across pins 6 & 14 yet.

Originally Posted by SlowLS1

Welcome back bro!

Since you have HP tuners, have you logged misfires for Cylinder 1?

Any change the ODB2 issues is related to you can bus issue?

Send me your email address and I can send you a PDF that has wiring schematics.

Brian

Hey Bud, No I have not done that, it's been crazy at work lately

Originally Posted by acutron42

Infidel67,

Here is some info I pulled from Alldata. You might want to try disconnecting your battery for awhile, reconnect it & then reflash your tune with the battery on a charger.

* Sometimes, while diagnosing a specific customer concern or after a repair, you may notice a history U-code present. However, there is no associated "current" or "active" status. Loss-of-communication U-codes such as these can set for a variety of reasons. Many times, they are transparent to the vehicle operator and technician, and/or have no associated symptoms. Eventually, they will erase themselves automatically after a number of fault-free ignition cycles. This condition would most likely be attributed to one of these scenarios:

- A device on the data communication circuit was disconnected while the communication circuit is awake.

- Power to one or more devices was interrupted during diagnosis.

- A low battery condition was present, so some devices stop communicating when battery voltage drops below a certain threshold.

- Battery power was restored to the vehicle and devices on the communication circuit did not all re-initialize at the same time.

- If a loss-of-communication U-code appears in history for no apparent reason, it is most likely associated with one of the scenarios above. These are all temporary conditions and should never be interpreted as an intermittent fault, causing you to replace a part.

* Do not replace a device reporting a U code. The U code identifies which device needs to be diagnosed for a communication issue.

* Communication may be available between some devices and the scan tool with one or more GMLAN serial data systems inoperative. This condition is due to those devices using multiple serial data communication systems.

* An open in the DLC ground circuit terminal 5 will allow the scan tool to operate but not communicate with the vehicle.

Thanks Bro, will go trough it ASAP, I send my email to both of you.