Configure to display Lambda, not AIM
Some round devices (notably those manufactured in 2021-09) were shipped with an unusual config, that displays AIM-data or -FU if AIM not received. Admittedly annoying. Sorry about that.
- device HW always carefully tested several times before sending
- If not actually using AIM stream, it can be reconfigured in 4 minutes.
We recommend to File/save config before proceeding.
- Also take note of some values (Advanced menu EGT and Wideband settings):
- EGT calibration: 151-152 usually
- EGT offset: 80..200 usually
- 0.5C / step, any value from 0..255 is normal if the device temp is roughly displayed as EGT temp when the K-thermocouple input is shorted
- Wideband pump_pw_zero: 99 usually (or close, eg. 98 less often)
- Wideband nernst_dc_target: 228 usually (mostly)
- Download [round_0.7.51.vemscfg] file to local disk
- File/upload config to device (with VemsTune)
- (Advanced/) EGT offset might be changed, so adjust according to your records, or calibrate with K-thermocouple input shorted
Alternatively: Edit vemscfg file:
- config.display_mode[N]=0x instead of 8x
- config.display_mode[N]=5x instead of Dx (but AFR is counterrecommended)
- eg. (most importantly)
- config.display_mode[0]=80 <= display data from AIM input
- change to
- config.display_mode[0]=00 <= display lambda measured by device
File/upload config (choose the edited vemscfg file).
After that, device displays lambda, and not AIM (which is not received => indicated by -FU).
We are checking how to set it from VT. (possibly VT ini change).
Thanks for the patience.
Issue with round (manufactured 2021-08) firmware 0.7.51
REPRODUCED ISSUE in lab. On good track now. Thanks for the patience
config.display_mode[0]=80 THIS CONFIG IS WRONG, >=80 (upper nibble >= 8) is for AIM function, but AIM it does NOT receive.
- Workaround: Edit file, like:
- config.display_mode[0]=00 instead of 80 (to display Lambda and EGT: recommended)
- config.display_mode[4]=50 instead of D0 (to display AFR, not recommended)
- and upload config. We're examining why VT does not make it more obvious that display is set to AIM.... (TODO: how to configure with VT for non-AIM ?)
The gauge is happy that the sensor is working and showing correct lambda in VemsTune.
- "display is slot 0 and max is 0 it's still showing -FU (problem!)
- Display Peak values="actual values" are selected, right ?
- Correct
- Display Peak values="actual values" are selected, right ?
It can show other things in the top row, but AFR or Lambda just shows "-FU" (indicating possibly Display Peak value="peak value" selected instead of "actual value", or target not reached problem, are the wires safe and sound ?).
- Wires must be safe and sound I?ve already used the 0-5v output to tune an engine with this and the 0-5v responds exactly as expected, x% more fuel in ecu = X% more richer in vemstune and on the analog out
Can you do Tools/Firmware verify 0.7.51 ? (just in case)
- uploading any other firmware version is not currently supported (this has full functionality, and no other fw relased for this device).
Please investigate and respond to report crvGcr
- we upload a config that shows correct lambda/O2
- your config (extracting from report)
- I?ll upload the latest config to the report.
- All configs ever uploaded to report
- I?ll upload the latest config to the report.