@chiranjeevi said in chamber heating fan - auto on when you set chamber temperature:

i tried the PT100 using the official daughterboard, but its not working well, maybe due to interferences. is there a way to add more thermistors to duet 2 wifi?

If you already have the Pt100 daughterboard that would probably be the easiest solution. Interference may be overcome with improved shielded cabling and 4 wire mode.

@T3P3Tony,

Thanks! this is exactly the answer I was searching for. I will try that out but assume it is working just fine.
Therefore I will close the ticket.👍 😊

@chrishamm SOLVED - Thanks
M400 did the trick.

@Exerqtor that looks about right - although you need to test to make sure.

you can just use the spacing setting, rather than the number of points, in you M557 command, since those values come from the spacings reported in the OM.

Am going to use the laser setup here as a template...

https://github.com/TeamGloomy/LPC-STM32-RRFUserConfigs/tree/master/K40 CO2 Laser - SKR 2 - ESP - paulg4h

Will report back on how I get on.

Assuming the bed heater is heater zero, If you change the M116 line to be:

if heat.heaters[0].current < 60 M116

it will only do the M116 if the current temperature is less than 60.

Note that the M116 needs to be indented by some spaces (I use four), and the next line must not be indented - RRF uses indents to delimit loops, conditional blocks etc.

I'd actually be inclined to make it

if heat.heaters[0].current < heat.heaters[0].standby M116

then it will do the M116 if the current temperature is less than whatever the heater is set to (as standby), so if you change the '60' value in future it will not need changing in multiple places in the file.

@OwenD I call the PID over M703. The code works as I posted it above

@Dennis_kim HF020 Pulse Driver Speed Motion Controller

It's an external board, but it is the best solution to make it act like a spindle, could be controlled with a digital output/heater/fan output. I believe @dc42 said that this was potentially a feature to be added in 3.5, but I think it might not be ready in time (as well as feed hold, which is also useful in places where you have a spindle).

@OwenD Damn, this did the trick. Thank you so much owen! also thanks @chrishamm

@OwenD that is awesome, thankyou! I will wire it up in order to try this and see how it goes... cheers...

@Anawandur

I have now searched through all the files (start.g, start script, filament script, intro line script) and I did not find the word "started" anywhere.

Lost in translation? I hope you didn’t search for "started" but instead looked for the German word "gestartet" … 😁

This aside, can you provide us with a screenshot of the error message?

Then, try to narrow down on the spot where the error occurs. To begin with, insert this line at the end of your start.g macro:

M291 P"Kuckuck" S0

And start your print (sufficient to simulate it with M37). If the error pops up before you see the message, it must be in start.g or any other macro which has been called before that. So, remove the M291 gCode and paste it into another macro of the call chain.

If, however, the error occurs after the message, look at the start section from your slicer.

Admittedly, this is a tedious task, but it's a good way to locate the origin of the error message you get. When you've spotted that macro, post it here.

@mikeabuilder
You can check if the messagebox array is null. If it's not null, then a message box is being displayed.

if state.messageBox!=null M292 ; cancel message box

@chrishamm It works!!

It both updated correctly, and now the M291 functions correctly.
Massive thanks Chris and Tony.

I'll now work on trying to understand how I can use the input to trigger Gcode commands

@jp From RRF 3.5 you can use the D parameter in M81 to power down after a certain number of seconds:

https://docs.duet3d.com/User_manual/Reference/Gcodes#m81-atx-power-off

@T3P3Tony Thanks a lot ! I missed them when I read through the object model I don't know why.

@arkayu I will continue the conversation in this thread as you say - it will require firmware updates:
https://forum.duet3d.com/topic/31842/returning-data-resived-from-i2c-slave-m260-to-calling-macro

@mikeabuilder Yes, I think it is a change from 3.5. The messagebox implementation is different from 3.4 because of the new types that are now supported but TBH I wasn't aware that T was supposed to be ignored before for S=2 and S=3. I'll check the docs again.

@Jos_mosa said in Motor Stop Command:

I guess we can not send other commands while that homing is in progress?

Correct, I believe it would be in a "Busy" state while the homing was in progress.

@Rodrigue-Richalland
You don't need to define a filament sensor
Just use the pin and define a trigger
See here
https://docs.duet3d.com/User_manual/Tuning/Triggers