Sounds good
Failed flash can happen for any number of reasons and happens regardless of type of connection, wired or wireless. In fact very little to none has to do with the actual connection itself as issues there are detected way before flashing actually kicks off.
At times people with piggyback devices running on OBD can interfere with both diagnostics and flashing, really anything running over OBD. Examples includes aftermarket valve controllers, tunes such as JB4, etc. Packets of data write acknowledgements can/do get lost if other devices are connected/active so make sure any piggyback devices aren't hooked up or active.
Among other things BM3's flash protocol checks battery voltage level as well as total estimated flash time comparing it to estimated discharge time of the battery and only allows the flash to start if all the checks have been checked off (e.g. motor off, ignition on, flash mode on, etc). There are also redundancies in place to recover and retransmit data in case of bad connections, dropped connections (disconnected and/or bad cables), battery on the phone/laptop dying or going to sleep. At times people open the door while flashing (e.g. too hot in the car
) and the vehicle will turn ignition off failing the flash.
We've placed all the warnings to let users know pre-flash but most of us are 'real men' and we all know real men don't read instructions even when they have to
No matter what though, at the end of the day when flashing over OBD you can't end up bricking these DMEs and there's always a way to recover, without pulling the DME out of the car. We've done everything you can imagine during testing in terms of failed flashes to ensure there's always a way to restore the DME back to normal through OBD,
as long as your battery has enough charge still.
Flashing checklist:
1) Engine off, driver's side seatbelt on, close doors and don't open while flashing
2) Hit the start button 3x to cycle ignition (on/off) and leave ignition on. Should show gas gauge level when ignition is on
3) Connect with bm3 and flash
4) Do yourself a favor and try to flash in a safe area just in case you end up having an odd issue such as battery charge related or phone/laptop dying etc
Some fun stats, since Sept. 7th '17 when we started archiving flash history BM3 has seen a total of 2510 flash requests of which 128 failed during write for one reason or another. 119 of those successfully recovered by simply repeating the flash and the remaining 9 ended up in the support queue on our support website where we stepped in to help such as with one of the user's in this thread to advise them on getting a battery charger and repeating the process.