@OwenD
Thanks for you quick reply. I will try.

@SonnyD1 here and there google advance search try it 🙂

@bubbar0b0t most SSRs will work with between 3V and 30V on the control terminals. If your does, then you should connect the positive control terminal f the SSR to the +ve OUT0 terminal and the negative SSR control terminals to the OUT0_NEG terminal - in other words, connect the SSR control terminals to the OUT0 terminals. Do not connect either SSR terminal directly to ground.

Thanks a lot guys, you were right (of course)

Sensor is now working like a charme 🙂
not sure how to set the topic as solved...

@misterjtc thanks for confirming that!

@Phaedrux many thanks all, I was able to get this up and running by following the guidance provided here. Cheers!

@djstree It's probably better to create a new thread where you describe your problem. I assume you've already checked out automatic heater tuning.

@Phaedrux perfect thanks. I was thinking putting something in daemon.g but figured there might be some built in function. Ill use M143 since I just want a shutdown if over temp.

@Michael-Hathaway it's interesting that the resets were previously reported as reset button but they are now reported as software reset. This supports the theory that the original resets were triggered by static discharge.

I recommend that you upgrade to firmware 3.4.5. There is a known issue in earlier 3.4 versions whereby a repeated event such as a motor stall can cause an "Out of memory" software reset.

@CCS86 2-wire fans are not designed to work with PWM. It's a minor miracle that so many of them do.

@achrn I'm glad you solved it.

RRF works to the Intel PWM fan specification at https://www.intel.com/content/dam/support/us/en/documents/intel-nuc/intel-4wire-pwm-fans-specs.pdf. According to section 2.1.4 the PWM input should he pulled up to 3.3V or 5V inside the fan. It appears that your fan either doesn't have a pullup or it has a very weak one.

@Atom-0 said in Accelerometer Error:

Board: Duet 3 MB6HC
DSF Version: 3.3.0
Firmware: RepRapFirmware for duet 3 MB6HC 3.3 (2021-06-15

I suggest you run sudo apt update and sudo apt upgrade on the pi terminal to update your firmwares to 3.4.5. Then ensure you have the latest input shaping plugin installed and try again.

https://docs.duet3d.com/User_manual/Tuning/Input_shaping_plugin

Well I was suggesting that you place the switch such that if the bltouch fails and the z axis continues to move the switch would trigger before the nozzle hits the bed.

@Phaedrux dont know what m552 s-1 does but ive dont plenty of toggling on and off with s0 and s1 and m587 ive done and redone after updating it with m997 s1

@J-Helps if a potential collision is detected then the print is aborted.

@Phaedrux thanks, i just placed my 3HC order. wasnt quite sure if that was the optimal model to go with, but it seems like it is. and will get significant expansion.

@Borgtribble It depends where you start in the upgrade path. If you're already on 3.x it's a lot more straightforward. The order I've given just ensures you have all the files needed in case you want to go back and forth between versions at some point. I include 3.3 because the firmware folder was added in that release.

@MintyTrebor thanks. It's strange that I don't see any malformed packets on either of my machines, and the ones you see don't appear to be triggered by a packet received by the Duet.

@Nordle said in Optical Endstops:

wouldn't it work to just run the sensor from any spare 5V pin on the baord?

Yes, I said that in my reply at https://forum.duet3d.com/post/305741.

@Nordle Yes, you can solder the pullup resistors to the pins on the back of connectors.

The electrons don't know where you added the pullups, just that they are there.