Beginner Needs Help - Anycubic Kossel Plus + Duet WiFi -- HOW?

deckingman

@dougal1957 Yes that would do it too I didn't even look at the config file.

Danal

I have Anycubic Kossel with TriGorrilla, and I have a couple of printers with Duet. Everything I have is a Delta. So maybe I can help. First specific q/a:

Where does the probe (the one that attaches with a magnet) wire to the Duet board?

Physical WIring: Attach it to the Z- endstop connector. See red circles in diagram. For a microswitch, polarity does not matter.

Configuration: In your config M558 command, specify Mode 4, and in the G31, the offset between the nozzle and the probe. The X/Y/Z offsets in the G31 need to be set to YOUR printer. Eyeball it to start with, and refine later.

Something close to:

G31 X20 Y10 Z5 P25
M558 P4 X0 Y0 Z1 H5 F100 T2000

alt text

mindbender9

@dougal1957 @deckingman

Thank you for your help with this. I really appreciate it.

I've uncommented the "Heater" section and now the Bed/"Heater 0" tool responds correctly and heats up as expected.

~~Unfortunately, the "Tool 0"/"Heater 1" line still displays a temperature of 2000C and "fault" - it does not change if I select a different temperature to test. Any suggestions?~~

mindbender9

@danal

Hi Danal - Thank you for the advice. Here's where I am:

a. I've re-crimped the "Z-" wire to the endstop connector and updated my config.g file with the new G-codes. The Z-value now shows a height value. Unfortunately, the "Z-probe" sensor value is still stuck at 1000. Is this ok?

b. When I press the "auto delta calibration" button in the web interface, the hot-end drops down and attempts to do its thing. Several errors pop up and eventually the process just stops.

0_1526409133657_efe9bba7-900b-414a-9e11-e0654c00fbb9-image.png

c. ~~Question: Where does the "T0" wire from the hot-end connect to? Is this why the "Tool 0"/"Heater 1" temperature is still displaying 2000C and has the following error?~~

"~~Error: Temperature reading fault on heater 1: sensor open circuit~~"

I really appreciate all of the help. How do you like your delta printers with the Duet boards? Do you have any tips or recommendations? Thanks again.

mindbender9

@dougal1957 @deckingman

Update - I reterminated the Hot-End/"Heater 1" power cables and moved the "T0"/Hot-End thermistor to the matching E0 dual pin connector. Both of the Heaters (Hot-End and Bed) are now responding to the temperature settings successfully.

Thank you for your help with this. The only thing remaining is to troubleshoot what these Z-probe errors are - and getting to understand what calibration means. The resources here are difficult to say the least.

But thanks again for getting my two Heater sources working. Cheers!

Danal

On your M558 command, add "I1". (That is an "eye one").

This inverts the probe. At the moment, the duet thinks the switch has already hit the bed, thus the "...already triggered...".

Once it is inverted, it should eliminate those error messages.

Danal

@mindbender9 said in Beginner Needs Help - Anycubic Kossel Plus + Duet WiFi -- HOW?:

I really appreciate all of the help. How do you like your delta printers with the Duet boards? Do you have any tips or recommendations? Thanks again.

Personally, I love them, and REALLY like the Duet with the Smart Effector. That effector uses the nozzle itself as a probe, so you can have a G32 in your "print start gcode".

Hints:

Once you get G32 working, be sure you "save" the results with an M500... and be sure that the printer "loads" the results every time it boots by having an M501 somewhere near the end of your "config.g".
Be sure the M665 L value is correct. This is the length of the diagonal rods, "joint center to joint center". Your Anycubic documentation should have this. This is the one parameter that G32 does NOT set... and is foundational to G32 getting the things it does set, getting those correct.
You should only have to probe/calibrate the printer when something changes. Removing and replacing the bed, changing nozzles, etc.

My sequence when calibrating the printer is something like:

Part 1:

Attach your probe.

Optionally, Heat the bed and the extruder. This increases the accuracy of the calibration, but is not absolutely required.

Machine Control > Auto Delta Calibration

Go to the G-Code Console and check the "deviation". Perhaps run it again and see if it gets better. Learn what is typical to YOUR printer. Here's a sequence from my "Big Fast Delta":

7:18:36 AMG32
Calibrated 6 factors using 7 points, deviation before 0.134 after 0.009
7:16:54 AMG32
Calibrated 6 factors using 7 points, deviation before 0.165 after 0.058

When the deviation is acceptable to you, issue an M500 to "save" the results.

Part 2:

Machine Control > hit the DROPDOWN next to "Auto Delta Calibration" and select "Run Mesh Grid Compensation"

This will probe a bunch of points and then pop up a grid map. Pay attention to the overall deviation numbers at the bottom. The "spread" should be small, less than 1/2 to 1MM.

0_1526473570126_Bed Mesh.PNG

mindbender9

Hi @Danal

Ok. So here's what I've done so far for calibrating my Kossel Plus:

I've set my the following lines in config.g to:

M558 P4 X0 Y0 Z1 H5 F1000 T5000 I1
M665 R134 L271 B85 H300

Followed Part 1 above:

a. Attached Probe to the Hot-End
b. I heated both the Hot-End to 180C and Bed to 60C
c. Clicked on "Home All" on the main page
After clicking the "Auto-Delta Calibration" button on the main page, the Hot-End (and probe) did the following:

a. The Hot-End and probe smashes into center of the bed. Hard.
b. The Hot-End scrapes along the bed towards the Z motor, rises up to about 3cm and clicked several times
c. The Hot-End remained about 3cm above the bed and moved towards the Y motor and clicked several times
d. The Hot-End remained 3cm above the bed and moved towards the X motor and clicked several times again
e. The Hot-End then centered itself, rose to 18cm and then froze.
Here's the error messages that occured during the Auto-Delta Calibration:

I don't know how you were able to check the "deviation" - What code did you use? AMG32 generated an error indicating that it was an unknown command.
I didn't understand what I'm supposed to do here, so I didn't proceed on to Part 2.
Here's my bed.g file:

; generated by RepRapFirmware Configuration Tool on Sun May 13 2018 19:16:40
M561 ; clear any bed transform
G28 ; home the printer

M401 ; deploy the Z probe

; Probe the bed at 3 peripheral and 0 halfway points, and perform 3-factor auto compensation
; Before running this, you should have set up your Z-probe trigger height to suit your build, in the G31 command in config.g.
G30 P0 X0 Y84.9 H0 Z-99999
G30 P1 X73.53 Y-42.45 H0 Z-99999
G30 P2 X-73.53 Y-42.45 H0 Z-99999
G30 P3 X0 Y0 H0 Z-99999 S3

M402 ; retract the Z probe

G1 X0 Y0 Z150 F15000 ; get the head out of the way of the bed

So to be honest, I'm not understanding what's going on and what's supposed to happen. Any suggestions on what to do now?

Thanks,

dc42

It sounds that your delta calibration is initially a long way out. Temporarily increase the H parameter in the M558 command to 30 and see if that allows you to calibrate without the "Z probe was not triggered" messages.

c310

@dc42 said in Beginner Needs Help - Anycubic Kossel Plus + Duet WiFi -- HOW?:

It sounds that your delta calibration is initially a long way out. Temporarily increase the H parameter in the M558 command to 30 and see if that allows you to calibrate without the "Z probe was not triggered" messages.

i had similar issue. here is a resolution that worked for me

delete config-override.g (or rename it)
home your delta
with a ruler measure nozzle height
put this measure into M665 Hxxxx
run auto-calibration
M500 to store results

mindbender9

@dc42 @c310

I following your instructions and the Z-probe did the same exact steps as before. The same "Error: Z probe was not triggered during probing move" errors appeared (one for each point).

I should note that this is the stock Z-probe that I'm using (it came with the Anycubic Kossel Linear Plus):

~~I did not run M500 to store the results since the probe was clicking while airborne (3cm above the bed). I don't know why this is happening - do you need to see any of my config files?~~

It's not the stock Z-probe that's clicking, because it's dead. The loud clicking is actually coming from either the diagonal arms which are fighting the movement, or the hot-end hardware as it's being moved toward the outer edge of the platform.

Either way, this isn't good. Something is wrong with either the configurations or the hardware. Way to go, Anycubic3d...

I'm stumped.

dc42

@mindbender9 said in Beginner Needs Help - Anycubic Kossel Plus + Duet WiFi -- HOW?:

@dc42 @c310

I following your instructions and the Z-probe did the same exact steps as before. The same "Error: Z probe was not triggered during probing move" errors appeared (one for each point).

I should note that this is the stock Z-probe that I'm using (it came with the Anycubic Kossel Linear Plus):

I did not run M500 to store the results since the probe was clicking while airborne (3cm above the bed). I don't know why this is happening - do you need to see any of my config files?

I'm stumped.

What do you mean by "the probe was clicking while airborne" ? Have you tested the z probe and its configuration? See https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe.

mindbender9

@dc42

It looks like the Z-probe doesn’t respond or stop if I attempt a Dynamic Test from the link above. The repeated contact with the bed at high speeds must’ve damaged it. I’m also looking at the damage to the surface of the bed, and I have to ask: Is this all typical for new Duet board owners?

Moving ahead - Is there a way to calibrate this printer without the use of a Z-probe? And if so, how?

I’m trying to make the most of this, but This is all very discouraging.

dc42

Hads the probe ever worked with the Duet? If not then it's probably a wiring or configuration issue.

You can do manual configuration as long as you are running fairly recent firmware. Set Z probe type 0 (that's P0 in the M558 command in config.g) to tell the firmware that you have no Z probe. Then run G31 as usual. The web interface will prompt you.

Danal

You can also make a probe for a couple of dollars/pounds, if you have access to a printer that works. (Check local libraries and maker organizations).

https://www.thingiverse.com/thing:1976680

And a microswitch, which are available from MANY channels. Here's what I did on an Anycubic that was old enough to have not shipped with a probe (non Duet board... but the switch holder and stuff is still good knowledge).

http://danalspub.com/2017/11/upgrading-an-anycubic-kossel-to-marlin-1-6-6/

mindbender9

@dc42

Hi DC. I'm not sure if the stock probe has ever worked from the beginning with either board, so I've ordered your DC42 IR sensor to continue this setup with. Your video on the IR sensor convinced me to purchase it, but I'm hopeful that its install will be easier.

In the meantime, I'll attempt the manual configuration with Z probe type 0 and see what happens (when I get home).

Question: If I run G31 (after setting the Z probe type to 0), will I have to save any settings or alter the config,g file with any values? If so, where are those values found?

Thank you for your continued help.

mindbender9

@danal

I've decided to upgrade to an IR sensor, but I appreciate your help.

Best regards and many thanks!

P.S. Your BFD delta is something else. Do the mag arms make a difference performance-wise?

Danal

@mindbender9 Yes, the mag arms are a HUGE benefit to almost any delta.

In this picture, which is "side light" to massively highlight flaws, the bottom piece was printed on a stock Anycubic Kossel Linear. The top is the exact same printer, nothing changed except upgraded to Hayden Huntley magnetic-end arms. Literally the same G-Code file, reprinted. Same filament.
alt text

dc42

@mindbender9 said in Beginner Needs Help - Anycubic Kossel Plus + Duet WiFi -- HOW?:

Question: If I run G31 (after setting the Z probe type to 0), will I have to save any settings or alter the config,g file with any values? If so, where are those values found?

I think you mean G32 not G31. See https://duet3d.dozuki.com/Wiki/Calibrating_a_delta_printer#Section_Saving_the_calibration_results.

mindbender9

@dc42

I should be receiving the DC42 IR Sensor on this Monday. Do you have any tips or suggestions for installing/configuring it (on my Anycubic Kossel)?

Thanks!