@dc42:

Your Z probe trigger height is very low. When the nozzle is touching the bed, what is the separation between the bed and the bottom edge of the IR sensor board? It should be between 1 and 2mm.

How thick is the glass?

The glass is 3mm and the separation between the bed and the bottom edge of the sensor is between 2.5 and 3mm.
I am planning to move the sensor as I am unhappy with the offset, I have set it at 1mm in my future new setup.

Antoine

Ordinary fans are not designed to work with PWM and it's a wonder that so many of them do. It sounds as though the fans you have purchased do not like PWM at all. You can change the PWM frequency using the F parameter in the M106 command, but I doubt it will help.

I use 24V 40mm fans from this supplier http://www.ebay.co.uk/itm/3D-Printer-24v-Cooling-Fan-25mm-30mm-40mm-50mm-60mm-Extruder-Fan-RepRap-/191458206299.

I have circumvented this security issue, I have added a password to the softAP function here: [https://github.com/chrishamm/DuetWiFiServer/blob/master/src/RepRapWiFi.cpp#L193(](https://github.com/chrishamm/DuetWiFiServer/blob/master/src/RepRapWiFi.cpp#L193()

for reference, I had to upgrade my aironet 1130 ap to a 1140 one. the esp8266 wasn't working with the old cisco ap.

No, you need to add it as a start-up command in whichever slicer you are using.

a) Do not over-engineer the solution.

b) consider your audience's skill level.

c) also very important, wallet size, both of these last are frankly limited.

d) Do not make the design mistakes others have made, and learned from "stand on the shoulders of giants"

For the extrusion speeds only the 2 slowest will feed without the stepper missing, so I really just want to remove them to make the web ui more usable for the rest of the family, but its no biggee.

Yes, speak to your supplier.

Looking at your config.g file I see that you have only one extruder drive configured on tool 0 yet you have mixing enabled. Try it without enabling mixing.

If you suspect a problem with the E0 motor driver, you could move the motor to E1 (with power off of course) and adjust your M563 command accordingly.

Now that i am a big piece forward I am facing a little problem. The two boards are quite large and the way the connectors are done it is impossible to put it in the base of a kossel (except when I give up height and make a much deeper base). The only options I see are either an external box with boards backt to back and push-pull fans in between. Or place them flat (next to each other) in the top of the printer.
For the latter I would need a shorter ribbon cable though.

Thanks, that makes sense.

I'm not able to change the password on this router, but in the meantime, I've set up another access point with an all numeric password. The duet is able to connect just fine in this case, so it's time to get on with the build…

@dc42:

I'll take a look at the code tomorrow. I did wonder whether it wasn't doing URI decoding, and if that's the case then i think the + character would be a problem too.

@DjDemonD:

So when changing something which effects z probe offset, try a variety of values using G31 and then when you've got the right offset save it with m500?

Yes.

Try the "Using external drivers" page on the wiki.

https://duet3d.com/wiki/Setting_up_automatic_probing_of_the_print_bed

Got it on the M552.

@dintid, I have quite a few Duet WiFi equipped printers here and use Chrome. I've not had connection issues at all in over a year (I worked with Chris H to capture network traffic to help him improve the network code about this time last year). This particular issue was odd and maybe just a fluke. Not had a problem since.

If your printer's X, Y and Z axes are not exactly at right angles, you can use that feature to compensate for it. Most people don't use it.

We have found the GT2 belts that are commonly used (including by us) on deltas from small to ~1.2m large work well. They are fibreglass core AFAIK and have no appreciable stretch. The bend radius has no issues in 20T pulleys that we use.

What I don't know is how well they scale to larger printers where stretch may be more pronounced.

See https://duet3d.com/wiki/Connecting_a_Z_probe.

Yet another two examples. I just created g-code with 50 millisecond segments (F1200, 1mm movements), so pauses (or step signals with shorter interval) going exactly every 50 ms, easy to find in analyzer logs:

All three motors paused at 7.420+ s position
Pause for X step, premature step for Y and Z at 7.520+ s position

Pause for X and Y, premature step for Z at 7.670+ s position, also steps are skewed at 7.770+ s position