after programing issue unlrelated?

[350whpsc]

i was working on a 10 fusion a couple days ago now did a rack swap, went in and did what i linked below in the pscm and now some how i have a weird running engine with these random codes showing up p0102 p0685 p061b-p before i dig deeper on this thing any chance i did something in forscan to cause this issue or unrelated?

i did what i found here
https://community.topdon.com/detail?id= ... 1unrelated?

[Don Ridley]

Did you connect a battery charger while you were updating the firmware? The instructions you followed are not complete and you should have read and followed the detailed Forscan instructions. The codes look like there is/was low voltage in the system. Hopefully you can clear the codes and they don't return.

[350whpsc]

we always find out the hard way.. there wasnt a battery charger hooked up.. and clearing codes dont fix the problem the p0102 p0685 come right back

[Don Ridley]

I don't have any firsthand experience troubleshooting those codes. But I would start with a wiring diagram and measure voltage at the sensors. They are simple devices.

[350whpsc]

im fairly doubt full its a wiring for sensor issue sense it didnt come up till i did what i did i was looking in the file on forscan since im not near the vehicle right now but noticed when looking at others online the pcm calibration level and part numbers seem to match while this one dont thinking that could be the problem but im new to all this

[Don Ridley]

I agree, it would be strange if PSCM firmware caused these faults. But none of us know how all these things are related. But we can take some measurment to prove the problem is not hardware/sensor related. Then you have to decide/guess where the programming error is. At least you will be chasing the problem.

[350whpsc]

i appreciate you giving a responds

[350whpsc]

I agree, it would be strange if PSCM firmware caused these faults. But none of us know how all these things are related. But we can take some measurment to prove the problem is not hardware/sensor related. Then you have to decide/guess where the programming error is. At least you will be chasing the problem.

I figured it out! it did indeed have a broken wire at the mafs plug someone else was messing with this thing before it has a new mafs in it.. so I became the lucky guy that it acted out again looked at mafs pids and and it was showing air flow not running.. wiggle the wiring around and walla the signal changed large amounts..

Thanks for trying to help me out your the only one that did

[Don Ridley]

That's great news!