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

Update Networking Code #5

Open
2 of 4 tasks
dimembermatt opened this issue Sep 14, 2020 · 0 comments
Open
2 of 4 tasks

Update Networking Code #5

dimembermatt opened this issue Sep 14, 2020 · 0 comments

Comments

@dimembermatt
Copy link
Contributor

dimembermatt commented Sep 14, 2020

This is a slightly higher level project:
We want to update the existing robot networking code that sets up an independent network and server for the robot and other robots to join.
We also want to update the existing API to match that in the webserverui communication protocol issue #4.

Specifically, we want to do the following:

  • see if we can optimize the creation and/or joining of networks and servers in the setupWifi() and startServer() functions. Low priority.
  • update the API exposed in startServer() to match the noted issue above, both in endpoint and types of request (PUT vs GET).
  • we also want to update the methods the robot use to communicate with the server joinServer(), getState(), etc. to match the expected result and do proper parsing for them.
  • finally, we want to look at reducing the processing time needed to manage on robot server requests and maximize the time used for the robot cycling through movements. From existing testing, the current code significantly hampers the smoothness of robot movement. We should look further into asynchronous HTTP event handling, possible usage of multiple cores (if the Pico Kit even has them), and removing significant code processing blockers outside of the DancingServos class. High priority.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant