Adjusted the PuTTy settings per the link
@Floyd and it still didn't seem to correct the issue of each text line being tabbed progressively further to the right, and word wrap anomalies...
I was able to copy and paste the otherwise difficult to read terminal readout into notepad, and post-process to a bit more legibility. Maybe this is an echo setting issue, where its doubling (or more) the number of characters for the tab so all subsequent rows get progressively more offset? Or maybe its representing tab differently than this x64 system is interpreting?
My description of this error is rough. Though it genuinely seems like there is an easy solution to this.
One notable concern that surfaced during my first session last night with the purpose of finding the health of the battery... I got home after work and a long route (nice weather here). There was still 40-50% capacity left in the battery per the dash meter. I plugged in, and logged on to print some stats and information on the battery SOH. When I hit the command for 'bms' the dash meter capacity reading went to empty (blank), as did the resulting measurements in the bms print out (see attached photo). This made me concerned, with catastrophic thoughts like, oh gosh Zero put some sort of back end block to trash the battery if logon was sketchy?? Then I though, and hoped, it was just some random glitch and the best thing I could do was logout, shut the bike down, and plug in for an overnight (balance) charge...
Look at the spec sheet though... it says all the cells were at a very low voltage. Yet, I had just rode it for at least 5 miles at speeds of 35-55 mph. Then after I bailed on the session after getting the anomalous reading, it started and drove fine the remaining distance to the garage, e.g. no volt sag and all lights and accessories were working as if the battery was still at ~50%.
That leads me to suppose that there was just some software glitch or user error in my navigation of the oddly tab justified console. Perhaps there is a voltage calibration setting for the bms or something, and now after an overnight charge, it automatically or I can manually reset?
I'll be starting up the bike in a bit to see what overnight charge did for the anomalous bms reading. Will report that back here later today.
Has anyone that had or has one of these earlier (gen1 or gen2) bikes exhibit a similar anomaly?
Side note, during this logon session and prior to the bms stat print below, I found that the blinking error light on the dash was indeed indicating a BMS CANbus error. Is it possible, this battery is actually a replacement and the BMS was bypassed or spoofed?
