VXDIAG VCX SE or OBDLink for Forscan Ford

Which is a better wireless VCI for Forscan? Check user review below.

 

“I tried this VCI (vxdiag vcx se pro) on different cars and different Software and I think it is one of the fastest with the Wireless function.
VXDIAG is the fastest wireless VCI used with Forscan, one of the best scanners for Ford cars.

I am very happy with this one. It is true wireless. I don’t use the USB cable and and it’s amazing fast.

I might compare with OBDLink with this one.  VCX SE is much quicker and more stable.

If you use the USB it is much faster but I prefer to use wireless if it is possible.

Let’s switch on your notification.
Before you start the diagnostic you should go over here on Settings and you have your connection.

You will select over here, your diagnostic VCI, in this car it’s this one-VXDIAG.

Let’s try to communicate with this car (i.e Ford Transit 2010). If it runs to USB cable, it is at least two-three times faster wireless connection. But also on wireless connection is very good.

This is an old car so has not so many modules.

 

I bought the Ford license from this one then I can do more in the future more experiments.

I recommend you use this one if you have it with the forscan software. vxdiag vcx se j2534 is very stable than OBDlink.

OBDlink does not disappoint me I use it for Renault link, it is very good for Forscan I use it also but with the older version.

And now with this version I have it only this one is started here because on these windows I have only Ford programs.

I do recommend using this version 2.3.50 with Forscan.

VXDIAG and Forscan 2.4.6 Update Ford Escape 2012 PCM

Just a quick note to advise that I was able to update the PCM calibration on MY2012 Ford Escape under Forscan 2.4.6 Beta using a recently purchased VXDIAG VCX Nano Ford configured as a J2534 pass thru device. While the ECU calibration update process was relatively smooth within Forscan, the more challenging process was to configure the VCX Nano to act as a J2534 pass-thru device.

 

The key, as noted elsewhere on the net, is to ONLY use the VXManager package to configure the VCX Nano as a J2534 pass-through device; and not use the AllScanner version of IDS at all. VX Manager can also be used to update the firmware on the VCX Nano in case a newer version is available. Once I had configured the VCX Nano as a J2534 pass-thru device within VXManager, it was straight-forward within Forscan to select the VCX Nano as the adapter/device to be used while updating the PCM calibration. Of note is that I connected my 2amp battery maintainer to the MY12 Ford Escape to ensure consistent voltage throughout my use of Forscan 2.4.6 Beta to perform the PCM update.

 

You can also use the vcx nano without having to run VX Manager (i.e. Use VCX Nano straight out of the box with Forscan). Can even leave adaptor choice on auto and it finds it.

 

I further updated the PCM from BRG to BRJ today using Ford FJDS with VCX Nano connected to MY12 Escape. I am assuming that the absence of similar option within Forscan to update the PCM from BRG to BRJ is simply the result of the development cycle for Forscan Beta. Below is configuration of the PCM on my MY12 Escape as things stand today:

 

PCM – Powertrain Control Module

Part number: AL8A-12A650-BRE

Calibration level: AL8A-12A650-BRE

Strategy : AL8A-14C204-BRJ

Hardware type: BL8A-12B684-BB

Ford F150 DRL Coding by VXDIAG and Forscan

The other day I messed around with Forscan on the F150 for the first time in a while, and it went well, so I got excited and started coding my own car.

I drove about 1,600km in America last year, and quite a few cars had DRL on.
I wasn’t really interested in it until now, but I thought I’d try something a little more American.

I connected VXDIAG VCX NANO Ford interface.

Forscan updated to the 2.3.31 when I was busy with coding last time, there were almost no menus, and I accessed and changed the address by myself, calculated the checksum, and entered it, but now, as you can see, there are as many items as you can see. You may not need to access the address anymore!!

I referred to various articles. This is the Dedicated DRL setting ON state.  the high beam is dimmed.

This is the high beam setting. I think it’s definitely brighter. I think the high beam setting is cool, but I don’t want the reflector to burn or get dull if I leave it on without halogen, so I decided not to.

blinker setting. This is very cool!! The turn signals attached to the door mirrors do not light up, only the front lights up. In this state, when the blinker was issued, it flashed, and the other side remained lit. I wish the other side would disappear. There were A and B in the item “DRL conditions”, but there was no change even if I changed it.

I ended up setting it to fog lights.

I changed it from the menu, but the address has been changed properly (naturally).

The lights in the pit would turn on the auto lights, so I used a fluorescent light for the sensor of the auto lights. By the way, if it was an LED work light, no matter how much I applied it, it was useless.

 www.vxdiagshop.com

Correct Mustang Speedmeter with VXDIAG & Forscan

Tutorial: How to correct Ford Mustang Speedmeter (if your car is just off from the factory or you’ve changed tire sizes) with Forscan and VXDIAG J2534 passthru.

 

What’s required:

A laptop running Windows

Free Forscan software with a free extended license

OBD scanner that works with Forscan ((VXDIAG VCX NANO Ford, VCX SE pro or other J2534 passthru))

How does it work?

For 2015-2019 Mustangs, Ford programs the tire size of the car on BCM line 726-12-01 in the second four-digit block of hex. For 2020+ Mustangs, it’s split between 726-15-01 and 726-15-02 as described below. It’s stored as the nominal circumference of the driven wheel in millimeters with a revs/mile conversion factor of 96.7%. To save you the trouble of doing a bunch of math and conversions between decimal and hexadecimal, I’ve come up with a hex calculator that you can use here: click here

This is covered in the spreadsheet, but for example my 2017 GT PP currently has this in the BCM as-built:

726-12-01 xxxx 0858 xxxx

If I changed my rear tires to 305/35R19’s, my calculated value is this:

726-12-01 xxxx 0843 xxxx

The x’s mean to leave whatever value is already there.

2015-2019 Mustangs share the 726-12-01 address. For 2020+ Mustangs, the location has changed to this:

726-15-01 xxxx xxxx ABxx
726-15-02 CDxx xxxx xxxx

ABCD = your calculated value. It’s split between the two addresses for 2020+ cars.

You also have two options here. You can simply enter the size of your current rear tires as in my example above, and using the nominal diameter of that tire size the calculator will give you a hex value you can program to get pretty close (maybe even dead on) with the speedometer. Tire manufacturers vary of course, and your car’s speedometer may be a little weird. So below the tire size calculator is a truing calculator that relies on a precise measurement from GPS.

As stated in the calculator, I recommend that you use a GPS that can output in tenths of a mile per hour, that you set the cruise on level ground as high as reasonable (eg 75mph) and that you use the needle rather than the digital speedo or digital cruise setting to set your speed, since the digital outputs are rounded to the nearest whole MPH. That is to say, you might see that the car is set to 75mph, but internally the car could be set to 74.5 or 75.4, and you’d never know because it’s rounded before it’s shown to you. Here is an example screen showing tenths of a MPH from a Garmin on the satellite info page (press and hold on the satellite reception strength bars in the upper left corner to get to this page.)

Try to set the needle exactly on one of the MPH hash marks on your speedometer for best results. Move your head to the right to eliminate parallax error at that speed, see the below video.

FWIW, if you have other Ford vehicles this seems to work on them as well. I’ve personally confirmed that it works on F150s so if you’ve got a giant bro-dozer with 35″ tires, it’s time to fix that speedometer!

I have a DTC now.

You WILL get a non-MIL DTC P160A (Control Module Vehicle Options Reconfiguration Error) when you change this in the PCM.

Thanks to the FORScan devs and some beta testing adventurers, we are able to reliably remove this DTC now using a new feature.

This new feature is only available in FORScan 2.3.11 or higher.

What you want to do is go into the computer-chip-looking tab in FORScan where you normally edit as-built. At the top, you’ll see a new function for the PCM – “Module initialization/relearn vehicle data” – see this screen shot:

Highlight that function and hit the play button, and follow the onscreen instructions to the letter.

Once it’s finished, rescan for DTC’s and remove the P160A DTC. Go drive around and scan for DTC’s again. You should be in the clear.

Note that if you ever wish to return to stock, you’ll have to run this procedure again after setting the as-built values for the tire size back to stock.

What should I do if I haven’t changed my tires but my speedometer doesn’t match my cruise setting? The speedo reads fast!

I feel this needs to be addressed, because people don’t seem to believe it.

There is a *large* amount of parallax error in these cars when the needle is pointed up, which it is when you’re at highway speeds of around 70-80. At those speeds your speedometer will appear to read 2-3mph faster than your cruise setting.

Why? The needle is thick and spaced out from the gauge face, so the perceived “needle” (the illuminated red center section) will give a great deal of parallax error unless you’re viewing perfectly perpendicular to the needle.

Unfortunately, the designers chose to put the speedometer in such a position that reading the speedo with your head perfectly perpendicular to the needle means moving your head WAY right, far away from any natural position in the car.

www.vxdiagshop.com

Will VXDIAG VCX NANO do Old Ford UBP Protocol?

Question: 

I have a 2003 Ford Expedition, and UBP refers to the communication protocol.   OBDLink MX Bluetooth and Forscan have had very few troubles connecting to several vehicles from early models to more recent MS-CAN equipped models. I wonder if the vxdiag vcx nano ford ids is able to access old Fords with UBP.

 

 

Answer:

Most other vehicles use CAN, but these older Fords use UBP to communicate with the PCM. Most devices available cannot communicate with UBP.

Obdlink does not support UBP. VXDIAG VCX NANO does not do old UBP Ford either.

Forscan has UBP support as of version 2.3.09 but only for Ford VCM2 Adapters and VCM2 Clones.

Support for UBP protocols in ELM327 based adapters is still being worked on hence the prompt for the switch change if ISO/UBP is expected on the board but to date reading UBP with ELM327 adapters has not been successful!

You need a UBP compatible scan tool. One of the few scan tools with UBP support is Ford VCM II.

Forscan Disable 2021 F150 Auto Start Stop Function

2021 Ford F-150 Auto Start Stop can now be disabled via FORScan. You will need a Forscan compatible J2534 interface, i.e the vxdiag vcx nano ford interface.

 

The following has been reported to disable Auto Start/Stop:
PSCM 730-03-01 xxxx xxxx 00–

If you keep the Stop Start status monitor open in the IPC (found in the Trip Fuel menu) you can monitor that every time auto stop start should kick in it will not due to a ‘steering maneuver in progress’, which is an auto stop start interrupt generated by setting this.

 

The person that first tested this newer mod (Airborne_Ape) said “In the tests this generates no errors, no DTC’s, no prompts, no chimes and keeps the battery monitor system active. The Auto Start Stop algorithm is just always interrupted by the PCSM and will never work.”

Can confirm: This is the only notification that I get, and it is only visible if you are already looking at this screen.

No errors, no warnings, no side effects (so far).

By changing that “1” to a “0” you’re basically just tricking the Power Steering Control Module into thinking that the steering wheel is currently in motion, and therefore A.S.S. is not activated.

Since this is a normal action that it looks for each time you stop it wouldn’t generate any kind of error, therefore, no error or warning messages.

Mission accomplished.

https://www.vxdiagshop.com/wholesale/vxdiag-vcx-nano-for-ford-mazda-2-in-1.html