Re: M1.5.5 ECU Communication Update
You need the generic interface - the type that VAG COM uses should do the trick,,, I've got a PCB schematic somewhere of the one I used, as the VAG COM wasn't always pulling up the high level enough...
You don't need the 16 pin OBD plug though for the 145/146, only the 156/147/gtv/spider needs the 16 pin. The 145/146 uses a 3 pin, in total parts, about <£15.
For now, it only works on M1.5.5 ECU, the phase 2 TS engines, unsure as to whether it would work on the earlier M2.10.x ECU.
The odometer you mention there mcguinn, is not fully functional yet, still working on the calculation. It is read only - so far all you see there is read only, but the ECU also stores total mileage - so you can see how many miles the ECU has done. There is no write procedure for that.
Displayed mileage on the instrument cluster is stored in the CPU in the Magnetti Marelli dials - and needs to have a programmer attached direclty to the CPU (or the CPU unsoldered and stuck in a reader/writer). Not something I'm interested in...
Coming next: test procedures: I have found the test mode, to enable you to test various inputs/outputs -eg you can open the variable manifold, put the fan relay on speed 1 or 2, etc
to sum up new alfaman:
a)yes. The more items you refresh, the slower the refresh rate - has been updated so you just pick want you want to update now.
b)there is nothing to change yet. Not planning to crack the seed request to enter download/upload for the fuel/ign maps. What were you hoping to change?
c)Nowhere yet, but if this takes off, may look at selling a cable/software bundle. Maybe.
Websites are like ********s, everyone has one, and im wary of any bloke trying to direct people into their's