Ranger Mods

Hi, I really would like to delete on my Everest Trend Auto the feature that changes automatically the right hand display to rev counter when the manual mode is activated with the gear lever, can this be done? Thanks in anticipation.

I believe it only does it when you go manual then change up or down. Pretty sure if I just leave it in sports mode but don't change gears then it does not change to Taco.

There could be a way around it but it is unknown and to go through every code and moved to sports mode shift up or down 100's of times means it may never be figured out.

Will check mine again and see what is does.

Hi Stewart, I believe you are correct. The change of display bothers me when I use off-road the manual shift to control which gear I'm in during engine braking or using rock mode, and want to look at the power distribution or lean angles displays as I normally do off-road. There is no sistematic way of finding which field has to be changed, other than trying them all one by one?

There is no structure to the changes being made so you cannot look and say it will be there unfortunately. Hence why so much time has been invested in the projects.

In mine it only changes to tacho on the initial gear selection after the move to sports mode. Changing gears while in sports mode does not change the display which ever one has been selected after the initial gear selection after the move to sports mode.

So, selecting the vehicle angle display after moving to sports mode and selecting another gear does not change the display back to tacho.

BTW, this is on normal mode, Doing this in another off road mode (sand, mud or rock) maybe different as I have not tried them.

I will try some changes this week. Changing IPC to think it is a manual transmission may fix the issue but you may have to forgo other things to get it. Will let you know the outcome.

It would be awesome if you could find a way to stop that from happening!!
It does my head in when constantly changing between auto and manual modes, which normally happens in situations requiring maximum concentration!

PS I have a 2016 built MY17 with sync 3, in case it matters.

Ok tested. I thought it would work

Change IPC 720-03-02 to xExx-xxxx-xx

You will get a new menu. Enable/Disable Hill Start which will not work and you will loose the PRNDS from below the speedo but because it now thinks it is a manual it will not change focus to the RPM gauge when you change gears in sports mode.

I have left mine less PRNDS as I never look at it anyway.

Cheers!
Is it possible that other functions might be affected, e.g the downshifting going downhill to keep the speed constant with cruise control on, or any other similar functions affecting the gear changes?

rusty-pie wrote: ↑Wed Jul 12, 2017 7:09 pm Cheers!
Is it possible that other functions might be affected, e.g the downshifting going downhill to keep the speed constant with cruise control on, or any other similar functions affecting the gear changes?

No the change is just visual. The downhill is controlled by the ABS and Cruise Control Modules so I see no reason why it would affect it.

One downside I noticed today is that doing this also means the IPC will not show what gear the vehicle is in when in sports mode.

I show my gears on the Ultragauge so not too much of an issue but is may affect others decisions on whether to change or not.

Mmmmm that is an issue for me...... might look into an alternative way.

Stuart, Is there any logic in how the modules are arranged, i.e. is there any way of excluding fields which definitely have no relationship with the display?

Apologies if this is a silly question but I am not yet familiar enough with how forscan works, in the past I have done some programming on my Audi and all the different sections were logically arranged and grouped.

No. All fields do have a relationship with the display. They turn features on or off depending on requirements of the vehicle. Tpms/no tpms, auto or manual, 2wd or 4wd etc.

If you mean Forscan itself then it is up to the developers to implement them in an easy to view way. Like when you view BCM asbuilt vs just BCM. I have put forward some additions but they have not been implemented at this time.

OK, so I guess that there is really no way of finding out other than changing one by one all the fields an check if that had an effect on the rev counter appearing, right?

Pretty much. I have mapped pretty much all of the IPC so I believe it is built into the firmware and cannot be modified. Not everything is an asbuilt option. So either use manual mode as above or you will just have to go through the whole thing again.

I would try it but having already spent 50+ hours on the IPC I'm pretty much done with it. You would need to change a bit at a time so there are 10's of thousands of changes to try.

Is there any risk of causing permanent damage if I change all the digits of each field at once to find out quicker which field controls that feature of the display, or do I really have to go one digit at the time?

You cannot find it out quicker. 0-1, A-F although some changes require more than 1 bit of data to be changed to have an effect. eg. F = 1111 or FF=11111111 bin. An option change maybe bin 11000111 vs. 01100111.

As I said above the chance that it is an option is pretty slim and it is probably built into the firmware so cannot be changed by modifying the asbuilt data. The asbuilt option will just be to change the cluster from auto to manual.

I did cause any permanent damage though I cannot guarantee you will not, everything I do is at my own risk and everything you do will be yours. Just be sure to backup your asbuilt before starting and be aware that numerous changes do effect adblue and cause all types of errors. They should be able to be cleared though.

From playing months and months ago I have a 99% functioning BCM so you can damage modules. I have had to factory reflash my ABS module 2 times as asbuilt changes corrupted the unit and would have meant the car was not going anywhere.

Playing with the unknown always comes with risks. Enjoy.

Rusty-pie, this is what i was alluding to when I said "No" over on FB. I knew it wouldn't be easy and so far what Stewart has said, it seems like a lot of work if it is even possible to get what you want exactly.

Id be just living with the inconvenience, even if it is such a minor one in the grand scheme of things.

Hi Steward, I did not mean to question your experience, you definitely have more patience than me you have spent all that time going through each digit one by one! I probably will end up doing what you suggest and leave the display as is because, as you say, it might not be worth the risk and the time.

Going back to my question, just for the sake of argument, I would like to use your post on the number of indicator flashes as an example to clarify my question:

Imagine I did not know what field I had to change to change the number of flashes. If in all the fields one by one I change all the digits to as series of "F" and then back to their original value, when I get to 724-01-01 and change it to FFFF-FFF-FF, that modifies (amongst other things I guess) the number of flashes to 7, so I know that that is the correct field that affects the number of flashes, and therefore I can start looking for the specific digit within the field, right?
Obviously my worry is that changing also all the other digits to "F" before changing them back to their original value could cause problems, and in the same way if problems could be caused by changing all the other fields to a series of “F” and back to their original value when I had found out that that was not the right field to change the number of flashes.

Hi Lonski, your "No" on FB was a way too condensed version of the explanation I got on this forum of the reasons why what I wanted to achieve is unpractical or too-time consuming; even if I will end up not doing anything about it as you suggested because of the reasons above, I still like to know exactly why this is the case. Nothing personal!

All good mate. Never questioned your question. Just pointing out that sometimes it's not worth playing and often those that play to far have an expectation that I will resolve it. Play all you want but just be aware of the pitfalls or at least have a way of getting back to default.

You would only make one change at a time to see if it made a difference. so xxxx-xFxx-xx. But it could have been 0-1 or A to F to make a difference. Take an example of the extra gauge in the Everest to display Intelligent 4WD gauge. There is a change in line 720-01-01 and also a change in line 720-07-02 to make it fully functional.

I would never change a whole line to all F's as 99% of the time an F does nothing anyway. Changing them all to 1 or A's would still not have the desired affect. It's a bit by bit process to really get to the bottom of it. Also a lot of comparing different models and at times luck.

A byte is broken down into bits so 0A for example has 8 bits IIIIIIII or 00000000, on or off. It may be one I or 0 that can disable or enable a feature or multiple bits.

Your best bet is to learn Hex, Binary, Decimal then slowly put it all together. It is also how I have to work out the gauges for the Scangauge, Ultragauge, Torque etc.

A lot of new codes are coming out recently due to more of Fords IDS software being reverse engineered, so most known changes will be available in due course even if not known before. Be patient and if there is a change then it may come sooner or later.

On another note but this also applies. I was writing lines to the ABS module tonight and corrupted it 3 times by doing so. Only way around it was to flash it back to default 3 separate times using my Ford IDS so just a warning... If I did not have it then I would be driving to Ford tomorrow with no ABS and no power steering, speed sensors, cruise control etc. etc. etc. Yes they all failed to talk to one another because of a 1 bit change and even though fixed I still didn't achieve what I set out to achieve.

rusty-pie wrote:Hi Lonski, your "No" on FB was a way too condensed version of the explanation I got on this forum of the reasons why what I wanted to achieve is unpractical or too-time consuming; even if I will end up not doing anything about it as you suggested because of the reasons above, I still like to know exactly why this is the case. Nothing personal!

No problems, understandable knowing your background. I didn't have the on hand and in depth knowledge that Stewart has to be able to explain to you why not.

Sent from my SM-G930F using Tapatalk