looks like it corrupted the Maslow.yaml file
USB_Serial_Configuration.txt (14.8 KB)
it crashed at waypoint 6 as it was supposed to start the next round of 9 measurements (waypoints 6-14) and I didn’t see it reporting that it calculated grid size
my guess is a memory allocation error. please post the corrupted maslow.yaml
Does not appear to be corrupt, can login and move around. As soon as I star the Configuration it locks up only way out is a power reset
maslow (10).yaml (6.9 KB)
This is where it failed, after it had done the initial steps:
assert failed: xTaskRemoveFromEventList tasks.c:3768 (pxUnblockedTCB)
Backtrace: 0x40379a06:0x3fcd2a60 0x4037ebe1:0x3fcd2a80 0x40385cd9:0x3fcd2aa0 0x40380c42:0x3fcd2bd0 0x4037fcec:0x3fcd2bf0
ELF file SHA256: 662cf4979663b72f
Rebooting…
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0xc (RTC_SW_CPU_RST),boot:0x8 (SPI_FAST_FLASH_BOOT)
Saved PC:0x4037963c
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce3808,len:0x4bc
load:0x403c9700,len:0xbd8
load:0x403cc700,len:0x2a0c
entry 0x403c98d0
[MSG:INFO: FluidNC v3.0.x (HEAD-6500de4)]
[MSG:INFO: Compiled with ESP32 SDK:v4.4.7-dirty]
[MSG:DBG: Spiffs mount failed: ESP_FAIL]
[MSG:INFO: Local filesystem type is littlefs]
[MSG:ERR: Skipping configuration file due to panic]
[MSG:INFO: Using default configuration]
[MSG:WARN: Ignored key Maslow_tlX]
[MSG:WARN: Ignored key Maslow_tlY]
[MSG:WARN: Ignored key Maslow_trX]
[MSG:WARN: Ignored key Maslow_trY]
[MSG:WARN: Ignored key Maslow_blX]
[MSG:WARN: Ignored key Maslow_blY]
[MSG:WARN: Ignored key Maslow_brX]
[MSG:WARN: Ignored key Maslow_brY]
[MSG:WARN: Ignored key Maslow_tlZ]
[MSG:WARN: Ignored key Maslow_trZ]
[MSG:WARN: Ignored key Maslow_blZ]
[MSG:WARN: Ignored key Maslow_brZ]
[MSG:WARN: Ignored key dc_servo]
[MSG:WARN: Ignored key y]
[MSG:ERR: Skipping key max_rate_mm_per_min indent 4 this indent 2]
[MSG:ERR: Skipping key acceleration_mm_per_sec2 indent 4 this indent 2]
[MSG:ERR: Skipping key max_travel_mm indent 4 this indent 2]
[MSG:ERR: Skipping key homing indent 4 this indent 2]
[MSG:ERR: Skipping key cycle indent 6 this indent 2]
[MSG:WARN: Ignored key cs_pin]
[MSG:WARN: microsteps value 0 constrained to range (1,256)]
[MSG:WARN: Ignored key cs_pin]
[MSG:WARN: microsteps value 0 constrained to range (1,256)]
[MSG:DBG: Running after-parse tasks]
[MSG:DBG: Checking configuration]
[
Ok, so a bug in calibration without corrupting the file. working on it…
David Lang
k
Ok, it was checking the wrong veriable so never invoked the grid size calculation here.
by the way, in the serial terminal you are using, do you have a way to specify baud rate and/or handshaking? the serial logs you are reporting have some occasional glitches
I am using fluidterm in its default mode. Don’t know if I can change handshaking or speed
Same again, this time at waypoint 52 Logs
Maslow-serial - 2025-10-07T105903.225.log (20.9 KB)
USB_Serial_Configuration.txt (14.8 KB)
well, getting better 
it allocated memory for 52 points and then tried to measure 81 points, no wonder it failed.
standby…
I think there was a problem with the 2nd log file you posted, that looked like the prior run that crashed after waypoint 5
but I think it calculated a grid something like 9x5 but then tried to run a grid of 9x9 and didn’t have the memory for it.
give this one a try
set all for grid size values to zero to trigger the full automatic sizing
Maslow_calibration_grid_width_mm_X: 0 # Auto-calc dimensions from geometry
Maslow_calibration_grid_height_mm_Y: 0
Maslow_calibration_grid_size_X: 0 # Auto-calc point counts from dimensions
Maslow_calibration_grid_size_Y: 0
Maslow_calibration_grid_spacing: 400 # Spacing between points
I’m trying to get it to change the behavior so that if ANY of the 4 are set to 0 it will auto calculate all 4. but it seems like copilot is stuck in a loop again
-
I’ll analyze the comment and make the requested changes.
-
The user wants to simplify the auto-calculation trigger: instead of requiring all 4 parameters (grid width, grid height, grid size X, grid size Y) to be 0 for full auto-calculation, if ANY of them is 0, the system should auto-calculate all 4 values.
-
Let me first examine the current code to understand how it works:
-
I need to understand the current implementation and make changes so that if ANY of the four grid configuration values are zero, the system will automatically calculate all four values.
-
I’ll analyze the comment and implement the requested change to make the auto-calculation trigger when ANY of the four grid parameters are set to 0.
-
I’ll analyze the comment and implement the requested change to make auto-calculation trigger if ANY of the four grid parameters are set to 0.
-
I’ll analyze the comment and implement the requested change.
-
The user wants to simplify the auto-calculation behavior so that if ANY of the four grid-related parameters (width, height, sizeX, sizeY) are set to 0, the system should automatically calculate ALL four values.
-
Let me first examine the current code to understand how it works:
in my experience, it’s going to take an hour for it to give up, and this is going to mean that I’ll need to open yet another issue to continue work as any request will get stuck in a loop like this 
in the meantime, you can test this version and in an hour or two I’ll get past this and have the next one ready to test (which, unless you find another bug, should just be this one with it being easier to trigger the automatic grid size
Ok, this should compute grid size in mm and points if any of the four values is zero
and there should be a maslow.yaml parameter
Maslow_calibration_grid_spacing: 400
that tells it how far apart to space the measurement points
on a full sheet of plywood ‘in the green’ it would create a 9x5 grid by default with a grid size of 7’ wide x 3’ high
This quietly failed after initial 6 run
Just-Queitly_died_after_initial_readings.txt (23.0 KB)
Maslow-serial - 2025-10-07T132301.834.log (30.1 KB)
Will try #660 now.
hmm, that died with an error I haven’t seen before. let’s see if the 660 build does any better (probably not, but fingers crossed)
assert failed: tcp_input IDF/components/lwip/lwip/src/core/tcp_in.c:287 (tcp_input: TIME-WAIT pcb->state == TIME-WAIT)
Backtrace: 0x40379a06:0x3fcbf1b0 0x4037ebe1:0x3fcbf1d0 0x40385cd9:0x3fcbf1f0 0x420a2b79:0x3fcbf320 0x420a811e:0x3fcbf390
panic again.
Guru Meditation Error: Core 1 panic’ed (StoreProhibited). Exception was unhandled.
ok, next iteration ready for testing.
Panic after 1st 6 Can we cut out 7 of the Spoilboard & Work thickness report lines please.
StillBroken.txt (14.9 KB)
Maslow-serial - 2025-10-07T154841.974.log (7.5 KB)
[MSG:INFO: Requesting state change from Calibration Computing to Calibrating]
[MSG:INFO: Calibration starting in HORIZONTAL orientation mode]
[MSG:INFO: Generating calibration grid after waypoint 5 calculation with updated anchor positions]
[MSG:INFO: Auto-calculating calibration grid parameters from frame geometry (at least one parameter set to 0)]
[Guru Meditation Error: Core 1 panic’ed (LoadStoreAlignment). Exception was unhandled.
Core 1 register dump:
PC : 0x42022499 PS : 0x00060d30 A0 : 0x8203d078 A1 : 0x3fcebc90
A2 : 0x454143ba A3 : 0x00000000 A4 : 0x3fcae8e8 A5 : 0x3fcae8d8
A6 : 0x3fcaebf0 A7 : 0x3fcaea48 A8 : 0x43d7a3c2 A9 : 0x00000000
A10 : 0x3fcebcf0 A11 : 0x0000008c A12 : 0x00000018 A13 : 0x000000c0
A14 : 0x3fc9e9cc A15 : 0x00000001 SAR : 0x0000001a EXCCAUSE: 0x00000009
EXCVADDR: 0x43d7a3c2 LBEG : 0x40056f5c LEND : 0x40056f72 LCOUNT : 0xffffffff
Backtrace: 0x42022496:0x3fcebc90 0x4203d075:0x3fcebd70 0x4215072d:0x3fcebd90 0x4204585b:0x3fcebdb0 0x42045aff:0x3fcebe30
ELF file SHA256: 07d61f829ea9771d
Rebooting…
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0xc (RTC_SW_CPU_RST),boot:0x8 (SPI_FAST_FLASH_BOOT)
Saved PC:0x4215848c
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce3808,len:0x4bc
load:0x403c9700,len:0xbd8
load:0x403cc700,len:0x2a0c
entry 0x403c98d0
[MSG:INFO: FluidNC v3.0.x (HEAD-59314cc)]
[MSG:INFO: Compiled with ESP32 SDK:v4.4.7-dirty]
[MSG:DBG: Spiffs mount failed: ESP_FAIL]
[MSG:INFO: Local filesystem type is littlefs]
[MSG:ERR: Skipping configuration file due to panic]
[MSG:INFO: Using default configuration]
[MSG:WARN: Ignored key Maslow_tlX]
[MSG:WARN: Ignored key Maslow_tlY]
[MSG:WARN: Ignored key Maslow_trX]
[
There is a PR I did today and is merged upstream to cut out the spoilboard reports unless the numbers change
1 Like
yet again. this time I tried to tell the AI to not just fix this problem, but look for other problems in the area and try to have it simulate and show the logs for a full calibration run.
let’s see what it does.
we had a ‘working’ system, it was just using the frame size as defined by the maslow.yaml, not the first 6 points, Ever since it moved that logic to take place after measuring point 5 it’s been playing wack-a-mole in finding memory not allocated at the right time, not allocated big enough, variables shadowed by local variables in a function, etc
hopefully the code analysis will find this with fewer round-trips
@bar has merged a lot of my fixes in the last few days, so I may need to end up rebasing this work manually to be able to take advantage of them and then start working on it with the AI again.