General Requirements:
a) Needs to generate 1kHz PWM signals of duty cycles ranging from 10% to 66% (Page 12) and 100% (I think for 12V idle state which has no frequency (Page 11))
a.1) Needs to switch duty cycles depending on how many EVs are plugged in
b) Needs to notice amplitude changes in control pilot
b.1) Needs to recognize 6 voltage levels (12V, 9V, 6V, 3V, 0V, and -12V, or more correctly, 6 voltage levels from 3.3V to -3.3V)
c) Needs to output ac or dc to actuators
c.1) Depending on choice of actuators, timing may be crucial. Solid state relays for example
d) Needs to recognize voltage in proximity pilot circuit (Page 14 Through 16)
d.1) Reveals what current rating for cable
d.2) Does not allow actuators to be activated until 1.5V is generated (Page 14)
e) Needs to receive input from current sensors and record values for billing purposes
e.1) Needs sufficient permanent storage
f) Possibly code for power savings, (likely will be copy and paste)
g) Watchdog code if software gets stuck (defined by pointer movement specifically)
Runtime Duration:
a) Structure the software so it can aptly react to EV input, (should be pretty easy, performance is not too important)
a.1) If solid state relays are used and shutting them off at the wave node is important, this criterion becomes incredibly important
Power Allocation Schema:
a) Takes user input about battery life and/or expected time of charger use. No input at all is also accepted.
a.1) Write a formula that relates battery life to time that switching device is on.
User Interface:
a) Informs user of how many plugs are in use
b) Allows user to input parameters like battery life and/or expected time of charger use. This should be touch screen.
c) Has alarm state that notifies the user that the charge is inaccessible
(Possibly) LED that indicates alarm state:
a) Visible from a driving distance so that cars know the charger is non-functional before pulling into the spot. Remember, a lot of EV have their charge port in the back and a lot of drivers are really bad at reverse parking.
Charging algorithms:
a) One at 208V 40A (Residential setting)
b) One at 220V 40A (Commercial setting)
c) The user inputs their battery level and the algorithm incorporates that. User could also input their vehicle size so we could use their battery capacity in the calculations as well. Time of day might be another parameter.
d) The manuals have a simple formula for calculating duty cycle from number of amps desired. We should create simple formulas as well
e) If the user doesn't specify then there is a default charging schema, and likely they are a lower priority since they didn't bother to specify anything
f) Ideas to start:
f.1) Find out how much power is given to a battery in 10 minutes. That will give some scale.
f.2) Gather a list of what batteries are on the market and their capacities. Here is a list of batteries (Smart car-16.5KWh, Hummer-246KWh, Model 3-50 to 82KWh
General Requirements: a) Needs to generate 1kHz PWM signals of duty cycles ranging from 10% to 66% (Page 12) and 100% (I think for 12V idle state which has no frequency (Page 11)) a.1) Needs to switch duty cycles depending on how many EVs are plugged in b) Needs to notice amplitude changes in control pilot b.1) Needs to recognize 6 voltage levels (12V, 9V, 6V, 3V, 0V, and -12V, or more correctly, 6 voltage levels from 3.3V to -3.3V) c) Needs to output ac or dc to actuators c.1) Depending on choice of actuators, timing may be crucial. Solid state relays for example d) Needs to recognize voltage in proximity pilot circuit (Page 14 Through 16) d.1) Reveals what current rating for cable d.2) Does not allow actuators to be activated until 1.5V is generated (Page 14) e) Needs to receive input from current sensors and record values for billing purposes e.1) Needs sufficient permanent storage f) Possibly code for power savings, (likely will be copy and paste) g) Watchdog code if software gets stuck (defined by pointer movement specifically)
Runtime Duration: a) Structure the software so it can aptly react to EV input, (should be pretty easy, performance is not too important) a.1) If solid state relays are used and shutting them off at the wave node is important, this criterion becomes incredibly important
Power Allocation Schema: a) Takes user input about battery life and/or expected time of charger use. No input at all is also accepted. a.1) Write a formula that relates battery life to time that switching device is on.
User Interface: a) Informs user of how many plugs are in use b) Allows user to input parameters like battery life and/or expected time of charger use. This should be touch screen. c) Has alarm state that notifies the user that the charge is inaccessible
(Possibly) LED that indicates alarm state: a) Visible from a driving distance so that cars know the charger is non-functional before pulling into the spot. Remember, a lot of EV have their charge port in the back and a lot of drivers are really bad at reverse parking.
Charging algorithms: a) One at 208V 40A (Residential setting) b) One at 220V 40A (Commercial setting) c) The user inputs their battery level and the algorithm incorporates that. User could also input their vehicle size so we could use their battery capacity in the calculations as well. Time of day might be another parameter. d) The manuals have a simple formula for calculating duty cycle from number of amps desired. We should create simple formulas as well e) If the user doesn't specify then there is a default charging schema, and likely they are a lower priority since they didn't bother to specify anything f) Ideas to start: f.1) Find out how much power is given to a battery in 10 minutes. That will give some scale. f.2) Gather a list of what batteries are on the market and their capacities. Here is a list of batteries (Smart car-16.5KWh, Hummer-246KWh, Model 3-50 to 82KWh