Jump to content
PCMTEC Forums
Roland@pcmtec

HOWTO: Run PCM standalone (eg engine swap). PATS disable and Speed Source Setup.

Recommended Posts

This guide requires the Professional version or higher as it requires editing the VID block.

To run the BA/BF PCM standalone there are two items that must be set up. Firstly the PATS security system must be disabled.

First locate auF16527 (PATS Alternate Switch) and auF16595 (PATS Switch). From the factory you will have:

auF16527: 0

auF16595: 1

image.png.f3014942c439fe934569111c8827f79f.png

Flip both values. So now you will have:

auF16527: 1

auF16595: 0

Now that the PATS security system is disabled the BCM/ICC will no longer function, you should only do this if you are not utilising the dash cluster in your new vehicle.

The next step is to change the speed source. From the factory the VSS (Vehicle Speed Source) would most likely have been set to use the speed from the ABS module or the TCM sent via CANBUS. We will now change this to use the output shaft speed (OSS) sensor. You'll obviously need to wire an actual speed sensor as well up to pin b7. Most people mount this on the rear of the manual gearboxes. 

image.png.344ca9f3f834e3ee35eba44ba8a6337e.png

Now change VSS_Source to Transmission Output Shaft Sensor.

image.thumb.png.ea6556a5d1d7e02d6e6559fc97d6f092.png

Whilst you are in the VID block editor it is recommended to adjust the final drive ratio and other gear ratios that may have changed.

This file will now allow the PCM to run standalone with no other modules.

Note that this guide only works for BA/BF and earlier PCMs. The FGs have a different CAN setup and the vehicle speed source setting is ignored, hence without an ABS module the vehicle will not run correctly.

Edit: This guide may not work for early model BA Falcons (eg 2004 and earlier) that run the 5.4L. A workaround for these models is to use a later model strategy from a manual 5.4L

Edit2: If you have a FG afaik the speed input will not work. You must run the PCM with no speed reference and tune out the various fmem torque limiting that occurs and speed related tables. 

Share this post


Link to post
Share on other sites

Update. We don't officially support engine/trans swaps due to the large amount of support time they consume.

We recommend talking to one of the many conversions shops to do this work for you, as we have seen countless cases of people buying 4 or 5 PCMs and randomly swapping modules generally making a mess of the vehicle (and spending a lot of cash in the process) only to go see one of these guys in the end. You will save yourself a lot of time and money to go see them from the start. They will ensure you buy the correct loom, PCM and various modules and then provide a tune that will run the vehicle without any of the hundreds of possible limp modes kicking in.

Brett Hogno at Custom Machine Works in QLD (PCM mail service for engine swaps)

https://www.facebook.com/Custom-Machine-Works-856789001022313/

Killa Kustom Kables & Conversions in QLD (Looms for conversion)

https://www.facebook.com/Killa-Kustom-Kables-Conversions-202181769825285/

Jack Whiteford (Transmission swaps, relinking modules etc) in VIC

https://www.facebook.com/josh.whiteford.5458

  • Like 1

Share this post


Link to post
Share on other sites

If your a workshop with the workshop version and wanting to get into the Ford engine conversions will you offer help?.

Share this post


Link to post
Share on other sites
Just now, will15 said:

If your a workshop with the workshop version and wanting to get into the Ford engine conversions will you offer help?.

We will help with any pcmtec software issues but not with conversion specific issues. 

Eg we have had a lot of cases of wiring issues, incompatible abs modules, people wanting help with how to relink modules and recode keys using other software. We regularly have people swap multiple PCMs and want us to refund credits as they end up licensing the car 4x.

Conversions are very difficult due to the fact you will need at least 2 other software packages to do the module relinking and key recoding. You'll also need experience knowing which abs modules match which pcm calibration and which tcm calibration matches which pcm calibration. You also run into wiring loom and speed sensor input issues. 

All of the above is beyond the scope of our support. If you do want support doing the above we have people who would be willing to give it to you for a fee. You could possibly even approach them to train you, eg hire them to fly down for a week (depending where you are). 

Share this post


Link to post
Share on other sites

I’m more looking at just doing stand alone ecu into older model cars the same as we do with ls1’s. I was doing some reading and it looks like the fg is more of an  issue due to speed sensor being can. If we use bf as a stand alone it should be pretty straight forward for us I assume?

Share this post


Link to post
Share on other sites

Yes any hall effect sensor will work in a BA/BF, you will need to modify the pulses per rev to suit. You use the "transmission output shaft sensor" option and wire it to the same input (B7)

Share this post


Link to post
Share on other sites

When you do an engine swap and leave the NA ABS module (or vice versa) and have a turbo calibration in the PCM you will normally get a permanent ABS/DSC fault. If this occurs I have a theory on a possible way to fix it without swapping or reprogramming the ABS module. This is not tested or verified, but it is worth experimenting with.

There are two configuration words which are sent via canbus to the ABS module.

auF2531    Encode calibration of engine configuration

This flag is broken down into the following bits

Upper Half Byte

0x10 = NA

0x20 = Turbo Charged

Lower Half Byte

0x01 = petrol

0x02 = petrol also??

You could try changing this word to say the vehicle is actually NA despite it being Turbo, or vice versa.

Eg if you have a turbo calibration you would see auF2531 equals 34 (0x22) which is turbo and petrol. You could change this to 18 (0x12) and see if this works.

 

In the case where you have Turbo'd a RWD Territory (never came in turbo with RWD) you could try changing the following word:

auF2193 Encode calibration of transmission and axle type

Upper Half Byte

0x80 = 4WD

0x40 = RWD

0x20 = AWD

Lower Half Bye

0x08 = Auto PCM Controlled (BTR)

0x04 = Auto TCM Controlled (ZF)

In the case of a RWD NA BTR Territory (0x88) which you have converted to turbo, you could try telling it the vehicle is a AWD by changing the value to 0x28

You could also try toggling the auF1678 (4 wheel drive) option.

 

  • Thanks 1

Share this post


Link to post
Share on other sites
Posted (edited)

So I was doing some comparisons of plenty of PCMs (19 different ones in fact!) and ended up with this bit breakdown for those two config words:

The only car I couldn't get was a N/A Territory (I'll likely go on carsales/pickles salvage to get an ID) to check if bit 7 of auF2193 was in fact used. (as mentioned with the 0x88? above) I couldn't verify the 4WD vs AWD part of auF2193 either; as there is no true 4WD anyway!

image.png.88477b3088f680aa27ac5f6cb7805c42.png

image.png.9339aff8843d478657946f7a6e17dac5.png

 

Edited by nat

Share this post


Link to post
Share on other sites

Apparently I can't edit the one above again: another thing to note is auF2193 does not exist in the FGmk2 onward or the SZ territory. 

I went and found a couple of N/A and Turbo Territory IDs and sure enough; there's no reference of a 4WD 0x80 bit. All fall into the bits I've posted above. Quite mysterious!

Share this post


Link to post
Share on other sites

Great work Nat. If you have the workshop version of the software in the strategy list we have pulled out common auF parameters and put them in there, we could add this to the list if you want as we can automate extracting a specific param from all calibrations into a csv.

image.thumb.png.a148f5be099bce7ed2e480416817fc0c.png

  • Like 1

Share this post


Link to post
Share on other sites
On 5/12/2019 at 12:16 PM, [email protected] said:

Great work Nat. If you have the workshop version of the software in the strategy list we have pulled out common auF parameters and put them in there, we could add this to the list if you want as we can automate extracting a specific param from all calibrations into a csv.

image.thumb.png.a148f5be099bce7ed2e480416817fc0c.png

Cheers Roland - I personally don’t have the workshop edition so wouldn’t get to use that function - whether or not it’s useful I suppose comes down to how many possible conversions any workshop would be doing to ever use this functionality (and whether or not it truely works!)

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...