Posts made by jay_s_uk

@Tech_Sam03 I don't think DWC works at all well on 5 or 7 inch screens. If you can hold off I would wait longer...

@Tech_Sam03 it looks the same as a mobile phone

@3DPMicro the settings page in DWC

@3DPMicro try clearing the browser cache first. Then if that doesn't work, look at the settings page and post here the software versions it reports

@JayT best off getting an accelerometer and measuring it properly.
And ZVD is not the most aggressive input shaper, see the data evaluation info here about the different shapers https://docs.duet3d.com/en/User_manual/Tuning/Input_shaping_plugin#data-evaluation
maybe try ei2 or ei3

@JayT yes, ringing is common. It happens more in Y on coreXY as you're moving the whole of x axis about

@JayT i don't think this will be something you can tune out by adjusting acceleration etc.
Input shaping is the way to go to reduce this

@JayT I would suggest running 3.6-RC3. Motion and input shaping has been rewritten in 3.6 and its much better than in 3.5

@JayT what firmware version are you running?

@awitc just check the firmware version installed once booted. You'll probably have to run M997

@mrjoneskod AFAIK, klipper doesn't currently support getting sensorless homing status over SPI like RRF does. In which case, that'll all need implementing into klipper

@DuetCDH the 1.02 6XD isn't fully supported until 3.5.3 so best update

@crpalmer said in 3.6.0-rc.2+2: more probing problems (G30 P0 K1 moves wrong tool):

This G30 command moves tool #0 to (150, 50) then probes Z to but appears to be reading the value of probe #1

That G30 has a K1 in it which means probe #1 so why wouldn't it be reading that?

@shirnschall the kraken motors have thermistors embedded in them so I doubt there's any issues. The ones they use are nothing special

@Macgyver there's no endif in RRF.
You just have to have the code indented correctly. No indent means the if has finished

I am please to announce the Mellow Airclick buttons https://s.click.aliexpress.com/e/_oFdvJAp
Although these buttons have been out for a while, they now have RRF support.

You can use them to send specific gcodes or call macros etc.
There is also no limit on the number of buttons that can be added.
Communication between the Airclick and RRF is via WiFi. The buttons use 433MHz.
I have documented their use here https://teamgloomy.github.io/airclick_general.html

@arturolaz there is this as well about the Roto itself

@CrazyCreator the V2 is inverted so your second config is correct

@droftarts Looking forward to seeing pictures of you with your robot arm fitted...

@CrazyCreator yes, if it's not connected it'll read like that. It'll also read like that if it's not calibrated