Edge not working at all.. Help
Edge not working at all.. Help
Ok so I got a 06' 4.6 and my buddy has a 07' 4.6. I sold it to him and he hooked it up and nothing happens on the screen at all. He already once installed it and it worked great. My truck has the stock tune and so does his, so now the Edge is at a still. Works and uploads on my truck, but does nothing not even come on on his. Its a Edge Evolution. Can he have a PCM or some kind of fuse blown not allowing it to get power?
See if the cigar lighter works on his truck. If not, it's a fuse. The lighter and the plug port use are seved by the same fuse.
__________________
Jim
Jim
Last edited by Bluejay; Sep 2, 2010 at 10:50 PM.
The OBD port is connected to the same fuse as the cigarette lighter it's possible thats what it is that fuse I believe is on the floor close to the firewall on the passenger side of the truck in the cab.
Don't see why you thought he was being sarcastic. He was saying he is the third person to say the same thing, it's the fuse.
__________________
Jim
Jim
Just cause a fuse blown to me isnt really a problem lol.. Thanks for the help guys, Im sure thats it.
Trending Topics

BTW, I come to Longview pretty often. My wife and I grew up there. May move back there some day, can't ever tell.
__________________
Jim
Jim
- Jack

Root Cause Analysis
An as-yet-to be-determined primary causality precipitated the catastrophic failure of the <fuse # here>, circuit leading to the corollary systemic disruption of the 12 volt supply rail to the Ford J1962 OBDII connector.
This resulted in the loss of connectivity to the J-2284 CANBUS interface, and a subsequent interruption of the datastream I/O to the end-user flash programming node currently on this bus.
Thus - it has been concluded that the fuse discontinuity was not the Root causality (sic: 'problem' fer y'all rednecks) but the visible secondary effect branching from the primary casuality.
The tertiary effect was the loss of connectivity to the end-user CAN node, but this was also the first-noticed physical manifistation of the primary causalitie's (to-be-determined) presence.
Finally, the quaternary effect invariably results in a "WTF?" post on an appropriaterly contextual online message board.
The Root primary causality remains a mystery. But it is in point of fact the PROBLEM.
Sorry - can't think of a simpler way to describe it :o

MGD
Last edited by MGDfan; Sep 3, 2010 at 05:21 PM.
I'll try to simplify this a bit if I may... 
Root Cause Analysis
An as-yet-to be-determined primary causality precipitated the catastrophic failure of the <fuse # here>, circuit leading to the corollary systemic disruption of the 12 volt supply rail to the Ford J1962 OBDII connector.
This resulted in the loss of connectivity to the J-2284 CANBUS interface, and a subsequent interruption of the datastream I/O to the end-user flash programming node currently on this bus.
Thus - it has been concluded that the fuse discontinuity was not the Root causality (sic: 'problem' fer y'all rednecks) but the visible secondary effect branching from the primary casuality.
The tertiary effect was the loss of connectivity to the end-user CAN node, but this was also the first-noticed physical manifistation of the primary causalitie's (to-be-determined) presence.
Finally, the quaternary effect invariably results in a "WTF?" post on an appropriaterly contextual online message board.
The Root primary causality remains a mystery. But it is in point of fact the PROBLEM.
Sorry - can't think of a simpler way to describe it :o

MGD

Root Cause Analysis
An as-yet-to be-determined primary causality precipitated the catastrophic failure of the <fuse # here>, circuit leading to the corollary systemic disruption of the 12 volt supply rail to the Ford J1962 OBDII connector.
This resulted in the loss of connectivity to the J-2284 CANBUS interface, and a subsequent interruption of the datastream I/O to the end-user flash programming node currently on this bus.
Thus - it has been concluded that the fuse discontinuity was not the Root causality (sic: 'problem' fer y'all rednecks) but the visible secondary effect branching from the primary casuality.
The tertiary effect was the loss of connectivity to the end-user CAN node, but this was also the first-noticed physical manifistation of the primary causalitie's (to-be-determined) presence.
Finally, the quaternary effect invariably results in a "WTF?" post on an appropriaterly contextual online message board.
The Root primary causality remains a mystery. But it is in point of fact the PROBLEM.
Sorry - can't think of a simpler way to describe it :o

MGD


X2
I'll try to simplify this a bit if I may... 
Root Cause Analysis
An as-yet-to be-determined primary causality precipitated the catastrophic failure of the <fuse # here>, circuit leading to the corollary systemic disruption of the 12 volt supply rail to the Ford J1962 OBDII connector.
This resulted in the loss of connectivity to the J-2284 CANBUS interface, and a subsequent interruption of the datastream I/O to the end-user flash programming node currently on this bus.
Thus - it has been concluded that the fuse discontinuity was not the Root causality (sic: 'problem' fer y'all rednecks) but the visible secondary effect branching from the primary casuality.
The tertiary effect was the loss of connectivity to the end-user CAN node, but this was also the first-noticed physical manifistation of the primary causalitie's (to-be-determined) presence.
Finally, the quaternary effect invariably results in a "WTF?" post on an appropriaterly contextual online message board.
The Root primary causality remains a mystery. But it is in point of fact the PROBLEM.
Sorry - can't think of a simpler way to describe it :o

MGD

Root Cause Analysis
An as-yet-to be-determined primary causality precipitated the catastrophic failure of the <fuse # here>, circuit leading to the corollary systemic disruption of the 12 volt supply rail to the Ford J1962 OBDII connector.
This resulted in the loss of connectivity to the J-2284 CANBUS interface, and a subsequent interruption of the datastream I/O to the end-user flash programming node currently on this bus.
Thus - it has been concluded that the fuse discontinuity was not the Root causality (sic: 'problem' fer y'all rednecks) but the visible secondary effect branching from the primary casuality.
The tertiary effect was the loss of connectivity to the end-user CAN node, but this was also the first-noticed physical manifistation of the primary causalitie's (to-be-determined) presence.
Finally, the quaternary effect invariably results in a "WTF?" post on an appropriaterly contextual online message board.
The Root primary causality remains a mystery. But it is in point of fact the PROBLEM.
Sorry - can't think of a simpler way to describe it :o

MGD
I'll try to simplify this a bit if I may... 
Root Cause Analysis
An as-yet-to be-determined primary causality precipitated the catastrophic failure of the <fuse # here>, circuit leading to the corollary systemic disruption of the 12 volt supply rail to the Ford J1962 OBDII connector.
This resulted in the loss of connectivity to the J-2284 CANBUS interface, and a subsequent interruption of the datastream I/O to the end-user flash programming node currently on this bus.
Thus - it has been concluded that the fuse discontinuity was not the Root causality (sic: 'problem' fer y'all rednecks) but the visible secondary effect branching from the primary casuality.
The tertiary effect was the loss of connectivity to the end-user CAN node, but this was also the first-noticed physical manifistation of the primary causalitie's (to-be-determined) presence.
Finally, the quaternary effect invariably results in a "WTF?" post on an appropriaterly contextual online message board.
The Root primary causality remains a mystery. But it is in point of fact the PROBLEM.
Sorry - can't think of a simpler way to describe it :o

MGD

Root Cause Analysis
An as-yet-to be-determined primary causality precipitated the catastrophic failure of the <fuse # here>, circuit leading to the corollary systemic disruption of the 12 volt supply rail to the Ford J1962 OBDII connector.
This resulted in the loss of connectivity to the J-2284 CANBUS interface, and a subsequent interruption of the datastream I/O to the end-user flash programming node currently on this bus.
Thus - it has been concluded that the fuse discontinuity was not the Root causality (sic: 'problem' fer y'all rednecks) but the visible secondary effect branching from the primary casuality.
The tertiary effect was the loss of connectivity to the end-user CAN node, but this was also the first-noticed physical manifistation of the primary causalitie's (to-be-determined) presence.
Finally, the quaternary effect invariably results in a "WTF?" post on an appropriaterly contextual online message board.
The Root primary causality remains a mystery. But it is in point of fact the PROBLEM.
Sorry - can't think of a simpler way to describe it :o

MGD
At least the part I understood.
__________________
Jim
Jim






