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.

Sign up for GitHub

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

Jump to bottom

Split robot firmware #34

Open
runeharlyk opened this issue Mar 18, 2024 · 1 comment
Open

Split robot firmware #34

runeharlyk opened this issue Mar 18, 2024 · 1 comment
Labels
enhancement New feature or request
Milestone
Robot software

Comments

@runeharlyk
Copy link
Owner

It could be beneficial to split the robot firmware into an interface/planner and a controller. This would give the user a choice for selecting hardware for budgeting etc.

The interface controller could be an esp32(cam), raspberry pi or jetson nano. It purpose would be taking input and planning trajectories.

The controller could be an esp32, teensy 4.0, stm32 or other. The main purpose would be collection sensor data (uss, button, imu, adc etc), calculate inverse kinematics and updating hardware (servos, led, oled)
@runeharlyk runeharlyk added the enhancement New feature or request label Mar 18, 2024
@runeharlyk runeharlyk added this to the Robot software milestone Mar 18, 2024
@Ian-cmd-ops
Copy link

Interesting to see which way you go.

@runeharlyk runeharlyk mentioned this issue Jun 18, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
Robot software
Development

No branches or pull requests
2 participants
@runeharlyk @Ian-cmd-ops