ElectricMotorcycleForum.com

  • May 16, 2024, 09:16:20 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

Electric Motorcycle Forum is live!

Pages: 1 ... 4 5 [6] 7

Author Topic: Log file parser utility  (Read 10979 times)

BrianTRice@gmail.com

  • Unofficial Zero Manual Editor
  • Hero Member
  • *****
  • Posts: 4014
  • Nerdy Adventurer
    • View Profile
    • Personal site
Re: Log file parser utility
« Reply #75 on: April 11, 2017, 12:00:37 AM »

I have created a powerful Highcharts web based viewer for MBB log files. This is an offline html file you can download from GitHub https://zero-motorcycle-community.github.io/browser-parse/  Check out these screenshots https://www.facebook.com/media/set/?set=a.10210866026279376.1073741840.1613544878&type=1&l=1fbc3493f7.

This is getting so useful and accessible. I need to try using these in earnest now on my phone for efficiency / data collection.

Thanks for being on this as I am terribly busy lately and still am catching up on forum activity.
Logged
Current: 2020 DSR, 2012 Suzuki V-Strom
Former: 2016 DSR, 2013 DS

Keith

  • Sr. Member
  • ****
  • Posts: 269
    • View Profile
Re: Log file parser utility
« Reply #76 on: April 13, 2017, 07:13:03 PM »

I have a list of improvements for the viewer but it is hard to work on software when the weather is nice. One thing on my list: I'd like to show rpm as speed and motor amps as torque, but the conversion factors vary for the different models. Maybe the numbers are in the Zero app since it does the conversions, anyone into decompiling?
Logged
2016 Zero FX, 2014 KTM 1190

BrianTRice@gmail.com

  • Unofficial Zero Manual Editor
  • Hero Member
  • *****
  • Posts: 4014
  • Nerdy Adventurer
    • View Profile
    • Personal site
Re: Log file parser utility
« Reply #77 on: April 14, 2017, 07:35:10 AM »

I have a list of improvements for the viewer but it is hard to work on software when the weather is nice. One thing on my list: I'd like to show rpm as speed and motor amps as torque, but the conversion factors vary for the different models. Maybe the numbers are in the Zero app since it does the conversions, anyone into decompiling?

The MBB settings have the factors stored for the speedometer calculation (since it performs it), which is obviously a kind of gearing/multiplication factor on the sprockets and outer tire diameter estimate.

I'm not sure about amps to torque, but I'll bet it's roughly the basic physics that uses the idea that power=current*voltage and power=torque*angular_velocity.

http://simplemotor.com/calculations/

So, you could take battery voltage / (current * <angular velocity in radians from RPM>) to get a rough torque estimate, I think. With a fudge factor of maybe 95% for transmission and rolling friction losses.
Logged
Current: 2020 DSR, 2012 Suzuki V-Strom
Former: 2016 DSR, 2013 DS

nevetsyad

  • Sr. Member
  • ****
  • Posts: 317
    • View Profile
Re: Log file parser utility
« Reply #78 on: April 14, 2017, 04:08:33 PM »

This tool confirmed that my bike has serious issues, while I'm told constantly that things are fine with it. 24-28% power available to the motor at 28-68% SOC and a decent ambient temp is not normal! Thank you!!! Going through old logs I've mailed in is making me angry.

Perfectly normal ride here:

Since I was in the parser, I pulled up my SR logs. 28% power available at 64% SOC. Yeah, that checks out, seems normal. Nothing wrong with this bike...

07615     01/11/2017 14:26:18   Riding                     PackTemp: h 19C, l 19C, PackSOC: 64%, Vpack: 92.516V, MotAmps: 148, BattAmps: 188, Mods: 10, MotTemp:  69C, CtrlTemp:  26C, AmbTemp:  15C, MotRPM:4564, Odo:12518km
 07616     01/11/2017 14:26:18   Batt Dischg Cur Limited    199 A (28%), MinCell: 3249mV, MaxPackTemp: 19C
When I got home:
07639     01/11/2017 14:37:18   Disarmed                   PackTemp: h 24C, l 24C, PackSOC: 53%, Vpack:102.373V, MotAmps:   0, BattAmps:   2, Mods: 01, MotTemp:  59C, CtrlTemp:  21C, AmbTemp:  13C, MotRPM:   0, Odo:12530km
Logged
2023 Energica Experia
2022 Lightning Strike (reservation)
2021 Energica Eva Ribelle (For Sale)
2020 Zero SR/S (sold)
2018 Zero DSR (sold)
2015 Zero SR (Lets call it sold)

mrwilsn

  • Hero Member
  • *****
  • Posts: 693
  • 2014 Zero S / 2017 Zero SR
    • View Profile
Re: Log file parser utility
« Reply #79 on: May 07, 2017, 01:02:29 AM »

I have created a powerful Highcharts web based viewer for MBB log files. This is an offline html file you can download from GitHub https://zero-motorcycle-community.github.io/browser-parse/  Check out these screenshots https://www.facebook.com/media/set/?set=a.10210866026279376.1073741840.1613544878&type=1&l=1fbc3493f7.

I just got around to playing with the tool.  What great work.  One suggested improvement would be to provide for downloading the data that gets graphed into a CSV file instead of just pics.  That would allow for some data manipulation.
Logged
2014 Zero S

Keith

  • Sr. Member
  • ****
  • Posts: 269
    • View Profile
Re: Log file parser utility
« Reply #80 on: May 07, 2017, 02:37:19 AM »

 ;D You might try the spreadsheet I made if you want the data more directly. I found that Google Sheets was a lot more capable than I thought. https://goo.gl/GGDcgr CSV download would be pretty easy to add to the viewer, I'll put it on my list (waiting for bad riding weather).
Logged
2016 Zero FX, 2014 KTM 1190

Tiger

  • Newbie
  • *
  • Posts: 4
    • View Profile
Re: Log file parser utility
« Reply #81 on: October 11, 2017, 03:12:28 PM »

Dear Keith, hello everybody,

I am Jochen from Germany.

I got a firmware update some days ago. After that I took a log file using the Zero App. But unfortunately the log viewer is not able to read it anymore. It just says "Not an MBB log file.". Before that firmware update everything worked well.

Is this a knwon issue? Something wrong with my bike? What could I do to analyze this?

Best regards,
Jochen
Logged

nevetsyad

  • Sr. Member
  • ****
  • Posts: 317
    • View Profile
Re: Log file parser utility
« Reply #82 on: October 11, 2017, 05:18:50 PM »

V51 made mine unreadable. They also take over and hour to pull now. You have SOC, capacity and range estimate issues also?
Logged
2023 Energica Experia
2022 Lightning Strike (reservation)
2021 Energica Eva Ribelle (For Sale)
2020 Zero SR/S (sold)
2018 Zero DSR (sold)
2015 Zero SR (Lets call it sold)

Tiger

  • Newbie
  • *
  • Posts: 4
    • View Profile
Re: Log file parser utility
« Reply #83 on: October 11, 2017, 06:30:34 PM »

You have SOC, capacity and range estimate issues also?

Yes, that was the reason to read out a log.
I am daily commuting the same route since a year. So I know what percantage is usually shown at "each corner", espacially the value arriving at work and arriving at home. Some day it looks as usuall, some day the consumption seems to be higher. So also on my last ride. Started with 100% at home in the morning and finished with 20% at home in the evening. Usually there was ~35%. After 2 hours doing nothing I switched on the bike again and there was 31%. 31% would be in the range of uncertainty. But 20% is definitely not.

I was completely satisfied with the original firmware (DSR 2016). Is it possible to go back?

Best reggards, Jochen
Logged

nevetsyad

  • Sr. Member
  • ****
  • Posts: 317
    • View Profile
Re: Log file parser utility
« Reply #84 on: October 11, 2017, 06:43:31 PM »

I'm still waiting to hear back from Zero. Send them your logs, without battery information. Tell them what is going on and ask when a firmware fix will be released.

I heard rumor that there's a new, v52 or v53 out already. You may be able to go to a dealer and get it updated to fix it already. My dealer is an hour away, I have to bring the family out there to drop it off, then bring them out there to help me pick it up, it sucks. I shouldn't have accepted the free update, half the time it breaks something.
Logged
2023 Energica Experia
2022 Lightning Strike (reservation)
2021 Energica Eva Ribelle (For Sale)
2020 Zero SR/S (sold)
2018 Zero DSR (sold)
2015 Zero SR (Lets call it sold)

clay.leihy

  • Sr. Member
  • ****
  • Posts: 337
    • View Profile
Re: Log file parser utility
« Reply #85 on: October 12, 2017, 04:41:18 AM »

I have v51 and the newest version of the app tells me I need to upgrade.

Sent from my Z982 using Tapatalk

Logged
Clay
DoD #2160,6

gt13013

  • Sr. Member
  • ****
  • Posts: 300
    • View Profile
Re: Log file parser utility
« Reply #86 on: October 16, 2017, 06:21:11 AM »

I have discovered the Zero Log Viewer today, and it is a really impressive and useful work. Thanks!

It has shown me that twice in the previous month, the engine temperature suddenly dropped to -100°C !!!
Has somebody else experienced the same thing? If you get it, you will have a line with "MotTemp:-100C" in the Zero Log Viewer.

I have a list of improvements for the viewer but it is hard to work on software when the weather is nice. One thing on my list: I'd like to show rpm as speed and motor amps as torque, but the conversion factors vary for the different models. Maybe the numbers are in the Zero app since it does the conversions, anyone into decompiling?
I have found the numbers for my bike in the specifications, at the end of the Owners Manual. These manuals are available at http://www.zeromotorcycles.com/owner-resources/
I attach a rpm to speed converter with the data of my bike (FXS 2016 11kW)


Logged
Zero S 2023, Zero FXS 2016

RickSteeb

  • Full Member
  • ***
  • Posts: 181
    • View Profile
Re: Log file parser utility
« Reply #87 on: June 11, 2018, 01:22:55 AM »

My 2013 FX logs don't translate; is there a version of the log parser available for the '13FX?

Many Thanks!
Logged
Current fleet: (2012 DS Recalled), 2014 SR, 2013 FX

BrianTRice@gmail.com

  • Unofficial Zero Manual Editor
  • Hero Member
  • *****
  • Posts: 4014
  • Nerdy Adventurer
    • View Profile
    • Personal site
Re: Log file parser utility
« Reply #88 on: June 13, 2018, 05:39:06 AM »

My 2013 FX logs don't translate; is there a version of the log parser available for the '13FX?

Many Thanks!

Unfortunately, that usually means that the export is truncated in an unfixable way. Sometimes retrying works, but if the problem is serious enough, it'll be best to have a dealer look or access the MBB by the OBD-II port directly to get logs that way.
Logged
Current: 2020 DSR, 2012 Suzuki V-Strom
Former: 2016 DSR, 2013 DS

netdomon

  • Newbie
  • *
  • Posts: 12
    • View Profile
Re: Log file parser utility
« Reply #89 on: June 13, 2018, 05:22:47 PM »

thank you mam!!
Pages: 1 ... 4 5 [6] 7