Topics created by Yonkiman

The estimates are already generated and maintained by the firmware. So I am surprised that DWC isn't showing them. Reloading DWC might help.

Hi,

I will do, in the mean time it looks like there some network issues. Some network trace reveals a huge amounts of tcp duplicates.
It takes 45min to upload a 3MB gcode file...
I'm going to investigate this first. I know I already had issues with some old cisco access point, it might be related as well.

@Yonkiman:

I just updated to 1.21RC1, and the reporting issue is fixed as you said.

But I'd like to better understand how you are handling the active low case. If you are using a NC switch (the safe way to do endstops) and want active low behavior, the STOP input would need to have a pull-down enabled, with the switch between the STOP input and 3.3V. When the carriage is not homed, the switch connects STOP to 3.3V, so the input is high. When the carriage homes, the switch opens, and the uC's internal pulldown takes the input to ~0V, so the input would be low.

However when I enable "active low" mode, the input is still pulled up to 3.3V, so there is no way to pull the input low. (Unless you are using a NO switch and tie one end of the switch to ground.)

How is active low supposed to work?

Active low would be used for a NO switch or a Hall effect endstop sensor.

Thanks guys.

Thanks!

You could give the Duet a fixed IP address in the M587 command.

Quite so - and tablets too.

If you connect with a second device, or if you pull the printer status with curl, be sure to go to this url to resolve this problem: http://192.168.0.192/rr_disconnect
I had the same problem, I was pulling the status with curl to display it in my statusbar, and adding a call to http://192.168.0.192/rr_disconnect after getting the json data resolved it.

Thanks everyone. In my mind I'd had it set to 5mm (I must have been thinking cm when I entered it) - was surprised to see 0.5mm in my config, but I still expected it to work (maybe not work WELL) since I didn't see a minimum in the docs.

My other (related) suggestion is an option for a single G30 probe command to probe multiple points and average them..

The new is a well-forgotten old.

+1 for this feature. The same problems with IR sensor forced me to stop using it.

The disconnection from the browser is not expected. Is it repeatable?

@deckingman:

Please don't take this the wrong way but if you are planning a major rebuild, then consider using aluminium tool plate which will give a you flat build surface thus negating the need to compensate for deviations. If you can build it rigid and square and use three lifting screws, you can also negate the need for any form of software level compensation. It doesn't cost much extra to do and it's so nice to be able to simply home the printer, then print something. I just put G28 (home all) in my start gcode as well as any heating commands. So if I want to print something, I turn on the printer, select the file to print then walk away and come back when it's finished. No messing around having to probe the bed.

I agree 100% with this. Build it with a good flat print bed and move on…. My current printer has a flat bed and has no need for bed compensation. I am building a new IDEX version with a flat piece of jig plate that will be indicated flat and parallel to the hotend travels. I will use a switch mounted on the back of my bed as a touch height for setting my hotends Z zero's when ever I change them. This will also allow me to run a regular nozzle along with a volcano nozzle on the U drive during the same print.

From the M207 entry on the Gcode wiki page:

Parameters
Snnn positive length to retract, in mm
Rnnn positive or negative additional length to un-retract, in mm

So it's doing exactly what it is supposed to.