rliles1

Why do you press LOCK twice? It locks everything on the first press. The purpose of the second press is precisely to honk the horn so your wife can find the truck after forgetting where she parked it.

jsdecorte

anyone know the min recommended pc specs to run forscan? looking to grab a cheap laptop/netbook and cant find what i need to run it effectively.

Livnitup

FORScan will run on anything from Windows XP - Windows 10
Here's a cheap tablet that will run FORScan:
Here's some cheap laptops: https://www.newegg.com/Product/Produ...Range=75%20125

Keep in mind that if you want to run a Bluetooth adapter with the cheap laptops above you'll need a USB Bluetooth adapter if it doesn't come with Bluetooth, otherwise you can get a USB adapter to use with FORScan.

Max91

I think a lot of owners that want this option have installed an aftermarket remote start that requires 4 (lock) presses on the fob. And some like me might hit it a couple of times just for peace of mind.

mkraffert

I just converted my front turn signal bulbs to switchback LEDs. When I exit the truck the parking lights lights come on and they flicker. I set 726-50-01 to 40BE. The sheet says: DRL - Low Beams and Dedicated DRL (this may get rid of flickering for LED conversions). Am I missing something? I turned off the hyperflash and that works fine. I think it's turning on the turns and the parking lights when I open the door to get out of the truck, but I don't know how to disable the turn part of it.

Thanks.

Cobra Gt

I am having an issue getting FORscan to connect. I paired the ODBLink MX BT device successfully, in fact i have done it several times. (Laptop, Win 7 Pro, built in BT adapter). I even tried with the ODBwiz software and it could not connect. It was looking on Com ports, which my laptop has none, which might be the issue. I have checked the Windows Updates, there were no important updates but a few optional, which I installed. Any ideas?

carrierj

If you have a stock halogen truck with LED switchbacks want your low beams and the white parks as DRL:
726-45-01 xxxx 7Fxx xxxx
726-50-01 02xx
726-26-02 x1xx xxxx xxxx

White parks only as DRL:
726-50-01 10xx
726-26-02 x1xx xxxx xxxx

Livnitup

You can't run ODBwiz & FORScan at the same time so close down ODBwiz when trying to connect in FORScan. Are you using the newest FORScan here? http://forscan.org/download/FORScanSetup2.3.12.beta.exe

In FORScan settings, connection tab, set Connection Type to Auto or Bluetooth

It should show the OBDlink MX under Bluetooth adapters like the pic below:

Cobra Gt

I was not trying to connect at the same time. I only installed ODBwiz when FORScan could not connect.

It is set to bluetooth, it is even looking at the correct unique identifier, as depicted in my screen shot above.

Livnitup

Try connecting in this exact order:
1. With truck shut off completely (and accessory timeout period expired), insert the MXBT into the truck and turn on truck (engine off)
2. Then launch FORScan and press connect
3. If that doesn't work, reboot laptop and then do steps 1 & 2 again.
4. If that still doesn't work, try a different laptop to rule out laptop #1

Sometimes I get the ELM not found message but this method works when that happens to me. Also make sure you're not using FORScan version 2.3.11 because they've found bugs in that version.