by cgrey8 » Sat Apr 07, 2007 6:20 pm
Some of the features I think need to be elaborated on:
02 ) Allows the user to mark rows while logging.
When you are datalogging down the road, you sometimes want to mark a place in the tune. If the engine starts misbehaving, you can quickly reach over and hit the CTRL key (or whatever key Clint settles on) and this will put a mark in the datalog. Then as you go back and look in the datalog, you can go right to the key places you wanted to see. In a 1 minute datalog, this is hardly useful. But in a 30 minute datalog, this can be quite handy.
03 ) Save separate payloads for different strategies
Unlike CalEdit, BE only shows saved payloads that are correct for the selected strategy so you don't see CBAZA-saved strategies when you are working with a GUFB BIN file.
04 ) Retrieve payloads form the TwEECer and then save them.
05 ) Allows different Payloads for each switch setting within the TwEECer
CalEdit would download different payloads, but because it COULD NOT upload the payload back out to make use of having different payloads down in each position. In fact if you switched BIN positions without downloading the current payload that CalCon was aware of, you'd just get trash. With BE, you can upload the new position's payload and start datalogging right away without having to redownload/write to the TwEECer.
10 ) Payloads and Definition files are open source.
This means if you've been working with your tune in CalEdit and haven't converted to BE yet, you can upload your tune from CalEdit (or the EEC stock tune), save it as a *.BIN file and start tuning in BE right away. Thanks to 04 ), you can even upload your CalEdit-defined payload into BE and start datalogging immediately.
Because the strategy and BIN are open source, any assembly-language BIN hackers out there can develop their own strategy file for them. But if you want a good starting point for developing such a definition file, I'd look and see if CalEdit does support your EEC's strategy and start using it to write off to the TwEECer, then read the CalEdit tune back out using the BE, next change something (scalar/function/table) in CalEdit. After that, read that changed BIN out using BE. Then, compare the two files in a HEX editor to find what you changed in the BIN. That's the hard piece of info to get. Assuming CalEdit has it right, you can at least get what CalEdit has. As you find more info beyond CalEdit, your def file is a solid foundation to work from.
So all this, not to mention the biggest features of them all...Clint's the developer, not someone that could care less about the customer. For those that are regulars on this forum, you know Clint has a reputation of standing by his product and actually FIXING bugs. I, for one, have no intention of using CalEdit ever again.
...Always Somethin'
89 Ranger Supercab w/97 Explorer 302, Explorer (GT40p) headers, C&L 73mm MAF, TREPerformance 255lph fuel pump, aftermarket T5, 8.8" rear w/3.27s, Powertrax Locker, A9P & Moates Quarterhorse
Member
V8-Ranger.com
)