Topics created by pandaym

@pandaym said in [3.3.0] - Folder structure issues?:

In the firmware folder I have 13, but in sys I have 16. Is it safe to delete all 16?

The difference is some IAP files used for older versions of RRF, so if you don't intend to go back to older versions, you can safely delete those files. You'd still be able to go back without them by uploading the combined zip file since they will usually include all required files for that version. (or using bossa to flash directly)

@droftarts said in Klipper features in RRF - Input shaping, -jerk, cal. scripts ?:

@pandaym For Input shaper, RRF version is https://duet3d.dozuki.com/Wiki/Gcode#Section_M593_Configure_Dynamic_Acceleration_Adjustment

klipper claims it works much better and have ability to remove more than one frequency

For Acceleration / square corner velocity / jerk you can change the jerk policy with P parameter in https://duet3d.dozuki.com/Wiki/Gcode#Section_M566_Set_allowable_instantaneous_speed_change. I'm not sure how it's 'gone' in Klipper (haven't really looked at it), unless they're using S curve motion planning. There's been a number of long threads about the arguments for and against S-curve; general view is there's little advantage in 3D printing, but probably good for slower CNC-type applications. (Cue flame war!)

they used something very similar to S curve with talk to moving to full S curve and the benefits are immediately visible on images of printed parts ppl shared (I have not tried myself)...

Calibration scripts - the addition of conditional gcode should make this much easier. Someone just needs to write them!

I think this is a good start, not sure what's missing here:
https://forum.duet3d.com/topic/6181/tuning-macros-menus-accel-jerk-retraction-pressure-advance

@Phaedrux said in Z probe was not triggered during probing move - bed crash:

Please keep us posted on if it continues to happen and if you remove the cancel.g file if that causes it to happen reliably again.

In addition to the motor current drop you can also add the BLTouch alarm release command to the start of homeall to clear any error state and retract the pin as a precaution. I think I may have mentioned that already.

Sorry, I did not press submit on the answer I had written here.

I disassembled the printer to redo some wiring etc. to finish it off. When I am done, I will continue testing it, and I will get back if it keeps happening. Also I will add the alarm release, just to have an extra precaution.

Thanks a lot for the help!

@nhof said in CoreXY - Sanity check on values for acc, jerk, speeds, etc.:

I would up the jerk setting on the extruder axis and maybe Z as well. 20 is very low, I use values of about 500-600 for my E. The rest looks reasonable to me.

Thanks a lot. You also on a Hemera?

Flashing red usually indicates error state if the self test is unable to successfully deploy and retract the probe or if the pin is blocked when trying to deploy. Could also be an intermittent wiring break depending on position.

As a precaution you can add the alarm release and pin retract command to the end of config.g and start of homeall to clear any errors just in case.

You can try and take the pin out of the probe and check it/clean it by removing the set screw on the top.