Firmware version 1.10 is out!
It’s got some bug fixes and some quality of life improvements. Nothing earth shattering, but generally progress!
3 Likes
Updated the firmware and am now getting a bunch of Error 3. Jogging z-axis still works though. (My Maslow was never working. Still trying to iron it out in the forums, but that’s another issue. Just thought I’d mention this here.)
Serial Messages
Index.html Version: 1.10
[MSG:INFO: Channel auto report interval set to 50 ms]
[MSG:INFO: FluidNC v3.0.x (noGit)]
[MSG:INFO: Compiled with ESP32 SDK:v4.4.7-dirty]
[MSG:INFO: Local filesystem type is littlefs]
[MSG:INFO: Configuration file:maslow.yaml]
[MSG:INFO: Machine Maslow S3 Board]
[MSG:INFO: Board Maslow]
[MSG:INFO: UART1 Tx:gpio.1 Rx:gpio.2 RTS:NO_PIN Baud:115200]
[MSG:INFO: SPI SCK:gpio.12 MOSI:gpio.11 MISO:gpio.13]
[MSG:INFO: SD Card cs_pin:gpio.10 detect:NO_PIN freq:8000000]
[MSG:INFO: Stepping:Timed Pulse:4us Dsbl Delay:0us Dir Delay:0us Idle Delay:240ms]
[MSG:INFO: Axis count 3]
[MSG:INFO: Axis X (-2438.400,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis Y (-1219.200,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis Z (-100.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: tmc_2209 UART1 Addr:0 Step:gpio.15 Dir:gpio.16 Disable:NO_PIN R:0.110]
[MSG:INFO: Motor1]
[MSG:INFO: tmc_2209 UART1 Addr:1 Step:gpio.46 Dir:gpio.38 Disable:NO_PIN R:0.110]
[MSG:INFO: Z Axis driver test passed]
[MSG:INFO: Z2 [MSG:INFO: Channel auto report interval set to 50 ms]
[MSG:INFO: FluidNC v3.0.x (noGit)]
[MSG:INFO: Compiled with ESP32 SDK:v4.4.7-dirty]
[MSG:INFO: Local filesystem type is littlefs]
[MSG:INFO: Configuration file:maslow.yaml]
[MSG:INFO: Machine Maslow S3 Board]
[MSG:INFO: Board Maslow]
[MSG:INFO: UART1 Tx:gpio.1 Rx:gpio.2 RTS:NO_PIN Baud:115200]
[MSG:INFO: SPI SCK:gpio.12 MOSI:gpio.11 MISO:gpio.13]
[MSG:INFO: SD Card cs_pin:gpio.10 detect:NO_PIN freq:8000000]
[MSG:INFO: Stepping:Timed Pulse:4us Dsbl Delay:0us Dir Delay:0us Idle Delay:240ms]
[MSG:INFO: Axis count 3]
[MSG:INFO: Axis X (-2438.400,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis Y (-1219.200,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis Z (-100.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: tmc_2209 UART1 Addr:0 Step:gpio.15 Dir:gpio.16 Disable:NO_PIN R:0.110]
[MSG:INFO: Motor1]
[MSG:INFO: tmc_2209 UART1 Addr:1 Step:gpio.46 Dir:gpio.38 Disable:NO_PIN R:0.110]
[MSG:INFO: Z Axis driver test passed]
[MSG:INFO: Z2 Axis driver test passed]
[MSG:INFO: Kinematic system: Cartesian]
[MSG:INFO: Using spindle NoSpindle]
[MSG:INFO: STA SSID is not set]
[MSG:INFO: AP SSID maslow IP 192.168.0.1 mask 255.255.255.0 channel 1]
[MSG:INFO: AP started]
[MSG:INFO: WiFi on]
[MSG:INFO: Captive Portal Started]
[MSG:INFO: HTTP started on port 80]
[MSG:INFO: Telnet started on port 23]
error:3
error:3
error:3
error:3
error:3[GC:G0 G54 G17 G21 G90 G94 M5 M9 T0 F0 S0]
error:3
error:3
error:3
error:3
error:3
error:3
error:3
error:3
error:3
error:3
[MSG:INFO: Channel auto report interval set to 50 ms]
[MSG:INFO: Caution: Unlocked]
JogTo: '$J=G91F300Z5
’
JogTo: '$J=G91F300Z-5
’
JogTo: '$J=G91F300Z-5
’
1 Like
I need a refresher on how to update the FW via WiFi. Can someone point me to the instructions. I have been able to download the Ver 1.10 files for WIN64 but am not sure which file need to be sent to the Maslow 4.1 via FluidNC.
1 Like
You can find those here:
It looks like error 3 is coming from a “Invalid $ statement”, I’m not sure why though.
Did you update your maslow.yaml file also? That could be causing it
Though I had “updated” my maslow.yaml file I was getting the error: 3 and an error about MaslowKinematics not available. Deleting the .yaml file and reuploading it appears to have corrected those errors.
1 Like
sadam wrote:
Though I had “updated” my maslow.yaml file I was getting the error: 3 and an error about MaslowKinematics not available. Deleting the .yaml file and reuploading it appears to have corrected those errors.
I had the same problem when I installed 1.09 via usb last week.
David Lang
1 Like
Alan Kirk wrote:
I need a refresher on how to update the FW via WiFi. Can someone point me to
the instructions. I have been able to download the Ver 1.10 files for WIN64
but am not sure which file need to be sent to the Maslow 4.1 via FluidNC.
what version are you starting from, if it’s <1.0 then you need to update via
USB
if you are starting after 1.0 then you need to upload firmware, index.html.gz,
and a new maslow.yaml (but copy the ancor positions from your old maslow.yaml,
they have new names in the new version)
David Lang
I updated to 1.05 when it came out. When I run the FluidNC WiFi tool I select the firmware.bin from the unzipped 1.10 folder and then Update. All seems to go fine, even get a restart on the Maslow4.1 but the serial data still shows ver 1.05.
Do I have to manually update the ver number via the FluidNC tool?
Alan Kirk at 1agkirk2@gmail.com
I didn’t update the yaml-file. Doesn’t that then cause a need for recalibration?
Olof wrote:
I didn¢t update the yaml-file. Doesn¢t that then cause a need for
recalibration?
calibration should probably be renamed to ‘find anchor locations’, as long as
you record the anchor locations from your old maslow.yaml file and put them in
the right place in the new one, you should be good.
with 1.09 the right place (and variable names) in the yaml file changed. so save
a copy of your old file and after you load the new one, go into the fluidnc
config tab and find the location variables and enter the values there (don’t
forget to save them after you enter them)
David Lang
1 Like
Alan Kirk wrote:
Do I have to manually update the ver number via the FluidNC tool?
no, but you do have to update the index.html.gz file, and when upgrading from
before 1.09, you need to update the maslow.yaml file (and re-enter the anchor
cordinates)
there is a version number for the firmware and a version number for the
index.html
David Lang
Thanks for the update.
Alan Kirk at 1agkirk2@gmail.com
Since the calibration procedure is such a B, perhaps we can get more guidance on when the .yaml really needs to be updated and perhaps even separate out the less stable parameters from the more stable parameters in different places?
Jason wrote:
Since the calibration procedure is such a B, perhaps we can get more guidance
on when the .yaml really needs to be updated and perhaps even separate out the
less stable parameters from the more stable parameters in different places?
In general, you do not need to replace the maslow.yaml unless you are told to.
It should be very rare (I posted elsewhere that I consider it a bug that the
firmware didn’t handle the 1.09 upgrade seamlessly)
I would love to have the frame parameters split into a different file, it would
make it much easier to have multiple files for different frames, but doing that
will take some pretty significant surgery to the fluidnc core code that handles
the yaml file, not a trivial thing to do.
David Lang
If the YAML parser understands one of include, !include, $include then we could just include the static file?
sadam wrote:
If the YAML parser understands one of
include,!include,$includethen we could just include the static file?
It does not appear that it does support include in any form. That would be handy
if it did.
It does look like there is something in the firmware that specifies that the
file is maslow.yaml, so it may be possible to change the file that it’s looking
for (need to test)
That wouldn’t help problems like the 1.09 step, because that release changed
what variables in the file it was looking for without including a transition
from the old layout.
David Lang
1 Like