| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 23 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 46:55:03 |
| Calls: | 583 |
| Files: | 1,138 |
| Messages: | 111,071 |
On 6/7/2025 1:44 pm, Noddy wrote:
The only device
On 6/07/2025 2:15 pm, Xeno wrote:
On 6/7/2025 1:44 pm, Noddy wrote:
The only device
<bullshit flushed>
Shut the fuck up.
Don't for a second think that I am even *remotely* interested in
conversing with the likes of a contemptible cunt like you. The *only*
reason I've spoken to you over the last couple of days was to set you up
so you could fall all over yourself in reply, and that worked
spectacularly well. Your ego simply wouldn't allow you to shut your
trap, and in the process you've been shown up to be *exactly* what you are:
A shit talking attention whore who operates *way* above his pay grade.
You have been shown to be a liar about evidence. You have been shown to
be a liar about knowledge. You have been shown to be a liar about experience, and you have been shown to be a liar about your previous comments. You have been profoundly humiliated, and deservedly so.
Do not reply to my comments ever again, you fucking pathetic heap of
shit. You're damaged goods. You're mentally deficient, and I have no interest whatsoever in anything you have to say.
If you had an *ounce* of self respect you would simply just fuck off,
and for good. Not just for a week and then reappear as someone else like
you did when you were Krypsis.
If there is any Karma at all in this world, then you will throw yourself under a train.
On 6/07/2025 1:21 pm, Clocky wrote:
On 5/07/2025 5:32 pm, Noddy wrote:
Bzzzt, that's a generic generic OBD2 description. The GM OBD2
employed by GM including Holden 25+ years permanently stores
history codes along with a whole bunch of information.
*Jesus* you are an utter fuckwit. Holden never used OBD2 until
the very last models. VE onwards.
OMG what the fuck are you on about now you ridiculous clueless
halfwit? OBD2 was introduced with the VT so that would be 1998 with
the introduction of the 5.7L V8. That's over 25 years ago!
Jesus you're fucking clueless :)
OBD2 compliance wasn't mandatory in Australia until January 1 2006, and
prior to this manufacturers used OBD1 or their own specific format
system which is exactly what Holden did. The First Commodore model
released in Australia that was truly OBD2 compatible was the VE model.
Prior to this their compliance was his and miss depending on the model/ engine combination.
Everyone loves quoting AI at the moment, including you, so suck on this:
Holden introduced OBD2 compliant models starting in 2006 for
vehicles manufactured in Australia and New Zealand. Specifically,
all Holden vehicles manufactured after January 1, 2006, were
required to be OBD-II compliant. While some earlier models may have
been compliant, it varied by manufacturer and model.
Key points:
Mandatory Compliance: All Holden vehicles manufactured in Australia
and New Zealand after January 1, 2006, were required to be OBD-II
compliant.
Pre-2006 Models: Some earlier Holden models might have
been OBD-II compliant, but it was not a standard requirement and
varied by vehicle.
Specific Models: For example, the Commodore from
the VZ series was OBD2 compliant from 2006, as were the Astra,
Barina, Caprice, and Captiva from 2006 or later. The Colorado and
Crewman were compliant from 2007 or later.
That you claim that you were leading hand/Foreman at a Holden dealership
yet seem to be as blissfully unaware of this as you were about
Windscreen construction is staggering enough, but you seem to be content
to totally ignore the fact that *all* of this is completely irrelevant
to the *fact* that once a DTC has gone through the minimum number of restarts without the fault being detected the code is permanently
deleted and *cannot* randomly be retrieved weeks later.
No matter *what* scan tool you're using :)
On 6/07/2025 2:15 pm, Xeno wrote:
On 6/7/2025 1:44 pm, Noddy wrote:
The only device
<bullshit flushed>
Shut the fuck up.
Don't for a second think that I am even *remotely* interested in
conversing with the likes of a contemptible cunt like you. The *only*
reason I've spoken to you over the last couple of days was to set you up
so you could fall all over yourself in reply, and that worked
spectacularly well. Your ego simply wouldn't allow you to shut your
trap, and in the process you've been shown up to be *exactly* what you are:
A shit talking attention whore who operates *way* above his pay grade.
You have been shown to be a liar about evidence. You have been shown to
be a liar about knowledge. You have been shown to be a liar about experience, and you have been shown to be a liar about your previous comments. You have been profoundly humiliated, and deservedly so.
Do not reply to my comments ever again, you fucking pathetic heap of
shit. You're damaged goods. You're mentally deficient, and I have no interest whatsoever in anything you have to say.
If you had an *ounce* of self respect you would simply just fuck off,
and for good. Not just for a week and then reappear as someone else like
you did when you were Krypsis.
If there is any Karma at all in this world, then you will throw yourself under a train.
On 6/7/2025 1:59 pm, Noddy wrote:
On 6/07/2025 1:21 pm, Clocky wrote:
On 5/07/2025 5:32 pm, Noddy wrote:
Bzzzt, that's a generic generic OBD2 description. The GM OBD2
employed by GM including Holden 25+ years permanently stores
history codes along with a whole bunch of information.
*Jesus* you are an utter fuckwit. Holden never used OBD2 until
the very last models. VE onwards.
OBD2 was present on previous models, it just wasn't mandatory.
OMG what the fuck are you on about now you ridiculous clueless
halfwit? OBD2 was introduced with the VT so that would be 1998 with
the introduction of the 5.7L V8. That's over 25 years ago!
Jesus you're fucking clueless :)
OBD2 compliance wasn't mandatory in Australia until January 1 2006, and
Nobody said it was mandatory, just that it was *introduced* on the VT.
OBD2 became mandatory in the US in 1996. GM knew it would become
mandatory in Australia in time so began putting it on cars here *before*
it became mandatory. That way, industry would be prepared for it. For
sure, I did a course on OBD2 *before* 2001 because OBD2 was already
present on some Australian vehicles by then.
A good point to make here is that, in the VT Commodore, the 5.7L Gen III
LS1 V8 was first used. This engine was a direct transplant from the US
and, as such, it was LEV certified. The LSII engines were LEV certified
from ~2001-2004. That means they would have been OBD2 compliant, even
here in Australia even though it wasn't mandatory.
prior to this manufacturers used OBD1 or their own specific format
system which is exactly what Holden did. The First Commodore model
released in Australia that was truly OBD2 compatible was the VE model.
Prior to this their compliance was his and miss depending on the model/
engine combination.
Compliant and compatible, learn the difference. A lot of engines in Australia were OBD2 compatible but local laws did not require
compliance. Holden, for one, just used the ECMs that were used in *OBD2 compliant US engines. Do you seriously think that GM would create a
separate ECM system just for Australia when it can simply use OBD2
compliant systems in a small market, like Australia, where compliance
isn't an issue?
Everyone loves quoting AI at the moment, including you, so suck on this:
Holden introduced OBD2 compliant models starting in 2006 for
Again, learn the difference between compliant and compatible.
vehicles manufactured in Australia and New Zealand. Specifically,
all Holden vehicles manufactured after January 1, 2006, were
required to be OBD-II compliant. While some earlier models may have
been compliant, it varied by manufacturer and model.
Key points:
Mandatory Compliance: All Holden vehicles manufactured in Australia
and New Zealand after January 1, 2006, were required to be OBD-II
compliant.
Were *required* to be OBD-II compliant after January 1, 2006.
Were *already* OBD-II *compatible* long *before* January 1, 2006
Pre-2006 Models: Some earlier Holden models might have
been OBD-II compliant, but it was not a standard requirement and
varied by vehicle.
There was no law in Australia to be compliant with - BUT - many models
*in Australia* were already compatible with US OBD-II LEV laws.
Specific Models: For example, the Commodore from
the VZ series was OBD2 compliant from 2006, as were the Astra,
Barina, Caprice, and Captiva from 2006 or later. The Colorado and
Crewman were compliant from 2007 or later.
Still don't get the difference between compliant and compatible Darren?
That you claim that you were leading hand/Foreman at a Holden
dealership yet seem to be as blissfully unaware of this as you were
about Windscreen construction is staggering enough, but you seem to be
content to totally ignore the fact that *all* of this is completely
irrelevant to the *fact* that once a DTC has gone through the minimum
number of restarts without the fault being detected the code is
permanently deleted and *cannot* randomly be retrieved weeks later.
No matter *what* scan tool you're using :)
Houston, we have a problem - and the problem is YOU, Darren. More to the point, it's your bullshit story. You claimed the owner had to clear the codes in order to keep driving the vehicle. If the vehicle becomes undrivable, typically by being placed into *Limp-In Mode*, code clearing will not work. The reason - when misfires have triggered a DTC severe
enough to cause limp-in mode, the DTCs will be *permanent DTCs* and
cannot be cleared by the code reader. Even if the vehicle is returned to driveability, the codes will remain as P Codes and can only be removed
by the ECM when 40 successful *consecutive* drive cycles have been completed. BTW, YOU came up with the number 40, and you are correct,
it's one of the few things you seem to understand from your Googling. In
my experience, an engine suffering random misfires will not make 40 consecutive drive cycles without a recurrence - and every recurrence
resets the drive cycle requirement back to 40.
That's just *one* of the many reasons why I know your misfire story is bullshit. The PDTCs will always remain and be readable in any decent
OBD2 compliant code reader and scanner.
On 8/07/2025 12:26 pm, Xeno wrote:
On 6/7/2025 1:59 pm, Noddy wrote:
On 6/07/2025 1:21 pm, Clocky wrote:
On 5/07/2025 5:32 pm, Noddy wrote:
Bzzzt, that's a generic generic OBD2 description. The GM OBD2
employed by GM including Holden 25+ years permanently stores
history codes along with a whole bunch of information.
*Jesus* you are an utter fuckwit. Holden never used OBD2 until
the very last models. VE onwards.
OBD2 was present on previous models, it just wasn't mandatory.
OMG what the fuck are you on about now you ridiculous clueless
halfwit? OBD2 was introduced with the VT so that would be 1998 with
the introduction of the 5.7L V8. That's over 25 years ago!
Jesus you're fucking clueless :)
OBD2 compliance wasn't mandatory in Australia until January 1 2006, and
Nobody said it was mandatory, just that it was *introduced* on the VT.
OBD2 became mandatory in the US in 1996. GM knew it would become
mandatory in Australia in time so began putting it on cars here
*before* it became mandatory. That way, industry would be prepared for
it. For sure, I did a course on OBD2 *before* 2001 because OBD2 was
already present on some Australian vehicles by then.
A good point to make here is that, in the VT Commodore, the 5.7L Gen
III LS1 V8 was first used. This engine was a direct transplant from
the US and, as such, it was LEV certified. The LSII engines were LEV
certified from ~2001-2004. That means they would have been OBD2
compliant, even here in Australia even though it wasn't mandatory.
prior to this manufacturers used OBD1 or their own specific format
system which is exactly what Holden did. The First Commodore model
released in Australia that was truly OBD2 compatible was the VE model.
Prior to this their compliance was his and miss depending on the model/
engine combination.
Compliant and compatible, learn the difference. A lot of engines in
Australia were OBD2 compatible but local laws did not require
compliance. Holden, for one, just used the ECMs that were used in
*OBD2 compliant US engines. Do you seriously think that GM would
create a separate ECM system just for Australia when it can simply use
OBD2 compliant systems in a small market, like Australia, where
compliance isn't an issue?
Everyone loves quoting AI at the moment, including you, so suck on this: >>>
Holden introduced OBD2 compliant models starting in 2006 for
Again, learn the difference between compliant and compatible.
vehicles manufactured in Australia and New Zealand. Specifically,
all Holden vehicles manufactured after January 1, 2006, were
required to be OBD-II compliant. While some earlier models may have
been compliant, it varied by manufacturer and model.
Key points:
Mandatory Compliance: All Holden vehicles manufactured in Australia
and New Zealand after January 1, 2006, were required to be OBD-II
compliant.
Were *required* to be OBD-II compliant after January 1, 2006.
Were *already* OBD-II *compatible* long *before* January 1, 2006
Pre-2006 Models: Some earlier Holden models might have
been OBD-II compliant, but it was not a standard requirement and
varied by vehicle.
There was no law in Australia to be compliant with - BUT - many models
*in Australia* were already compatible with US OBD-II LEV laws.
Specific Models: For example, the Commodore from
the VZ series was OBD2 compliant from 2006, as were the Astra,
Barina, Caprice, and Captiva from 2006 or later. The Colorado and
Crewman were compliant from 2007 or later.
Still don't get the difference between compliant and compatible Darren?
That you claim that you were leading hand/Foreman at a Holden
dealership yet seem to be as blissfully unaware of this as you were
about Windscreen construction is staggering enough, but you seem to
be content to totally ignore the fact that *all* of this is
completely irrelevant to the *fact* that once a DTC has gone through
the minimum number of restarts without the fault being detected the
code is permanently deleted and *cannot* randomly be retrieved weeks
later.
No matter *what* scan tool you're using :)
Houston, we have a problem - and the problem is YOU, Darren. More to
the point, it's your bullshit story. You claimed the owner had to
clear the codes in order to keep driving the vehicle. If the vehicle
becomes undrivable, typically by being placed into *Limp-In Mode*,
code clearing will not work. The reason - when misfires have triggered
a DTC severe enough to cause limp-in mode, the DTCs will be *permanent
DTCs* and cannot be cleared by the code reader. Even if the vehicle is
returned to driveability, the codes will remain as P Codes and can
only be removed by the ECM when 40 successful *consecutive* drive
cycles have been completed. BTW, YOU came up with the number 40, and
you are correct, it's one of the few things you seem to understand
from your Googling. In my experience, an engine suffering random
misfires will not make 40 consecutive drive cycles without a
recurrence - and every recurrence resets the drive cycle requirement
back to 40.
That's just *one* of the many reasons why I know your misfire story is
bullshit. The PDTCs will always remain and be readable in any decent
OBD2 compliant code reader and scanner.
Don't waste your time. He's an idiot who will just spin his incompetence into something else.
You can't educate him. It's impossible. He's as ignorant as he is stupid which is why he keeps tripping up when fabricating these nonsense stories.
He'll never realise how fucking stupid he looks right now.