ca smog legal cam
#41
I just think anything with any kind of rough idle will alert the tester, even if it "sniffs" clean. Now that they only do visual and plug into the OBD2 port, hard to say if they fail any aftermarket tune. GM dealers reflash stuff all the time, and I would think a GOOD tuner could make a smooth tune "transparent".
How ever the OEMs did not keep the best records as in some cases when you look on GM vehicles prior to 2006 it shows calibrations but no known check sum.
The C.A.R.B. smog program is going to look for things like Custom Operating Systems where the calibration number changes. Or like some aftermarket tuning equipment puts an extra character when it re flashes it's canned tune.
My understanding is that currently, it takes a snapshot from your vehicle's PCM/ECM of the calibration as well as the some other info like the VIN that is stored on the module.
It looks for the Readiness monitor status and probably when the last time the codes were cleared.
What I don't know is how they determine if a calibration is correct for your vehicle and if or when it fails you for it. Is it done on the spot or does someone review the information and look for anomalies?
I almost positive a COS operating system would fail or DSP 5 tune would fail right away.
But what if you flashed say a flex fuel operating system into a non flex fuel vehicle and they both happened to be the same year?
Or what if you put an 05 operating system in an 03 vehicle and corrected the Vin number.
#42
I just think anything with any kind of rough idle will alert the tester, even if it "sniffs" clean. Now that they only do visual and plug into the OBD2 port, hard to say if they fail any aftermarket tune. GM dealers reflash stuff all the time, and I would think a GOOD tuner could make a smooth tune "transparent".
#43
My 2000 has a motor swap from a 2001. The vehicle was referred to Bureau of Automotive Repair and they certified the swap with a sticker noting the change in emissions equipment and the VIN. This was all done by the previous owner.
#44
2000 and up cars are not sniffed at all - only visual and readiness monitor check. What fails aftermarket tunes is manipulation of the readiness monitors. Say for example the heated catalyst monitor, which won't set with long tube headers, is often programmed to not run, meaning it won't set a DTC, but it will always show as ready. The tech will reset the monitors so none of them should be set to ready when the let is turned back on. If any are ready, it's an automatic fail.
#45
Your 2000 what??? has a 2001 motor From????
#46
2000 and up cars are not sniffed at all - only visual and readiness monitor check. What fails aftermarket tunes is manipulation of the readiness monitors. Say for example the heated catalyst monitor, which won't set with long tube headers, is often programmed to not run, meaning it won't set a DTC, but it will always show as ready. The tech will reset the monitors so none of them should be set to ready when the let is turned back on. If any are ready, it's an automatic fail.
#47
So out of curiosity if you have a 224 cam with 113 or 114 lsa, which is a pretty mild cam, and the tuner just tunes the timing and air/fuel mapping but leaves all the emission systems alone. This will not pass smog? I find this hard to believe. I'm not a guru at this smog stuff though.
#48
The 224 might be a little too lumpy in the idle dept. A rough idle means sloppy firing at low RPM, which might set off a code or two (JUST speculating here).
I'm learning about this stuff too, being a fellow Californiano.
I'm learning about this stuff too, being a fellow Californiano.
#49
#50
#52
Easiest way to check the tune, is the checksum.
Common technique in ANY kind of programming... to identify the program, you just add up the binary value of every word in the program, and compare it to the "gold standard" whatever that might be in the particular instance. Regardless, it INSTANTLY tells you if there's an error (most common use of it) or deliberate alteration. Doesn't have to be "add"... you can byte-wise XOR, binary shift (=shift if the bit is 1, not if it's 0, compare the result byte after going through the entire program this way), and so on. Maybe even do more than one such algorithm because even if a REAL SMART programmer came along and knew what you were going to do, it's basically impossible to make it pass if multiple methods are used.
Kind of a no-brainer in the embedded processor world for finding tampering.
Common technique in ANY kind of programming... to identify the program, you just add up the binary value of every word in the program, and compare it to the "gold standard" whatever that might be in the particular instance. Regardless, it INSTANTLY tells you if there's an error (most common use of it) or deliberate alteration. Doesn't have to be "add"... you can byte-wise XOR, binary shift (=shift if the bit is 1, not if it's 0, compare the result byte after going through the entire program this way), and so on. Maybe even do more than one such algorithm because even if a REAL SMART programmer came along and knew what you were going to do, it's basically impossible to make it pass if multiple methods are used.
Kind of a no-brainer in the embedded processor world for finding tampering.
#53
I also have a pair of JBA short tube headers CA legal for sale if you'd like them. new never installed. I wanted to be smog compliant but hey, you only live once.[/QUOTE]
I’m interested in your headers if still available. Send me a PM I’m in the LA area as well, thanks!
I’m interested in your headers if still available. Send me a PM I’m in the LA area as well, thanks!
#54
Easiest way to check the tune, is the checksum.
Common technique in ANY kind of programming... to identify the program, you just add up the binary value of every word in the program, and compare it to the "gold standard" whatever that might be in the particular instance. Regardless, it INSTANTLY tells you if there's an error (most common use of it) or deliberate alteration. Doesn't have to be "add"... you can byte-wise XOR, binary shift (=shift if the bit is 1, not if it's 0, compare the result byte after going through the entire program this way), and so on. Maybe even do more than one such algorithm because even if a REAL SMART programmer came along and knew what you were going to do, it's basically impossible to make it pass if multiple methods are used.
Kind of a no-brainer in the embedded processor world for finding tampering.
Common technique in ANY kind of programming... to identify the program, you just add up the binary value of every word in the program, and compare it to the "gold standard" whatever that might be in the particular instance. Regardless, it INSTANTLY tells you if there's an error (most common use of it) or deliberate alteration. Doesn't have to be "add"... you can byte-wise XOR, binary shift (=shift if the bit is 1, not if it's 0, compare the result byte after going through the entire program this way), and so on. Maybe even do more than one such algorithm because even if a REAL SMART programmer came along and knew what you were going to do, it's basically impossible to make it pass if multiple methods are used.
Kind of a no-brainer in the embedded processor world for finding tampering.
#55
Question is: what values do they actually have (if they have them at all), what happens if they see the values change...?
#56
Joined: Nov 2003
Posts: 6,170
Likes: 219
From: Wichita KS / Rancho San Diego
It would be interesting to hear from more guys with modded tunes who have been tested. I thought they just tested for emissions-related codes and emissions components that showed "not ready" (or is it "ready" per earlier posts?).
So for instance, my M6 Formula which only has skip shift tuned out and altered timing tables might pass. But leaving aside visuals, would my 2000 A4 with 2002 OS and massively modified tables with emissions DTCs set to "not report" pass?
So for instance, my M6 Formula which only has skip shift tuned out and altered timing tables might pass. But leaving aside visuals, would my 2000 A4 with 2002 OS and massively modified tables with emissions DTCs set to "not report" pass?
#57
Also there can be factory software updates that may or may not be installed, since that's up to the owner. I know there was one for 2000. So different checksums possible for the same car.
#58
It would be interesting to hear from more guys with modded tunes who have been tested. I thought they just tested for emissions-related codes and emissions components that showed "not ready" (or is it "ready" per earlier posts?).
So for instance, my M6 Formula which only has skip shift tuned out and altered timing tables might pass. But leaving aside visuals, would my 2000 A4 with 2002 OS and massively modified tables with emissions DTCs set to "not report" pass?
So for instance, my M6 Formula which only has skip shift tuned out and altered timing tables might pass. But leaving aside visuals, would my 2000 A4 with 2002 OS and massively modified tables with emissions DTCs set to "not report" pass?
#59
According to the emissions sticker on my 2000 TA, it doesn't list the EGR as an emmisions device. So removing that and tuning it out whouldn't fail a visual inspection. Maybe it changes a computer setting on 98-2000 and is able to be detected. I'm not sure.
#60
I’m interested in your headers if still available. Send me a PM I’m in the LA area as well, thanks![/QUOTE]