[Ovmsdev] Volt/Ampera CAN Logs

mikeljo at mac.com mikeljo at mac.com
Thu Jun 28 22:09:37 HKT 2012


Hi,

i think too that this are total separated Buses.
-> Multi CAN Monitor! :-)

tonight i send the LOGs and the cycling IDs i found. BTW: the logs from yesterday are from the main CAN Bus DS.


Bye
Michael


Am 28.06.2012 um 15:05 schrieb Mark Webb-Johnson:

> Michael,
> 
> I looked at your previous two log files (DS and RH), and they don't seem to match-up with the powertrain logs from before. I think these are completely separate buses with completely separate data, rather than sources of data multiplexed onto the one bus.
> 
> Regarding the counters, it is common to see increasing counters (odometer, trip, kWh used, etc), but seems strange they would cycle after just 4, particularly as you describe.
> 
> Regards, Mark.
> 
> On 28 Jun, 2012, at 8:29 PM, mikeljo at mac.com wrote:
> 
>> Hi,
>> 
>> yesterday i got some Logs.
>> I do one log for each action. Lock/unlock car, open/close door, Remote start, Plugin/remove Charging Plug, .....
>> I do the action in 5 second interval.
>> I think i found some IDs.
>> And i found something interesting: Some IDs cycle 4 with 4 times Blocks. That mean there is a counter or an adress field in one data field that repeats after 4 times. It counts like 10 20 30 40, FF FE FD FC, or...... the rest of the data fields change there value.
>> Can anybody confirm?
>> Didi anybody see this before?
>> I can see this after sort the Logs (Excel). As Sort field i use the ID. So i can see the value changing over time.
>> 
>> Bye
>> Michael
>> 
>> 
>> 
>> Am 11.06.2012 um 16:39 schrieb Michael Jochum:
>> 
>>> Hi,
>>> 
>>> today i got some Logs from both Expansion Buses (DS (Chassis Expansion), RH(High Voltage Powertrain Expansion), Pin 12 and 13). Made an Cable for this.
>>> The trc are the time stamped Logs. The txt show only the IDs, the last Values and some comments from me.
>>> Unfortunately both stops after 5-10 seconds the car switched of.
>>> Car stands still. Clear sky view.
>>> 
>>> <20120612-Michas Volt Logs>
>>> 
>>> Next i made a Cable for the RH High Voltage Energy Management BUS (Pin 3 and 11) and than a cable for the Low Speed GMLAN (SWCAN ~33.3kbps) - Body Electrical Services Only  at Pin 1 DS. 
>>>  
>>> Bye
>>> Michael
>>> 
>>> 
>>> 
>>> Am 02.06.2012 um 18:45 schrieb R. Scott Perry:
>>> 
>>>> Hi Michael,
>>>> 
>>>> I cannot find the data from 32A does not appear elsewhere in the logs.
>>>> 
>>>> My guess is that OnStar uses a separate GPS system than the navigation, and OnStar sends the latitude/longitude on 32A, and the navigation system sends it on a different bus (or, hopefully, on the same bus but with a different CAN ID).
>>>> 
>>>> I'll take a look at your log file, and see if I can find the GPS information, if it is in there.
>>>>                    -Scott
>>>> 
>>>> 
>>>> On 6/2/2012 7:16 AM, Michael Jochum wrote:
>>>>> Hi Scott,
>>>>> 
>>>>> can you check that the data from ID 32A is somewhere else in your logs?
>>>>> in mine 32A is always zero. We have here no OnStar. But i have the full package including Navigation.
>>>>> 
>>>>> Bye
>>>>> michael
>>>>> 
>>>>> 
>>>>>> 
>>>>>> The latitude/longitude conversion is almost the same as what you have for the Tesla, with two exceptions -- changing the 2048 to 1000, as noted, and the accounting for negative numbers is different.  It seems that the number the Volt supplies is a 31-bit signed integer.  The easiest way to handle that, I think, would be to add "latlon = latlon<<  1;" before checking for<0, and then "latlon = latlon>>  1;" afterwards.  Running the code you have with those two changes seems to work fine.
>>>>>> 
>>>>>> The bad news is that I have checked all my log files (I have been logging almost all the time I have driven for about 8 months now), and the CAN ID 32A (latitude/longitude) has never shown all zeroes.  If the GPS data is unobtainable, I believe the car reports the most recent reading.  The GPS data comes from the OnStar system, so I am thinking it may only provide the data if the OnStar service has been activated, which could be a problem for owners outside of U.S/Canada.
>>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> OvmsDev mailing list
>>>>> OvmsDev at lists.teslaclub.hk
>>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>>>> 
>>>> _______________________________________________
>>>> OvmsDev mailing list
>>>> OvmsDev at lists.teslaclub.hk
>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>> 
>>> _______________________________________________
>>> OvmsDev mailing list
>>> OvmsDev at lists.teslaclub.hk
>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>> 
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.teslaclub.hk
>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
> 
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20120628/f71a12a1/attachment.htm>


More information about the OvmsDev mailing list