Bill
-
Posts
380 -
Joined
-
Days Won
50
Content Type
Profiles
Forums
Events
Posts posted by Bill
-
-
14 hours ago, Puffwagon said:
I had a check, there is continuity on pin 4 but nothing on pin 5. I guess I'll take the centre console out and pull the carpet back to find exactly where the loom goes through the floor.
Asking a perhaps obvious question, does the shifter wiring go straight to the trans?
The wiring from the ZF6 connector goes to the C20 connector which is the large main engine wiring loom connector, passenger side of the engine. It's not uncommon to find broken wires here or near the ZF connector. Image is FG but the wiring location is the same. Wire colours may differ
From the C20 connector, it goes to a connector in the passenger footwell. It's also not uncommon to find this section of wiring loom has rubbed through on the aluminium AC pipe near the passenger shock tower. If water has made it into these connectors, there'll be corrosion on the connector pins.
It's rare to find any broken wires in the cab, but it's possible. The territory manual I have for SY doesn't have wiring diagrams for the ZF6, only BTR so is not useful. The FG manual shows the ute wiring loom goes directly from the passenger footwell to the shifter whereas the sedan shows an additional connector beside the passenger seat that may be accessible if the foot scuff plate is removed. I wouldn't go searching for this one unless there was an issue between the footwell & shifter.
I've run out of time to get more images, but it gives you a starting point.-
1
-
-
Check continuity between tip+ at the shifter & pin 5 at the TCM connector. Tip- is pin4.
Check the pin isn't pushed back in the ZF connector & the TCM pin isn't damaged. Wiring damage near the connector is possible too.
Sorry for the poor quality wiring diagram. I had to zoom out further than I wanted before being able to snip the image.
-
1
-
-
25 minutes ago, BarraTuna said:
Easiest solution is to flash on a manual strategy
That’s ok if the hardware isn’t ABU-212 or ABU-242. They don’t have the IO for the clutch switch so cruise will never work.
-
2
-
-
On 12/12/2023 at 8:21 PM, Braydenapps said:
Hey Bill is there any way to correct that without needing Workshop edition? I'm only on Enthusiast currently.
From memory, enthusiast level doesn't allow for you to use the return to stock feature. I missed the bit about it not recognising the cal id. When it can't read VIN & Cal ID, it's tuner locked as per what hjtrbo has said. FORScan usually has no problems returning it to stock but you need to be a paying customer, have a particular version of FORScan & the factory files. If the VIN is missing from the VID, FORScan won't show the VIN section for you to write it & takes some knowledge on how to trick it to re-add it.
If you want to retain the tune, Custom Machine Works is your best option.....if it's not locked using PCMTEC.-
1
-
-
Unlike tuning applications, FORScan doesn't care if the VIN is programmed into the VID block & will connect regardless of it being there or not. I can see the VIN isn't displayed in any of your FORScan screenshots. This is often seen in stock PCM's that have had the VID block programmed incorrectly using IDS or FJDS. I've lost count of the number of times I've seen it.
-
On 11/16/2023 at 11:04 PM, GeorgeAuto said:
Long shot but if you still have I would buy
I may have a new DLP + AEM X-SERIES 30-0310 all wired up ready to go. I put it together for a bloke, he lost his job & I haven't heard from him for a few months. If you're interested, send me a PM & i'll check if he still wants it.
-
2 hours ago, BarbysG6E said:
Is there a way to use the Openport 2.0 adaptor the access MS CAN with forscan
I need to disable police mode in a G6E but I can't pick-up the instrument cluster?
I know the eBay spec elm adaptors have a manual switch but I only have the op 2.0
No, the Tatrix doesn't support MS CAN & you should avoid the cheap ELMs with a manual switch, they're usually cheap crap.
The VGATE vLinker FS cable is a cheap auto switching cable with regular firmware updates to keep up with FORScan development.-
1
-
-
Here's download link for Xspurt Injector data for their different size injectors, if anyone needs a starting point https://www.racerindustries.com.au/injector-data-files/
-
1
-
-
Update on the bricked TCM. The TCM is now recovered.
It arrived & FORScan would find the TCM but would only recognise the OS calibration, not the 7J105 calibration.
Identifying the TCM with other software, confirmed the same thing. It's been re-flashed with a full OS & calibration write, tested & will be posted back tomorrow.
-
1
-
-
-
45 minutes ago, hjtrbo said:
Well holy fuck, tried the new Forscan Beta with module programming recovery mode. She bloody worked!!! My PCM is back alive and ready to roll. Caveat is you need to buy the 1 year license at $21AUD, the extended trial license won't let you do it.
That's great mate.
You need the paid licence to get access to the beta area of the forum to get the download link for 2.4.8beta but yes, recovery mode works well. It took a few emails, sending debug data to the FORScan team in 2.4.7.test builds to get it working properly with the vLinker FS & J2534 devices. There were a few service procedure interrupted errors, resulting in no communication with the PCM, but they got there in the end. I had another tool I could use to recover the PCM, so it was ready to try again when another test build was provided.
So far, I've only had 1 PCM sent to me that I haven't been able to properly recover using FORScan or return to stock. The PCM wouldn't communicate in car with any scan tools, HP or read using PCMtec recovery mode. I wasn't going to licence it to try writing to it.
It was an ABU-244 BA turbo PCM, that would recover using FORScan over & over. Once recovered, it would then read with HP, PCMtec & FORScan. Give it half hour to an hour of being connected on the bench & it wouldn't communicate again. Leave it disconnected for a few hours & it could be recovered again using FORScan but kept losing COMMS over time. Not a FORScan issue but a hardware issue. It'd been sent for repairs twice & sent back after being supposedly being repaired, prior to being sent to me. A replacement PCM was installed & that solved the problem.
There's a few other things you can do with FORScan PCM programming, that are pretty handy, if you have the Ford calibration files & spend a bit of time to work out a few workarounds.-
2
-
-
46 minutes ago, Jamiem said:
Hi.
I have flashed a zf 6hp26 tcm about 30 times and now it won't communicate with pcmtec or forscan.
Have checked power to trans plug from battery and key on.
What is the chance that I have bricked it ?
I've seen a couple of bricked TCM's & it's usually been the result of trying to flash with low voltage or high temp. I'd ask what codes you have but you have no COMMS.
If you think you may have bricked it because of one of these problems or others, send me a PM & we can discuss possible recovery options.
-
8 hours ago, Andre34 said:
@Roland@pcmtec I’ve got a bf na xr6 mk2 zf. It already has intake and exhaust cam tables. Will this work as fully independent cam timing or will I still need to make changes? HACCKA5
I’m about to take it for a retune but my tuner has never used pcmtec before so I want to get it as ready as possible so he just has to tune the values for me.
Cheers.
BF has fully independent VCT
-
2
-
-
10 hours ago, yoda598 said:
Extremely late reply but I wanted to be sure the issue was resolved as I've been tricked before 😅
It was intact a faulty powersteering switch. Disconnected it and 75+ hours with 0 issues. Turns out that when I had it unplugged before the abs module wasn't the original as I was chasing the issue ect. So went back to abs module from the fairlane and all sorted!
Thanks for the update. The PSPS & wiring are often overlooked but are known to cause weird issues.
-
28 minutes ago, BeerTurbo said:
auF1716 - engine size - "80"
i did this on my turbo terry and the zf went into limp mode.
Did you make all the other changes you listed in your previous post or just auF1716?
Do you remember what the codes were?
On 7/3/2023 at 9:28 PM, BeerTurbo said: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"
-
1 hour ago, brenden said:
thanks for the reply bill, This ute has had the turbo ECU and loom installed, We have managed to get the old ORI N/A ECU off the bloke that purchased it so I can read it, I should be able to copy just the VIN over?, the turbo ECU is out of a ZF6 turbo FG mk1 and is going into a ZF6 auto FGmk1 N/A car with a built turbo engine
Yes, use the calibration merge function & just copy the VIN from the na file to the turbo file
-
2
-
-
2 hours ago, brenden said:
I got a bit more info out of the customer because I noticed this ECU has the same VIN as the last ute I just tuned for him..... he has another turbo fg, he thought the ECU in that was dead so he replaced it, turns out the ECU was not the problem so he has 2 turbo ECUs with the same VIN and iv got one here that I gotta make work in this N/A turbo converted ute 🤦♂️
Make use of the factory turbo PCM. Get onto Hootens Harnesses on FaceBook & get a patch loom to add the factory boost control. FYI, Hootens (Bill) is taking some time off but if you're lucky, he might still be at work & might just have a patch loom on the shelf.
Update the PCM VIN to what the car is, if it's FG1, do step 2 of PATS programming...."Module initialisation" & it should be right to start & tune. Don't do step 1 as this will delete the keys. Not a problem if you have 2 keys but unnecessary.
You may need to change strategies depending on if it's currently tuned for auto or manual to suit the setup. This may also include having a matching TCM calibration if ZF6 & an ABS variant change.
IF it's FG2, you're going to need someone with IDS or FJDS to carry out PATS programming. -
17 minutes ago, overlap said:
If it is possible there must be more to it? . If no pcm is detected the "trans" button is not selectable in the logger.
Open a stock file & then start the datalogger
-
1
-
-
8 minutes ago, yoda598 said:
Have had it unplugged, same issue. Also unplugged noise suppressor same issue. Fitted a replacement abs module today, same issue. Last thing to swap is tcm.
Unplugging the noise suppressor will stop it from doing its intended job. Noise suppression.
I haven’t seen a faulty TCM that hasn’t produced fault codes but yours could be the first.
Let us know how it goes.
-
15 minutes ago, kris.ford said:
Hello Sir, Where can I find the setting to change the charge rate?
It is AuF16449 Target battery voltage min (car running)?
auF16449 & auF16489
-
1
-
-
16 minutes ago, yoda598 said:
I actually haven't looked to see if it's there.
Psp as in power steering pressure switch? Interesting.. never heard of them causing an issue..
No pattern that I've noticed. It's by far the most unpredictable issue I have had to date.
Yes, power steering pressure switch. Usually due to it causing VREF or SIGRTN to open circuit or ground.
I've had one where spinning the top section of the switch & flipping the wiring over itself whilst doing this would influence the fault. -
5 hours ago, yoda598 said:
you can see in attached datalog, the speed is working fine. however failry early on the speed freezes. ive also checked on forscan, all 4 individual wheel speed sensors continue to work. Currently thinking tcm failure or abs module failure. i have changed ; PCM, genuine ford coils, spark plugs. Ive checked all engine bay plugs and cleaned them, i have a spare tcm, not sure if i have an abs module. i have the turbo territory here im stripping but not sure the units are compatible.
Is the noise suppressor under the intake manifold connected & wiring ok, good earth? Not sure if it also reduces noise on the bus, but it's connected directly to coil wiring & back to the PCM via the A connector & meant to suppress radio noise.
A faulty PSP switch & wiring will at times cause very weird issues but not cause a fault code.
Have you checked if there's a consistent pattern ie when trans TOT reaches a set temp, rpm & load? -
7 hours ago, jzxdan said:
Thanks for following this up - I've managed to fix the issue. I did some browsing of these forums and came across this thread:
Long story short, changing auF12105: "Engine peak torque for SCP". from 138 (F6X value) to 120 (stock TT value), it seems to have cleared the error right away. Didn't have to reprogram or anything in forscan. I left the VID block values from my original read in the merged file.
Good to see you've got it sorted & that the info we now have on auF12105 is providing a simple fix for people.
-
5 hours ago, yoda598 said:
How common is a tcm failure? Trying to diagnose a bf fairlane ghia I recently purchased. Symptoms are :
trac light comes up, scan code - steering angle circuit.
Speedo drops out, shortly followed by zf sticking in whatever gear it's In. Followed by a shit ton of canbus com errors and invalid data for speed and rpm.Have Changed coils, new battery and checked alternator. Very intermittent issue. Trac light doesn't always come up and seems unrelated to zf issue. Car was well looked after before I purchased it, so I don't think it's a neglected service or anything. Will attach pic of codes. I should add that I've datalogged the individual wheel speed using forscan, they all continue to work after the issue has happened, but the actual speed output stops at whatever speed the issue happens at.
TCM failure happens but isn't common unless the gearbox has suffered the dreaded milkshake or it's been incorrectly handled.
SAS fault C1956 is present at the time of request. Everything else appears to have cleared, so it's an issue that needs to be looked at.
I'll attach an image of the ABS/DCS wiring circuit. Check power & earth circuits. Follow the CANbus circuits, noting the modules the data all passes through as there may be an issue somewhere in between.
Also make sure the SAS is correctly located & not loose. I've seen one that wasn't right that caused intermittent issues.
For the ABS section of the workshop manual, go to https://fordforums.com.au/wsmpub/bf/206-09.html
There's very good information for diagnostic & testing, including pinpoint tests. Do these tests to rule out a SAS & ABS module fault.
Speedo dropping out, gearbox not knowing what to do & having a heap of comms fault codes is very common when coils fail....even new coils. Anything that causes noise on the bus will do it. Usually, faulty coils will also cause a P0500 no speed source fault code, resulting in loss of speedo & ZF issues.
If you need additional wiring diagrams, they can also be found here https://fordforums.com.au/vbportal/viewarticle.php?articleid=1818
If you need something a bit better quality, let me know.
Upshift not working
in Transmission Tuning (AUS)
Posted
Not a problem mate & whilst I don't mind a beer, I don't expect anything. Have a beer for me