Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[BrianTRice@gmail.com]

This is a technical assistance request for owners of Zero models in the S+DS and FX/FXS platforms made on or after 2017.


Background:
The unofficial log parser is a community project to help owners decode Zero logs. The code is at:
https://github.com/zero-motorcycle-community/zero-log-parser/
and the service that uses it is at:
http://home.hasslers.net/zerologparser/


There is a format change that Zero introduced to the log header, currently documented as a bug:
https://github.com/zero-motorcycle-community/zero-log-parser/issues/15


I introduced a change recently to help address this, BUT we are missing files that help us understand how Zero decodes those logs, and this ultimately prevents us from a correct interpretation of those logs.


In this way, BTW, the unofficial log parser has become a victim of its own success, because it was built by emulating the output that Zero provides to owners when they share their logs with customer service. Because the unofficial log parser has become so commonplace to use and mostly correct, this process of correction stalled.


So, I'm looking for volunteers who can send me text-file logs that Zero has provided to them, NOT unofficial log parse text-file logs, so that we can compare and correct the unofficial log parser. Obviously, the original log (that ends in .bin) will also be helpful.


You can email me at (my forum handle) at gmail.com to avoid sharing it publicly and also to avoid forum attachment size limits.


Thanks!

[MrBlc]

*bump*
is this the reason for this error?:
File "zero_log_parser.py", line 74
    def decode_str(log_text_segment: bytearray) -> str:
                                   ^
SyntaxError: invalid syntax

[BrianTRice@gmail.com]

*bump*
is this the reason for this error?:
File "zero_log_parser.py", line 74
    def decode_str(log_text_segment: bytearray) -> str:
                                   ^
SyntaxError: invalid syntax

No, that's because you're using it with Python 2, which we've migrated off of because it's now deprecated. Please run it with Python 3.

The issue is that the header byte structure was changed significantly, and we have no official parsed logs from Zero to compare and emulate. That's how the log parser was built in the first place, and this process is now broken or non-existent anyway.

[MrBlc]

To be honest i wanted to have a reason to bump the thread for you, and i just happened to get that error.
Weirdly enough i had installed python3, but you were right (as usual).
Thank you for quick reply

[BrianTRice@gmail.com]

Okay, I'm glad someone is paying attention, because this does concern me. Access to bike data is important for owners to be able to independently understand and verify claims from the manufacturer and service technicians. We need to understand how our bikes operate (and how they sometimes fail!).

The specific request I have is: if you own a 2017+ year model, please get Zero customer service to send you a decoded log, and send me or someone who can work on the Python code your binary and decoded text log so we can understand what is contained in this header so we can emulate Zero's tools.

[MrBlc]

Easier said than done.. I was hoping my last error would initiate such a request from customer service, but when i talked to them, he just replied "that error means we need to get the bike in to a shop to read out the diagnostics directly. The information you pull from the app is not enough".
Seems to me that they are aware and try to avoid divulging more information than they have to..

[valnar]

It seems the easiest way to crack this nut is to have a good relationship with your local Zero dealer.  Maybe just ask them?

[BrianTRice@gmail.com]

It seems the easiest way to crack this nut is to have a good relationship with your local Zero dealer.  Maybe just ask them?

That's not how the mobile application works. It sends the logs directly to Zero.

But yes, I would invite an owner to ask their dealer for a log decode. We need the actual files, though, not hearsay.

[JaimeC]

Okay then... here's a stupid question:  Has anyone reached out to Harlan Flagg for this?

[BrianTRice@gmail.com]

Okay then... here's a stupid question:  Has anyone reached out to Harlan Flagg for this?

They/you could. I'm not going to ask a dealer for one of their customers' logs, though. I'd hope I can ask them for one of their own bikes' logs. So hopefully a customer can ask for their own logs and forward them for study.

For what it's worth, I did get someone to help identify the firmware revision field, and I've inferred the board revision field if someone can run zero_log_parser.py directly to confirm (since Greg Hassler's site is broken lately).

[JaimeC]

Unfortunately I'm on the other side of the country from Hollywood Electrics... but I'm assuming he has his own Zero, if not he could pull the logs from a demo bike...

[BrianTRice@gmail.com]

Yeah, dealers can do this. What I need are matching copies of OFFICIALLY decoded and raw logs. Pretty simple, just not something we get access to, which is kind of my point - that Zero may be cutting owners off, and that is not in anyone's best interest, despite it likely appealing to Zero's self-protective nature.

[gadgetgirl]

This may be old news, but I was told by Zero today that they consider decoded logs for my SR/F to be proprietary information, and have a policy to not disclose them.

[Crissa]

Yes, their position is pretty legally shakey if also common.

-Crissa

[Auriga]

Yes, their position is pretty legally shakey if also common.

-Crissa

I'm curious why you think it's legally shaky? Other than OBDII information, I'm not sure I've ever been able to access software logs in any vehicle I've owned. Tesla folks have been having this argument too, and it looks like they also have been unsuccessful(except for the crash data recorder).