Delco OSE FlashTool V1.51

[VL400]

I end up having to kill the Flashtool with task manager and turn the ignition off in the vehicle.

I have had this very occasionally and suspect its caused by the chatter, it keeps on flowing holding up the program waiting for silence. Try reducing the silence timeout like VX_L67 suggested.

There will be some changes in future versions to try and better sync to the bus.

[3th4n]

I thought I had buggered my pcm today (VYII Berlina) - luckily I had got a few bins before I played with anything.

Flashing in a modified cal, progress bar went through all the way and I must've gotten a bit excited (I'm new to tuning) and didn't read the checksum box that popped up and clicked cancel!!! Then it tells me the flash failed......

I turn the ignition off and turn it back on and it wont start, also the check engine light is on.... No worries Ill just connect the cable again and flash in the original cal, but its not connecting.

I disconnected the battery for an hour and I'm thinking of wreckers in the area where i might get a new pcm. Reconnected the battery and it started and ran again so all good. Ill have to do a get bin again later to see if the modified cal made it in or if it reverted to stock.

Still gonna get another pcm anyway though, that was a little TOO close

EDIT: Yep it saved the modded bin but it threw the check engine light/no start problem again. Ive disconnected the battery again but I think I should reflash it with the Flash PCM Auto Fix Checksum box selected.

[VL400]

It sounds like the PCM has not reset after the flash process, some PCMs do this but have not been able to recreate the problem consistantly. If you do not hear some relays click and the fuel pump prime when everything is finished the PCM is likely stuck in the boot code still, disconnecting the battery or PCM plugs fixes it.

PM me if you want to try a different version of the flashtool to help fix the issue.

[Brados]

Just a question regarding a VY flash pcm. Recently I have been using Write Cal (with Flash PCM Auto Fix Checksum) and after writing the calibration data and resetting the PCM the Flashtool does not reconnect to the PCM properly. It just loops with "Waiting for Slience..." "Chatter detected after..." forever. I end up having to kill the Flashtool with task manager and turn the ignition off in the vehicle. However the vehicle will start and there is check engine light. What is happening here? I am sure I once had it working with the validation and checksum writing at it is supposed to. Vehicle is VYII Berlina (so more bus chatter if that helps any). Flashtool 1.45 but 1.42 behaves the same.

Hi All,

I final got around to purchasing a new laptop so I can get back into tuning again as I have not touched it in almost 1.5 years now.

Seem to have the same problem (VY Flash PCM), the flash tool won't connect as it cannot find silence. It seemed more like the tool was stuck in a loop than the car's actual silence as when I minimized the tool, right clicked on it and opened it from the task bar it would suddenly find silence and connect.

I ran a 'GET BIN' just to be sure it actually was connected and it worked. I should have stopped there.

I was then went to ''write cal' as I have a new tune I wished to load and it wrote succesfull however after the checksum part and the second write could not find silence and the 'trick' no longer worked. It wrote to a few selected addresses then kept failing, aborting and asking to retry with the same result each time.

Car is doing a few odd things now, after disconnecting the battery it now primes the fuel pump and cranks but does not start or attempt to start.

Any idea how to fix the silence issue? I would first like to attempt to salvage my current ECU before I start looking aroud for a replacement

I believe this is the first time I have used version 1.45.

What I do not understand is that the text says it needs 15ms, yet it states 'Detected chatter after 70ms'. In that past it only failed to find silence when it was less than 15ms if I remember? See attached. Any thoughts?

Cheers,
Braydon

[VL400]

There will be some changes to the silence detection code in the next release, I suspect windows is introducing some lag the way the code is handled in the current version. Windows 8 seems to have made things worse in this regard and when trying to find really short sections of free bus time its not working very well.

[3th4n]

Car is doing a few odd things now, after disconnecting the battery it now primes the fuel pump and cranks but does not start or attempt to start

How long did you disconnect the battery for? I don't know if it makes a difference but I had a similar issue that was resolved by leaving the battery off for about an hour. Worth a shot if you haven't tried it already.

[Brados]

Hi guys,

Cheers for the feedback.

I managed to get the flash tool to connect and write a single calibration to correct the failed one. Car is now functional again

However, it took a few hours of attempts to before I managed to get the tool to connect and not stay stuck in the waiting for silence loop. I tried disconnecting the battery for a while then lock, then unlock the car and I think it made the car a little less confused and let me connect that one time. However I have not managed to replicate this again.

I cannot seem to get the tool to connect at all now, however if I right click on the OSE tool logo on the task bar while it is stuck in the loop it seems to suddenly find the PCM and connect, however this is what caught me out before as when it gets to the checksum check after a write and needs to re-write this trick does not work.

Is is possible going back to version 1.42 would help (I don't have a copy of 1.42 however) or is it likely a windows 8 issue?

[VL400]

Can you try the latest 1.49 version, there is a change to how the silence detection is handled.

[j_ds_au]

Memcal Based ECU/PCM: The requirements are that the ECM or PCM is fitted with a NVRAM in place of the memcal loaded with a write capabale bin (ie OSE code)

Sorry if this is a newb question, but the NVRAM and OSE code is only needed for writing, right? So I can just read a stock PCM bin without such? (Then there's the problem of only being able to read a partial bin if it's banked, but that's another matter.)

Joe.

[VL400]

Correct, read only from a ECU/PCM running a memcal with the limitation of only getting one bank (you get the calibration area so can check out the tune still). Flash PCMs can read banks correctly as I have a bootloader that is uploaded to the PCM, it overcomes the 64k memory limitation of the factory byte request mode.

If its a factory memcal we have most bins packaged up in a tool .. http://pcmhacking.net/forums/viewtopic.php?f=3&t=905