[Ovmsdev] OVMS v2 Memory/Settings Corruption

Julien Banchet jaxx at jaxx.org
Fri Nov 25 15:16:32 HKT 2016


Sorry, I only gave flaky examples because I switched phones recently and
was lazy to digup the old one that had some screenshots

Here are some real cases
C33651886877
+336518867s7
+3365188T877
+336518868h7

That said, it still is way more than a simple bit flip, and only corrupts
the phone number as far as I can recall.

I have no explanation, all I can say is, most of the time, I plug the OVMS
when I plan charging later in the morning, usually when I'm still
underground and a handful of seconds before putting contact (if this can
point to any clue)

Anyways, gonna try cutting GPRS this morning and see how quick it
discharges and might automate switching SMS<->SMSIP once in a while to keep
an eye on the battery (my cell operator has an API) though it might wearout
eeprom even more :-/

JaXX./.


On Fri, Nov 25, 2016 at 1:56 AM, Mark Webb-Johnson <mark at webb-johnson.net>
wrote:

> $ perl -e 'printf "%08b\n",ord("5");'
> 00110101
> $ perl -e 'printf "%08b\n",ord("k");'
> 01101011
> $ perl -e 'printf "%08b\n",ord("8");'
> 00111000
> $ perl -e 'printf "%08b\n",ord("Z");'
> 01011010
>
> Strange. Seems more than a simple bit flip. I haven’t seen this myself, or
> heard of it much from other users.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.teslaclub.hk/pipermail/ovmsdev/attachments/20161125/2b0661a8/attachment.html>


More information about the OvmsDev mailing list