GT350 FORScan Tweaks

[mattlqx]

Just wondering if any one else found DTCs when they connected through Forscan?
I had DTCs in three of the modules...
Where is the best place to find info on DTCs on the web? When I search the web, seems like all that's online start with a P, forscan gave me one C, two Bs and two Us. (Apologies if this has already been posted)

P codes are mostly generic OBDII trouble codes. The DTCs are error codes from their respective CAN modules that are very specific.

The DTCs should be very well detailed by themselves if you click on them. You shouldn't need to look anything up. For example, when I hit some DTCs on my F-250, it said exactly what was wrong and places to look for fix like "Ignition Key Sensor Fault, Check for ground short between X and Y."

Sponsored

 

[NightmareMoon]

I keep getting ELM connection error, I tried changing the ports, auto connection, Bluetooth connections etc... anyone else have some hints on getting Forscan to connect? I looked on there forums but haven't found anything that works yet.

1) You want everything on auto.
2) try the PC software that comes with the ODBLink MX and see if that works (it should)
3) even if it works with the ODBLink app try this: forget the bluetooth device from windows, shut down all apps, and re-parent thr device to windows (push the physical button on the ODBLink and add it in windows, then start FORScan and let it autodetect.

After struggling with the ELM connection problem for an hour last night, it was a forget/reparent that seemed to get it working. Good luck!

 

[Tank]

P codes are mostly generic OBDII trouble codes. The DTCs are error codes from their respective CAN modules that are very specific.

The DTCs should be very well detailed by themselves if you click on them. You shouldn't need to look anything up. For example, when I hit some DTCs on my F-250, it said exactly what was wrong and places to look for fix like "Ignition Key Sensor Fault, Check for ground short between X and Y."

Thanks for the info Matt! I'll do some more digging...

 

[Madlock]

I was thinking some sort of conversion might be needed...Thanks [MENTION=8071]Madlock[/MENTION]

Just thought I'd see how any lurking social justice warriors may be biting today. ;)

 

[bdub85]

Has anyone found a way to keep the exhaust valves open all the time?

 

[live2ride90]

1) You want everything on auto.
2) try the PC software that comes with the ODBLink MX and see if that works (it should)
3) even if it works with the ODBLink app try this: forget the bluetooth device from windows, shut down all apps, and re-parent thr device to windows (push the physical button on the ODBLink and add it in windows, then start FORScan and let it autodetect.

After struggling with the ELM connection problem for an hour last night, it was a forget/reparent that seemed to get it working. Good luck!

Thanks man, I will try this again. There was no software that came with ODBlink, just the android app to download which doesn't help if you are trying to use it on a windows laptop. I got the MX B/T adapter that was mentioned earlier in the thread.

 

[NightmareMoon]

You can download PC software online for it if you do a little searching. That step is really just to isolate the issue to FORScan or the B/T adapter. Probably re-pairing it should get you running. Feel free to PM me if you're still having problems.

 

[VNMSNK]

Great thread and very easy to utilize. Kudos to all the trailblazers here. The F150 forum is very educational to get you started and make sure you start out by saving all of your original configurations. You only need the OBDlink software to intially pair it to your PC. Once paired, connecting to Forscan is simple.

 

[dotJake]

I also turned off the seatbelt chime because that got on my nerves too. I always have my seatbelt on but I have a (bad) habit of taking it off once I get into my neighborhood. It's nice to keep everything silent now.

[MENTION=17837]raiderjatt02[/MENTION] where did you find the info for this? Not seeing it on any Mustang sheets. Thanks.

 

[NipSC4328]

@raiderjatt02 where did you find the info for this? Not seeing it on any Mustang sheets. Thanks.

The owners manual has directions for turning off the seat belt chime, doesn't take any OBD tools or software.

 

[dotJake]

The owners manual has directions for turning off the seat belt chime, doesn't take any OBD tools or software.

Oh. That. I should probably read it :doh:

 

[NipSC4328]

Oh. That. I should probably read it :doh:

Lol, I wouldn't have known it either if I hadn't done it on my '14 F150 Platinum, same procedure.

 

[raiderjatt02]

[MENTION=17837]raiderjatt02[/MENTION] where did you find the info for this? Not seeing it on any Mustang sheets. Thanks.

It was in the first post in this thread by [MENTION=19066]Epiphany[/MENTION]

The owners manual has directions for turning off the seat belt chime, doesn't take any OBD tools or software.

Wait, seriously? That might have been easier but it's not as fun!

 

[Madlock]

I was thinking some sort of conversion might be needed...Thanks [MENTION=8071]Madlock[/MENTION]

Not everybody was going to get that one. ;)

 

[fionic]

[MENTION=17837]raiderjatt02[/MENTION] where did you find the info for this? Not seeing it on any Mustang sheets. Thanks.

Wait, seriously? That might have been easier but it's not as fun!

btw, this can still be done in forscan if you wanted.

use the RCM module configuration (the non-asbuilt one), and you should see the beltminder driver/passenger in the list of things you can enable/disable. see my shitty attached image. (not mine, but I added the arrow)

Sponsored