Skip to content

index-cal cfg updates & fixes - #43

Open
3DPrintDemon wants to merge 1 commit into
BondtechAB:mainfrom
3DPrintDemon:update_indx_cal
Open

index-cal cfg updates & fixes#43
3DPrintDemon wants to merge 1 commit into
BondtechAB:mainfrom
3DPrintDemon:update_indx_cal

Conversation

@3DPrintDemon

Copy link
Copy Markdown

Fix camera cal macro names, move cal test inboard, improve load cell cal macro, add manual tool remove & toolhead state resets.

  • Camera calibration names with numerics in the middle always fail
    Cal fail

  • Changing the names to written numbers fixes this.

  • Move testing inbound slightly for peace of mind.

  • Improve load cell calibration macro

  • Add manual tool remove & set state macro

  • Add manual toolhead reset state macro

Feel free to edit or discard what you wish.

…cal macro, add manual tool remove & toolhead state resets
@kilene001-bit

Copy link
Copy Markdown

I found an issue in CAL_THREE_SAVE_XY_OFFSET while testing the camera calibration macros on a six-tool INDX setup.

At this point the nozzle has already been physically centered over the camera, and off_x / off_y represent the displacement from the saved T0 camera position. Applying the offset with MOVE=1 causes an additional physical move by the same vector after the values have been saved.

In testing, the resulting physical position was:

camera_position + 2 * calculated_offset

This affects any tool with a non-zero XY offset. A subsequent move back to the camera coordinates can hide the initial displacement, but it adds an unnecessary round trip and can expose motion or tool-seating repeatability error.

Removing MOVE=1 keeps the already-centered nozzle physically stationary while updating the coordinate system:

SET_GCODE_OFFSET X={"%.3f"|format(off_x)} Y={"%.3f"|format(off_y)}

The MOVE=1 in CAL_TWO_PREP_TOOL_CAL, where existing offsets are cleared before moving to the camera position, should remain unchanged.

After removing it, saving the offset produced no physical movement, and the resulting G-code position matched the saved camera reference within 0.0004 mm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants