Shiv: there are rumors about SMART not being compatible with other re-flashes!
Evolved Member
iTrader: (20)
Joined: Mar 2003
Posts: 4,941
Likes: 0
From: Danville/Blackhawk, California
Originally Posted by juyanith
Bump for Zeus.
I'm really curious about this as well. I don't see why the Xede wouldn't be able to adjust the parameters on any flash, but I think Zeus raises some valid questions. I'm particularly interested in the one about the OBD-II reader. I don't live in an emission testing state, but I'd still hate to have the port plugged just to cover up the P0300 code. Especially since I've never had that problem with my evo. Zeus, you mentioned "that people have had problems running SMART on top of custom flashes", could you be more specific? Feel free to PM me if you'd prefer.
I'm really curious about this as well. I don't see why the Xede wouldn't be able to adjust the parameters on any flash, but I think Zeus raises some valid questions. I'm particularly interested in the one about the OBD-II reader. I don't live in an emission testing state, but I'd still hate to have the port plugged just to cover up the P0300 code. Especially since I've never had that problem with my evo. Zeus, you mentioned "that people have had problems running SMART on top of custom flashes", could you be more specific? Feel free to PM me if you'd prefer.
The purpose of the C-Reader is to supress the P0300 problem that some cars experience in stock form. The more "timing gymnastics" you do with the ECU, the more P0300-prone the car gets. With the SMART timing functions fully active (ie. with timing being added in during no knock conditions), there is more of a chance for throwing the P0300 code. Again, some cars will not ever throw a car. But some will. So the C-Reader is viewed as an inexpensive precaution. One that helps on the diagnosis front as well.
As for some Flashes not being compatible with the SMART system, I don't know if that is true. I've run into one customer who is running a Dynoflash with the SMART system. When adding timing during no knock conditions (something that the baselines SMART timing tables that I posted up DONT do yet), it would immediatley throw a P0300 code. Of course, no C-Reader was installed at the time so it is likely the system would perform as it should once fully set up. I have not seen any car with any of our Flashes so eager to throw such a code. But these results aren't very conclusive to say the least. Could have been just one isolated incidence. I'm in the process of updating the available SMART timing tables to include realtime timing advance instead of just retard.
Shiv
Last edited by shiv@vishnu; Aug 9, 2005 at 01:38 PM.
I must be one of the lucky ones. I have an older XEDE, have gone through numerous firmware updates, upgraded to a GT3076, and have only had 1 P0300 code pop up ever. Hopefully, when I install my SMART stuff, I will not have a problem either.
Originally Posted by jj_008
I must be one of the lucky ones. I have an older XEDE, have gone through numerous firmware updates, upgraded to a GT3076, and have only had 1 P0300 code pop up ever. Hopefully, when I install my SMART stuff, I will not have a problem either.
I too have an old XEDE - As soon as I went catless, I do the 0420 & 0300 All the Time
To quote Zappa "It's a way of life" 
Originally Posted by shiv@vishnu
The purpose of the C-Reader is to supress the P0300 problem that some cars experience in stock form. The more "timing gymnastics" you do with the ECU, the more P0300-prone the car gets. With the SMART timing functions fully active (ie. with timing being added in during no knock conditions), there is more of a chance for throwing the P0300 code. Again, some cars will not ever throw a car. But some will. So the C-Reader is viewed as an inexpensive precaution. One that helps on the diagnosis front as well.
As for some Flashes not being compatible with the SMART system, I don't know if that is true. I've run into one customer who is running a Dynoflash with the SMART system. When adding timing during no knock conditions (something that the baselines SMART timing tables that I posted up DONT do yet), it would immediatley throw a P0300 code. Of course, no C-Reader was installed at the time so it is likely the system would perform as it should once fully set up. I have not seen any car with any of our Flashes so eager to throw such a code. But these results aren't very conclusive to say the least. Could have been just one isolated incidence. I'm in the process of updating the available SMART timing tables to include realtime timing advance instead of just retard.
Shiv
As for some Flashes not being compatible with the SMART system, I don't know if that is true. I've run into one customer who is running a Dynoflash with the SMART system. When adding timing during no knock conditions (something that the baselines SMART timing tables that I posted up DONT do yet), it would immediatley throw a P0300 code. Of course, no C-Reader was installed at the time so it is likely the system would perform as it should once fully set up. I have not seen any car with any of our Flashes so eager to throw such a code. But these results aren't very conclusive to say the least. Could have been just one isolated incidence. I'm in the process of updating the available SMART timing tables to include realtime timing advance instead of just retard.
Shiv
Zeus, it occurs to me that even if you get P0300s with SMART, you could load your "safe" Xede map and remove the C-Reader when you go to get tested. The only issue would be if (for some reason) you couldn't use SMART on top of your existing ECU flash because it won't function properly. From what Shiv says that doesn't seem likely, but the only way to know for sure would be to try it.
