Posts made by pr0xyfl00d3r

@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

I have a Tronxy X5SA working with the wifi version

@phaedrux said in Auto Bed Leveling Map on Tronxy X5SA:

@pr0xyfl00d3r said in Auto Bed Leveling Map on Tronxy X5SA:

i have added Z Baby Stepping
Current Offset: 0.2 mm and seems to be ok, i think i can see a slight bubble to the sheet on the bed

If you find a consistent amount of baby stepping that you need you can add it to the G31 Z value to make it permanent.

Has the height map image improved at all? Is the first layer going down better?

Yes the map has flatten by half ish..

@phaedrux said in Auto Bed Leveling Map on Tronxy X5SA:

@pr0xyfl00d3r said in Auto Bed Leveling Map on Tronxy X5SA:

What can i do to stop the Heatbed and hotend warming up before the bed leveling in the start script?

i keep getting Error: Z probe readings not consistent

The slicer will add temp commands automatically if you don't add your own, so you could add some after the homing commands if you want.

The probe readings not consistent error is because we've set the tolerance quite low with M558 S0.003 You can increase that value to make it less sensitive I think the default is 0.005.

Ok, will have to look into added some code maybe, thank you for your help with this is very appreciated.

i have added Z Baby Stepping
Current Offset: 0.2 mm and seems to be ok, i think i can see a slight bubble to the sheet on the bed

What can i do to stop the Heatbed and hotend warming up before the bed leveling in the start script?

i keep getting Error: Z probe readings not consistent

@phaedrux said in Auto Bed Leveling Map on Tronxy X5SA:

@pr0xyfl00d3r said in Auto Bed Leveling Map on Tronxy X5SA:

@phaedrux said in Auto Bed Leveling Map on Tronxy X5SA:

A10 R0.5 S0.003 B0

just to check add this to the end of the code i already have ?

Yup, add it to what you have already in your M558. Did it change the resulting heightmap at all?

@pr0xyfl00d3r said in Auto Bed Leveling Map on Tronxy X5SA:

the 0.56 i got from following https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe

That would be used in the G31 command to tell the printer how far the nozzle is from the bed when the probe triggers, but isn't useful elsewhere. You can prime the nozzle at whatever height you like. I use 0.3, but as long as it's doing what you want for the prime it can be whatever height you want. The slicer will move to the correct first layer height afterwards. Though it should be noted that having a Z move like that to prime the nozzle can confuse the DWC and result in the first layer height and layer counter to behave oddly. It may be better to move that nozzle prime into it's own macro that lives in the sys folder on the Duet. Then you can use M98 0:/sys/NozzlePrime.g to call it in your slicer start code.

@pr0xyfl00d3r said in Auto Bed Leveling Map on Tronxy X5SA:

This is from the print

That doesn't look too bad... Can you try again, this time with no brim, single perimeter, and a single layer of 0.2? That should make it easier to see.

@pr0xyfl00d3r said in Auto Bed Leveling Map on Tronxy X5SA:

But can i simplify it or need much of it?

Once you have the heightmap sorted out you may be able to get away with just doing a single detailed G29 once in a while and then loading the saved heightmap before the print rather than doing a less detailed but faster G29 before every print. It will depend on how well your bed maintains it's geometry/leveling.

@phaedrux said in Auto Bed Leveling Map on Tronxy X5SA:

@pr0xyfl00d3r said in Auto Bed Leveling Map on Tronxy X5SA:

@phaedrux said in Auto Bed Leveling Map on Tronxy X5SA:

A10 R0.5 S0.003 B0

just to check add this to the end of the code i already have ?

Yup, add it to what you have already in your M558. Did it change the resulting heightmap at all?

@pr0xyfl00d3r said in Auto Bed Leveling Map on Tronxy X5SA:

the 0.56 i got from following https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe

That would be used in the G31 command to tell the printer how far the nozzle is from the bed when the probe triggers, but isn't useful elsewhere. You can prime the nozzle at whatever height you like. I use 0.3, but as long as it's doing what you want for the prime it can be whatever height you want. The slicer will move to the correct first layer height afterwards. Though it should be noted that having a Z move like that to prime the nozzle can confuse the DWC and result in the first layer height and layer counter to behave oddly. It may be better to move that nozzle prime into it's own macro that lives in the sys folder on the Duet. Then you can use M98 0:/sys/NozzlePrime.g to call it in your slicer start code.

@pr0xyfl00d3r said in Auto Bed Leveling Map on Tronxy X5SA:

This is from the print

That doesn't look too bad... Can you try again, this time with no brim, single perimeter, and a single layer of 0.2? That should make it easier to see.

@pr0xyfl00d3r said in Auto Bed Leveling Map on Tronxy X5SA:

But can i simplify it or need much of it?

Once you have the heightmap sorted out you may be able to get away with just doing a single detailed G29 once in a while and then loading the saved heightmap before the print rather than doing a less detailed but faster G29 before every print. It will depend on how well your bed maintains it's geometry/leveling.

Ok retrying the file...

@phaedrux said in Auto Bed Leveling Map on Tronxy X5SA:

It's totally possible that the bed is actually that warped. The color map exaggerates the differences to make them easy to see, but the actual deviations aren't that extreme. -1.5 to +0.4mm wouldn't surprise me for a Tronxy bed.

What happens if you print a test file like this? Does the bed compensation work to keep the first layer in contact?

0_1546986596745_bedlevel_nozzle_0.4_200x200-0.3-0.8.stl

This is from the print

@phaedrux said in Auto Bed Leveling Map on Tronxy X5SA:

A10 R0.5 S0.003 B0

just to check add this to the end of the code i already have ?

@phaedrux said in Auto Bed Leveling Map on Tronxy X5SA:

@pr0xyfl00d3r said in Auto Bed Leveling Map on Tronxy X5SA:

M558

Can you try adding A10 R0.5 S0.003 B0 to your M558 command?

This will set it to try up to 10 probes until it gets 2 consecutive readings within 0.003, and it will wait 0.5 seconds between probe travels to let the machine settle, and will disable any heaters during the probe move to eliminate any electrical interference.

I will after this file is finished..

in my simplify3d setting for the starting script i had the following

G28 ; home all axes
G29 ; auto bed level
G1 Z0.2 F3000 ; get ready to prime
G92 E0 ; reset extrusion distance
G1 X100 E10 F600 ; prime nozzle

which i changed to
G28 ; home all axes
G29 ; auto bed level
G28 ; home all axes
G1 Z0.56 F3000 ; get ready to prime
G92 E0 ; reset extrusion distance
G1 X100 E10 F600 ; prime nozzle

now it did not hit the bed and does go through the print, the 0.56 i got from following https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe

But can i simplify it or need much of it?

The bed is not warped works perfect with factory board setup, i am running the file you posted and video what is does, when i tried a file earlier it rams in the heatbed