@kivlow Please post your full config.g and the response to M122.

Generally, in order of most likely to least likely, spiky temperature readings are caused by:

intermittent wiring - loose connections, poor crimping, frayed wires, dry solder joints. It may only happen when the wiring moves, or when temperature changes. failing temperature sensor - may only show when at temperature Electrical interference - usually from heater or motor wiring running very close to the temperature sensor wiring. Generally shows when machine is operating Power supply issues - faulty or failing power supply, external power spikes (eg large/noisy dc motor on the same electrical circuit starting/stopping) Hardware issues - faulty Duet board. Firmware bug - least likely because this is heavily tested, and would be reported by other users.

Ian

I have also replicated this issue with firmware version 3.5.4 using Orcaslicer GCODE. I was able to recover operation by toggling off "Exclude Objects"

Oddly, this was working fine for slicing normal STL files but occurred when I was running Orcaslicer's built-in pressure advance calibration tests.

@fotomas I can't see anything wrong with your wiring.
I'm not aware of it being possible to damage when programmed as a probe. We do have a few users who haven't been able to get one working recently though. I've only ever tested a v1 microprobe. I don't have a V2.

@adventureman See the guides on the wiki, on the left side. Work through them to understand how to change the configuration with config.g. Specifically for changing the motor direction, see https://docs.duet3d.com/en/How_to_guides/Commissioning#h-10-check-stepper-motors and see the sub section 'Reversing a stepper motor". But really you want to start at the beginning of this page, and check through everything.

Ian

@Timothee-Leblond There's no one quick way to set it, unfortunately, because it depends on the motors, current, speed and Duet board you're using, so you have to tune it. See this guide https://docs.duet3d.com/en/User_manual/Connecting_hardware/Sensors_stall_detection

Ian

@LindsayC Although weirdly the position error is associated with the 1HCL board driver itself (boards->2->drivers->positionError) and not the axis it's assigned to (Move->axes) as you'd expect.

@CarlosR What Duet board and firmware version are you running? Send M122 and post the response. How is it currently configured?

I haven't set up MQTT myself, so I don't have any experience. Can you look at the documentation here, and see how far that gets you:
https://docs.duet3d.com/User_manual/Reference/Gcodes#m5864-configure-mqtt-client
https://github.com/Duet3D/MQTT-WPA2-Enterprise-Demo

Have a look at some of the forum threads on MQTT too: https://forum.duet3d.com/search?term=Mqtt&in=titles

Ian

@Gianluca @Nuramori I think we've found why this happens: check that 'Single bed control` in DWC Settings > Machine-Specific is not enabled. It's a bug that's being fixed for the next release.

You can tell if this is turned on, as there's a drop down arrow next to 'Bed' in the 'Tools' section. Same for Chambers, if you use that.

Ian

@Ballador @phoenix @Simonjb I think we've found why this happens: check that 'Single bed control` in DWC Settings > Machine-Specific is not enabled. It's a bug that's being fixed for the next release.

You can tell if this is turned on, as there's a drop down arrow next to 'Bed' in the 'Tools' section. Same for Chambers, if you use that.

Ian

@chrishamm said in Web interface showing -273.1 in Active and Standby:

M568 P0 S0 R0

It worked thank you

@dc42 tanks sorry for the noise then 🙂 need to keep up on my reading.

@chimaeragh if you're getting a replacement board I would look at one of the duet 3 products as the duet 2 is end of life

@droftarts
Ian thank you very much!
Problem solved
🤗

@Simon-1 I wired a slider switch into the 5v power line mounted to the side of the PD cases. Super easy if your using serial. Might be harder with the ribbon cable. However, I almost never use the switch the screen saver seems good enough.

@Electriceye try clearing your browser cache

@drivetrainsystems if you are using a Single Board Computer attached to the Duet using SPI then you can read the object model from Duet Software Framework, either in a plugin or via the REST API.

Final tests:

For 3.6.0-beta2(.post3) all relevant data-types (float,int,bool,string) worked as expected.

For 3.5.4 with dsf-python-3.5.0 setting string-data and accessing it via "echo ..." also works.

So issue solved for me - merci!
Thx @all for their support to answer questions and find/solve issues!

@droftarts Thank you very much

@jay_s_uk

Hi, this appears to have fixed the issue, thanks.