thank you for the precise answer mr prj

In my case I am not 100% convinced its the cable, because like I said it only ever worked with slow init on 0x00 adress not 0x01 even if that is supposed to be the ECU... but even ME7logger/visualme7logger require manual change from 0x01 to 0x00 init otherwise it will simply not work. Even on K-line cable cutting j2534 from the picture.

I have also flashed a different software on my ecu (018CM) which has support for KWP2000 and such.. irrelevant but I tried Vehical again with the cable again now and instead of the timeout error it simply says no reply to 5 baud init from ECU, like all other software I've ever tried in this car.

I know you are probably right since I am not too big on communication protocols but just to confirm I will order a tactrix clone(how do they handle the internet connection for the initialize phase, they like to "die" with active internet connection).
Also I will try with kw1281 / kwp2000 software/write/modify some code see if I can replicate what is exactly happening why it wont connect even with slow init on 0x01 with kline cable either so..

Would be nice to see how this performs finally.

Why would OP's cable not be capable of doing kw1281 protocol?.....

https://www.blafusel.de/obd/obd2_kw1281.html#5

Is it possible OP have shitty Windows 232 drivers?....I've had that before with various USB-RS232 devices.  Ended up downloading directly from ftdi.

https://ftdichip.com/drivers/vcp-drivers/

Also where's the pop up message that says your cable is incompatible, please purchase one from prj's OBD2 store?  You slacking on the try catch handlers?  . 

Your selective reading ability is amazing.
Chipsoft (original) was only tested on a CAN controller.
If you get no reply from it on K-Line then the K-Line on it is busted, plain and simple.

Your continued idea, that the software is somehow at fault is just stupid.
There are hundreds of users using the free ME7 functionality every day, and none of them are having any problems with it.

Probably because they're not using a china clone of an obscure russian cable with a busted K-Line, and then wondering why a K-Line protocol does not work.
If SLOW-0x01 works in ME7Logger with a KKL and does not work in VehiCAL logger it shows clear as day that your cable does not have a functional K-Line at all.
Doing any further tests is pointless -> get a J2534 interface with a functional K-Line driver or contact Chipsoft support if you actually have an authentic cable. It's their issue to fix, not mine.

I am not going to entertain any more allegations or respond to your insane theories when you are just using hardware that has no functional K-Line to talk to a K-Line ECU.
Maybe next thing is you will try to communicate with the ECU without anything connected to the car or computer at all and then blame the software that it can not talk to the ECU telepathically

https://ecutools.eu/chip-tuning/chipsoft-j2534-pro/
It says support of additional Kline bus on pins 3,8,9,11,12,13,15.  It might help.

I am pretty sure I do not have a clone cable it was bought straight from ECUTools (the exact link above even) , it should be original Chipsoft Russia/Ukraine cable, so yes I could contact them to see whats up with it if there is anything.

If you dont have handson experience with this cable, its a little bit funky - to use it a s K-line only cable it comes with an 'application' which rewrites the firmware to works a k-line serial port without J2534 functionality(ofcourse in this mode it does not work with Vehical at all)
It looks like when you have it in J2534 mode K-line does not seem to work ? Could test it with some j2534 diag software I guess... or even me7logger in this mode, but even if it does(and it prolly does) then its no good for the original issue.

I'll go ahead and test that right now, alteast that will confirm if Kline works or not

But again... on the older software 0x01 never ever worked.. flashing the newer software on 0x00 is now "broken" and 0x01 works as it should on the same exact K-line cable, so the setup is at play aswell here since its not a "normal" setup.

I switched it into Kline adapter mode yesterday and noticed couldnt get an echo even with me7logger, so I thought that cannot be right, checking via device manager it does not install the K-line drivers... ofcourse it does not tell you this.... except in a small part of the manual... because the driver is not signed.

So you gotta disable driver signing to manually install it when its in k-line mode. Did so and tested with Me7logger and voila it works like the oldie cable.
Okay, so we knows it works as a K-line adapter(one of the main functions / selling points of it...lol)


Switching it back to J2534 mode, and giving Vehical a go pretty much end up with same result after messing about for one hour or so, trying all combos and such.

If ignition on and trying to connect on Auto, Auto baud, it will connect with double slow 0x01. But after 2 seconds or so it will throw the error attached below -timeout/no ecu reponse.

Without turning ignition off, and trying on auto connect it will "connect" on fast 0x10 but fails to detect baud rate
So if I then try to connect via fast 0x10 and select baud rate manually it will just say wrong reply, find second attached image below.

This what I've been able to get out from it...

The developer definetly says the cable  is capable of K-line exchange as a J2534 adapter but at the moment it does not seem to be case I need to find/test it with another program with j2534 passthrough to see if it works there on a K-line connection or not I guess to confirm which is the last "unknown" of this cable.

I shouldve gotten the Dialink it looks like... maybe that works better oh well.
Let me know what you think and probably should write something indeed to Denis/Chipsoft so we can use the cable in every application lol.