This content is not included in
your SAE MOBILUS subscription, or you are not logged in.
Electric Vehicle Power Transfer System Using Conductive Automated Connection Devices
- Ground Vehicle Standard
- J3105_202001
- Issued
Downloadable datasets available
Annotation ability available
Sector:
Issuing Committee:
Language:
English
Scope
This document covers the general physical, electrical, functional, testing, and performance requirements for conductive power transfer, primarily for vehicles using a conductive ACD connection capable of transferring DC power. It defines conductive power transfer methods, including the infrastructure electrical contact interface, the vehicle connection interface, the electrical characteristics of the DC supply, and the communication system. It also covers the functional and dimensional requirements for the vehicle connection interface and supply equipment interface. There are also sub-documents which are identified by a SAE J3105/1, SAE J3105/2, and SAE J3105/3. These will be specific requirements for a specific interface defined in the sub-document.
-
SAE J3105: Main document, including most requirements.
-
○
SAE J3105/1: Infrastructure-Mounted Cross Rail Connection
-
○
SAE J3105/2: Vehicle-Mounted Pantograph Connection
-
○
SAE J3105/3: Enclosed Pin and Socket Connection
-
○
Rationale
On-route conductive solutions are attractive to heavy-duty applications where down-time resulting from charge operations need to be minimized and the operator prefers to make the connection without leaving the driver's seat. The existing SAE charging standards do not address on-route conductive charging solutions that serve to promote all day operation of high capacity electric vehicles.
Recommended Content
Topic
Data Sets - Support Documents
Title | Description | Download |
---|---|---|
Unnamed Dataset 1 | ||
Unnamed Dataset 2 | ||
Unnamed Dataset 3 | ||
Unnamed Dataset 4 | ||
Unnamed Dataset 5 | ||
Unnamed Dataset 6 | ||
Unnamed Dataset 7 | ||
Unnamed Dataset 8 | ||
Unnamed Dataset 9 | ||
Unnamed Dataset 10 | ||
Unnamed Dataset 11 | ||
Unnamed Dataset 12 | ||
Table 1 | Peak-to-peak ripple | |
Table A1 | Definition of vehicle/EVSE states with PLC | |
Table A2 | Control pilot state voltage range reference from mated charge connection | |
Table A3 | EVSE control pilot circuit parameters with PLC control (see ) | |
Table A4 | EV control pilot circuit parameters with PLC control (see ) | |
Table B1 | EV control pilot circuit parameters with PLC control (see ) | |
Table C1 | Sequence description for normal start up | |
Table C2 | Sequence description for normal stop | |
Table C3 | Sequence description for DC supply initiated emergency stop | |
Table C4 | Sequence description for EV-initiated emergency stop | |
Table C1 | OEM IDs | |
Table D1 | Usage of message elements supportedAppProtocolReq | |
Table D2 | Usage of message elements supportedAppProtocolRes | |
Table D4 | Usage of message elements SessionSetupRes | |
Table D5 | Usage of message elements ServiceDiscoveryReq | |
Table D6 | Usage of message elements ServiceDiscoveryRes | |
Table D7 | Usage of message elements ServicePaymentSelectionReq | |
Table D8 | Usage of message elements ContractAuthenticationReq | |
Table D9 | Usage of message elements ContractAuthenticationRes | |
Table D10 | Usage of message elements ChargeParameterDiscoveryReq | |
Table D11 | Usage of message elements ChargeParameterDiscoveryRes | |
Table D12 | Usage of message elements PowerDeliveryReq | |
Table D13 | Usage of message elements PowerDeliveryRes | |
Unnamed Dataset 36 | ||
Unnamed Dataset 37 | ||
Table D16 | Timeout value of cable check handling | |
Table D17 | Usage of message elements CableCheckRes | |
Table D18 | Usage of message elements PreChargeReq | |
Table D19 | Usage of message elements PreChargeRes | |
Table D20 | Usage of message elements CurrentDemandReq | |
Table D21 | Usage of message elements CurrentDemandRes | |
Table D22 | Usage of message element ServiceTagType | |
Table D24 | Usage of message element ServiceType | |
Table D26 | Usage of message elements NotificationType | |
Table D28 | Usage of message elements ChargingProfileType | |
Table D29 | Usage of message elements ProfileEntryType | |
Table D31 | Usage of message elements SAScheduleTupleType | |
Table D32 | Usage of message elements PMaxScheduleType | |
Table D33 | Usage of message elements PMaxScheduleEntryType | |
Table D34 | Usage of message elements SalesTariffType | |
Table D35 | Usage of message elements SalesTariffType | |
Table D36 | Usage of message elements PMaxScheduleEntryType | |
Table D37 | Usage of message elements ConsumptionCostType | |
Table D38 | Usage of message elements CostType | |
Table D40 | Usage of message elements SlectedServiceType | |
Table D41 | Usage of message elements DC_EVSEStatusType | |
Table D42 | Usage of message elements DC_EVStatusType | |
Table D43 | Usage of message elements DC_EVChargeParameterType | |
Table D44 | Usage of message parameter DC_EVSEChargeParameterType | |
Table D45 | Usage of message parameter DC_EVPowerDeliveryParameterType | |
Table D46 | EVCC and SECC message sequence and session timing parameter values | |
Unnamed Dataset 64 | ||
Unnamed Dataset 65 | ||
Unnamed Dataset 66 | ||
Unnamed Dataset 67 | ||
Unnamed Dataset 68 | ||
Unnamed Dataset 69 |
Issuing Committee
The Hybrid Technical Standards Committee reports to the Powertrain Systems Group of the Motor Vehicle Council. The Committee is responsible for developing and maintaining SAE Standards, Recommended Practices, and Information Reports related to the field of hybrid vehicle technology. The following topics are within the scope of this committee's work: ¿ safety aspects of hybrid systems in vehicles ¿ test procedures to establish the performance of hybrid systems and components ¿ nomenclature ¿ vehicle interface and serviceability requirements Participants in the SAE Hybrid Technical Standards Committee include OEMs, suppliers, consulting firms, government, and other interested parties.
Reference
Number | Title |
---|
* Redlines comparisons are available for those standards
listed in the Revision History that contain a radio button. A
redline comparison of the current version against a revision is
accomplished by selecting the radio button next to the standard and
then selecting 'compare'. At this time, Redline versions only exist
for some AMS standards. SAE will continue to add redline versioning
with ongoing updates to SAE MOBILUS.