MODULE VSM (Vehicle Security Module ) I recently change(used one) this module on my expedition 03 and the forscan software dont detect this module ,but my scaner did detect the module.
can any body cheer there experience and help with this mater of forscan software don't detect this module ?
thanks for any help you can provide .
old module (Reason to change the module ,battery ligth charge problems only, key fob ans door locks works ok )
Junk yard module (Expedition problems : key fob only open the driver side door and the latch window,and do nothing on the rest of the doors )
battery Ligth charge problems resolved .
VSM Vehicle Security module Expedition 03
-
Don Ridley
- Posts: 1562
- Joined: Sun Apr 01, 2018 2:31 am
- Vehicle: 2016 Transit Connect
Re: VSM Vehicle Security module Expedition 03
Are you using a new vehicle profile?
Re: VSM Vehicle Security module Expedition 03
2003 Expedition has VSM on the UBP bus. This is a proprietary old Ford protocol that isn't supported by the OBD and J2534 adapters. The only adapter that supports it and we know about is Ford VCMII. If you use Ford VCMII in J2534 mode, FORScan should be able to recognize this module.
What is the "your scanner" that was able to detect this module ?
What is the "your scanner" that was able to detect this module ?
-
tractmec
- Posts: 2109
- Joined: Thu May 26, 2016 11:43 pm
- Vehicle: F150 5.4 Triton 2005 Fusion 3.0 2010
Re: VSM Vehicle Security module Expedition 03
FORScan wrote: Sun Mar 01, 2026 2:09 am 2003 Expedition has VSM on the UBP bus. This is a proprietary old Ford protocol that isn't supported by the OBD and J2534 adapters. The only adapter that supports it and we know about is Ford VCMII. If you use Ford VCMII in J2534 mode, FORScan should be able to recognize this module.
What is the "your scanner" that was able to detect this module ?
I would also be interested if you would relate the scanner you said that was able to read the UBP network and the VSM? The J2534 companies I enquired about this did not even understand what the UBP network was(Stands For UART Based Protocol)asegura wrote: Sat Feb 28, 2026 4:39 pm MODULE VSM (Vehicle Security Module ) I recently change(used one) this module on my expedition 03 and the forscan software dont detect this module ,but my scaner did detect the module.
can any body cheer there experience and help with this mater of forscan software don't detect this module ?
thanks for any help you can provide .
old module (Reason to change the module ,battery ligth charge problems only, key fob ans door locks works ok )
Junk yard module (Expedition problems : key fob only open the driver side door and the latch window,and do nothing on the rest of the doors )
battery Ligth charge problems resolved .
FORScan did try for several versions to read UBP with the Manual HSMSCAN switch on the Old ELM327 Adapters(no longer recommended by FORScan) with a KLINE protocol but gave it up as a Ford VCM2 Access only( note that UBP access has been removed in the later FORD VCM3)!
I have owned a 2003 Expedition(Eddie Bower Edition) and the only Adapter that would access the UBP network and read the VSM was the Ford VCM2! Also have a 2005 F150 with this network and VSM Module
Forscan will detect and read the UBP network and the VSM over a Ford VCM2 including AsBuilt data and PID reads and has been able to since FORScan Version 2.3.09(I helped to develop the UBP protocol ability read but no firmware/calibration file for module replacement install)
Depending on Expedition trim level there should be several modules(Heated/Cooled seats, Drivers seat, EHVAC, 4X4, Air Suspension etc) on the UBP network!
Does your aforementioned scanner see those too?
UBP does have a Connection to the IPC(Mostly for vehicle information display) but I am not understanding how that would cause a problem with the Battery Charge light as the Alternator and the Charge light are controlled by the PCM over the PWM/SCP network(See Gen _Mon and GEN _ COM Or Generator Monitor and Generator Command in the PCM PID section under the Oscilloscope Icon)!
If your "Scanner" sees this network and able to load the VSM PID's this can be used to trouble shoot the RKE and door lock and door ajar switch functions!
As to the RKE fob malfunction, the question I would ask is did you reprogram all of your RKE fobs to the used VSM using the Ignition 8 Key on off sequence(Surprised any door locks under RKE fobs work at all if you did not do this)?
Also Can you open all the door/lift gate locks using the 5 digit Code Printed on the used VSM label and pressing the 3-4 button(Press Button 5-6 for the lift glass) after the code opens the drivers door with the door key pad!
Do the Lock buttons on the Arm rests work properly with the used VSM?
This test would eliminate the Used VSM internal Lock/Unlock Relays as being the problem if the locks cycle lock and unlock all doors with the key Pad and the Armrest buttons!
That hopefully is helpful?