V3 on a Classic... and it works!

V3 SOFTWARE EMU CLASSIC V3 BETA
1

I had a bit of time to load the new firmware onto an Emu Classic today. The engine is an Alfa twinspark from a 1988 Alfa 75. It’s a naturally aspirated two litre 4 cylinder, running Alpha-n with ITBs, an IACV and map sensor,

The v3.065 firmware installation was straightforward (following the guide in the usual way). I had prepared a project file using v3.064 and loading that into the ECU went smoothly, with just two notifications:

Error: Cannot find table wboLambdaTable in current project. Skipped.

Error: Cannot find table wboIPNormTable in current project. Skipped.

I wasn’t sure (still not sure) what toese errors relate to as I had a Lambda table in my map, so decided to just try to start the car… and boom, it fired straight up! I think it actually started faster than with the v1 firmware.

The pre-loaded PID settings worked ok for the initial idle conrol, but it’s going to take me a little time to get used to the new PID settings work in v3.

I didn’t have time to take the car out of the shed, so was just playing with the idle control today.

One thing I’m grappling with is my CLT fan activation. With the ITB set-up, I need to add in about 20% DC to the idle to keep the engine at idle speed. As my CLT temperature get’s close to the fan activation temperature, I think the CLT voltage fluctuates a little and hits the fan activation temp, then the voltage drops back down below activation temp. I have a 25ms delay on the fan activation, so the fan doesn’t start up, but the voltage causes my idle valve DC to spike up and down, causing the engine to surge a little. Is there some way that I can activate a filter on the CLT input (in the way that you can for other analogue inputs)?

Very happy with the way things went today - great job to the team!

2

If you have noisy CLT then something is wrong with your wiring harness.

3

It’s fluctuating by a degree, but agree a coolant sensor shouldn’t do that and i’m just trying to delay the inevitable rewire that it needs…

4

There is a hysteresis for coolant fan. By default is the 5 degres. Time to engnage is a delay between CF falg set and coolant fan engage. It gives time for idle controller to increase the DC

5

OK, i decreased my hysteris value, so can try adusting that back up. Does the idle DC increase start based on the flag being triggered, or only after the delay period?

6

Idle increase is immediate the fan is physicaly engaged after the delay.

7

That makes sense based on what i’m seeing. If the idle DC only increased once the delay was completed, that might cure it, but that would defeat the original purpose of the delay… I’ll live with it for another month until i can do a rewire. Thanks for the clarifications.