[Ovmsdev] Ampera remote start/stop function

Mon Feb 25 00:25:06 HKT 2013

I've been working through the logs (if anyone else needs a look, let me know).

I started by converting to crtd format, so I could use some of my tools on it.

Looking at a bunch of other logs provided by volt/ampera drivers, we've so far seen 108 unique can arbitration IDs:

096 097 098 0AA 0B1 0B9 0BA 0BB 0BC 0BD 0C1 0C4 0C5 0C7 0C9 0D1 0D3 0F1 101 120 12A 130 135 137 139 140 148
160 17D 182 185 186 1A1 1A3 1C3 1C4 1C5 1C6 1DF 1E1 1E5 1E9 1EB 1ED 1EF 1F1 1F3 1F4 1F5 1FB 200 202 204 206
214 222 224 226 228 230 236 238 287 2C3 2C7 2F1 2F9 32A 32C 348 34A 3C1 3C9 3CB 3D1 3DC 3DD 3E3 3E9 3ED 3F1
3F9 3FB 3FC 451 4C1 4C5 4C7 4C9 4CB 4D1 4D7 4D9 4E1 4E9 4F1 500 514 52A 530 589 770 772 773 778 77D 77F 787

Looking at your logs, I see five new ones have shown up:

22A 362 385 7E4 7EC

22A is jumping all over the place. 362 is all zeros. 385 is zeros up until 10:56:05.178, when it changes to show what may be temperature, and then at 10:57:47.007 it seem to switch back to zeros.

The 7E4 and 7EC ones are the most interesting, as they are OBDII style request/response. Here are the relevant logs:

10:44:47.323 R11 7E4 02 1A A5 00 00 00 00 00
10:44:47.335 R11 7EC 04 5A A5 01 03 AA AA AA

10:44:47.533 R11 7E4 03 22 83 77 00 00 00 00
10:44:47.536 R11 7EC 06 62 83 77 06 0A 2D AA

10:44:47.744 R11 7E4 02 1A A4 00 00 00 00 00
10:44:47.746 R11 7EC 10 09 5A A4 1C 1C 1C 1C

10:44:47.762 R11 7E4 30 00 00 00 00 00 00 00
10:44:47.766 R11 7EC 21 1C 1C 1C AA AA AA AA

10:44:48.622 R11 7EC 07 62 41 AB 00 00 00 00

10:44:49.105 R11 7E4 03 22 41 AC 00 00 00 00
10:44:49.187 R11 7E4 03 22 41 AB 00 00 00 00
10:44:50.011 R11 7E4 03 22 43 9B 00 00 00 00
10:44:50.309 R11 7E4 03 22 83 E1 00 00 00 00
10:44:50.680 R11 7E4 03 22 83 75 00 00 00 00
10:44:50.683 R11 7EC 06 62 83 75 06 0A 2D AA

10:44:50.757 R11 7E4 03 22 41 A6 00 00 00 00
10:44:52.575 R11 7E4 03 22 43 89 00 00 00 00

Note that 7E4 is the Hybrid Powertrain Control Module B, and 7EC is the reply to that request.

OBDII standard requests are:
0x01 - Request Current Powertrain Diagnostic Data
0x02 - Request Powertrain Freeze Frame Data
0x03 - Request Emission-Related Diagnostic Trouble Codes
0x04 - Clear/Reset Emission-Related Diagnostic Information
0x05 - Request Oxygen Sensor Monitoring Test Results
0x06 - Request On-Board Monitoring Test Results for Specific Monitored Systems
0x07 - Request Emission-Related Diagnostic Trouble Codes Detected During Current or Last Completed Driving Cycle
0x08 - Request Control of On-Board System, Test or Component
0x09 - Request Vehicle Information
0x0A - Request Emission-Related Diagnostic Trouble Codes with Permanent Status
GMLAN enhanced services are:

0x10 - Initiate Diagnostics
0x12 - Read Failure Record
0x1A - Read Diagnostic ID (DID)
0x20 - Return To Normal
0x22 - Read Data By Parameter ID (PID)
0x23 - Read Memory Address
0x27 - Security Access
0x28 - Disable Normal Communications
0x2C - Define Dynamic Data Packet ID (DPID)
0x2D - Define PID by Memory Address
0x34 - Request Download
0x36 - Transfer Data
0x3B - Write DID
0x3E - Tester Present
0xA2 - Report Programming State
0xA5 - Enter Programming Mode
0xA9 - Check Codes
0xAA - Read DPID
0xAE - Device Control
So, what we are seeing is:

10:44:47.323 R11 7E4 02 1A A5 00 00 00 00 00
==> Read diagnostic ID A5
10:44:47.335 R11 7EC 04 5A A5 01 03 AA AA AA
==> Respond diagnostic ID A5 is 0103

10:44:47.533 R11 7E4 03 22 83 77 00 00 00 00
==> Request extended PID 8377
10:44:47.536 R11 7EC 06 62 83 77 06 0A 2D AA
==> Respond extended PID 8377 is 060A2D

10:44:47.744 R11 7E4 02 1A A4 00 00 00 00 00
==> Read diagnostic ID A4
10:44:47.746 R11 7EC 10 09 5A A4 1C 1C 1C 1C
==> Weird response - seem shifted over one. But, presumably a response to diagnostic ID A4. Maybe corrupt in the log?

10:44:47.762 R11 7E4 30 00 00 00 00 00 00 00
==> Bizarre. Corrupt?
10:44:47.766 R11 7EC 21 1C 1C 1C AA AA AA AA
==> Bizarre. Corrupt?

10:44:48.622 R11 7EC 07 62 41 AB 00 00 00 00
==> Response to an extended PID request for 41AB, value 000000

10:44:49.105 R11 7E4 03 22 41 AC 00 00 00 00
==> Extended PID request for pid 41AC
10:44:49.187 R11 7E4 03 22 41 AB 00 00 00 00
==> Extended PID request for pid 41AB
10:44:50.011 R11 7E4 03 22 43 9B 00 00 00 00
==> Extended PID request for pid 439B
10:44:50.309 R11 7E4 03 22 83 E1 00 00 00 00
==> Extended PID request for pid 83E1
10:44:50.680 R11 7E4 03 22 83 75 00 00 00 00
==> Extended PID request for pid 8375
10:44:50.683 R11 7EC 06 62 83 75 06 0A 2D AA
==> Respond extended PID request for pid 8375, value 060A2D

10:44:50.757 R11 7E4 03 22 41 A6 00 00 00 00
==> Extended PID request for pid 41A6
10:44:52.575 R11 7E4 03 22 43 89 00 00 00 00
==> Extended PID request for pid 4389

The log file has  a large number of 'data overrun errors' around 10:44:48 and 10:44:49 - I suspect that a few of few of the requests/replies were lost around that time. The start (10:44:47) of the log looks ok.

Looking at the idle can bus from 10:41, waking up at 10:44 is interesting:

10:41:37.203 R11 2C3 06 59 06 A0 06 A0 CA 00
10:41:37.203 R11 3D1 01 36 80 00 00 00 00 00
10:41:37.203 R11 3E9 00 00 00 00 00 00 00 00
10:44:47.323 R11 7E4 02 1A A5 00 00 00 00 00
10:44:47.335 R11 7EC 04 5A A5 01 03 AA AA AA
10:44:47.353 R11 1EB 02 52

It certainly looks like the 7E4 02 1A A5 00 00 00 00 00 woke things up.

I'll keep looking, but it seems that the log file is inconsistent as the logger got overloaded.

Regards, Mark

On 23 Feb, 2013, at 3:13 AM, rgjones at sbcglobal.net wrote:

> 
> Hello Folks,
> I just captured CAN data during onstar commands for remote start/stop lock/unlock.
> Below are my notes.  Where should I send the log file?
> Regards,
> Richard
> San Diego
> 2013 Volt #119292
> 
> Fri Feb 22, 2013 10am PST
> VIN: 1g1re6e49du119292
> 
> Car plugged in, locked, finished charging (green led blinking)
> 
> walk up to car
> fob - unlock
> open passenger door - get in
> close passenger door.
> 10:41
> start android onstar app
> request status update (push refresh icon on app) 
> 10:43 - app shows doing refresh
> see CAN activity
> 10:44 app finally updates - 120V battery fully charged 36 mile ev range 152 fuel range  Oil life remaining 86% odo 3955 miles
> 10:45 can updates stop
> onstart remote door lock
> 1052 - sent lock cmd
> 1052 locked - lots of can
> 1053 remote start sent.  failed as key in vehicle 1054
> 1054 remote unlock 1054 done
> 1055 leave via passenger door, close it.
> keyfob lock 1055
> leave key out of range of the car
> 1055 remote start req 
> 1056 app says "cabin temp being set for optimal comfort"
> lots of CAN
> Dash still off, but orange engine light is on.
> 1057 send cancel engine start.
> 1057 - engine light off - app says done
> 
> 
> -rw-r--r-- 1 root root 17471412 2013-02-22 10:59 volt_130222_1_CAN_log.txt
> Fri Feb 22, 2013 10am PST
> VIN: 1g1re6e49du119292
> 
> 
> Car plugged in, locked, finished charging (green led blinking)
> 
> walk up to car
> fob - unlock
> open passenger door - get in
> close passenger door.
> 10:41
> start android onstar app
> request status update (push refresh icon on app) 
> 10:43 - app shows doing refresh
> see CAN activity
> 10:44 app finally updates - 120V battery fully charged 36 mile ev range 152 fuel range  Oil life remaining 86% odo 3955 miles
> 10:45 can updates stop
> onstart remote door lock
> 1052 - sent lock cmd
> 1052 locked - lots of can
> 1053 remote start sent.  failed as key in vehicle 1054
> 1054 remote unlock 1054 done
> 1055 leave via passenger door, close it.
> keyfob lock 1055
> leave key out of range of the car
> 1055 remote start req 
> 1056 app says "cabin temp being set for optimal comfort"
> lots of CAN
> Dash still off, but orange engine light is on.
> 1057 send cancel engine start.
> 1057 - engine light off - app says done
> 
> 
> -rw-r--r-- 1 root root 17471412 2013-02-22 10:59 volt_130222_1_CAN_log.txt
> gzip volt_130222_1_CAN_log.txt 
> tattler:~# tail volt_130222_1_CAN_log.txt 
> 10:58:02.055852 S. id=0x000001c4 dat=0xca:0x62:0xc1:0x10:0x04:0x00:0x03:0xfe
> 10:58:02.057282 S. id=0x000001c5 dat=0x2c:0x03:0x2c:0x03:0x2e:0x01
> 10:58:02.058671 S. id=0x000001f4 dat=0x00:0x00:0x00:0x00:0x00:0x00
> 10:58:02.060073 S. id=0x00000287 dat=0xc1:0x00
> 10:58:02.062044 S. id=0x000002c3 dat=0x06:0x5b:0x06:0xa0:0x06:0xa0:0xca:0x00
> 10:58:02.062468 S. id=0x000000bc dat=0x37:0x00:0x00:0x40:0x00:0x00:0x00:0x00
> 10:58:02.062785 S. id=0x000000aa dat=0x2c:0x03:0x2c:0x03:0x04:0x53:0xfb:0x00
> 10:58:02.063088 S. id=0x000000c9 dat=0x00:0x00:0x00:0x27:0x00:0x10:0x08:0x00
> 10:58:02.063392 S. id=0x000001ed dat=0x01:0x90:0x00:0x00:0x00:0x00:0x18:0x01
> 10:58:02.063691 S. id=0x000001ef dat=0x00:0x00:0x00:0x00
> gzip volt_130222_1_CAN_log.txt 
> -rw-r--r-- 1 root root 1888643 2013-02-22 10:59 volt_130222_1_CAN_log.txt.gz
> 
> 
> 
> --- On Sat, 2/16/13, Mark Webb-Johnson <mark at webb-johnson.net> wrote:
> 
> From: Mark Webb-Johnson <mark at webb-johnson.net>
> Subject: Re: [Ovmsdev] Ampera remote start/stop function
> To: "OVMS Developers" <ovmsdev at lists.teslaclub.hk>
> Date: Saturday, February 16, 2013, 12:03 AM
> 
> Rens,
> 
> The car-side technical discussion is going on here:
> 
> http://gm-volt.com/forum/showthread.php?12958-CAN-bus-reading-remote-viewing-of-charge-state
> 
> We're after pretty much the same things as the DashDaq people, so there is a lot of overlap.
> 
> From the App, it is no problem. We can use HomeLink for testing at the moment, and implement something properly when we know it is feasible.
> 
> The problem is that we need CAN bus dumps while OnStar / KeyFob pre-heat and remote start/stop is commanded. For that, we need someone with a Volt in the USA and CAN-USB logger to help us try to find the commands.
> 
> Regards, Mark.
> 
> On 16 Feb, 2013, at 7:56 AM, Rens Meijer <r.meijer at atlantis-it.nl> wrote:
> 
>> Hello,
>>  
>> Last week I received the OVMS V2 module to monitor my Ampera. I already had an OVMS V1 module to monitor the Tesla Roadster, so it works nicely from 1 app.
>>  
>> In winter I like the remote start/stop function of the Ampera to pre-heat the car.
>> I found this Youtube that in the US it is possible with the OnStar system to remote start/stop the car. See at 2.21 in the movie.
>> http://www.youtube.com/watch?v=IOJMVbQnNIU&sns=em
>> Has somebody already made a CAN bus log during the remote start/stop by using the remote control? If you are able to find the sequence, how easy would it be to configure the current home buttons in the app to implement the start/stop function?
>> I would like to hear your thoughts on this?
>>  
>> Best Regards,
>>  
>> Rens
>>  
>>  
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.teslaclub.hk
>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
> 
> 
> -----Inline Attachment Follows-----
> 
> _______________________________________________
> 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/20130225/783e4753/attachment.htm>