|
Title: Readiness Post by: dilly on March 01, 2019, 04:57:32 PM i made another post but i don't think it is appropriate now to post in the reverse engineering since now it is turning towards the noob side
previous topic in Reverse engineering just thought i would share my recent findings just messing with the codewords etc in my file. point being is that following the s4 wiki and the readiness thread here, i could not get the monitors to run (O2 sensor, Evap, SAI) after making these changes all but SAI (assuming because cwsls is zero'd. will set to 1 and update thread) ran and completed. (being that evap and sai valves relays etc are unplugged) don't know if it matters for much of you but if it is in your damos why not try it. below are the changes i made on top of following the wiki and other readiness thread in this forum Code: CDTES Codeword: turn off tank venting diagnosis (EURO-Coding), CD..=0 ->no Dia - Codewort Tankentlüftungsdiagnose abschalten (EURO-Codierung), CD..=0 ->keine Dia changed from 0.00 (0x00) to 1.00 (0x01). I changed CWSLS back to 1 and zeroed below codewords but SAI still says abort while trying to run the test in vcds Code: CWDSLSA changed from 10.00 (0x0A) to 0.00 (0x00). everything else runs either on it's own or completes via vcds method i dont think in NY the inspection machine cares about the unsupported monitors but if it got scanned as supported last year and says unsupported this year then there might be a red flag thrown up. Title: Re: Readiness Post by: Risky on March 01, 2019, 08:14:51 PM When a vin is flagged it only comes back to the inspector. The auditor just comes by and looks at tapes to make sure no one cold scanned it. The auditor sometimes never even shows up. Sometimes completely stock cars get flagged.
Edit: another important piece of info. is that when u try to push a car threw with monitors unsupported you still can fail. This is because there is an error that pops up, now it is the inspectors choice to pass it or not, it's there choice to either cancel or continue. So if you have monitors that are unsupported I recommend going to someone you know and know what they're doing. Make sure they are actually unsupported though (example: all ready in vcds but unsupported via obd.) Title: Re: Readiness Post by: _nameless on March 01, 2019, 08:55:12 PM Or just make an actually show ready
Title: Re: Readiness Post by: Risky on March 01, 2019, 09:26:52 PM Title: Re: Readiness Post by: dilly on March 01, 2019, 10:47:35 PM When a vin is flagged it only comes back to the inspector. The auditor just comes by and looks at tapes to make sure no one cold scanned it. The auditor sometimes never even shows up. Sometimes completely stock cars get flagged. Edit: another important piece of info. is that when u try to push a car threw with monitors unsupported you still can fail. This is because there is an error that pops up, now it is the inspectors choice to pass it or not, it's there choice to either cancel or continue. So if you have monitors that are unsupported I recommend going to someone you know and know what they're doing. Make sure they are actually unsupported though (example: all ready in vcds but unsupported via obd.) yeah that is what i figured because with the file that was on my ecu i believe most monitors were set to unsupported and i watched the error pop up car flagged for review or something. we scanned it again and it passed. buddy told me oh well he will probably get a call in a few days about it. (let's say he has been in contact a few times with the state lol) and i also understand that in ny any car 2001 and up can have 1 monitor failed but ideally i want all to run and complete. now the last thing i can think of messing with SAI is CWKONABG. as it is set to stock at 5, i could set it to 1 and see what it does. but would this interfere with the monitor running since this codeword tells the ecu the install state of cats and sai? thanks for the info guys |