Long story short I bought a blue cable local, turns out it has ch340 chip..(this was ages ago). I tried figuring it out with Logger,Lemminwinks and other stuff I was messing around with and it didnt seem to work.
Recently - few months back - I tried it again , new OS , etc. still couldnt get it to work. I used the CH chip drivers, maybe I could try with cdm/ftdi ones. I also have a VCDS clone( Atmege,rs232, and ftdi apparently) but couldnt get that to work either ages ago with lemminwinks , dumb or not it didnt matter, so I wanna ask the pros here ( so you dont ree @ me when I post vcds logs in the future lol).

So some people said you can use CH340 to log with ME7logger, is this true ? So far ive seen nothing else just that you can apparently.
Cheers.

I'll try to mess around with the drivers in the coming days, also with vcds cable too, maybe it works somehow

Aside this what the hell ch340 is good for lol..

Yeah, I figured something of sorts is going because I took both cables apart the and vagcom indeed had an FTDI chip - if I remember right - but it wouldnt work. I'll update if I figure some fuckery out.

IMO you're wasting your time

Time is money so it would be chepaer to buy a ftdi cable

Order it now, the sooner you order it the sooner you get it. And in meanwhile try to connect with ch340. My advice.

Allright, so turns out you can use CH340 based chip to log or do any K line protocol stuff most likely , even nefmoto flasher if someone would rewrite it to use com port instead of ftdi drivers etc.

Anyways here is how to get shiet working:

Install CH340 drivers without the cable plugged in.

Download link - http://www.wch.cn/downloads/file/65.html

Just run it and press install.

After that plug the cable into the obd port then into your PC, and wait a few secs , it should automatically detect it and it should say ur device is ready to be used.
Go to Device Manager and find the cable under Ports / Serial cables , right click it and go to properties.

Set the following settings here:



then press advanced and set the following settings here:



I'd advise to use COM4 , because COM3 is often used on laptops also make sure to always plug the cable into the same usb port to avoid issues. FTDI eeprom doesnt let this happen it always keeps the same com port even with different usb port.

You obviously need to have your ECU file from Me7info , this is explained in the ME7Logger readme. BUT after you get ur ECU file from info, open it in notepad and set the connection value to 0x00, like so
whatever ME7info thinks is good, change this...!

Connect      = SLOW-0x00

Use VisualME7Logger to generate your config files ( values to log) BUT you cannot use VisualME7logger because it seems to overwrite stuff and it simply doesnt work for now( for me , another user reported it works)...

When you generated the config file , open it in notepad and change Sample/second to 50 !!!

So to start logging, open a CMD window where the ME7logger exe is located and type ME7Logger -p COM4 log.cfg

COM4 being the COM port you use and log.cfg is whatever is your config file named ( that you saved in VisualME7Logger)

so have that command ready, turn ignition on, press enter on laptop and it should connect. After this start the car and your done

Maybe. But I posted them so if anyone has a ch chip they put the exact same settings and its guaranteed to work. You can set whatever I am just saying it works.

Yes I know the command line options, but it wasnt working before I changed sample/s to 50... and ox00 init mode, also it doesnt work throught VisualME7Logger.(for ME) .exactly why I posted the settings...

and yeah I know printscreen but I cba to put them on usb too when I am transferring shiet to PC to post here.