@dc42 said in Bed Mesh, then heat up:

@pr0xyfl00d3r said in Bed Mesh, then heat up:

I was ok, but if i run the print it heats the bed and hotend before the mesh, i want to run the mesh before the heating but cant figure out how to delay the heating

Assuming that you are printing a GCode file from the SD card, you can put the homing and mesh bed compensation commands in start.g instead, so they get executed before the heating commands that your slicer puts at the start of the GCode file. You may also wish to include a T0 command in start.g.

Thanks for the reply..

Can you give me an example of what to put in the start.g as I'm new to Duet,

is it as simple as the following?

;homeall.g

g28 ; Home All
g32 ; Bed mesh
T0

also, do I have to put something in the gcode to trigger the start.g?

@deckingman said in Bed Mesh, then heat up:

@pr0xyfl00d3r So essentially what you have a series of gcode (or mcode) commands that you want to run consecutively, before a print. You can either put all those commands into your slicer start gcode section, or you can put them in a macro, or you can use a combination of both - i.e. call a macro from the slicer start gcode.

A macro is nothing more than a sequence of commands that get carried out one after another. The homing files are examples of this. There is no point in re-inventing the wheel so you wouldn't want to put all the individual homing commands into the start gcode or some other macro - you just call the homing macro from within another, or the start gcode section of the slicer.

I feel that I might not have explained that well. Does it help or have I confused you even more?

I was ok, but if i run the print it heats the bed and hotend before the mesh, i want to run the mesh before the heating but cant figure out how to delay the heating

I'm looking how to get the following to work when i start a print.

Home,
Auto Bed Mesh
Home
Heat bed and Hotend,
Prime
Start the print.

does this all go in the slicers gcode or can i use the g files on the board?

Also during the print when it comes to the point when its about to change layers extra material comes out leaving a lil bump that the nozzle hits

@gavatron3000 said in Retraction seams to be reversed:

I see your esteps are up near 800. You might be over speeding your stepper. With my old bondtech qr I wasnt able to go much past 50mm/s and I was around 500 steps that was roughly 500rpm at the stepper

I have an E3D Titan with the compact stepper they sell which in the documentation they say to start of with 837 but after running some config test with extruding some material I found that E797.332 was good,

I got this after testing extruding 100mm of filament.

@phaedrux said in Retraction seams to be reversed:

@pr0xyfl00d3r looks like your extruder acceleration is 10000 and 80mms retraction is quite fast. I wonder if the motor is perhaps skipping or stuttering which maybe looks like it's going in reverse? Try reducing e acceleration to say 3000.

Also try disabling wipe.

Ok will give it a go.

@phaedrux said in Retraction seams to be reversed:

Need a lot more information.

Board version? Firmware? config.g? Slicer settings? Pictures? Video?

Duet 2 Wifi, v1.04.
0_1549934973886_config-3.g
Simplify3d is 4.1.1

I will try do a video later

At the point, my printer is set to retract before a move a fair amount of filament comes out from the hotend onto the print.

I am using Simplify3D for the slicer on a Tronxy x5sa

Here is my Z probe connections and config file

0_1547187024799_config.g

I have this working on my X5SA,

I have my Sensor with + & - plugged into a always on fan with the 12v jumper on and the signal cable going into the Z probe in which is next to the PanelDue connector,

Here is the Config for Z probe fron my config.g file

; Z-Probe
M574 Z1 Z2 S2 ; Set endstops controlled by probe
M558 P5 I1 H5 F120 T6000 A10 R0.5 S0.005 B0 ; Set Z probe type to modulated and the dive height + speeds
G31 P500 X-35 Y0 Z0.26 ; Set Z probe trigger value, offset and trigger height
M557 X10:300 Y20:310 S50 ; Define mesh grid