I've been chasing an issue for a week and have narrowed it down to the point where it is worth reporting.
Specs:
Teensy 4.1
T41UX5BB v2.2
gender 1.6.2
Web Builder v1.0.1 Updated to grblHAL build/patch 20260726
After adding the "File based tool table" plugin, my Spindle relay fails to engage and the middle LED light on an M3.
Removing the plugin works as expected with relay output
With or without the plugin $pins are identical. $395=0 on both. The differences is in the report produced by $spindles.
With the tool table plugin enabled I get a list from 1-7 with the 0 entry missing entirely. Without the plugin I get the normal 0-7 with "PWM, enabled as spine 0, active" in the first slot.
For what it is worth, Claude says to my prompt: "When adding file based tooltable, I loose my 0 entry in $spindles alltogether. The list starts at 1"
Thought process
That's a more precise and telling symptom than before — this isn't a settings reset, it's an actual registration failure. One specific spindle driver (whichever was assigned ID 0 — almost certainly plain PWM, matching the pattern from grblHAL's own example output) is failing to register at all when File Based Tool Table is compiled in. Everything else keeps its original ID number; slot 0 just vanishes rather than everything shifting down.
That also explains the LED/relay behavior from your last message: your $395 is still literally set to 0 (never reset), but since nothing registers at ID 0 anymore, grblHAL falls back to some minimal default PWM-only behavior when it can't resolve the configured spindle — which is why pin 13 lights up like plain PWM even though nothing legitimate is actually assigned to that ID.
Two things to do:
Run $spindles again after this build, note the ID your relay-driving VFD driver now shows (it should still be there, just under its same original number, since only slot 0 disappeared), and set $395 to that ID explicitly.
This is worth reporting upstream — a file-based tool table plugin, which per its own docs only reads a file off the SD card, has no business causing a spindle driver to fail registration. That's a real resource/dependency conflict in how Web Builder is compiling these two together, and you have about as clean a repro case as anyone could ask for (same board, same everything else, one plugin toggle, one spindle driver silently disappears).
I've been chasing an issue for a week and have narrowed it down to the point where it is worth reporting.
Specs:
Teensy 4.1
T41UX5BB v2.2
gender 1.6.2
Web Builder v1.0.1 Updated to grblHAL build/patch 20260726
After adding the "File based tool table" plugin, my Spindle relay fails to engage and the middle LED light on an M3.
Removing the plugin works as expected with relay output
With or without the plugin $pins are identical. $395=0 on both. The differences is in the report produced by $spindles.
With the tool table plugin enabled I get a list from 1-7 with the 0 entry missing entirely. Without the plugin I get the normal 0-7 with "PWM, enabled as spine 0, active" in the first slot.
For what it is worth, Claude says to my prompt: "When adding file based tooltable, I loose my 0 entry in $spindles alltogether. The list starts at 1"
Thought process
That's a more precise and telling symptom than before — this isn't a settings reset, it's an actual registration failure. One specific spindle driver (whichever was assigned ID 0 — almost certainly plain PWM, matching the pattern from grblHAL's own example output) is failing to register at all when File Based Tool Table is compiled in. Everything else keeps its original ID number; slot 0 just vanishes rather than everything shifting down.
That also explains the LED/relay behavior from your last message: your $395 is still literally set to 0 (never reset), but since nothing registers at ID 0 anymore, grblHAL falls back to some minimal default PWM-only behavior when it can't resolve the configured spindle — which is why pin 13 lights up like plain PWM even though nothing legitimate is actually assigned to that ID.
Two things to do:
Run $spindles again after this build, note the ID your relay-driving VFD driver now shows (it should still be there, just under its same original number, since only slot 0 disappeared), and set $395 to that ID explicitly.
This is worth reporting upstream — a file-based tool table plugin, which per its own docs only reads a file off the SD card, has no business causing a spindle driver to fail registration. That's a real resource/dependency conflict in how Web Builder is compiling these two together, and you have about as clean a repro case as anyone could ask for (same board, same everything else, one plugin toggle, one spindle driver silently disappears).