Suddenly can't read ECU (using standard tools or mss6x flasher). Any ideas?

[S54B32]

Are you aware of newer/better/different drivers than the 2.12.36.4?

Depends what exact chipset you have inside cable. VID and PID from device manager help. I mean there are TONS of possible serial converter chipsets, of course most are like 2-3 different ones that are used in these typical cables

[Tbonem3]

Are you aware of newer/better/different drivers than the 2.12.36.4?

[S54B32]

Yes, they're always empty anyway, I rename them and move them to a back up folder right away, and clear the contents of the files to remain in WORK folder.

But would that have any impact on reading with Mss6x flasher? I think you just need Ediabas installed for that?

I'm wondering if there was any way to ruin the 2 cables I've been using the past few weeks. That's my only thought.

Check again drivers (or better reinstall), depending on what cable they use different serial converter chips and therefore different drivers. And they also get sometimes different com ports assigned. Had similar issue long time ago

[Tbonem3]

Yes, they're always empty anyway, I rename them and move them to a back up folder right away, and clear the contents of the files to remain in WORK folder.

But would that have any impact on reading with Mss6x flasher? I think you just need Ediabas installed for that?

I'm wondering if there was any way to ruin the 2 cables I've been using the past few weeks. That's my only thought.

[kaiv]

Tried clearing your TRC/MAN file?

[Tbonem3]

Well I still don't get it, but I'm back connected again.

I got a 3rd cable, the cheapest one yet, non switchable, just dcan (unbridged 7/8) for E90, and it's connecting. So my expensive ediabaslib loaded cable and my decent switchable k+dcan cable both magically stopped working at the same time? Very odd.

Anyway, at least I can connect. I'm thinking I should count my blessings that I've been able to code the car with everything I want and I shouldn't press my luck with any more fooling around lol. Back to suspension and exhaust work for me I think :P

[Tbonem3]

As I said, everything was working. No changes to windows/drivers. Everything is correct that I can think of.

Probably need to see if someone else's computer works. My schwaben scanner does connect, so I'm thinking my computer, but it was just working and I double checked all the common settings/issues. So damn frustrating.

Oh, forgot to mention something - the laptop and software work perfectly with my E46 so go figure. I got one thing telling me it's the E90 that's the problem, yet I can connect with schwaben tool and conduct all of the functions, so then I think laptop/cable, but they connect to E46 just fine. WTF.

[ppm008]

Windows version ?
any Update ?
Virus and or scanner ?
check path of system, ediabas path present ?

[Tbonem3]

Random issue if you don't mind mulling it over.

I've been coding and doing a little bit of flashing the last week, no issues with most of it. I recently replaced my battery, registered it (tool32). Nothing else has been touched.

Anyway, just yesterday I tried using INPA, winkfp, NCSexpert, and am getting an error about not communicating with module.

Almost all advice online is the common stuff, check ftdi drivers, com to 1, latency to 1, etc.

Well all that was already done, I was communicating fine, but now can't. I try Terra's MSS6x flasher and it can't read the ECU.

Car works perfectly, I don't think I bricked it. Now, my Schwaben scanner (foxwell) still connects fine, I can read errors, clear adaptations, exercise modules.

Could both of my cables magically go bad? Really strange and its got me pretty depressed. This is why I really don't like computers. I didn't do anything out of the ordinary, and now can't read the ECU. even though the schwaben tool seems to.

I looked at the physcial OBD port, and it does look like some pins got deformed a little or pushed to the side. I straightened them all out, and still no dice.

Has anyone heard of not being able to access the ECU yet the car still starts and runs fine? Almost every thread turns out to be a issue with flashing. I only flashed the mss60 with winkfp once, and it worked. Most of the other work I've done is with NCSExpert.

Thanks