These are issues that have been identified or requested. This is not a roadmap or TODO list. It just captures feedback we get.
Release scripts need lots of testing
Lines 81 and 104 need a space before the ending bracket: if [ "$chip" == "esp32" ]; then
on OSX 14.5. using Lonely Binary ESP32-S3-N16R8 dev kit board. install-wifi_s3... fluidnc doesn't seem to start.
on OSX 14.5, using ESPRESSIF ESP32-S3-WROOM-1, the installer fails to connect
P should be a required parameter. Currently you can skip it and FNC will assume P0.
Adding some way for users to customize screens
(Mitch says: I wrote a version of the Tablet UI in microPython/LVGL for the CrowPanel 7, and tried to hand off the code to someone else for completion and maintenance. It kept running into the problem that the LVGL API changes constantly, and they stopped supporting the microPython binding. There is a guy named Kevin Schlosser who supports LVGL/microPython on his own, with a nice build system, but he changes the API rather frequently too, so deployment is sort of a never-ending hassle.)
These are things that have been suggested by others. The developers are only compensated by small donations at this time, so each is free to choose what they work on.
See this announcement.
This would improve laser engravings by making files smaller and motion more efficient.
This is pretty challenging. FluidNC would need to scan the entire file before starting. Gcode senders are not designed for this type of workflow.
I/O expansion has removed some limitations on I/O count. Motor driver and spindle alarms could be helpful.
We don't see this as a high priority at this time. Some features offer little benefit, but result in high amounts of work and support. We believe backlash compensation only helps large and rigid machines.
Currently they are typically always enabled. Since we have more I/O with expanders, etc, it might make sense to support this. It also allows better control of startup states.
This is where a single line of gcode is run at a time. It is done for troubleshooting and testing gcode files and machines. Typically the cycle start is used to begin the next line.
The immediate (not wait) mode is now supported.
To persist after power cycles
Allow jogs in the proper direction to clear a switch when the active switch end is known. Also consider adding the end to the alarm message.
Add the ability to rotate coordinate systems with the G10 L2 command. This is discussed here.
Add an option where probe activations become hard faults when not probing.
Many people have accidentally damaged probe tips or toolsetters crashing into them in G0 through G3 modes. It would be nice to limit it to run mode only to allow testing of the probe continuity without faulting.
This feature could fine tune pulse rise times and reflections.