First “Real” ride with v3.0 in a Twizy
Hi, Feedback on my First real ride after having had it sit >12h without a crash on my desk. I did have to auto wifi.mode off (instead of ap/apclient), otherwise nor v2 or v3 server wouldn't connect (ppp up, underground parking). Sidenote, before off-ing wifi, using my iPhone, web server went mute at a moment on ap: W (133945) websocket: WebSocketHandler[0x3fff15e0]: job queue overflow W (133975) websocket: WebSocketHandler[0x3fff15e0]: job queue overflow W (134225) websocket: WebSocketHandler[0x3fff15e0]: job queue overflow W (134475) websocket: WebSocketHandler[0x3fff15e0]: job queue overflow W (134725) websocket: WebSocketHandler[0x3fff15e0]: job queue overflow Otherwise RAM hovered around 70kB free. https://pastebin.com/EHBSHp4X (It doesn’t “stream” that much, I initially thought of regular crashes but monotonic keeps counting, I’ll have to figure a way to log the console somehow during a drive Getting usable despite the lack of a passive GPS :-) I really though I cut v2 before taking off, but got notifications from Michael’s server Volts: !SD:35mV !C1:+50mV !C2:+40mV !C3:+45mV !C4:+40mV !C5:+45mV !C6:-25mV !C7:-25mV !C8:-25mV !C9:-25mV !C10:-25mV !C11:-25mV !C12:-25mV !C13:-25mV !C14:+25mV Temps: SD:1C OK Ouch, I really need to let the cells balance sometimes. Trip 8.8km 21.0kph 81Wpk/23% SOC+42949656.0%=79.7%=== 22% 68Wpk/5%+++ 37% 3.0kps 222Wpk/0%--- 40% 2.0kps -43Wpk/433% :-) First ride metrics or Battery was really ~ -42949740% full :-) JB./.
Julien, Am 21.03.2018 um 10:37 schrieb Julien “JaXX” Banchet:
Volts: !SD:35mV !C1:+50mV !C2:+40mV !C3:+45mV !C4:+40mV !C5:+45mV !C6:-25mV !C7:-25mV !C8:-25mV !C9:-25mV !C10:-25mV !C11:-25mV !C12:-25mV !C13:-25mV !C14:+25mV Temps: SD:1C OK Ouch, I really need to let the cells balance sometimes.
Trip 8.8km 21.0kph 81Wpk/23% SOC+42949656.0%=79.7%=== 22% 68Wpk/5%+++ 37% 3.0kps 222Wpk/0%--- 40% 2.0kps -43Wpk/433% :-) First ride metrics or Battery was really ~ -42949740% full :-)
The SOC difference should now be correct. I think the cell deviation alert is a bug in the new processing. The voltages come in three CAN frames, frame #1 covers cells 1-5, frame #2 6-10, frame #3 11-14. So it seems frame #1 was missing, but the deviation system still triggered the alert. I just had a similar effect while test driving the kickdown function. I'll have a look at that. Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
participants (2)
-
Julien “JaXX” Banchet -
Michael Balzer