Skip to content

Bug: Luban 4.15.0 ignores machine.def.json Start/End G‑Code – hardcoded G‑Code in JS bundle overrides profiles #2606

Description

🐞 bug report

Affected Version(s)

The issue is caused in version 4.15.0

To Reproduce

  1. Luban is stopped
  2. Change content of file: C:\Program Files\Snapmaker Luban\resources\app\src\app\app.a32eb564a8ba9b7552fd.bundle.js
    from s.push("G0 X-10 Y-10 F3000") to s.push("G0 X35 Y35 F3000") <=========
  3. Start Luban
  4. New project
  5. Slice project and export it
  6. Generated GCode looks like the folowing (just a snipet)

;Snapmaker Luban 4.15.0
;Mon Feb 23 2026 10:5:24
T0
M82 ;absolute extrusion mode
;Start GCode begin
G28 ;home
M104 S200
M140 S65
M109 S200 ;Wait for Hotend Temperature
M190 S65 ;Wait for Bed Temperature
G90 ;absolute positioning
G0 X35 Y35 F3000 <=========
G0 Z0 F1800

=> The START and END GCODE does not come from profile settings !!!
=> The START and END GCODE is HARD CODED in the bundle file!
=> Profiles are inkonsistent
=> Dokumentation is wrong
=> Behaviour of Slicer is not as it should

Expected behavior
Profiles should be used in the Sclicer, not the hardcoded bundle file (which is officially not documented)

🌍 My Environment

  • Operating System: Windows 11 Pro
  • Printer: Original, Snapmaker 2.0 / A350 (actual Firmware version)
  • Snapmaker Luban 4.15.0

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions