** what is really going on with this ? What can be considered real, and what is misunderstanding, or "excuse" ? (the vemslogs seem absolutely real).

** You clearly reported that you received LSU4.9 sensor and you had to set LSU4.9 in config yourself (congrats !), now reporting that you received LSU4.2 sensor but ordered LSU4.9 (which is not the case).

** So did you receive LSU4.2 than ? Which is actually true? Either is fine for the order, but technically it matters if wbo2 related supports is needed.

Sorry about that: indeed the config file was uploaded exactly as requested without any change; would have been kind to change config for LSU4.9 (ECUs are tested during manufacturing; packaging is separate step: the sensor, paper and small SSC5-LSU4.9 loom is included in the pack during packaging).

The 'update' was on VE and lamda tables that i had reviewed myself after recent checks.

Cool, thanks.

* so it seems the low oil-level is unlit when engine is started and oil-pressure is present (good)

** I need this fixed and corrected as it may cause longterm problems with my dash on parts that are no longer available

** There should be no high-voltage or anything similar that could damage the dash.

* Yes, the semantics in fw changed slightly a few years ago and not exactly same VE (or reqfuel) values are needed for same injector-pulsewidth (multiple benchtests showed within 1.5%, definitely much lower than 15%). Usually no difference when upgrading, but when a very old (eg. 1.2.11) config / tables are uploaded to new firmware (eg. 1.2.23 or later) => it might be somewhat rich (changes are on the safe side at least, but tuning is good... It is actually tunable as the main feature, so that it can always be tuned to the actual setup including injectors, fuel pressure regulator, head, turbo, firmware-generation).

** if you post an 1.2.11 vemslog and 1.2.31 vemslog on same engine (under similar conditions, eg MAT, CLT), we'll verify and investigate. If possible, point us to ...sec and ...sec time positions with comparable input-vector but more than 1.5% difference in injpw/(MAP*VE*req_fuel * enrichments).

* EGO was reading around 85 on all map regions

** ... aha, so removing appr 15% fuel(pw). (also same effect if eg fuel pressure is 4 bar instead of 3 bar, or if injector is different. I assume same types, just the fw differed - actually very same engine if I understand... But than, as the SSC5 WBO2-connection is backwards-compatible, your existing old LSU4.2 sensor can be used with the old SSC5-LSU4.2 loom, with old wbo2 sensor calibration value, and even old 1.2.11 fw... with same behavior that you liked that every possible way that matters - obviously ECU serialnr differ and new ECU has a bit more protection against installation abuse, eg. on analog inputs )

** If multiplier is that consistent (including idle?), might be easier to compensate with req_fuel (*=0.85). Just in case, check warmup and afterstart enrichment (is warmup enrichment 100% at CLT=72C ? Maybe it's ~115% causing the excess fuel / richness ? The view / calc model has a fuel pw related selection (try right-click) where the calculation can be followed, all factors of it... very useful.

** and considering latest info, and loom pinout matching LSU4.2, that might be perfectly correct (and than anything with LSU4.9 setting is on the wrong track and explains many things)

After changing the wide band setting to match the LSU4.9 sensor and tried to recalibrate, it went to 255 for me to have 20.1 at air.

Ahh OK, so actually very close. As a car owner, if got absolutely certain about LSU4.9 type, keep the 255 config value. (and if you really care, compensate for the over-sensitive LSU4.9 sensor with lambdatarget=0.89 where 0.88 intended; 1.00 where 1.00)

** With that simple info, for no charge to you, we were considering to send an LSU4.9 sensor that is verified not at the extremely-sensitive end of the Bosch gaussian distribution (and we'd verify a stock of 300+ similar sensors without heating, to see how many are that extremely sensitive, if any).

*** OK. Although an Ohm measurement is the simplest thing that comes up during install (verifying injectors, igncoils, CLT/MAT sensors, WBO2 sensors, wires, all routine part of install+tune - even with a factory ECU if it comes to real-life diagnostic ). Anyway, glad to here you can tune the ECU, because that solves it all: you should be able to tune it as you wish.

** It just means that lower deviation from 1.0 lamda is displayed (lower than the real 20.9% O2 value is displayed; and higher than real lambda value displayed:

Any air pressure, elevation, humidity data perhaps ? Would only be useful with Rcal Ohm data though)

** it does not even prevent closed loop feedback EGO/lambda mixture control. VT can be configured to compensate, or another sensor can be used of course.

I am now using my old VEMS and i can send this unit back for all necessary checks.

It can be tuned where the engine is.

Maybe send the sensor if anything (but not before measuring Rcal).

I also tried 1.2.30 version without any success.

That is no surprise, as 1.2.30 works exactly as configured just like 1.2.31 (it's just that 1.2.31 has some new convenience and trigger features).

* perhaps all is good, as the vemslogs indicate... there are multiple contradictions in all claims (eg. multiple times stated and indirectly indicated that LSU4.9 received and had to change config from LSU4.2 to match LSU4.9 ... than he decides he received LSU4.2 ... since order was "with_LSU4sensor: yes", which means unspecified either LSU4.9 or LSU4.2; => either is good if configured so, and cable-pinout matches: we just need to verify accordingly)

* the sensor might be faulty (we do NOT heat the sensor, the sensor is tested by the manufacturer - Bosch in this case). But according to logs (and even calibration) the sensor seem to work and respond well.

* or perhaps the SSC5-LSU4.9 small loom might have 2 wires swapped, or perhaps all mirrored ? (we test the v3, and the manufacturer of the loom tests the loom, we just supply that from the shelf).

** still not properly confirmed below - confirmation only possible if the LSU4.9 / LSU4.2 becomes certainty; although probably good, otherwise vemslogs would look different

Besides the measurement, write the SSC5 pin number and the wire color for each pin (and the wire-color at the LSU4.9 sensor !), and verify connectivity and pin-correctness of the small SSC5-LSU4.9 loom according to the [LSU4.9 pdf].

* Marcel, as i mentioned to the email. It is most likely that VEMS has sent the wrong sensor to me when ordered the 4.9

** No, you said that "The lamda sensor 4.9 you provided cannot be calibrated now either"

** that means that you were sent LSU4.9;

** also, you didn't choose LSU4.2 or LSU4.9, but the LSU4 which can be either. So it's impossible that the wrong sensor type was sent. (it might be theoretically possible during summer holidays that the cable included was for the other type - but HEY, you would notice and report that the connector size is different and cannot be mated... wouldn't you ? )

"there is no attachment of .2 or .9 on the invoice and i dont understand why"

Because it is IRRELEVANT for the invoice. Logic dictates that the installer looks at the real sensor (not the invoice, which is not involved in the circuit !) and configures accordingly.

* In addition, as i connect my previous ECU no oil warning coming up

Why do you need 2 ECU for the same engine ? Was it ordered as spare ?

* Even though as you say it may not have any implications, i do not want to take the chance and ruin an original dash of an audi RS2

** Do not worry: if the dash breaks because of 0/12V tachin signal (which is always used for these dashes), we'll replace the dash.

* Therefore i would like to send both the lambda probe and ECU back to you for inspection and checks of the grounds and i would like this ECU to be tested on a vehicle before you send it back.

** Of course, just follow [instructions first]. I would like to receive clear reports without multiple contradictions.

To determine what is going on please provide a bit more information, please answer the following questions for me:

* are you using a new (or old please specify) lsu 4.2 or lsu 4.9 probe during the free-air calibration and is it in free-air not in exhaust ?

** The first 4.9 lsu calibration (with the wrong selection on vemstune, 4.2 instead of 4.9 matching the LSU4.9 sensor received) was done with a sensor completely new. The second calibration where the 255 was reached without being able to calibrate was done after the same 4.9 sensor was used with the car idling and myself looking at the trigger with a strobe light. So basically very little use.

||SSC5|| WBO2 || color || wirecolor inside sensor ||

It seems to be made to LSU4.2 pinout (it's a miracle that it works with LSU4.9 at all)... See [aan_doc.pdf]

* Apparently and after an email from Marcel, it seems that VEMS shop has sent me the wrong lambda probe.

** that is impossible, as the motronic55 was ordered with the LSU4=yes option that allows either type; not the (also selectable), more specific LSU4.2 or LSU4.9 which specifies type clearly

* when I read about the connector being different, I thought the size was slightly smaller, but when included in the package I get a connector to go with everything I thought I was sent the correct parts

** so it sounds now you received LSU4.2 (which is correct part) with correct loom for it, that has correct connector, and correct pinout

* In addition I didn't have my old 4.2LSU nearby to compare.

** But maybe you can read the numbers from the sensor ? Or measure the dimensions of the sensor connector ? Or take a photo (maybe with some ruler next to the connector, to better see scale ) ?

----

Can you help us understand how the misunderstandings arise ?

* Is English your native language ? ( parts shipped to UK. And apparently native, but maybe your 2nd language ?)

* Does Vasilios M. (guy from Munich, Germany, but usually shipping to Trikala, Greece) support you "connecting the sensors and map switching option etc." ?

** his discount (granted just recently) involved supporting you, but there is no sign of it whatsoever !

"Vasilios P... from UK bought after my suggestion directly from the shop as I was away on vacation. I will support him from now on on connecting the sensors and map switching option etc."

He even ordered "VEMS motronic55" since than, with same spec, but with discount. So atm this looks exactly like:

* order a device full-price

* referring that and get discount, ordered with discount

* asking to refund the full-price, and keep the same spec discounted device ?

Wether or not, wasted way too much time already with all the contradictions. Real information is absolutely required for support, misleading, contradicting ... info is not the way to go.

**Answered email about this subject

-----

Answer to both parties above Marcel and Dave

Look, just to clarify (and i will be ringing later to speak to someone)

1. the ECU ordered by me ( i am not Vasilis M from Munich but Vasilis P from the UK. I have no connection to Vasilis M from munich) was meant as an upgrade to my current ECU +/- spare. My current ECU was bought from EFIExpress back in 2009.

2. I ordered the ECU with the intention to have 1.2.31 and LSU 4.9 implemented as i am very busy with 2 small children, use the car almost everyday and was hoping to make a quick swap with everything being pnp.

3. When i placed the order, by checking the link: use lsu4 on the motronic pnp vems shop page, it links to LSU4.9 so i THOUGHT if i tick the WITH LSU4 i would be getting the LSU4.9 and not 4.2. This is where the problems start, as i assume i have a new ECU with a 4.9 connector and loom all ready to be fitted. I have schematics to go with it as were included in the order. Last time i fitted the LSU4.2 was in 2009 so no i did not check the size or the cable color on vems wiki to clarify what i had been sent. This was my mistake and i do apologise for not noticing sooner as the lamda issue and clarifications could have been avoided.

I therefore have an ECU without the 27k nerst pinup and without the 4.9 lamda. As i mentioned above the 2 lamda sensors (my old one 4.2 and the one sent from VEMS are IDENTICAL, have same size connectors but have different part numbers.

4. Besides the LSU issue, the dash issue is equally important to me. I cannot accept to use this ECU with it having some kind of electronic malfunction whereas it should not as a brand new item. This OIL level warning before startup can be very confusing and will force me to regularly check for oil level in a perfectly ok engine. I find this unacceptable for a brand new ECU to be working like this and vems trying to say: sure, its ok, it wont damage anything, when it shouldnt be doing it in the first place!!!

I would therefore like the ECU to be sent back to be checked for the above fault. If it cannot be fixed id like a refund. If it can be fixed, then id like the 27k pinup included and ill buy the 4.9LSU with the loom to connect to the ECU when sent back.

thanks

-----

Spoke to Marcel on the phone and clarified matters. Many thanks

ordered the 4.9LSU sensor