Jump to content

Bill

Members
  • Posts

    380
  • Joined

  • Days Won

    50

Posts posted by Bill

  1. On 10/27/2022 at 2:37 PM, Kirby@PCMTec said:

    So we had an interesting ABS issue come up recently with two sperate cars. Basically there appears to be a FG build in the wild which what I would call a "Police Special". Apart from the normal police enables, this has a very particular strategy and ABS config.

     

    1) The engine is a 'normal' FG engine build

    2) ABS is set to F6 / Force 6 - 4Pot (19-01-01)

    3) Unclear if the car was fit with the larger 4-pot or not at build time.

    4) Strategy is HAEDLG7 - we have only ever seen it on these "ex police" vehicles.

     

    Problem being is that this particular strategy also needed the upgrade to the HAAE4 strategy for our CustomOS. When you did this - the ABS would fault. Essentially the ABS then became aware that the car was not using a F6 Strategy (or in this case, this special police hybrid). The upgrade to a F6 strategy was off the cards due to the engine differences (engine, turbo, injectors) without a whole bunch of time spent copying parameters and giving it a run on the dyno to be sure.

    So how do you fix it? The first option is to reset the ABS unit to the standard XR6T variant (19-06-01), but if you are running the larger brakes (4pot or 6pot) this is not ideal because it will not be using the appropriate ABS calibration for that package, additionally this requires FORSCAN and knowledge on how to use it.

    Second option is to figure out how the ABS knew that the PCM was not a "F6" PCM. We knew this was being communicated from the PCM somehow, but we had yet to identify a parameter in the PCM (if any) which was identifying this difference. Well due to the excellent work of @jakka351 and some time spent comparing stock files in PCMTec, we landed on the following information:

    - In the engine configuration frame that is sent on CAN, along with cylinder count, displacement, also contains a "peak engine torque" value.

    - Some anecdotal information said that for a Ford this value was always 0x82, and for a FPV this value was always a 0x8A

    - Doing some in-depth compares between known F6 strategies and normal strategies as well as the information on this CAN message led us to the parameter : auF12105: "Engine peak torque for SCP".

    This is a development parameter, and therefore only in Workshop Edition.

    Current Understanding is as Follows:

    Essentially this parameter is "130" (0x82) on all normal strategies - be it I6, V8 or otherwise. and "138" (0x8A) on all the F6 / FPV strategies.

    The name and allocation in the CAN frame is a misnomer, its not actually peak torque value.

    (I will look at renaming this in our database in the future for clarity.)

     

    When we set this value to 138 in the normal strategy with the F6 ABS, the error was cleared and we were able to proceed with MultiTune on the car, without having to change the ABS setting back to XR6T.

     

    Why is this important? Well first off it shows us the value of some of these development parameters that we continue to explore and learn about, but more importantly, it means that if you are doing a brake upgrade on a non-FPV car, you can now run the ABS in the correct setting for that brake package and ensure you don't get any warning lights / ABS no bueno.

     

    Cheers 

    @Kirby@PCMTec an update for auF12105

    The values for auF12105, shown at the far right for (Ford/FPV Switch)
    130=FG XR6T, BF & FG V8 FPV.
    138=BF, F6X & FG 4.0 FPV.   
    image.thumb.png.c9aa4446f9e2bb3ced49c4b3a0d4e707.png 

    The auF12105 values I've found for other variants are as per below which isn't correctly reflected in the parameter description
    image.thumb.png.abd0e9002120b7f0f77a61f8cb4840fb.png

    auF12105 isn't found when searched in FGX Sprint UEAA or UEAB.
    I wasn't able to find a BF manual 3V file but could have missed one when filtering.

    • Like 2
  2. On 3/16/2023 at 6:18 PM, Bill said:

    Is the screenshot a read with the original 260 PCM & TCM?
    I thought the Tear Tag A5ME was a XR8 one & a check in Etis shows the VIN is for a XR8.
     

    image.thumb.png.f6cfb28556f6f3f25f25468b04404974.png

    UPDATE on this due to incorrect info. A5ME is actually a BF V8 FPV Tear Tag, not XR8 as I previously said. The VIN is however XR8.
    The values for auF12105, shown at the far right for (Ford/FPV Switch)
    130=FG XR6T, BF & FG V8 FPV.
    138=BF, F6X & FG 4.0 FPV.   
    image.thumb.png.c9aa4446f9e2bb3ced49c4b3a0d4e707.png 

    The auF12105 values I've found for other variants are as per below
    image.thumb.png.d5390451430b05c6b3dccafb494556a9.png

  3. Sorry for the late reply. auF2531 Encode calibration of engine configuration is another parameter that I forgot to mention
    NA = 18
    Turbo = 34
    image.thumb.png.d3421c5601df83ec6ef6a55a157a1f5a.png
    Same applies for ZF 03988
    NA = 18
    Turbo = 34
    image.thumb.png.4eeb990b77d4630e542278a6dc1834e0.png

    Usually no change is needed if going like for like but your file is a na PCM calibration & turbo TCM calibration so there's a mismatch.
    Changing this in some instances causes an ABS mismatch (I've seen the mismatch in BF), but might be what was required to make it work in FG. 

    Sounds like it's probably no-longer required, unless you want to try it to confirm.
    There were a couple of other parameters I was looking at some time ago but would need to go back to some spreadsheets to refresh my memory.

    • Like 1
  4. 21 hours ago, Jase said:

    Hey Guys. Hoping for some more help. I have checked the auF1692 to match ZF03987. And they are both 4, So I guess they match but still cannot use the Turbo tune, same transmission fault.... So I copied my NA tune back after painstakingly going through pretty much every parameter and changing them to match the Turbo tune.

    Was this a U0301 fault code or something else? Your case is the only one so far I'm aware of where it hasn't worked.

  5. 8 hours ago, BeerTurbo said:

    @Bill @Puffwagon cheers. tonights run had no trc issues.

    this is a ba turbo pcm, but for reference i changed (all of this at once so not sure what really was the fix)

     

    auF2495 - TQ Reduction  2:Traction Control - "0"

    auF0410 - ETC Traction Control -"disable etc trc"

    auF0265 - traction control - "6666"

    auF0264  -traction control "6666"

    auF0262 - traction control - 1

    auF0261 - traction control - 0

    auF1716 - engine size - "80"

     

    Cool. The same should work on any BA and possibly BF too 

  6. 2 hours ago, Puffwagon said:

    I was sure there was a parameter with a value of 40 for traction control and if you set it out of range it disables it. I can't find it tho but it might be it auF1716. I'm also fairly sure there was mention of it on the forum but again I can't find it.

    Sounds about right Puff. @BeerTurbo have a look in the HOWTO: Traction control thread. Setting it to 80 or 1 to set it out of range comes to mind.

  7. 10 hours ago, Puffwagon said:

    So it could have just been one parameter rather than the whole calibration?

    The thread I linked says as much.

    Yes, the one parameter can be enough to fix the issue. @Jase could still try it if he wanted to use the turbo ZF calibration & if it doesn't work, change it back.

    You have to go to the thread "ZF Transmission swaps" to find the info on changing auF1692 to match ZF03987.

  8. 41 minutes ago, Jase said:

    Ok. No I didnt know that and appreciate the advice, thank you.  So when I install the new Turbo trans and reconnect the battery, Turn the key.. What will I need to actually do??

    I was expecting a transmission fault etc. Then needing to either change the TCM from my NA trans to the new Turbo trans or pair the new TCM in PCMTec to my car.

    All advice is very much appreciate..

    If you're extremely lucky, ZF03987 and auF1692 will be the same values. If they're not, there's some info here on changing the PCM scalar & hoping it'll work.
     

     

  9. 9 hours ago, kurtandkevo said:

    Can anyone point me in the right direction on how to tell my ecu it’s a manual box having some trouble trying to figure it out

    Do you have ABU-214 or ABU-244 hardware? If it's a factory XR6T it should be one of the 2. You'll find this info on the sticker on the side of the PCM.
    If yes, you are best to flash it with a full manual strategy, not try to tell the auto strategy to be manual.

    If you're using a NA PCM, make sure you're using a manual PCM, not the auto one as they don't have the clutch switch hardware.

    You can use either a BA XR6T or F6 manual strategy but will need to log MTX ratios to change ratios for the cruise control to work with the TR6060.

    This has already been covered in various other posts. The one below has links within it to other topics that you'll need to read for more info.
     

     

  10. 35 minutes ago, Hermie said:

    Bill

    Also the steering column and key are not from the same vehicle hence why I need to do a complete key reprogram, can this be done with PCMtec or is Forscan my best option for this.

    You'll need FORScan for key programming.
    Get a second key from eBay with transponder chip (approx $20) & get a locksmith to cut it (approx $30) but make sure they don't clone the chip.

  11. 26 minutes ago, Hermie said:

    @Bill not standalone anymore, setup is sitting in a 69 Mustang and running a complete wiring and modules out of a XR8 Ute 2007, still running the original PCM so the ZF 6speed still matches, will turn PATS back on when I have an extra key done as I only have 1 one at the moment also running a modified BF steering Column as well. You helped me out with a previous post regarding diff ratio and speed sensor settings. Still need to take it out to see if the speedo is working and hoping limp mode will be sorted.

    Haha, I didn't connect the 2 posts but do remember now. Usually if you're running standalone, both PATS switches will be inverted. It's odd to just see only one inverted like you have. 
    Having only one key, doesn't matter as far as PATS is concerned, if that key was already programmed, you're running all the original modules & have the factory key transponder reader. 

    The tune you posted during the week still has the speed source set to ABS via wire instead of ABS via CAN. Not sure if you posted the current version or an old one. You've fitted the original wheel speed sensors & ABS module, so it needs to be changed to ABS via CAN, or it will still have no speedo & be in limp mode.

  12. Hi Peter, just checking if A16 is correct? I've just replaced a BA engine harness after having to diagnose a couple of issues. One problem was due to a broken wire between pin A16 to throttle position sensor & the other was due to a broken wire between A18 & trans shift solenoid. The wiring insulation had rubbed through on the AC hard line near the PCM.

    image.thumb.png.95bc5d89c13eb6b24e482fe0f9f5dade.png

     

  13. 43 minutes ago, Hermie said:

    @Bill so my setting as suggested above where set that way previously so not the issue there, and as per @Barry I also went through all my connectors and wiring and found nothing. The transmission is not switching the earth/negative to the reverse relay.

    The PATS switch was switched off by others as this was originally going to be standalone set up, bought as a package where you send you PCM & wiring harmess to them and they reprogram  PCM and Mod the harness. This was done like many years ago and engine & trans has only 60k on them.

    Is this still a standalone setup? What's the setup?

×
×
  • Create New...