Releases: bdring/FluidNC
v3.6.5-pre1
Test release for auto reporting and WebUI Tablet continuous jogging
This test release has automatic status reporting so the sender does not have to send ? and $G periodically in order to update its display. The feature can be enabled by sending $report/interval=100, or $ri=100, to set the auto-reporting interval to 100 ms. The WebUI index.html.gz that is included automatically enables the feature. To use the new WebUI, you will need to upload it separately to your local filesystem, after installing the new firmware.
Automatic reporting happens during motion, and any time that the state changes.
It should be possible to use this feature with senders other than WebUI by sending the $RI=100 command from the sender's console - and then you probably want to configure the sender for a long interval between explicit status requests.
In addition to auto-reporting, the new WebUI's Tablet UI supports continuous jogging, by holding down the jog button. A short tap will perform a fixed-length jog by the selected distance. If you hold it down, it will jog continuously until you release the button.
v3.6.4
- Fixed RMT stepping engine issues with step pausing due to UART activity.
- Fixed RMT erratic pulse widths due to Espressif library changes.
- Increased step pulse length max to 30uS for slow TB6560 drivers
v3.6.4-pre3
v3.6.4-pre1
This is a test release for a problem that has affected several people - potentially everybody who uses RMT stepping. A change in the underlying ESP-IDF toolkit from Espressif led to an uninitialized variable that, in turn, cause the RMT hardware to randomly use the wrong clock. Sometimes it would work right, then after you reboot, it would be wrong and the step pulses would be too long by a huge margin.
v3.6.3
New Features
- Added $Motor/Enable ( or $ME) command to compliment the $Motor/Disable (or $MD) command
- $30 will now respond with the max speed on the speed_map (emulates Grbl). This is for compatibility with some gcode senders.
Enhancements and fixes
-
GPIO Input Reading Overhaul. This fixes the occasional problem with reading limit switches.
-
Fixed motion stuttering when using I2S pins on spindles.
-
Fixed CoreXY Homing.
-
Created new SPI driver. This fixes issues with talking to Trinamic drivers.
-
More accurate test for Trinamic motor communications. It tries to read the driver "version" to see if it matches the configuration.
TestLimits
This test release fixes some 3.6.2 problems with limits (which can make motors not run) and corexy homing. Give it a try and report back.
v3.6.2
New Features
- LittleFS is now supported for the local filesystem. The default is still SPIFFS but you can switch to LittleFS per http://wiki.fluidnc.com/en/support/filesystem_migration. In some future release LittleFS will become the default.
- Reserved GPIO pins, like those used for FLASH communication, will now report an error in the startup messages.
- You can now use multiple WebSockets and open multiple WebUI pages.
- Tool numbers can now go up to 99999999
Fixes
- Fixed resume after feedhold
- Dynamixel servo fixes
- Fixed laser staying on during hold
- Fixed decoding of WebUI real time characters (overrides, etc)
- Fixed some parking issues
There is a change to the WebUI. You should load the new one to pick up some bug fixes. It is in the wifi folder of the release.
http://wiki.fluidnc.com/en/installation#upgrading-firmware
v3.6.1
Features
- Safety door and parking improvements. It is now configurable.
- Spindles now have a config option to stop during an alarm.
- Dual motor single switch homing is now supported. The axis is not squared.
Enhancements and Fixes
- Numerous homing and limit switch improvements.
v3.5.1-pre-FS
Test release for file improvements. It supports both SPIFFS and LittleFS for the local filesystem. If you have an SD card, you can switch to LittleFS as follows:
$localfs/migrate=littlefs
That will backup all of your local files to the SD card, reformat the local filesystem to LittleFS, then restore the backup onto the newly-formatted local FS. You can go back the other way with:
$localfs/migrate=spiffs
TestPullups
This is a test release for a bug that only affects active-high limit pins with large-value/weak pulldowns. The problem is that the internal pullup resistor on limit pins was activated even if you did not say :pu in the config file. If there is a weak pulldown, the combination of the pullup and the weak pulldown can make the pin float at an intermediate voltage which could be interpreted as high even if the external switch is not active, so there would never be a low-to-high transition.