From 42f20b303db47cfd3a4aad8c7eb1ad5ac1b976b0 Mon Sep 17 00:00:00 2001 From: melfey Date: Sun, 24 May 2026 10:38:51 -0500 Subject: [PATCH] readme and comment changes --- README.md | 4 +++- src/core/motor.rs | 2 +- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 6a4e1cb..f4c44fc 100644 --- a/README.md +++ b/README.md @@ -1,4 +1,6 @@ -# Robotics Navigation and Control Via Postcard *RNavP* +# *RNavP* + +## Robotics Navigation and Control Via Postcard This is a crate designed to assit in development for the entire stack from the MCU(Running Embassy) to a STD computer talking to that MCU Via postcard for Drivetrain control. Designed for intergration with ROS2 but is *NOT* required and will work for any STD enviroment for the control system diff --git a/src/core/motor.rs b/src/core/motor.rs index d43b2c0..75dd963 100644 --- a/src/core/motor.rs +++ b/src/core/motor.rs @@ -116,7 +116,7 @@ pub trait Driver { /// Some sensors may also provide current and voltage feedback, if implemented the communication system can sync them to the host you for. /// Can also be used for other custom logic. They are unused by RNavP, entirely optional. pub trait Sensor { - ///Returns the speed struct value from the motors sensor + ///Returns the speed struct value from the motors sensor. /// This should be non-blocking, there should be some form of cached value ready to go as soon as the method is called /// /// IF properly returned in the correct Enum Data field, all other systems will use the value propely, being unit agnostic later.