@dc42 said in hierarchy of control over gcodes, machine vs filament vs slicer:

The printer speed and acceleration limits should always be set no higher than the printer can reliably achieve. Otherwise you may end up with the slicer commanding the printer to move faster than it can manage, especially if you use the speed factor control in DWC or PanelDue to increase speed. You can of course set lower speeds and accelerations in the slicer settings.

That's something I have wondered in the past. If the slicer says to move at 100mm/s, and RRF has the speed limit set to 150mm/s, I would expect the printer to move at 100mm/s. If the speed factor control is then set to 200% in DWC, what happens? How fast does RRF drive the printer? 150 or 200mm/s?

I mention speeds, but presumably this applies to accelerations just the same?

I did look in the DWC manual for the speed factor control but it wasn't clear to me what limits were still imposed, if any.

This also had me wondering the other day as I was adjusting pressure advance as well as input shaping. In particular if pressure advance could result in extruder feed rates outside the limits that I had specified in RRF, and if some sort of clipping might occur if hard limits were enforced resulting in some obscure printing artefact. Same with input shaping and how the actual moves sent to move the head might look after going through a 'shaper filter' and whether they too were being 'clipped'. ... I have a background in audio design where clipping is just about the worst thing imaginable for a poor audiophile. 🙂

Now that I'm running two linear delta machines, where the amount the effector moves is not nicely related to the rotation of a single stepper but some combination of all three depending where on the print bed you are, it really starts to do my head in. Plus that's without considering bed mesh correction, tapering, skew adjustment, or others I don't even know about. 🙂

A user submitted a pull request to PrusaSlicer some time ago to fetch the printer speed and acceleration limits from the RRF object model and to modify the print time calculation to better reflect RRF when RRF is the selected firmware type; but unfortunately it wasn't actioned. See https://github.com/prusa3d/PrusaSlicer/pull/8087.

Oh, that's a shame, I for one would have found it useful.

@t3p3tony I've already tried that, it copies the file, resets and it's back to square one, can't connect to it 😞

@dc42 I experimented some more and came up with testing routine. Trying to set StealthChop to SpreadCycle at low speed. No luck... Or maybe at 10mm/s is all I can get?

Accel/jerk are halved in comparison to normal operation.

Each testing sequence consists of:

Configuration Homing with tuning Three sets of moves of Y and U separately Each set has different speed - 10, 50 and 100mm/s

It runs five tests with different configuration each:

StealthChop to SpreadCycle with switch at 10.4 mm/s StealthChop to SpreadCycle with switch at 52.1 mm/s StealthChop to SpreadCycle with switch at 93.8 mm/s Pure SpreadCycle Pure StealthChop

I've recorded a routine with first 3 sequences. Every time movement is above switch speed then "clack" happens. Its visibly less noticeable at low setting, but is still there. As it's increased then it gets much worse.

If you could look if I did homing/tuning correctly, please.

I'll proceed to experimenting with different speeds. Previously when I picked different values for M569 and M915 I've got some improvement - clacking was getting less and less visible.

Thanks for your time and input.

Video (last two removed for brevity):
https://youtu.be/yojaNXBJG9s

Macros:
stealthChop.home.g

; Homing and tuning M18 X U Y Z ; Disable motors M17 X U Y Z ; Enable motors G4 P100 ; Wait G91 ; Relative positioning G1 Z5 F1000 H2 ; Lift Z relative to current position G1 X-999 U999 Y-999 F3000 H1 ; Move and Tune G1 X5 U-5 Y5 F6000 H2 ; Go back a few mm G1 X-999 U999 Y-999 F360 H1 ; Move again G1 Z-5 F1000 H2 ; Return Z to previous height G90 ; BLTouch preperation M280 P0 S160 ; Precautionary alarm release M280 P0 S90 ; Ensure the pin is raised ; Home Z using the Z-Probe G91 ; Relative positioning G1 Z10 F1000 H2 ; Lift Z relative to current position G90 ; Absolute positioning G1 X-130 Y-115 F6000 ; Move T0 to probing point, including probe offset G30 ; Probe the bed and set Z to the probe offset G1 Z10 F1000 ; Raise Z off the bed

stealthChop.test.g

; Initial settings var distance = 30 ;mm var speed_high = 100 ;mm/s var speed_high_min = 60 * var.speed_high; var speed_med = 50 ;mm/s var speed_med_min = 60 * var.speed_med; var speed_low = 10 ;mm/s var speed_low_min = 60 * var.speed_low; G1 X-999 U0 Y0 F3000 ; Prepare for test G4 P1000 ; Test Low Speed while iterations < 3 G1 U{var.distance/4} F{var.speed_low_min} G1 U{-(var.distance/4)} F{var.speed_low_min} while iterations < 3 G1 Y{var.distance/4} F{var.speed_low_min} G1 Y{-(var.distance/4)} F{var.speed_low_min} ; Test Medium Speed while iterations < 3 G1 U{var.distance/2} F{var.speed_med_min} G1 U{-(var.distance/2)} F{var.speed_med_min} while iterations < 3 G1 Y{var.distance/2} F{var.speed_med_min} G1 Y{-(var.distance/2)} F{var.speed_med_min} ; Test High Speed while iterations < 3 G1 U{var.distance} F{var.speed_high_min} G1 U{-(var.distance)} F{var.speed_high_min} while iterations < 3 G1 Y{var.distance} F{var.speed_high_min} G1 Y{-(var.distance)} F{var.speed_high_min}

stealthChop.spreadCycle.test.g

; RR VCast IDEX (Cartesian) ; Duet 3 6HC TMC5160 ; Testing U and Y ; XUY using 2.5A/3.1V LDO-42STH47-2504AC ; https://www.ratrig.com/nema-17-stepper-motor.html ; 1. Load StealthChop to SpreadCycle settings ; 2. Tune drivers ; 3. Run test for StealthChop to SpreadCycle ; 4. Run test for StealthChop only ; 5. Run test for SpreadCycle only G4 S5 ; Time to start recording :) ; Accel/Jerk are halved in comparison to normal operation M906 X2125 U2125 Y2125 Z1600:1600 E350:350 I50 ; set currents M566 X350 U350 Y350 Z60:60 E300:300 ; set maximum instantaneous speed changes (mm/min) M203 X6000 U6000 Y6000 Z1800:1800 E3600:3600 ; set maximum speeds (mm/min) M201 X400 U400 Y450 Z100:100 E600:600 ; set accelerations (mm/s^2) M204 P400 T400 ;------------------------------------ ;---- StealthChop to SpreadCycle ---- ;------------------------------------ echo "Enable StealthChop to SpreadCycle settings (Switch Speed - 10.4 mm/s)" ; Reset Coolstep M915 P0.0:0.1:0.2:0.3:0.4:0.5 T1 ; disable coolstep M915 P20.0:21.0 T1 ; disable coolstep ; Set U M569 P0.1 S0 D3 V900 H900 M915 P0.1 T900 ; Set Y M569 P0.2 S0 D3 V900 H900 M915 P0.2 T900 ; Homing and tuning M98 p"/macros/stealthChop.home.g" M98 p"/macros/stealthChop.test.g" echo "Enable StealthChop to SpreadCycle settings (Switch speed - 52.1 mm/s)" ; Reset Coolstep M915 P0.0:0.1:0.2:0.3:0.4:0.5 T1 ; disable coolstep M915 P20.0:21.0 T1 ; disable coolstep ; Set U M569 P0.1 S0 D3 V180 H180 M915 P0.1 T180 ; Set Y M569 P0.2 S0 D3 V180 H180 M915 P0.2 T180 ; Homing and tuning M98 p"/macros/stealthChop.home.g" M98 p"/macros/stealthChop.test.g" echo "Enable StealthChop to SpreadCycle settings (Switch speed - 93.8 mm/s)" ; Reset Coolstep M915 P0.0:0.1:0.2:0.3:0.4:0.5 T1 ; disable coolstep M915 P20.0:21.0 T1 ; disable coolstep ; Set U M569 P0.1 S0 D3 V100 H100 M915 P0.1 T100 ; Set Y M569 P0.2 S0 D3 V100 H100 M915 P0.2 T100 ; Homing and tuning M98 p"/macros/stealthChop.home.g" M98 p"/macros/stealthChop.test.g" ;------------------------------------ ;---- SpreadCycle only ---- ;------------------------------------ echo "Enable SpreadCycle settings" ; Reset Coolstep M915 P0.0:0.1:0.2:0.3:0.4:0.5 T1 ; disable coolstep M915 P20.0:21.0 T1 ; disable coolstep ; Set U (Factory values) M569 P0.1 S0 D2 H200 M915 P0.1 T2000 ; Set Y M569 P0.2 S0 D2 H200 M915 P0.2 T2000 ; Homing and tuning M98 p"/macros/stealthChop.home.g" M98 p"/macros/stealthChop.test.g" ;------------------------------------ ;---- StealthChop only ---- ;------------------------------------ echo "Enable StealthChop settings" ; Reset Coolstep M915 P0.0:0.1:0.2:0.3:0.4:0.5 T1 ; disable coolstep M915 P20.0:21.0 T1 ; disable coolstep ; Set U (Above 100mm/s) M569 P0.1 S0 D3 V50 H50 M915 P0.1 T50 ; Set Y M569 P0.2 S0 D3 V50 H50 M915 P0.2 T50 ; Homing and tuning M98 p"/macros/stealthChop.home.g" M98 p"/macros/stealthChop.test.g"

@sebkritikel

Thank you for your in-depth answer. Sorry I haven't replied earlier. I haven't been able to work on this for a few days.

Regarding this question you asked me:

Now, as far as when you unselect T2, do you still have it as "G1 X-75 U365 F6000" OR "G1 H2 X-75 U365 F6000" ? I tested my tfree2.g by having it go a few mm off the homing position, and it worked as expect (i.e. it went to U365 and NOT U368.7).

At the time you asked the question, my tfree2.g was like this:

G91 ; relative axis movement G1 Z3 F500 ; up 3mm G90 ; absolute axis movement G1 X-75 U365 F6000 ; park the X and U carriages

However, I have just tried playing around with the U value of the G1 command and found that with U215, after unselecting T2, the U carriage moves to its parking position and reported position is U=365. i.e. works correctly to me.

My possible explanation for this is that this command in tfree2.g is executed still with the offsets applied. As a reminder, my G10 command for T2 is: G10 P2 X0 Y0 U-150 Z0. So, 215+150= 365.

Also, I haved tried adding the H2 parameter on tfree2.g but the carriadges kept crashing onto the ends. I guess that by playing around a little I would have found a value that also ended up with the carriadges parked in the correct position, but went the other way instead.

I think I am going to leave it like this for the time being.

Also, I have another question. In my tfree2.g, Z is raised 3mm. The machine does so correctly. However, after finishing releasing T2, it moves the Z back down. Is this something done automatically by RRF?

Thank you once again.

@MauriceM said in Problem to Set Up Duet Wifi:

but i did the fallback procedure an now the baord is listed as bossa in the com. this cant be right, or?

you probably need to reset the board as part of the fallback procedure, or ensure the erase jumper is removed after conncecting with bossa, but before starting the writing.

Definitely hold back on calling me a genius too! 😋

alright, great, thanks!
(can I mark this as solved?)

If you have a spare heater output (or you use RRF3, which allows you to configure a fan pin as a heater output), you can connect the fan to it. Then use the M307 I parameter for that heater to invert the sense of operation, i.e. the PWM will increase as the temperature rises. Is that what you need?

@dc42

Hello!

Checked what you said and it solved my problem.

For some reason the cables on the endstops were ALL wired incorrectly (and all were different in the way they were connected) so I checked everything with a multi meter and everything is no correct.

Also i needed to set them to normally open instead of normally closed.

Everything is now homing perfectly as it should. On to the next bump!

Thank you for your help!

Thanks, @oliof !

this happen to me i fix by going to endstop config and switch from false to true and that fix the homing problem