@Dutchprinting you could use MQTT to send a message from the duet when something happens (using M118) otherwise its a case of polling the duet for data and looking for the change.
NodeRed has a node written for RRF that would be an easy way to get the email functionality

@T3P3Tony

Thanks for the info and the re-location.

Frederick

@droftarts

Thanks for the reply.

I believe I have a way to do what I want.

Frederick

@Zoltan3D In SBC mode you also have sbc.memory.available + sbc.memory.total for the SBC RAM. The macro dc42 posted should work for the SBC storage device as well.

@aceranic Just found other port, it is <single bed control which was on. after off, all is good with Bed temp.
Also 3.5.3 has issues with WiFi, will try 3.5.4.

@Handymanpa54 start a new thread please and add in as much info as possible e.g. config, board. Firmware version

@jedi well get the connection going as detailed there and then send
M122 and M552 and post the outputs here

Hello! Just got back from traveling. (Sorry got delayed for a few days.) I tried updating to 3.5.4 which seems to fix the issue. I'll keep doing some test. Thanks a lot for the help.

@Electriceye Check the start and end gcode, Klipper commands have crept in there, that aren't controlled by the firmware type switch.

Ian

@oliof said in Can&#x60;t connect to Duet Web Control due to dynamic IP address:

consider setting up AP mode on the printer for a direct connection.

In this case it's a 6HC, so no AP mode, but direct wired connection would be ideal.

@droftarts

That's really good to know, as I def want to implement input shaping and it sounds like the LIS2DW and LIS3DH accelerometers are the way to go. What shocks me is how incredibly inexpensive those are compared to the ADXL345, with
higher resolution, less artifacts and lower cost seems counter intuitive. 😉

I'm looking forward to getting this implemented asap, as input shaping seems to be the way to go!

Many thanks to all for the input- much appreciated!

Cheers!

@RodrigoRMaraujo Thanks for reporting this, it will be fixed in the next 3.5 release. Version 3.6 is not affected.

@3DPMicro I have captured this as a feature request:

https://github.com/Duet3D/RepRapFirmware/issues/1069

T3P3 created this issue in Duet3D/RepRapFirmware open Allow any axis to be hidden #1069

@dc42 many thanks for your feedback.
Can you please suggest me some resources to read in order to have more details about this technique!

@dc42 just as suspected 🙂
filament counter is counting correctly anyway.

@Simonjb yes, the reason for this bug appeared after 3.5.4 was released. It’s been fixed, but there hasn’t been a release since. See the last couple of updates here https://github.com/Duet3D/DuetWebControl/activity

Ian