You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: