Showing posts with label vcm2. Show all posts
Showing posts with label vcm2. Show all posts
Saturday, March 4, 2017
How to get Nissan Consult III Plus work with Ford VCM2
How to get Nissan Consult III Plus work with Ford VCM2
Have got the alliance vi to work with Consult3 plus software. And make Consult III+ to run it with Ford VCM II interface.
CarDaq
Actica Passthru+ XS
Python1B
Nissan USB Diag
Alliance VI
And The obvious tool VI2
Actica Passthru+ XS
Python1B
Nissan USB Diag
Alliance VI
And The obvious tool VI2
all these are the best to work with Consult 3 plus.
others will also work but maybe not as well.
The Ignition ON its not seen if you use VCM II
I use AVDI and Ignition ON it is not seen too
I read that no matter what j2534 tool you use the Ignition ON its not seen
Probably, only if use Alliance VI2, but alliance vi is quite a bit more complicated to set up
I use AVDI and Ignition ON it is not seen too
I read that no matter what j2534 tool you use the Ignition ON its not seen
Probably, only if use Alliance VI2, but alliance vi is quite a bit more complicated to set up
Here is thesetup of VCM II with Nissan Consult 3+.
For ford VCMII
In the Diagnostictool.ini put Ford-VCM-II
Install the consult 3 plus
Install your VCMII Manager and drivers.
In passthru 4.04 in reg edit and rename NISSAN_VI2 To something else
change name Bosch Ford-VCM-II to NISSAN_VI2
Reboot computer and test it
In the Diagnostictool.ini put Ford-VCM-II
Install the consult 3 plus
Install your VCMII Manager and drivers.
In passthru 4.04 in reg edit and rename NISSAN_VI2 To something else
change name Bosch Ford-VCM-II to NISSAN_VI2
Reboot computer and test it
I tested it once with limited success.
Attachment: [Diagnostictool.ini]
https://mega.nz/#!5kMm2TwI!1m7PLJEx_DM_ll3a1UBWuG4ZviRlSyH80iKvJN0-BLk
Note 1: [alliance vi]
The sonde alliance vi is the end for the sonde can clip RTL. remplaced by sonde alliance vi but what is it.
Renault Aliance VCI = 100% Same with Nissan Consult III VCI...
Just & ONLY different name...
Just & ONLY different name...
Note 2: [workable sw]Clone Consult III (who using patch) for to working with Nissan Consult III S/W, DID NOT working with Clip Software!!!
It seems now Clip S/W needs NEW "Pill" for Clones..
Original:How to get Nissan Consult III Plus work with Ford VCM2?
Available link for download
Sunday, January 22, 2017
How to get JLR SDD to work with Ford IDS in a VCM2 clone
How to get JLR SDD to work with Ford IDS in a VCM2 clone
JLR SDD v142 and Ford IDS v100 can work no issues in one VCM2 china clone, if you pay attention to the synchronization of sw and fw.
That is, the software of Ford and JLR (Jaguar & Land Rover) has the corresponding VCM2 firmware versions. Software and firmware should be in sync. For example, IDS V86 is compatible with vcm fw: A, and SDD v135 also with vcm fw: A. But if you install IDS v98 for use, then the vcm firmware version would turn B, but the corresponding vcm firmware version remains A, as for SDD v135. The firmware version of IDS and SDD is different. When you convert IDS to SDD, or SDD to IDS, the system would pop up info as below like VCMII software update... To ask you to match the firmware with the software.





So for sake of compatibility, to update software.
For vcm2 units, Ford ids v86 had better work with JLR sdd v135,
ids v98 with sdd v140,
vcm2 ids v100 with sdd v142,
For the vcm unit, its not allow to update. Its a must.
vcm ids v86 with sdd v136.
Original - from diyobd2.fr obd2 francais:How to get JLR SDD to work with Ford IDS in a VCM2 clone
Available link for download
Subscribe to:
Posts (Atom)