Topics created by taylo708

@taylo708
I was assuming you were not getting the humidity readings from the sensor.
If you have the sensor set up to display the humidity then you can use daemon.g to control the heater.
I'd imaging you'd need to set up several global variables in config.g including one to ensure you can turn the heater on/off

global ChamberHeaterOn = false global lowHumidity = 25 global midHumidity = 50 global highHumidity = 75

Then in daemon.g use something like this (change the sensor value)

if global.ChamberHeaterOn = false M140 S-273.1 ; switch off heater elif sensors.analog[2].lastReading <= global lowHumidity M140 S40 elif sensors.analog[2].lastReading <= global midHumidity M140 S60 elif sensors.analog[2].lastReading <= global highHumidity M140 S80 else ; whatever you want to do if over the high value

And set up a couple of buttons to set the global to true or false to offer manual control when needed

Hey @dvmourik, i put your config on my machine, but couldn't reproduce the problem. unfortunately.

Would RRF-3.2.x or RRF-3.3 and PD-1.24 work as a workaround for you?

Slowly i start to believe it might be related to the wiring.

Can you test the following:

disconnect duet3 from network (just to be sure it's nothing on the network keeping duet3 very busy) enter M115 in the paneldue console and post reply start the duet3 and paneldue your cable (check if error continues to occur) start the duet3 and paneldue with short cable (check if error continues to occur)

@mrehorstdmd Yes they sent me the motors I linked as a replacement for the original steppers. I had been pushing them to go closed loop for a year or so. They reached out and told me they had closed loop replacements for me that would plug and play.