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.

[Smsoplaeser]

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?

[Smsoplaeser]

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.)

[Smsoplaeser]

Sorry X-axis motor current..

[terjeio]

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

[Smsoplaeser]

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.

[Smsoplaeser]

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...

[Smsoplaeser]

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

[iLoveAndyBaker]

Issue: Web Builder:
RP2040 Generic, I2C OLED display via web builder, selecting 3rd party OLED Display #1, SSD1306

Missing I2C_ENABLE section in generic RP2040 3 axis map? Strobe is there, but what about the data/clock pins?

Attempting to connect a SSD1306 via I2C to an RP2040 running generic. It's not clear from the board maps where I2C is mapped to, and the generic map lacks I2C designations like some of the other boards (PicoBob DLX, although it maps SCL to GPIO29 which I thought was an unexposed ADC pin for measuring Vsys?) so no testing was possible uploading Picobob DLX to a bare Pi Pico 2040.

Verified in OLED plugin code that the address for the OLED was 0x3C. Tried all SDA/SCL pin sets with no luck and pins defined as "aux" in the board map.

At any rate, I tested OLED example code on the same board and could get the display working with Adafruit example code, so it's wired up properly, but inop from the software side.

I'll see if it works in manual compilation, but I feel safe saying that it's not working, or isn't documented sufficiently for operation in the web builder.

Thank you!

[phil-barrett]

What does $pins give you? I see this on an RP2350B based board.

[PIN:31,I2C SCK]
[PIN:30,I2C SDA]

I ordered a couple of those displays to test. Will give it a try when they get here.

[terjeio]

The pin map was bad, fixed now. I tested the board map with my I2C LCD display and that works. My I2C OLEDs are dead so I cannot verify the OLED plugin.

[phil-barrett]

Got the display but the vendor lied - sent me 128x32, not 128x64 as claimed in the ad. Grrrr....

[iLoveAndyBaker]

Thank you for updating the pin mapping, that portion seems to have worked. Very cool that it's working on an LCD.

OLED Tested NOT working with a SSD1306 128x64 OLED display. I can confirm I2C traffic with an oscilloscope, clock and data signals look like I2C and are on the appropriate pins, and I can see data updates moving over the bus when jogging an axis. I tried the other display "drivers" as well to check for a mismatch there. As previously stated, I had these displays working on these pins with an Arduino sketch, ruling out a hardware issue.

[terjeio]

Are you sure it is a SSD1306 and not a SH1106 - or something else?

My two dead displays also accepts the I2C traffic but do not display anything. I have tried with different init sequences - but nothing on the screen... I know from earlier they can be hard to get to display anything, so perhaps they are not dead after all? And you have a similar issue - perhaps due to the init sequence beeing inncorrect?

Very cool that it's working on an LCD.

I am running the I2C interface display plugin in grblHAL and my MPG & DRO code on a separate Pico controlling the display.

[iLoveAndyBaker]

100% sure it's a 128x64 SSD1306 - Using the Adafruit example code, changing only the wire port to Wire1, SDA and SCL to 26 and 27, and changing the address to 0x3C, which is what the ssd1306_i2c.h file specifies. Photo confirms 64 pixel height. I did try the display at both 0x3C and 0x3D, I moved the address select resistor to both positions and adjusted the code accordingly, both work in Arduino, neither work in GrblHAL.

part number is GME12864 as shown on the back of the display board. The I2C address that's set doesn't determine the resolution of the display, I think it's just set as a common default, but it's up to the assembly house how they populate the board. You're certain you have the 32 pixel variety?

[phil-barrett]

I am seeing the same problem. Works with the Adafruit demo code but not grblHAL. Two different vendors, same result. The Adafruit code says that 3C is the 128x32 version but your explanation makes sense. Could be just an Adafruit thing. Maybe post an issue on the author's github site. I'm out of town until Saturday so can't check anything else.

By the way, the two displays I got have different pinouts. One is the same as in your photo, the other has Vcc at the other end.

[karoria]

I confirm SSD1306 working nicely on teensy4.1 with luc's oled plugin. I compiled the project manually not by web-builder. Just in case this might help you. I am using my customized board.

[fpq473]

The GRBLHAL2000 (iMXRT1062) supports 5 axes, so I think its profile should specify 5, not 4, axes.

https://github.com/grblHAL/iMXRT1062/blob/b1cb61cee6378b03fc7b7e2cac54aaf0c31d9037/driver.json#L130

[terjeio]

Updated now, thanks for reporting.

[Bartekn86]

Embroidery
Command failed: pio run -etest -cjob.ini
src/driver.c: In function 'driver_init':
src/driver.c:2944:21: warning: initialization from incompatible pointer type [-Wincompatible-pointer-types]
.pulse_on = spindlePulseOn,
^
src/driver.c:2944:21: note: (near initialization for 'spindle.pulse_on')
src/driver.c: In function 'ppi_timeout_isr':
src/driver.c:3215:5: error: too few arguments to function 'spindle_off'
spindle_off();
^
src/driver.c:1688:20: note: declared here
inline static void spindle_off (spindle_ptrs_t *spindle)
^
*** [.pio/build/test/src/driver.c.o] Error 1
========================== [FAILED] Took 1.09 seconds ==========================

after enable laser ppi plugin, when disabled all works properly
T41U5XBB teensy 4.1

[Bartekn86]

thank you

[terjeio]

Wb Builder updated now.

[ImagineerNL]

Great tool, some suggestions:

• Can the 'note' field be added in the json save/load? (That way we can store notes in the specific saved boardsetups.)
• The Advanced Features tab is missing some [i] blocks. I'm particularly curious on information on how to implement the functionality behind the checkboxes of.
  • Backlash compensation
  • Spindle linearisation
  • Minimize Probe overshoot

[phil-barrett]

Saving notes is a good idea.

Spindle linearization is a complex beast. deserves a complete wiki entry on it's own.

[ImagineerNL]

I know that it's more than a tooltip; other [i] blocks link to those wiki pages, on grblhal or external.
On the above subjects i couldnt find any related info, else i'd be happy to convert and submit it to a wiki page.

[engigeer]

I know that it's more than a tooltip; other [i] blocks link to those wiki pages, on grblhal or external. On the above subjects i couldnt find any related info, else i'd be happy to convert and submit it to a wiki page.

There is some info on spindle linearization here:
https://github.com/grblHAL/core/wiki/Spindle-sync

[ImagineerNL]

oh wow that is completely different compared to what i expected.
But reading that, it feels like i dont even actually need that functionality....
Started a new discussion to not go offtopic on that

[phil-barrett]

Web builder problem for PicoCNC. Spindle PWM pin appears to be left out of the build. $16=4 does not invert the PWM output (GPIO 27) and M3Sxxxx does not control it. $pins does not show GPIO 27 being assigned. This was a build with only the defaults used (PWM spindle option selected). A build from March 2025 does show GPIO 27 assigned to PWM and PWM pin behaves as expected.

[VER:1.1f.20250419:]
[OPT:VNMSL,100,1024,3,0]
[AXS:3:XYZ]
[NEWOPT:ENUMS,RT+,ES,SED]
[FIRMWARE:grblHAL]
[SIGNALS:HSEP]
[NVS STORAGE:*FLASH 4K]
[FREE MEMORY:464K]
[DRIVER:RP2350]
[DRIVER VERSION:250412]
[DRIVER OPTIONS:SDK_2.1.0]
[BOARD:PicoCNC]
[AUX IO:5,8,0,1]
[PLUGIN:Bootloader Entry v0.01]
[PLUGIN:FS macro plugin v0.17]


$pins
[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:4,Z limit min]
[PIN:10,Aux in 0,P0]
[PIN:11,Aux in 1,P1]
[PIN:12,Aux in 2,P2]
[PIN:9,Aux in 3,P3]
[PIN:26,Aux in 5,P4]
[PIN:SR8.0,X step]
[PIN:SR8.1,Y step]
[PIN:SR8.2,Z step]
[PIN:SR8.4,X dir]
[PIN:SR8.5,Y dir]
[PIN:SR8.6,Z dir]
[PIN:SR16.0,X enable]
[PIN:SR16.1,Y enable]
[PIN:SR16.2,Z enable]
[PIN:SR16.5,Spindle on]
[PIN:SR16.4,Spindle direction]
[PIN:SR16.6,Mist]
[PIN:SR16.7,Flood]
[PIN:2,Aux out 0,N/A]
[PIN:SR16.3,Aux out 4,N/A]
[PIN:SR16.8,Aux out 9,P0]
[PIN:SR16.9,Aux out 10,P1]
[PIN:SR16.10,Aux out 11,P2]
[PIN:SR16.11,Aux out 12,P3]
[PIN:SR16.12,Aux out 13,P4]
[PIN:SR16.13,Aux out 14,P5]
[PIN:SR16.14,Aux out 16,P6]
[PIN:SR16.15,Aux out 17,P7]
[PIN:13,Aux analog out 0,E0]
[PIN:25,LED G]
[PIN:1,RX,Primary UART]
[PIN:0,TX,Primary UART]

[terjeio]

A regression, should be fixed now.

[phil-barrett]

Thanks!

[Bartekn86]

hi, on actual fw, pwm output do not work, on firmware builded 09.04.2025 pwm works T41U5XBB teensy 4.1
thank you

[terjeio]

Fixed now.

[Prelo96]

Board esp32 mks tinibe1 4axis config 1 spindle pwm end enabling no directions
In web builder I got issue upgrading from old version.
Seems like the free inputs are less than before and door pin can't be enabled anymore, also no free pins for macros. Any suggestions?
Thank you

[terjeio]

I have now set number of free inputs to 1 for the Web Builder.
FYI the Web Builder is not perfect, e.g. for now I do not have data and code to add limit (depending on number of motors configured) or control inputs to the free pool - it is on my todo list.

[patrickmcquay]

looks like something in the recent change to add the pwm pin broke something if the spindle is not set to pwm:

[patrickmcquay]

This appears fixed now?

[terjeio]

Yes, should be.

[patrickmcquay]

Tried the "all" option, and now the enable pin on my z axis never goes low. Using a PicoCNC, I'm assuming this is unrelated to the above spindle issue and is more related to the newer build of the firmware.

[patrickmcquay]

Also I've since tried to go back to pwm and still the enable pin on z stays high. Every other motor works as expected.

[phil-barrett]

As a quick work around, you can just disconnect the Z enable wire.

Could you post the results of $pins?

[patrickmcquay]

client $pins
[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.2,Z enable]
[PIN:SR16.5,Spindle on]
[PIN:SR16.4,Spindle direction]
[PIN:27,Spindle PWM]
[PIN:SR16.6,Mist]
[PIN:SR16.7,Flood]
[PIN:2,Aux out 0,N/A]
[PIN:SR16.3,Aux out 4,N/A]
[PIN:SR16.8,Aux out 9,P0]
[PIN:SR16.9,Aux out 10,P1]
[PIN:SR16.10,Aux out 11,P2]
[PIN:SR16.11,Aux out 12,P3]
[PIN:SR16.12,Aux out 13,P4]
[PIN:SR16.13,Aux out 14,P5]
[PIN:SR16.14,Aux out 16,P6]
[PIN:SR16.15,Aux out 17,P7]
[PIN:13,SD card CS]
[PIN:1,RX,Primary UART]
[PIN:0,TX,Primary UART]
ok

[terjeio]

It was a bug in the shift register code, fixed now.

[patrickmcquay]

Niice! Thanks!

[JamesHagerman]

grblHAL build/patch 20250514
Driver: STM32F1xx
Board: Mach3 USB breakout (BSMCE04U)

I'm trying to build an MPG pendant using an external ESP32. I'm stuck and I can't tell if it's an issue with the web builder or some setting I've gotten wrong.

Attempting with Auxiliary input switchover

When I set MPG & DRO mode: to this value, I get an error which blocks the Generate and download firmware button: DIGITAL IN: available 0, required 1.

But that doesn't make sense based on the board map which defines AUXINPUT1_PORT and AUXINPUT1_PIN separately and should be clear for use.

Attempting with Real time command switchover

When I use this value, I can generate and flash the board... But sending the 0x8B character code to the RX pin on the 10 pin IDC connector (documented as 9 PD2 - UART5 Rx in the mach3_bob_map.h file) doesn't do anything at all.

• I've removed the pull up and pull down resistors on that line.
• The ESP32 is powered from the IDC connector and is sending 3.3v serial directly to the STM32 chip on the controller board
• I'm using grblSerial.begin(115200, SERIAL_8N1, GRBL_RX_PIN, GRBL_TX_PIN); in my code to init the serial port
• I'm sending the character code with grblSerial.write(0x8B);

But I don't see the |MPG:1 report being spit out by the controller on the USB UART in my gcode sender as expected.

For completeness:

• I'm attempting to send estop messages using grblSerial.write(0x94);
• I'm attempting to send jog messages using something like the following:

grblSerial.write(0x91);         // Command: MPG jog
grblSerial.write(0x01);         // Axis bitmask: X = 0x01
grblSerial.write(0x32);         // LSB: 50 microns = 0x0032
grblSerial.write(0x00);         // MSB: high byte of 0x0032

Further reading lead me to try setting Keypad: to UART in the Web Builder... But then I get a new error: SERIAL PORTS: available 1, required 2.

I'm not sure what I'm doing wrong here.

Is this intended to be supported by Web Builder?

[terjeio]

Is this intended to be supported by Web Builder?

Yes, but the board definition was incorrect for digital inputs and the Web Builder code claimed two serial ports when only one should be claimed. Updated now.

The real time switchover command works for me when compiling locally, I have not tested yet with Web Builder builds.
Do you get a response from the controller if you request a status by sending ? from the pendant when the keypad plugin or real time switchover is enabled?

[JamesHagerman]

Thank you for taking a look and for finding a fix!

I regret that I haven't had a chance to test the change or the response from ?.

That said, if you're curious, here's the mess I'm working with on the pendant side. https://github.com/JamesHagerman/esp32-mpg-pendant-for-grblhal

Code should be clean enough to test with but I probably need to handle responses on the TX line from the controller at some point.

I'll get back to you with results when I have them.

[JamesHagerman]

Okay, I tried sending a plain ? character out of the ESP32's TX pin to the controllers RX pin at 115200 baud, 8N1. Nothing seemed to happen on the controller. Should the sender (I'm using UGS) report something? Or is the response supposed to come over the same serial port (the one I'm not currently reading from in my firmware 😬?)

In the Web Builder, I'm picking 4 axes, Real time command switchover, Backlash compensation, and that's it. I'll try with the Keypad: set to UART tomorrow... But I can't set that and MPG at the same time. I'm not sure how that should work exactly.

[JamesHagerman]

@terjeio, I've done a bit more work on this and have an update.

I'm now seeing an <Idle|...> stream being sent to my MPG pendant firmware from the TX pin on the BSMCE04U controller board. When I send ? or 0x8B characters to the RX pin on the controller, I see no response from the controller.

Here's the output from $I via the USB serial port for the firmware I'm currently running:

[VER:1.1f.20250609:]
[OPT:VNMSL,100,1024,4,0]
[AXS:4:XYZA]
[NEWOPT:ENUMS,RT+,PROBES=1,ES,MPG,SED]
[FIRMWARE:grblHAL]
[SIGNALS:HSEP]
[NVS STORAGE:*FLASH]
[DRIVER:STM32F103RC]
[DRIVER VERSION:250609]
[BOARD:MACH3 USB BOB (BSMCE04U)]
[AUX IO:2,0,0,0]
[PLUGIN:Keypad v1.42]

Is it possible to configure grblHAL to accept commands from a sender like UGS over USB while also accepting MPG control characters from the UART on the board? I thought that was the entire point, but I'm a bit lost here and want to verify my assumptions. 😅

Thanks for the help!

[terjeio]

When I send ? or 0x8B characters to the RX pin on the controller, I see no response from the controller.

It works for me, so you may have a hardware issue?
Sending 0x8B can be tricky, when testing on a Windows machine I use a file containing the character and copy that to the serial port from a command prompt like this: copy 0x8B.txt \\.\com40

I use puTTY when testing, when opening up a connection to the main port before copying the file I see that MPG mode toggles each time I copy:

GrblHAL 1.1f ['$' or '$HELP' for help]
<Idle|MPos:0.000,0.000,0.000|Bf:100,1024|FS:0,0|Pn:XYZP|WCO:0.000,0.000,0.000|WCS:G54|Ov:100,100,100|A:|Sc:|MPG:1|H:0|T:0|P:0|TLR:0|FW:grblHAL>
<Idle|MPos:0.000,0.000,0.000|Bf:100,1024|FS:0,0|Pn:XYZP|MPG:0>

If I connect with puTTY to the MPG port when MPG is enabled, indicated by MPG:1 in the status report, then I have full control of the machine.

0x8B.txt

Is it possible to configure grblHAL to accept commands from a sender like UGS over USB while also accepting MPG control characters from the UART on the board?

Yes. The keypad plugin adds a number of other characters as well - for jogging etc. These are only acted upon if MPG mode is off.

I use a USB <> UART breakout connected to the MPG port when testing.

[crackinx]

not sure if this is an issue with GrblHAL or not, but I am compiling for a btt_skr_pro_1.2 with a Huanyang VFD using a serial to rs485 module. I have had it working in the past but I just reflashed from Ganged Y to auto square, all flashed fine but now I suddenly am getting an Alarm 14 (Spindle at speed Timeout) at boot, I have tried all settings, vfd connected and not, rs485 module disconnected, I tried flashing for both HY V1 and P2A. The Only way I can clear the error is to reflash with pwm control instead and that is not ideal. Any Help?

[crackinx]

Sounds similar to my issue: #753

Maybe there was a regression recently and I just caught the tail end of it? I thought it was an issue with my vfd or the modbus lines.

mine was booting with the error and it could not be cleared, so i couldn't even unlock the machine to test other stuff.

[patrickmcquay]

Did you happen to get the versions of the previous ones and the new one? Maybe something got fixed recently.

[crackinx]

I didn't, but if it was something that got fixed it was within the last 2 hours.

[terjeio]

So this was with a local build and not with the Web Builder? I just updated the Web Builder to the latest commit, it has been a while since I did that.

[crackinx]

No, it was with the web builder each time. If there were no changes then that's super odd.

[piyushverma]

Web Builder is doing great job, I just build for stm32f103 bluepill, it would be great if there is some document that what changes effecting what config file which can also help to build locally ifneeded.

After hours of try I am not able to build it locally with reduced code size, I try to disable my_machine.h , driver.json but it does not effect binary size.

Any suggestion or pointer will be very helpful

[terjeio]

After hours of try I am not able to build it locally with reduced code size

Which version did you download? The latest commit cannot be compiled for the *pills any more. Use the latest release instead.

I am about to remove support for the *pills in the Web Builder since I am not willing to spend the time to tweak code to make it compile anymore. Please switch to the newer Blackpills supported by the F4xx driver - they are faster and supports more features.

Web Builder is doing great job, I just build for stm32f103 bluepill, it would be great if there is some document that what changes effecting what config file which can also help to build locally ifneeded.

Basically this: do not enable optional features and compile optimized for size. Debug build will fail to compile. And use the STM32 CubeIDE to build, PlatformIO for some reason generates a larger binary. And if you are willing to dig into the core support for unused features can be removed - e.g. tool changes or stuff not supported by the driver. Be warned though - it is not easy to rip out stuff...

[phil-barrett]

Regression? I am building for PicoCNC. The resulting .uf2 loads but fails to boot. No USB port is created on the PC and there is no USB notification alert. Tried it for Pico2 (PicoCNC w/RP2350) and got the same result. In both cases I took the web builder defaults (which includes Connection: Native USB).

HW is good, older FW builds work ok.

[terjeio]

Regression?

Kind of - at least the RP MCUs behaves differently from the rest and crashes with new code... Fixed now.

[phil-barrett]

Thanks!

[phil-barrett]

Another Regression? PicoCNC and RP23U56XBB M64/M65 do not work for Aux 0 - n (2 or 7, depending on board). The value at the pins does not change. grblHAL is bounds checking the P value.

It works for earlier builds.