@matt3o Well done! And a very nice Print!

@tinchus I think you can solve the problem with putting an ";E" after the comment semi-colon, like this:
G1 Z400 ;E drop the print bed (E to exclude from layer count)

(Obviously, you need to be in absolute positioning mode for this to work)

@andreic I think your ducts produces to much back pressure. You should test the fan in "free air" for comparison...

@educatingsavvas i think T-1 should work

@cr3d I don't know which macro is called when the filament out sensor triggers...
But in that macro you can "store" the actual Extruder Value in a variable, make your math, and call another macro after 50cm of extruding.
Eventually is daemon.g also a good option to put the code in...

@o_lampe said in rc servo not moving:

@cosmowave

Sservo pins are just GpOut pins with a different default PWM frequency.

Maybe you must not overwrite the Servo frequency with 'Q500'?

I have tried different frequencies, also without a "Q" Value

@dc42 said in rc servo not moving:

@cosmowave said in rc servo not moving:

M950 S1 C”exp.heater3” Q500 ; assign GPIO port 1 to heater3 on expansion connector, servo mode M280 P1 S46 ; set (~1deg?) servo position on GPIO port 1 (Servo range 44.2 - 141.2?)

Looks like those are the wrong sort of double quote characters in your M950 command. The correct ones look like " not ”.

O yes! You are right! This is a bit embarassing...
sorry for that, and thanks!

@cosmowave Can it be that there is a problem of the format of your variable?
e.g. the variable is a string, but M92 needs a "float"...

@mintytrebor
I will try that in the evening...
Some days ago, i have tried to install the plugin with RRF3.3b3.
Was the same problem. So i think, something is wrong in my system or browser.
I will clear the browser cache and history before installing the "new" set.

@handymanpa54 I use a macro for manually leveling the bed.
The macro moves to the 4 corners, 20mm away from max.

; LevelAssist macro
; this macro helps for manually leveling the bed, it moves the nozzle to 4 probing points (20mm away from min/max area)
; the macro will automatically aborted if no user action during 120s

var EntryTime = state.upTime												; set start time
var ReturnTime = 120														; set abort time

if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed		; axles homed ?
	M291 P"axles not homed! perform homing ?" R"LevelAssist" S3
	G28																		; homing

; loop beginn 
while state.upTime < {var.EntryTime + var.ReturnTime}								; loop until cancel or abort time
	M291 P"move to Point1 ?" R"LevelAssist" S3								; message
	
	G0 Z4																	; Z +
	G0 X{move.axes[0].min + 20} Y{move.axes[1].min + 20}					; move XY to Point1
	G0 Z0																	; Z -
	set var.EntryTime = state.upTime										; reset start time

	M291 P"move to Point2 ?" R"LevelAssist" S3								; message
	
	G0 Z4																	; Z +
	G0 X{move.axes[0].min + 20} Y{move.axes[1].max - 20}					; move XY to Point2
	G0 Z0																	; Z -
	set var.EntryTime = state.upTime										; reset start time
	
	M291 P"move to Point3 ?" R"LevelAssist" S3								; message
	
	G0 Z4																	; Z +
	G0 X{move.axes[0].max - 20} Y{move.axes[1].max - 20}					; move XY to Point3
	G0 Z0																	; Z -
	set var.EntryTime = state.upTime										; reset start time
	
	M291 P"move to Point4 ?" R"LevelAssist" S3								; message
	
	G0 Z4																	; Z +
	G0 X{move.axes[0].max - 20} Y{move.axes[1].min + 20}					; move XY to Point4
	G0 Z0																	; Z -
	set var.EntryTime = state.upTime										; reset start time
	
	M291 P"once again or cancel ?" R"LevelAssist" S3						; once again?

@blaidd Your connector can lead to a problem!
You should try to crimp them more carefully. The free thin copper wires can produce a short circuit!

@jens55 Can you please post a photo of your filament cooler setup?

@chris94 no problem. you're welcome.

@chris94 very nice!

@kb58 In line 8500 of your gcode is the 100mm move

@kb58 There is a G1 Z50 F1200 move in it!

@kb58 what is in your "print_end.g" macro?

@chris94 can you probably try it at lower speed?

@chris94 it can be, that the stepper missing some steps.
But it is strange when it happens only during that move...

@chris94 What happens if you put a G90 in slicer startcode?

@chris94 Yeah sure...
Can it be, that the z move in you gcode (G1 F100 Z0.8) is done relative instead of absolute.
But if this is the case, i don't know why...
But eventually you can hear/feel/see the little 0.8mm move?