More Related Content
Similar to Evergreen info session2
Similar to Evergreen info session2 (20)
Recently uploaded
Recently uploaded (20)
Evergreen info session2
- 2. Outline Overview Introduction Evergreen Features New NavEngine Features Overview Consumption Model One-to-many Search Summary 1
- 3. Outline Overview Introduction Evergreen Features New NavEngine Features Overview Consumption Model One-to-many Search Summary 2 Overview
- 4. Introduction Evergreen: reduce range anxiety in Renault electric cars Evergreen has two deliverables NFA 2.5: update of TomTom NAV2 in-dash device. In Production. Used in Renault Fluence ZE cars. MM2012: part of Strasbourg Bug xing phase. This talk is about Strasbourg. 3 Overview
- 5. Evergreen Features Electric charging stations (=ePOIs) seen on map Navigate to ePOI, search for ePOIs, etc. Dynamic ePOI data from Renault server Caching of dynamic ePOI data ePOI compatibility check 4 Overview
- 6. Evergreen Features, Part 2 Consumption model yields energy estimate Driving style differences → learning driver pro le New eco-routing uses consumption model Warning in case user cannot reach destination 5 Overview
- 7. Evergreen Features, Part 3 Route colored according to reachability Patatoid = Reachable area on map Warning in case battery is low 6 Overview
- 8. Teams Involved User Interface. Map Visualization. Patatoid rendering NavEngine. Consumption model, one-to-many search DALE. ePOI data structures, ePOI caching MapToolChain. Node elevation format, ePOI format CPU. Node elevation data, ePOI data BU Automotive. Car interface, Learning Driver Pro le TTSD. User update of ePOI data 7 Overview
- 9. Challenges Lots of components involved. Communication gaps. Incomplete, inconsistent requirements from Renault Continuously changing requirements No meaningful schedule Platform changes: NFA 2.5 NAV2, Strasbourg Android 8 Overview
- 10. Outline Overview Introduction Evergreen Features New NavEngine Features Overview Consumption Model One-to-many Search Summary 9 New NavEngine Features
- 11. Overview 10 New NavEngine Features
- 12. Evergreen code base DALE and NavEngine code within NavCore: CrossPlatform/NavCore/DataCore/ElectricVehicle subdirectory functionality contained /. con guration, lifecycle /ActiveObjects route reachability, patatoid /Interfaces internal C++ interfaces /POI ePOIs, ePOI cache /Reachability consumption model /ReachabilityAreaVisualization patatoid rendering 11 New NavEngine Features
- 13. Consumption Model Necessary for patatoid, route coloring, destination ag Speci ed by Renault Rules for estimating the consumption of a single line consumption of a single line Consumption = FVehicleCons + slopeCons + auxCons Unit is energy in kWh 12 New NavEngine Features
- 14. FVehicle Consumption Speed-dependent consumption Accounts for friction, air drag FVehicle = table of consumption per distance for a given speed Example: at a speed of 70 km/h, it's 7.3 kWh per 100 km FVehicle consumption of a single line FVehicleCons = FVehicle(line speed) × length of segment FVehicle table = output of Learning Driver Pro le 13 New NavEngine Features
- 15. Slope Consumption Additional consumption when driving uphill Battery recharge when driving downhill Needs node elevation data slope consumption slopeCons = constant × carWeight × g × ∆height constant = 0.97 for uphill, 0.9 for downhill m g = 9.81 s2 ∆height = height(toNode) − height(fromNode) Check to ensure battery is not recharged beyond capacity 14 New NavEngine Features
- 16. Auxiliary Consumption Consumption due to heating, air condition, lights, etc. auxiliary consumption auxCons = auxPower × travel time of line auxPower is the auxiliary power given in Watts Delivered via re ection from car Value is unknown at system startup Special rules about what value to assume in that case 15 New NavEngine Features
- 17. Consumption Model Summary Consumption of single line: sum of three parts FVehicle consumption. Uses Learning Driver Pro le output Slope consumption. Uses node elevation Auxiliary consumption. Uses auxilary power from car Needs: Node elevation data Weight of car, auxiliary power, FVehicle table Necessary for: 16 New NavEngine Features
- 18. One-to-many Search Search in all directions from current position Similar to route planning, but without destination For all possible optimal routes, applies consumption model to check how much energy is needed Needed for: patatoid shape, exact ePOI distances 17 New NavEngine Features
- 19. Outline Overview Introduction Evergreen Features New NavEngine Features Overview Consumption Model One-to-many Search Summary 18 Summary
- 20. Summary Evergreen: reduce range anxiety in Renault electric cars Electric charging stations Node elevation data Consumption model. Used for: 19 Summary