EFIDynoTuning Forum

Thank you, Decipha. I've downloaded that xdf and loaded it up in TPRS and can see lots and lots and lots of functions. 'Tis a shame that BE doesn't have something similar so I could easily use your excellent how-to's and translate them to BE-speak.

But by having TPRS I can double-click on a function and see what it looks like, which helps find it in BE. So at least I think I can get there.

Thanks again!

Thank you, Decipha. I appreciate your guidance and I'll take it and stick with BE. But I'll still do my best to get my head around the your excellent instructions.

Do you have a table that shows what function #'s relate to each of your descriptions?

Ok, I've downloaded TPRT and installed it. Then I went through the setup as described on the How To: Getting Started page. However, while the MongoosePro Ford is mentioned I don't really see how to configure TPRT for it in the writeup. So if anyone has any guidance on how to set up for it I'd appreciate it.

Also, I am confused about PCMflash &/or MMCFlasher. Is one or the other of them needed with a Mongoose Pro?

Last, I'm assuming that TPRT does datalogging via a USB port. While I have the analog output of my wideband tied into the EGR port of my PCM, it doesn't work. Core Tuning took a look and said my PCM uses a different kind of EGR port and it isn't compatible with a 0 - 5v signal. So I've been using a serial/USB connection. Will this work with TPRT?

Thanks again. Sorry to be so needy.

I'm confused. I'm running a stock setup with a few parameter changes, so I shouldn't have any custom code. Right?

As for the BIN, I installed AGANN/YER2 into the PCM and then tweaked it with BE. That created the BE tune file that is in the PCM now. Which is the BIN - right?

So wouldn't I just read that and then modify it instead of downloading something else and starting over?

I can see that BE might not be able to read Decipha's tune if there is custom code in it. But from what little I understand I'm running stock code with a few modified parameters, so I would think TPRT should read it. Having said that, I'm not going to try it until Decipha says it will.

As a little background on this, my truck was built for overlanding. It is heavy as it has a winch, dual massive batteries, an inverter, on-board air, bed-mounted toolbox, bed cover, etc. The engine has the latest EFI heads but no EGR nor purge system. Long-tube headers with true dual exhaust, 33" tires and 3.55 gears.

With Core Tuning's help it is running pretty well, but needs more tuning. As said, the idle needs work, and reading Decipha's writeup I'm pretty sure there's a problem with the either the MAF curve or fuel system setup. The cold idle is too low and the warm idle is too high - and the KAMRF's are about 15% high.

I was going to write a new tune this afternoon to add some cold RPM, but that is just probably fixing a symptom and not the problem. So instead I'll download and install TPRT and be ready if Decipha says to read the ECU.

Good info. Thanks!

I agree that "just about everything you need to know is in the write-ups." I read quite a bit on here before really getting into BE, but had assumed that having that info would map nicely to BE. It does from a theory standpoint, but not from a practice standpoint as "everyone labels things differently".

Fortunately my transient fueling is ok. Not perfect, but good enough that you can't feel it in the vehicle, just see it in the log. And the folks at Core Tuning got me close enough that most people could live with it. I'm not most people and want to dial it in a bit more.

I believe that leaves me with a couple of questions:

• Can TPRT read a BE tune? (I think the answer is yes as I believe the ECU expects everything to be in its appointed place, which doesn't vary based on whatever software wrote or read it.)
• Is there in danger in reading a BE tune with TPRT? (I'm pretty sure the answer is no if it truly is just reading.)

I assume there is info in TPRT about masks, so I'll be interested to see what it finds when it reads my tune. I found a mask that BE says controls what tests are run and another that BE says determines what test results can light the CEL. BE provided what bits do what and, being an old PDP-8 programmer I figured out what decimal code to give it and at least got the CEL turned off for what I think was the lack of mis-fire hardware. (Yes, in theory I'd already disabled that test, but something was still setting a code that BE nor my scanner could find.) So I'm interested to see what TPRT says about it.

Thanks again!

Ok, that got me to do some reading and I assume Tprt is Tuner Pro RT. Right? And it is free but a "measly donation" gets rid of the pop-up?

As said, I have the Mongoose Pro Ford made by Drewtech, and it appears to work with TPRT. Right?

So if I were to "convert" then I could read my tune and all of the parameters would be in Decipha? Meaning the instructions on this site would match what I'm seeing in TPRT? If so, that sounds very good and I don't need a Rosetta Stone.

Which then brings me to options available for help. And I see one that looks very enticing:

$0+ - FREE Tune Analysis
This service is provided free of charge for those with current tunes from ANOTHER tuner who wishes to have a second opinion on their current tune.
Highly modified vehicles that require dyno pulls will be charged a fee. If you are DIY tuning, simply post your tune and a warm cruise datalog in the TUNE REVIEW SECTION of the forum.

Is that really available? Can I send a datalog from BE or does it need to be from TPRT?

Oops, I see you responded while I was typing, dleach1407. Thanks!

Tprt?

Ok, thanks. And since I don't have nor use Tunerpro, ne'er the twain shall meet. But I'll still be reading your directions since they are very informative and helpful, and trying to decipher which BE parameter you are talking about. May come back with more questions, but realize that I may not get answers.

Guys - I'm sorry I've missed the questions and answers. I had ticked the " Notify me when a reply is posted" box but didn't think I was getting email notifications. However I just found them in the spam folder and corrected that. Sorry! I feel really embarrassed as I run a forum so thought I know how these things work.

But wwhite is right, I'm using AGANN/YER2 and the ECU has a catchword of YAZ3 and that is an ML1-441. The engine is a Scotty-built 460 w/a ZF5 and EEC-V with MAF & SEFI so it fits that well. I've worked with Core Tuning and have gotten the system running quite well, but there are things that I want to improve, like the idle. I've been reading the how-to on that on this site and think I could follow it - if I understood which scalars and functions are which.

Dechipa - I don't know what services you offer. But I've purchased Binary Editor and one token plus the Mongoose Pro cable, so I'm into Core Tuning for quite a few dollars. I am making progress on the tune but have a few issues I want to sort. I do have an idle that is too high, running around 800 RPM warm when I've told it to run at 648. And I'm working on what Core Tuning calls the Idle Air Adder for ECT table to get the warmup sorted. Plus I'd like to add a bit more timing.

So I would appreciate your guidance.