Unichip Applications??? - Page 3 - Perth-WRX.com

mr_psi · #21 08-06-2007, 09:40 AM

powerfc + scali/sean = porn

Intra · #22 08-06-2007, 09:46 AM

i would have to agree with the power fc route, just find a shop you trust to do the work. Unless you wanna run more then 2 bar , maybe consider a motec.

pete gopal · #23 08-06-2007, 09:49 AM

Any word when verso will be available for 99/00 emailed them by no response thus far...

maddog · #24 08-06-2007, 12:41 PM

Quote:

Originally Posted by Intra

heheh.

Ok Facts.

1. 94 -00 had a change from the Jecs based board which ran a mitsubishi melps 7700 MCU to a denso manufactured board with a Motorola based MCU and now a Hitachi based MCU. There were heaps of logic changes and operational routines which control how the engine reacts to feedback and environmental changes. Not to mention they are all completely different MCU's which need different opcodes to relate back to operands. If we dig even further you'll notice the break down is like this

94 - 96 : Jecs revision with SSM Support
97 - 98 : Changed board revision with SSM Support
99 - 00 : Changed board revision with new connector and obd2 support and SSM support

01 -> current :Changed again , with OBD2 and SSM support and future support to SSMIII

2. "adjusted accordingly" is closed loop, an adjusting of engine conditions based on feedback is what i would classify as closed loop. Open loop is usually based on conditions of throttle or other factors which tell the ecu to then disregard feedback.

3. Emissions didn't seem to be much of a worry early on in the game, Subaru along with other manufacturers are now in a position to keep within emission laws much tighter then before and that can clearly be seen with stock mixtures, more elaborative components such as TGV's to aid atomization on warm up, Air pump in newer models to inject more air to help with burn etc.

Apologies up front for hijacking the thread, but the humble Unichip was always incorrectly blamed for the OEM ECU boost spike.

1. Nice start...

2. Further factual data...I am not referring to the entire ECU process just the Boost. Boost control on pre 01 Imprezas use two main maps. Both are 8x8 in size, but have entirely different functions. Being: "Boost Achieve" and "Duty Cycle Aim". Boost Achieve is two dimensional, and as you know, varied according to both RPM and engine load (some models kept load static).

Duty aim map specifies the "best guess" duty cycles required to deliver the desired boost curve, specified in the Boost Achieve map. This map allows the ECU to take a GUESS at the required actuator duty BEFORE closed loop control homes in on the desired boost. Get your aim map too high, and the boost will overshoot. Get it too low, and spool up will be impaired in lower gears.

Quasi closed loop, virtual open loop until it gets within control parameters, parameters that vary with RPM and load. Yes you are technically correct but given the system does not work its as good as open loop

What happens to boost on a cold night in a pre 01

3. Change is guaranteed! Good discussion.

Kato · #25 08-06-2007, 01:20 PM

Interesting discussion here.

On topic: Unichip - meh. As others have said look at a Power FC instead. I don't like the idea of 'tricking' the stock ecu into thinking its doing something its not. Regardless of how good the tune is, it just doesn't seem right. But thats just me.

Now for the open/closed loop discussion...

My brief understanding:

Open loop system: No feedback is involved. Pre-programmed maps are run without checking any meaured variables.

Closed loop system: Feedback is put back into the controller from measured variables.

Easiest analogy (had to use a word with 'anal' in it) is an airconditioning system. If you just turn it on, cold air comes out. No check to see if the air is too cold, if the room is too cold or you are frozen. Open loop system.

A climate control air conditioning system gets feedback from different variables to hold the temperature of the room at a specified temperature. Closed loop system.

Now as for the ECU's... From my brief understanding the ECU has a target map for boost, which it tries to achieve. Now to achieve this it has to be reading variables so it can correct the boost to arrive at its target. To me this sounds like a closed loop PID controller.