Ford Focus ST Forum banner
201 - 220 of 2,075 Posts
Discussion starter · #201 ·
Just got global open/close enabled. Thanks guys! I'm having some weird issues with my elm though. Couldn't get forscan to read after connection and a few times focccus failed to stay connected after I read the BCM. I tried a few times and eventually got it.
I do not like reading from the bcm for whatever reason it will not load all the data like it should. Where as if you load your asbuilt file instead, all the blocks fill, now change the global open box to what you want and click write to bcm, now no problems. Also, you should open Forscan and clear the now 30ish dtc's you have.

Sent via Tapatalk using Galaxy Note 2
 
Yeah I will do this when I can get ForScan to connect. Still didnt want to. It would connect, but then say something about an ELM error after. Ill check it again tomorrow.
 
That is really odd. I have no idea why it would only work with the key off. unless you got a random error the first time and it was gone the second. honestly I have no idea. The bcm does have power with the key off to support the key fob so that could be why it worked
Yeah, that's what I think is the reason why it worked. Either way it worked. Planning on experimenting with some other features tomorrow such as the Taillight option since my N/A has Euro Taillights and the emergency brake lamp option.
 
Ok I was def able to change the config in the IPC - sync freaked out and wont come back on completely. I have to reload the ab file to the ipc and see if I can master reset. if not I will have to reload the calibration files for sync. at this point I am wondering if I should look through the sync files now and see if I can tie this together
 
Discussion starter · #206 ·
Just ordered the elm. Pretty psyched to get the global windows working. Does it matter what chipset version of the ELM you order? Amazon had both 1.4 and 1.5. 1.4 had better ratings and more ratings. Both are USB.
I ordered a 1.5 that has the mod built in for both busses as well. My obdlink works fine for the global open application but wanted to get something else for testing purposes

Sent via Tapatalk using Galaxy Note 2
 
Discussion starter · #208 ·
Do you have a link for where you got yours from please?
Well...I went back and looked at it again and I must have misread the description. It is canbus readable but doesnt say both. Plus apparently it is coming from overseas.

Sent via Tapatalk using Galaxy Note 2
 
Discussion starter · #210 ·
Ok I was def able to change the config in the IPC - sync freaked out and wont come back on completely. I have to reload the ab file to the ipc and see if I can master reset. if not I will have to reload the calibration files for sync. at this point I am wondering if I should look through the sync files now and see if I can tie this together
I was reading that the Imobilizer theft deterent is tied to sync, becareful with this software.

I finally figured out how to determine the latest pcm calibrations. The one in my car is NOT the latest. unfortunately I only have access to pcm stuff. DL33T, can you get me the latest ipc calibration number according to your IDS?

Sent via Tapatalk using Galaxy Note 2
 
Yah give me a little while. Doing this in between easter stuff plus packing... We are moving. First up get sync back online. As far as the theft detergent the car starts and drives. Sync boots ... Just not correctly. I have a feeling its looking for a file that doesn't exist. Looking at the video from the nav TV again I notice it doesn't do CCC data. It reprograms sync ... Back to the drawing board
 
I was finally able to clear all the codes after global open/close with Forscan.
 
Discussion starter · #217 ·
I was finally able to clear all the codes after global open/close with Forscan.
Whenever you read or write with the program you are basically stopping the flow of messages on the bus to address only the module you need in this case the bcm. The rest of the modules see this as errors which cause the dtc's. Once you clear the dtc's they dont come back till you use Focccus again.

Sent via Tapatalk using Galaxy Note 2
 
Whenever you read or write with the program you are basically stopping the flow of messages on the bus to address only the module you need in this case the bcm. The rest of the modules see this as errors which cause the dtc's. Once you clear the dtc's they dont come back till you use Focccus again.

Sent via Tapatalk using Galaxy Note 2
Ah I see. Makes sense. There sure were a ton of them :)
 
Discussion starter · #219 ·
Ah I see. Makes sense. There sure were a ton of them :)
Yes. Forscan reports them as lost communication errors. Now you know why.

Sent via Tapatalk using Galaxy Note 2
 
Discussion starter · #220 ·
I took a short video to demonstrate how far away you could be to get the window function to work. Unfortunately I couldnt make my phone camera stay zoomed to that far and stay in focus. Had to be atleast 50 yards if not further. Try it. You might be surprised.

Sent via Tapatalk using Galaxy Note 2
 
201 - 220 of 2,075 Posts