Add optional tcp support for connecting to grbl (plus other small improvements) #524
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Make a simple series of change to support connecting to gRBL remotely in addition to local serial (essentially just proxying over a tcp socket). This allows one to use a simple proxy box (like a Raspberry Pi setup with something like ser2net) and avoid having to keep your CNC connected to the main machine.
I had to make some other changes to the project file to be able to compile successfully but I can pull them out if desired.
I added a text input in the settings pane to be able to specify the host:port combo:
I have been using this functionality myself for the past few months without issues with a Raspberry Pi 3 and ser2net setup with this configuration: