VCM2 not connecting to vehicle

[t0m541]

I have a 2015 Transit Custom.
I have been trying to connect to the vehicle using my VCM2 unit, (I've also tried my ELM unit too)
Forscan see's the two boxes and identifies the and connects to them.
But I keep getting the error "unable to connect to vehicle, please ensure ignition is on"
Which it is, the ODB2 port is supplying power to the VCM2 as the power light illuminates.
I know the ODB2 port is working too as I have an XTool diagnostic tablet which communicates with the vehicle without issue.
I used to use Forscan and Ford IDS with the VCM2 on my older van so I know it works ok, but it seems like this newer version has some kind of firewall against other software than OEM manufacturers stuff.
Incidentally, I trying to program up my spare key.
The XTool does the later smart keys, but not the bladed type.

[tractmec]

I have a 2015 Transit Custom.
I have been trying to connect to the vehicle using my VCM2 unit, (I've also tried my ELM unit too)
Forscan see's the two boxes and identifies the and connects to them.
But I keep getting the error "unable to connect to vehicle, please ensure ignition is on"
Which it is, the ODB2 port is supplying power to the VCM2 as the power light illuminates.
I know the ODB2 port is working too as I have an XTool diagnostic tablet which communicates with the vehicle without issue.
I used to use Forscan and Ford IDS with the VCM2 on my older van so I know it works ok, but it seems like this newer version has some kind of firewall against other software than OEM manufacturers stuff.
Incidentally, I trying to program up my spare key.
The XTool does the later smart keys, but not the bladed type.

I assume you have the Bosch VCI Manager software installed in the Computer and that you can connect to the VCM2 through the VCI interface(Should be a Program called VCI Manager(Ford-VCM-ii) in the Windows start menu under Bosch)!
You have the FORScan connection type set to J2534(Do not auto connect) with FORD-VCM-ii showing in the J2534 adapter window and all other J2534 specific settings set to auto?

Does the VCM2 Power light illuminate when you plug the DLC cable into the vehicle without the VCM2 USB connected to the Computer? The Power light will or should illuminate with either the USB connected or the DLC connected! An easy way to check if you are getting 12 volt+ at pin 16 in the DLC port is to connect the DLC cable first and if the Power light does not illuminate then the reason for no 12 volt+ power at pin 16 will need to be investigated(not sure on 2015 Transit but Pin socket 16 in the DLC connector used to be fused live from the same fuse as the 12Volt DC power Connection)!

ELM327/FTDI based adapters must have 12Volt+ power at DLC Socket 16 in order to operate at all(also do not use auto connect)!

Not being familiar with the Xtool I cannot comment on whether or not it needs 12+ from the DLC connector!

A Far as I understand there is no reason, firewall or otherwise that a VCM2 or an ELM327 adapter on FORScan should not connect to a 2015MY vehicle given proper install and good connections at the DLC connector!

Without more information I cannot comment further!

[t0m541]

Hi, the power light comes on on the VCM when either plugged into the OBD port or the USB.
Forscan sees the VCM as the J2534 Kvaser interface.
I do have the Bosch VCi manager installed.
The connection is set to the J2534 and other settings to auto.
I would have thought that the Elm connection would have worked as the USB adapter is a Forscan one.
Forscan does see either adapter when they're plugged in but says that the vehicle is off, even though there is obviously power for the power light to be on.
The XTool also takes its power from the OBD port if needed.
I'll try running the software again and see if I can select the Bosch VCi adapter.
Ive used this adapter many times on this laptop with the same settings on other vehicles without issue.
Cheers

[tractmec]

Hi, the power light comes on on the VCM when either plugged into the OBD port or the USB.
Forscan sees the VCM as the J2534 Kvaser interface.
I do have the Bosch VCi manager installed.
The connection is set to the J2534 and other settings to auto.
I would have thought that the Elm connection would have worked as the USB adapter is a Forscan one.
Forscan does see either adapter when they're plugged in but says that the vehicle is off, even though there is obviously power for the power light to be on.
The XTool also takes its power from the OBD port if needed.
I'll try running the software again and see if I can select the Bosch VCi adapter.
Ive used this adapter many times on this laptop with the same settings on other vehicles without issue.
Cheers

I see one problem right off! FORScan is connecting to the wrong J2534 interface! I do not know what the Kvaser interface is but the VCM2 should be using the Bosch VCI manager interface! Being as you have an Xtool installed I am suspicious that FORScan is trying to use the Xtool interface instead of the VCI manager! There should be a choice between the two interfaces in the FORScan J2534 connections! If there is only the Kvaser then something is wrong and the VCI manger interface is not being found by FORScan!
If you were to try connecting FORScan to the VCM2 without the VCM being connected by USB, you should see a large rectangle with a VCM2 ICON in the top left corner with a BIG red X over it! If not FORScan is not trying to connect to a VCI interface!

Run the VCI manager from the Bosch folder(with the VCM2 USB Plugged in) in the start menu and make sure you see a VCM2 Icon with the VCM2 Serial Number under it High lighted in Blue under the VCMii Explorer Tab and also make sure that it will Connect(Green Check Mark and the Computer light will blink to signify data transfer) and Disconnect and that the Page button will cause the Speaker in the VCM2 to sound when connected!
If and when it connects go to the Tab marked "VCMii Update" and check what VCI software version and Release date is being reported as compatible! FORScan should work with the latest one from Motorcraft.
Mine uses the one BOSCH still offers from their website as 2.3.85.7!

If none of that works then something is wrong with the RNDIS network that must be installed in the Device manager by Windows(is a windows driver and should appear in the Device Manger Network Adapters list when ever the VCM2 is plugged in and should give you the USB sound connection sound when it is plugged in)!
It should have been plug and play when the VCM2 is first plugged in for the VCM2 to be able to install from the VCI manager installer on first USB connection(that install interface that should have said "do not unplug the USB cable until the Installation completes" and should have been run when you first plugged in the VCM2 USB)!

As Far as your ELM327 adapter is concerned, if it has any FORScan/FORScan Pro Label on it "DITCH IT"(see this Topic: viewtopic.php?f=4&t=17072)! It is cheap clone which I suspect FORScan had to take it's Manufacturer to court in order to recover their trademark when this Bunch basically stole it! FORScan discovered it also was not even using all the Protocols FORScan uses!

FORScan does not make nor does it endorse any Adapter other than the ones they have had some input into their development and those(OBDLink EX and MX+ and vLinker FS and FD) are listed on the FORScan Product page!

Just my advice, Up to you however!

[t0m541]

Hi, thank you for the advice.
I re run the Bosch installer and then plugged in the VCM, just into the laptop not the vehicle.
I ran Forscan and checked connections and the VCM appeared in the drop down menu, so I selected it.
I then tried it on the vehicle tonight and it connected straight away.
I now have to relearn how to use Forscan, it's been at least 5 years since I last had to use it to program up a vehicle and I've played with a lot of other diagnostic software since then, hence the Kvaser interface.
I do have a question regarding Forscan.
I'm trying to program up a new key as the vehicle only has one.
I've had a look through the menu and into the programming tab, saved all the configurations to computer.
Where would I find the key programming section, I was thinking it would be under the BCM tab, but don't want to be tinkering about.
I did that once with the BCM and accidentally put the vehicle into error mode as it was looking for passenger seat airbags it didn't have.
It took a new BCM to fix that gaffe.