Please visit the Conversion Interest page to help us gauge DIYers interest!

We Support Net Neutrality, please visit battleforthenet.com and savetheinternet.com and wikipedia.org/wiki/Net_neutrality for more information.

Talk:Plug-In Hybrids

From EAA-PHEV

Jump to: navigation, search

Contents

[edit] Standards

I was thinking we need a page for PHEV standards (for any vehicle). In particular, I would like a place where standards are developed among the community of PHEV designers. Presently, I am working on a proposal for standards used in presenting the detailed status of the PHEV conversion on the CAN bus and on a computer interface. The data could be:

  • actual pack info: voltage, current, resistance, average temperature, state of charge, calendar age, usage, number of block with highest resistance, number of block with lowest capacity
  • info on individual blocks: block number, voltage, temperature, resistance...
  • info on the PHEV system: machine state, plug state, charger state, charge time, initial SOC, voltage and temperature, final SOC, voltage and temperature...

The data could be available:

  • on the CAN bus, for a CAN Data Logger
  • on a separate serial port (RS232, USB), for a laptop (for display or data logger application)

In the navigation menu, I would place the PHEV standards page under the Plug-In Hybrids heading, after the link to the Terms page. DavideAndrea 08:46, 23 January 2007 (CST)

That sounds like a great idea! Though I'm not sure I'm going to be much help in determining which packet ID's or the structure for such messages. I would be sure to develop them in a manner to maximize their flexibility for future use by many different projects. Plan for system voltages up to 600 volts with the smallest cell values (Ni) at 1.2vpc for about 500, call it 512 individual blocks each potentially reporting their ID, Voltage, Temp, Resistance, Current, etc. We might even consider the possibility of multiple semi-independent systems in the same vehicle each with their own "machine ID" as part of their packets? Perhaps I'm going a little overboard here, just some thoughts. Anyway, feel free to get started on a new section or entirely new page and I'll add it to the main menu once it reaches that point. --Rjf 08:40, 25 January 2007 (CST)
Thanks.

I'll create a page called PHEV Standards, and start with the above mentioned project. If and when this issue becomes too large, we could create a page just for it, and point to it from the Standards page.

By the way, I may be working with the SAE on this, but I'd try to use this wiki for the work.

Thanks, DavideAndrea 18:45, 25 January 2007 (CST)

[edit] Converted PHEV Vehicles Data

I need to work out a better way to organize converted vehicle data, perhaps by using vehicle templates and a formatting template? So, each vehicle might get it's own template, which could then be categorized by make, model, location, etc... These vehicle templates might then call on a formatting template to keep the layout uniform. The vehicle templates might call this formatting template with something like:

{{PHEVs|make=Toyota|model=Prius|year=2004|date=Fall 2004
|name=CalCars [[PriusPlus]] and http://calcars.org
|converter=[[User:Rgremban]], [[EDrive|EnergyCS]], and CalCars
|info=[[PriusPlus History]]
|image=[[Image:Local Image]]
|country=US
|state=CA
|city=Palo Alto
|range_deplete=10
|range_blended=20
|battery_capacity=3.2kWh
}}

Then vehicle templates could be included in a full list, or parsed by something like the Extension:DynamicPageList

Personal tools