Topics created by awitc

@droftarts Great! Exactly what I was looking for, must have overlooked the note. Thanks!

@awitc yes the printing file will continue to execute in parallel with the trigger macro. However, no new triggers except emergency stop will be activated until that trigger macro has completed, because a single GCode channel handles all triggers.

The addition of "^" helped to bring the voltages to 0.7V and 3.3V respectively. I thought the pullup on the input is enabled by default. Thanks a lot!

I found also that testing the trigger with a M117 message makes the message show up only the first time the trigger is evoked. At least in my case.

@awitc Almost certainly this is the wiring picking up interference, poor connections on the thermocouples, or they are grounding on the heater block. See https://docs.duet3d.com/en/User_manual/Connecting_hardware/Temperature_connecting_thermocouples#wiring-the-thermocouple

Thermocouples are susceptible to inductive interference, so can pick up signals from other wires, eg heaters using PWM, or motor wires. If possible route the thermocouple wires away from these wires, especially if you are getting interference when the heater or stepper motors are on. If not, look at the wires, check they are not grounding on metal work, and all connections are good. Ideally use shielded twisted pair wiring for thermocouples.

See @dc42 's advice in these threads https://forum.duet3d.com/post/318950 and https://forum.duet3d.com/post/270256 and have a search of the forum for other similar thermocouple issues. I'll add some of this to the documentation.

If you have a very old version of the thermocouple board (pre 2018), check if it is using MAX31855 chips. These were more affected by interference, although it is possible to add capacitors to mitigate this; see https://forum.duet3d.com/post/20525 for a hint on how to do this, though the original post was on the old forum, so is lost to the mists of time...

Ian

@awitc RRF doesn't need to know what microstepping is in use, it just needs the steps/mm setting for that axis or motor. The M350 command was introduced to allow RRF to select the microstepping to use when using drivers that allow it to be controlled.

I guess we could improve the error message, because what it really means in this case is that RRF is unable to select x32 microstepping on your driver, because it has no control over the driver microstepping.

I might have tracked the issue down, asked a question with more information here. If my daemon.g was the culprit, sorry for the waste of time.

@awitc not specifically. A custom panel can display almost anything from the object model, so if it exists in there then you should be able to show it. You can use the object model plugin to browse the object model.

@awitc assuming you purchased that thermocouple board from a genuine Duet3D reseller, please start a warranty claim by emailing warranty@duet3d.com. Include a link to this thread in your email and cc your supplier.

@droftarts I used the red/white, blue/white, brown/white, and green/white. I didn't ground the shield.

Thank you for your replies @jay_s_uk and @dc42. Both suggestions seem to be valid solutions. I will firstly look more into the daemon.g file, as it is more customizable and fitting for my purpose.