Skip to main content

Eclipse CANought

Eclipse CANought provides extensions to the Eclipse Kanto project focused on automotive market segment capabilities by standardizing and securing CAN communications. Eclipse CANought contributes the J1939 and UDS translator services to Eclipse Kanto and thus meets the automotive industry specific needs for CAN communications and security.

In-scope

  1. CAN Security Manager: manages CAN access and bandwidth allocation for balancing utilization across multiple applications
  2. MQTT APIs for J1939 and UDS communication in a well-documented format using the AsyncAPI specification
  3. Boilerplate Docker files, such as
    1. A Dockerfile for a Visual Studio Code Dev Container
    2. A Dockerfile for google unit tests, MQTT interface tests and static code analysis
    3. A Dockerfile for building the final application
    4. A Docker Compose file for running the application
  4. Boilerplate C++ code and helper files for a) The J1939 and UDS client application and b) The J1939 and UDS Translator service such as
    1. CMake files
    2. Application initialization code
    3. Functions/methods for J1939 and UDS MQTT API Calls
    4. Functions/methods for J1939 and UDS Message Handlers
  5. A J1939 and UDS Translator Validator for validating that a given implementation of the J1939 and UDS Translator MQTT APIs are implemented correctly
  6. Possibly, code generators, to automatically generate the boilerplate C++ code or Rust code for both the Translator client and the Translator server

Out-of-scope

  1. An implementation of the J1939 and UDS libraries themselves is out-of-scope. The J1939 license does not permit open source implementations of the J1939 specifications or stack.

Basics

Repositories

Repository Commits Reviews Issues
https://github.com/eclipse-canought/up-cpp-server 3 3 0
https://github.com/eclipse-canought/.eclipsefdn 1 0 0
https://github.com/eclipse-canought/up-cpp-client 1 0 0

Activity - commits

There have been 5 commits made by 4 people on 3 repositories over the last 12 months.

Activity - issues

There have been 0 issues submitted by 0 people on 0 repositories over the last 12 months.

Activity - reviews

There have been 3 reviews submitted by 2 people on 1 repositories over the last 12 months.

The EMO oversees the lifecycle of Eclipse projects, trademark and IP management, and provides a governance framework and recommendations on open source best practices.

See the project’s PMI page at https://projects.eclipse.org/projects/iot.kanto.canought

Releases

Reviews

IP Lab requests

Organization Settings

  • GitHub organization: eclipse-canought
  • 2FA enforced: True
  • Default workflow permissions: read

Branch Protections

This project has a total of 6 repositories in its associated GitHub organization eclipse-canought . The graph below outlines the percentange of repositories that have either defined a Branch Protection Rule or Repository Ruleset: Branch protections

SDV Maturity badges recognise achievements made by the project towards the SDV maturity assessment goals. Learn more on the dedicated page .

These badges only apply to the SDV Working Group .

Blueprints integration

Is the project used to showcase the resolution of a real-life situation, either individually or integrated with other Eclipse SDV projects? See the SDV Blueprints project for more information.

This project has not registered any activity on the criteria.

Requirements

How well is the project doing when it comes to Requirements e.g. defining, versioning and managing, traceability, coverage, etc? For more details on the needs for the different levels of the Requirements Criteria read its definition here .

This project has not registered any activity on the criteria.

Testing

How well is the project doing when it comes to Testing e.g. defining, versioning and managing, traceability, coverage, types of tests etc? For more details on the needs for the different levels of the Testing Criteria read its definition here .

This project has not registered any activity on the criteria.

Documentation

How well is the project doing when it comes to Documentation e.g. types of documents depending on contents, versioning, etc? For more details on the needs for the different levels of the Documentation Criteria read its definition here .

This project has not registered any activity on the criteria.

Coding Guidelines

How well is the project doing when it comes to Coding Guidelines e.g. defining, adhering, managing issues etc? For more details on the needs for the different levels of the Coding Guidelines Criteria read its definition here .

This project has not registered any activity on the criteria.

Release process

How well is the project doing when it comes to Releases e.g. defining a process, versioning and managing, release notes, coverage etc? For more details on the needs for the different levels of the Release Process Criteria read its definition here .

This project has not registered any activity on the criteria.

OSS Best Practices

Is the project respecting OSS good practices files in their repositories? See also the legal documentation checker for more information.

OSS Best Practices badge for iot.kanto.canought

<a href="https://metrics.eclipse.org/projects/iot.kanto.canought" alt="OSS Best Practices badge for iot.kanto.canought">![OSS Best Practices badge for iot.kanto.canought](https://metrics.eclipse.org/badges/iot.kanto.canought_badge_oss_best_practices.png)</a>

Back to the top