PLATON Mock-Up calculating SOC

Introduction

How-To

1. select the NMEA logfile
2. enter a cut off time of "02/14/18 12:10:08"
3. set Power of charging pause 1 to zero (actually the stop is due to congestion)
4. click on calculate
5. you might enter one additional charging pause by clicking in the map (timestamp should be before cut-off time), position 2 is a candidate

It is now possible uploading own GPS/GNSS files (first click on the checkbox nearby), please test with GLONASS readings.

If you are bus operator please also fill in the questionnaiere, so we may adapt our work to your needs, many thanks

Development level 24.4.2018

The model ist charging agnostic, i.e. the charging method may be conductive or inductive. The only type of charging which is not implemented, is charging while driving. For inductive charging the charging efficinecy may be lowered.

1. Vehicle translation: complete taking real efficiency of a battery electric power train, but no resistive losses in the accumulator, assumption for rotational masses to be validated, vehicle library to choose from appreciated, define passengees leaving/boarding at stops.
2. Drive train: efficiency map introducted for motor and generator (estimation), max. powe and efficiency when exceeding max. power assumed.
3. Charging: max. charging power depends on the SOC (simple model with linear dependency),, efficiency could be detailed, time to disconnect to be considered in the simulation
4. Heat demand: actually minimum convective heat loss defined, velocity adds to that: model to be refined, heat pump to be included, ancillary energy demand to be validated (also for BMS).
5. Data quality velocity: 5 past measurements (measured at 5 Hz) taken, with different filters depending on variance, targeting to take an average of two GPS modules, positioned at different locations in the bus, filtering should be evaluated, python software for recording from two GPS receivers at 5 Hz to be improved, so average position is taken, or weighted average (with HDOP).
6. Customisation: choosing own GPS log files possible, GPS-logs may be restricted to a defined timestamp.
7. User Support: potential pauses are indicated via numbers, non active strech is greyed out.
8. Usability: validation of user entries against boundaries, storing user input (with user registration).
9. Added functionality: variation of energy storage and chargung power to satisfy SOC-requirements, calculation of total cost of ownership, automatic position determination for first completed tour not yet implemented but colored circles for start and stop .
10. What-If-scenarios to be applied manually:
    • How will costs change if the time at the turning point is elongated?
    • Where placing the turning point for two lines running partly parallel.
    • should parallel lines be separated allowing faster cheaper charging
    • is ubiquitious inductive charging an option - cost-wise?
    • how local energy storage may reduce infrastructure cost?