@Jim46 The flashing light is the DIAG light. It flashes to show the firmware is running. It's perfectly normal. If you remember back to when your Duet wasn't working, this was the LED that was only very dimly lit, indicating the firmware had been deleted! 53.333 steps per mm sounds correct for the belts. But does your Z run on belts too? Most Z axis run on leadscrews, and the steps per mm will be different. If it does run on the same belts, then yes, that should be the same as X and Y. The config tool usually assumes the Z will run on leadscrews, so sets the motor settings for this. You can change them to the same as X and Y if you're running a belt Z axis. If you are running leadscrews, but you don't know what they are or how many steps per mm to set them to, post a picture of the leadscrew with a ruler next to it, and try and measure the diameter. Also take a picture of the opn end of the leadscrew (ie not the one connected to the motor), as this will show how many 'starts' it has. Ian

@Damien if it’s any help I’ve been looking myself at the stepper motors today as I also have an ender 5 pro, the reprap store sells them and lists the current for both types the 42-40 and 42-34 as 1.5 amps I’ve tried the motors at 800ma as the guild says and also at 1200ma (80%) both settings are noisy! But at least you’ve managed to print something I can’t even get my first layer down yet properly yet, still learning just very slowly!

@Phaedrux I am on RRF2. Is it possible to damage all three mosfets at the same time, even though 2 of them weren't connected to any fans and the non PWM fans are working?

@zapta Both. It generates a new acceleration and/or jerk command before each print move.

@oozeBot Nice design. It reminds me of the VORON2 printer, but cool that the z only uses 2 motors. I looked at the post for the Z motor brake. Does the relay always remain powered (even if the printer is off) in order to short the coils?

Rolling back to stand-alone mode was very easy. I've got the same gcode running now, we haven't made it 'the furthest', yet, but it appears to be running smoothly. It's worth noting that transition time between tools seems faster. With the SBC attached, there was a momentary 'pause' between tfreeN.g and tpreN.g. The transitions are now immediate in stand-alone mode. edit: we have made it further than any other attempt. I'll let it keep running as I'm benchmarking 'time per cm with minimal printing' (ie tool-change overhead).

At what layer heights, extrusion widths, and print speeds are you seeing this happen?

(Possibly) New issue with messages. If I execute G32 directly, I get the Leadscrew adjustments made: 0.005 0.040 -0.000, points used 3, (mean, deviation) before (0.014, 0.017) after (0.000, 0.000) message back. If I execute G32 from a macro, I don't. For the good case, I see 2 messages in the DCS log... DuetControlServer[4316]: [debug] Completed G30 P2 X230 Y-222 Z-99999 S3 ; probe near a leadscrew and calibrate 3 motors => Leadscrew adjustments made: 0.005 0.040 -0.000, points used 3, (mean, deviation) before (0.014, 0.017) after (0.000, 0.000) DuetControlServer[4316]: Leadscrew adjustments made: 0.005 0.040 -0.000, points used 3, (mean, deviation) before (0.014, 0.017) after (0.000, 0.000) When run from a macro I only see... DuetControlServer[4316]: [debug] Completed G30 P2 X230 Y-222 Z-99999 S3 ; probe near a leadscrew and calibrate 3 motors => Leadscrew adjustments made: 0.005 0.040 -0.000, points used 3, (mean, deviation) before (0.014, 0.017) after (0.000, 0.000)

@dc42 said in Cannot get in Duet 3 web server after upgrade: Does it just sit there doing nothing, or does it eventually give an error message? It just sits there. No error message

@droftarts My fail.... Ye. That's right, I've also found it after many fails. Anyway, thanks for the reply

This seems like a really good candidate for a bowden setup to remove the motor/extruder mass entirely.

Ok so i did miss understand the concept of deselect tools. Thank you very much for the help and quick reply.

The huge drop shown in the temp graph indicates that the sensor has lost communication with the board entirely. Failing crimp or cable exacerbated by movement and flexing during a print as you've found.

@Phaedrux I have tried it again and though it is creating the resurrect file now it is not resuming, I think my power supply maybe the issue here so I will have to leave this where it is until I can purchase a better power supply for the printer. Plus I am waiting on a new e3d brass hotend nozzel as I think a lot of my stringging issues could be due to the hardened nozzel I have from what I have read elsewhere. Thank you for taking the time and trouble to help me with this.

@dc42 is there an object model variable for the state of the power supply ? Also as i'm totally noob in this type of programmation, can't do anything, as everything i try turns to nothing ^^ i'll just continue as it is and deal with it i think ^^ thanks anyway

Can you post a photo of the hotend? Is there something in direct physical contact with the heat block? Is the fan blowing directly on the block without a silicone sock? Perhaps the Ender 5 Plus is using a different thermistor than other creality hotends and your thermistor values are completely off.

@Kandar said in Error: G1/G2/G3: intermediate position outside machine limits: @droftarts This message also appears when I do "run mesh grid compensation" This happens when the grid you've specified contains areas that the probe cannot physically reach, so it's telling you it's skipped them. Your mesh spacing is 112, but your grid 52-280=228. 228/112=2.03 So change your grid spacing to 114 and it should fit two points into the grid on X. That won't help for Y though. The best way to optimize the grid size is to take your M208 minima and maxima and subtract/add the probe offsets which will give you the areas that the probe can actually reach. Then set the spacing or adjust the grid size so that you can get a nice even number of points in both directions. As for the G1/G2/G3 error, you haven't provided the gcode that is causing the error so it's hard to say what's happening.

@imrj I have been printing Ninjatek Armadillo TPU. E3D Aero extruder 0.4mm nozzle. Base was a PLA profile, tweaked heat settings to suit, 220 / 40. Retraction 50mm/s length 1mm Print speed 55mm/s, infill 45mm/s, walls 27.5mm/s, top/bottom speed 15mm/s HTH Paul

@SpoonUnit NO - Normally Open, NC = Normally Closed. HTH

@imrj Just a couple of suggestions until someone more knowledgable come along. Try add P0 to your M143, so M143 H0 P0 S150. P0 should be the default but just in case.... You could also try adding A0 as well - again that should be the default. Finally, try putting M140 H0 before the M143. I've no idea if any of the above will help - just a hunch base on https://duet3d.dozuki.com/Wiki/Gcode#Section_M143_in_RRF_3_01RC2_and_later