Another Predator
-
Hi Ian,
I used the original effector with the mag arms (printed the adapters) whats funny is I didn't even try to get anything level or square I literally slapped it together set the offset 1 level and it just worked.
I have the effector still wired I can carefully attach it to the Duet2 and try it i cant fit the effector to the other board it's locked down
but I've written this thing off now I don't expect this to ever work with duet but after spending all this time I do want to know whats wrong maybe it will help someone else some day...probably notI post a video of it once its fitted
Thanks
C -
-
-
@Carlo
What is your current Z probe offset? -
G31 P100 X0 Y0 Z-0.159
-
@Carlo
I can't remember offhand which way to adjust the offset to bring it closer, but try both of these, one will certainly be too high, but the other, does that give you a 0.1mm gap when running the macro I posted?G31 P100 X0 Y0 Z-0.059 G31 P100 X0 Y0 Z-0.259 -
They have all been tried
it's 0.05 to bring it closer dc42 suggested 0.05 so I've tried all the -0. possible infact the video I posted is -0.05
-
@Carlo
I know you've tried them whilst printing, but try -0.059 and run the macro. Is the gap 0.1mm? -
-
@Carlo
So with -0.059, the gap is exactly 0.1mm after running the macro I posted. Correct? -
Yes spot on 0.1mm
-
@Carlo
Ok, set that in your config. Then create the bed mesh with G29 S0. Once the mesh is complete, try to print the levelling model.I know you've done this so many times before, but let's try now we know the nozzle positioning is correct ok? Use the level_test.gcode I have you before, because I know it doesn't have anything in it to mess with the settings.
-
-
It failed but it's too close to the bed just I think but its the best its ever looked.
-
@Carlo
So it was sticking but not extruding because it was too close? Try changing the offset to say -0.1? -
Sorry been having net issues i'll adjust it 0.01 increments see if it works better.
It was extruding and really sticking but as it did the next pass it was squishing too hard almost transparent and curling up at the outer edges indented in the middle as it cooledThanks
C -
Hi NexxCat,
Can I ask is Z hop enabled in the bed level test file you kindly sliced for me ?
Or is that controlled via config.g ? ...so print files call M207: Retraction if Z hop is set on M207 in config.g Z hop is invoked on all Retractions ?Thanks
C -
@Carlo said in Another Predator:
It was extruding and really sticking but as it did the next pass it was squishing too hard almost transparent and curling up at the outer edges indented in the middle as it cooled
This makes it sound like the first layer printed fine, but when printing the second layer it was too close, ie it didn't move correctly/far enough in Z. This made me think either you Z jerk or acceleration is too high, or your steps per mm are wrong (which would explain a lot!). I haven’t found the standard Marlin config for the Anycubic Predator, but did find https://github.com/halofx/Marlin-2.0-Predator/blob/master/Marlin/Configuration.h
Steps per mm on each axis are 80, for standard 1.8 degree motors. You haven’t changed yours for 0.9 degree, have you?
I haven’t been through the Marlin config for acceleration and jerk settings, as on phone with tiny screen! But would be worth checking. Just remember Marlin specifies speeds in mm/sec, RRF in mm/min. If you have the Marlin configuration.h you’re running on your standard board, even better; please post it.
Ian
Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : TronXY X5S with Duet 3 MB6HC and Roto toolboard
-
@Carlo said in Another Predator:
Can I ask is Z hop enabled in the bed level test file you kindly sliced for me ?
Or is that controlled via config.g ? ...so print files call M207: Retraction if Z hop is set on M207 in config.g Z hop is invoked on all Retractions ?Firmware retraction must be enabled in the slicer. That will replace any G1 E-# moves with a G10/G11 to retract and unretract. The config.g must then contain an M207 command to tell the firmware how much and how fast to unretract. Zhop can be added in the slicer and or firmware retraction command.
If you don't have an M207 command in your config.g then nothing will happen when a G10/G11 is encountered in the gcode file.
If you look at the gcode file itself you should be able to tell by looking for G10/G11.
-
Hi Ian,
No they are set to 80 ...this is a Gorrila board which as far as I know is chit-tu based ? so M500 is like M8500 and not sure all the commands for it are known and the board is locked down... again as far as I know.
I wish it was set wrong...NexxCat was kind enough to have sliced the test file for me and it's very close so just using that to adjust trigger height..
it's really close but the Z hop seems to be an issue.Thanks
C
