Waldo, the way I understand this (& this is by no means my area of expertise, so please forgive me if I get some of the specifics wrong - I'm just an 'End tune User', not a tuner or particularly skilled in how they do their job &/or explaining any of that! So the following is just my vaguely educated users way of explaining it all
) is that basically what's happening to your Spyder right now is
precisely why sending your ECU off & getting all the necessary tables etc hard coded is
better than the temporary/adjustable method of flashing it & intercepting & replacing or maybe just adding a preset finangle factor to vary all the control signals your ECU sends ..... :lecturef_smilie:
With the hard coding ECU Upgrade method, all the necessary tables are upgraded/modified so that none of those errors can occur, because the sensors are sending in their readings in & the ECU is responding to them in exactly the manner it
has to due to that hard coding, so there's no errors to report - your engine (well, in this case, my engine, not yours
) just runs a helluva lot better than the techs would normally expect,
[I]IF they even notice it &/or can even tell![/I]
hyea:
However, because you left the flash tune active, your flash tune is still effectively intercepting some or all of those signals & it's then adjusting some outputs &/or causing some components to respond/perform differently to what the ECU expects; &/or it's ignoring either the ECU output or the sensor input and instead of using the ECU's hard coded tables, it forces the operation of the engine to use of the flash tables instead - only the ECU & some/all the other computers can detect this, hence the error messages!! :banghead: Sure, if you turn the flash off & let everything work off the standard ECU tables, you shouldn't get all those error messages; but every time you run off the flash tables instead of the ECU it'll be racking up some of those messages somewhere.... And the Techs can only see them as failures of the engine/control system to run as it/they should in accordance to the hard coded (standard, one size might fit most) tables, cos their s/ware (BUDS or whatever) hasn't been designed to read any of the flash info! :gaah:
That's not necessarily saying the Upgrade flash tables you're running/that you've got are bad, cos a good tuner should be able to create tables that are waaayyy more suited to the majority of
YOUR riding & the conditions you ride in rather than relying on the '
one set of parameters will maybe work OK for most of these engines wherever they are used anywhere around the World' tables that the ECU leaves the factory with, so I'd expect the flash tune you have is still going to be better for your engine within those bounds than the std ECU tune allows... and that's definitely supported by the info in Mike's post above. :thumbup:
BUT, there's a distinct possibility that at times your engine will be generating at least
some of those error messages over time (maybe only when BUDS is connected??
) and the various computers &/or Control Systems
WILL try to '
clear &/or fix' those if at all possible within the bounds of their programming/logic circuits - and who knows
WHAT that'll end up doing in the long run! :dontknow: :shocked:
Apologies if any of the above's not specifically correct or exactly the way it works, but as I said, I'm just an End User who happens to have a fair bit of experience in using these ECU Upgrades & Flash Tunes in their various forms, and the above is simply my attempt at para-phrasing what the experts told me when I had these sort of issues & passing it on/explaining that in terms which most of us should be able to understand about the differences between the 2 methods that are creating this problem for Waldo & maybe also for other users of those 'not hard coded' temporary or switchable flash tunes.... Just Sayin'
