![]() ![]() For the Cetus, this area is from (-180, 0 to 0, 180) at least as reported by the Cetus software when moving objects around. If I'm not mistaken, the offset in Simplif圓D is used to move the origin in Simplif圓D to match the location on the printer (front left for the Cetus) so that you are sure placing components in a printable area. You put your printer height in there which raises the origin above the top of the printer in the preview screen so when placing objects they float above the top of the printer area. I did notice that the offset values on the GCODE tab in Simplif圓D are used to move the origin around the print bed. ![]() But while it might look good, if I can't use the output files.well. It heated up (still convinced this has to do with the material selected in Cetus and not the gcode file itself.?), threw error and then proceeded to start cooling down.Īnd here I got a nifty (kinda) custom STL for my Cetus setup so the screws are shown on the bed and the front is indicated with an arrow (kinda.only from the bottom thanks to limitations in Simplif圓D and how they apply the custom STL to the print bed). Opened Cetus software, initialized printer, went into "maintenance" pressed "stop" button (it wasn't doing anything anyway). Would be nice to be able to edit my previous dice. If G28 is not currently supported by the gcode interpreter, then I would think it would ignore the line (in the case of a G28-only file, it should do nothing if it doesn't know that G28 = initialize). ![]() I did find it strange that a simple G28 gcode file would cause the heater to turn on and then turn off. I'm not sure I know what you mean by the Cetus software doing something else but I'll see if I can make any progress today. I'll try to stop it before sending an gcode in case it is doing anything. And they can only find the origin by G28. I'm not an expert (been at it for about 1.5 years and learning stuff every day!) but I've never sent a gcode file to my printer that didn't start with G28 to make sure the origin is set properly (and end with G28 to park the head home after printing). Of course, that assumes the USB port is ever enabled to provide a serial connection that can be used by Octoprint/Pronterface and the like. After all, 3D printers are "dumb" as they only know where the print head is relative to where they think the origin is located. Well, that doesn't bode well for the prospect of Octoprint working, does it. ![]() So long story short: I got the weird high numbers by simply test printing and adjusting the values till the result was somewhat acceptable The difference between the gcode lengths and the actual extruded lengths seem to be vastly different with the Cetus. Also when sending the Gcode command to extrude 100mm of filament the extruder gear would barely turn. Unfortunalty I don't know the default value for the extruder's steps per unit. Then you'd get a ratio to multiply with the extruder's current steps per unit. You do that by sending Gcode to your printer to extrude a specific amount of filament and comparing that to the real extruded length of filament. When using Gcode you have to calibrate the extruder, as the printer doesn't know how much steps of the extruder motor translate into the wanted length of pushed filament. Yes they are way to high, but here ist the problem: I imported it but see some weirdness, like on the extrusion multiplier and retraction distance, whic … ![]()
0 Comments
Leave a Reply. |