JOIN/SIGN UP
Already a Member? |
GET INVOLVED
Understanding and Engaging in COVESA Expert Groups & Projects |
COLLABORATIVE PROJECTS
HISTORICAL
SDV Telemetry Project - On Hold |
...
Table of Contents |
---|
Reaction to previously presented conventions, introduced
How to handle alter sampling conventions
Tooling & .csv converter topic
- no comments or offers for support so we continue here between geotab and etas
FMS-update
- Carlton explained again the background of why J1939 is a good std to abstract into our guidelines using the VSS data model
- potentially missusing overlays or need another DEG discusion required
- explained about the wishes from the fMS standards group that SAE J1939 causes them issues/cost due to being so closely copupled to CAN and HW
> (melissa request) Create an overview of what data is actually relavent for each additional field we are proposing for VSS overlay
> do we define our own DSL (data sampling Language) for measuring the data or do we want to change VSS
-currently DEG (data expert group) is discussing this topic and thinking that they need to have a way to managed this for specific vehicles
J1939 questions
- Some OEMs even considering replacing CAN with IP in the future
how do we get VSS to become protocol agnostic
- Melissa asked if we want to do something with the data >
- How do we do "plug and play" HW > can the CV BoF be a place that we also focus on this aspect of CV upfitting etc
- Suppliers & Tiers will need to focus on the lower level abstraction (ford opinion)
Cummins focus:
- Cummins to support for the FMS topic > we really need to focus on the fleet beenfits aspect
UNECE1516 direction = Operations: Warranties status & SW updates for all makes/models/components could be highly beneficial
- Should there be some sort of standard defiend in the control layer for updates etc in COVESA
...