Another Predator

[Carlo]

Hi,

Does anyone know if I can send the board and effector back to Duet to be tested ?

Thanks

[NexxCat]

Not sure if it will be any help, but my full Duet2Wifi config for my predator is here:
https://github.com/nexx/Anycubic-Predator-Duet

It certainly looks like you're too far away from the bed.

On the github, you'll also find the macro's I use, including one I run prior to every first print since power-on.

I'll try and help further when I can, but hopefully this helps for now. The current github is for RRF, but if you go backwards in the history, my RRF2 config is there too.

[Carlo]

@NexxCat

Thanks NexxCat I started with yours and Jay_uks and your carriage adaptors Thank you for posting them.

It isn't to far away the effector is being lifted away I've tried baby stepping but it just digs up whats been printed honestly after 4 weeks constant not sure there is any combination I have not tried and I'm really not exaggerating
So today the machine is over 6mm shorter than this afternoon according to the calibration?

[NexxCat]

Have you checked that the probe is actually returning repeatable values?

Create a macro with the following in it:

G28
G30 P0 X0 Y0 Z-9999
G30 P1 X0 Y0 Z-9999
G30 P2 X0 Y0 Z-9999
G30 P3 X0 Y0 Z-9999
G30 P4 X0 Y0 Z-9999
G30 P5 X0 Y0 Z-9999
G30 P6 X0 Y0 Z-9999
G30 P7 X0 Y0 Z-9999
G30 P8 X0 Y0 Z-9999
G30 P9 X0 Y0 Z-9999 S-1

What does the console report after the macro runs?

[Carlo]

@NexxCat

I’ll try it first thing tomorrow and post back the results.

Thanks
C

[Carlo]

@NexxCat

Hi,

Results of the macro below.

M98 P"0:/macros/Probe test"

G32 bed probe heights: -0.078 -0.065 -0.065 -0.103 -0.090 -0.078 -0.090 -0.090 -0.090 -0.065, mean -0.082, deviation from mean 0.013

Thanks for help

[NexxCat]

@Carlo Your repeatability isn't as low as mine, but it still seems well within reason:

M98 P"0:/macros/ProbeRepeatability.g"
G32 bed probe heights: -0.036 -0.036 -0.042 -0.036 -0.036 -0.042 -0.036 -0.042 -0.036 -0.036, mean -0.038, deviation from mean 0.003

When you run the delta calibration, are you doing it with the bed and nozzle cold or hot? My macro for calibrating heats the bed to 60C and the nozzle to 130C before it calibrates.

[droftarts]

@Carlo If you're probing the bed with heaters on, turn them off by adding B1 to your M558 command. To quote @dc42 here https://forum.duet3d.com/post/97669

The reason we keep the heaters off during the recovery time is that some probes (e.g. BLTouch) need to recover from the effects of the magnetic field generated by the bed heater.

Ian

[Carlo]

@NexxCat
Hi NexxCat,

Hot..220c hotend 70c Bed....I'll set the heat as you have mentioned.

Thanks

B1 added Thanks droraft.

[Carlo]

@NexxCat

Hi,

Results at 110c and 60c

M98 P"0:/macros/Probe test"
G32 bed probe heights: 4.041 4.053 4.041 4.066 4.041 4.053 4.053 4.053 4.053 4.066, mean 4.052, deviation from mean 0.009

Thanks

[Danal]

@Carlo said in Another Predator:

0.009

That's pretty darn good. Some mechanics (switch and/or overall printer) may do better... but that's a very good number on its own.

[NexxCat]

@Carlo said in Another Predator:

@NexxCat

Hi,

Results at 110c and 60c

M98 P"0:/macros/Probe test"
G32 bed probe heights: 4.041 4.053 4.041 4.066 4.041 4.053 4.053 4.053 4.053 4.066, mean 4.052, deviation from mean 0.009

Thanks

That's an excellent result, though I'm curious as why the probe heights are now in the positive and last night they were negative. That offset would certainly explain why nothing is sticking to the bed.

[Carlo]

@NexxCat

Ahh apologies I did change the endstops.... had to the only thing I hadn't changed adjusted the height so now..

M98 P"0:/macros/Probe test"

G32 bed probe heights: -0.196 -0.196 -0.196 -0.196 -0.196 -0.196 -0.196 -0.196 -0.196 -0.184, mean -0.195, deviation from mean 0.004

Better ?

Thanks

[NexxCat]

@Carlo Yeah that looks fine. Hm. What is your current Z offset set to? In config.g you're after the line like:

G31 P100 X0 Y0 Z-0.210

Sorry if this has already been mentioned in the thread, just looking for things at the state of play right now.

[Carlo]

@NexxCat

No that's fine I'll add that in....not sure I want to click upload now don't want to be disappointed ...or cry in front of dudes!

[Carlo]

@NexxCat

Sorry I didn't read that fully Z-0.06

[Carlo]

@Carlo

This is the result I think everyone looks and thinks it's too far from the bed but it's not actually completing the print move it's changing direction before it should in the picture you can see where the print does a U turn on it's self so it never joins the print together it just doesn't complete the move almost like the radius is wrong like the circle is smaller than it is I'm watching it and it does not complete the circles or arcs it never makes it to the end it changes direction and doesn't go back to finish it.

Where it has printed ..it stuck and the outer ring is on the second layer but there is a gap in it.. as have all the arcs and full circles they all have a gap in them and relative to the size the outer are bigger gaps than the inner i.e. the further out it goes the bigger the gap.

[NexxCat]

@Carlo
Have you re-sliced that bed level print, or are you printing the gcode that came with the predator?

[Carlo]

@NexxCat

Hi,

It's re-sliced and I have one sliced by another user on these forums they are both the same in fact all prints are the exactly the same.
I wanted to rule the file out so another one of you extremely helpful users kindly sliced it for me to rule the file out for my own sanity.

[NexxCat]

@Carlo
Give me a few minutes. I'm going to craft a gcode file for you to run, based on my startup settings and prime line. If you want to try that, we'll see what happens?