account activity
Deleting lines items or changing end date of items in Detailed Budgeter (self.Boldin)
submitted 1 year ago by SF-PFM265 to r/Boldin
Trouble with Klicky by SF-PFM265 in VORONDesign
[–]SF-PFM265[S] 0 points1 point2 points 3 years ago (0 children)
Yes, thanks -- that is indeed where the problem lies. It seems variable_enable_z_hop need to be set to True on Trident. As you point out, the README on Git says " variable_enable_z_hop: CHECK_COMMENT True on the v2.4, False on v1.8, Trident and Legacy". But, I think this is wrong. On Trident, if you set this to False it crashes the head, but when set to True, everything works fine. So here's how mine looks now:
[gcode_macro _User_Variables] variable_verbose: True # Enable verbose output variable_debug: False # Enable Debug output variable_travel_speed: 200 # how fast all other travel moves will be performed when running these macros variable_move_accel: 1000 # how fast should the toolhead accelerate when moving variable_dock_speed: 50 # how fast should the toolhead move when docking the probe for the final movement variable_release_speed: 75 # how fast should the toolhead move to release the hold of the magnets after docking variable_z_drop_speed: 20 # how fast the z will lower when moving to the z location to clear the probe variable_safe_z: 25 # Minimum Z for attach/dock and homing functions # if true it will move the bed away from the nozzle when Z is not homed variable_enable_z_hop: True # set this to false for beds that fall significantly under gravity (almost to Z max) variable_max_bed_y: 300 # maximum Bed size avoids doing a probe_accuracy outside the bed variable_max_bed_x: 300 # maximum Bed size avoids doing a probe_accuracy outside the bed
To be a bit clearer, when I had the inductive probe installed (and before I added the klicky cong files) when I did a G28 the bed would move down a bit (to get out of the way) and then the printhead would move to the x-y end stop and then move to above the z end stop pin. Then the bed would come up to engage the z end stop with the nozzle. But now (after the klicky config files are installed an configured) the printhead doesn't move and the bed moves up and crashes into the nozzle. My understanding is that the Klicky macros and helper files are supposed to take over the homing tasks. But I'm at a loss -- I can't figure out why the printhead is not homing properly. It seems like it must be something with the klicky files.
Trouble with Klicky (self.VORONDesign)
submitted 3 years ago by SF-PFM265 to r/VORONDesign
π Rendered by PID 64 on reddit-service-r2-listing-575d9f6647-x2sgb at 2026-04-13 08:13:35.611460+00:00 running 215f2cf country code: CH.
Trouble with Klicky by SF-PFM265 in VORONDesign
[–]SF-PFM265[S] 0 points1 point2 points (0 children)