[Fix] Make the Websocket work again #5
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for the note... interestingly Waveshare send my daughter a link to a preset bullseye build that works... my assumption is they were able to pull up an image of all the old code. Their demo web page runs flawlessly for me right now but I haven't tried to edit anything yet. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The code is quite outdated, and despite the fact that it can be installed on the legacy Debian Bullseye it looks like the opencv drivers may need update as well, therefore the change in the code. Most importantly, the websocket on port 8888 couldn't start due to threading issue, and as a result the robot couldn't be controlled from the dashboard level.
Mind that it works only if manually run
webServer.pyfile for example over SSH tunnel on your PC.