Would there be a way to log the ACD ECU using the OP 2.0 cable's standalone logging feature?

According to the evoscan datasetting xmls, both use mut2 protocol and obviously they are both loggable through the OBD port.

The only options I know of that can be set in the logcfg.txt configuration file for standalone logging are 'type' (which is set to 'mut2' for ECU logging, so I imagine this would stay the same following my previous hypothesis), and 'setpinvoltage' which allows us to set certain OBD pins to a certain voltage. Is it possible that by applying the correct voltage to certain pins we would trigger ACD logging instead of ECU logging?

Any ideas?

 

Sorry for a slight off topic, but I've never been able to log ACD/AYC with my 2.0 cable at all (only had success with a 1.3U cable). If you have been successful with the 2.0 and Evoscan, I'd really appreciate it if you could share what version of Evoscan you are using.

Thanks

 

Actually I haven't even tried w/ the 2.0 and Evoscan yet. Maybe I should see if that works in the first place before skipping ahead to standalone logging

 

I have never managed to get the OpenPort2 to log ACD controller, there seems to be some incompatibility there somehow.

Maybe it would work if it had its own port, not one shared with efi and ABS.