Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Darryl@pcmtec

  1. With version 1.23 we will move the remaining "rapier transmission" parameters out of the development section and put them into the "ZF 6HP PCM Parameters":
  2. @Superb I have added the extra parameters you require to the Enthusiast and Professional packages. Download the latest 1.22 from the web site and you should be able to log these now.
  3. Hi itcy, I had a car that was tuned elsewhere and it did the same thing. First point of call is to check your injectors are dialed in properly. Mine was sitting around the 270rwkw and it went to about 320rwkw on the baby turbo at 14psi.
  4. haha, I agree. Unfortunately the motor trade wrote the specifications for J2534 specifically for Windows and then developed all the software based on that specification.
  5. To clarify using bootcamp and running Windows native works fine. I did this on my Mac a few years ago. Doing anything in a VM environment was where the drivers had issues so we decided not to support it (as well as the reasons @Roland@pcmtec mentioned). Simply partition the disk and boot Windows native.
  6. License is on a user/account basis so you will need to license the file to edit and flash it using your your account. Having said that and assuming the tuner who did the original tune did not tuner lock it you can read the tune out and edit it without licensing it. The changes you make will be stored in the file and can be shared with other PCMTec users. When you want to write the updated file into the vehicle the vehicle must be licensed.
  7. Before you start on trying to find out if there is anything wrong with the calibration on a car that was working please ensure the Brake Switch and Clutch switches are working properly. It is quite common that they fail and the cruise control will not operate if either of these switches is on.
  8. Bosch Green 42 lb injectors work well on the scaled factory turbo injector data. Just scale it up so the high slope is around 48lb/hr. I have already posted up injector data that works reasonably well for the Siemens Deka 60s:
  9. It is on the list for a future release. And the DTC reading is on the list to be fixed as well.
  10. Hi Will, quick question are you using the latest beta 1.21 release available from your downloads page: https://pcmtec.com/downloads
  11. Hi effxr6t, You can reduce the number of parameters shown by opening a tune and using the View Menu: For example you could un-tick Professional, Workshop and OEM Areas and there will be a reduced set of parameters to edit. You should be able to do most of your tuning with these parameters. With regard to separating the Editor and the Scanner we are looking at that as an option.
  12. Will have a look but all modules will see it as it is broadcast type message. Also seems to be the only spot where the mk2 sends the cranking flag and is in BF, FG Mk1 and mk2. Have not checked the BA yet.
  13. Last byte has two flags: 0x01 = Brake Switch On 0x04 = Cranking in Progress Byte 1: rate of change of RPM vs time [maths equivalent d(RPM)/d(t)] Byte 2: Throttle Percent Byte 3: Pedal Postition Byte 4: Hill Descent Flags Bytes 5 and 6: Engine RPM Byte 7 is a flag to clear malfunction fault codes Byte 8 as above
  14. Nigel, Can you check on the FG2 if the cranking flag in msg 12D silences the alarms?
  15. Some Alarms like low oil pressure, seat belt warning and the lovely locking of the doors if the customer has that set up MK2 FGs do not have message 200
  16. msg 0x200 details (FG Falcon only): Bytes 1 & 2 : (Actual Wheel Torque in N-M / Wheel torque to Engine torque) + 512.0 Bytes 3 & 4: (Minimum Wheel Torque in N-M / Wheel torque to Engine torque) + 512.0 Bytes 5 & 6: (Maximum Wheel Torque in N-M / Wheel torque to Engine torque) + 512.0 Byte 7: Flags: 0x80 = Torque type is Engine Torque 0x40 = torque calculation includes losses (inertia,...) 0x20 = Catalyst protection active Bottom 2 bits are crank status. Still checking this but I believe it is: 0 = no crank, 1 = crank pending, 2 = low voltage cranking Byte 8: non 0 => key off timer in minutes (rounded up to next minute)
  17. base octane is correct but I think it is US specification.
  18. Pretty sure Ford tuned for 95 and up to 10% ethanol as well, putting in better petrol allows for more power but there are still places in Australia where you cannot buy 98 at all. The autooctane setting most tuners turn it off because they tell their customers it is tuned for 98, putting 95/91 octane in their tuned vehicle would lead to disaster.
  19. Ensure you have a good look the ZF calibration to the Sprint as well. The ZF and the PCM are in constant communication about torque and throttle position, ... Changing the torque table in the engine gets communicated to the ZF via CAN, if the ZF does not like what it sees then it will request torque cut or throttle cut in some cases. We have had customers alter the torque table and ZF will tell the car to shut the throttle no matter what your settings on throttle cut are. Also when the ZF requests a torque reduction of say 120Nm it wants to see that torque reduction figure from the engine.
  20. Finnigan, The stock TMAP and Boost sensors for the turbo Falcon are rated to 255 Kpa. 100Kpa is atmospherics pressure so 155Kpa of boost or about 22.5psi. It is more likely you are exceeding the voltage limits for the boost and TMAP sensors which will cause the clip. Raise these to 5.0V and see if that resolves the issue:
  21. And you can also turn the rear O2 sensor off by setting auF0011 to 0: Do not change auF0010 to 1 on a V8. Not sure why Ford does this but it uses the number of O2 sensors on a V8 to run certain V8 code.
  22. It is used to help to keep the catalyst within its correct window and hence compensate for aged front O2 sensors. Ford calls the logic FAOSC to do this and can be controlled in the calibration.
  23. Further testing required but to disable traction control in a MK 2 FG: Set auF0410 to Disable ETC Traction Contol : And set auF2495 to 0:
  24. Will, I would check the wiring first. If it is a BF I would also check the small plug (C) on the PCM as this coming loose can cause these sorts of errors as well. Here is the workshop manual entry description of the error codes and what to do: Also check the maximum volts for the boost sensor (under Speed Density -> Scalars)
  25. Hi Milanski Here is the process to follow that will allow you to return the car to a state where the X3 will recognize the vehicle. For each tune in the X3: Write it into the Vehicle Read the vehicle (PCM and TCM) Save the file without licensing it. Now you have saved all the the tunes and can restore them in case you want to use the X3 later. Remember which was the last tune you wrote (organize it so it is the one you want to tune with PCMTec). This will be the tec file you will need to flash back into the vehicle in order for the X3 to recognize the vehicle. DO NOT EDIT this file. Backup all the tec files read and keep them is a safe place where you wont edit them. Open the tune you want to edit, license it and save it as a new file. If the X3 has not changed the OSID of the PCM in any of its tunes you will be licensed for all the tunes you read out of the vehicle (you will know this by opening each of the tunes and they will be licensed). It is not a requirement to fix the corrupt OSID to enable full editing capabilities but it will restrict you from seeing what has been altered from the stock file. Fix the Corrupt OSID for the Vehicle in the licensed file. this does not change any tuning areas but allows PCMTec to correctly identify the original calibration and what areas have been tuned when you use the Compare/History function. You can repeat the fix of the corrupted OSID for each of the files you read and that way you can see the change history for each file.
  • Create New...