|
Post by olasharan on Aug 16, 2019 11:39:01 GMT
Hello! Bought the ODBEleven Pro Version to be able to read the error codes corresponding with the yellow error indications concerning AdBlue (urea liquid) that are present on the dashboard of my VW Sharan 4Motion 2013. But after scanning the ODBEleven did not present any such error codes, the engine e.g. was flawless. Is there anything wrong with me or missing functionality of the ODBEleven? By the way, I bought the Pro version, but Pro functionality cannot be activated since the system claims that the activation code is already used by another account. Looking forward to responses! OlaSharan
|
|
|
Post by Thirsty on Aug 17, 2019 9:02:52 GMT
For the PRO code write the support and show them you're invoice etc. In 99% of the cases OBDeleven showed me all fault codes :/
|
|
|
Post by olasharan on Aug 23, 2019 11:57:01 GMT
Hello! Thx, will contact support! Concerning reading SCR (or adBlue) error codes I suspect that after replacing the NOx sensor, something I did, the system (ECU) notices that the problem was addressed and hence deletes the error code(s) (accessible by the ODBeleven) but leaves the message on the display until it can verify that exhaust gases really are OK. In my case I had to drive around 30 km before the yellow error message on the display all of a sudden on the highway disappeared. The supplier of the NOx sensor XENON4U (https://xenons4u.co.uk/ and xenons4u.co.uk/vw-audi-03l907807r-5wk96737-nox-sensor.html) informed me that a new NOx sensor needs to be calibrated before it can work correctly and that this calibration may require something like 30 km.
|
|