Yes it can be used with the Duet wifi, you hook it up the same as you would to any other control board

I just updated the firmware to 1.18RC2 and the issue is fixed. Thank you so much for the help!

I think the diagram in the previous post is how they are suggesting you connect the probe to other equipment, not what is inside it.

I suggest you connect the brown and blue wires to the always-on fan connector, and the black wire through a small signal Schottky diode to the endstop STP pin, cathode to the black wire.

Thanks for all the info! I truly appreciate the help I'll check out the options and see which one is more will fit me better thank you.

Thanks for the help! Okay, sounds like trial and error it is. I asked as there is a section in the Wiki that has not been filled in about tuning stuff.

I have discovered one thing that I should have been obvious. You cannot use DWC to move the motors to see if there's any change in speed unless you change the move speed in Settings-User Interface-Machine. The default speed is limited to 100mm/sec.

Your config.g file should have a M501 command near the end, which causes config-override.g to be run. So the values in config-override.g override earlier settings in config.g.

I use both a phone/tablet and a PanelDue. I find the web interface on the tablet completely usable on the 7 inch screen (so a 10 inch will be better).

I do find the PanelDue a bit quicker to access key functions but that's at least partly because it's tethered/mounted on the printer so i don't have e to locate it in my office.

We're planning a modest increase in the very near future, and a greater increase in firmware 1.19. For Nema 23 motors, 2.3A rated current is a good choice, and is what I am testing with.

yes, but the interface speed seems odd (see output below).
If I remove the card and run M122 again, it says 'SD card 0 not detected, interface speed: 0.2MBytes/sec'.
If I start the Duet without card and run M122, I get 'SD card 0 not detected, interface speed: 30.0MBytes/sec'.

Diagnostics Used output buffers: 1 of 32 (2 max) Platform Diagnostics: Memory usage: Program static ram used: 13132 Dynamic ram used: 81780 Recycled dynamic ram: 3392 Current stack ram used: 2752 Maximum stack ram used: 3584 Never used ram: 29184 Last reset 00:00:14 ago, cause: power up Error status: 0 Bed probe heights: 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 Free file entries: 10 SD card 0 detected, interface speed: 0.2MBytes/sec SD card longest block write time: 0.0ms MCU temperature: min 24.5, current 26.6, max 27.6 Supply voltage: min 0.4, current 0.6, max 0.9, under voltage events: 0, over voltage events: 0 Slowest main loop (seconds): 0.000512; fastest: 0.000042 Move Diagnostics: MaxReps: 0, StepErrors: 0\. Underruns: 0 Heat Diagnostics: Bed heater = 0, chamber heater = -1 GCodes Diagnostics: Move available? no Stack pointer: 0 of 5 macro is idle http is idle telnet is idle serial is ready with "M122" aux is idle file is idle Network Diagnostics: WiFiServer is disabled SPI underruns 0, overruns 0 Webserver Diagnostics: HTTP sessions: 0 of 8 ok

What is your printer? Try putting in nothing more than G28 in your start script. You will then have to set the temperatures from the web interface. Note that when you change the process the profile will change to "modified" and in order to save it you must click update profile or save as new. My start script is specific to my machine/process. Also you can write gcode commands for moving, priming, and wiping the nozzle as well as setting the center of the build plate. Look at what G92 does.

hi all thanks for the help (dc42)
ok problems

memory card stopped working ( replaced card sorted )
extruder getting hot and over extruding and under extruding and completely failing after 3 hours

turned out i had my blue wire ad snapped inside the sheaf …....while cheeking and rerunning all the wire it fell in half in my hand strange

its now 4 hours into a 6 hour print and back to normal
p.s i got an extra motor in the post now

ok thanks dc42
the forum is a great tool for everyone

+1 for postimage

Here's another idea. Configure a chamber temperature heater as normal using M141. Also configure a spare fan channel as a thermostatic fan controlled by the chamber temperature, set to turn on at a temperature a little higher than you have the chamber temperature set in normal use.

That's correct.

Panel Due 4.3 connected and reporting temps…that was easy following your directions here:
https://miscsolutions.wordpress.com/paneldue/

Again, thank you, thank you!

There is already a password, you just need to configure it in config.g.

I just cut off the connector and crimped a new one on and the readings are solid when pulling on the wires. Wouldn't you know, it was the only one I didn't change when I went from Smoothie to Duet.

Firmware Name: RepRapFirmware for Duet WiFi
Firmware Electronics: Duet WiFi 1.0
Firmware Version: 1.17e (2017-02-10)
WiFi Server Version: 1.03 (ch fork)
Web Interface Version: 1.14a

Thanks, that was the problem. I'm frustrated that I missed that. Argh I should have known that.
Thanks again dc42

@dc42:

Torque is not affected by microstepping. The confusion arises because various sites publish incremental torque per microstep - which of course does go down as microstepping increases, because the change in movement angle per microstep goes down.

You can select which motors to use interpolation on if you wish, just use two separate M350 commands. But if you use x16 microstepping then I am not aware of any situation in which it is better to turn interpolation off.

Good to know, interpolation it is!