Ranger Mods

Hi All,

Has anyone been successful with getting forscan running with a 2.0L MK3 Ranger?

When connecting to the vehicle is asks me to select the type of vehicle and gives me two options,both of which are labeled "Error". Followed by which version of SYNC the vehicle is fitted with, Being SYNC 3.

Once pushing through that section it appears to function normally. I can view live data from the vehicle and open and appear to be able to edit the ASBULIT Data. But no option for the quick selection for enabling / disabling or adjusting features.

I have seen some people suggesting that most of the control modules appear to be the same between the MK2 & MK3, but clearly the software is having an issue / isn't aware of the different powerplant and drivetrain of the Bi-Turbo.

Any help would be appreciated

Thanks

Hi Adrian,

Please follow this and PM me the file


Providing FORScan Debug information
FORScan for Windows

Note: FORScan for Windows has Debug Mode setting enabled by default so debug information is recorded always. So all what user needs is to send the information from the laptop. The instruction below explains how to do it. However, if the Debug Mode setting was previously disabled for some reason, you have to enable it, remove vehicle profile (Vehicles->Profiles, delete vehicle from the list), connect and reproduce the problem before move forward with the steps below.

1. Make sure FORScan is closed.
2. Open FORScan Log folder.
2.1.Windows 7 and older: press Windows Start button->All programms->FORScan->FORScan Log folder.
2.2. Windows 8 and newer: click on the Windows icon at the bottom left corner. Find FORScan group in the list (under letter 'F'). Expand the group. Find FORScan Log folder item in the expanded group and click on it.
3. Folder with logs will be opened, you should see 2 files there: dump.bin and FORScan.log (may be more). Please zip them (if possible).

If I come across a UAII Everest, would the same be required? Or would the Ranger one be sufficient to cover both?

I do not know. I need someone to give me some logs for a PX3 so I can make sure it is up to date.

Any news on this one Stewart ?
I have a 2.0 PX3 with no non asbuilt options.

PerthRanga wrote: ↑Wed Dec 19, 2018 9:51 pm Any news on this one Stewart ?
I have a 2.0 PX3 with no non asbuilt options.

As per a few posts above. I need some log files, I still have not received anything from anyone.

Thanks Stewart
Didn’t see this post until after the PX3 was gone.
Have another one on Friday but it’s the 3.2 so will download the files if it’s an issue.
Brett

PerthRanga wrote: ↑Thu Dec 20, 2018 10:34 am Thanks Stewart
Didn’t see this post until after the PX3 was gone.
Have another one on Friday but it’s the 3.2 so will download the files if it’s an issue.
Brett

I think the 3.2l should be fine and pick up ok. It's the 2.0l that may be the issue.

Log of each would be a bonus.

Hi All,

Sorry for the delay. I am about to send some log files from my 2.0L Bi-Turbo Wildtrak to Stewart.

Thanks Again

There was a serious issue with the database and with the logs supplied it has now been fixed.

Should have a test build soon.

Another test build 23/12/2018

Should resolve PX3 connection issues. Please test and let me know where it is at with relation to non-asbuilt.

Download here download/FORScanSetup.SAEB.exe

Thanks Stewart,

I've been away for a few days, sorry about the delay.

I have been able to test with software update and it connects without an issue now, but almost everything (expect the SYNC 3 Parameters) is in ASBUILT format as shown in the attached screenshot. Thanks Again

Thanks Adrian,

I will get all the current non asbuilt options from the px2 added to the px3, will advise when ready for testing, hoping you can test each item for me as I do not have access to a px3?

No worries, Happy to Help.

Thanks Again

adrian.robinson.ar wrote: ↑Sat Jan 05, 2019 7:19 pm No worries, Happy to Help.

Thanks Again

Adrian, please test the version in this thread viewtopic.php?f=3&t=2326