Versions Compared

Old Version 4

changes.mady.by.user Ulf Bjorkengren

Saved on

compared with

New Version Current

changes.mady.by.user Ulf Bjorkengren

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

See COVESA Common Meeting Schedule for meeting link. The meeting is open to anyone.

Policies

  • CVIS-status-2024-fall.pptxIt is expected that all meeting participants have read the compliance statement. Every meeting will start with a reminder.

  • Every meeting will start with appointment of note taker. Notes can be on-line, or off-line and if so mailed to moderator within 24 hours. Fair scheduling, i. CVIS-file-repoe. all should take turn. A reason for not taking it is if one expect to speak much at the meeting.

  • Strive for making signal objects reusable by other signal specifications. 

...

  • Compliance statement
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized Topics:
    • xxx
  • General topics:
    • Open Pull Requests CVIS
    • Issues CVIS
    • Discussions CVIS
  • Other
  • Prioritized topics for next meeting


Meeting notes  2024-09-09

  • Compliance statement
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized Topics:
    • use vsspathlist.json to vet the content of the Truck tree.
    • Cargo location - to be continued.
      • Example scenario of a truck being loaded?
    • Next meeting sept 23 is cancelled as it is the same week as the AMM.
    • Todays meeting was cut short due to low participation.

Meeting notes  2024-08-26

  • Other
    • Review AMM presentation draft

Meeting notes  2024-08-12

  • Compliance statement
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized Topics:
    • Proposal on new domain structure built on Cargo variations. 
      • Wally: No formal standardization today. Tire as location reference. Three levels, 6 "doors", compartments. Fleets interested to discuss this. TMC f2f mid Sept. We should try to come up with proposals.
    • CVIS issues
      • Data recorder/Driver data
        • Tech stack example for driver recorder use case. HIM config tree added after the meeting. Ulf to explain in next meeting.
        • Truck/Driver trees contain metadata for the represented signals, actual (transient) data is in the state storage data buffer. Driver recorder unit may contain data from multiple drivers. How represent these multiple "driver instances" in the data model?
        • Driver recorder specific data (type, version, time-to-calibration, etc) should be represented in the Truck tree.
    • HIM configurator demo. Moved to next meeting.
  • Other
    • Status update presentation at the AMM
      • Will be presented at the CV expert group presentation on Wed. Ted will sync it.
        • Ulf create first proposal.

Meeting notes  2024-07-15

  • Compliance statement
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized Topics:
  • Other
    • Summer recess
      • Skip the meeting on July 29. Next meeting Aug 12. 
    • Status update presentation at the AMM
      • Ulf willing to present. Wally interested. Possibly Ted. Ulf to submit to Paul's request on presentation abstract.
    • Trucking Industry Overview, Urban Jonson, SERJON (includes truck categorization in NA,  see  EU truck categorization

Meeting notes  2024-07-01

  • Compliance statement
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized Topics:
    • CVIS issues
      • Driver data - follows the driver as he goes between assets. Hours driving, time of break, driver settings,
        • Europe - driver has physical card, as above, speed...
      • Diagnostics data - OBD CARB biased term; fleet like actionable info as well as raw data; DTC plus location code important
    • Continue tree definition discussion.
      • Heavy duty Europe X tons? Class 1: < 3.5 ton, Class 2: 3.5-12 tons, Class 3 > 12 tons
        • Should Light trucks be separate tree?  One tree for all classes is likely => Do not use Heavy duty in naming.
      • Create a Bus tree as the signal set etc are quite different.
    • allowed definitions now in the common objects folder. himConfigurator can be used to substitute references to external Datatype tree with actual definitions.
    • HIM configurator demo. 

Meeting notes  2024-06-17

  • Compliance statement
  • Welcome and agenda discussion - anything that needs to be added?
  • Prioritized Topics:
    • Present the initial documentation at https://covesa.github.io/commercial-vehicle-information-specifications/
    • Discuss documentation layout.
      • Ted: looking to jumpstart the signaling work, leverage other existing work (eg FMS J1939 already mapped to VSS by Bosch) 
        Wally: centerline approach is a better way. fleet doesn't think centerline - how to represent
        ... VRMS uses driver side, front, back etc instead of centerline
        ... body type
        ... data in cargo area growing extensively
        Ted: on history of node location - which is driver side, etc. I like the center line but we also need a representation humans are more likely to use - we can potentially support more than one path 
    • Discuss 'first level' of branches for the respective trees (Tractor/Trailer).
      • Driver branch o separate tree? 
        • AP:Put tgether info about this for next meeting.
      • Sergey: Standards for where package is stored?
        • TMC can help?
      • Rename Tractor to Truck. Wait until checked.
      • Diagnostics - branch or tree?
    • HIM configurator demo (if time permits). 
  • General topics:
    • Open Pull Requests CVIS
    • Issues CVIS
    • Discussions CVIS
  • Other
  • Prioritized topics for next meeting

...