[wizkid1358]

What is the best to get additional parameters defined for a certain strategy in Binary Editor? I'm tuning my 2002 Harley Davidson F150 with PCM code EKO1 on strategy OMAE1. I have a new engine setup this year that revs a lot higher than the original. The problem is there seems to be a parameter that limits RPM before the supercharger bypass solenoid is triggered. So every time it went above a certain RPM it would trigger the bypass open and I would lose all boost. I just have it shut off right now which seems to be what most people wind up doing. I would like to keep it on though for when other people are driving the truck (especially when towing) and the temps get out of control. Looking in Tuner Pro for the OMAE2 strategy there is an RPM parameter for the bypass solenoid.

[jsa]

You could ask the definition author to add it.

You could add the parameter yourself.

BE has a method for a user to add a parameter to an encrypted def, I believe. Have a dig through the menu's.

[wizkid1358]

I sent a couple emails to Ben at Core Tuning but I never got a response. I also tried using the info from tuner pro to add the parameters to BE with the user defined parameters. The strategy is different and it looks like OMAE2 doesn't use the same address as my OMAE1. Decompiling my current strategy and finding the correct address is a little beyond my current capabilities. I'm not sure how to even make a bin file to decompile off of what I'm currently running.

[jsa]

An OEM bin can be read out of your EEC with QH and BE. Open an empty definition file with BE then use the FORD menu item to do the read. From there on it's a steep learning curve to disassemble and find the limiters in the bin.

Mmmm, nothing positive to be said for that level of after sales service.

[wizkid1358]

That is a good starting point so thanks for that. Maybe I'll dig into that next week. I don't want to throw Core Tuning or Ben under the bus. They are usually very helpful when I've had licensing issues in the past and after I asked for the adaptive fuel air flow tables to be added he immediately added them for my strategy.

[jsa]

Ok, maybe it's a case of needing time to find the parameters.

[wizkid1358]

jsa, where do I find a blank definition file to open in BE? If I close out of the current tune and do a read with the database enabled it automatically finds the strategy and only allows me to save a .beb file. If I disable the database it give me an error saying the loaded strategy must have a PCM defined on the config worksheet.

[wizkid1358]

Never mind. I was able to make a bin with Tuner Pro. Now the real fun begins.

[jsa]

Blank def

[wizkid1358]

So I found it in bank 1 at address 3a6e. Same as OMAE2. The issue seems to be with how I'm adding the user defined parameter to BE. I tried using 0x13A6E as the address and BE just displays 0 RPM. Anyone have any information on setting up user defined parameters in BE?

SC Bypass RPM limit 2.png (230.15 KiB) Viewed 4742 times

[jsa]

Give 0x11A6E a go.

BE addresses for S F T start at 0 for ROM ignoring the 0x2000 RAM.

BE payload addresses are actual addresses.

[wizkid1358]

No luck there. Is it possible because I'm using an encrypted def?

SC Bypass RPM limit 3.png (235.77 KiB) Viewed 4683 times

[jsa]

I thought the whole idea of user PID's was to allow user additions to encrypted def's.

Clint would be the best to sort out why it's not working.

[sailorbob]

If the definition has the 'PCMType' configuration option set to 'EEC_216K' (which it should be for OMAE*) and the 'EEC' configuration option set to 'True' then 0x13A6E is the address to use (assuming it is the correct address for the SCB_N parameter). But if 'EEC' configuration option is set to 'False' or missing then you will need to subtract 0x4000 from the address.

[jsa]

Every days a school day...0x0fa6e...so bank prefix is irrelevant in BE then?

[sailorbob]

It is if the 'EEC' configuration option is set to 'False' or missing from the definition.

[cgrey8]

If the definition has the 'PCMType' configuration option set to 'EEC_216K' (which it should be for OMAE*) and the 'EEC' configuration option set to 'True' then 0x13A6E is the address to use (assuming it is the correct address for the SCB_N parameter). But if 'EEC' configuration option is set to 'False' or missing then you will need to subtract 0x4000 from the address.

I'm not sure I followed a bit of that...mostly because I've not been involved with the multi-bank development efforts within BE at all. So it's most likely additions were made to BE to support different concepts & ways of describing memory offsets in definitions that aided the def-developers in some way that doesn't make sense to me since I have no multi-bank bin/def dev experience.

Can you break this down a bit more with some back-story about these things? For example, the different PCMTypes, what EEC configuration is doing, why 0x4000 when false (if the explanation doesn't make that obvious). The only thing I understood in all of this is the concept of banks.

[wizkid1358]

Well 0x0fa6e looks to be it. Reads as 23200 with no equation set and divided by 4 it is 5800. PCM type looks to be set as 216k as shown below but I do not know what the EEC configuration is set to.

About Binary Editor.png (132.43 KiB) Viewed 4617 times

[jsa]

The S F & T parameters are in ROM.

Each bank ROM starts 0xb2000. b being the bank number.

For a bank aware situation that would require the bank number less 0x2000.

For a bank unaware situation looking at a ROM address in Bank 1, it's an actual address in the binary. Bank 0 and 1 ROM both start at 0x2000, so thats adds up to 0x4000.

[wizkid1358]

So are the addresses in all the banks offset by the same amount (-4000) or is it different for each bank? Example being bank 0 is -2000, bank 8 is -6000, bank 9 is -8000.

[jsa]

Screenshot_20220107-195941_Xodo Docs.jpg (127.25 KiB) Viewed 4493 times

4x 56k banks of rom is 224kb, which does not match any PCMtype in the help file.

For 4x 56k banks, yes it would be 0x2000, 0x4000, 0x6000 & 0x8000.

A 4 bank of 216kb type has another 8kb at the end of bank 1(??) that is not in the bin file. So that would be 0x2000, 0x4000, 0x8000 & 0x10000.

I've spent very little time on multibanks and multibank defs, I'm happy to be corrected.

[wizkid1358]

The offset seems to be different for banks 8 and 9. 0x83F9D should be the switch to disable transient fuel correction at idle. I pointed BE to both 0x7BF9D and 0x7DF9D and both show as 255 when it should be 0.

[jsa]

Can you post the bin?

[wizkid1358]

Here it is.

OMAE1 Read.bin

(256 KiB) Downloaded 99 times

[jsa]

An image in your post above shows that a 224kb file is loaded.

[sc544x4f150]

That is the bin file I created with Tuner Pro using Decipha's instructions for a 256K PCM. I'm guessing this is not correct then? I wasn't able to make one with Binary Editor with the blank definition you supplied. The image you are referring to is "About Binary Editor" screenshot that shows the PCM type as EEC 216k 4 banks right?

[jsa]

The 256kb bin looks ok.

Yep it show EEC 216k and a file size of 0x38000 which is 224k.

Do a wildcard search on the bin for

Code: Select all

f9*

I don't see an 0xff at any matching address.

Makes me wonder what's in the BEB at the *f9d addresses you tried.

[sailorbob]

You need to ensure you are using the same calibration file size as that given by the 'PCMType' configuration option as otherwise you are most likely going to end up corrupting the file because values will get written to the wrong address.

[wizkid1358]

Here is the instructions I used to create the bin file. It states that all 96-04 PCMs are 256K.

bin file creation.png (219.23 KiB) Viewed 4314 times

If that isn't right for 224K does someone have the right settings I could use to get another bin file?

In TunerPro with Decipha's OMAE2 XDF the variables in bank 8 and 9 in my bin file load correctly so it again seems like the issue is pointing BE to the correct addresses for whatever format the BEB file has the addresses stored in. So far everything in bank 0 and 1 matches between BE and TunerPro using the 0x2000 and 0x4000 offset for the addresses but bank 8 and 9 seem to use something different in the BEB file than 0x8000 and 0x10000 offsets.

After typing all of that, it seems the banks in the BEB file are numbered 0,1,2,3 instead of 0,1,8,9. I just used address 0x2BF9D and now it shows correctly.

[sailorbob]

The guide you have posted is just a 'catch all' way of reading an eec-v and does not take into account the various ROM sizes found in the the eec-v. Once you have read the ECU using that method you need to then alter the binary file to match the actual ROM size. There is no 'bank' in a binary file but you must ensure the data in the binary file is in the same order as the banks when using the Binary Editor software.