Connecting
-
Starting from Grbl firmware v0.9h the default Baud rate is now set to 115200. For this reason bCNC uses 115200 as the default baud rate too. If you need to change, please refer to Configuration where you can manually adjust some specific settings
-
Select the correct Serial port using the inputBox in the "Connection" groupBox either by writing the correct string or selecting one of the discovered ports enumerated in the comboBox
-
Press the
Open button (this operation can be automated by setting openserial=1 in Configuration file) -
For versions prior to 0.6: Once connected the status will display Locked use the
unlock button to move grbl to an idle state. For versions after 0.9.6, bCNC will display idle state after grbl executes valid g-code so there is no requirement to unlock. Jogging, play, pause, resume, stop will clear the connection status and will show grbl state. -
Click on the
Terminal tab to see the welcome message of Grbl or any possible error messages -
Now you're ready to do some work, load
a G-code file, use some of the Tools to create, or modify something using the integrated Editor.
This page describes how you can use bCNC to connect to the remote CNC machine through internet.
On the server (where GRBL is) you don't run bCNC. Instead you run software that will make the GRBL available over network.
You can connect your existing GRBL to Mikrotik router with USB (or serial) port and configure it to share the port over IP: https://wiki.mikrotik.com/wiki/Serial_Port_Usage#Accessing_a_serial_device_as_if_it_were_physically_connected_to_your_PCs.27_COM_port
You can run ser2net daemon to make your serial port (ant therefore existing GRBL setup) accessible over IP: http://ser2net.sourceforge.net/
You can run GRBL on ESP32 board and therefore get bluetooth and wifi support https://github.com/bdring/Grbl_Esp32/wiki/ESP3D-Web-UI-for-Grbl_ESP32
i found, that pyserial library already knows how to connect to remote serial using this URL syntax (#592):
-
socket://localhost:2217(= plain TCP connection) -
rfc2217://localhost:2217(= rfc2217 connection) -
spy:///dev/ttyUSB3?raw(= debug serial traffic to STDERR) -
hwgrep://0451:f432(USB VID:PID)
More documentation here: https://pyserial.readthedocs.io/en/latest/url_handlers.html
On the client side (where you run bCNC) you can first attach the remote serial port. It will then be available localy and therefore usable with any application (including bCNC) as if it was directly attached to local system.
socat pty,link=/dev/ttyS23 tcp:towel.blinkenlights.nl:23
