Page History

...

Monday 2021-11-22

• )

Monday 2021-10-25

• We suggested to rework the overview picture into one part showing how components are stored in repository, and another for deployment
• LiveSim is not connected at both ends.  The diagram suggests there is a deployment where data is fed from livesim but also fed back into livesim, which doesn't make sense.  You either collect real data (from some kind of VSS Feeder writing into in-vehicle state storage) or you feed the system from the livesim.  It is true that Livesim consumes a OVDS database format, but it does not 
• Can we start using some kind of online editing tool or common format in the future? (anything that allows other people to change)
  • YEd?
  • Fallback is always PPTX file (works in MS Office and LibreOffice)

Monday 2021-08-23

• Geotab data format to VSS conversion is possible.  About 50 signal translations have been defined.
  • Data sets can then be provided (in OVDS format) 
  • Position information likely coming (pending consent).
  • examples: position, speed, ignition, oil temp, turning indicators, seat belt
  • 5-10 vehicles, that type of range.
  • How can/shall we use this data?
• Stephen reminds about VSS-formated dataset that Access has defined before (available with a demo in GitHub).
• CCS demos have before focused on Vehicle→OEM cloud parts.  Development in the usage of data, cloud based applications, and deployment/automation as previously discussed.
• Curve logging implementation in VISS is new compared to last AMM.  It can be demonstrated.
• Android app - reads from VHAL sends signal to cloud.  Opportunity to use VSS and/or VISS?

...