Topics created by peridot

@peridot:

Unfortunately even with the computed H values I still don't get good pre-fit deviations out of the autoprobe (and the post-fit deviations are not always great either).

That's to be expected to some extent. If you need to use H values to correct for effector tilt, then you have a geometrical error that the model used by the printer (including the auto calibration code) does not account for.

If you can't track down the geometrical error that cause effector tilt. then in the very near future you will be able to use grid-based bed compensation to compensate for the residual height errors.

Thanks! I'll take a look once I'm not tinkering with anything else.

http://reprap.org/wiki/RepRap_Firmware_macros#System_macros

Ah, I see the problem - I was misreading my data sheet by a factor of ten. So the numbers made it look like there was a huge advantage to using two high temperatures; turns out it helps a little bit and only throws the room-temperature reading off by a few degrees.

Well you certainly couldn't miss it though LOL

I haven't tried to see the debug output from USB, but it would be nice to have an easy access to a more detailed autoprobing information.

Added mine to Thingiverse as well http://www.thingiverse.com/thing:1830918. It has an enclosed 80mm fan to blow on the underside of the board, exhausting through slots top and bottom. Cable entry is left side but I've included the open scad file so it'd be easy enough to change.

I agree with this before, but i watched closely the dice project from Rene Jurack where he tested lot of setup to finish with high value. I made my tests in this way.
For the extruder high value i cannot explain clearly why they gave me better result…

Yes, that's right. CoreNG is also the hardware abstraction !ayer for iap4e.bin.

Great, thanks dc42.

There was already some text and schematics for Duet fan connection here :
http://otocoup.com/aql/#hlp:allb/fans

HTTP Digest is supported by browsers already, though. I guess your idea is to use a web form and set a cookie rather than HTTP Digest's direct inclusion in the headers? Both are somewhat vulnerable to spoofing, unless the Digest approach does something with one-off nonces. I suppose people are more used to typing passwords into web forms than having the browser pop up an authentication dialog.

Just to make sure I understand: although there are HTTP, FTP, and telnet servers in RepRapFirmware, the Duet WiFi runs all its network services on the ESP8266, right? I see there is an HTTP server there. Presumably it communicates with the Duet CPU via SPI, via G-codes and file transfers.

@peridot:

For some reason the firmware decided my hot end wasn't heating fast enough, declared a fault, and shut down the hot end heater. But nothing else stopped: the head kept moving and the print started - with a stone-cold hot end. Trying to shove filament through a cold hot end is bad for the printer. This is not a good response to thermal misbehaviour.

It's already on the firmware change list to stop the print when a heater fault is detected. Meanwhile, cold extrusion prevention will kick in when the temperature has dropped at enough, at 170C AFAIR.

If the name you entered during WiFi setup is coral, then coral.local is how you address it via mdns. The name defined in config.g is not currently used for network accessing.

Thanks!!

Please switch to 1.19beta1 and try again. See https://www.duet3d.com/forum/thread.php?id=1620 for upgrade instructions.

Done:

https://github.com/T3P3/Duet/blob/master/DuetWifiv1.0/DuetWifi_Schematic.pdf

For KiCAD you need to use at least version 4.0.2. The custom parts are in the distribution on Github, you might need to point your libraries path at that, I thought it was relative within the project but maybe its not.

edit: added a page to the wiki that links to the source files:
https://duet3d.com/wiki/Source_Files