1 / 10

Feasibility Investigation of Hydrogen Vehicle Authorization System for Hydrogen Fueling

Feasibility Investigation of Hydrogen Vehicle Authorization System for Hydrogen Fueling. Jacquelyn Button California Fuel Cell Partnership May 5, 2010 NHA Hydrogen Conference and Expo. Background .

keziah
Download Presentation

Feasibility Investigation of Hydrogen Vehicle Authorization System for Hydrogen Fueling

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Feasibility Investigation of Hydrogen Vehicle Authorization System for Hydrogen Fueling Jacquelyn Button California Fuel Cell Partnership May 5, 2010 NHA Hydrogen Conference and Expo

  2. Background • July 2009 SAE approached CaFCP to investigate a method (hardware and signals) for Hydrogen Vehicle Authorization System • Provide signal for confirmation of authorization • Provide a means to allow for alternate fueling protocols per SAE J2601 (optional)* • Transmit secondary confirmation of 70 MPa (optional) • Evaluation/intermediate demonstration period • Project team formed September 2009 *Provide a path for continued development – enabling modifications for a more performance based approached

  3. HVAS project team

  4. Timeline

  5. Concept

  6. Hardware selection • HVAS differences from J2799 communication • Static signal at the beginning of fill • Only provides identifier signal • Hardware requirements include • Does not require control interface from vehicle ECU • Does not require external power source from vehicle • Options considered for HVAS hardware (non-J2799) • RFID • Wi-Fi • ICC • IrDA

  7. Concept cont’d OEM encodes RFID with VIN (last 6 digits unique identifiers) Central admin adds vehicle to database Dispenser identifies vehicle from database Vehicle receives fuel Non-OEM vehicle 3rd party vehicle certification

  8. Discussions • RFID location on vehicle and protocol • Reaction to unauthorized HVAS signal • Utilization of HVAS to replace PIN • Identifying central administrator • Establishing criteria for OEM HVAS signal • Finalizing fields in HVAS database

  9. Future work • RFID placement study underway • Pilot demo to begin shortly thereafter • Analysis of pilot demo and recommendations to SAE by EOY 2010

  10. Questions Jackie Button Project Engineer jbutton@cafcp.org 916.375.7421 www.cafcp.org

More Related