# "Start from line" injecting a G54 again gsender 1.6.4

**URL:** <https://forum.sienci.com/t/start-from-line-injecting-a-g54-again-gsender-1-6-4/27642>\
**Category:** 🐛 Bug\
**Created:** [November 10, 2026, 3:05pm UTC](https://forum.sienci.com/t/start-from-line-injecting-a-g54-again-gsender-1-6-4/27642 "2026-11-10T15:05:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kpeoples86](https://forum.sienci.com/letter_avatar_proxy/v4/letter/k/ea5d25/32.png) [@kpeoples86](https://forum.sienci.com/u/kpeoples86)\
**Post date:** [November 10, 2026, 3:05pm UTC](https://forum.sienci.com/t/start-from-line-injecting-a-g54-again-gsender-1-6-4/27642/1 "2026-11-10T15:05:00Z")

</div>

This was an issue with a previous version of gsender and was fixed with an update and I just ruined a sign project where I was using G59.1 on my 4x4 Mk1 Altmill. I didn’t take a screenshot of the console but I saw the G54 in the code after running the first line of code that I had requested. I had to test it with a small gcode project because the console window drops after a certain number of lines. I started my sign project with my Z zeroed in the air and as quickly as I could hit pause the sign project’s gcode had already buffered past the starting code in the console’s history.

[This is a reference](https://forum.sienci.com/t/start-from-line/12299) to the acknowledgement of the issue and resolving it, but the issue is back in 1.6.4.

I would like to see this resolved but I now know if its fixed again every time I upgrade I have to test it to see if it’s still fixed.

---

<div class="post-metadata">

**Author:** ![Shilpa](https://forum.sienci.com/letter_avatar_proxy/v4/letter/s/a183cd/32.png) [@Shilpa](https://forum.sienci.com/u/Shilpa)\
**Post date:** [November 10, 2026, 4:04pm UTC](https://forum.sienci.com/t/start-from-line-injecting-a-g54-again-gsender-1-6-4/27642/2 "2026-11-10T16:04:19Z")

</div>

Hi @kpeoples86 , Thanks for reporting this issue and sorry about your sign project.

We have passed the issue to the development team to fix it.
