Safety Mode - prevent engine flooding caused by not following firmware upgrade steps
See [VemsTune Help] (contains the info one needs).
Old notes:
- for 1.1.83 (or newer) firmware use VemsTune 2011-01-14 or newer. Really.
- if you use I-button (=have v3 with "1 wire interface"=yes, own an I-button AND enable it in config) then see ButtonImmobilizer (than not touching on I-button between fw upgrade and config upload will provide similar anti-flood features as this safetymode, so you don't need this page).
Usage - for firmware 1.1.83 (or newer)
From firmware version 1.1.83 the Injector and ignition outputs are disabled after firmware upload.
- in later 2.x firmware stepper outputs are also disabled
- Lots of cars have ignition coils connected to stepper outputs
- normally: p259 is not used for ignition, and not disabled: most notably CEL (warninglight) output can be active (or flashing if ECU is waiting for 1-wire I-Button authentication)
To reenable the ECU:
- easy way: In "firmware upload" press enter (not "cancel" !) in the "upload saved config" step.
That's all. Nothing special needs to be done in the normal case. For advanced users:
- if you cancelled that step, you can also do it later: upload a proper config and VemsTune (newer than 2011-01-14) sets automatically.
- OR manually: set prohibit/iButton high and low byte manually, values below (do it only if the config on the ECU is verified and all good)
Background information: - for the curious
After firmware upload the config might be absolutely wrong.
- If the recommended firmware upgrade process was not followed (eg. fuses not removed), in the past it could result in injectors open after boot
- => engine flooded with fuel or ignition fuse blown.
- this cannot happen with the correct procedure. But the procedure was inconvenient and some steps sometimes got forgotten.
Solution:
From firmware version 1.1.83 the Injector and ignition outputs are disabled by default, until they are enabled by
either
- a special firmware-version dependant configuration word (named prohibit, 2 bytes) re-enables it
- naturally, after firmware upgrade, this word will be wrong, and need to be set. (VemsTune newer than 2010-10-03 set automatically after config upload).
- OR - if using iButton anti-theft - , enabled by touching on the configured I-Button.
- needless to say, do NOT touch on, until uploading the correct config
Advanced users - will not be needed since VemsTune 2010-11-xx and newer calculates this and sets after config upload.
Calculation example for prohibit values:
- bit 15: PS2-type
- bit 14..13: 0 not using now
- bit 12..10: firmware version first number
- bit 9..7: firmware version second number
- bit 6..0: firmware version third number
- example:
- non ps2 1 .1 83:
- 000 001 001 1010011= 0x04D3 -> prohibit high byte is decimal 4, prohibit low byte is decimal 211
- non ps2 1 .2 31:
- 000 001 010 0011111= 0x0517 -> prohibit high byte is decimal 5, prohibit low byte is decimal 33
There is a special code to prohibit variables which works with any firmware for developing, Use it only if nothing else works: 0xBEEF
- ECU calibrations dialog prohibit high,low byte settings:
- 04, 213 for 1.1.85 (nonps2)
- 04, 215 for 1.1.87 (nonps2)
- 04, 216 for 1.1.88 (nonps2)
- 04, 128+x for 1.1.x (nonps2)
- 132, 128+x for 1.1.x (ps2)
- 190, 239 (=0xBEEF) enables inj+ign for any firmware even if no valid config has been uploaded
- therefore not recommended, (except as last resort), because it might flood your cylinders with fuel if config is not uploaded, or after a future firmware upgrade
- so if you used this BEEF trick, please change this to 0,0 before firmware upgrade, or apply the oldschool precautions: remove injector conn, fuelpump fuse, ignfuse, etc...