Awesome, thanks! 🙂

The WiFi firmware version didn't change with the 1.18 release.

We could produce the table you suggest, but it would contain a lot of "don't know" entries because when we upgrade DWC and RRF at the same time, we don't normally test different combinations of versions together.

For version 1.18.1 onwards you will be able to go to the appropriate Release in the RRF github repo and view or download the complete set of files for that release.

@dc42:

I think spaces should be allowed, but I haven't tested it.

I'm commissioning my printer now (using 1.18) and yes, spaces are working in the WiFi password.

1N4007 will be adequate as a flyback diode for a 7W motor.

yeah lets continue the discussion here:
https://www.duet3d.com/forum/thread.php?id=170

I can see the value in setting based on existing conditions (like increase temp by X) - this is effectively a relative mode for temperature and other settings that we apply this to.

Adding to the M500 settings that are saved would also be useful (but of course adds to the potential confusion, which is why i wanted to just edit the config.g always)

We are continuing to more closer to a general language for programming using gcodes….a friend of mine compared it to the development of shader languages in GPUs into general purpose programming languages.

Already on the firmware wish list. We included two power monitors in the Duet WiFi/Duet Ethernet hardware to make this easier to implement.

@dc42:

I guess I should allow you to provide min and max temperatures, and either smooth PWM between them or or on/off at them.

I'd say that would cover all eventualities for all users. As I said, it's not a huge issue - just a "would be nice to have" at some time in the future.

@kraegar:

Perhaps my bowden was too short, but then if I made it longer the extruders just kind of balanced on the bowden. But with how I had them, it changed the tilt of my effector. I can re-test now that I have a digital method to measure. Before I noticed it by using the mini IR probe, and checking the trigger height offset at various points. I noticed the trigger heights changed if I totally disconnected the flying extruder vs. having it on my printer. (it also changed the measurements from the seemecnc accelerometer probe some, too)

to deal with tilt i just place my nozzle at the correct height where any tilt in any direction dose not deflect the nozzle tip… ( this means mechanically moving the hotend to the right height )

~Russ

Sounds like a very good target feature list for 1.19.

Bit more testing and it does appear that in all cases there is an initial Y motion before the arc starts.

I've put a pull request in with chris: https://github.com/chrishamm/DuetWebControl/pull/33/commits/eb2a220471c4c520314c29534fe00d53d217a782

iDeveloUK opened this pull request in chrishamm/DuetWebControl closed Piecon Integration #33

Thanks for that report.

There is a longer term aspiration to more tightly integrate the functionality embodies in the configuration tool that Jackal linked with DuetWebControl. There is other work higher up the priority list right now though.

@Flyer007:

Might be better to just offer triggers to another board. Which is then tasked with the LED control. Addressable LEDs can use a lot of resources.

I would like this since I run a Pi3 with camera on it to serve the Duet Wifi, video. I am also setting it up for the LEDs, enclosure heater and filament dryer controls.

i think this is the ideal solution