On Monday, 2 October 2023 at 10:02:30 UTC+11, Clocky wrote:
> On 28/09/2023 7:04 pm, Noddy wrote:
> > On 28/09/2023 8:34 pm, Keithr0 wrote:
> >> On 28/09/2023 6:19 pm, Xeno wrote:
> >
> >>>> By what means does the ECU tell the difference between the problem
> >>>> being fixed or just going away for the appropriate number of cycles.
> >>>
> >>> Darren story indicates that the MIL didn't go away, the owner erased
> >>> it because it *annoyed him*. Remember?
> >>>
> >>> The story has more holes than a colander and is currently suffering
> >>> story drift as Darren gets *schooled*.
> >>>
> >> That is not an answer to the question asked.
> >
> > That's right, because (a) that's not what I said, and (b) he's trying to
> > avoid giving a detailed answer because he doesn't *have* one :)
> >
> > Just to remind the clueless warriors amongst us who like to reinvent
> > history, the car in question was a 2012 VE Clubsport R8, and it had a
> > random intermittent fault that reported a "cylinder misfire" (P1303 if I
> > remember correctly). The owner kept a bluetooth dongle permanently
> > plugged into the OBD2 port, and when the fault occurred he would make a
> > note of what it was and then clear the codes which extinguished the
> > check engine light. According to him no other faults were ever
> > recorded, and the fault had happened more than once it would go for
> > weeks at a time without it ever occurring.
> >
> > Now, to anyone with any actual hands on *experience* (as opposed to the
> > make believe "transferred" kind :) that in itself was enough to tell you
> > all you needed to know with regard to the usefulness of the information
> > which could be gleaned from the vehicle's ECU, and for those who don't
> > know what I'm talking about I shall explain.
> *You* don't know what you're talking about and you're adjusting your
> story to try and attempt to weasel your way out of your predicament.
> >
> > When the owner presented the car to me it was for a basic oil & filter
> > change, and while it was here he asked if I could "take a look" at it
> > regarding the cylinder misfire. I knew from asking him when it last
> > occurred that it was only a pending code
> A "pending code" for a cylinder misfire? LOL, you goose.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Just in case you *missed* my comment the first time around, what is your problem with a *pending* code on a misfire??.
Inquiring minds need to know!.

> that had been generated, and I
> > *also* knew that given that it was considerably more that a couple of
> > weeks since that time that the ECU had seen the minimum number of fault
> > free warm up cycles and that any trace of the fault in the ECU was long
> > gone which was precisely why I didn't bother hooking up my scan tool as
> > it would have told me nothing.
> This is where you take the car to an experienced mechanic. Your bullshit
> above might sound good to someone who knows even less than you but it is
> absolute *bullshit*!
>
> Codes are stored and *especially* misfire codes are stored with captured
> data at the point the code occurred including how many times the misfire
> occurred, which cylinder, how long since the last ignition cycle (iow
> startup) as well as ignition cycles since etc etc etc.
>
> The fact you admit that you didn't plug in a diagnostic scan tool and
> reached for part swapping which is the *worst* option when *everything*
> you need to diagnose the fault with 100% certainty is already at hand
> and can easily be determined by plugging in the scan tool just proves
> how fucking incompetent you are.
>
> You have absolutely no idea about any of this stuff and you bluff and
> bluster make believe story doesn't fly one little bit.