Please help, what am I missing? Wrong firmware or interface? Wrong order of operations?
Device Built, tests ok.
Frame Built
Retract belts to Zero - Seems Ok
Extend Belts to Anchors - Seems Ok
Find Anchor Locations - Will not start. Process.
Serial Messages:
Index.html Version: v1.19-64-g291dac60
Grbl 1.20 [FluidNC v1.20 (wifi) ‘$’ for help]
Grbl 1.20 [FluidNC v1.20 (wifi) ‘$’ for help]
This probably not the problem, but your index.html.gz version does not match the FluidNC version (V1.19 Vs V.20). Firstly get them to the same version. Here is the version you require. save it to Downloads, do not unzip it.
index.html.gz (134.3 KB)
To load, go to FluidNC tab, click on the Green button, , Click on Upload File, then find the file you just downloaded and double click. When it has loaded click close, then click the Red Button (Restart FluidNC)
After it restarts, Click on Save serial and cut and paste a copy here. Serial.log file will be in the downloads directory.
Then, without going to Apply Tension, go to the setup menu and select Find Anchors
No movement….
Serial Messages
Index.html Version: v1.20
Grbl 1.20 [FluidNC v1.20 (wifi) ‘$’ for help]
Grbl 1.20 [FluidNC v1.20 (wifi) ‘$’ for help]
Release Tension
Find Anchors
Can you go into set up and press Test and copy the result here.
Normal sequence for 1st time is:
I suggest at this stage you run a few air runs without a bit in to get an idea of how the Maslow works
Test
Index.html Version: v1.20
Should have been a lot more than that
Try reloading the browser connection
Go to the serial.log window press Ctrl A and then Ctrl C then paste the result here with Ctrl V
I have to go out for a couple of hours shortly
Thanks for the help.
Status, I completely erased everything and started fresh. Everything is showing v1.2
Followed the instructions provided above. But, despite waiting motionless for a minute (propped up on an incline) I never moved from extend-ING to exten-DED.
This is where I’m stopped now. Is there any way to end extending state? di I fail procedure? Or something else…but I am getting proper messages now…
Serial Messages
Index.html Version: v1.20
[MSG:INFO: FluidNC v1.20]
[MSG:INFO: Compiled with ESP32 SDK:v4.4.7-dirty]
[MSG:INFO: Local filesystem type is littlefs]
[MSG:INFO: Configuration file:maslow.yaml]
[MSG:WARN: Ignored key MaslowAutoUpdate]
[MSG:WARN: Ignored key MaslowUpdateURL]
[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 5]
[MSG:INFO: Axis A (-4000.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis B (-4000.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis C (-4000.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis D (-4000.000,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.11]
[MSG:INFO: Motor1]
[MSG:INFO: tmc_2209 UART1 Addr:1 Step:gpio.46 Dir:NO_PIN Disable:NO_PIN R:0.11]
[MSG:INFO: Z Axis driver test passed]
[MSG:INFO: Z2 Axis driver test passed]
[MSG:INFO: Using spindle NoSpindle]
[MSG:INFO: Connecting to STA SSID:Oubliette]
[MSG:INFO: Connecting.]
[MSG:INFO: Connecting..]
[MSG:INFO: Connected - IP is 10.10.70.177]
[MSG:INFO: WiFi on]
[MSG:INFO: Start mDNS with hostname:http://maslow.local/\]
[MSG:INFO: WebSocket send protection active (canSend() checks enabled)]
[MSG:INFO: SSDP Started]
[MSG:INFO: HTTP started on port 80]
[MSG:INFO: Telnet started on port 23]
Grbl 1.20 [FluidNC v1.20 (wifi) ‘$’ for help]
Grbl 1.20 [FluidNC v1.20 (wifi) ‘$’ for help]
[MSG:INFO: ‘$H’|‘$X’ to unlock]
[MSG:INFO: Encoder connected on Top Left]
[MSG:INFO: Motor detected on Top Left]
[MSG:INFO: Encoder connected on Top Right]
[MSG:INFO: Motor detected on Top Right]
[MSG:INFO: Encoder connected on Bottom Left]
[MSG:INFO: Motor detected on Bottom Left]
[MSG:INFO: Encoder connected on Bottom Right]
[MSG:INFO: Motor detected on Bottom Right]
[MSG:INFO: Current z-axis position loaded as: 2.000]
[MSG:INFO: Saved belt positions in NVS are marked as stale/invalid (value=0) - machine will remain in UNKNOWN state until belts are calibrated/extended]
[MSG:INFO: Starting Maslow Version v1.20]
[MSG:INFO: Maslow update loop registered with hardware watchdog]
[MSG:INFO: Channel auto report interval set to 50 ms]
A couple of questions:
what state is the machine displaying now?
Did you pull all the belts out until the Fan stopped?
Are you on a vertical or horizontal setup?
Did you hook the belts up to anchors after 6 (sorry I left that out)
Mhue Ai wrote:
Status, I completely erased everything and started fresh. Everything is
showing v1.2
just a note, this is 1.20, 1.2 was 18 revisions ago 
ok, so you are on the correct version.
you power on, have the belts disconnected the state is probably unknown
you hit retract to pull the belts all the way in the state becomes retracted
this is needed as we don’t know what the belt lengths are. After you get going,
if the shutdown is clean, it will remember the belt lengths and start in either
retracted or extended state
you hit extend all and feed them out until they stop and the state becomes
extended
you attach the belts to the anchors and hit ‘find anchors’
give us the logs at that point
David Lang
Thanks for the help guys.
I missed one step. You have to pull the cable COMPLETELY out.
G2G
new question, I can’t find anything on this.
Made it through calibration but the calibratio nsetting weren’t saved. how do I make sure I don’t have to recalibrate every time I try and use the device OR there is a failure and it self-resets?
Hmmm how do you know that it didn’t save?
It should save automatically and be a one time thing. You shouldn’t have to do it again.
because I went to use it and it need to be recalibrated.
Will try again and see what happens.
What usually happens in that case it is that it did find anchor locations, but it uses a slightly different check to confirm that they are accurate enough next time it is set up which means that it’s possible to have it pass the first time, but then fail the check next time.
Basically it did save the results, but when it double checked them next time it found they weren’t quite good enough.
Running locate anchors again should fix it.
thanks digging throuhg the yaml and the code.
If looks like the calibration (anchor point locations) is permanent But the belt length tracking and homing state are in RAM and lost on every power cycle.
Is this your understanding and did I get it right? Is there any way not to have to go through it every time? Al it takes is one bad gcode load and the device has to be reset…
Mhue Ai wrote:
If looks like the calibration (anchor point locations) is permanent But the
belt length tracking and homing state are in RAM and lost on every power
cycle.
we do save the belt lengths when the machine goes idle while in specific states.
But if the machine has an unclean shutdown, that data will be lost and you need
to retract/extend/apply tension (and set Z-stop) to get the machine to know
where it is again.
Early on, especially when struggling through teething problems, this will seem
like every time (or more).
David Lang
