General Disclaimer:   (HV) (DC) injury or death hazard,   use at your own risk,   may void warranty.

Difference between revisions of "Talk:Plug-In Hybrids"

From My wiki
Jump to navigation Jump to search
(Standards)
(→‎Standards: sounds good.)
Line 10: Line 10:
 
In the navigation menu, I would place the PHEV standards page under the Plug-In Hybrids heading, after the link to the Terms page.
 
In the navigation menu, I would place the PHEV standards page under the Plug-In Hybrids heading, after the link to the Terms page.
 
[[User:DavideAndrea|DavideAndrea]] 08:46, 23 January 2007 (CST)
 
[[User:DavideAndrea|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. --[[User:Rjf|Rjf]] 08:40, 25 January 2007 (CST)

Revision as of 14:40, 25 January 2007

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)