well, apparently to this guy anything that isn't a stand alone is a piggy back...
We may earn a small commission from affiliate links and paid advertisements. Terms
that is the lamest explanation i ever heard...any thing added into the factory ecu is basically a piggyback cuz your still using a factory computer to run it
it replaces the stock rom chip? gee thats funny im pretty sure you have to desolder the board and put a couple sockets in with some resistors so it would be adding them in i used to run hondata at the time they didnt support itbs and was forced to find an alternative to run my all motor car and neptune just barely came out and wasnt offering software with there units and i wasnt gonna tow my car 150miles to get it tuned when i have my own dyno^For real. AND to clear that up, its not added to the ECU, it replaces the stock rom chip.
Sounds like someone is blinded by big name and dollar parts
Sounds like someone is blinded by big name and dollar parts
Why piggybacks (vafc, emanage) "suck" by pgmfi:
Piggy Back controllers allow stock ECUs to do things that they normally can't do, like run larger injectors or deal with boost. Remember that piggyback controllers work by altering sensor signals before they get to the ECU.
Most of the time, the primary signal being messed with is the Map Sensor. This is critically important in a Speed Density car. The Map Sensor is used by the ECU to guess how much air is going into the car, and therefore how much fuel to supply in order to match airflow. When you "lean" out a car with an AFC, you are simply decreasing the Map Sensor signal - the ECU responds to the decrease in manifold pressure by supplying less fuel. When you "richen" a car with an AFC, you are simply increasing the Map Sensor signal - the ECU responds to the increase in manifold pressure by supplying more fuel.
The change in fueling happens for a reason: if you look at a fuel table, Map Sensor values correspond with columns. When you increase or decrease the signal from the Map Sensor, you are simply making the ECU use a different column than it originally would have used. (see Understanding Maps if you need some help understanding reading Fuel and Ign tables)
But wait, isn't the Map Sensor used for determining ignition requirements too? When you "lean" out a car with a Piggy Back, you also in all likelyhood advanced timing. When you "richen" a car with a Piggy Back, you also in all likelyhood retarded timing. Look at trends horizontally (as MAP changes) in an ignition table, and you will see why this happens. This helps explain why so many boosted cars running on the "AFC hack" have issues due to excessive ignition advance.
The bottom line: Piggy Back Controllers suck because you cannot independently adjust fuel and ignition. Any changes to fueling will produce a change in ignition too, and often this is undesirable.
any thing added into the factory ecu is basically a piggyback cuz your still using a factory computer to run it
A Piggy Back controller is a device that "piggybacks" on top of the ECU. Piggybacks intercept signals coming from the engine and alter them before they reach the ECU. The most commonly abused piggyback controllers are the Apexi SAFC, VAFC, SAFC2 and VAFC2. The Greddy E-Manage is a big badass piggyback controller on steroids. You could think of a lot of the garbage that comes with a JRSC kit as a piggyback, as their relay and crap setup causes bogus sensor values to be passed to the ECU.
yes, yes, yes, yes and yes. crome does all that.how about control boost, traction control, boost by gears, datalog hours of info and loop itself to the begining ,anti-lag and crome is not a standalone its a program designed to work with a ("FACTORY ECU") so how is that considered like a standalone? factory ecu's have boundries that are already in the program, standalones you make your own boundries it does what you tell it too.