Skip to content

This is my Cube Robotics OS with subsystem divided linear control

Notifications You must be signed in to change notification settings

dr-mrsthemonarch/CROS

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

43 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

C.R.O.S. The Cubic Robitics Operating System

 _    _      _                            _          _____ ______ _____ _____ 
| |  | |    | |                          | |        /  __ \| ___ \  _  /  ___|
| |  | | ___| | ___ ___  _ __ ___   ___  | |_ ___   | /  \/| |_/ / | | \ `--. 
| |/\| |/ _ \ |/ __/ _ \| '_ ` _ \ / _ \ | __/ _ \  | |    |    /| | | |`--. \
\  /\  /  __/ | (_| (_) | | | | | |  __/ | || (_) | | \__/\| |\ \\ \_/ /\__/ /
 \/  \/ \___|_|\___\___/|_| |_| |_|\___|  \__\___/   \____/\_| \_|\___/\____/ 

Welcome to the CROS. My novice attempt at creating a robotics OS for use with my accompanying Reaction wheel balanced Cube. The required Library, the SensorCaller (name subject to change) is also included in the repo.

The CROS allows access via serial to the Benture Box main interface. Currnetly using SimpleCLI a user can access all sensors individually and see any values required. The user can adjust individual controller gains, turn them on or off and also plot entire subsystem data. It's a basic interface but is an excellent starting point for anyone looking to use MADGWICK filters for angular display and control. I will likely be upgrading the CLI to another at somepoint, or changing to another core as the OS isn't responsive at times likely due to TaskScheduler.

Also cause I suck at coding.

About

This is my Cube Robotics OS with subsystem divided linear control

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages