I connected k line to Alfa 159 (2009) jtdm 1.9 16V.
There is no connection to my Alfa.
I used serial monitor (software found online) to sniff packets between multiecuscan (on my Personal Computer) and Alfa.
This is the recorded messages, that I successfully decoded with the protocol found at http://read.pudn.com/downloads118/ebook/500929/14230-2.pdf and http://read.pudn.com/downloads118/ebook/500929/14230-3.pdf
Push CONNECT button on multiecuscan
PC>ALFA StartCommunicationRequest: 81 10 f1 81 03
PC>ALFA StartCommunicationRequest: 81 10 f1 81 03
ALFA>PC StartCommunicationPositiveResponse: c3 f1 90 c1 ef cf c3
PC>ALFA AccessTimingParameterRequest: 82 10 f1 83 01 07 (set parameters to default values)
ALFA>PC AccessTimingParameterPositiveResponse:c2 f1 90 c3 81 87
PC>ALFA AccessTimingParameterRequest: 82 10 f1 83 02 08 (read active timing parameters)
ALFA>PC AccessTimingParameterPositiveResponse:c7 f1 90 c3 82 b2 82 ae 94 8a 8d (p2min=178 p2max=130 p3min=174 p3max=148 p4min=138)
PC>ALFA ReadEcuIdentification Request: 82 10 f1 1a 97 34
PC>ALFA ReadEcuIdentification Request: 82 10 f1 1a 97 34
PC>ALFA ReadEcuIdentification Request: 82 10 f1 1a 91 2e
PC>ALFA ReadEcuIdentification Request: 82 10 f1 1a 91 2e
PC>ALFA ReadEcuIdentification Request: 82 10 f1 1a 92 2f
No answer from alfa. The multiecuscan seems to restart the communication now, performing these requests:
PC>ALFA StartCommunicationRequest: 81 10 f1 81 03 .
PC>ALFA StartCommunicationRequest: 81 10 f1 81 03
No answer from alfa, then multiecuscan closes the serial port.
Could it be a timing problem? Once received timing parameters
(AccessTimingParameter Positive Response) messages sent by Personal Computer does not obtain answer from Alfa.
Note: each byte sent by multiecuscan on the serial line, returns back to multiecuscan, probably due to the interface board circuit. I suspect this is normal since multiecuscan seems to communicate with Alfa, even if partially. I didn't reported echoed bytes here, since they are pretty unuseful.