Support of J2534 (Pass-Thru) adapters in FORScan v2.2.*

[obd.tech]

I can confirm that GM MDI version 1 works fine with Forscan Software.
Really fast to scan through the modules.
Thanks to the software creators

[lateonthebrakes]

This was asked in this thread before but no one replied to him, so I'll also ask if anyone has tested the VCI-Mini J2534 for Toyota
with Forscan.
Dirt cheap on Ebay
https://www.ebay.com/itm/MINI-VCI-Inter ... 1438.l2649

I would love to know the answer to this as well. I use it for TechStream on my LX 470 with no issues. FORScan doesn't seem to recognize the cable or my F-150 though.

[JimCar]

J2534 Adapter with potentian diagnostic usage.
I state my experiance with J2534 adapter ScanDoc from quantexlab.com
I tried to coding with "as build data" an used ABS unit. Ford Maverick year 2005
This adapter made it Successfully, but I mention that has also diagnostic usage DTC, Reset Unit, Data list etc.
I go to investigate further this adapter.

[Rick81]

Hi all isn't tactrix cable a j2534 pass through?

[Natev24]

Using a Mongoose Plus Ford 2 connected with USB. Forscan will connect but gives errors for all modules DTC. Can edit as built and other items but cannot see DTC. Using the adapters J2354 toolbox or the Roush RDT application pulls the DTCs up just fine, although I have none. I just used this adapter to load the new Roush calibration to my 2021 Mustang Phase 2. When I use Forscan with my obdmx+ everything works fine. I checked settings and the adapter was selected correctly but everything was set to auto not sure if this is a baudrate issue. I can provide files and details if requested. I have not tried letting it auto detect the vehicle and am using a generic 2020 mustang load since the Roush load is not recognized. I am on the latest non-beta version.

[GH057R103R]

Hi all isn't tactrix cable a j2534 pass through?

yes it is, but it doesn't connect to MS-CAN network...

[travis199]

Hi guys, was anybody able to scan all the modules with the nexiq? I can't scan for example IPC module and I am not sure if I do something wrong or the nexiq just is not able to do it?

Thanks!

[KrstGor]

Using a Mongoose Plus Ford 2 connected with USB. Forscan will connect but gives errors for all modules DTC. Can edit as built and other items but cannot see DTC. Using the adapters J2354 toolbox or the Roush RDT application pulls the DTCs up just fine, although I have none. I just used this adapter to load the new Roush calibration to my 2021 Mustang Phase 2. When I use Forscan with my obdmx+ everything works fine. I checked settings and the adapter was selected correctly but everything was set to auto not sure if this is a baudrate issue. I can provide files and details if requested. I have not tried letting it auto detect the vehicle and am using a generic 2020 mustang load since the Roush load is not recognized. I am on the latest non-beta version.

How about this:

Delete any stored vehicle profiles in Forscan.

Make sure you have the latest drivers for the Mongoose installed.

Reconnect to vehicle, select J2534, leave the rest on "auto".

Let me know if it helps!

[jSONBB]

nonContinuousModeDetailedReport_2002__Ford__Escape__GLOBAL_OBDII__01052023152506.pdf

(38.41 KiB) Downloaded 673 times

Report of non Continuous DTCs as reported by the Mitchell MD-350. FORScan does not know what multiples of these tests are - gives incorrect data output. I will update this with the list of DTCs from FORScan later today for comparison.

[Ecmbuster]

nonContinuousModeDetailedReport_2002__Ford__Escape__GLOBAL_OBDII__01052023152506.pdf
Report of non Continuous DTCs as reported by the Mitchell MD-350. FORScan does not know what multiples of these tests are - gives incorrect data output. I will update this with the list of DTCs from FORScan later today for comparison.

This is how MODE 6 is identified with FORScan with a J2534-2 device and Bluetooth adapter.
You are incorrect trying to operate that tool, all it did is generate a report from itself, NOT FORScan!

Misfire mode6.jpg (227.98 KiB) Viewed 15648 times