FluidNC is designed to have basic compatibility with Grbl senders using the USB/Serial connection. The compatibility is focused on running your machine and sending gcode.
It is not compatible with Grbl on how you set up parameters and options. FluidNC has a vastly more flexible and comprehensive system. The Grbl $$ settings and compile time options were far too limiting, so we created the config file system.
Below are some links to some gcode senders. They have not all been tested with FluidNC. If you want to add one to this list, let us know.
After connecting, click the reset button to sync Grbl_ESP32 and CNCJS
CONTROL connects to the websocket of the wifi build out of the box.
Fluid Control is Android app, connects to Telnet over Wi-Fi. Freemium.
Original Grbl was based on Arduinos which typically reboot when you connect to them. When a sender opens a connection it can immediately recognize Grbl by the initial messages it sends.
FluidNC prefers not to be rebooted when connected. FluidNC supports multiple connection types including Wifi and Bluetooth. Rebooting would break those connections and could kill a job that is already running. Those connections can take a long time to re-establish.
Here is a good flowchart to determine the version (FluidNC, Grbl, etc) in all cases.
Grbl 3.4 [FluidNC v3.4.2 (wifi) '$' for help]
If your sender is very picky about the exact text and revision in the message you can change it with the $Start/Message command.
We do not want any connection to arbitrarily reboot the firmware. This means some senders will not see the message. most controllers or ESP32 module will have a manual reset button.
If you have issues or questions about these, please consider contacting those developers before contacting us.