Tuning...learning

[EFI Guy]

I would bet your TPS is working but your Payload.csv file is missing it. The last 3 or 4 updates have been real glitchy and in one case the payload file just disappeared.

 

[ba123]

Might be pin #47.

 

[nvrstuk]

I would bet your TPS is working but your Payload.csv file is missing it. The last 3 or 4 updates have been real glitchy and in one case the payload file just disappeared.

Garry- is this info for me?? If so, I will find out how I check to see if that "Payload.csv" file is missing. THANKYOU

I am going to test pin 47 to grd (pin 26) and pin 46 to grd (pin 26), move the throttle and see if I get a reading that varies with the throttle moving. That would prove that the TPS and associated wiring is working and then it could possibly be a connection in the 60 pin harness connector to the ECU but it looks fine.

Here I go... again! After I find a decent pic of the pin number locations on the A9l.... I probably have 18 saved on my computer but where????

 

[ba123]

This help?

Love the internet.

 

[EFI Guy]

Garry- is this info for me?? If so, I will find out how I check to see if that "Payload.csv" file is missing. THANKYOU

Yes. Find your payload.csv file. You can open it in Office, excel, etc... Make sure TPS is listed in it.

 

[nvrstuk]

Yes. Find your payload.csv file. You can open it in Office, excel, etc... Make sure TPS is listed in it.

Thanks. Will do that today .
Finished putting together a short block 408 for Tim who you are helping now.

Thanks again. I will look.

 

[nvrstuk]

Here's what my daughter (I searched but nothing) found. I'll

TP but no TPS.

Now to figure out where, how to get that loaded up. lol

 

[nvrstuk]

FInally got 30 minutes to check pins 46 & pin 47 at my ecu with the key on, engine off.

.9volts at idle & 4.6V at WOT

I knew with 100% certainty that my ECU was receiving a signal from from the TPS but like we all know, we have to eliminate that.

Now to tell my tuner that so we either RE-download Binary Editor again (and hopefully not go thru 2-3 weeks again of "the software doesn't comunicate with my Windows" again like it did earlier OR try something else.

I remember saying back in '96 how EFI when it worked was great but when it didn't you couldn't find a tougher PITA project to troubleshoot! Should have listened to myself! lol

 

[nvrstuk]

Pics?

Where are the pics???

2 & 3 are a 408 short block for my buddy Tim.

Pic #4 is out my shop window.
Smoke!

Visibility is almost 1 mile!

 

[nvrstuk]

Another pic... winter is coming as evidenced by our 50deg F temp this am...

Got the bottom half for a snow bike today.

Now I need a 450 KTM or equiv.

 

[Yeller]

Ooooooo new toys

 

[nvrstuk]

Ooooooo new toys

Planning ahead!

 

[nvrstuk]

I would bet your TPS is working but your Payload.csv file is missing it. The last 3 or 4 updates have been real glitchy and in one case the payload file just disappeared.

HIT me alongside the head... too much going on around here. I had to back up for a minute to get a different look.

Thanks Garry, I understand what you're saying now. Clint downloaded a new BE Sunday night and the next morning it wouldn't datalog! That simple, thanks Garry!

Update: The payload file is wandering around my laptop but can't be utilized by BE for some reason. see screenshot pic

 

[nvrstuk]

I would bet your TPS is working but your Payload.csv file is missing it. The last 3 or 4 updates have been real glitchy and in one case the payload file just disappeared.

That's exactly what happened. The payload file is no longer in BE. The pic above shows it's still in my computer probably causing grief somewhere else...

 

[DirtDonk]

As the peeps at the Volvo factory in Sweden used to say... "The software is never wrong and can't be broken" or words to that effect.
This to my buddy who was so much the go-to Volvo mechanic that even the factory would call him to do some troubleshooting.
But he could never convince them that now and then, the software was just not thinking straight.

Paul

 

[bmc69]

As the peeps at the Volvo factory in Sweden used to say... "The software is never wrong and can't be broken" or words to that effect.
This to my buddy who was so much the go-to Volvo mechanic that even the factory would call him to do some troubleshooting.
But he could never convince them that now and then, the software was just not thinking straight.

Paul

My business is designing, building and supplying advanced marine control systems. I'm constantly reinforcing the fact that control software never has a "mind of its own"..it dutifully repeats the same thread(s) over and over and over... When something isn't working, you find the problem in the I/O or sensors. But the owner's techs tend to look askance at the one thing they understand the least when it comes to troubleshooting a problem onboard the vessel. Blame it on that "black box" with all the magic inside.

 

[bigmuddy]

My business is designing, building and supplying advanced marine control systems. I'm constantly reinforcing the fact that control software never has a "mind of its own"..it dutifully repeats the same thread(s) over and over and over... When something isn't working, you find the problem in the I/O or sensors. But the owner's techs tend to look askance at the one thing they understand the least when it comes to troubleshooting a problem onboard the vessel. Blame it on that "black box" with all the magic inside.

In a past life I was in charge of QA/QC for a type of metered spray system run off of a PLC. roughly 30 different systems with slightly different programming but otherwise relatively the same. Anyway, they all had their individual quirks on start up but I was always amazed at how after the system had been running for a week everything just kind of smoothed out on its own, almost like it was learning? but I believe this was more about parts wearing in and the individual pieces just working better over time, which made the whole system more functional. I think bronco's are more or less the same.

 

[nvrstuk]

My business is designing, building and supplying advanced marine control systems. I'm constantly reinforcing the fact that control software never has a "mind of its own"..it dutifully repeats the same thread(s) over and over and over... When something isn't working, you find the problem in the I/O or sensors. But the owner's techs tend to look askance at the one thing they understand the least when it comes to troubleshooting a problem onboard the vessel. Blame it on that "black box" with all the magic inside.

Absolutely that's what we blame first! lol

In this isolated case it was software and hardware (laptop) software not talking.

I'll confess one of the "software problems was a "mode" setting I had on Mode 3 instead of Mode 2.

Still chuckling because you are right on about the blame!