You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
Thank you for doing this!I have now verified all known codes using CAN bus-injection and summarized the result in the attached file as information to those who may be interested. The debug messages were largely known and contain less news, but I now got all the enduser messages and message color codes too. Since these alerts were all raised by can-bus injection on a part and were not observed in a car as they naturally occur, there is no guarantee that they all can actually be observed in a car. These results are for VDS firmware version 3.22 only. The previously published reults cover several firmware versions. If anyone wants the excel sheet of messages that was used to generate the pdf, feel free to pm me.
Amazing!I have now verified all known codes using CAN bus-injection and summarized the result in the attached file as information to those who may be interested. The debug messages were largely known and contain less news, but I now got all the enduser messages and message color codes too. Since these alerts were all raised by can-bus injection on a part and were not observed in a car as they naturally occur, there is no guarantee that they all can actually be observed in a car. These results are for VDS firmware version 3.22 only. The previously published reults cover several firmware versions. If anyone wants the excel sheet of messages that was used to generate the pdf, feel free to pm me.
Thanks so much for all your hard work! Will these error numbers be generated as error messages from the OVMS app or on the VDS screen?I have now verified all known codes using CAN bus-injection and summarized the result in the attached file as information to those who may be interested. The debug messages were largely known and contain less news, but I now got all the enduser messages and message color codes too. Since these alerts were all raised by can-bus injection on a part and were not observed in a car as they naturally occur, there is no guarantee that they all can actually be observed in a car. These results are for VDS firmware version 3.22 only. The previously published reults cover several firmware versions. If anyone wants the excel sheet of messages that was used to generate the pdf, feel free to pm me.
My opinion... Always include the original manufacture's text as-is, but add to it for clarity or recommended action.The error messages that are displayed in the OVMS app for the Roadster come from a file on the OVMS server. I will work with Mark to incorporate @einhalv's list. One question in my mind is whether to use the debug versions of the messages. For me personally I want the extra detail, but for some people the acronyms and text of the debug messages may be too cryptic. Perhaps a synthesis would be best.
One question in my mind is whether to use the debug versions of the messages. For me personally I want the extra detail, but for some people the acronyms and text of the debug messages may be too cryptic. Perhaps a synthesis would be best.
That was my thought. Also expand the module acronyms in the debug messages, e.g. DMC = Digital Motor Controller.Of course, if we are not concerned about the length of the message texts in the OVMS, we could have both joined into one marking the two parts. e.g., E: and D:.
Two things have changed since the original VECE implementation (where the server converted the code to text): 1) we have now decoded the CAN bus messages in more detail and know exactly how a particular code is raised/cleared, and 2) we now have much more flash memory in the module than v1/v2 had. I think we can simply move all these text messages into the TR vehicle module and convert code->text there. That way we can also have a configurable debug/normal flag just like the VDS has. It would be helpful to compress these as much as possible (perhaps just code\0message\0code\0message\0\0 or something like that - not too worried about time, as there aren't that many and they aren't raised too frequently).The error messages that are displayed in the OVMS app for the Roadster come from a file on the OVMS server. I will work with Mark to incorporate @einhalv's list. One question in my mind is whether to use the debug versions of the messages. For me personally I want the extra detail, but for some people the acronyms and text of the debug messages may be too cryptic. Perhaps a synthesis would be best.
The original approach was to mimimic the VDS exactly. Same range calculation (rounding bugs and all), same messages, etc.Rather than having to choose between normal and debug messages, I think it would be better to synthesize a message for each code that is easy to understand while providing useful details. So I'd say that allowing for a normal/debug selection isn't a strong motivation to move the error messages into the OVMS firmware. If you think it is important for the Roadster to work the same way as other vehicles, then OK, but otherwise I don't see a big problem with leaving the text on the server.