CHANGES:
- Header editing. About time, eh? This only works with the dev/boost roms and the ITB Rom(s). The ITB vacuum headers are editable too as they are interpolated from a vector now.
- NOTE: in the dev rom header editing, there is a bug (feature?) that allows you to change an NA column to a boost column. I wont tell you how, though :).
- ITB maps now use the same formula as the rest of the obd0 vtec stuff.
- Fixed ITB code so that it uses the proper TPS memory and the proper vector for that mem. The column indexing has been pretty thoroughly tested for both all-vacuum (using the new vac vector) and all-tps configurations.
- Fixed the TPS formula in the logger. All this time it has been wrong for a couple of ecus.
- This release does NOT support older ITB roms. It may open them, but the TPS headers will be all wrong and the vacuum headers wont be properly edited.
- When starting an emulator session, BRE does not automatically 'put' the rom to the emulator. This can be turned back on in the emulator options.
- Due to some folk's logger timeout issues, you can adjust the number of tolerated bad samples. This is in the logger options at the bottom ("# errors before logger times out"). Default is 10. If the logger sees more than this value of consecutive bad samples, it will time out.
- Interpolation on the maps. Right click and there is an 'Interpolate X' which will interpolate in the X direction, and 'Interpolate Y' will interpolate all cells in the Y direction.
- Rom notes feature. You can add notes to your rom. Pr3 and pw0 only. Look in the Scripts menu. Shortcut is Ctrl+Shift+N. You only get 128 bytes. If you want more there will have to be a lot of whining.
- Fixed IAT logging in PR3 roms. If you have a boost bin, you will need to use the new bin. If you have an NA bin that you used the 'Add datalogging' feature, you can just click the 'Add Datalogging' menu item again.
- Got rid of the Pr3-93 logging bin. You must use the 'Add Datalogging' feature on 93 roms now.
CHANGES:
- fixed divide by 0 error in rpm calc for vtec roms
- save prompt displays the filename
- More support for NG60 roms
- Support for different map sensors: 2.5 and 3 bar.
- Codes disable functionality.
- 1 wire vtec support
- map trace can be had in the main rom window. In the Logger options, under the map trace group there is a new option 'In Rom' which will enable this functionaity.
- Interpolation trace is now supported in the Datalogger. You can turn it on or off in the Datalogger Options dialog. It positions a 'phantom' cell on the map being traced where the ECU is actually using. When enabled, the phantom cell should show up during logging and replays in both the rom maps and the Logger maps (provided you have both enabled). This only works for fuel as there isnt enough memory in the ecu to save ignition interp as well.
- The map's fuel formulas for obd0 vtec have CHANGED. They are no longer the same as the other obd0 formulas. They are now more accurate. Keep in mind these formulas will NOT change your maps, just the way the values appear. You will probably notice that the values are quite a bit lower. i.e. a value of 16 ms before will probably be somewhere around 13.8ms. DO NOT COMPARE MAPS BETWEEN OLDER VERSIONS OF BRE AND 2.2.3 OR LATER VARIANTS.
- RPM, Temp, and TPS calc functions in HondaEcu, VT0Ecu, Pm6Ng.
- Logging 93 rom included with the zip.
CHANGES:
- Fixed Pr3-93 basics (row headers, all params should work). I went through every feature in the param page and compared the code changes to that of the pr3-58's params. There is still no datalogging or any of the other "advanced" features for it. More features will be gradually added as I deem necessary.
- Stock Pr3-93 bin included with BRE.
- Loading of outputfunctions.cs is now done automatically.
CHANGES:
- Fixed the autostart. It now displays the file its actually writing to at the top of the logger window.
- Fixed logger. Opening the options no longer wipes the log files.
- Fixed the timeout on the NG logger. It will just wait on timeout, so dont shut the car off when logging.
- Took out dyno function. It will not be seen again until I get everything sorted out.
- CEL shift light is included in the build. You must load the script through the script manager.
CHANGES:
- Restructured some of the back end so the maps capture all byte changed events. Now, when a byte for the headers is changed in the ITB or dev column headers, the map is updated. This is preliminary code for header editing at the maps.
- Changed the ITB rom's column scalars. Also, for the time being there is a header editing mechanism in the extra tables for the ITB roms. Its all raw, but its better than winhex.
- Logger now logs final Fuel (in milliseconds) and Ignition (deg. of advance). The formulas are straight out of the code so they should be more accurate than what is displayed in the maps. BUT you NEED to use one of the NEW bins included with this release or the ignition will be way off.
- Dyno feature. It has been difficult for me to get good data so it needs a ton of testing. To use it, open a log in the log analyzer. There will be a dyno tab with the current run in the graph. To overlay runs, change the opacity/color, or change the parameters of the formula, open the Analyzer options and edit away. If you get a nice run with a nice graph I am requiring you to post the log file so I can see it. I realize its missing a bit of functionality (ie always in hp/ft.lbs and AFR), but it will come eventually.
- Got rid of the stupid Dev page tab for the dev roms. The map sensor option is in the main properties tab and the headers are not editable in the editor right now (until I finish the editing at the maps).
- There is an add logging script now so no more datalogging roms will be prvided, only stock roms. You MUST add datalogging to NA bins if you want to use the datalogger. The boost bins still have logging. When the logging is added, the pw0 bins no longer suffer from their odd running bugs.
- The boost bins are the latest and greatest. I made them more uniform and more 'stock' like. i.e. the maps are just extended stock maps so you WILL NEED to edit them. No more asking me what the maps are scaled for. They arent scaled. That is left up to you (well, BRE can do it for you).
- There is an IACV duty cycle adjustment script under the scripts menu. A smaller (read: negative) value means a higher duty cycle (its wierd, I know). The obd1 guys use a similar method for editing and their min is 120 while max is at -120. However, the code is slightly different and my car wouldnt idle at target with anything larger (value wise) than -350.
- I sped up the grid's painting A LOT. This should make the whole app faster: real time auto tune, map trace, editing while logging and emulating, etc.
- The LiveEdit downlading on the ostrich is now threaded. When you make a change or two, the number of bytes left to send is written to the ROM window's right status panel. Then you know when all of the changes were actually made.
- Fixed the Ignition retard bug. It now actually takes when you use the function.
- fixed locale issues. You still cant analyze or replay a log from a different locale, but everything works as expected. Also, no longer do you have to convert the bre.ex.econfig vals from '.' to the',' notation, its now implicit.
- General cleanup and unnoticable bug fixes.
CHANGES:
- Support for Xtronics Romulator.
- Gauges have a transparent background. Yay. To use the new feature I rearranged the gauges on the obd0 vtec datalogger (look in the script, the old code is still there, but its been commented out)
- More code cleanup.
CHANGES:
- locale: you can now use the ',' char for the decimal point in all textboxes and the grids if your locale specifies. Also, The logger will separate the log file data with ';' instead of the ',' if your locale specifies the ',' as a decimal point. That being said, you cannot analyze/replay logs from locales different from the locale on your machine (unless you change the locale).
- Datalogging AutoStart is up and running. The options are under the options menu in the Datalogger form. I will post a testing thread which explains how to use it in the BRE forum.
- Bunch of dumb stuff I found I fixed: text boxes that dont validate, replay->log mode or vise versa clears the grids, code cleanup, etc.
CHANGES:
- Will now switch map trace tabs on vtec transition when logging.
- Using anti-aliasing in the gauge drawing, so they should be prettier and not so jagged.
- Fixed the o2 logging bug in the euro boost code.
- Small changes to the roms: disabled checksum on all of them, made the maps all uniform (they are ALL now just extended NA maps. You must make your own base maps).
- Added an Extra Tables dialog (in the tools menu when a rom is open). This is for testing the vcal tables in the rom such as ECT, IAT, idle, and startup enrichment.
- Startup file: you can have BRE open a file on startup. Its in the File menu.
- Fixed the crashing on startup of a second instance. Now it will display a dialog telling you that 2 instances may be open. You can create multiple instance of BRE only when you have 2 installations of BRE, otherwise, BRE cant share the scripts or the brelogs.txt file.
CHANGES:
- Toolbar for open, save and save as. More are on the way, but I need to figure out how to do it in a clean (code wize) fashion.
- Ostrich connection code rewritten so it should be WAY more reliable when connecting to the device. Needs to be tested more. If BRE is killed and its connected to the ostrich, the ostrich will be left at 921.6k, so some other programs will not be able to connect to the ostrich (i.e. TurboEdit). This is fixed by connecting to the ostrich again with BRE (or TunerProRT). It always takes 2 tries to connect again at 921.6k with BRE, so do the ctrl+R, wait for the "No ostrich found" box, then ctrl+R again and it should connect. When BRE or a ROM is closed cleanly, the baud is reset back to 115200 baud and there is no issue reconnecting. If you have any issue connecting to the ostrich, LET ME KNOW.
- Can now type '-' in wideband adjustment boxes with all text highlighted.
- The lambda or afr option is propigated through the analyzer and the target afr editing tabs.
- Temp is right (or very close) in the datalogger script.
- Restructuring of config file data in the application (global Properties object).
- Real-time autotune bug that would only use the non-vtec target afr for both vtec and non vtec fixed. (needs more testing).
- Real-time autotune options Max Column Deviation and Max Row Deviation are now hooked up. (Real time Auto tune needs more testing)
- Target AFR event at RomRep level that propigates a target afr change to everything that uses target afr.
- Many minor exception catches and small bug fixes.
CHANGES:
- BRE now only asks to save the rom if the rom has been changed. A little '*' is put in the title bar of the rom if it has been edited, just like every other app in existence.
- You can now adjust the wideband output value if it is off. There are text boxes in the Datalogger options dialog. In a pinch, you could use this to defne a new wideband sensor. You could use the stock o2 definition (which outputs a raw value) then use the two boxes to input the formula of the new wideband (assuming its linear). The boxes are used in the general linear function form of y=mx+b. So the function is: final_output_value = multiply_box*wideband_corrected_value + add_box.
- The new Datalogger actually works. Its been tested on a PR3 and with an NG rom in a PS9. Realtime auto tune has been tested and is working with the new logger as well.
- In the logger options, you can no specify lambda or AFR. Internally, everything is in afr so the log files will be in afr, the autotune will be in afr, etc, but you can see lambda.
- XP look and feel (visual styles). If I missed anything (buttons or something), let me know.
- Better versioning. I will keep track from now on. Exe file no longer named bre20.exe.
- Fixed script references to bre.exe.
CHANGES:
- New datalogger. TEST IT. It is script driven so the operation of the logger for any ecu definition can be edited and extended.
- Fixed ITB support. There is a new ITB file within the zip.
- Tons of little stuff fixed/updated.
- The auto tune function can now block out cells you dont want tuned. There are grids under the auto tune options dialog box.
CHANGES:
- Scripting is here! READ THE API. READ THE INCLUDED SCRIPTS. The Script Manager is under the Extras menu (or F5).
- Small stuff (cleanup mostly)
- The JDM PW0 boost rom had some issues, it is now fixed. No more solid cel.
- ALL bytes that are changed are now sent to the ostrich. Yay. Before only the maps were sent.
CHANGES:
- If your boosted car with a bigger map sensor throws a code 3, its is because of the lower limit on the map sensor calculation. Today I uploaded new boost roms with the lower limits set to 0. That means it should never ever throw a code 3.
CHANGES:
- fixed a bug that negated the automatic multiplier detection. now all the boost efficiency and fuel adjust works with the 3 bar and large injector changes.
- NOTE: the lowest pulsewidth that the code allows is 1.08. It may display lower in BRE (until the save), but it cannot go lower.
CHANGES:
- Converted BRE to managed code. Finally.
- Opens multiple files from the open dilog.
- Revlimit is now 2 byte deal so you can go lower than 7219 rpm.
- fixed the command line open (so now you can associate BRE with bin files so it opens the file when you dbl click a bin file).
CHANGES:
- Boost efficiency feature. Right click in a fuel map.
CHANGES:
- Added multipliers for injetors and displacement change. Look under the edit menu.
- The scroll bars on the grid are the devil. I finally got them working like they should, but now there is a focus issue on the rom form. When clicking on one tab, the focus is shifted to something that isnt the tab page or grid so when you use the arrow keys it goes through the tabs and not the grid. I hate it but I cant figure out how to fix it yet and I have already spent 10X more time on it than I should have. You now need to physically click on the grid to shift focus so the arrow keys work.
- Some other random clean up/bug fixes.
CHANGES:
- I added a "high-speed" option to the ostrich options. it operates at 920k baud in high speed mode and 115200 baud in low speed mode. The reason for this is so people with computers that dont like 920k can still use the ostrich in BRE.
CHANGES:
- I attempted to fix the connectivity issue with the ostrich. Sometimes it would not connect and I dont know why. I rewrote the connect function so it should now connect without problem at either 115200 or 920000 baud, favoring, of course, 920k.
- I fixed some issues in the grid control. The scroll bars work better (they dont steal focus from the grid anymore) and I fixed some painting issues. Also, since the scroll bars dont steal focus, you can use the arrow keys to navigate through the grid. Finally.
- Other small, not noticable stuff fixed as well.
CHANGES:
- The gauges now dont eat processor time. Yay.
CHANGES:
- Rewrote most of the logging. It is now WAY faster. I got 20 samples per second (50ms) easy on my compaq AMD 2800+ laptop (system properties says 2 GHz). I didnt try anything faster. Please note that if you watch the digital dash while logging at high speed, much processor time will be used. This is because BRE needs to paint each gauge on each sample. I hope to fix this soon by rewriting the painting routine.
- Also, when you shut the car off with the logging going, It just clicks the stop button. It used to freeze.
- The realtime autotuning works MUCH better. It now does not overshoot the target. I was having a latency issue but it has been fixed. Now there are a bunch more parameters the user will need to edit. They are in the config file for now. They will not take effect until you stop and then start the realtime auto tuning. The only problem is that it is slow. So it is really only useful for tuning cruising when the cell does not change very often. This is because of the time it takes for the changes to propigate through the ostrich, ecu, and engine to make it all the way to the wideband and back through the ECU to the logger.
- Added a Autotune Options dialog box. It is in the edit menu.
- Small bug fixes here and there. Stuff that most probably wouldnt notice.
CHANGES:
- More Logging problems... They have been fixed. I think. Columns should* be 100% correct now. You NEED to use the new datalogging code contained in the roms provided for all this to work. All is working on my pr3-58 powered car.
- Datalog analyzer is more complete. It now has a target AFR for each map and calculates the difference between masured and target. The Target AFR maps NEED to be edited by the user the first time around. Obd0 vtec ecus dont have target lambda maps stock.
- The auto tune button adjusts the fuel map based on the difference between the measured and target AFRs. It works fairly well but is incomplete. Features for "locking out" cells to not auto tune, guessing for the cells not hit by the logger, and the requsite Autotune options dialog box will be added. For now you can edit the min and max autotune percentages in the config file.
- Realtime Autotuning. This is also incomplete. It *does* work, however. How well it works is yet to be seen. The idea is that you can drive around and BRE will tune as it goes.
- The copy and paste functions use the real clipboard now so you can copy and paste between BRE and excel, turboedit, Textpad, whatever.
- The option boxes now remember your settings. For this to work you need to use the bre.exe.config file provided. i.e. dont just copy the exe file into your BRE directory.
- The editor now automatically figures out the fuel multipliers. If the user enters a value that is too big, it will increment the multiplier until the current cell fits, and then it gets the other values in the row as close to what they were before as possible.
- Knock sensor disable added. Finally eh?
- Some dumb things that shouldve been fixed log ago. i.e. The child form menus now properly merge with the MDI parent, a little more exception catching, etc.
- Ostrich support. Go into the ostrich options and set it up how you like then click the "Begin Ostrich Session..." (or ctrl+R) and it will download the rom to the emulator. Sometimes there are issues connecting for some reason. I havent yet figured out why. It may take one or two extra tries to get it connected, but usually it works first try.
- It operates at 920K baud. If another app sets it to something odd then there is a slight chance that there may be issues with BRE connecting. BRE will connect no problem if it was previously set at 115200 baud or 920K. It does not try all possible baud rates because there is really no reson to. If BRE is closed normally and not killed by the task manager then it will reset the baud to 115200 for other apps. So keep in mind that if you, for some reason, need to kill the app you should open BRE, start and then stop an ostrich session to reset the baud rate for, say, TurboEdit or Crome.
- ONLY changing the maps and multipliers will write to the emulator. That means changing the revlimit, vtec, etc. will not immediately write to the ostrich. You will need to click "Put rom" (ctrl+shift+p) to rewrite the whole rom after making rom property changes. Dont worry its fast anyway (faster than even downloading a few changes in manual download mode). I may eventually make the properties download to the emulator, but at this point its a bunch of work with little gain (considering you can just click "Put rom").
- Live edit mode will immediately write the changes to the emulator. When the numbers in the map change to your values it has already been written to the ostrich.
- Verify the ROM every now and then to make sure all is well and your changes are downloading (ctrl+shift+V).
- If you feel so inclined you can unplug the ostrich in the middle of a session. When you are done doing what you have to do, reconnect and BRE will recognize the reconnect then put the whole rom so you can pick up where you left off. I was unable to find a way to have a real event fired when the port was reconnected so I am polling. If you know how to fire an event on a disconnect or reconnect please inform me.
- Unfortunately, I realized my serial library takes up ~10% of the processor when anything is connected with it. So I am looking into making it not suck. Sorry about that.
- All ostrich stuff was tested on PR3-58 code with the new 10.10.O ostrich firmware and was known working when this release was uploaded.
- This is new stuff so if you find any bugs and are SURE that its not because of user error contact me with as much information as you can think of regarding the bug (steps to reproduce, rom, other apps running, etc.).
- The user can adjust the fuel maps through the logger. While logging and watching the map trace the user can push ctrl+i or ctrl+d for a small change and ctrl+shift+i or ctrl+shift+d for a larger change. This will change the fuel value through the emulator in the cell that the map trace is currently on. In the Emulation options you can set the small and large change values, and can choose between a percentage or add type adjustment.
Of course, BRE will need to be in live edit mode for the changes to take place right away. Otherwise you will need to "put" or manual download after making a few changes.
CHANGES:
- fixed row and column logging now the rows are correct for non vtec as well as vtec. Columns are correct now as well.
- moved the loggers to a menu in the ROM. You can only datalog with a rom open.
- Added the rough draft of a datalog analyzer. All it does is display the avg AFR from the csv in each cell. It also accounts for interpolation so the afr displayed in each cell should correspond 100% to that cell.
- Datalogging is still very in progress. I am trying to sort it out with the ostrich, realtime editing, auto tune, etc.
CHANGES:
- Oops. I fixed BRE so it now opens stock obd0 vtec roms again.
- fixed the cel disable functions so that it works with pw0's
- Added a Jdm PW0 datalogging bin to the zip
- Updated the JdmPw0 boost code (try2)
CHANGES:
- Added boost ignition retard functions. Right click on your ignition map.
CHANGES:
- Added support for motorola 2.5 bar map sensor
- Added a cel disable function
- NG Datalogger is now for NG 55/56/60 logging code
BRE Documentation Home