firmware updates while wired up to an engine?

[tomiata]

Is it dangerous to do firmware updates while wired up to an engine? I saw a warning in the ms documents about be sure to disconnect injectors or coils while doing an update.

Similarly, if the engine type is reset to default, Ford Aspire whatever, after a firmware update, if you are wired up to an engine with a different engine type could that do something bad like wiggle signals that might cause damage for a different engine type until the correct engine type is set?

Or should you say always disconnect the ecu when doing an update?

Is it bad that my injectors bounce around when I do a writeconfig command?

[AndreyB]

I'd say yes, it's dangerous to update firmware while the vehicle is powered up. Being plugged into an unpowered vehicle is hopefully not an issue.

With Frankenso you can have the car OFF and I hope it's save to update while powering only the stm32 via USB - since the is no +12 anywhere we should be fine.

With Frankenstein same thing - I hope it's safe as long as +12v is turned off. With the power supply sucking in +5 supplied via USB this means you need to disconnect the power supply.

There are multiple things to be concerned if we are updating the firmware while the vehicle is powered up - one of them is that potentially the config might get reset to the default engine type and worst case scenario some line gets inverted because of that.

TDB Re: writeconfig

[tomiata]

I see there is a new a warning message on the console output about doing "writeconfig" while the ignition switch is on. That is good for safety sake.

In my setup running the java console from my linux laptop, when I turn the key switch off and turn back on, Discovery reboots, and I lose my serial connection and have to restart the java console too, which is a pain.

Is there a way to kill the engine from a console command so I can stop it to change a setting?

And is there any safe way to power Discovery to do a writeconfig without removing it or unplugging the ECU harness?

Thanks!

[AndreyB]

Code: Select all

static void stopEngine(void) {
	// todo
}

this sits like that since November, 8 when I've realized that my fancy CRANK button on the radiator is lacking 'kill it already' functionality. I guess time to implement this command this weekend.

using a TTL dongle - or the board with a TTL chip would kind of help since TTL would be powered by laptop (not the car) so rebooting ARM chip does not break connectivity.

Please also note that 12v-against-USB power conflict was a suspect in http://rusefi.com/forum/viewtopic.php?f=3&t=662&start=70#p12381 but that was until another one got fried without USB power so who knows.

[tomiata]

I guess that doing a disable injectors would kill the engine? Is there any problem doing it that way?

[AndreyB]

I guess that doing a disable injectors would kill the engine? Is there any problem doing it that way?

Yes, this would kill the engine while the firmware is active. The plan for stopengine is to rill fuel and spark for 3 seconds.

What's going on while you are updating the firmware is still an open question.