Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

High Systemcore cpu utilization from REV HW Client

Open
#303 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
java

Research direction

Start by reproducing the reported idle setup with Motioncore attached, no devices plugged in, and REV HW Client inactive. Inspect the five CAN Send Threads and compare their CPU use with the report's roughly 6% per thread; done means the unexplained idle utilization is understood and the regression is addressed.

Written by the indexing model from the issue text.

Description

REV Robotics
Image

The 5 "CAN Send Thread"s are using ~6% (of a single cpu core) each, for a total of 6-8% overall cpu utilization. REV HW client is not active, this is out of the box idling. Motioncore is attached, but no devices are plugged in.

Dominant language
Java
Stars
190
Forks
25
Avg merge
6h 20m
Merged PRs (30d)
12

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from wpilibsuite/SystemcoreTesting

All issues in wpilibsuite/SystemcoreTesting

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.