Best posts made by cosmowave

As a small "fun project" i have designed and produced a new hotend and effector for my Delta Tower V2.
My idea was to stay fully compatible with the original Delta Tower hardware but with a smaller and watercooled hotend.
Addititionally, the new hotend design is for 1.75mm filament, to cover both diameters in the future.
The effector is milled from "aircraft" aluminium. There is still some weight reduction possible because the effector is very stiff.

But now some pictures of my design. Eventually, it gives some ideas to other forum users.
If someone has suggestions for improving the design... everything is welcome.

@chrishamm Thank you too for fixing it. I will try it again today evening...
Once again, many thanks for all other in the "RRF project" involved people for the work and commitment like @dc42 , @droftarts, @Phaedrux and all others which i may have forgotten to mention!

I'm very happy and it's a pleasure to use DUET3D boards and the RRF firmware!

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

This post is only for information and for closing this point!

The problem with my tacho signal is solved.
I have developed a signal multiplier/divider with a raspberry pi pico. The system is able to multiply or divide an incoming (tacho) signal with a factor between 1 and 15.
When i multiply my flowmeter tachosignal with factor 5, i'm allways in a range which RRF can read.

If somebody has a similar problem, i'm happy to share my project.

Sorry for answering to this old post. And this is only for info:
I have finished the work on my prototype watercooled hotend. Now it's ready to make first tests...
The heating block and heatbreak is from a DTO hotend.

Here are some images

@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

This post is just for info:

I have expanded this "TachoMod" project a bit.
Actual version is V4.0 with the following additional functions:

• Raspberry Pico has now a small OLED-Display (with 2 buttons) for displaying datas and enabling a menu
• Tacho-signal period and rpm of in-/output is displayed
• Menu for changing multiply/divide mode, factor, timeout, pulse per revolution
• stores all settings on onboard memory

If someone is interessed, i can share the source code and additional infos...

@o_lampe Thanks.
These aren't brass water connectors. That would be too heavy!
They are from coated titanium.

EDIT: I tried to save weight where it is possible. I used aluminium bolts to mount the parts on the effector. Next time it would be suffizient to machine the effector in a "L-shape" instead of a "U-shape". Actually it is more than stiff enough and that would be safing much weight.

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

@agusano Which FW Version are you using?

Eventually you can invert it with a leading "!" in the M950 command

M950 F2 C"!Fan2" Q25000

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

Oh, i have seen now, that the second line has to be intended!
It's all clear now.

@mikeabuilder said in Bainbridge BARN Mark4:

but we're thinking of moving it to a location under the printing zone

try to install the electronics with good accessibility... it's much easier to make changes or checking some things.

@nightowl Yes. It makes sense to write some macros.
You can define the "start.g" and "end.g" macros in the sys folder , which are automatically called at start / end of your job.

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

@davidewen You have to write a macro with M300 and G4...

@eranglr Ah... ok. It's not possible because it's one long move...
Sorry for that.
Not sure if you can make something with "segmentation"?

EDIT: could be possible to use segmentation with M669, which is dividing a long move in many shorter moves...