Here is 0.74.3 which lowers the SPI clock frequency to make the encoders more robust to EMF
firmware.bin (1.6 MB)
Here is 0.74.3 which lowers the SPI clock frequency to make the encoders more robust to EMF
firmware.bin (1.6 MB)
Here is 0.76.1 which is mostly meant for @anna and some testing we are doing but I figured I would make it public as well. This version disables the 15mm while moving error message so we can explore what happens if we ignore it and see if it creates real problems for our cuts.
firmware.bin (1.6 MB)
I’ve tested this version twice now and both times it still threw the 15 mm error code. From what I’ve seen each time it throws it, its saying it about the arm that is the loosest of the 4.
This version will still display the error message, it just won’t stop cutting
On GitHub 0.77 seems to be the latest release right now. There is however no firmware.bin file there. Am I missing something?
Same here, cant find the file…
You are right, I didn’t upload the firmware.bin
It should be fixed now!
Thanks for catching that!
Perfect, I noticed that if I load the GC file first and then do the rehang dance the ESP crashed after the extent all step.
If load it after the rehang it works as expected.
Can you tell me more about that? I’m not quite sure I understand. Which is the GC file?
Are you referring to selecting/loading or uploading a gcode file while the Maslow is unmounted, then mounting it?
(this is not a yes or no question, I am asking if you are talking about choosing a file that is already on the SD card and causing it to load the preview, or if you are talking about putting a new one on the SD card)
Yes
What I’m referring to is loading a gcode file from the SD card ahead of retract-extend-apply tension.
It fails after the extend all is finished. Honestly I’ve only tried twice I can share the gcode file later if it’s useful.
It’s not a big issue but I figured it might give some guidance on debugging.
I wouldn’t worry about it being the specific file, seems more likely that the issue is doing that before the mounting process and that software is not handling the transition well while having a file loaded when it finishes that process and “gives you control” of the whole system.
I would just not load/preview files with the machine unmounted as a best practice at this time, at least not when you’re intending to mount it and cut, rather just doing that after the mounting.
Here is 0.78.1 which fixes issues with some of the maslow specific configuration settings being overwritten in 0.78.
This will fix the wifi network name and host name being fluidnc instead of maslow, the maslow.yaml file not being found, and the blue LED not blinking out the IP address.
index.html.gz (158.7 KB)
maslow.yaml (3.3 KB)
firmware.bin (1.8 MB)
1st- Also awesome to see the collaboration in the community! Wish i had more technical background to contribute, but will be testing this shortly. 2nd- Stupid question- the ‘index.html.gz’ downloads here as a file folder labeled ‘index.html’. Should i upload/update as the entire folder or the html inside this folder? Should i re-name any?
This one is a little tricky. Some computers automatically unzip the file into index.html which we don’t want, some computers also just hide the .gz extension so the file name that you see is index.html but there is actually a hidden “.gz” on the end.
You want to upload the index.html.gz file without changing it
Thank you soo much! I’ll upload it as the original zip and touch nothing! This might be a good note to add to the setup instructions on the main webpage to avoid confusion. Thanks for all your work man!
Can’t upload the new file 0.78.1 not able to connect to M4 through wifi or USB?
I ran calibration with the ‘interstitial’ firmware release. All seemed okay, no errors thrown, but I noticed my Z axis was at 11.0 even when it was correctly set at onset of calibration.
Any ideas here? Shall i proceed with the cut or how might i fix this? Or is it even broken?
With this result im not sure if i understand the z-axis starting position and defining of “home” (bit to work surface)?
FYI- When i hit define home right after the calibration it indicated a “-11.0”
Just confirming you took the bit out and/or the moved the z all the way to the bottom before calibrating?