On windows you can just use my logger, it is way easier and the patch for SLOW-0x00 is built in. It's free for the C167 ME7 controllers.
Will need to get a J2534 cable. There's lots of cheap tactrix clones on aliexpress. While I wouldn't recommend them for professional use, for hobby use they certainly work well enough.
Thank you, I have not came across your logger while searching for solutions
Right now I am already deep by 3 cables. Myself personally I don't have issues at the moment, and buying J2534 cable just to reconnect with the engine running is not something I need.
Good writeup but the main thing is the 0x00 connection,otherwise it works exactly the same as an FTDI cable...
I was not able to connect with my FTDI cable (which I bought after failing to connect with C340)
so that's why I wrote this how-to, to help total newbies like me to not waste 3-4 weeks looking for that GOLDEN cable and magical settings.
If you buy a cheap blue cable on ali/ebay - you're guaranteed to get CH340.
Also continuing about your message: not only 0x00, as with that - I wasn't able to connect as well. It's a combination of 125000 baud rate for more free k line, a 50 sample rate AND slow-0x00 connection. That is what lets you connect without a new wire pulled from ecu to obd2 OR pulling the dash fuses, as mentioned in tl;dr comment
I like the last option about visualme7logger
So you've made all this cmd things and the last one says there is a GUI for that
What I meant that this helps with VisualME7Logger as well, as it's using ME7Logger in the backend. So if you did all the changes mentioned, you would just have change COM port in Options (the -p option in cmd) and change SLOW-0x11 to SLOW-0x00 because that is not picked up by GUI from the ECU file