Syvecs Forums

For a few weeks my engine has been dying intermittently.

The rev counter will fall to zero and it will lose all power, if I turn the ignition off and then back on it will (with the engine still turning) instantly jump back into life but if I just leave the ignition on it takes 5-15 seconds before it comes back.

Sometimes it will do that 3-4 times a minute and other times it will go 15 mins without cutting out.

So I downloaded the syvecs software and this is what I have found.
With the ignition on but without the engine running with sMon or sMsg running on my laptop you can see the s6 will die intermittently, it will go from connected to disconnected.

If, after it disconnects I turn the ignition off and then back on again it will instantly reconnect but if I just leave the ignition on it will sometimes reconnect right away but usually takes 10-15 seconds before it resets.

I have attached 3 screen shots showing the software reports “last reset cause 5” if I turn off the ignition and then back on and "last reset cause 2" if I leave it to reset itself.

This is not something I have seen before myself, but my first suggestion is to check your wiring, especially the RS232 wiring as some odd things can happen if it gets shorted or looped back, and also poor or intermittent earth wiring.

It might also be prudent to upgrade the firmware (this will require help to reset some of the strategys and put proper values in).

If it's a GP then bench testing on a known good loom would be useful, failing any revelations a strip back to Syvecs might be on the cards.

Paul

Hi Pavlo
Thanks for the reply

I have checked the wiring as best as I can but the fact that it still dies intermittently regardless of having the engine running or not and wiggling any of the wires connected to the ecu does not cause it to die seems to suggest that it is an internal fault inside the ecu. Also it dies much more frequently when first switched on and less as the unit warms up makes it more likely to be an internal fault.

This was recently mapped by Ryan and was perfect for 1000 miles or so and then just started playing up out of the blue so seems unlikely that it is firmware related.

I have included a log of what happens when the ingition is first swithed on as reported by sMsg in case that can shed some light on it.

In that case I would suggest you contact Syvecs for an returns number so it can be looked at, at least the fault is easily repeated.