Open SebastianMusser opened 1 month ago
Just wanted to add that I had the same issue.
Had about 34k lines of code, paused and iosender jumped back to line 1 after starting again. That happen somewhere after line 30000.
But I didn't take any screenshots but could upload the gcode upon request.
I'll try to replicate this. On your end can you try the latest edge version - it could be that the issue has been fixed already.
grblHAL has also been recently changed related to cycle start signalling, but this is only relevant if a button is connected to the cycle start input and the job is (re)started by pressing it.
I was able to reproduce it right now again with EDGE 2.0445p7 EDGE.
And because you mentioned it - yes, I pause and resume with a button / hardkey that is attached to the flexi (I use drew's button breakout board).
Ok, I was not able to reproduce with the latest grblHAL build with a STM32F7xx board, so this could be a controller issue. Which grblHAL build are you using (Help > About)?
I am using this one https://github.com/Expatria-Technologies/STM32F4xx/releases/tag/flexi-hal-v1.0.0.2.
In order to reproduce it, you need to let the gcode run quite a bit. When I reproduced it right now, pause/resume worked fine the first 20min, but then after a while - after several tool changes - it just restarted the whole job.
I let it run to completion and did several feed holds/cycle starts with ioSender buttons. I did not try using buttons connected to the controller. What could be interesting is the output from the $LEV command (last events) after failure, I suspect that somehow reset is triggered by the cycle start signal.
ok, will try to reproduce it again and then do $LEV .
Actually my pc was still running after I hit STOP (after I reproduced it).
The output of $LEV is:
[MSG:] [MSG:] [MSG:] [MSG:] [MSG:Stop] $LEV [LASTEVENTS:H,,,,]
Update: reproduced it again, but this only happens with the hardkeys / the button breakout board. The Iosender softkeys do not seam to trigger this behaviour.
This time "$LEV" gave me [LASTEVENTS:S,,,,]
I have uploaded new edge versions (p8) for you to try. Note that there is a "bug" in the controller as well, but this only affects tool change mode 'Normal', $341=0. A fix for this has just been committed.
I have uploaded new edge versions (p8) for you to try. Note that there is a "bug" in the controller as well, but this only affects tool change mode 'Normal', $341=0. A fix for this has just been committed.
fix pulled in here: https://github.com/Expatria-Technologies/STM32F4xx/releases/tag/flexi-hal-v1.0.0.4
I downloaded and tested the p8 build, and I could not reproduce THIS issue, but I ran into something else / new:
I was trying to stress the system with several pause/ resume interactions (all with the button breakout board), and after a few attempts the machine would just refuse to resume again (this time I hit pause when it was rapiding to the tool setter)
As you can see in that video, the status is "feed hold", and the "START" button is correctly "read" (according to that red icon), but it just wont resume.
No idea if this is related to the p8 release, but this is the first time I see that.
Hi terjeio! Today I stumbled into the following issue:
I ran a pretty big gcode (26k lines, several toolchanges), and somewhere towards the end I paused the machine for a few seconds. After I hit "START" again, the machine moved a bit towards the next hole, then it raised to Zmax and stayed there.
IOsender still showed the correct line of gcode, BUT, the orange "TOOL" was lit. After I hit start again, it did a tool touch-off and then started the gcode from the first line again.
I posted this in the printnc / #grblhal channel, and Drewnabobber was able to reproduce this behaviour with 2.044, but not with 2.0.40).
Attached you find a screenshot and the gcode (had to rename it to .txt).
ZandTramplates.txt![IMG_5795](https://github.com/terjeio/ioSender/assets/152463461/d23b7bc1-734f-4084-9bae-4dd01003ad30)