PCMTec Development Blog

[luke111]

the NA ecu can run a turbo no problems. However, it will not be able to do boost control. You cannot use a later model (bf/fg) ecu with 2 plugs as the inputs/outputs have been reallocated to different pins, and they cannot control the BA automatic.

And given your application, you would change the map sensor to a turbo one (loom adaptor required as they are different plugs). And one setting changed in the PCM so it understands its a turbo map sensor, not a NA map sensor.

WOW!!
This is great news! Thanks for the tips!
I really didn't want to swap ECU's because I've already got the PATS disabled in my ECU to run in my XH ute.
Any tips/advice/links on how to change this one setting?
I was thinking if the map sensor is just a 0-5V input to the ECU, then I could just plug in a 2 bar or 3 bar sensor and go?

I use an innovate MTX-L, SSI-4 + Pocket logger to tune my GSXR1000. I then put it into Logworks to make new maps.
I just love Logworks. Its fantastic one you get your head around it.
I will put all this gear into my XH soon but there's no point at the moment.

[DarrylC]

He actually makes a great point and will be a tuning issue if we can independently change the overlap.

Normally you'd need even more speed density maps to achieve a true airflow model if you can change the angle of both cams, eg like the coyote which has far more speed density maps.

Looking at the maps we found they do tune both cams independently in the BF, however it is very limited, eg the only do it above load 1.0 and before the turbo comes fully on song. They handle the fact this screws up the SD maps by adding a fudge factor for the SD maps. See these screenshots

SD slope map (there is also a corresponding zero) which is per cam angle. Now the issue is if you start dynamically changing the overlap as well, this screws up your airflow model.

The dynamic overlap map is very very limited in what it does. Basically from load 1.0 and above at 600 rpm it increases the overlap by 24 degrees. It goes back to 0 at 4000 rpm and all other loads.

Now to fudge the SD maps so the model still "works" they added two other maps which effectively fudges the SD value.

A degrees vs rpm map.
A load vs rpm map.

These two allow the exhaust cam to work. In the coyote I believe they have gone down a better but more complicated model with 10 SD maps which are all interpolated between each other to calculate the SD.

Anyway so I think if we start messing with the overlap allowed these maps will also need tweaking. We have them all mapped but will definitely need some testing by a competent tuner to discover how they should best be tuned.

Ford may have helped us here We found the the additional SD tables that are exhaust cam dependant. There are 4 of them and 3 are no-opps adding 0.0 or multiplying by 1.0. However the one is interesting as is what someone believe does EGR but it is just like the "Tuning Correction table" for the normal SD table so it would appear Ford has done the base level SD work on the cam tables for us. I doubt this is just a coincidence as these tables pop up when the ability to alter the exhaust cam independently is available.
Probably another one of those tables that differentiates our software

[VX L67 Getrag]

HPT wont even support the TCU for the 6R80 which they already support for older ford trucks as those applications have it integrated into the PCM.

Have not heard of "ECU24", the SID204 in the Ford Territory appears to use a different seed/key algo to the others. There are people tuning them via OBD but not sure what software they are using.

Yeah I did a search the other day & found what i mentioned...
http://ces24.com/devices/37-siemens-sof ... obdii.html

You have to buy that along with the actual device that uses it & is half that actual cards price, but yeah with it only doing SID201 & SID204 at the moment it won't really do what I want(debating buying it anyway).

As far as the 6R80 TCM I would try tricking HPT as if the ECM is not connected or unstable(with corrput VIN) you can just choose to read TCM so long as it is a supported controller like you had mentioned with other vehicles(I was able to at least do this with there older software, 2.25 from memory).

[ejukated]

its not supported by HPT, the Aussie application uses a separate TCM. In the US, its part of the engine PCM

Not sure how the CES24 works but apparently Dimsport supports the Ford ECU

[DarrylC]

its not supported by HPT, the Aussie application uses a separate TCM. In the US, its part of the engine PCM

Not sure how the CES24 works but apparently Dimsport supports the Ford ECU

Not quite, Eric told me there are two options for the 6R80. The early ones used a separate TCM and the later ones it was back in the PCM. HPT support both as the Mustangs and trucks have both options.

[VX L67 Getrag]

its not supported by HPT, the Aussie application uses a separate TCM. In the US, its part of the engine PCM

Not sure how the CES24 works but apparently Dimsport supports the Ford ECU

Dimsport is just a split off from alientech back in 1993 with various allegations they split but they're both still working together in ways but both expensive & imho I think alientech have more to offer for the high price, but both of them are a lot more expensive than that ces24 stuff.

[luke111]

Hey rolls, will we be able to datalog direct to SD card using an OpenPort 2.0 with your program?

[rolls]

No. That is something proprietary in the open port. You have to use their software for that.

You also have to physically remove it an d plug it into your pcto set it up, there is no passthrough to talk to it. Basically the user. Experience would suck so I'm not even going to look at it.

Writing an android driver and plugging it i to your phone would be better but that is a huge time investment.

[ejukated]

its not supported by HPT, the Aussie application uses a separate TCM. In the US, its part of the engine PCM

Not sure how the CES24 works but apparently Dimsport supports the Ford ECU

Not quite, Eric told me there are two options for the 6R80. The early ones used a separate TCM and the later ones it was back in the PCM. HPT support both as the Mustangs and trucks have both options.

Interesting, he only mentioned the PCM one. Do you have a list of which has what?

[rmrmd1956]

This is a bit off topic, but it may be implamented in the software being discussed in the future "hopefully"...

I was wondering if anyone knows how to or can convert the Ford VBF (or has a full binary copy of similar) attached file to .bin.
It is to suit the Ford Ranger which is the same as the BT50 & is an auto 3.2L turbo diesel.

I had to zip it as the site doesn't allow .vbf extensions

Thanks in advance.

In case you didn't understand the Vadis format, I've attached the .bin with correct offset