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

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.
 

works great . had a bit of trouble communicating with windows 10 but manage to get it working

Hi, I bought VXDIAG VCX NANO from you last week and I received it, thanks.
I also want to buy the software of ford and mazda, if I buy the laptop together, can you preinstall for me? For I am not so good at it.
Thanks in advance.

is any of the sp239 internet updatable and internet upgradable through the original ford IDS software?

can it be updated through the original ford ids software?

is the sp239 internet updatable and upgradable?

how about item sp239-b, does it do everything the original vcm2 can do?

Does it operate and function just like the ford original vcm2?