That's just it (with Forscan)
Time is money
We used to just swap a known good master switch into the harness and see if it then worked
Time was money for us too at the dealer
I bought a few parts like a MAP sensor for my toolbox and had a few wiper motors kicking around and master switches etc..

 

Just shows you have used it RLXXI
That is not a bad price, but I am still wondering if I can afford a R1234yf recycler
Someday maybe

 

Oh yeah, that little scan tool made me a lot of coin back in the day, easily paid for itself. The VCMII on the other hand was what I considered at the time I bought my truck back in 2013, an accessory to it. Made a little coin with it but got it for personal use mainly.

 

It sure is nice having what you need
I had to pay the dealer I used to work at 240 to program 3 keys, on a F150 that someone had turned off the key programming, using the WDS or newer cards than mine
I couldn't do it
I was not going to mess with forscan, and still don't myself, even if I could have saved the 240
I was selling the truck anyway and just added the 240 to my selling price

 

It'll read all the same pids. They just may not be called exactly the same thing. Poke around in the menu to see if something looks close.

Forscan is IDS reverse engineered.

 

Yeah I can translate the PIDs well enough, but I as far as I can tell forscan can't "trigger the GEM active command delayed accessory to on" or trigger the OTD on and off.

 

Yeah it's there, you have to select the pids then trigger it with play arrow bottom left of screen.

 

Hmm okay, I'll take another look.

 

If you can't find it, check the forscan forum. Oh and it only works in the Windows version. Not the app.

 

Yeah I'm using the windows version. Under "configuration and programming" there's 2 configurables for the GEM but they have nothing to do with toggling relay status.

EDIT: I think I found it, it looks like it's in the logging section but there's a small drop-down to change the mode from Read to Control

 

Alright, this is kind of weird but maybe kind of promising. Using this "control" function, I don't really know what I'm doing, but I can get some behavior out of it.

Here's the choices I have for control, and you can see the ones I've selected.


Here's the PIDs I'm monitoring. The pinpoint test says to monitor D_PWRLY which I'm reading as "delay power relay" and I believe this is ACCDLY "accessory delay relay circuit" in Forscan.


Here is the PID status key on, without doing any Control


Status of Control screen, before doing anything.


So description of what happens next. The driver's door is open and the dome light is on. If I touch anything at all in control I hear a click and the dome light shuts off - this is just an FYI as maybe it's meaningful, maybe not.
The pinpoint test says to turn Delay Relay ON, then Toggle OTD between ON and OFF but then asks if the Delay Relay value agrees with the mode. As I toggle the OTD ON and OFF, the ACCDLY will switch between ON and OFF-FAIL. I don't think the FAIL is literal in this context and it's just off, but maybe someone knows better. The pintpoint test does mention that it could go to OFFO-G which I'm assuming means "off open ground" Perhaps that's what off-fail is in forscan?




Also, when switching OTD ON, the LF_PW_RLY will also go on for a few seconds, then go back to OFF-FAIL. Don't know if this is meaningful.



To be continued in next post...

 

Deviating from the test script here and playing around, here's the maybe weird behavior or maybe not. If I control on the battery saver relay, and then control on the OTD relay, the window will roll down, and I can start and stop it by controlling the OTD relay on and off. The "control" of the ACCDLY relay is irrelevant, however whenever the OTD relay is controlled ON the PID for ACCDLY will also turn ON along with LF_PW_RLY.

So, if ACCDLY Control is ON, then ACCDLY is ON. But, if OTD relay is ON then *both* ACCDLY and LF_PW_RLY go ON.

 

Ok then if you would agree the values are equal here's the next test steps. Wish I could be more exacting with the info but I was trained with NGS, WDS, IDS via Ford schools. Forscan was made in Russia, I can only guess like anyone else how to interpret their parallels. That's where their forum might be of use to you, learn the nuances etc...never really gave it a hard look. I use IDS.

 

Does this apply to 2015 F250, (Single Power window inoperative LH) driver side just quit working? All three other windows work fine. Installed new switch same thing, wires between door and dash are OK no breaks. No power to motor. I have a new regulator and motor to install but not sure I need it since no power.... thoughts?

 

No
Above thread is for a 1999 and your 2015 wiring diagram and troubleshooting flow chart will be different
But you should be able to figure it out
Just to clarify you peeled back the boot to the drivers door and see no broken wires?
You pulled the drivers door panel and tested the wires to the switch and motor for power?
If power, can you manually make the window go up and down with test leads?,
If not, it needs a motor
Good luck