ElectricMotorcycleForum.com

  • November 25, 2024, 12:39:59 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

Electric Motorcycle Forum is live!

Pages: [1]

Author Topic: Log file format?  (Read 1508 times)

LiveandLetDrive

  • Full Member
  • ***
  • Posts: 115
    • View Profile
    • If you must cage, cage well.
Log file format?
« on: December 17, 2014, 06:58:33 AM »


Is the log file format something proprietary or can we open them with some utility?  I requested a decrypted one once before but never really chased them for it.  It would be great to be able to just email it to myself and have a poke around.
Logged
2013 Zero FX, 2005 Triumph Sprint ST, 2000 Triumph Tiger, 1970 Triumph T100R Daytona, 1970 Honda SL100  (Latter three for sale!)

Doug S

  • Hero Member
  • *****
  • Posts: 1631
    • View Profile
Re: Log file format?
« Reply #1 on: December 17, 2014, 08:52:55 AM »

I emailed it to myself once just out of curiosity. It was a very, very short file, a couple hundred bytes at most, with very repetitive characters and little variation that would indicate any sort of useful information. I came to the conclusion that it was either encrypted, only failure records (and therefore had virtually no contents in my case, since the bike was running perfectly), or both.

Not a very interesting experiment. I'd love if it were a proper log file and we could access it. Why not do it that way?? A $5 flash RAM could store a LOT of log information, which would be very fun and perhaps informative to play with.
Logged
There's no better alarm clock than sunlight on asphalt.

Francois

  • Full Member
  • ***
  • Posts: 106
    • View Profile
Re: Log file format?
« Reply #2 on: December 17, 2014, 03:18:42 PM »

i like to see also, if you have the solution
Logged

LiveandLetDrive

  • Full Member
  • ***
  • Posts: 115
    • View Profile
    • If you must cage, cage well.
Re: Log file format?
« Reply #3 on: December 19, 2014, 01:18:58 AM »

Here's the first few lines of one I sent myself back in January.  The date stamp at the beginning may be a born-on date as I received it in October last year.  I'd forgotten it was a legible as it is.  Not sure if it goes back to the beginning of time or starts dumping the early stuff at some point.  The last ~2/3 of the file is just a string of "ÿ"s.  I'll ask my firmware pro buddy what he thinks of it and I'll let you all know if I hear anything from Zero about it.

¡¡¡¡Sep 26 2013 13:06:01 ÿÿÿÿÿÿÿÿÿÿ ÿÿÿÿ±w;     Â±w;     Ã»  ·  Ï   â€š$ Š® á+" ’ xN          ÿÏ     â€¢$     , v '   Å“      -?ÛR    <®  e 
       f       Ã¿Ã¿Ã¿Ã¿Ã¿Ã¿Ã¿Ã¿$              ÃŽÃ»     ]ü     
       Ã¿Ã¿Ã¿Ã¿Ã¿Ã¿Ã¿Ã¿       =L  ˹         Ã­      ÿÿÿÿÿÿÿÿ               ÃÃ»     Uü            Ã¿Ã¿Ã¿Ã¿Ã¿Ã¿Ã¿Ã¿  ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ2013_mbb_abd281_00369           Sep 26 2013 13:07:28 3:07:29    538XX3Z19DCC03197  Å¡c
À    Sep 26 2013 13:07:29 ÿÿÿÿÿÿÿÿÿÿ @  FX              d n F K (V  „ ,d @”ìÿú  ùÿÿÿ !             `ê      À'        ÿÿÿ    P   '  ¸       \&    üd d         Ã¿Ã¿Ã¿Ã¿Ã¿Ã¿ ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ££££\  a     Â²/=/³R  F    ²/#z´R @F ð ²/cz´R  F   '²1©ªÄR² :©ªÄR         Â²CýþMÏÄRUnexpected contactor close. Batt: 99437 mV, Cap: 100125 mV ²/¥ÅR @F ñ ²/7¥ÅR  F    ²1EðÆR² :EðÆR       Â²/ÔóÆR @F ñ ²/ôÆR  F   '²Aý+‰ÇRUnexpected contactor close. Batt: 85375 mV, Cap: 89187 mV ²13ÚR ² :3ÚR
   ²1q¬ÚR² :q¬ÚR         Â²/ŸÜÚR PÁR@  E   f²/Dþ«R 1ÃE ²/Dþ«R  ÃE    ²/Dþ«R 1ÃE ²/Eþ«R  ÃE    ²1ÿ̬R ² :ÿ̬R      Â²1†Õ¬R² :†Õ¬R         Â²1¡Í­R ² :¡Í­R
      Â²1Ë5¯R ² :Ë5¯R         Â²//³R @F ñ ¢¢¢¢sˆ    4  ²=ý   DEBUG: Event Log reformatted due to bad read pointer. ²&ý   DEBUG: Log data at offset 0x0: ²:ý     A2 A2 A2 A2 53 E7 01 00 5B E7 01 00 69 14 00 00  ²:ý     45 42 55 47 3A 20 4D 6F 64 75 6C 65 20 30 31 20  ²:ý     46 45 54 73 20 61 72 65 20 6E 6F 77 20 43 6C 6F  ²:ý     73 65 64 00 B2 08 3D 83 BA 8E 52 00 B2 08 3D 83  ²Eý   WARNING: A non-critical element failed to initialize properly ²(ý   DEBUG: Reset: Power-On, External ²   4   ²      ²3                 Â²3                ²ý   CAN0 ACK error ²(    ²3    c–         Â²(v¯ÇR²6v¯ÇR²3v¯ÇRq–         Â²Cýv¯ÇRDEBUG: Module scheme changed from None mode to Running mode ²=ýv¯ÇRDEBUG: Module mode Change Does Not Require Disconnect ²*w¯ÇR²)ýx¯ÇRDEBUG: Sevcon Contactor Drive ON. ²3x¯ÇR _– À– O– ²3x¯ÇRm– À– O– ²,ýx¯ÇRDEBUG: Module 00 FETs are now Closed ²,ýx¯ÇRDEBUG: Module 01 FETs are now Closed ²=x¯ÇR ²=x¯ÇR²!ýx¯ÇRINFO:  Enabling Charger 1 ²!ýx¯ÇRINFO:  Enabling Charger 2 ²&ýx¯ÇRContactor took 367 ms to close ²W>x¯ÇR÷m
” ÷m – ¹m – zm – <m – <m Õ ýl – ýl – x— Õ :— Õ ²,€¯ÇR8 –          ²   9€¯ÇR²,¼¯ÇR8 ~’   ? 
 D ²   9¼¯ÇR\²(ý    DEBUG: Reset: Power-On, External ²   4    ²   0     ²Dý    DEBUG: Module scheme changed from None mode to Charging mode ²3                  ²3                 ²(     Â²3     ó”         Â²(¥´ÇR²3¥´ÇRõ”         Â²6¦´ÇR²ý§´ÇRCAN1 BIT0 error ²*§´ÇR²)ý§´ÇRDEBUG: Sevcon Contactor Drive ON. ²3§´ÇR í” õ” ‹” ²3§´ÇRñ” õ” ‹” ²,ý§´ÇRDEBUG: Module 00 FETs are now Closed ²,ý§´ÇRDEBUG: Module 01 FETs are now Closed ²=§´ÇR ²!ý§´ÇRINFO:  Enabling Charger 0 ²!ý§´ÇRINFO:  Enabling Charger 1 ²!ý§´ÇRINFO:  Enabling Charger 2 ²&ý§´ÇRContactor took 375 ms to close ²=§´ÇR²W>§´ÇRZh “ Ýg É” `g Š” ãf Š” ff É” 'f É” 'f Š” !g Š” – Š” – Š” ²-¯´ÇR4 Ú• úÿ ²(ý    DEBUG: Reset: Power-On, External ²   4    ²   0     ²Dý    DEBUG: Module scheme changed from None mode to Charging mode
Logged
2013 Zero FX, 2005 Triumph Sprint ST, 2000 Triumph Tiger, 1970 Triumph T100R Daytona, 1970 Honda SL100  (Latter three for sale!)

LiveandLetDrive

  • Full Member
  • ***
  • Posts: 115
    • View Profile
    • If you must cage, cage well.
Re: Log file format?
« Reply #4 on: December 19, 2014, 01:59:12 AM »

Here it is attached.  I stripped out the non-text stuff.  No time stamps which I imagine is part of the unreadable characters.  Always a long string of characters after "Contactor took --- ms to close" and various lengths between other statements.  If it records every charge event it's got to be a looong file by now!


Sep 26 2013 13:06:01
2013_mbb_abd281_00369
Sep 26 2013 13:07:28 3:07:29
Sep 26 2013 13:07:29

Unexpected contactor close. Batt: 99437 mV, Cap: 100125 mV
Unexpected contactor close. Batt: 85375 mV, Cap: 89187 mV
DEBUG: Event Log reformatted due to bad read pointer.
DEBUG: Log data at offset 0x0:
WARNING: A non-critical element failed to initialize properly
DEBUG: Reset: Power-On, External
CAN0 ACK error
DEBUG: Module scheme changed from None mode to Running mode
DEBUG: Module mode Change Does Not Require Disconnect
DEBUG: Sevcon Contactor Drive ON.
DEBUG: Module 00 FETs are now Closed
DEBUG: Module 01 FETs are now Closed
INFO:  Enabling Charger 1
INFO:  Enabling Charger 2
Contactor took 367 ms to close
DEBUG: Reset: Power-On, External
DEBUG: Module scheme changed from None mode to Charging mode
CAN1 BIT0 error
DEBUG: Sevcon Contactor Drive ON.
DEBUG: Module 00 FETs are now Closed
DEBUG: Module 01 FETs are now Closed
INFO:  Enabling Charger 0
INFO:  Enabling Charger 1
INFO:  Enabling Charger 2
Contactor took 375 ms to close
DEBUG: Reset: Power-On, External
DEBUG: Module scheme changed from None mode to Charging mode
DEBUG: Sevcon Contactor Drive ON.
DEBUG: Module 00 FETs are now Closed
DEBUG: Module 01 FETs are now Closed
INFO:  Enabling Charger 0
INFO:  Enabling Charger 1
INFO:  Enabling Charger 2
Contactor took 391 ms to close
Logged
2013 Zero FX, 2005 Triumph Sprint ST, 2000 Triumph Tiger, 1970 Triumph T100R Daytona, 1970 Honda SL100  (Latter three for sale!)

firepower

  • Hero Member
  • *****
  • Posts: 686
  • Hanoi, Vietnam
    • View Profile
Re: Log file format?
« Reply #5 on: December 19, 2014, 08:26:45 AM »

y symbol is FF hex , use for blank memory location.(erased eproms contain FF)
Logged

Justin Andrews

  • Hero Member
  • *****
  • Posts: 1032
    • View Profile
Re: Log file format?
« Reply #6 on: December 19, 2014, 04:11:10 PM »

You really need to look at this file in a hex editor, particuarly one that allows you to show blocks of data as either bytes, shorts, ints, unsigned ints or floats. The symbols after the text strings are binary data, I have NO doubt in my mind about that. I also have a suspicion that after each of the character blocks the data size varies according to what was output in the string. So a contactor closing has additional engineering data after it, possibly. Its a hunch as I've not counted the stride of each data block after each type of string report. Yet.

The killer is working out what is what in that data block (byte, short, int, etc) and its MUCH harder to then work out what each value means.
Logged
Zero 2015 SR (+PT);
Yamaha Diversion 900

PhreaK

  • Full Member
  • ***
  • Posts: 143
    • View Profile
Re: Log file format?
« Reply #7 on: May 28, 2015, 09:28:37 PM »

I'd say Firepower is on the money with the EPROM hunch. The raw log file that LiveandLetDrive posted above is right on the dot at 128mb (0x20000 bytes). Based on this I'd assume that it's probably just running as a ringbuffer within that space.

From a cursory look it looks like it uses a 2 byte footer / delimiter of {0x00 0xb2} between entries. The sections which map to ASCII are pretty self explanatory. Aside from that, it looks like there may be some form of heartbeat or timestamp in there as well. There's a 6 byte sequence which (at least in LiveandLetDrive's logs) ends in 0x52 throughout. You can spot this in areas where there not much else being logged following the {0x00 0xb2} delimiter and from appears to increment throughout. I'll see if I can make sense of some of the rest when I get bored.

Thanks for posting this by the way. Checking out a second hand SR tomorrow. Should be interesting turning up with a phone and laptop to check it over. Give me the ability to extract logs and parse them for evidence of defects vs dealing with that messy mechanical stuff any day.
Logged
2014 Zero SR

Justin Andrews

  • Hero Member
  • *****
  • Posts: 1032
    • View Profile
Re: Log file format?
« Reply #8 on: May 28, 2015, 09:57:45 PM »

I have one of these.
http://hollywoodelectrics.com/product/diginow-data-reaper-dongle/

I can strongly recommend it for looking at your logs.
Logged
Zero 2015 SR (+PT);
Yamaha Diversion 900
Pages: [1]