I am sorry that I also do not understand this. I, too, am coming from smoothie. In the past, I would do a g32 with a microswitch. It would check for bed level at some unknown height above the bed. Then I would remove the microswitch, lower the nozzle til just touching the paper, G92 Z0 and M500. boom.

With this, I have been trying for over an hour. I did the autocalibration with the microswitch on. And then I removed the microswitch. Z0 results in the nozzle sitting 18.64mm above the bed.

I tried to follow this:
https://www.duet3d.com/wiki/Calibrating_a_delta_printer

I use M208 S1 Z-20 to allow the nozzle to move down.
I use G Z-18.64 to lower nozzle to piece of paper (that works)

then I have tried changing this in the config:
G31 P600 X11 Y0 Z0 ; Set Z probe trigger value, offset and trigger height
to
G31 P600 X11 Y0 Z18.64 ; Set Z probe trigger value, offset and trigger height

but still when Z0 the nozzle is at 18.64mm above bed.

I've deleted the last few lines from the config-override and then lowered nozzle to bed, used g92 Z0 then M500, reopened config-override:
G31 T1 P500 X0.0 Y0.0 Z0.70
G31 T3 P500 X0.0 Y0.0 Z0.70
G31 T4 P600 X11.0 Y0.0 Z18.64

How do I convince my machine that it needs to be 18.64mm lower?

I decided to go into config-override and I changed this line:
M665 L304.170 R151.502 H241.959 B125.0 X0.025 Y0.027 Z0.000 ;
to
M665 L304.170 R151.502 H260.599 B125.0 X0.025 Y0.027 Z0.000 ;new-H260.599 old-H241.959

basically, I told the machine that it was 18.64mm taller than it calibrated at. That seems to work. but what is the correct way?

Wow - awesome support. Thank you!

Thank you for all your help. Now that my fan is mapped, the M106 commands work. I'll see if my cura is generating M106 S0 or M107.. but if M107 then it is an easy edit.

Thank you again.

Steve

OK, I am chipping away at this. I plugged a fan into Fan1. I entered M106 P1 S100. Fan went on. This is GREAT. I entered M107. Fan stayed on. I entered M107 P1. Fan stayed on. I entered M106 P1 S0 and fan went off. So, control is good.

I believe I need to now map the fan, something like this:
M563 P0 D0 H1 F1 ; Define tool 0

Now M106 S### works for on and M106 S0 works for off. But M107 doesn't turn off fan. Any ideas?

Inserted a homemade jumper into I_5V_EN. Now the Wifi is working. Duet is no longer connected to Windows 7 via usb. Now I can access 192.168.1.101 via Mac and Windows and Android. Thank you

Also, I tested a single fan on an always on and it works. So, I'll go with the assumption I only fried just Fan0.

For now, I just need to learn how to switch on fan1 via gcode

Thank you

Thank you for the ideas. I needed to run to my son's basketball game. Now I've got time to work on this. I did buy an actual Duet Wifi from SeeMeCNC. Oddly, it was shy a jumper on the Z. So I stole a jumper from the I_5V_EN (which I wrongly assumed would give power to the always on fan) . I powered the always on fan directly from the power supply.

I will now make a jumper from a defunct fan by twisting the wires together to enable internal 5volts. Will let you know how I get on.

Thank you again

dc42, Thank you for taking the time to reply. I really appreciate it.

To directly respond to your questions:
"Please explain the apparent contradiction between "I doesn't seem to show up on wifi" and "On the Windows 7 machine, I can open an explorer and see the web interface". If you can see the web interface, it must be attaching to your WiFi network."
-My windows 7 machine is not set up for wifi, it is connected to internet via ethernet cable attached to a wired and wireless router. My other machines are connected to same network wirelessly. So, I can connect the duet to my win 7 machine via USB. I can use pronterface to control machine via usb and issue M552 commands. I can issue M552 S1 to get an IP address. I can enter that IP address in an explorer on windows 7 machine and see the web interface. However, if I enter that same IP address using my Mac, chromebook, android phone, android tablet, they can't see the web interface. Also, when I unplug the usb cable from the Windows 7 machine, I then lose the connection to the Duet. So, it doesn't seem to be connecting via Wifi, it appears to be connecting only via usb.

"Please check your wiring. I suspect you had the + and - fan wires swapped, or else a short in your fan wiring. Driving 3 normal brushless fans from one fan output is OK. Putting the jumper to connect VFAN to VIN is the correct way to select 12V fan power, assuming you are using 12V VIN."
-Ok, good to know that I had the jumpers correct. I've tried a single fan and still no love on fan0. I assume from the drawing that V_fan is positive and Fan0- is negative. Later, I'll test the subsequent fans to see if they are switching on with M106 or if I have blown the fan "area" .

regarding the bed thermistor… I was being a moron. After the fan blew, I wasn't thinking clearly. I solved it

Thank you

Steve

New to Duet Wifi - Apparently I need lots of help

I got my Duet Wifi yesterday. Today, I removed an MKS sbase "smoothie" from my delta - all the components were working, but the motion got unpredictable at higher speeds. I have got some things working and not others.

Not working:
WiFi - I've got the Duet Wifi connected via USB to my Win 7 machine. I've found it as Duet on COM9. I've connected to it via Pronterface and issued M552 S1. From there it just seems to hang. I wait 30 seconds, then 30 more… I doesn't seem to show up on wifi. On the Windows 7 machine, I can open an explorer and see the web interface. Should the blue light on the wifi come on and stay on? It comes on when connecting to pc via usb for a moment, but then goes off. Is there a definitive "light chart" in regards to every LED and status?

Fans - my always on fan works fine directly connected to 12v power supply. However, I think I have already fried my PWM Fan0 connection. On previous board, I had 3 12volt cooling fans connected to the "fan" connection. It worked. On the duet, I connected all three fans to Fan0. I think I misunderstood the use of the jumper...as I had placed it to bridge V-fan and Vin. When I issued a M106 S50, I let the magic smoke out of that part of the board. I would really appreciate strategies for testing Fan0 (and remaining Fan1 and 2) and correctly setting the jumper for 12v. My power supply is 12v 5A, so I had assumed that Vin was 12v

Bed Thermistor - my bed is heated with mains via SSR and the bed thermistor is in the correct location next to the bed connection. When I try to heat the bed, the SSR switches on and bed starts to warm, but the thermistor continues to read the ambient room temp. So, I end up switching the bed back off. I'll continue to read about how to configure for this thermistor, which says RRRF100K in my old smoothie config.

It homes correctly and seems to move correctly. Hotend heats correctly and extruder seems to work. But, I could use some ideas to get the rest of it working.

Thanks

Steve