Original thread here: Gsender unable to progress past specific code line - Community Support / Vectric - Sienci Community Forum
While trying to help a user who had problems running a g-code file, I observed the g-code would crash my system when running the file check. Details are in the other thread.
Diagnostic file is attached
diagnostics_3-2-2026_10-05-34.zip (1.7 MB)
So I was looking into this and it seems to be not a gSender problem but a firmware issue.
I was able to recreate it on the SLB using gSender 1.5.7
For kicks, I ran the file through ioSender - exact same behaviour, idles at line 31186.
I’ll test the latest firmware/slbEXT on ioSender and gSender but it seems to happen regardless of sender, so not a gSender specific issue. I’m wondering if there’s an issue with planning the small movements on the firmware side.
SLB-ext and a later internal firmware (20251111) doesn’t hang the file. It does seem to be sienciHAL specific issue.
Ha!
All you guylls buying that modern speedy sturdy spindly shiney new stuff! Look at yall now, ey!
Ha!
Think I’m gonna carve this here file now on my squeaky rusty cando oldmill!
Ha!
Closing this since it’s outside our control (firmware) and also fixed in modern grblHAL versions. Thanks to everyones hard work in the original thread in helping him clean up his toolpath.
