'Adding' this would be not impossible but really hard. Too hard compared to the gain.
Still no high performance logging with this method, since you can log only 8 variables per
logging request and the ecu has to do the whole data conversion itself, which is quite a lot
of instructions to perform for each log request.

So far I saw these two images with support for readDBLI:
EPK = 40/1/ME7.5/3/4016.31//24E/Dst06o/071002//
- '0261207931'         (SSECUHN)   
- '1037366920'         (SSECUSN)     
- '4B0906018DA '       (VAG part number)
- '0006'               (VAG sw number)     
               
EPK = 40/1/ME7.5/5/4016.32//24E/Dst02o/180902//
- '0261207941'         (SSECUHN)   
- '1037366871'         (SSECUSN)   
- '8E0909518AH '       (VAG part number)
- '0002'               (VAG sw number)   
   
Raising the baud rate could be relatively easy implemented, but the gain would be nearly zero.
The kwp1281 protocol requests echo bytes to be sent by the communication
partner for each transmitted byte, so the "round-trip-time" is limiting. This is mostly
defined by the time slices the ecu uses for processing data, which is 10ms,
the baud rate is not the limiting factor here. Plus you get only four variables per log request.

On the screen where you choose which component to connect to, ie engine, instrument, etc, there is a field at the bottom that allows you to manually enter a component address. Try entering 0x11 in there.

This may allow you to start a KWP2000 session with the ECU, but I doubt you will be able to do anything more at this point.

May I ask how you can tell if an ECU has support for readDBLI by looking at the bin?

Thanks,
Rey

Ah. you're hitting it with requests and monitoring reqponses. I thought maybe you could recognize the code by looking at the raw hex.

Try disconnecting cluster fuse, ECUX doesn't work for me at all unless I disconnect cluster.