Bed origin settings vs firmware settings.
-
Simplify3D / Cura does not communicate in any way
your X0 Y0 coordinates need to be correct. that is all.
and Simplify3D / Cura does not know about bed leveling. you need to add that manually.
-
@Veti ok so I'm confused again. If I've calibrated everything in the firmware then those calibrations should be reflected in Cura correct? Or do I need to do a G32 in the starting script of Cura?
Maybe I should rephrase, Cura only needs the build volume because the offsets are saved in the firmware?
-
@mmartin said in Bed origin settings vs firmware settings.:
Cura only needs the build volume because the offsets are saved in the firmware?
Yes.
regarding G32, that is not mesh bed leveling. G29 is.
-
@Veti Ok so I should just run a G29 in the firmware and the mesh will automatically be used for my sliced code from Cura?
-
@mmartin said in Bed origin settings vs firmware settings.:
Ok so I should just run a G29 in the firmware and the mesh will automatically be used for my sliced code from Cura?
i dont know what you mean by "run a G29 in the firmware".
you need to add G29 to the start G code. and its needs to be after the G28
-
@Veti In the Duet Web Interface I can send commands to the printer. So sending G29 to the printer should start the bed leveling process and save the corresponding mesh correct? Or are you saying that this has to be done in the sliced Gcode for every print?
-
if you want to use an existing heigh map, you need to issue
G29 S1 in the start of your g code (also after any G28) -
@Veti ok this answers my question. Thanks!
-
@mmartin said in Bed origin settings vs firmware settings.:
@oliof I understand this, but my question is how does it know where the origin is located? My printhead uses offsets (X-1, Y-27) to set the origin to the corner of the bed.
I think you've got it sorted out now, but here's a bit more information. M208 in your config.g tells the firmware where your extents of physical travel are. The slicer doesn't need to be aware of that specifically. All it cares about is where 0,0 is and how far it can move in X Y Z. Since you aren't going to be printing in negative space off the build plate. Some slicers like PrusaSlicer have the option to add an offset so you can set both the print volume and the offset of the 0,0 point, but Cura doesn't.
-
@Phaedrux If i were set the offsets in both the firmware and the slicer would it be doubling the offsets? This feature is available in Simplify3d as well.
-
@mmartin said in Bed origin settings vs firmware settings.:
If i were set the offsets in both the firmware and the slicer would it be doubling the offsets?
Yes, basically. Since you're already using a negative offset in M208 to place the 0,0 point on the actual printable bed area you don't need to do that again in the slicer.
In that other thread you had asked
"is there a way to add bed heat before the homing and also bed probing? My sensor needs the bed to be heated to produce accurate results. I've been doing it manually but it would be nice to automate this process as well."
Yes. Normally the slicer will check your start gcode section for any heating commands. If they exist, it will let you take control. If they don't exist, it will set the temps as configured before the start gcode section comes into play.
The slicer will also let you use some placeholder values for the temperatures in the start gcode section. Each slicer has different placeholder names, so you'll have to do some googling for your slicer.
If you want to see exactly what the slicer is doing, you need to slice a model and then look at the exported gcode file.
Regardless, if you want the temp of the bed to be 60 before you do the homing and probing, just add a command to heat the bed to 60 and wait for it to finish before the command to home and probe.
M190 S60
G28
G29 -
@Phaedrux Very Helpful. Thanks!
-
@Phaedrux what about settings such as linear progression?
-
If you mean pressure advance, that can go wherever you want really. If the value will stay the same you can put it directly in config.g. Or you can put it in the slicer start gcode.
-
@Phaedrux yes thats the one. This is where I get confused as some things I need to run in the start Gcode and others work directly from the firmware.
-
@mmartin said in Bed origin settings vs firmware settings.:
This is where I get confused as some things I need to run in the start Gcode and others work directly from the firmware.
Maybe this will help.
The firmware is configured entirely by gcode commands. Those commands are contained in macro files. A macro is just a text file with a list of commands run in order. Config.g is a macro that gets run at startup. The sliced gcode file you get from the slicer is just a macro containing all the movement commands.
Each slicer is a bit different but generally it will have a few user configurable gcode sections that you can use to send additional gcode commands before, during, after the main printing gcode.
Most things can be configured in config.g because it gets run at startup. This is where all the machine specifics are defined.
Anything that relates to prep before a print starts probably belongs either in the slicer start gcode section or if you use many different slicers you could use the macro file start.g. This macro gets run before a print starts. It can be used to home the printer, load a heightmap, preheat the bed and nozzle, set the pressure advance, etc etc.
-
@Phaedrux This is very helpful! Thanks, this type of thing should be pinned to the tuning and tweaking forum.
-
@mmartin Well it's kind of the fundamental concept of RepRapFirmware.
https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_G_Code_Everywhere
