Welcome to the 2GNT Forum! Interested In Advertising with 2GNT?
Home | Site Background| Info&Specs| Mods & Tech Info | CAPS | Part Reviews | Donate | 2GNT Stickers |
Search Printer-friendly copy Email this topic to a friend 0 Users in Chat
Top 2GNT Technical Performance/Engine Engine Management Systems & Controllers topic #1727
View in linear mode

Subject: "RE: Uninstalling SAFC II from 99 eclipse rs" Previous topic | Next topic
Teamner947Jan-11-06 12:28 PM
Donating 2GNT member
3168 posts,
Click to send email to this author Click to send private message to this author Click to view this author's profile Click to add this author to your buddy list
#1733, "RE: Uninstalling SAFC II from 99 eclipse rs"
In response to In response to 1




          

Originally posted by Star Turbo Talon
Well as you can see most of the SAFC wires are just tapped into the factory wires. those can be unsoldered or cut in the clear and the factory wires can be taped up. 2 wires from the SAFC when spliced actually cut the Map signal wire. These two wires need to be cut away from the SAFC and spliced back together. That should complete the removal of the Harness splicing. Terry


If the SAFC was installed correctly you don't have to cut or solder anything to disable it, there are connectors included with the system that allow the user to un-bypass the MAP sensor output.


2016 WRX STi Limited (current)
2001 A4 1.8tqms (donated)
1991 GVR4 #1933 (sold)
old.dsmregistry.com/detail.php?carid=218 (dismantled)

  

Report This Post to Admin Printer-friendly copy | Reply | Reply with quote

Uninstalling SAFC II from 99 eclipse rs [View all] , evotunedscc, Jan-08-06 01:10 PM
  RE: Uninstalling SAFC II from 99 eclipse rs, AdministratorStar Turbo Talon, Jan-08-06 05:11 PM, #1
RE: Uninstalling SAFC II from 99 eclipse rs, Teamner947, Jan-11-06 12:28 PM #2

Top 2GNT Technical Performance/Engine Engine Management Systems & Controllers topic #1727 Previous topic | Next topic
Powered by DCForum+ Version 1.2
Copyright 1997-2003 DCScripts.com

I generated this page in 0.022374153137207 seconds, executing 14 queries.