|Home | WikiLEC | Repairs | Upgrades | Gallery | Buy & Sell | Mountain Chips | Meets & Events | Contact||
Thank you, so at least your observations are the same than mines.GeoffSmith wrote:0x0004: Always 0x01 and used by ES
Would you need a .est import/export too? I can add that to my todo list.To help with my hardware development etc., I also save raw data (minus the 273 byte header) and use .est (ElanScan Turbo).
Maybe, it's hard to guess :/I keep meaning to ask ESM about the 5th byte as I foresee it being useful if, for example, sat nav coordinate data is tagged onto the end of each row it could be set to 0x02.
GeoffSmith wrote:0x010A: Always 0x47?
I just had a look in my notes and 0x47 is (?) the size of one "packet" stored by ElanScan (the data from the ECU minus the header and checksum, plus the timestamp)Giniw wrote:PS: as for 0x010A I don't remember but I probably found what it is used for because I only missed that 1 integer.
I will tell you what I think it is when I have my notes.
Users browsing this forum: No registered users and 1 guest