Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CMOS battery monitoring #1452

Closed
3 tasks done
nobuotakamasa opened this issue Jul 28, 2022 · 2 comments
Closed
3 tasks done

CMOS battery monitoring #1452

nobuotakamasa opened this issue Jul 28, 2022 · 2 comments
Assignees
Labels
type:new-feature New functionalities or additions, feature requests.

Comments

@nobuotakamasa
Copy link
Contributor

Checklist

  • I've read the contribution guidelines.
  • I've searched other issues and no duplicate issues were found.
  • I've agreed with the maintainers that I can plan this task.

Description

I would like to add a function to raise the soundness of CMOS batteries to diagnostics.

Purpose

PC have a CMOS battery to store the state of the BIOS and to run the RTC. When the battery is exhausted, the contents of the BIOS will be erased and the RTC will be reset.
If it happens, the BIOS will be initialized at each boot.
The following problems occur.

  • The BIOS settings are erased.
  • It takes time to start the PC.
  • The RTC time is incorrect.
    To avoid the above problems, provide a function to raise the CMOS battery status to diagnostics.

Possible approaches

The default policy is to get the result of "cat /proc/driver/rtc".
As an optional is to get the result of lm-sensors.
Depending on the PC, lm-sensors can be used to monitor the voltage of CMOS batteries.
The default operation is OK, but monitoring with lm-sensors allows you to replace the battery before it runs out completely.
It is recommended because you can avoid the risk of sudden battery exhaustion.

Definition of done

Being able to reflect the battery status in diagnostics.

@stale
Copy link

stale bot commented Sep 26, 2022

This pull request has been automatically marked as stale because it has not had recent activity.

@stale stale bot added the status:stale Inactive or outdated issues. (auto-assigned) label Sep 26, 2022
@stale stale bot removed the status:stale Inactive or outdated issues. (auto-assigned) label Oct 20, 2022
@ito-san
Copy link
Contributor

ito-san commented Oct 20, 2022

This issue was fixed in #1989. I'm closing this issue.

@ito-san ito-san closed this as completed Oct 20, 2022
technolojin pushed a commit to technolojin/autoware.universe that referenced this issue Aug 15, 2024
…ublished trajectory (autowarefoundation#8164) (autowarefoundation#1452)

add timestamp and frame ID to published trajectory

Signed-off-by: kyoichi-sugahara <[email protected]>
Co-authored-by: Kyoichi Sugahara <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:new-feature New functionalities or additions, feature requests.
Projects
None yet
Development

No branches or pull requests

3 participants