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.

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

Extruders don't heat up? #18

Open
LukeBonathan opened this issue Oct 25, 2018 · 5 comments
Open

Extruders don't heat up? #18

LukeBonathan opened this issue Oct 25, 2018 · 5 comments
Labels
enhancement This will change the expected behaviour.

Comments

@LukeBonathan
Copy link

Hi there

I'm now able to export a file using the x3g writer. However the files I export don't engage the extruder heaters. Is there a logical reason for this or might I be missing something?

cube.x3g.zip

Thanks,

Luke

@Ghostkeeper
Copy link
Owner

Ghostkeeper commented Oct 27, 2018

I don't know of a good way to decode X3G files to see if it's instructing the printer to heat... 😢 It's not a plaintext format, and no slicer seems to be able to display a print preview or anything.

There are 4 possible causes I can think of:

  • Cura isn't outputting the temperature commands in its g-code.
  • This X3GWriter plug-in calls upon GPX to convert g-code to X3G. The plug-in could be calling GPX with the wrong parameters.
  • GPX isn't outputting the temperature commands in its X3G even though they are present in the g-code.
  • The firmware isn't heating the extruders when reading the X3G file.

The first should be easy to test: Save your slice to g-code instead, and see if there are any M104 or M109 commands in the file. If there are not, then there's two things you need to check in your Machine Settings (under Manage Printers...):

  • The g-code flavour must not be set to "ultigcode".
  • In the starting g-code, there should either not be any {material_print_temperature} or it should be in the last M109 or M104 command.

The second can be verified if you have a Cura log of the moment that you're saving the X3G file. X3GWriter puts a log entry of the command that it sends to GPX.

For the third and fourth options, all I can really do is search the internet for bugs. What's your printer, and is the firmware of the printer up to date?

@Ghostkeeper Ghostkeeper added the help wanted The developers need help from the community to solve this. label Nov 18, 2018
@Meganium97
Copy link

"and no slicer seems to be able to display a print preview or anything."
I am using flashprint and when I import said file, it outputs a "Load file failed" error.
As a side note, anything I export as x3g using this software always will output this same exact error when importing to flashprint.

@Ghostkeeper
Copy link
Owner

I've used FlashForge in the past too to visualise it (this post is really quite old) but in its current form (v4.6.0) FlashForge seems to just display a bunch of squares, a bit like what Cura does when the flow is set to 99999%.

@Meganium97
Copy link

I’ve figured it out now. I believe that x3gwriter is outputting the newer sailfish version of makerbot firmware and that is what is confusing flashprint. I recently upgraded my FFC to sailfish and now it works flawlessly.

@Ghostkeeper
Copy link
Owner

Oh, okay. That would probably be good for me to document, then. Thanks.

@Ghostkeeper Ghostkeeper added enhancement This will change the expected behaviour. and removed help wanted The developers need help from the community to solve this. labels Jun 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement This will change the expected behaviour.
Projects
None yet
Development

No branches or pull requests

3 participants