Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

no start gcode #19521

Closed
Scull215 opened this issue Aug 10, 2024 · 18 comments
Closed

no start gcode #19521

Scull215 opened this issue Aug 10, 2024 · 18 comments
Labels
Status: Under Investigation The issue has been confirmed or is assumed to be likely to be a real issue. It's pending discussion. Type: Discussion Open-ended discussion (compared to specific question).

Comments

@Scull215
Copy link

Cura Version

5.7.1

Operating System

windows 11

Printer

elegoo neptune 4 plus

Reproduction steps

i send the gcode and im not getting any part of the start gcode in the gcode file but i do have it in the slicer

Actual results

no start gcode

Expected results

start gcode then file

Add your .zip and screenshots here ⬇️

XYZ 20mm Calibration Cube - 1278865.zip
@Scull215 Scull215 added Status: Triage This ticket requires input from someone of the Cura team Type: Bug The code does not produce the intended behavior. labels Aug 10, 2024
@GregValiant GregValiant added the Status: Needs Info Needs more information before action can be taken. label Aug 11, 2024
@GregValiant
Copy link
Collaborator

Thanks for the report.
I've never heard of that before and I've never had the problem.
We will need a project file and the Cura.log file. Zip them up and post them here. The instructions are on the page you filled out for the report.

@Scull215
Copy link
Author

Scull215 commented Aug 11, 2024 via email

@github-actions github-actions bot removed the Status: Needs Info Needs more information before action can be taken. label Aug 11, 2024
@GregValiant
Copy link
Collaborator

You cannot post files here via Email. You must come here and post the file. All files must be "zipped".

@Scull215
Copy link
Author

cura.log.zip

@LilBub
Copy link

LilBub commented Aug 13, 2024

One question - how is the gcode being sent? SD card? USB connection (i.e. Octoprint, etc.)
I ask since I had a similar issue that required "Wait for Nozzle Heat" to be checked.

@Scull215
Copy link
Author

Scull215 commented Aug 13, 2024 via email

@GregValiant GregValiant added Status: Needs Info Needs more information before action can be taken. and removed Status: Triage This ticket requires input from someone of the Cura team labels Aug 13, 2024
@GregValiant
Copy link
Collaborator

This doesn't seem to be a Cura problem. Something you are doing locally (hardware, software, firmware) seems to be keeping the StartUp gcode from making it to the printer. The log file indicates the StartUp is being added.

Have you tried saving to an SD card just to see if the gcode is correct when it comes out of Cura?

@Scull215
Copy link
Author

Scull215 commented Aug 13, 2024 via email

@github-actions github-actions bot removed the Status: Needs Info Needs more information before action can be taken. label Aug 13, 2024
@Scull215
Copy link
Author

Scull215 commented Aug 13, 2024 via email

@GregValiant
Copy link
Collaborator

Do a slice, save the gcode file. Zip the gcode file and post the zip folder here directly to the site.
This is the only report about this "Disappearing StartUp" problem and your log looked good.
It would be helpful if you carefully described your printing process from the time slicing ends until the printer starts to move. Step by step.

@Scull215
Copy link
Author

I added 2 files 1 is resliced not even 10 min ago and the other I redownloaded from the printer the downloaded one was uploaded to it through the cura/moonraker connection with the start print button checked
EN4P_xyzCalibration_cube1.zip
EN4P_xyzCalibration_cube (downloaded from printer).zip

@GregValiant
Copy link
Collaborator

As you stated, there is no "StartUp Gcode" in either file you posted.
When I install an Elegoo Neptune 4 Plus in Cura the StartUp Gcode in the Cura Machine Settings is this:

;ELEGOO NEPTUNE 4 PLUS
M220 S100 ;Set the feed speed to 100%
M221 S100 ;Set the flow rate to 100%
M104 S140 ;Start heating extruder
M190 S{material_bed_temperature_layer_0} ;Wait for the bed to reach print temp
G90
G28 ;home
G1 Z10 F300
G1 X115 Y0 F6000
G1 Z0 F300
M109 S{material_print_temperature_layer_0} ;Wait for extruder to reach print temp
G92 E0 ;Reset Extruder
G1 X115 Y0 Z0.4 F300 ;Move to start position
G1 X215 E30 F400 ;Draw the first line
G1 Z0.6 F120.0 ;Move to side a little
G1 X210 F3000
G92 E0 ;Reset Extruder

And that is what shows up in the Gcode file I generate.
If you go to "Settings / Printer / Manage Printers" and then click on "Machine Settings" what do you have in the StartUp Gcode box in the lower left of the dialog?
This is the stock installation of the Neptune 4 Plus
image

@Scull215
Copy link
Author

Scull215 commented Aug 14, 2024 via email

@GregValiant
Copy link
Collaborator

I don't know. There may be something in the MoonRaker plugin that is causing it. As far as I can tell, if MoonRaker is not involved then the Gcode should contain the StartUp gcode as shown in Cura. There are posts on Reddit regarding problems with the Neptune 4 Plus and MoonRaker. 5.7.1 is old enough that any incompatibilities with MoonRaker should have been discovered and fixed by the author.

Have you tried just copying the Gcode to an SD card and printing from the SD card? Making everything as simple as you can would be a good place to start. The Gcode file you save should have the StartUp Gcode in it. (You can open any Gcode file in a text editor like Windows Notepad.)
As you add complexity to the workflow you will know when something breaks it.

@Scull215
Copy link
Author

Scull215 commented Aug 14, 2024 via email

@Scull215
Copy link
Author

EN4P_xyzCalibration_cube.zip
Ya same thing happened, printer inbuilt homing at start of print then it tried to go straight to printing without preheating Klipper errored due to under minimum temp
note: yes with the start code it does normally home the printer twice at the start of every print

@GregValiant
Copy link
Collaborator

GregValiant commented Aug 15, 2024 •
edited
Loading

When Cura slices something and puts together the toolpath into what will become the gcode file, the gcode file is stored in sections.
Section 0 is the opening paragraph from:
;FLAVOR:Marlin
to
;POSTPROCESSED

Section 1 is from:
;Generated with Cura_SteamEngine 5.8.0
to
;LAYER_COUNT:114

Section 2 contains more than just the startup gcode, and section 2 is missing in it's entirety. That would seem to imply a badly behaving plugin, or post processor.

You have a non-Cura plugin installed.
;Thumbnail generated by the Elegoo Neptune Thumbnails plugin version 4.4.0
I think that plugin is behaving badly and deleting your "section 1" that includes the StartUp Gcode.
So disable or un-install that plugin and try again.

@GregValiant GregValiant added Type: Discussion Open-ended discussion (compared to specific question). Status: Under Investigation The issue has been confirmed or is assumed to be likely to be a real issue. It's pending discussion. and removed Type: Bug The code does not produce the intended behavior. labels Aug 15, 2024
@GregValiant
Copy link
Collaborator

I'm going to remove the bug label and close this because the problem is that Elegoo plugin.
You can post a bug report on the the plugin author's github page HERE.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Status: Under Investigation The issue has been confirmed or is assumed to be likely to be a real issue. It's pending discussion. Type: Discussion Open-ended discussion (compared to specific question).
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@LilBub @GregValiant @Scull215