FreeEMS Issues - Firmware
View Issue Details
0000337FirmwareSerial Commspublic2011-10-23 19:412011-10-23 20:57
normalminorhave not tried
New Feature
0000337: Return status flag in packet header to indicate potential problems and add API call to return list of issues from ECU
 Right now there are possible conditions where the tuning software can make changes to ram pages. if hte tuning software dies, laptop battery goes dead, whatever, when hte user reconnects he has NO IDEA that there is a potential dataloss scenario (ram/flash out of sync).

Suggest a "red flag" bit in the header of response packets that indicates a potential issue. Thus the tuning software could trigger a query to get more information about what is possibly wrong. This query should return an array of appropriate error codes (16 bit per code) that corresponds to an applicable message/course of action that the tuning software can do or appropriately notify the end user. The packet header should define the payload length so that hte list of codes can be arbritrary in length.

i.e. Possible warning/error codes:
RAM/FLASH not in sync for location X
Excessive serial Error rate
Excessive Decoder resync errors
Voltage low warning
Voltage high warning
S12x CPU load warning (if this can even be calculated)
Xgate CPU load warning (if this can even be calculated)

I think this would be worthwhile as it allows the ECU to tell the user "hey something's going wrong here", and since the ECU is typically constantly streaming, having a bit within the header indicating there are issues and the tuning software should?can invesitgate is a Good Thing. The binary log stream will also catch that bit being set so its a good debugging tool as well.
No tags attached.

2011-10-23 20:57   
Functionality like some of this is on the menu, other stuff has to come first.