Communication for Plug-in Electric Vehicles Ford Advanced Vehicle Technology

Format:

Conference/Event

Author/Creator:

Scholer, Scholer, author.

Contributor:

Bourton, Michael

Fietzek, Cliff

Godfrey, Tim

Maitra, Arindam

Mepham, Dan

Müller, Michael

Oliver, Doug

Taha, Eloi

Venkatesh, Donthy

Conference Name:

SAE 2012 World Congress & Exhibition (2012-04-24 : Detroit, Michigan, United States)

Language:

English

Physical Description:

1 online resource

Place of Publication:

Warrendale, PA SAE International 2012

Summary:

This paper is the third in the series of documents designed torecord the progress on the SAE Plug-in Electric Vehicle (PEV)communication task force. The initial paper (2010-01-0837)introduced utility communications (J2836/1 and J2847/1) andhow the SAE task force interfaced with other organizations. Thesecond paper (2011-01-0866) focused on the next steps of theutility requirements and added DC charging (J2836/2 andJ2847/2) along with initial effort for Reverse Power Flow(J2836/3 and J2847/3). This paper continues with thefollowing: 1. Completion of DC charging's 1st step publicationof J2836/2 and J2847/2. 2. Completion of 1st step ofcommunication requirements as it relates to PowerLine Carrier (PLC)captured in J2931/1. This leads to testing of PLC products forUtility and DC charging messages using EPRI's test plan andschedule. 3. Progress for PEV communications interoperability inJ2953/1.The Use cases, general information and architecture are alsobeing developed and/or updated for the following. 4. Reverse PowerFlow (J2836/3 and J2847/3), 5. Diagnostics (J2836/4 andJ2847/4), 6. Customer to PEV and HAN/NAN communication (J2836/5& J2847/5).The existing approach continues for these documents whereas theJ2836 series to capture the use cases and general informationthat feeds into the J2847 series with corresponding specificrequirements. J2931/1 includes the overall and protocolrequirements and J2953 includes the interoperability criteria.The SAE document partitioning allows the teams to focus onspecific functions but also allows combinations that build on eachother (e.g., Reverse Power Flow with off-board conversion wouldinclude the DC communication requirements and only add theadditional criteria for that aspect of Reverse Power Flow (RPF),including architecture variations).These documents are also expected to progress thru at leastthree ballot steps with Step 1 being "what we thinkworks," Step 2 "implement and updatechanges/additions" and Step 3 being a final review andclean-up. However, more intermediate steps may occur as needed. Theintent of these standards is to capture the requirements andoptions that will enable opportunities for the customer to have abetter experience with the PEV

Notes:

Vendor supplied data

Publisher Number:

2012-01-1036

Access Restriction:

Restricted for use by site license