1.1.99 - seems to operate OK, but 1.2.0 recommended because of annoying usable testing (test results welcome, of course) (if you tested experimental secret versions, check firmware info so you don't accidentally leave any 1.1.99 earlier than 2012-05-07 on an ECU)

* getting more and more positive feedback, including Fero's Nissan 360 tooth (6cyl, using ignore sectrig above 4000 setting) works perfectly

* wideband measures up to 50 lambda measurement per second (when both channels enabled: 25 per channel)

** EGO also improved when "dynamic speed"=enabled (recommended testing).

** just in case, recommended to verify wbo2 free-air calibration and check nernst voltage is appr. 4.5V (0.45V above pump-)

* configurable warmup LSU4 wideband sensor on boot when ego_conf WBO2_WARMUP_ONBOOT bit1=0

** useful during early stage of install (although it's best to have a blindplug in the exhaust until the engine idles well), or for producer-gas powerplants

* config11 bit3=1 disables launch when ALS switch is activated (earlier, and when bit3=0, launch takes precedence). See (improved operation in) 1.2.6

** renamed in new VT. Note: this bit used to be called the "Throttle-body / port injection" (so you can toggle in old VT) and had no effect on operation at all before firmware 1.1.99.

* there was a bit long feature-freeze while important tools were developed and improved to confirm ignition and injection correctness and accuracy in a large number of setups, in wide range of operating conditions

----

1.1.98 - NOT released (only for testing !) and will never be released

* KNOW BUG: ADC-can-freeze at startup values - fixed in 1.1.99 but 1.1.98 will not be release

** on bench, when we play trigger continuously, and do LOTSOF power-cycles, ADC (eg. MAP, TPS, ... values) can freeze once in 30 cases

** on real engine (someone said every 50th startup on a 60-2 4cyl, every 10th on a mitsubishi 4cyl) it can also act same way (than engine idles at MAP=101kPa like trash)

* both WBO2 channels are displayed in VemsTune (and captured in vemslog). Question. How do you calibrate second WBO2 chanel/ display free air O2 reading??.........

** when ordering assembled controller, request in order comment that both WBO2 channels are tested (otherwise some pins like heater2 might be used for other functions, like analog input channel)

*** Respecting the above, also ensure R103 75k soldered on existing or self built boards.

* selectable noise-cancellation strategy for wheelspeed1 input

** after improving noise-filtering to work well (with automatic time-threshold) with a shown noise-pattern (prelling), some users complained that their wheelspeed worked well earlier with the manually adjustable time-threshold but not with the new one. So we made the old / new strategy selectable from config

* tachometer output improved at high RPM

** (unlike the precise ignition and inj outputs, tachout is issued from userspace, but now with higher priority).

** Freq was ok but duty was deviating, some tacho-gauges shown to be sensitive about this, now improved

* more tolerant to race condition between auditrigger 135 pulse signal and the crankhome-VR pulse. (eg when the sectrig pulse comes after 269, 270 or 271 primtrig pulse).

** auditrigger camhall scope (in 1.1.97) made the firmware to only work for c270 auditrigger, now c129 (like MembersPage/KevinBlack/PorscheTurbo ) and divby43 and divby27 works again

* stepper pins set to 12V at poweroff (not to GND) if negative polarity configured for stepper iac

* made MembersPage/Fero/MitsubishiEVO sync condition stricter after startup in [1.1.98_evosync]

** This means that before first spark it will need a full camsync revolution (1.0 .. 2.0 camrot depending on starting position: 1.5 camrot on average), but more tolerant to noise at startup.

----

1.1.97 - NOT released (only for testing Nissan 360 and more testing for BMW double-vanos)

* Around when subaru 36-2-2-2 VVTI (camshaft angle control, AVCS) was implemented, the subaru 36-2-2-2 without camsync config setup was hijacked for some time for mitsubishi-evo (a setup made according to bogus specs we received, later remade with a different approach and config). Now from 1.1.97 gifted back to subaru (while factory subaru-s have camsync, which was not effected, it makes sense to run subarus with wasted spark setup without camsync: possible again).

* high-current (powerful) unipolar stepper driven from 4 injector outputs.

** We'll think about how this (rarely used, but useful) feature to make the chance minimal that this annoys those who don't use it. Not compiled in by default (and needs special config: stepper+ iac-dual-solenoid configured)

* triggerlog is now useful at higher RPM (eg. with 60-2 at >9k RPM), as the primary teeth are "compressed" (eg. only missing tooth is shown at high RPM, not every tooth)

* more tolerant if sectrig is lost (or moved out of the allowed window) at high RPM especially if missing tooth primtrig signal is OK (especially useful with doublevanos / VVTI apps).

* 360 tooth Nissan trigger implemented (eg skyline)

** 4 or 6 window pulse goes to primtrig-HALL

** sectrig=HALL, 360 pulse connected to EC36/13

** hardware-divby4 NOT required (and not recommended), since benctest RPM>12000 RPM (more than 2.1 million pulses / minute) without the divider

* cam-hall scope is possible (hall connected to third trigger instead of masking the crankhome VR). Known limitation in 1.1.97 (only effecting auditrigger divbyN and divby3 in 1.1.97, and not an issue from 1.1.98):

** only the traditional c270, divby3, 2*135=270 real tooth per cycle works (90 teeth in config). c129, or divby43 or divby27 does NOT work

----

[1.1.96] - RELEASED

* extrapulse triggers (with cam position measurement support for camshaft-angle-control)

** like some Honda 30, 30, 30, 10,20, 30, 30, 30, 30, 30, 30, 30, 30 crankwheel

** 120, 120, 40,80, 120, 120, 120 camwheel (typical 6cyl inline truck/powerplant engine)

** other extrapulse trigger examples: 60,120, 180 or 90,90, 180 (the simplest 4-cyl crankwheel). The latter can be configured as 4-1 also.

* BMW double-vanos with 60-2 primary trigger

** 6+extrapulse MUST be connected to sectrig !

** optional (but recommended): the other cam, 6 evenly placed pulses can be connected to the 3d trigger. The "exhaust cam" table is used for this, regardless of which cam the signal is actually from (is this from the intake cam in the factory app ?).

** Fero(BMW Tököl) needs to swap the intake and exhaust cam signal connections (so the 6+extrapulse goes to the secondary trigger not the 3d trigger).

* RPM actuator ("shiftlight") semantics changed at very low RPM, because the intended hysteresys was non-intuitive for configured 0 or 100 RPM threshold:

** if configured to 0 RPM, then shows running (trigger pulses seen) / not running

** if configured to 100 RPM, then turns on above 200 RPM, turns off below 100 RPM

** if configured > 100 RPM then works as originally (+-100 RPM threshold)

* with original InputTrigger/AudiTrigger "Hallgebersignal" is around the crankhome-VR pulse (VT/Tools/play trigger "c270" type: sectrig is every 270 primtrig pulse: every second crankhome-VR masked away by the HALL signal)

** in some installs like the camsync is short and so unfixably offsetted that it cannot mask away one of 2 crankhome-VR pulses

** from 1.1.96, if Motorsport/camshaft angle control/third trigger is enabled with auditrigger, than one sectrig pulse expected every 135 primtrig pulse, and the camsync can be connected to the 3d trigger input (only available on econoseal pin if requested explicitely, since normally only useful for double-VVTI setups where exhaust cam is also controlled hydraulically like the BMW double-Vanos)

** pleasant side-effect: all 3 triggers show up in the triggerlog ("primtrig", "sectrig", "exhaust cam"). See example: in VemsTune analyze the triggerlog from [download zip of this share]. Therefore with this setup it's even easier to diagnose if the crankhome-VR or the cam-HALL signal is faulty. Traditionally possible to diagnose by disconnecting HALL sensor (with cam-HALL inverter, pulling HALL input to GND also needed)

** for now, only tested with divby3 (not with divby27 or other dividers). Keep the 3d trigger disabled unless you really know what you are doing and ready to bench, strobe, etc... Just in case, VemsTune validate will warn if 3d trigger is enabled (usually not intended).

----

[1.1.95] - RELEASED

* improved wheelspeed filtering of noisy (prelling) wheelspeed signal (on both wheelspeed inputs)

** Sami provided a suitably noisy log (thanx!) from the mechanical reed-relay of his audi transmission, so we could implement better filtering that handles this case:

** Above 318 (km/h or mph according to calibration) it's considered prelling-noise and filtered. 255-318 is allowed (no overflow to 0), measured speed stays high. 0-255 is displayed normally (good signal was good earlier also).

* For 1.1.94 and earlier, wheelspeed dependent launch-mode must be used when wheelspeed is used at all.

** even if all launchRPM values are same (say 4500 RPM) and speed bins are all 255

** from 1.1.95 the no-wheelspeed dependent mode might work as expected (even if wheelspeed>=1) with just 1-RPM value configured

** it is still recommended to use the wheelspeed dependent launch-mode (which is more flexible anyway) when wheelspeed is used.

* SD-card read-retry number bumped up so

** some really slow cards that did not work earlier can now be used (the standards does not specify max delay)

----

[1.1.94] RELEASED

* [Trans Brake Creep]

** feature was implemented in 1.1.90 but now TRANS_BRAKE_CREEP enabled in default my_make (available to every VEMS user without special request)

* logging will restart if SD-card is removed and (usually another) card is inserted.

** drag and rally racers requested this to restart SD-logging within about half minute after SD-card swap (even if engine is not stopped)

** this feature was implemented in 1.1.92 and worked well for SD-card swap, but if the SD-card was removed but another card not inserted (or SD-card logging was enabled with card not installed at all), the reinit attempt disabled interrupts for milliseconds (not microseconds), causing occasional trigger-error. Fixed in 1.1.94 : Now enabling SD-card does not cause trigger-error even if card is not installed (This cannot cause trigger-error in <1.1.92 since it does not try to reinitialize the card again and again, only at startup).

* if priming pulse was configured non-0, than actual priming pulse was min 6 msec (range: 6.1 to 31.5 msec)

** new range is 0.1 to 25.5 msec

----

1.1.93 - was never released, now withdrawn, see 1.1.94 notes

* [exhaust cam control] also supported with 2 solenoid "Vanos" mode (not just with PWM "suzuki"-mode)

* in 1.1.92 and 1.1.93 disable SD-card logging if SD-card is not installed or removed (otherwise trigger-err might show up every 32 second).

** If SD-card is enabled, it is recommended to use >=1.1.94 or < 1.1.92 so this cannot effect even if SD-card is unplugged or disconnected

----

1.1.92 - was never released, now withdrawn, see 1.1.94 notes

* InputTrigger/SubaruThirtySixMinusTwoMinusTwoMinusTwo supported with camshaft control of both left and right camshaft

** A (right, intake) connected to secondary trigger input

** and B (left, also intake but connected to "exhaust cam input").

** please note (if upgrading from a working pre-1.1.92 subaru config) that tooth0 got 30 crankdeg delay to the "4BTDC10" point so: trigger_tooth=02 (instead of 3) and TDC delay=120 deg - verify with strobe !

* suzuki cam position (camshaft angle control) also supported

** both are tested with signals that match scopeshots (and also fluctuated a bit to allow reasonable deviation). Need real-engine tests (experienced installers).

* MembersPage/Fero/MitsubishiEVO supported

* iac_close_minmap can be set to any reasonable (non-FF) value, will not effect IAC flag

* in 1.1.92 and 1.1.93 disable SD-card logging if SD-card is not installed or removed (otherwise trigger-err might show up every 32 second).

** If SD-card is enabled, it is recommended to use >=1.1.94 or < 1.1.92 so this cannot effect even if SD-card is unplugged or disconnected

----

1.1.91 - will not be released

* Anytrim controls expanded with speed sensor inputs as trimming source

* GPS speed sent out to Round on AIM protocol

* in 1.1.91, leave iac_close_minmap at FF (510 kPa default value) - or use 1.1.92

** otherwise iac flag might be left on in some cases, possibly effecting sparkadv (due to iac retard)

----

1.1.90 - will never be released

* Iac can force to specified duty when reached the specified Map (usefull for Boost)

* Injector dead time has a simpler strategy

* Triggerlog logs the Spark events

* Maserati trigger support: MembersPage/OddFireSixCyl

* Staging injectors can switch with RPM limits

----

1.1.89

* v3 can now log GPS data to SDcard

** when vemstune notebook is not connected, a GPS can be connected to comm-port (our GPS is 4800 baud, which, unfortunately is different from the standard 19200 baud aim-default baudrate)

** anyway, time information is no longer lacking for logfiles ... this way GPS replaces RTC

** second serial input on V3 also can use for GPS

** for details see: GenBoard/LoggerIntegration/MMC

* MembersPage/DamirMuha/MagnetMmarelliCamSensor support

** new sectrig setting: to neglect the offending pulses from 3 (or more) sectrig pulses

* the new vemstune (coming out late Febr) syncs superfast to 1.1.89

** VT recognizes page-data checksums and only downloads changed pages (like rsync).

** But initial config-download is much faster also

* Secondary trigger input can use as a stand-alone primary trigger

----

[1.1.88] Withdrawn !

* withdrawn because compiled with KNOCK_ALTERNATIVE that seems to cause problems (ign advance different than table) under certain circumstances. Upgrade to latest released version is highly recommended.

** the actual ign-advance is in the log

** if the upgrade is expensive, we'll benchtest any config on request (best to use MembersPage or VemsTune Help to post vemslog or vemscfg) and report if the test shows it is effected, and upgrade the config to latest release, test that too, to make upgrade a simple "connect and upload" type 4 minute operation.

* Rover K series 36-1-1-1 type MembersPage/YasecElise trigger supported

** configure "elise trigger": from "primary trigger" dialog upload Elise configlet if available, else: "4cyl 36-1 no camsync", press validate. Set number of tooth to 32 (not 35). Press burn.

From tooth_wheel=20 (decimal 32) the firmware will know it's not 36-1