DIYEFI.org Forum

Hard resets field doesn't seem to count resets, not those from the buttons which I verified do work, nor from the button on the device. Need clock to be set it stone before i can set this up... Why can't/don't you do it like MLV does it with just looking for sequential counters and read the SP5 var...

Hard resets field doesn't seem to count resets, not those from the buttons which I verified do work, nor from the button on the device. Need clock to be set it stone before i can set this up... If you want to display some of your existing MS bit flags/lights/etcs you could provide translated servic...

For a custom loggable solution that is tuning software agnostic. (doesn't require the tuning software to have (much) special knowledge, especially prior to connecting to the ECU to work) Provide the following API calls: Request list of loggable var ID's. call should provide back a list of how many v...

the packet length is 101 bytes as it said in the debug message, but the header WITHIN the packet says the payload is way larger than it should be....

BUG detected....

Full packet received, len 101 bytes
Ack/Nack Flag: 0
Has Sequence Flag: 1
Has Length Flag: 1
Payload length 35705
Sequence id: 77
Payload id: 401
Payload base offset: 6

Happened when requesting a basic datalog packet as per your API. used NO length args as per the API.

From what I can gather looking at kernel docs (install kernel-doc pkg, read /usr/share/doc/linux-doc/filesystems/ locks.txt and mandatory-locking.txt.gz), it appears that locking in general in linux is basically a mess, and its because every other unix seems to have done it differently over the year...

Fred, you also forgot offset within that locationID No I didn't! :-) What I said was that I expect you to know that one plum, two apples and one watermelon take up (1 + 4 + 4 + 30) = 39 units of size. If each field has an offset, it's asking to break all the time when editing. Lets make it dynamic ...

Another idea. fred days theres about 350K of flash. Why not take all the xml stuff the tuning software(s) will want, and tar/bzip2/lzma it an stuff it in a known static location ID in flash, the firmware itself doesn't need it to run (so no worry about having the firmware need to deal with decompres...

To create C we need: To generate the UI and process the data we need: locationID Descriptions for each field, user and/or dev preferably one copy for both. Data for defaults to load from file in offline Names for each field Raw types for each field Internal units for each field Conversion informati...

Depending on your language of choice for the markup, either develop a tool in C, or in somescripting langauge (perl?) that you compile FIRST as part of the build process that can then do the parsing/code generation in the next stage, and finally compile all that into objects and distributables that ...