[Ovmsdev] Roadster: Some alerts not showing up

[Mark Webb-Johnson]

Chip,

Good suggestion, But unfortunately we haven’t been able to find that signal on the can bus. I suspect it is never sent, but just entered and stored in the VDS; as the vms sends debug alerts regardless of the setting. The alert message strings are in the vds firmware, and vms only sends codes.

To do this properly would require ovms doing what the vds does - have an alert code -> debug/user,message table and do the conversion and filtering there (not in the server). But that is quite a bit of code flash memory.

Regards, Mark

> On 31 Oct 2019, at 4:50 PM, Chip Cangialose <chip at cangmag.com> wrote:
> 
> 
> Watching this thread with some interest as I, like Greg, would like to see the “Debug” alerts over OVMS.  I would note that if the goal is to have OVMS show what the VDS shows, if you have the Roadster set to “Show Debug”, then OVMS will not show what VDS shows.  Is it possible to track the status of “Debug reporting to VDS” in the car, and have the OVMS server relay accordingly?
> 
> Thanks, and apologies for jumping in.
> 
> Chip
> 
> Sent from my tablet
> 
> 
> 
>> On Thu, Oct 31, 2019 at 1:30 AM +0100, "Mark Webb-Johnson" <mark at webb-johnson.net> wrote:
>> 
>> 
>> The server doesn’t have any per-vehicle configuration (other than authentication), so not sure how this could be easily done server side.
>> 
>> A kludge might be to pickup the notification event in a javascript on the module, and then raise a new different textual event for specific IDs - but not sure if the vehicle module javascript framework gets enough about the raised notification in order to do that.
>> 
>> An alternate kludge would be to manually list vehicle IDs to be exempted from the DMC policy in the ovms_server.conf file, and have code to check that in ovms_server.pl.
>> 
>> But, that said, I’m not really sure why we would want this. Our goal has always been to mirror what it says on the little VDS in the car, and that doesn’t show these debug-only alerts. The solution we have is not perfect, but it does avoid the worst of them. I have received so many support questions and concerns from roadster users of OVMS asking about these over the years - Tesla is aware that they false positive so labelled them as debug-only, so why would we want to bombard the user with these alerts every time he drives/charges the car?
>> 
>> Regards, Mark.
>> 
>>> On 31 Oct 2019, at 7:39 AM, Greg D. <gregd2350 at gmail.com> wrote:
>>> 
>>> Bummer.
>>> 
>>> Can we make this configurable?  While I understand that debug messages aren't intended to be seen by the user, in the 10 years since these cars launched we have come to know a lot more about some of the, um, "quirks" in their design.  These alerts can be important!  
>>> 
>>> Greg
>>> 
>>> 
>>> Mark Webb-Johnson wrote:
>>>> Greg,
>>>> 
>>>> Yes, this change to the server code:
>>>> 
>>>> * bcc02c27 Ignore DMC push alert messages
>>>> 
>>>> That won’t notify debug-only messages, but will still continue to notify the user-visible ones (to better mimick the behaviour in the car itself). Including, for the roadster:
>>>> 
>>>> 1144=DMC: Powertrain Problem Service Required
>>>> 1146=DMC: Motor Fan Problem
>>>> 
>>>> Regards, Mark.
>>>> 
>>>>> On 31 Oct 2019, at 7:01 AM, Greg D. <gregd2350 at gmail.com> wrote:
>>>>> 
>>>>> Hi folks (Mark, probably),
>>>>> 
>>>>> Interesting...  My Tesla Roadster has been having trouble with its PEM
>>>>> fan, causing a bunch of 1146 Alerts to be generated while driving and/or
>>>>> charging.  I've been monitoring the situation via OVMSv3. 
>>>>> 
>>>>> The alerts suddenly stopped a bit over a week ago.  Other events
>>>>> continue to be received (charge start, stop, key in / door open, etc.),
>>>>> but not the 1146's.  I do a monthly download of the car logs, and to my
>>>>> surprise (and disappointment), the 1146s are still happening.
>>>>> 
>>>>> Was there a change to the plumbing somewhere such that these diagnostic
>>>>> alerts (perhaps versus user-visible events) are now being filtered out? 
>>>>> 
>>>>> Thanks,
>>>>> 
>>>>> Greg
>>>>> 
>>>>> _______________________________________________
>>>>> OvmsDev mailing list
>>>>> OvmsDev at lists.openvehicles.com
>>>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> OvmsDev mailing list
>>>> OvmsDev at lists.openvehicles.com
>>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>>> 
>>> _______________________________________________
>>> OvmsDev mailing list
>>> OvmsDev at lists.openvehicles.com
>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>> 
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20191031/2f0f38d5/attachment.htm>