I burnt my 2nd chip today and took the car out for a test drive again. Anyway this is the 2nd time this has happened it also happened when I put my 1st chip in.

The 1st time after I put my 1st ever burned chip into car the SES light came on and stayed on. I plugged the scanner into my car AutoXray and it found no errors.

So I start the car again and SES light does not come on. So I took the car out for a drive and all was fine.


Today I put my 2nd chip into car after editing my 1st chip and start up no problems and head to the shops. I park the car after about 5mins of driving and visit the post office and come back out to the car.

I start the car and the SES light comes on. The laptop with the AKM cable and moates software could not communicate with the ECM and could not establish connection. The runs rough as **** and I get home.

I think to myself WTF??

I get home talk to my mate for about 5mins get back into car and start the car and it starts up and no SES light and sounded good. The laptop communicated with the ECM and all was normal.

I did disconnect the battery terminal before putting in new chip.

Anyone have any ideas? Could it be a bug using WinBin? Or something else. Cause this is very strange.

The car runs good now and I did not do anything to it.

 

a couple of thing i could think of. the moates adapter is not fully seated. the zif is not fully seated in the adapter. the chip is not fully seated in the zif. just some things that cross my mind when i see stuff like that. worst case could be a bad header on the ecm it self.

 

may also want to check all the solder joints on the moates adapter too. i have three of the adapters and they are all great, but it's possible a bad solder joint might have slipped past him.

 

I can pretty much rule out solder joints because I am not using the moates adaptor. I have a low profile zif adaptor soldered onto the memcal which has good joints! Then I have an aries ziff adaptor seated into that.

The only real thing that it could be when I think about is that my memcal is in 2 pieces. I cut the memcal in 2 cause I had my 86 memcal and that had the low profile zif socket on it.

So I cut that off and I also cut my 92 memcal so I had the knock sensor circuit. I then placed these 2parts into the ecm. It is a tight fit and maybe it is a little tight and not seated 100%

I might need to pull it out and file away from the both ends just a fraction more so they don't push on each other and pull each other up.

The is possibly the only thing, or it could be WinBin. I wanted to burn my 3rd chip with spark table adjustments but it would not burn the chip programming fault.

So I thought it was the eprom programmer or the eprom but when I burnt my 2nd chip again it did it no worries.

I think I might get the TunerCat TDF for my car.

 

i prefer tunercat and the moates adapter. the tunrecat software is much more user friendly and the GUI really makes all the diference. the moates adpater works good for me get one.

 

I am pretty sure that I uncovered the problem.

I also performed one more test to see if the new chips I am burning are correct. Well I placed my stock copy of my original chip in and the SES light comes on and then off and on again before I start the car. It kinda flashes which is correct before starting the car. Then it turns off when the car is started.

The new chips that I have burnt behave differently. The SES light will come on but will not go off and come back on before the car is started. The light just comes on and does not blink like it should. Once the car is started it turns off but there is also another problem I just discovered.

My fan turns on without any reason when the fuel pump primes!!

So I can definitely say now that WinBin is buggy as hell and should not be used. I used the version 0.11 I know they have a version 0.14 but I never could find a ECU file that worked with it well. All the numbers were messed around when I opened it up.

Looks like I will get the TDF definition file.

Is anyone else using WinBin and having no problems if so what version and what ECU file? Could you email it to me please.

Thanks,
Mike

 

don't know if it will help you but I have a bad 29c256 that for some odd reason will occasionally mess up. I could start it up sometimes and would run fine, and sometimes I could start it up and check engine light would come on and get no communication to scanner and then mysteriously go off again while driving. The times it messed up I could bring it in and read the prom and the first few lines of data were FF. Reburn and all was well. This is the only prom that gave me problems my other one works fine all the time.