I would like to add to this. There are several cases where error 16 showed up that have nothing to do with chip or wiring. I ve suffered from a pretty rare case myself on a 4209/4132 board where a CBXR was installed. Clearly no-one including Chi believed that it wasn't my install error and advised i replace the harness. Off course i tested the harness to ensure it had no flaws. Im quite neurotic and made absolutely sure all components were working before and install was done as clean as it gets.
What happened:
After install the board worked fine for a couple of charges. But suddenly i was faced with a buzzing phone mid-ride, the tail sunk into the asphalt (like empty-battery pushback) and the board started a wild accelleration with tail scraping the floor. Bailout was only way to stop which happened a couple of times in full traffic...pretty scary if you dont expect it.
Conditions:
Some conditions had to be met for this to happen.
- App needs to be at 1%. So the board calculated that full stock battery capacity had to be used up.
- Voltage needed to drop below 53v. Typically the voltage after the error would be between 53.4 and 52,8v.
- Below pushback speed. Im afraid that, if this error happened above pushback speed, the board likely would nosedive without warning. I cannot be sure but lucky i did not have to find out in the field.
- A reboot of the board AFTER the error showed up guaranteed i was able to ride the board till empty. No more error16.
After some thinking and troubleshooting to discard other things causing problems it occured to me that the board simply had no other option to display this error, thus 16 showed up. What probably was happening is a critical error where the board cannot resolve unless rebooted. There are possible cases where it occurs and even a reboot does not solve it, bricking the board (4210/4150 boards that were initially lucky to have a functioning cbxr at start).
Also the possibility that some boards do not carry the app-indicated firmware in all components: a 4132 controller with non-4132 bms.
What can be concluded is, that app indication is not always what's installed. Also the coding is said to be poorly done. I know nothing about coding but my thoughts were supported by people working/flashing/repairing this stuff.
My problem was solved: i sent in my bms to have it flashed to a compatible custom firmware. This is possible up to/incl 4209/4132 boards.