@mrehorstdmd Thank you very much for sharing. I fighted the issue half a day and finally used your advise - do not bother ) and made a model with 2 walls that printed without issues.

@R006 the value stored in probepoints.GetZHeight(x) is the height error (i.e. actual height at which the probe triggered less the configured trigger height) that was measured by the G30 Px command in your bed.g file. So in your example the stored value would be 0.5.

The bed is modelled as a flat plan if there 4 leadscrews are configured or as a twisted plane if 4 are configured. RRF uses a linear least squares algorithm to calculate the corrections.

@Phaedrux :
I will probe and check on diff XYpoints.

Can you tell me how much variation in the min & max reading after probing is acceptable to avoid creating gaps or tightening effect, if axes are all true & there isn't any tilt or skew?

IF i currently limit the amount of correction in M671 - S parameter, then what it should be to avoid creating gaps/tightening effect?

@p8blr said in Help configuring multiple heaters/sensors on Mosquito Magnum+:

M563 P1 S"Mosquito 1" D1 H5 F3

You only have heater5 assigned to the tool. Try H5:6

I have added the Model to NopSCADlib if anybody needs an OpenSCAD model.

0d813bde-7be0-4d40-9d77-715bc09d2256-image.png

got it couldn't find the e mail but finally I did . Thanks

@gringo

thats it. Now it works.

Thanks a lot @droftarts

@gringo
Ok
I'm clearly not up with M150 so hopefully someone else can help

All I can suggest is changing this

;loop through all the LED's while iterations < global.ledSize - 1 ; set to 1 less than number of LED's in neopixel if global.runLED = false M150 R0 U0 B0 P0 W0 S58 F0 ; turn off neopixels echo "exiting loop" break if global.ledState = 0 echo "next LED on " , iterations M150 R{global.rLED} U{global.gLED} B{global.bLED} W{global.wLED} P{global.ledBrightness} S1 F0 else echo "Next LED off" , iterations M150 R0 U0 B0 W0 P0 S1 F0 ; set next LED in loop to either brightness or off G4 S{global.ledDelay}

To this

;loop through all the LED's while iterations < global.ledSize if global.runLED = false M150 R0 U0 B0 P0 W0 S58 F0 ; turn off neopixels echo "exiting loop" break if global.ledState = 0 echo "next LED on " , iterations M150 R{global.rLED} U{global.gLED} B{global.bLED} W{global.wLED} P{global.ledBrightness} S{iterations+1} F0 else echo "Next LED off" , iterations M150 R0 U0 B0 W0 P0 S{iterations +1} F0 ; set next LED in loop to either brightness or off G4 S{global.ledDelay}

@droftarts said in Cant print taller than 200mm:

M208

spot on. Thank you!
160f0c63-2d31-451e-925e-41964068c8be-image.png

@HebigT
I watched it earlier.
Cool project and kudos to the developer both for doing it and sharing it.
I can see OEM's going for something like that to make calibration something that users need not know anything about. But it seems a lot of complexity to essentially pick a value when you an do it by eye with no added cost.

@Phaedrux there was a bug in Cura 5.3 that was fixed in 5.3.1

Hello everybody,
after send the code for the dsf log this said that trigger6 do the restart...

I checked trigger6 and my config.g and is truth... i did a mistake in the config.g file...

Sorry for that, i was desperate!!

Thanks for your support!

@Thugmek @Phaedrux Yes, it requires a recent DuetPi image, though. Also it's a good idea to check if the latest DSF packages are installed, recent ones should list external drives as SD card items.

M21 in SBC mode is just a wrapper for the mount utility, it could be used to mount network shares, for example. Possible examples are already documented on the G-codes dictionary page.

@teddphilipss The big problem I found is the clearance between the extruder and the rods, when the effector tilts. It needs a large effector. Or use a Bowden config, which I don't like very much (I will soon switch to a direct extruder on my FL SUN).

@chrishamm this worked! Thank you so much!

@sinned6915 related github issue:
https://github.com/Duet3D/RepRapFirmware/issues/622

T3P3 created this issue in Duet3D/RepRapFirmware open G30 improvements #622

@CvetanTokov related github issue:
https://github.com/Duet3D/RepRapFirmware/issues/620

T3P3 created this issue in Duet3D/RepRapFirmware open Tn P6 entered in resurrect.g when it should be Tn P0 #620

@tkln no, you need to define each motor as a separate axis, and move that. So for the X axis, define an extra axis U which has the motor you want to move independently:

M584 X0.2:0.3 U0.3

Then you can move the U axis with G1 U5 (relative rather than anbsolute axis movements will probably work best). I’m not sure exactly what will happen when you send a subsequent G1 X… movement, though. It should keep the spacing you have set. You will also need to home the U axis first, or give it a position with G92.

RRF does not natively support a six axis delta, so it will rely on the slicer to send appropriate commands if using more than the standard 3 axes.

Ian

@chrishamm Great, I'm waiting to experience. I see on Github : https://github.com/Duet3D/DuetPrintFarm

@skezo tracking this github issue here:
https://github.com/Duet3D/RepRapFirmware/issues/437

can you confirm its fixed in 3.5.0beta3?

michele-bertoni created this issue in Duet3D/RepRapFirmware closed Abort command in load.g or unload.g filament macros changes filament, as it was correctly loaded/unloaded #437