Page History

...

Value measurement formats

Wednesday 2020-09-02

Recap of implementation plan and status.

The plan/status table in CCS Proof-Of-Concept - Work Breakdown Structure is a bit outdated (wrong(?) responsibles, wrong plan).
It still needs a bit of an update.  For now taking the notes here.

In Vehicle Server : still W3C_VehicleSignalInterfaceImpl

State Storage : Implemented by statestorage dir in ccs-w3c-client
Connection vehiclesever to statestorage is in ovds client / server in same repo

Demo Goal

Vehicle/OEM cloudside

- Data collection into state storage by driving the simulator around
- Gen2 server support get/set and subscription
- (Subscription using timer should work, but is not change triggered yet)
- OEM Cloud: Vehicle client can be set to send requests on a timer. Using a file to list signals.
- Stores data with timestamps into database
- Aim for signals that can be graphed
- How to visualize? Grafana. First approach integrate with sqlite according to current schema.

Neutral-Cloud-side
- Swift app with GraphQL client (mostly exists)
- Fetches data from GraphQL server in OEM cloud (server not yet started)
- Shown in a iOS application
- Easiest to go directly to OEM cloud for this demo

Remaining work:

• Integration OpenDS to statestorage (Gunnar)
  • Define the signals that we expect to have (from OpenDS) --> Swift App can use
• !! GraphQL to OEM database integration (?)
• Grafana investigation and integration (Gunnar?)
• + "Fake" data feeder for Electrical Vehicle related signals
  • list of signals need to match OpenDS is delivering
• packaging/testing, preparation
• (Optional) Subscription hook on new value / change - make server aware

Side tracks:

•  Consider using influxdb instead in cloud (database optimized for time series data)

Monday,  July 27 - Vehicle Data Model, Common Vehicle Interface Initiative

...