Making new def for BE

Scaffy · Post by **Scaffy** » Fri Oct 10, 2008 8:09 pm

Can someone please help me by pointing me in the right direction as to how to go about creating my own def file on BE. I'm in Australia and our EECs have near to no support at all. I'm running the tweecer and some guys here have hacked the EEC I'm running, but they're not using BE. They're running the moates gear and tunerpro. Because I have the tweecer already, I want to try and use that still and hopefully help out a few guys over here with the same EEC as me.

Thanks in advance for any help.

Scaffy · Post by **Scaffy** » Sat Oct 11, 2008 2:01 am

It's ok, I've found the definition template. Now to work out what goes where...

Post by **2Shaker** » Sat Oct 11, 2008 7:23 am

Would changing the EEC to one of the more popular ones discussed here be an easier or more practical solution? Maybe there is a strategy/calibration here that is close to yours. What is your catch code, year of vehicle etc.?

Scaffy · Post by **Scaffy** » Sat Oct 11, 2008 7:47 am

As far as I know, our wiring looms and your eecs aren't compatible.

My car is a '96 Ford Falcon XR8. My catch code is 6DFC. I think I've found a way to cheat by using the GUFB strategy, finding the same PIDs and changing the address. Does anyone know if this will work or if I'm wasting my time?

A guy I've just started chatting with has found a lot of parameters in the 6DFC using hexplorer by using the GUFB def to compare his findings with, so all the names of everything are the same.

86GT · Post by **86GT** » Sat Oct 11, 2008 3:51 pm

I just uploaded the new template sorry it was not the most recent. BE version 2.3.1 Added some new columns that support new features. If you have an XDF from tunerPro it can be converted with BE to get you a good starting point.

Scaffy · Post by **Scaffy** » Sat Oct 11, 2008 11:05 pm

Thanks 86GT, that's what I'm actually doing now. It's a slow process, but is easy enough.

I can see many hours going into this, but be well worth it.

Cheers

86GT · Post by **86GT** » Sat Oct 11, 2008 11:25 pm

the conversion is quick is that what is taking you a while because BE will open the XDF.

Scaffy · Post by **Scaffy** » Sun Oct 12, 2008 1:13 am

Sorry, I'm not too sure what you mean conversion...

What I'm doing is this. I have tuner pro opened with the NVMG8.xdf and 6dfc.bin. I also have the gufb excel worksheet open which is the strategy for BE. I then did a save as and saved that as 6DFC. What I'm doing now, is selecting the parameters in tuner pro, hitting f2 and all the info comes up. I then copy the PID and use the "find" function in excel where it finds the parameter for me. I then cut and paste the address from tuner pro to excel and move on to the next one.

Is there an easier way to do it than this? Please tell me there is.

Post by **cgrey8** » Sun Oct 12, 2008 6:27 am

If you already have a TunerPro XDF file, then just import the XDF directly into BE so BE displays the definition like TunerPro does. From there, you can save the definition in BE to be in XLS format and edit it like the GUFx defs.

To do this, click OPEN Definition, and from the dropdown box in the browse window, select the TunerPro XDF instead of the BE XLS file format.

86GT · Post by **86GT** » Sun Oct 12, 2008 12:07 pm

Just as Chris said.

If you have any problems send me the XDF and I will convert it for you.

Scaffy · Post by **Scaffy** » Sun Oct 12, 2008 6:03 pm

When I open BE and the xdf, a dialogue box comes up asking me how many banks as follows.

XDF Address Offset

Enter the address offset
For a 1 bank tune enter 8192
For a 2 bank tune enter x
For a 4 bank tune enter x

It is written just as I have written it above. Because I have no values for 2 bank, which it is, I have to set it to one bank. Then once it's open it has a bitch about the levels not being set right. Then, when I open up the 6dfc.bin, another dialogue box comes up, saying "the normalizer has no value in column index 0. Make sure the normalizer has not been filtered out and that it still exists.

Once I hit ok a couple of times, it opens the bin, but all the values seem to be maxed out. After saving it and then opening the new .xls everything is very different to what I've been looking at with the gufb.xls that I've been modifying.

If you want to have a look at it, the link to get the nvmg8 def is at the bottom of the Ford listing at http://www.tunerpro.net/downloadBinDefs.htm

You'll also find the 6dfc.bin there as well.

I'll just keep modifying the GUFB for now.

Thanks for your help

Post by **cgrey8** » Sun Oct 12, 2008 6:42 pm

Send your XDF and BIN file to Clint (86GT) so he can look into why the import isn't going more smoothly. That's the whole purpose of the feature is to make the transition to BE from TunerPro smooth. If that's not happening, he needs to know about it so he can correct it.

Scaffy · Post by **Scaffy** » Sun Oct 12, 2008 7:03 pm

Please excuse my ignorance, but is Clint the developer of BE or something?

Is that link sufficient, as it has both the bin and XDF there? Or do you want to give me an email address so I can send it on?

Thanks,

Chad

Post by **cgrey8** » Sun Oct 12, 2008 7:16 pm

Yes. Clint (86GT) is the developer of both BE and EA...a very valued member of this board.

Scaffy · Post by **Scaffy** » Sun Oct 12, 2008 7:25 pm

Great, I should have begun asking questions a long time ago then!

86GT · Post by **86GT** » Sun Oct 12, 2008 7:50 pm

Yes i am Clint and will help with the import

Scaffy · Post by **Scaffy** » Sun Oct 12, 2008 9:10 pm

Thanks Clint, I appreciate it.

Jaysen · Post by **Jaysen** » Mon Oct 13, 2008 8:04 am

Gday All

Ive been helping Scaffy with his Aussie ECU, as Im running the same ECU, and Ive been using TunerPro with the Moates Ostrich, Emu, Burn1 combo and F3 chips. Im quite the fan of TunerPro, however BE and EA do seem to have a hell of a lot more stuff that can be done ie heaps of RT datalogging options with the right hardware, and Im keen to work with both, as Im not a fan of CalEdit/CalCon.

From the info above, Ill also have a go at converting the xdf to xls via BE, and see how it pans out. Ive only downloaded BE last night, but already Im very impressed, and I really love the idea of user friendly definition creation, which has been a little difficult with other GUI tuning software packages. Keep up the great work Clint!

Cheers
Jaysen

Post by **cgrey8** » Mon Oct 13, 2008 9:06 am

Unlike with other tuning softwares (TunerPro included), BE is constantly being updated with new features...some in-your-face features that make the user-experience much better, and some definition developer features that the average user will never see. Clint's been very receptive to the needs of both the users and of the definition developers. It's just unfortunate that decompiling and reverse-engineering isn't any easier.

86GT · Post by **86GT** » Mon Oct 13, 2008 9:18 am

The idea is if the user interface is easy enough the users time can be spent on the reverse engineering of the tune rather than having to fight the tune and the user interface.

Jaysen
Let me know if you have any trouble converting the XDF files. I can help or even convert it for you and send it back via email

Jaysen · Post by **Jaysen** » Mon Oct 13, 2008 10:24 am

Ive been playing with this for a few hours now, but still fighting with it. What I think my problem might be is that our Aussie EECV's are a 256k 2 bank bin, with the code starting at 0x22000, and the parameter data of this particular bin starting at 0x2A000. Im aware that the EECV's you guys use in the states have thier parameter data starting at 0x12000, which could be part of my prob as it doesnt seem to have all the parameters, nor are they in the right place. When I open the Explore Binary button, I should see my catch code and strategy at 0x19F06, but instead its found at 0x15F06, where did the 0x4000 data go?

I might take you up on the email option if you dont mind Clint?

Cheers
Jaysen

86GT · Post by **86GT** » Mon Oct 13, 2008 10:27 am

sure send me the BIN and the XDF and I will take a look

86GT · Post by **86GT** » Mon Oct 13, 2008 10:29 am

The other thing to note is what is the offset in tuner pro. If you hit ctrl F2 there is a offset there. I need to know what you have it set to.

Jaysen · Post by **Jaysen** » Mon Oct 13, 2008 10:51 am

Clint

My base offset is set to 0 as I thought that it might effect my ability to RT tune, Ive not tried it with a different offset.

Ive sent you an email to Clint@EECAnalyzer.net

Cheers
Jaysen

86GT · Post by **86GT** » Mon Oct 13, 2008 10:56 am

Got it

86GT · Post by **86GT** » Mon Oct 13, 2008 12:33 pm

I just sent the file back.

Scaffy · Post by **Scaffy** » Tue Oct 14, 2008 9:57 pm

Cheers for the files Clint.

I've just discovered a problem in BE, more than likely due to my stupid need to press buttons when I don't know what they do. I opened a tab in BE and there was something about LC1 in there. I clicked a button to do with LC1 and it came up saying no mts port available, then shut BE down. When I try and open it up again, it just shows the dialogue box saying the same thing and doesn't open. I Uninstalled the re-installed and it still does the same.

86GT · Post by **86GT** » Tue Oct 14, 2008 11:09 pm

once you open BE goto the hardware tab and disable the LC1 and the error will go away. The reason you are getting the error is because the PC does not have a com port.

Scaffy · Post by **Scaffy** » Wed Oct 15, 2008 12:49 am

BE doesn't open. All it does is come up with the dialogue box, saying no mts port available or whatever. I hit ok or close it and that's it. It doesn't continue to open.

86GT · Post by **86GT** » Wed Oct 15, 2008 9:34 am

In the BE directory there is a folder called CONFIG. Open that and delete the LC1.xml file and then try that. If that does not work then delete the entire CONFIG directory and try it again.

Making new def for BE

Re: Making new def for BE

Re: Making new def for BE

Re: Making new def for BE

Re: Making new def for BE

Re: Making new def for BE

Re: Making new def for BE

Re: Making new def for BE

Re: Making new def for BE

Re: Making new def for BE

Re: Making new def for BE

Re: Making new def for BE

Re: Making new def for BE

Re: Making new def for BE

Re: Making new def for BE

Re: Making new def for BE

Re: Making new def for BE

Re: Making new def for BE

Re: Making new def for BE

Re: Making new def for BE

Re: Making new def for BE

Re: Making new def for BE

Re: Making new def for BE

Re: Making new def for BE

Re: Making new def for BE

Re: Making new def for BE

Re: Making new def for BE

Re: Making new def for BE

Re: Making new def for BE

Re: Making new def for BE

Who is online