[93foxturbo]

ok guys since my car is off the road for winter, i think its good time for me to figure out my tuning issues. my biggest issue with tweecer was lack of explanation about some tabs in scalars,functions and tables. recently i been doing some research and figured out a way to datalog boost and afr using dataq-which i will be ordering shortly. i also noticed lot of ppl recommend binary editor software over tweecer. main reason seems like its easy to work with vs tweecer but that means i need to pay $70(us funds) for license. so heres my question:
1)- in your guys opinion whats the main advantage of switching to binary editor,since you guys have more hands on experience.is it really worth it as some ppl swear that it works awesome and theres no need to switch to BE.i really had no problem with tweecer as it gets the job done.
2)-can BE datalog if buy license?

btw i got 1993 mustang lx,5.0 with single turbo.stock engine and stock ecm with tweecer r/t.
thanks guys.

[cgrey8]

First off, what EEC and strategy does it use? Before you can consider BE, you must be using a supported EEC. Otherwise it's a moot point.

Assuming you are supported or are willing to swap out your EEC for a more common EEC like an 89-93 Mustang EEC, then you cannot go wrong with BE. You can even evaluate using it as an editor for free. This does require that you continue to use CalEdit/CalCon to write your tunes, configure your payload, and datalog. With a licensed version of BE you can abandon CalEdit/Calcon altogether.

[93foxturbo]

sorry i forgot to mention.....i got 1993 mustang 5.0 with single turbo.i have tweecer r/t currently.

i will edit my first post.

so if i read it right i can get BE working without registering it(i.e-pay $70)?? so do i just make changes in BE but still use calcon to datalog? i downloaded BE couple of weeks ago and all the tabs under tables,scalar,functions are empty. i would like to atleast use BE without having to register just to compare how easy it is VS caledit. wont mind paying to register if its way better...know what i mean?

[cgrey8]

Yes, you can use BE as a tune editor. What EEC do you have? Telling us that will indicate what def file you need to open in BE.

Once you open a def file, the scalar/function/table tabs will have things listed. I believe you can now use an unlicensed version of BE to upload your tune out of the TwEECer so you can begin editing it using it in a free capacity. See since CalEdit saves your tune in a proprietary format *.ccf, you can't load your tune file into BE. But you can upload it from the TwEECer. So once its uploaded into BE, save it in *.BIN format which is not an encrypted format. From there, edit away at the tune. Save it. And open the resulting *.BIN tunes you make in BE in CalEdit to download/write the tune to the TwEECer. CalEdit should let you open a *.BIN file, it just won't let you save your tune in *.BIN format.

[93foxturbo]

i have tried opening BE and the def file tab doesnt even light up.if i re start BE then it lights up.but when i click on it error message"the path is not of legal form" comes up.

i have 1993 eec so by soing some research i need to load guf1 file??

[cgrey8]

Def file tab???

[93foxturbo]

yes when you open BE,to the left bottom corner it says "definition file".underneath there are 4 tabs. one with the file symbol.it only lights up once.when i click on it error message "the path is not of leagl form" shows up. after that i cant click on the tab anymore.

[cgrey8]

That sounds like a bug. Report that to Clint G....he's the developer of both BE and EA and is active on this forum as 86GT.

[93foxturbo]

i wonder if i should delete BE and download it again and see if that helps.

[cgrey8]

Also make sure you are using the BE32, not the BE16. And when it is downloaded and installed, run the Web Updater to update it to the latest code.

[93foxturbo]

Also make sure you are using the BE32, not the BE16. And when it is downloaded and installed, run the Web Updater to update it to the latest code.

yes i just deleted and downloaded BE32. now i was able to click on file tab and choose guf1. but now i see message saying "go to about tab to register definition file and BE" after i click ok to this message another one pops up saying "check the file name and make sure it has revision number within it.the name of the file must have phrase'revx' within the name.'x' can be replaced with any valid number"

after i click ok to that i see nothing under tables,scalar,function drop menus... man this is hurting my head

[cgrey8]

Again, those sound like bugs.

That should show you how few people actually use BE in an unregistered capacity for bugs like that to exist and not get reported...assuming this isn't something misconfigured on your end.

Work with Clint to get them resolved. BE is free as an editor or at least as far as I know.

[93foxturbo]

ok it was my fault. seems like when i was opening files,in the bottom drop menu i forgot to change to files of type to "all supported files"-that opened latest guf rev 43z so now its all good.i got all my scalars,tables,functions filled up.


i guess from here on i need to read factory eec to see the values but if i remember correctly since its an unregistered version it wont allow me to read eec stock values.therefore i must input values to every scalar,function,tables manually ---correct??

[cgrey8]

I asked Clint to change that behavior to allow people to read the TwEECer to do exactly what you are trying to do. It won't let you write values without being registered. But it should now let you read the TwEECer so you can get your tune WITHOUT having to fat-finger all the values back in.

[93foxturbo]

so let me just go over step by step what i think i need to do from here.lemme know if iam correct.:

-hook up tweecer to laptop.
-open BE and click on "read(upload)tune from hardware"-this will hopefully fill in all the values for functions,scalars and tables.
(or can i read factory eec instead of tweecer??)
-make necessary adjustments on BE and click "write (download)tune to hardware".
-open caledit and select payloads and start datalog with calcon.

can i do this without having to register? this way i can atleast compare the caledit and BE and if i like it i will register it to get rid of caledit and calcon altogether.

BTW i was looking into this 6-7 months ago middleof season but was discouraged on the sole reason that it wont let me read tweecer at that time. its great that clint is looking after customer's concerns unlike tweecer IMO.

thanks a lot man for your help.seems like iam getting somewhere.all i need to do now is order dataq so that i can datalog boost and afr in calcon.

[86GT]

I am jumping in late but being a 93 I would think it is a GUFB and not a GUF1. Look at the EEC and read off the 3 or 4 digit code. It should read something like A9L or A3M, or A3M1 or something like that. This calibration code will tell use what definition file you need.

Like chris mentioned make sure you have BE 32 and Not BE16. The BE version number should be 2.3 or better.

[93foxturbo]

my eec says A3M.and yes i ended up downloading 32BE.right on top of my BE it says binaryeditor2.3.6 so i guess i got the latest version.

[86GT]

Ok that means you need to use the GUFB definition file and not the GUF1

[cgrey8]

so let me just go over step by step what i think i need to do from here.lemme know if iam correct.:

-hook up tweecer to laptop.
-open BE and click on "read(upload)tune from hardware"-this will hopefully fill in all the values for functions,scalars and tables.
(or can i read factory eec instead of tweecer??)

You can do both. But with a GUF1 strat EEC, there's not a really compelling reason to upload the stock tune. The stock tunes are readily available in the GUF1 definition folder in your BE installation as well as most of the other supported strategies. Uploading your CalEdit tweaks from the TwEECer is really what you are after.

-make necessary adjustments on BE and click "write (download)tune to hardware".

ONLY if BE is registered. Registering BE will let you write your changes back to the TwEECer. With the unregistered version, you can only upload/read the tune. Then save it to a file. To get your changes back into the TwEECer without registration, you'll need to open the file you saved from BE in CalEdit and write it that way.

-open caledit and select payloads and start datalog with calcon.

Once CalEdit has written your BE-edited tune, then you can datalog with CalCon like normal. Again with a registered version of BE, you can do away with CalEdit/Calcon.

...can i do this without having to register? this way i can atleast compare the caledit and BE and if i like it i will register it to get rid of caledit and calcon altogether.

Again, you can read only with an unregistered version. But you can write out anything you do in BE back to the TwEECer using CalEdit/CalCon. In a free capacity, BE will only let you upload and edit the tune. Once you register you can write and datalog from BE.

...BTW i was looking into this 6-7 months ago middleof season but was discouraged on the sole reason that it wont let me read tweecer at that time. its great that clint is looking after customer's concerns unlike tweecer IMO.

Clint is a VERY active member of the tuning community and of this forum unlike Mike Glover (the guy that gets your TwEECer purchase money).

...thanks a lot man for your help.seems like iam getting somewhere.all i need to do now is order dataq so that i can datalog boost and afr in calcon.

It sounds like you are on your way. With a registered version of BE, setting up the DataQ is 100x easier than with CalEdit.

[93foxturbo]

cgrey and 86 gt thanks a lot guys for help. i already hooked up everything and read caledit tune from my tweecer.got all the values for now and was playing around with them..went through different scalars,etc. sawsome explanation on certain tabs in scalar which is nice.

one thing i was curious was to see how maf transfer in functions is setup in BE opposed to caledit. in cal edit you can go lean or rich using % if you want to,didnt see that feature there in BE or am i just missing it somewhere. reason i was curious was it took me hours if not days to get the maf transfer running right in caledit and having that % feature was nice atleast to get it in ball park.also noticed there werent any pre saved MAF files when i went into import.was hoping to find 80mm C&L maf with 42lb calibration in there.

things i liked about BE was it seemed its way faster compared to CALedit. uploads are going way smoother then CE. i wasjust kinda fed up with CE not reading or communicating with eec or laptop.

again guys thanks a lot for putting up with my newbie questions.

[86GT]

You can highlight cells in BE and then right click. You have a bunch of options from there. You can multiply divide subtract and add.

[cgrey8]

Adjusting the MAF rich or lean by a percent is what the multiply by feature will do in the right-click menu. However instead of that feature being limited to only the MAF curve, you have that functionality on ALL parameters in BE...scalars, functions, & tables. Tables will most likely use the add/subtract features the most. Functions will likely use multiply/divide the most.

And yes, after dealing with BE and learning all the ins and outs, I think you'll find it's well worth registering so you can abandon CalEdit/Calcon. Not to mention, values are more accurate in BE. The biggest one being CalCon datalogs Injector PW wrong. It's close, but wrong and thus trying to tune Injector Slopes using CalCon datalogs will prove most frustrating because no matter how much you adjust, your slopes will always recalculate to something smaller due to the inaccuracy. We lived with that for YEARS before we figured out Calcon was just doing flat out wrong. And since you can't change the behavior of Calcon, people that use it are just stuck with it. But in BE, we had the ability to correct the problem and now slope calcs from EA come out far more accurate than they did with CalCon.

Another thing, CalEdit mislabelled some of the spark tables. Sealevel, Base, and Alt spark tables are mislabelled in CalEdit, but correct in BE's GUFx defs.

The GUF1 (A9P) strategy in CalEdit also never exposed the Adaptive Control table for users to edit it, nor the Transient Fuel table. But it's there in BE.

But did any of that ever get updated/fixed in CalEdit? No. And likely never will hence why BE came to be in the 1st place.

[wa_4x4builder]

Like chris mentioned make sure you have BE 32 and Not BE16. The BE version number should be 2.3 or better.

Can someone take the few moments to school us on when and why you'd want to use BE32 vs. BE16 and how do you know which of the .cry files to use? I've got an A9L, but with two .cry files, I'm not sure which to select and having done a diff to determine what makes them unique. There must be a reason or there wouldn't be two of them :-)

Thanks,
Chris

[cgrey8]

With an A9L, you shouldn't need a CRY file. CRY files are def files that are encrypted and thus require licensing to use. All of the GUFx defs are open source and thus don't require licensing to open in BE. If you have a CRY file for a GUFB strategy, then don't register it as the "free" one is feature complete. BTW, GUFB is the strat the A9L is a member of.

As for which version of BE to use, the BE32 is the newest and has all the updates. It works on the more popular EECs...mostly the EEC-IVs. However the newer EEC-V stuff is not converting from BE16 to BE32 as fast. So for the few that use the unconverted EEC-V strats, they need BE16.

[wa_4x4builder]

With an A9L, you shouldn't need a CRY file. CRY files are def files that are encrypted and thus require licensing to use. All of the GUFx defs are open source and thus don't require licensing to open in BE. If you have a CRY file for a GUFB strategy, then don't register it as the "free" one is feature complete. BTW, GUFB is the strat the A9L is a member of.

Makes sense on the A9L; but on some of the other supported .bins/strategies, there are multiple .cry files. For example, CZAW0, there are two .cry files available. I see a file named CZAW0 Rev 14ro.140.cry and CZAW0 Rev 17Cro.141.cry (typing from memory, so they may not be *exactly* named those names). Why two files? Which is the one to select? I'm going to take a WAG and say one is for the BE16 and one is for the BE32, is that correct?

Thanks for the answers.

[cgrey8]

That sounds like left over remnants from old configurations or something. Looking on the BE def file webpage, I see there's only 1 CRY file. It's a Rev9 and its indicated as ReadOnly. That means you can open it with a tune to view the def before purchasing to make sure it has everything you are going to want.

However I do see 2 CRY files in the GURE and I don't know why. You'd need to contact Clint to find out why he's got 2 CRY files posted there. But just speculating, I'd assume you want the one with the higher rev number??? But that's just a guess.

Upon purchasing, you should be receive a CRY file that will work with your BE installation. The CRY file will be married to your BE installation instance so it will only work with the BE installation it was coded for. If you need additional copies for other BE installs, you'd need to work that out with the CRY file supplier which would not be Clint. CRY files are developed by individuals other than Clint and they support their file independently of BE.

[86GT]

Yes currently CRY files are for thos individules that want to create definition files but protect the contents within. It the folder where you found the CRY file is a text file that has the contact information for that cry file. You will need to email that person for a unlock code.

The letters 'ro' in the title is 'Read Only' This allows you to load it in BE and see the tuning parameters. It will not allow you to save the tune. This is so you can see what the definition file has to offer before you purchase an unlock code from the owner.

Chris is correct, use the higher rev number. I will clean up the old files.