Web Builder issues 2025

[terjeio]

For reporting issues with the Web Builder. Previous discussion can be found here.

[joyfab]

grblHAL build/patch 20250114.
Driver: RP2040 (Pi Pico & Pi Pico W)
Board : BTT SKR Pico 1.0
Native USB or virtual 3 axes: No Work. Alarm $X error 79. No way to unlock.
Native USB or virtual 4 axes: run like a charm with 4 axes. $X unlock is available.
So using 4 instead 3 but don't now why..
release 20240228 was running well in 3 axis but new version give a problem on 3 axis:
no way to unlock, as well as on Pico or PicoW.

[terjeio]

Native USB or virtual 3 axes: No Work. Alarm $X error 79. No way to unlock.

$14 cannot be used to invert the estop input?

[terjeio]

Should be fixed now.

[Dexus]

grblHAL/RP2040#109

mdns not build

[TPMoyer]

Terje:
Yes I understand this is off topic, but am unaware of another way to contact you.
I made a mistake and deleted the "Additional or extended settings" page from the core/wiki
Please restore the page.

Had opened an edit to point to a new page enumerating the outputs from $help and the several $help topic   commands.     

Got stuck in the edit, and bailed by pushing the delete page button.
This deleted the original page, not just the incorrectly modified page.
Ohhhhh crap.

[terjeio]

Restored now.

[Perlovka]

Building for Teensy fails with error 422

Command failed: pio run -etest -cjob.ini
src/ioports_analog.c: In function 'wait_on_input':
src/ioports_analog.c:387:16: error: 'mcp3221' undeclared (first use in this function)
if(port == mcp3221.id)
^
src/ioports_analog.c:387:16: note: each undeclared identifier is reported only once for each function it appears in
src/ioports_analog.c: In function 'get_pin_info':
src/ioports_analog.c:412:34: error: 'mcp3221' undeclared (first use in this function)
if(pin.id == mcp3221.id)
^
src/ioports_analog.c: In function 'set_pin_description':
src/ioports_analog.c:446:24: error: 'mcp3221' undeclared (first use in this function)
if(port == mcp3221.id)
^
src/ioports_analog.c: In function 'claim':
src/ioports_analog.c:468:30: error: 'mcp3221' undeclared (first use in this function)
*port == mcp3221.id ? mcp3221.mode.claimed :
^
*** [.pio/build/test/src/ioports_analog.c.o] Error 1
========================= [FAILED] Took 16.66 seconds =========================

[terjeio]

Fixed, thanks for reporting.

[dddidi]

Was trying to build a new firmware with the web builder because I am strugling with #653 and #634 too when building with pio under windows.
But currently the build process for ESP32 boards is not working.
I have tried several times with different settings and different boards for ESP, but I always get the error: message Build failed: 504

[terjeio]

Try again now, I have been meddling with the Web Builder code (I do not have a test server yet).
If still fails the which board are you compiling for?

[dddidi]

Thank you for your quick response.
I am trying to build for the "MKS Tinybee V1.0"
For the test I did not set any parameters just selected the board and pressed generate.
But the build failed again (Build failed: 504)

[terjeio]

Builds for me. Did you reload the page (I forgot to mention that).

[dddidi]

OK. Reload of the Page did the trick.
Thank you very much for your help.
I was able to download the firmware.

[euridium]

i am trying to build for picobob_dlx. 4 axis with networking.
the reset pin is not mapped as you would expexct (gpio 3), as its state isn't changed by the estop input on a mach3 BOB.
when i compile the picobob non delux - the pin is proppery mapped and it works.

looking at the board profiles i suspect it is to do with this section :

// Define user-control controls (cycle start, reset, feed hold) input pins. Only Estop is supported on the Mach3 BOB.
#ifndef I2C_STROBE_ENABLE
#define RESET_PIN 3
#else
//reset pin is swapped to keypad when present, frees up additional input.
#define RESET_PIN 15
#define AUXINPUT2_PIN 3
#endif

so is i2c strobe set, when it should not be (i havn't selected the MPG and keyboard etc.)

thoughts?

[terjeio]

Incorrect map file, fix commited. The new server has been updated.

[customsolutions]

Back again, had to take a break and work on some other projects.... I have been following and read back thru posts but did not find anything on this.
I used webuilder, nucleo-f446re and cnc shield, i did select lightburn ppi, and cluster, 3 axis cartesian etc. When lightburn recognizes it as grbl_lpc. Any experiences/thoughts on that?

[customsolutions]

Btw, i selected ppi and cluster just to play with them. Dont know a ton about them or if that is related to the lpc issue

[terjeio]

grbl or grbl_lpc seems to be the two options available for grbl based controllers. grbl_lpc is seemingly automatically selected if the LightBurn clusters plugin is enabled. You can switch to the grbl profile manually if you want to.
BTW a better place for LightBurn support is likely their own forum - I have not used this software myself yet.

[customsolutions]

Actually here ended up being exactly where I needed to ask, because in your response you answered my question. It was because of the clusters plugin. So thank you. Not even sure if the clusters plug in is useful in my application. Currently just a nucleo with arduio cnc shield.
Thanks

[Dietz0r]

Quick question: is there a reason that the flexihal board map (STM32F4xx) is not included in the webbuilder?

[Dietz0r]

okay, so apparantly there's a python conversion script for .hex to uf2 :) so i dont need to touch the DFU or bootloader! :)

link to script: uf2 conversion script
link to source: uf2 bootloader source

[engigeer]

I think this might actually be the source for the flexi bootloader: https://github.com/Expatria-Technologies/tinyuf2

[Dietz0r]

I think this might actually be the source for the flexi bootloader: https://github.com/Expatria-Technologies/tinyuf2

correct, but the uf2 conversion should be the same

[engigeer]

It uses a custom version of grbHAL and I do not have a board to verify with,. I can add it if anybody verifies with the upstream code.

Would you be open to me submitting a PR to add some files necessary to facilitate building firmware for the flexi with the upstream code? I believe we can get it to be minimally functional with just a linker script and the uf2 conversion files, but there are also some spi and i2c customizations by Expatria that might be nice to include (with appropriate code guards of course).

[terjeio]

Would you be open to me submitting a PR

Yes - then I have something to comment on if needed.

[jubazdk]

Hi again...
I wrote not long ago about H7XX build failed error 422. And the missing 22mΩ for the TMC 5160T PLUS.
I think there is an error in the same build for the H7XX (SKR 3 EZ and TMC5160T PLUS).
When I try to set the current for the stepper motor it errors, (Error 2 - Bad number format | Missing the expected G-code word value or numeric value format is not valid.)
I just tested it with the previous firmware, witch works, and just now with the latest, and it errors.

Best regards Jubaz

[terjeio]

Which command?

[jubazdk]

In Iosender - Settings: Grbl - X-axis acceleration, if you change the mA value it errors.
(Bad number format | Missing the expected G-code word value or numeric value format is not valid.)

[jubazdk]

Sorry X-axis motor current..

[terjeio]

Odd, if you set the current from the MDI with $140 do you get the same error?

[jubazdk]

Sorry did not try that, and I just left... but the last firmware I build (web builder) just befor you fixed the 22mohm for the TMC5160T PLUS worked fine setting the current for the stepper motor.

[jubazdk]

It is not only the x axis, y, and z gives the same error too, just to let you know since you wrote $140

[terjeio]

Try a 50 milliohm build - working?
There is a buffer overflow with 22 milliohm since max current passes 10A, max validation value is four digits (9999 mA).
I'll fix the overflow in the next commit - I never expected TMC drivers outputting > 10A...

[jubazdk]

IRMS 10.6A and peak 15A.
I will try the 50 milliohm tomorrow and report back. Thank you for your help.

[phil-barrett]

iMXRT1062 Teensy 4.1/T41U5XBB. Number of Axes: 5 gets an error. MOTORS: available 5, required 6. No ganged Axis.

[terjeio]

UI bug, appears when one of the axes has two motors assigned and 5 axes is selected without deselecting two motors for the axis first.
Will fix when I add axis letter assignment option to "Number of axes".

[phil-barrett]

The error message (and greyed out generate button) persists even if you go back and change the ganged axis to single. At that point, one needs to close the page and reopen it to get it to behave.

[ViciousViscous]

I'm trying to put together a 5-axis firmware using the web builder for a teensy and I keep getting an error 422. I've even just tried a default 3-axis firmware without any settings changed and I still get and error 422.

Here are my settings:
Driver: Teensy
Board: T41U5XBB

The only options I've changed are number of axes to 5 and spindle 1 to on/off.

Command failed: pio run -etest -cjob.ini
In file included from src/networking/etag.c:43:0:
src/networking/httpd.h:52:23: fatal error: lwip/init.h: No such file or directory
compilation terminated.
*** [.pio/build/test/src/networking/etag.c.o] Error 1
========================== [FAILED] Took 1.16 seconds ==========================

Sorry if I'm missing something super obvious and it's a problem on my end.

[terjeio]

Fixed now.

[gcormier]

I'm still getting error 422 when compiling in web builder, or locally.

Command failed: pio run -etest -cjob.ini
boards/longboard32.c: In function 'board_init':
boards/longboard32.c:223:13: warning: unused variable 'port' [-Wunused-variable]
xbar_t *port;
^~~~
plugins/eventout.c: In function 'event_settings_restore':
plugins/eventout.c:390:42: warning: array subscript is above array bounds [-Warray-bounds]
plugin_settings.event[idx].trigger = Event_Ignore;
~~~~~~~~~~~~~~~~~~~~~^~~~~
spindle/offset.c: In function 'onSpindleSelected':
spindle/offset.c:85:30: error: 'parser_state_t {aka struct <anonymous>}' has no member named 'g92_coord_offset'; did you mean 'g92_offset'?
gc_state.g92_coord_offset[0] += plugin_settings.offset[0].x * (laser_spindle_id == -1 ? -1.0f : 1.0f);
^~~~~~~~~~~~~~~~
g92_offset
spindle/offset.c:86:30: error: 'parser_state_t {aka struct <anonymous>}' has no member named 'g92_coord_offset'; did you mean 'g92_offset'?
gc_state.g92_coord_offset[1] += plugin_settings.offset[0].y * (laser_spindle_id == -1 ? -1.0f : 1.0f);
^~~~~~~~~~~~~~~~
g92_offset
*** [.pio/build/test/libf72/spindle/offset.o] Error 1
========================== [FAILED] Took 3.34 seconds ==========================

[gcormier]

STM32F4xx_LONGBOARD32_EXT (2).json
This is the file I'm loading in web builder to compile.

[gcormier]

Weird. I just re-selected all settings from scratch in web builder and that error went away.

[terjeio]

Another "typo" from the latest refactoring, fixed now.

[RetEECS]

I am getting a build error whenever I select the "Add extended settings" option for the Trinamic drivers:
web_builder.log
STM32H7xx_BTT_OCTOPUS_MAX.json
(not that it really affects me much yet since I have not yet worked out what, if any, extended settings I might want to change!).

[terjeio]

A settings definitions line was inadvertenly deleted, fixed in the latest core commit. The H7 driver has to be updated for the fix to propagate.

[dresco]

For info, H7 driver has just been updated.

[terjeio]

and the Web Builder too.

[Bartekn86]

hi, is there any option to move all unciritical services from dtcm to psram ? webui, ftp, gcode buffer , errors, everything that is not FLASH labeled?
I would like to free up as much CPU memory as possible to be used for the planner buffer and step generation.

[terjeio]

Which MCU?

[Bartekn86]

sorry, i forgot to add, imxrt

[terjeio]

Ok, I recently freed 64K of RAM by decorating many functions with FLASHMEM. More could be done but be aware that the RAM used for code is allocated in 32K chunks - so a lot of the smaller functions has to be FLASHMEM'ed to free up another chunk.
Moving code to PSRAM is not trivial, and I am not sure that would be of any benefit - since the code has to come from flash in the first place. Less wait cycles?
As I understand it malloc'ed memory comes from DMAMEM, the planner buffer is malloc'ed so nothing to gain there.
Static buffers could be moved to DMAMEM as a first step, I have tried that but the system became unstable so I did not investigate further. This could be due to alignment and/or cache issues. And since the Teensy4 does not have a JTAG port it is time consuming to debug.

As for using PSRAM it would be nice if someone could try that, I currently do not have a Teensy with PSRAM so I am not able to do it. And I would think it is not something many users would need so I am not too keen to spend time on it either.

[Bartekn86]

Thank you for your comprehensive answer, I will gladly buy such a PSRAM chip and send it to you if necessary, if anyone else would like to use this memory

[slowsauce]

Build failed: 422

pibot y auto square and display

Command failed: pio run -etest -cjob.ini
In file included from main/driver.c:55:
main/grbl/motor_pins.h:453:4: error: #error "Auto squared Y-axis requires second limit pin input"
#error "Auto squared Y-axis requires second limit pin input"
^~~~~
*** [.pio/build/test/main/driver.o] Error 1
========================== [FAILED] Took 4.35 seconds ==========================

[terjeio]

Fix committed, Web Builder updated.

[gaffagnu]

I am experiencing a motor synchronization and communication issue on my Jackpot V1 board with grblHAL firmware generated via the Web Builder. On my MPCNC setup with dual endstops, the motors in the X and Y pairs run at different speeds; X1 and Y1 move at the expected speed, while X2 and Y2 move at roughly one-third of that speed. The console reports "Warning: could not communicate with stepper driver" during boot and when running M122. Perhaps indicating a failure in the UART communication with the TMC2209 drivers? This error remains on the same board slots even when motor drivers are swapped. The hardware and drivers function perfectly when running FluidNC.

[terjeio]

Can you try a new Web Builder build? I have modified the code switching the TMC UART channels a bit.

[gaffagnu]

Flashing a new build from webbuilder didn't fix the problem. I fully erased the flash and flashed bootloader, partition and firmware. If you have any specific instructions for me to try, or information to provide, i will happily do so.

[terjeio]

What is the output from the $SDS command?

[gaffagnu]

Only output from $SDS is:
[MOTORFAULT:XYZ,XY]

Below is the out from terminal when the board is booting:
Connected to /dev/ttyUSB0 with a baud rate of 115200
[SIGNALS:EP]
[NVS STORAGE:*FLASH 4K]
[FREE MEMORY:231K]
[DRIVER:ESP32]
[DRIVER VERSION:260204]
[DRIVER OPTIONS:4.4.2]
[BOARD:Jackpot]
[AUX IO:0,2,0,0]
[PLUGIN:Trinamic v0.31]
ok
$0=5.0 (Step pulse time, μs)
$1=25 (Step idle delay, ms)
$2=0 (Step pulse invert, mask)
$3=0 (Step direction invert, mask)
$4=7 (Invert step enable pin, boolean)
$5=0 (Invert limit pins, boolean)
$6=0 (Invert probe pin, boolean)
$8=0
$9=1
$10=511 (Status report options, mask)
$11=0.010 (Junction deviation, mm)
$12=0.002 (Arc tolerance, mm)
$13=0 (Report in inches, boolean)
$14=0
$15=0
$16=0
$17=0
$18=0
$19=0
$20=0 (Soft limits enable, boolean)
$21=0 (Hard limits enable, mask)
$22=0 (Homing cycle enable, mask)
$23=0 (Homing direction invert, mask)
$24=25.0 (Homing locate feed rate, mm/min)
$25=500.0 (Homing search seek rate, mm/min)
$26=250 (Homing switch debounce delay, ms)
$27=1.000 (Homing switch pull-off distance, mm)
$28=0.100 (G73 pull-off distance, mm)
$29=0.0 (Step Pulse Delay, μs)
$30=1000.000 (Maximum spindle speed, rpm)
$31=0.000 (Spindle Mode, )
$32=0 (Laser-mode enabled as spindle, boolean)
$33=5000.0 (Spindle Frequency, Hz)
$34=0.0 (Spindle Duty Cycle, %)
$35=0.0 (Minimum spindle speed, %)
$36=100.0 (Maximum spindle speed, %)
$37=0 (Deenergized Steppers, %)
$39=1 (Printable Command Characters, boolean)
$40=0 (Soft Limits Jogging, boolean)
$41=0
$42=2
$43=1 (Homing Locate Cycle, )
$44=4 (Axis Mask, )
$45=3 (Axis Mask, )
$46=0 (Axis Mask, )
$56=5.0
$57=100.0
$58=-5.0
$59=500.0
$60=0 (Restore Default Overrides, boolean)
$61=0 (Ignore Safety Door Signal, boolean)
$62=0 (Sleep Function, boolean)
$63=3 (Disable Laser on Hold, boolean)
$64=0 (Alarm on Startup, boolean)
$65=0 (Allow Feedrate Override, boolean)
$100=250.00000 (X-axis travel resolution, step/mm)
$101=250.00000 (Y-axis travel resolution, step/mm)
$102=250.00000 (Z-axis travel resolution, step/mm)
$110=500.000 (X-axis maximum rate, mm/min)
$111=500.000 (Y-axis maximum rate, mm/min)
$112=500.000 (Z-axis maximum rate, mm/min)
$120=10.000 (X-axis acceleration, mm/sec^2)
$121=10.000 (Y-axis acceleration, mm/sec^2)
$122=10.000 (Z-axis acceleration, mm/sec^2)
$130=200.000 (X-axis maximum travel, mm)
$131=200.000 (Y-axis maximum travel, mm)
$132=200.000 (Z-axis maximum travel, mm)
$140=500
$141=500
$142=500
$150=16
$151=16
$152=16
$200=22.0
$201=22.0
$202=22.0
$210=50
$211=50
$212=50
$220=22.0
$221=22.0
$222=22.0
$338=7
$339=0
$341=0 (Manual tool change mode, )
$342=30.0 (Probing distance, mm)
$343=25.0 (Probing slow feed rate, mm/min)
$344=200.0 (Probing seek feed rate, mm/min)
$345=200.0
$346=1
$372=0
$384=0
$392=4.0
$393=1.0
$394=0.0
$398=100
$481=0
$484=1
$485=0
$486=0
$539=0.0
$650=0
$673=0.0
$676=15
$680=0
$700=0
ok
[VER:1.1f.20260218:]
[OPT:VNMSL2,100,1024,3,0]
[NEWOPT:ENUMS,RT+,ES,REBOOT,TC,SED,RTC]
[FIRMWARE:grblHAL]
[SIGNALS:EP]
[NVS STORAGE:*FLASH 4K]
[FREE MEMORY:231K]
[DRIVER:ESP32]
[DRIVER VERSION:260204]
[DRIVER OPTIONS:4.4.2]
[BOARD:Jackpot]
[AUX IO:0,2,0,0]
[PLUGIN:Trinamic v0.31]
ok
[VER:1.1f.20260218:]
[OPT:VNMSL2,100,1024,3,0]
[NEWOPT:ENUMS,RT+,ES,REBOOT,TC,SED,RTC]
[FIRMWARE:grblHAL]
[SIGNALS:EP]
[NVS STORAGE:*FLASH 4K]
[FREE MEMORY:231K]
[DRIVER:ESP32]
[DRIVER VERSION:260204]
[DRIVER OPTIONS:4.4.2]
[BOARD:Jackpot]
[AUX IO:0,2,0,0]
[PLUGIN:Trinamic v0.31]
ok
[VER:1.1f.20260218:]
[OPT:VNMSL2,100,1024,3,0]
[NEWOPT:ENUMS,RT+,ES,REBOOT,TC,SED,RTC]
[FIRMWARE:grblHAL]
[SIGNALS:EP]
[NVS STORAGE:*FLASH 4K]
[FREE MEMORY:231K]
[DRIVER:ESP32]
[DRIVER VERSION:260204]
[DRIVER OPTIONS:4.4.2]
[BOARD:Jackpot]
[AUX IO:0,2,0,0]
[PLUGIN:Trinamic v0.31]
ok
ok
ok
ok
ok
ok
[G54:0.000,0.000,0.000]
[G55:0.000,0.000,0.000]
[G56:0.000,0.000,0.000]
[G57:0.000,0.000,0.000]
[G58:0.000,0.000,0.000]
[G59:0.000,0.000,0.000]
[G59.1:0.000,0.000,0.000]
[G59.2:0.000,0.000,0.000]
[G59.3:0.000,0.000,0.000]
[G28:0.000,0.000,0.000]
[G30:0.000,0.000,0.000]
[G92:0.000,0.000,0.000]
[TLO:0.000,0.000,0.000]
[PRB:0.000,0.000,0.000:0]
ok
[SPINDLE:0|0|0|*DIRV|PWM|0.0,1000.0]
ok
ok
ok
ok
ok
ok
[G54:0.000,0.000,0.000]
[G55:0.000,0.000,0.000]
[G56:0.000,0.000,0.000]
[G57:0.000,0.000,0.000]
[G58:0.000,0.000,0.000]
[G59:0.000,0.000,0.000]
[G59.1:0.000,0.000,0.000]
[G59.2:0.000,0.000,0.000]
[G59.3:0.000,0.000,0.000]
[G28:0.000,0.000,0.000]
[G30:0.000,0.000,0.000]
[G92:0.000,0.000,0.000]
[TLO:0.000,0.000,0.000]
[PRB:0.000,0.000,0.000:0]
ok
[SPINDLE:0|0|0|*DIRV|PWM|0.0,1000.0]
ok
ok
ok
ok
ok
ok
[G54:0.000,0.000,0.000]
[G55:0.000,0.000,0.000]
[G56:0.000,0.000,0.000]
[G57:0.000,0.000,0.000]
[G58:0.000,0.000,0.000]
[G59:0.000,0.000,0.000]
[G59.1:0.000,0.000,0.000]
[G59.2:0.000,0.000,0.000]
[G59.3:0.000,0.000,0.000]
[G28:0.000,0.000,0.000]
[G30:0.000,0.000,0.000]
[G92:0.000,0.000,0.000]
[TLO:0.000,0.000,0.000]
[PRB:0.000,0.000,0.000:0]
ok
[SPINDLE:0|0|0|*DIRV|PWM|0.0,1000.0]
ok

[terjeio]

I have committed a new fix for you to try. Note that I have changed the pinmap, mainly affecting PWM spindle pins.

[gaffagnu]

This version is working; the machine autohomes successfully with independent motor control on all axes. General functions seem stable. I am not using PWM for my spindle, so I haven't been able to test that specific output.

The only issue encountered so far is that running M122 causes a hard crash of the ESP32 with the following error:
[TRINAMIC]
X Y Z X2 Y2
Driver TMC2209 TMC2209 TMC2209 TMC2209 TMC2209
Set current 500 500 500 500 500
RMS current 490 490 490 490 490
Peak current 692 692 692 692 692
Run current 15/31 15/31 15/31 15/31 15/31
Hold current 7/31 7/31 7/31 7/31 7/31
CS actual 7/31 7/31 7/31 7/31 7/31
PWM scale 9 9 9 9 9
vsense 1=0.180 1=0.180 1=0.180 1=0.180 1=0.180
stealthChop false false false false false
msteps 16 16 16 16 16
tstep 1048575 1048575 1048575 1048575 1048575
pwm
threshold 0 0 0 0 0
[mm/s] 0 0 0 0 0
OT prewarn false false false false false
OT prewarn has
been triggered false false false false false
off time 3 3 3 3 3
blank time 1 1 1 1 1
hysteresis
-end -1 -1 -1 -1 -1
-start 1 1 1 1 1
Stallguard thrs 0 0 0 0 0
DRIVER STATUS:
Guru Meditation Error: Core 1 panic'ed (LoadProhibited). Exception was unhandled.
Core 1 register dump:
PC : 0x400f0ef1 PS : 0x00060f30 A0 : 0x800d9300 A1 : 0x3ffb5f60
A2 : 0x00000000 A3 : 0x3ffb5f70 A4 : 0x3ffc3db8 A5 : 0x3f409ecc
A6 : 0x3ffc3da8 A7 : 0x400d39ac A8 : 0x00000000 A9 : 0x3ffc3d70
A10 : 0x3f40a003 A11 : 0x3f409ee9 A12 : 0x000000a0 A13 : 0x3ffc3de7
A14 : 0x00000000 A15 : 0x3fc70a3d SAR : 0x00000004 EXCCAUSE: 0x0000001c
EXCVADDR: 0x00000070 LBEG : 0x400014fd LEND : 0x4000150d LCOUNT : 0xfffffffc
Backtrace: 0x400f0eee:0x3ffb5f60 0x400d92fd:0x3ffb6030 0x400de453:0x3ffb6130 0x400d4cac:0x3ffb6170 0x400d23eb:0x3ffb61b0
ELF file SHA256: 3e202ae66a80eb3a
CPU halted.

[terjeio]

The only issue encountered so far is that running M122 causes a hard crash of the ESP32

This is a bug showing up only for the ESP32, will be fixed in the next commit.

[terjeio]

M122 fix comitted.

[gaffagnu]

M122 works as intended now. Thank you for your time and work!

[nono-einstein]

Hi, when trying to build for flexihal I run into some questions and issues:

1. When o page 1 selecting # of axes, what exactly is meant here? Physical motors, or logical axes? And if the latter, is Y1+Y2 seen as one axis from the number of axes point of view? I am able to select 4 axes (where I mean to have x, y1 and 2 with autosquare, z and a rotation axis. So I connect 5 physical axes to the board and I can move these BUT the homing for Y fails. ( I am able by the way to correctly switch x, y, z and a and have to assume that y2 is a) But homing the axis y2 during Y home fails due to the software not recognizing the a limit as y2 limit. On the web I see a lot of references of the webbuilder allowing to set the appropriate links between inout and function but this is at the moment of writing at least no longer true (was it available in the past?

--> I tested with end stop 5 (M4) or 'B' for y2, and that worked.
Perhaps updating the WIKI where it is stated that the autosquare used the endstop 'A' where this, at least with flexihal, depends on whether or not a rotary axis is used.

2. I also have the issue that when selecting 5 axes the GUI assumes 6 axes needed. Perhaps this somehow conflicts internally and causes the bug?

[terjeio]

When o page 1 selecting # of axes, what exactly is meant here? Physical motors, or logical axes?

Logical axes.

And if the latter, is Y1+Y2 seen as one axis from the number of axes point of view?

Correct.

But homing the axis y2 during Y home fails due to the software not recognizing the a limit as y2 limit.

The driver designates motors as X, Y, Z and then M3, M4, ... for the rest. Additional axes (A, B, ...) are assigned to M3, M4, ... and secondary motors for X, Y and Z from remaining motors. E.g. a X, ganged/auto squared Y, Z, A -> X, Y, Z, A ->M3 and Y2 -> M4. Sadly most board labeling (silk screen) assumes no ganged/auto squared axes...

Perhaps updating the WIKI where it is stated that the autosquare used the endstop 'A' where this, at least with flexihal, depends on whether or not a rotary axis is used.

The board documentation should add this? Best would be if the boards used the same motor designation as the driver...

I also have the issue that when selecting 5 axes the GUI assumes 6 axes needed. Perhaps this somehow conflicts internally and causes the bug?

It is a bug in the WebUI, I am working on a new version where this is fixed.

[KISStek]

SP2040/BTT-SKR-Pico doesn't build the plasma code:

$I
[VER:1.1f.20260331:]
[OPT:VNMSL,100,1024,3,0]
[AXS:3:XYZ]
[NEWOPT:ENUMS,RT+,ES,TC,SED,RTC,TMC=7]
[FIRMWARE:grblHAL]
[SIGNALS:EP]
[NVS STORAGE:*FLASH 4K]
[FREE MEMORY:203K]
[DRIVER:RP2040@125MHz]
[DRIVER VERSION:260324]
[DRIVER OPTIONS:SDK_2.1.0]
[BOARD:BTT SKR Pico 1.0]
[PLUGIN:Bootloader Entry v0.01]
[PLUGIN:Trinamic v0.33]
[PLUGIN:PWM servo v0.04]
[PLUGIN:BLTouch v0.06]
[PLUGIN:FS macro plugin v0.22]
ok
RP2040_BTT_SKR_PICO_10.json

[terjeio]

It seems the board does not have enough free aux inputs, at least one is required for arc ok. Not sure if a workaround can be made.

[WilliamH-u]

I tried using the web builder for RP2040 driver and none of the board types ive tried worked for making the firmware. I tried it on many different browsers, search engines and computers, it gives me this error message when I try to make the "generic" board, no settings changed at the bottom:

"Command failed: make
/home/dev/RP2040/grbl/modbus.c: In function 'modbus_message':
/home/dev/RP2040/grbl/modbus.c:298:45: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
298 | cmd.adu[(idx << 1) + 8] = (uint8_t)(values[idx] & 0xFF);
| ~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/dev/RP2040/grbl/modbus.c:24:
/home/dev/RP2040/grbl/modbus.h:86:13: note: at offset 12 into destination object 'adu' of size 12
86 | uint8_t adu[MODBUS_MAX_ADU_SIZE];
| ^~~
/home/dev/RP2040/grbl/modbus.c:288:45: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
288 | cmd.adu[(idx << 1) + 4] = (uint8_t)(values[idx] >> 8);
| ~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/dev/RP2040/grbl/modbus.h:86:13: note: at offset 12 into destination object 'adu' of size 12
86 | uint8_t adu[MODBUS_MAX_ADU_SIZE];
| ^~~
/home/dev/RP2040/grbl/modbus.c:289:45: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
289 | cmd.adu[(idx << 1) + 5] = (uint8_t)(values[idx] & 0xFF);
| ~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/dev/RP2040/grbl/modbus.h:86:13: note: at offset 13 into destination object 'adu' of size 12
86 | uint8_t adu[MODBUS_MAX_ADU_SIZE];
| ^~~
In function 'gen_numname',
inlined from 'dir_register' at /home/dev/RP2040/fatfs/ff.c:2543:4:
/home/dev/RP2040/fatfs/ff.c:2018:15: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
2018 | ns[i] = '';
| ~~~~~~^~~~~
/home/dev/RP2040/fatfs/ff.c: In function 'dir_register':
/home/dev/RP2040/fatfs/ff.c:1989:14: note: at offset -1 into destination object 'ns' of size 8
1989 | BYTE ns[8], c;
| ^
/home/dev/RP2040/fatfs/diskio.c: In function 'send_initial_clock_train':
/home/dev/RP2040/fatfs/diskio.c:165:5: error: 'dev' undeclared (first use in this function); did you mean 'div'?
165 | dev.f_clock = 400000;
| ^~~
| div
/home/dev/RP2040/fatfs/diskio.c:165:5: note: each undeclared identifier is reported only once for each function it appears in
make[2]: *** [CMakeFiles/grblHAL.dir/build.make:1615: CMakeFiles/grblHAL.dir/fatfs/diskio.c.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:1783: CMakeFiles/grblHAL.dir/all] Error 2
make: *** [Makefile:91: all] Error 2
"

[phil-barrett]

I am also seeing build failures for RP2040 & friends. Always get the Modbus error message even when no modbus options are selected.

[terjeio]

Fix committed, it was an oversight related to fatfs (SD card) changes. The modbus related messages are warnings, I should turn those off as they are not correct.

[KISStek]

Can’t you use TH0 or THB? Those are both free ADC inputs. Mike McDonald ***@***.***

…

On Apr 18, 2026, at 2:25 AM, Terje Io ***@***.***> wrote: It seems the board does not have enough free aux inputs, at least one is required for arc ok. Not sure if a workaround can be made.

[terjeio]

Can’t you use TH0 or THB? Those are both free ADC inputs.

Those are inputs are connected via resistors and cannot be used for digital inputs since shorting the input to ground leaves the voltage at the MCU pins at 0.5 x AVDD (1.65V) which is above the max low level voltage (0.8V). A better option would be to try one of the serial port pins at P5 if you do not use that. Or possibly the SERVOS pin at P11.

[KISStek]

I was referring to using the TH0 or THB pins for the Arc Voltage input. I believe they are plenty of digital pins that could be used for Arc OK. But whatever, I’ve switched to a BTT SKR 3 H723 that I can build for myself. Mike McDonald

…

On Apr 21, 2026, at 1:53 PM, Terje Io ***@***.***> wrote: Can’t you use TH0 or THB? Those are both free ADC inputs. Those are inputs are connected via resistors and cannot be used for digital inputs since shorting the input to ground leaves the voltage at the MCU pins at 0.5 x AVDD (1.65V) which is above the max low level voltage (0.8V). A better option would be to try one of the serial port pins at P5 if you do not use that. Or possibly the SERVOS pin at P11. — Reply to this email directly, view it on GitHub <#645?email_source=notifications&email_token=BAUENQFKAPCOVOTN4GVNUI34W7NTZA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRWGYYTENZTUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-16661273>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BAUENQBWSQIEXFZAMT6V7DD4W7NTZAVCNFSM6AAAAABUOK4KZOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMNRWGEZDOMY>. You are receiving this because you commented. [ { ***@***.***": "http://schema.org", ***@***.***": "EmailMessage", "potentialAction": { ***@***.***": "ViewAction", "target": "#645?email_source=notifications\u0026email_token=BAUENQB2XW4HS3I7E3AARUL4W7NTZA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRWGYYTENZTUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSVWO3LBNFWF6Y3MNFRWW#discussioncomment-16661273", "url": "#645?email_source=notifications\u0026email_token=BAUENQB2XW4HS3I7E3AARUL4W7NTZA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRWGYYTENZTUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSVWO3LBNFWF6Y3MNFRWW#discussioncomment-16661273", "name": "View Discussion" }, "description": "View this Discussion on GitHub", "publisher": { ***@***.***": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[KISStek]

Maybe a better solution is to not allow the PLASMA option for boards that can’t easily support it. Mike McDonald

…

On Apr 21, 2026, at 3:18 PM, Michael McDonald ***@***.***> wrote: I was referring to using the TH0 or THB pins for the Arc Voltage input. I believe they are plenty of digital pins that could be used for Arc OK. But whatever, I’ve switched to a BTT SKR 3 H723 that I can build for myself. Mike McDonald > On Apr 21, 2026, at 1:53 PM, Terje Io ***@***.***> wrote: > > > Can’t you use TH0 or THB? Those are both free ADC inputs. > > Those are inputs are connected via resistors and cannot be used for digital inputs since shorting the input to ground leaves the voltage at the MCU pins at 0.5 x AVDD (1.65V) which is above the max low level voltage (0.8V). A better option would be to try one of the serial port pins at P5 if you do not use that. Or possibly the SERVOS pin at P11. > > — > Reply to this email directly, view it on GitHub <#645?email_source=notifications&email_token=BAUENQFKAPCOVOTN4GVNUI34W7NTZA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRWGYYTENZTUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-16661273>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BAUENQBWSQIEXFZAMT6V7DD4W7NTZAVCNFSM6AAAAABUOK4KZOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMNRWGEZDOMY>. > You are receiving this because you commented. > > [ { ***@***.***": "http://schema.org", ***@***.***": "EmailMessage", "potentialAction": { ***@***.***": "ViewAction", "target": "#645?email_source=notifications\u0026email_token=BAUENQB2XW4HS3I7E3AARUL4W7NTZA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRWGYYTENZTUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSVWO3LBNFWF6Y3MNFRWW#discussioncomment-16661273", "url": "#645?email_source=notifications\u0026email_token=BAUENQB2XW4HS3I7E3AARUL4W7NTZA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRWGYYTENZTUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSVWO3LBNFWF6Y3MNFRWW#discussioncomment-16661273", "name": "View Discussion" }, "description": "View this Discussion on GitHub", "publisher": { ***@***.***": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[ionstorm66]

Is it possible to use the MCP3221 arc voltage board on boards with no analog inputs? Both MCP3221 and plasma aren't available for the Scylla, which has i2c but no analog inputs free.

[terjeio]

It is possible when the I2C bus is available and it is for the Scylla. The MCP3221 option is not available in the Web Builder since the board data provided does not have I2C capability listed. @dresco may add it.

[dresco]

Thanks @terjeio, will do. Best to add for all board I guess, as per the F4xx driver?

[terjeio]

The best is just to add "i2c": 1 to the boards with a header for the I2C bus.

[ionstorm66]

Did a test locally and it works perfectly.

[patrickmcquay]

looks like there is something going on with aux pin assignments on the PicoCNC, when only a MODVFD spindle is selected. I'm not using any other spindle, and I've left the ModBus RX/TX direction output checkbox unchecked as I have an interface that handles that for me.

m64 p0 does nothing that I can see
m64 p1 turns on the spindle enabled output
m64 p2 turns on aux0
m64 p3 turns on aux1
m64 p4 turns on aux2

Here is the board settings file from web builder:
RP2040_PICO_CNC (2).json

And here is a $pins output from the board running that firmware:

[PIN:7,Feed hold]
[PIN:8,Cycle start]
[PIN:22,Emergency stop]
[PIN:28,Probe]
[PIN:6,X limit min]
[PIN:5,Y limit min]
[PIN:3,Y limit min 2]
[PIN:4,Z limit min]
[PIN:9,Aux in 0,P0]
[PIN:26,Aux in 2,P1]
[PIN:SR8.0,X step]
[PIN:SR8.1,Y step]
[PIN:SR8.3,Y2 step]
[PIN:SR8.2,Z step]
[PIN:SR8.4,X dir]
[PIN:SR8.5,Y dir]
[PIN:SR8.7,Y2 dir]
[PIN:SR8.6,Z dir]
[PIN:SR16.0,X enable]
[PIN:SR16.1,Y enable]
[PIN:SR16.3,Y enable]
[PIN:SR16.2,Z enable]
[PIN:SR16.6,Mist]
[PIN:SR16.7,Flood]
[PIN:2,Aux out 0,N/A]
[PIN:SR16.4,Aux out 5,P0]
[PIN:SR16.5,Aux out 6,P1]
[PIN:SR16.8,Aux out 9,P2]
[PIN:SR16.9,Aux out 10,P3]
[PIN:SR16.10,Aux out 11,P4]
[PIN:SR16.11,Aux out 12,P5]
[PIN:SR16.12,Aux out 13,P6]
[PIN:SR16.13,Aux out 14,P7]
[PIN:SR16.14,Aux out 15,P8]
[PIN:SR16.15,Aux out 16,P9]
[PIN:25,LED G]
[PIN:13,SD card CS]
[PIN:1,RX,Modbus]
[PIN:0,TX,Modbus]

[terjeio]

Spindle enable and direction outputs for the PWM spindle are claimed from the aux output pool and freed up when not enabled.
SR16.4 is spindle direction when enabled, P0 when not.
SR16.5 is spindle enable when enabled, P1 when not.
Both works for me when testing with LEDs connected to the Spindle pin header.

FYI P numbers are always started from P0 and and are consecutive, configuration changes that alter which aux pins are claimed may alter their mapping to the actual outputs,.

[patrickmcquay]

Ohh. I wasnt testing direction, because its not in the outputs in the middle right of the board. Thats my bad. I will verify that that works as well.

I guess I was also assuming that P0 was always going to be aux0 as well.

I appreciate the information.