you asked, i just located it.

 

I know. I forgot to say thanks

Lucas

 

anything for you guys

 

Subscribing. Interesting to say the least.

 

Yes it IS in direct conflict!
See, to really make you understand WHY there can't be a freeze frame in the ECM with a stock software from Smarty, I'd need to explain you exactly what Smarty does. I think you understand why that ain't going to happen.

Nope that's not logic, that's an asumption!
Let me take the example of the DRB/StarScan. When those write an update into an ECM they whipe: out all codes, freeze frames, trip data, key counts, secret key, key counts.

Well Smarty whipes out only the "bad" but keeps to good.....

Clear as mud?

Marco

 

im not trying to argue either way ...im asking a question really, If he threw that code when his truck was stock (mine has thrown lots of codes stock for no reason) is there a way that the computer freez framed that(in stock form) and kept it stored some how? And now that smarty brings that exact code up it now looks like the smarty caused it even though it was from a long time ago when the truck was stock???

 

subscribed!!!

 

subscribed ...

I don't know about anyone else but i'm impressed when a vendor defends / explains his product in a public forum ...

takes a big set ... thanks Marco

 

That's the great thing about Marco. No matter what forum, website, etc. He gets on and answers questions. Up front to the point. Then throw in the countless off the wall requests we give him and he delivers. Keep up the good work Marco. BTW: Ordering another one for wife's '06 tomorrow.

 

Marco,
I think it would help if you could explain how user error while reloading Smarty SW would generate/retain codes/freeze frames.

Also, not all scanners have been created equally; do you have enough info to tell us which scantools read correctly and which don't?

 

Playing devils advocate here, that statement makes no sense and smacks of avoiding the issue. Irregardless of what you claim, here is what is actually happening:

1. Code and FF set with Smarty loaded.

2. Smarty unloaded.

3. Code and FF still present

(White97GTVert correct this if I have misinterpreted)

Assumption: code and FF is present with operating paramters that could possibly indicate there was a device that woud constitute warranty violation.

This would negate your claim of "undetectability"?

It's pretty "logical" to "assume" there is an issue here. A logical assumption based on observed phenomena is not a SWAG. Enough people accept it and it becomes FACT.

Now, without giving away trade secrets would you please explain why this is happening when you claim it cannot?

Can you shed some light, or, are we supposed to take it on "faith" like the Banks claim "will not void your warranty"?

What is the possible cause? Is it the ECU revision? The scanner? Smarty revision? or ??

Marco, I DO NOT have an agenda so do not take this as an attack on your product which I think quite highly of. The hard questions are here for the answering and the world IS watching.

 

My obd scanner shows freeze frame info of any code set or at the time you enter freeze frame. What does the info tell you is wrong?

 

You are correct. What I would really like is for somebody else who has a scantool or even a cheaper code-reader (like an Actron 9175 which I ALSO have and also shows the freeze frame data) to try this on their own truck.

My truck could possibly be an anomaly and then this whole discussion is fruitless.

I don't want this to come off as i am trashin on Smarty or his wonderful creator. If my truck is a fluke then everything is right with the world and the claim of "undetectability" is most certainly and rightly deserved.

I LOVE MY SMARTY! I just don't want the dealer to know about it right now. I guess that won't matter after Christmas comes and I'm dropping a new turbo on the rig anyways. Then its bye-bye warranty anyways.

 

The FF will grab opearational data on the engine, boost, temp, fuel, pressure, etc. By reading this you can tell where the issue is that caused the code and/or whether its just a nuisance code.

The fact that it is there AND the parameters are there is a trigger for STAR to start looking. If the parameters are outside the normal range it is basis for warranty denial.

 

That puts things into a different perspective!
I understood that if there's a code present with a modified SW and then return to stock, the same code ( thus FF) remains present also once back to stock.
That is impossible!

NOW i understand what's the "problem".
A code is set once the programming of the stock software has finished!
That's a completly different scenario!!!
Altough, I've never (*) seen that happen on my own with Smarty, this one I can believe.

(*) I've seen that happen once after an update done to the ECM with a stock software using the StarScan for that update...never with Smarty...

One time out of the many updates on different trucks I've done! I thought it was a glitch but it seems like there are trucks ( or ECM's?) out there who can reproduce that "glitch" quiet frequently!
Hmmmm....

Good news is, the DC tools do not display FF if the code(s) have been cleared.

Marco