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

Setting up Address:Port instead of just COM Terminal... #655

Open
silver2row opened this issue Feb 7, 2025 · 0 comments
Open

Setting up Address:Port instead of just COM Terminal... #655

silver2row opened this issue Feb 7, 2025 · 0 comments

Comments

@silver2row
Copy link

Is your feature request related to a problem? Please describe.
Hello...I am trying to connect to a machine now that accepts IPADDR:PORT syntax and I cannot attempt to get connected via COM ports (I Think).

When I set up the machine and run the source, the machine works by IP:PORT instead of having a driver for COM on Windows...

Describe the solution you'd like
I would like this feature of Candle to accept IP:PORT instead of COM. Is this possible from the developers from Candle?

Describe alternatives you've considered
I tried bCNC and I can connect to the software but I am having trouble using the bCNC source as of now with my controller. I was thinking since I have used Candle in the past and currently with success like with the Teensy4.1 and grblHAL, I can try it with my current 32-bit RISC controller.

Additional context
So far, the connection says connected but I cannot set any machine parameters on the GUI/front end. So, the front end GUI does not know where exactly my machine location is located at any given time. I used a .nc file for running it but it just gets sent and does not have the option for accepting it and then allowing the GUI/Candle to instantiate the file.

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