With ftdi cable using this program will be able to dump bin in mode2. If tac support it.
We need to have a log of pcm-tac communication, Can you wire the modules and intercept the wire that goes to pcm.
With mdi and universal patcher you can monitor aldl in j-console.
You need to set protocol to gm_uart_ps baud=8192 and for pins use 00000900. The aldl is at pin9 on obd2 connector.
using 22.1.0 logger it doesn't appear to have a selection for a J2534 tool? Its just an empty selection box. The protocols and baud rate selections are empty as well.
Gampy wrote:On tab J-Console, if the Device Type drop down list in the group box J-Console is empty, then you do not have a properly installed J2534 VCI ...
UniversalPatcher-Logger_DeviceType.jpg
-Enjoy
thanks I forgot about setting up the MDI on this new laptop. I think I'm rolling now.
just waiting on some J1962 connectors to arrive and I'll make a little breakout harness for the MDI.
kur4o wrote:Do you have mdi manager installed. It will add the registry entries needed for device selection.
It reads registry for all installed j-2534 dlls and should list them no matter they are connected or not.
Or there is some weird bug.
I got everything setup, scrapped some stuff together as I couldn't wait lol.
The logger wasn't really working. Every now and again it would catch some bytes. pin 16 on 12volts and pins 4and5 grounded. pin 9 to either of the two data lines, same results.
This was the logger setup- says err_channel_in_use. Not sure what that means or how to fix it?
There is 2 lines marked as aldl. Not sure if they are separate or tied internally in modules, to reduce the risk of loosing tac control.
Pcm 1mb blue,green pin14 pin 15 blue connector
tac pin12 pin 13 connector tan c1
Can you check if pins are tied internally in modules, if they are tied it is one channel communication and it doesn`t matter where you will intercept.
If they are not tied it could be dual channel communication.