cura 4.5 doesn't work

[asfcarvalho]

[asfcarvalho]

When I try to use the X3GWriter in CURA 4.5 the printer doesn't work, just in CURA 4.2.1

[Ghostkeeper]

I'm unable to reproduce this problem. The plug-in seems to load fine in Cura 4.5. As you can see I saved a .x3g file here:

Are you sure you've updated the plug-in? Cura 4.4 and 4.5 are supported starting from version 1.1.11.

[Digisembler]

Same sort of thing here (ish). i have version 1.1.11 on cura 4.5. slices fine, saves fine. When i go to run the file on my makerbot replicator 2x, that's where i'm having trouble...


screen images show that the file name is some sort of temp name, the bed warms up, but never clicks over to heat the nozzle. 2nd image shows (under monitoring window) that it's waiting on homing. not sure what that means, or if i can figure out how to edit that or what to do about it. (since x3g is binary... or unreadable either way). Any suggestions? thanks.

[Digisembler]

to add to this - it zeros out, but then doesn't move the bed down and move the heads over to the heat extruder spot (forward left corner, opposite the 0,0,0 spot) (whatever that command is). so, it just hangs. thanks. (old makerbot software generally works ok, but there isn't a horizontal expansion setting in the makerbot s/w, so, getting dimensionally accurate parts is tough without a lot of sanding) (the main reason i want to use cura, other than cura is just way more awesomer...

[Ghostkeeper]

screen images show that the file name is some sort of temp name

That's probably because this plug-in writes it to a temporary file, because GPX requires a file name to write to (can't write to a stream) but Cura needs it as a stream. So it creates a temporary file, lets GPX write to that file, and then reads that file back in for Cura.

I don't know what would make your printer firmware wait for homing. Perhaps the steps per mm are not configured correctly and it's homing extremely slowly or something? Or perhaps it thinks that the endstops are on the other side? I think that this is caused by having the wrong machine_x3g_variant metadata entry in your printer definition, or wrong machine settings. Which definition are you using?