DA Data Errors?

[RobertISaar]

i don't think it is a 6E issue so much as the 7165 in general. some are just really flakey when it comes to comms.

[delcowizzid]

does it only happen with 6E or all code bases.are the sensor grounds and ecu grounds earthed seperate and do you have hard drive protection on your laptop it can cause logging issues when it stops the HD spinning when you bump your laptop causing log issues

[xtreamvette69]

RobertIsaar][/COLOR] i don't think it is a 6E issue so much as the 7165 in general. some are just really flakey when it comes to comms.

behaves same as it did with the old other ecm. but why was it doing so good then with no changes now so bad? why so random and yet consistant?i can connect and disconnect from it indefinatly without issues probablyforever but once log/record a while it wont let me connect no matter what i try till its ready. think more or less delay(listen for silance would help?) oh and i just checked and saw that moates just updated his driver install exe, think it was updated for a reason or just because the chip manufacturer has new drivers up?

does it only happen with 6E or all code bases.are the sensor grounds and ecu grounds earthed seperate and do you have hard drive protection on your laptop it can cause logging issues when it stops the HD spinning when you bump your laptop causing log issues

not sure about anything else except the 6E as thats all i've used it for l8ly, it did log the old 870 ecm fine without issues. but then again it was logging the 165ecm without issues as well.

as for grounds, the harness has only been repinned to the 165 ecm so grounds are same as the would be on a 86 vette, i have checked them and cleaned them as well as added more.. like i said all problems seemed gone and all was working great then it just started this behaviour all over again.


i do have HD protection on this lappy and it is on but wasnt giving any issues just before this and doubt its activating as it will data error jus setting still in ideling car on the seat(guess next try i should watch to make sure the HDD protection doesnt activate but doubting it does)

like i said though, the oddest part about it even though random seems to be that it only does it once car is warmed up.. usually 170*-200* then doesnt want to reconnect till some time passes or car cools some. might be coincadence but seems odd.

also as i said logs dont seem to show any odd voltage etc before it happens unless im overlooking it. reason i say unless i'm overlooking it is because one of the last times it happened i noticed something i thought odd(my oil pressure gauge on dash usually displays 80# at idle or close, sometimes dropping to 79 but the last time TP errored out my gauge dropped to 55 just before or as it started erroring) i really should investigate that gauge sending unit and wiring though anyhow because setting at 80 always at idle jus seems odd as well.

also TP is in record mode when this happens, could that be important? i should hook to and log it just with key on engine off, log and record key on engine off, log running, log and record running.. just to try and nerrow down and or eliminate possibilities, think that would be a good idea?

[xtreamvette69]

ok did further testing and these are my findings on what i checked, idk if any help or not.. i just dont know what else to check.
i checked and will add that FTDI is on com 4 and driver ver is 2.8.24.0

---cold engine (hasnt been run in past 24hrs)
---key on engine off took 37 errors to finally connect.
---connected and logging/recording @ 3:25pm, TP is running at 8:21-9:86HZ
---at 3:35pm i activate HDD protection by shaking pc=no errors or problems.
---at 3:38pm the ecm case and chip are at 79*f
---at 3:40pm i start the engine TP still logging and still recording.(no new errors)
---at 3:58pm engine is now up to 203*f and fan has kicked on. (no new errors)
---at 3:59pm just almost exactly as fan kicks off (errors begin flashing and no connect) ecm case temp is @ 90*f and chip is @91*f...........................
.................................................. ...............................................
---after trying everything such as shut down TP then restart=nothing
---key off wait/ key on= nothing
---disconnect everything/ reconnect=nothing
---blow on ecm/chip
---4:08pm finally try to connect after blowing on ecm/chip ecm is 77* and chip is 78* car 197*f i get 16 errors then a connect. (ecm and chip temps coincedence?)
---4:12pm i start car still logging but no record
---4:16pm i get just one data error glitch
---4:17pm constant errors and not able to log or connect again... ecm case was only up to 84-85.5*f and chip was 93*f-96*f

---------------this was the end of my testing-----------------
all testing was done under the mild conditions of just setting and idling.
also keep in mind that it is an infered temp gun and being closer or further away and angle effect it some, so temp may not all be exact but close.

another test i did When TP lost connection and wouldnt connect besides trying the handheld, i also tried to jump A&B terminals ALDL and that was working perfectly..fan came on and started flashing the all ok code 12.

[delcowizzid]

burn a different code onto an eprom even if it doesnt suit the car and swap codes once upto temp and see if you can connect

[EagleMark]

That would see if it was the mask... so maybe $32?

But as Robert said he does not beleive it is $6E and it is ECM, when I said I've been reading those stories for years it just happens to be $6E, but your temp testing is sure pointing at a ECM issue!

Some guys with that ECM have no issue...

[RobertISaar]

32, 32B and 6E, i've seen all of them do it to some degree. i really have no idea why either. it's one of the reasons i've shied away from anything 7165 powered.