DA Data Errors?

[delcowizzid]

what adx are you using for logging link it up

[xtreamvette69]

using arap bin, $6E def file and 1227165_6E.adx

[xtreamvette69]

hmm ok so i'm still having this issue or having it again or got worse or something but it is a lil differant now that i edited the adx file to get rid of the DA data errors...i have read through many of the issue threads here as well as all around the net and most of what i see is problems getting it to work(initial connection) but no probs after that.

oh also failed to mention i am using the moates cable ('ALDU1 and CABL1')pricey lil bugger, sorry mark i didnt know there were any avalible on this site.. and cheaper too..
kinda thinking maybe sendin an email to moates about this see if he has any ideas, because for that much money for a cable i should deserve a lil support lol.

now what it is doing is working great, may take up to 20 tries showing data error till it connects(that speed has progressivly gotten worse it seems from what it use to be).

anyhow once connected works great was logging for many mins at a time(probably 5mins - 10mins no issues, but lately it is more like just a few mins(about the time it takes to get from cold to 170* sometimes almost 200* then bam..bombardment of red flash data errors, data doesnt update, if recording log it quits recording and it never recovers the connection.
click disconnect then reconnect = red flashy data errors, no connect.
close tunerpro then open it= red flashy data errors, no connect.
key off 20-40 seconds then on(read post talking bout this by moates someplace)= red flashy errors
even reboot pc doesnt always cure it, almost like its a time delay or temp that needs to cool off issue.

so to recap.. for a while after fixing errors with by editing ADX files with a pause/silance also fixed one with the adding 1 trick= all was well, never lost connection or had any problems. it was always me stopping the recordings not tunerpro having errors.
now after random length of time(usually less then a few mins) TP just starts erroring out (constant flash of error/connecting just like unplugging it) also same end result as unplugging it.
cant reconnect till it wants me to it seems, have tried a few ways.

any ideas? its back to almost being unusable again or at least not efficiant to run a recorded log session only to find that TP stopped responding long before you were done, so you have to do it all over again.

[EagleMark]

I've been reading stories like that with $6E data for years....

[xtreamvette69]

thats not helping and not what i want to hear.
why so random though, for days perfectly behaved then bam, nothing but troubles?
why do some never have problems? seems unlikely that the ecm's are just flakey on diff levels and random times.. must be some sorta trigger although i dont see odd behaviour on logs before it happens... i just feel i'm missing something here.

oh and did i mention this is a new rebuilt ecm as well.

i'm getting ohh soooo close to just getting a megasquirt and being done with this other factory stuff. not really but have been thinking strongly about it.

[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