@jay_s_uk Wow I seriously have read over that 10 times I think. sorry for the unnessecary question
Thanks all!
Best posts made by SanderLPFRG
-
RE: On-device start gcode handling
-
RE: Trying to fix my dual markforged (HAQ-XY) kinematics
@gloomyandy said in Trying to fix my dual markforged (HAQ-XY) kinematics:
at it is probably not a good thing
Ill redesign the belt tensioning mechanism and the belt mounting, when measuring it indeed looks to be too loose
WIll see what this does -
RE: How do I use the filament sensor as a trigger for autoloading??
@OwenD I did exactly that yesterday late afternoon. It is working now.
; Custom buttons M950 J1 C"^io2.in" ; define logical input for E1 filamentsensor M581 P1 T2 S0 R2 ; define trigger for filament auto load (trigger2.g) M581 P1 T4 S1 R1 ; define trigger for filament runout (trigger4.g)
Thank you very much both!
-
RE: M291 S4+ commands not working on RRF 3.5beta2
@chrishamm It works!!
It both updated correctly, and now the M291 functions correctly.
Massive thanks Chris and Tony.I'll now work on trying to understand how I can use the input to trigger Gcode commands
-
RE: Cannot use M291 input as variable in loop
@OwenD Damn, this did the trick. Thank you so much owen! also thanks @chrishamm
-
RE: longterm probe reliability testing
My goal is to test a shitload of probes, and see how much it starts to deviate after thousands. Your script might actually work, let me test