Posts made by jay_s_uk

@SpeedyDad because you have a height map applied and it's therefore moving in Z too.
M566 Z12 is way too low, especially for a v2.4. There's no reason it can't be the same as X and Y with it being belted. But if you don't want to go that high, make it at least 60, if not 120

@SpeedyDad post your config. You probably have your jerk set too low on Z

@SonnyD1 why are you configuring them in the tool change files? Why not just have them configured all the time in config.g?

@h4nty update to 3.5.4. There's a new WiFi firmware which should fix what you're seeing

@dogboy I've never setup a scara but there are a couple of pages on the duet docs depending on the type of scara.
https://docs.duet3d.com/User_manual/Machine_configuration/Configuration_SCARA
That's for a serial Scara
https://docs.duet3d.com/User_manual/Machine_configuration/Configuration_five_bar_parallel_scara
And that's for a 5 bar parallel scara

@dogboy I'm assuming the steppers have their own drivers?
In which case the 6XD doesn't care about the microstepping set. All it cares about are the steps per mm

@justGuner

That's why we have this note. I should probably update it anyway to lump 2240s in with 5160s and mention it only applies to stepsticks

And I'll look at updating the driver image

@justGuner it's a limitation of that board I'm afraid as there is no way to set SPI and UART.
You could operate them in "stepdir" mode but being unable to turn off the UART/SPI pins may lead to difficulties.
And as you've pointed out, there no way to set the current or even the microstepping on the driver so you may be out of luck there.
We haven't added TMC2130 drivers as they tend to run hot and don't add anything that 2208/2209 drivers are missing. I'm not sure how easy it would be to add support yourself. Maybe @gloomyandy can comment.

@mrehorstdmd I think this is to do we the number of AJAX tries etc

@kingofthegeeks IIRC it should just be

M950 H3 C"1.out0+out1" T5

Notice the lack of the second 1.

@ketirange dc42 will want the full outputs of the M122's or at least the firmware version information as there are a few interim versions of 3.6 beta 2 floating about.

@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.

@fotomas https://teamgloomy.github.io/fly_e3_pro_v3_bltouch_3_5.html#configg-changes-1
See here for microprobe config changes for RRF. It doesn't use a servo so you don't use an S in M950. You also need to change your deploy and retract macros.
Don't forget to invert the probe for the V2 as well

@Timothee-Leblond I don't see a T0 at the end of your config.
You could also put T0 at the beginning of your start gcode in your slicer

@adventureman duet don't sell on AliExpress so I'm afraid you have a cloned board.

@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

@chimaeragh if its hot enough that you can't keep your finger on it then the MCU is dead

@chimaeragh do any components get hot to the touch?

work through this wiki page here https://docs.duet3d.com/en/User_manual/Troubleshooting/Duet_wont_respond

@Electriceye try clearing your browser cache

@Leeuw123 try adding D3 V40 to each M569 line