new $EE tuning thing!

[steveo]

Is it safe to use the flash tools with the PCM in the car (not in a bench)?

of course, 98.2% safe!!

most people flash LT1s in-car. just make sure headlights are off, stereo off, heater off, connection stable, etc.

eehack tries to help by testing for connection stability before beginning the flash routine

If I understood correctly a patched BIN should not be read and tuned again. You can't patch it first then start tuning? What would be the best way to do with patches?

you aren't the first person to misunderstand what eehack's 'patches' are, or how they work.

i'm sorry i didn't document it better, i can't figure out how to explain it more clearly.

eehack's patches are inserted passively during flash specifically so you DONT have to worry about them.

it's done this way for a few reasons:

- nothing is ever written to disk, your tune on disk is not altered. you don't have to think about how you will 'un-patch' or save backed up 'un-patched' copies of bins. what a total waste of time. eehack does not edit bins.
- if the patches affect your car, just flash again with the checkbox unchecked.
- i wont have to distribute updated special XDF files with patches in them.
- tunercat users can use my software

you don't have to do anything. nothing will break. just leave the patch button checked. tune as normal. it's designed specifically so you dont' have to worry about it or do anything. just tune as normal and enjoy a few small enhancements to datalogging.

right before it flashes, it just flips a few bytes around. that's all.

there's one downside:

if you read that bin later, it's not exactly the same bin that you wrote. it's been altered.

right now that doesn't matter, but what if i have to patch a table relocation to enable some new feature in the future?

in short, just keep copies of the bins you're tuning on disk if you're going to leave patching enabled, dont use the ecm's eeprom as a backup for your virgin bin files. if you're planning to read your bin file back from the ecm every time you tune it, seriously, reconsider how you tune.

i think calling them 'patches' keep convincing everyone that i'm somehow messing with their tune?

if any of this bothers you, uncheck the patch box.

I am going to repair a couple of corrupted PCMs in a week or so (socketing and flashing). I have a bench setup, if you need to test any flash routines I can do it.

cool! it's working very well right now, but hang tight 'cause the next beta will need some testing, im working on increasing the write block size.

Thanks for the hard work. You should set up a paypal donate button in the program, lots of effort in this tool.

other people have suggested that too. you know, for the life of me, i can't seem to navigate around paypal's site and get a donate button working... maybe i'll try again.

[Montecarlodrag]

you don't have to do anything. nothing will break. just leave the patch button checked. tune as normal. it's designed specifically so you dont' have to worry about it or do anything. just tune as normal and enjoy a few small enhancements to datalogging.
right before it flashes, it just flips a few bytes around. that's all.

there's one downside:

if you read that bin later, it's not exactly the same bin that you wrote. it's been altered.
right now that doesn't matter, but what if i have to patch a table relocation to enable some new feature in the future?

I think this sums it all for me. It is as I imagined it would work but I wanted to be sure. So as long as you always flash with eehack you can tune as usual without worrying about anything. If you by mistake flash using winflash nothing happens, you only lose the datalogging enhancement. Cool!!

[sherlock9c1]

some reports today, using Beta3 (apologies):
1. When I'd lose connection to the PCM, it would never successfully reconnect. If I hit "disconnect" and then "connect," it came back up almost instantly.
2. Auto trans gear selectors do not work.
3. I got several Blue Screens of Death once I got over 20,000 records. ERR_MULTIPLE_INT... something. My phone camera did not capture it.

I will try the newest version momentarily.

[sherlock9c1]

Beta5 isn't working for me either. I'm trying multiple compatibility options (run as admin, compatibility for win7), no success, and no error messages.

The other complicating factor is that Windows 10 is doing some major updates. At least they did on 12/25 right before I installed Beta4. But Beta3 still works even after that.

I am getting an error on system startup now "There was a problem starting C:\Windows\System32\LogiLDA.dll"
The specified module could not be found. I will try installing this.

[steveo]

2. Auto trans gear selectors do not work.

i'd believe that, they should be working in the latest beta.

I am getting an error on system startup now "There was a problem starting C:\Windows\System32\LogiLDA.dll"

that's a mouse driver. i think your computer is haunted.

3. I got several Blue Screens of Death once I got over 20,000 records. ERR_MULTIPLE_INT... something. My phone camera did not capture it.

i've tested it to well over a million records (which is a huge unrealistic amount of records) on windows xp, windows 7, and windows 10.

Beta5 isn't working for me either. I'm trying multiple compatibility options (run as admin, compatibility for win7), no success, and no error messages.

one thing you could try doing, is use the old beta and 'reset settings', then close it right away. perhaps there's a bad pathname in there or something? still, i haven't really changed anything that'd prevent it from starting.. god knows how your mouse driver dissapeared, or eextra got corrupted during download either.

[steveo]

1. When I'd lose connection to the PCM, it would never successfully reconnect. If I hit "disconnect" and then "connect," it came back up almost instantly.

i can't reproduce that problem, either. are we talking key-off key-on kind of 'lost connection' or something else?

[sherlock9c1]

Lost connection was while driving on the highway on a 30 minute trip. Someone else was driving, I was in the passenger seat monitoring connection. All of a sudden the error #s would start skyrocketing, so I'd hit "disconnect" and "connect" and quickly everything was back up and recording.

I tried opening 4.0 Beta3 and hitting "Reset to Defaults" on the config menu, then opening 4.0beta5, and no dice. I'm not getting any error messages either. Is there some way to open it such that I get error messages?

[steveo]

that kind of desync shouldn't happen, and it should reconnect on its own after a few seconds of errors.