His bike is his primary means of transport... So i don't want to risk it fails because he will not be able to drive anymore until firmware is correctly replaced.
Yesterday afternoon, because of my fw_upgrade.js failed for HUB cntrl. via "new method" (old method ok, also for M400) I downloaded the complete source code again. I tried from within the program, but it also stops at a few % upload for my hub controller just like my fw_upgrade.js did.
So today i looked at my previous version which still does work for Hub controller using "new method". I tried comparing it to the combined latest version i have. I know the reason now. Back then, tested hub controller, eventually worked. M400 not. We changed code till M400 did work.
Code then got changed to work for the 2 methods. Tested that with M400 => worked. But i did then not test again the hub controller if i recall well to see if that still worked... Probably because i was already in the middle of trying display to update...
Because of the question from FlippyThermos i wanted to check first and connected hub cntrl again and realized the hub controller did not work anymore via "new method" in combined code.
Anyway today after several hours i got my fw_upgrade.js working again for hub controller. It picks automatically "new method" and if i force it to use "old method" it works too. Also M400 still works, it picks automatically "old method".
There is more to it i wonder about because i'm no coder but ok it's working. The M820 looks way less picky
