-
Notifications
You must be signed in to change notification settings - Fork 16
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
Comments
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:
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 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? |
"and no slicer seems to be able to display a print preview or anything." |
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%. |
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. |
Oh, okay. That would probably be good for me to document, then. Thanks. |
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
The text was updated successfully, but these errors were encountered: