Well.. That fast baud enable still doesnt work for some reason.. Im not quite sure why. But should be able to set to standard rate of 34800 until I sort that out.
On the plus side, a bit of tinkeringand soldering got the OBD2 cable working. Looks like it uses a elm322, so works on the VPW protocol. Hooked her up to my scantool and.., It worked!
When selecting VY Engine Gen3, it sends back:
[17:08:49:167] Received: 6C 10 F1 20 64
So 6C priority byte, to 10(pcm), from F1(scantool)... so.. what to respond back to that with.. will need to go over those logs taken before.
Ill now set the elm header to 6C F1 10 to pretent to be the pcm and see what happens.
*Edit
Heres our winning frames:
[15:30:52:187] Received: 6C 10 F1 20 64
[15:30:52:187] Received: 6C F1 10 60 72
[15:30:53:653] Received: 6C 10 F1 20 64
[15:30:53:653] Received: 6C F1 10 60 72
[15:30:53:669] Received: 6C 10 F1 10 01 07
[15:30:53:684] Received: 6C F1 10 50 01 84
So need to fire off 6C F1 10 60 72.. must just check if pcm is present.
Tech2 recognises my responses back, but this elm cable is a dinosaur and isnt quick enough to capture data, stop monitoring, fire off frame and begin monitoring again, since tech2 then looks for the next message to receive but the elm misses it and tech2 says communication lost... will need two cables for this
