How to Set up Subaru SSM4 (Subaru Select Monitor IV) software with J2534 Device?
You can make SSM4 work with any J2534 capable device.
SSM4 is compatible with most SAE J2534 interfaces such as Autel Jbox, Snap-On passthru PRO, LAUNCH J-BOX, VXDIAG, Mongoose, Openport 2.0, VAS5054, GM MDI/MDI2, SM Pro2, Cardaq, Nexiq2 original, AVDI etc.
Just replace the DST-i DLL file with your device DLL. (and rename it)
Program Files/DST-i/Drivers/DSTIV32.dll
copy and paste j2534 dll (function library) into Program Files/DST-i/Drivers/DSTIV32.dll
copy original dll name and then rename it xxDSTiV32.dll
then rename your j2534 dll to same name as OEM dll thus tricking the SSM4 into thinking you’re using the SSM4 Device.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\PassThruSupport.04.04\DENSO CORPORATION – DST-i]
“DllVersion”=”02.08”
“ConfigApplication”=”C:\\Program Files\\DST-i\\drivers\\DSTi_ConfigTool.exe”
“Name”=”DST-i”
“FunctionLibrary”=”C:\\Program Files\\DST-i\\drivers\\DSTiDV32.dll”
“Vendor”=”DENSO CORPORATION”
“CAN”=dword:00000001
“ISO14230″=dword:00000001
“ISO9141″=dword:00000001
“ISO15765″=dword:00000001
“APIVersion”=”04.04”
in the line “FunctionLibrary” here is the path to the driver DST-I, you change it to the path to the driver of your PassThru device. I look like this:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\PassThruSupport.04.04\DENSO CORPORATION – DST-i]
“DllVersion”=”02.08”
“ConfigApplication”=”C:\\Program Files\\DST-i\\drivers\\DSTi_ConfigTool.exe”
“Name”=”DST-i”
“FunctionLibrary”=”C:\\WINDOWS\\system32\\tcnptm32.dll”
“Vendor”=”DENSO CORPORATION”
“CAN”=dword:00000001
“ISO14230″=dword:00000001
“ISO9141″=dword:00000001
“ISO15765″=dword:00000001
“APIVersion”=”04.04”
But to work with PassThru will be only SSM IV. Only SSM 4, cars from 2014 of release. SSM3 is only compatible with vxdiag subaru, Denso DST-i or Hitachi HDS3000 interface. For ssm4 you can make any J2534 interface.
Feedback:
1). Just Replace the Program Files/DST-i/Drivers/DSTIV32.dll.
file with the AbrPT32.dll file and rename it DSTiV32.dll and it works perfect.
2).
I have a cardaq and have it working with ssm4.
3). Genuine AVDI works, no problem. Both SSM3 and SSM4. SSM3 works with AVDI no problem. Just run the set passthruSubaru.exe in your Abrites start menu folder and choose SDI in the Interface box menu inside SSM3. There’s no need to edit registry or anything like that.
4). I can confirm that ssm4 works 100% with nexiq 2 (original). Scanning, flashing, everything works. Replaced and renamed the dll and voila!
Here’s the modified dll file for Nexiq2. It’s already been renamed so leave the name unchanged. You copy it and overwrite the original file in :
Windows x86 : C:/Program Files/DST-i/Drivers/
Windows x64 : C:/Program Files(X86)/DST-i/Drivers/
After that, Nexiq2 will show up in the list of multiplexers-make sure you choose Nexiq Usb Link 2 USB and the pass-thru option anytime SSM4 asks you. I highly recommend you ONLY use the USB option and avoid Bluetooth and WIFI , especially when flashing.
ONLY SSM4 WILL WORK WITH IT, SSM3 WILL NOT !!!
You can make SSM4 work with any J2534 capable device.
SSM4 is compatible with most SAE J2534 interfaces such as Autel Jbox, Snap-On passthru PRO, LAUNCH J-BOX, VXDIAG, Mongoose, Openport 2.0, VAS5054, GM MDI/MDI2, SM Pro2, Cardaq, Nexiq2 original, AVDI etc.
Just replace the DST-i DLL file with your device DLL. (and rename it)
Program Files/DST-i/Drivers/DSTIV32.dll
copy and paste j2534 dll (function library) into Program Files/DST-i/Drivers/DSTIV32.dll
copy original dll name and then rename it xxDSTiV32.dll
then rename your j2534 dll to same name as OEM dll thus tricking the SSM4 into thinking you’re using the SSM4 Device.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\PassThruSupport.04.04\DENSO CORPORATION – DST-i]
“DllVersion”=”02.08”
“ConfigApplication”=”C:\\Program Files\\DST-i\\drivers\\DSTi_ConfigTool.exe”
“Name”=”DST-i”
“FunctionLibrary”=”C:\\Program Files\\DST-i\\drivers\\DSTiDV32.dll”
“Vendor”=”DENSO CORPORATION”
“CAN”=dword:00000001
“ISO14230″=dword:00000001
“ISO9141″=dword:00000001
“ISO15765″=dword:00000001
“APIVersion”=”04.04”
in the line “FunctionLibrary” here is the path to the driver DST-I, you change it to the path to the driver of your PassThru device. I look like this:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\PassThruSupport.04.04\DENSO CORPORATION – DST-i]
“DllVersion”=”02.08”
“ConfigApplication”=”C:\\Program Files\\DST-i\\drivers\\DSTi_ConfigTool.exe”
“Name”=”DST-i”
“FunctionLibrary”=”C:\\WINDOWS\\system32\\tcnptm32.dll”
“Vendor”=”DENSO CORPORATION”
“CAN”=dword:00000001
“ISO14230″=dword:00000001
“ISO9141″=dword:00000001
“ISO15765″=dword:00000001
“APIVersion”=”04.04”
But to work with PassThru will be only SSM IV. Only SSM 4, cars from 2014 of release. SSM3 is only compatible with vxdiag subaru, Denso DST-i or Hitachi HDS3000 interface. For ssm4 you can make any J2534 interface.
Feedback:
1). Just Replace the Program Files/DST-i/Drivers/DSTIV32.dll.
file with the AbrPT32.dll file and rename it DSTiV32.dll and it works perfect.
2).
I have a cardaq and have it working with ssm4.
3). Genuine AVDI works, no problem. Both SSM3 and SSM4. SSM3 works with AVDI no problem. Just run the set passthruSubaru.exe in your Abrites start menu folder and choose SDI in the Interface box menu inside SSM3. There’s no need to edit registry or anything like that.
4). I can confirm that ssm4 works 100% with nexiq 2 (original). Scanning, flashing, everything works. Replaced and renamed the dll and voila!
Here’s the modified dll file for Nexiq2. It’s already been renamed so leave the name unchanged. You copy it and overwrite the original file in :
Windows x86 : C:/Program Files/DST-i/Drivers/
Windows x64 : C:/Program Files(X86)/DST-i/Drivers/
After that, Nexiq2 will show up in the list of multiplexers-make sure you choose Nexiq Usb Link 2 USB and the pass-thru option anytime SSM4 asks you. I highly recommend you ONLY use the USB option and avoid Bluetooth and WIFI , especially when flashing.
ONLY SSM4 WILL WORK WITH IT, SSM3 WILL NOT !!!