Obd11: Trouble Codes: Null - Unknown, Intermittent

Discussion in 'Vehicle Faults Warranty Repairs Issues & Problems' started by tomkasz, 18 Mar 2020.

  1. tomkasz

    tomkasz New Member

    Does anyone know what the problem might be?
    It appears to me occasionally, once a month or less.
    There are no other problems.

  2. mmi

    mmi Senior Member VCDS User VIP Member T6 Legend

    Impossible to tell as OBD11 is probably not up to date. Unfortunately the report omits the actual (raw) fault code.

    Has the ECU been updated recently - in year 2019-20? It is EU6 with AdBlue? Your software version 6189 is different what I have collected in the past for CXGB-engines (4209).

    Using OBD11 I got the same null-unknown after an ECU update. Fortunately VCDS did better job interpreting the fault.
    Robert and tomkasz like this.
  3. tomkasz

    tomkasz New Member

    I understand that you mean this part in the cloud, because the client application itself is the latest. Are you suggesting, that OB11 manufacturer has not yet implemented the errors that occur in the latest version of software? The question is whether it wasn't VW that predicted such a situation and returning the error without the code is not caused by the VW programmers and the ECU manufacturer (probably Bosch), as follows.

    This was updated in connection with VW-Gate (in 2019). So now it is less polluting. This is how I initially assumed, referring to the above mentioned information, that it was the implementation of the nitric oxide fixes that caused an error that was not predicted and "implemented". Although I suppose that all of this amendment is only a slight increase in the amount of injected fuel and the operation of the AdBlue injector regardless of the exhaust temperature (all the time). But maybe "by the way" something else has been broken or there is a completely unknown exception.
    What error did the VCDS show in your case?

    I do not have access to VCDS, but I can switch OBD11 to interpretation not according to VW but pure OBD standard, how do you think it can show something more about error?
    mmi likes this.
  4. mmi

    mmi Senior Member VCDS User VIP Member T6 Legend

    Yes, the OBD11 application info is based on data on their server - so the "new" engine is obviously not mapped correctly to data.

    I'm confident (based on VCDS data) that the fault codes are still old existing ones - the OBD11 just gets confused with "new" unidentified engine software version - and unfortunately doesn't even show all what was pulled out.

    Anyways, I'm hopeful that at OBD11 HQ they now have got a couple of alarms of unidentified fault + "new" engines and in due course will provide an update :thumbsup:

    Re generic OBD standard fault codes - I'm afraid nothing is there as they are just common on all brands, mostly emission related. Unless the fault is one of the generic ones, of course.

    My OBD11 null-unknown was reported by VCDS as 27277 - System Voltage P0562 Too Low. The van had been parked for about a month, so quite valid one, though started just fine. So not relevant to yours as in your snapshot the voltage is perfectly normal (mine was below 7 Volts).

    By the way, did you remove date stamp from the data?
    Robert and tomkasz like this.
  5. tomkasz

    tomkasz New Member

    Thank you very much for all your answers.

    I also hope so, I reported this error to them on the official forum.

    Not that it's a full dump without cuts. Such as I could send from application to e-mail (OBD11 function). I understand it's about some kind of coded timestamp, because the date and time itself is on the second full line.

    I also have an older one, similar, but with Polish descriptions. This one is cut off, but I can't tell you why.

    Robert and mmi like this.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice