Item P isn't specifically about connecting to hidden networks, but should cover that.

The post is here
https://www.duet3d.com/forum/thread.php?id=8

I will move this to the firmware wishlist section

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.

And if you don't turn off heaters in the cancel.g file, but you do have a cancel.g file (with g28, for eg) the heaters don't turn off. I like this feature very much, as I manually set Z height and so having the heaters remain on saves time when restarting a print to adjust z height.

OK, point taken.

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.

I believe Pronterface has this feature. I'm not sure exactly how it works, but you could hand the firmware a list of X/Y rectangles, and perhaps it could then ignore all moves with an end coordinate within any of the rectangles. I don't know that it's worth implementing, but then I have a flaky printer with a small bed.

@dc42:

Yes we could add Telnet support and I will if there is enough demand (unless someone else does it first). However, Telnet is a very insecure protocol, not at all the sort of thing that I want running on my network, let alone on a WiFi connected device. One of the high priorities on my list is to improve the http security.

Just to add to the demand, I registered to say I'd love to have telnet. 😉 My primary intention is actually to syslog interesting responses.

The issue with http is that (at least in my current version on duet 0.8.5) sometimes I can't get g-code response reliably — I believe other browsers are eating it up, though never bothered to figure it out.

Of course I can also get all that over USB, but if I have telnet I can free up the raspberry that is connected to printers. (not sure what for, though).

And yes, geekiness also makes one feel comfortable having telnet 🙂

We're in 32-bit land, though, does it make sense to allow multiple sets of PID parameters for multiple target temperatures? One per ten Celsius degrees, perhaps, or a maximum of five and it picks the closest? I don't know how short of EEPROM and code space the Duet is.

You can do the same thing with G10 P0 Z### to set up a Z offset, and G10 P0 to show the current offset. However, any change you make won't take effect until all moves alrready in the queue have been completed.

Amazing! One more reason everyone should upgrade to a duet.

@T3P3Tony:

Another option would be to add software PWM to any unused GPIO pin that can currently be used by M42 depending on the PWM frequency wanted this could add too much overhead though.

The overhead would be high unless the PWM resolution were limited to 1ms or the timing were done in the step ISR, which I would rather avoid because of the impact on maximum step generation speed.

Regarding deciding if a heater output is used or not, rather than a new M code, why not just allow all heaters that are not added to a tool to be used as PWM?

For safety reasons I would rather the user made a definite statement that there is no heater attached to the pin. But perhaps we don't need a new M code, we could add an option to M305 instead.

I second this demand, as for miscellaneous reasons, I have done the calibration many, many times.
What I have done yet to help is making a macro for each sensing point. This macro go to the given point 0.5mm above 0, so P0 go to point 0 X, Y , Z=0.5, P1 go to P1 point X,Y, Z= 0.5, etc. This help a lot compared to the manual move to each point.