nichols89ben
commented
5 months ago For some additional context, if anyone happens to see this. Here is the debug output with these additional options. From what I can tell, theres nothing setitng wise telling X2 to park in X1. I let it crash into X1 and after a few skips, it zoomed (very fast) to X2 home, then running into the endstop and skipping some more (assuming due to it thinking its position was different)
#define DEBUG_DXC_MODE
#define DEBUG_ECHOLNPGM
#define DEBUG_TOOL_CHANGE
Set T0
Send: T0 D
echo:T0 D
>>> T X161.3000 Y133.2000 Z13.4500
...(0)
Active Extruder: 0
<<< T X161.3000 Y133.2000 Z13.4500
ok
X:161.2969 Y:133.2000 Z:13.4500 E:0.0000 Count X:10323 Y:10656 Z:5380
Set T1
Send: T1 D
echo:T1 D
>>> T X161.3000 Y133.2000 Z13.4500
...(1)
Axis X min:25.0000 max:365.0000
Dual X Carriage Mode AUTO_PARK
MoveX to -51.3000
>>> set_axis_is_at_home(X)
current_position= X365.0000 Y133.2000 Z13.4500 : New Extruder
Active extruder parked: yes
current_position= X365.0000 Y133.2000 Z13.4500 : New extruder (parked)
Offset Tool XYZ by { 0.0000, 0.0000, 0.0000 }
current_position= X365.0000 Y133.2000 Z13.4500 : sync_plan_position
Move back Z only
do_blocking_move_to_z(13.4500, 5.0000)
>>> do_blocking_move_to X365.0000 Y133.2000 Z13.4500
> X365.0000 Y133.2000 Z13.4500
<<< do_blocking_move_to X365.0000 Y133.2000 Z13.4500
Active Extruder: 1
<<< T X365.0000 Y133.2000 Z13.4500
X:365.0000 Y:133.2000 Z:13.4500 E:0.0000 Count X:23360 Y:10656 Z:5380
Set T0 again - Crash, first smashes into left X1 Carriage, then rapidly tries to move past X2 Max and crashes into
endstop (maybe becasue it thought it was farther left)
Send: T0 D
echo:T0 D
>>> T X365.0000 Y133.2000 Z13.4500
...(0)
Axis X min:-55.0000 max:288.0000
X:365.0000 Y:133.2000 Z:13.4500 E:0.0000 Count X:23360 Y:10656 Z:5380
echo:busy: processing
Dual X Carriage Mode AUTO_PARK
MoveX to 365.0000
X:-4.4062 Y:133.2000 Z:13.4500 E:0.0000 Count X:-277 Y:10656 Z:5380
>>> set_axis_is_at_home(X)
> home_offset[X] = 0.0000
current_position= X-51.3000 Y133.2000 Z13.4500 :
<<< set_axis_is_at_home(X)
current_position= X-51.3000 Y133.2000 Z13.4500 : New Extruder
Active extruder parked: yes
current_position= X-51.3000 Y133.2000 Z13.4500 : New extruder (parked)
Offset Tool XYZ by { 0.0000, 0.0000, 0.0000 }
current_position= X-51.3000 Y133.2000 Z13.4500 : sync_plan_position
Move back Z only
do_blocking_move_to_z(13.4500, 5.0000)
>>> do_blocking_move_to X-51.3000 Y133.2000 Z13.4500
> X-51.3000 Y133.2000 Z13.4500
<<< do_blocking_move_to X-51.3000 Y133.2000 Z13.4500
Active Extruder: 0
<<< T X-51.3000 Y133.2000 Z13.4500
X:-51.2969 Y:133.2000 Z:13.4500 E:0.0000 Count X:-3283 Y:10656 Z:5380
InsanityAutomation
thisiskeithb
ellensp
p3p
Did you test the latest
bugfix-2.1.xcode?Yes, and the problem still exists.
Bug Description
On an IDEX set up, after switching active extruder from T0 to T1, T0 parks to the endstop, but mumps out a few mm from the max, taking some space away from T1. If the tool is changed back to T0 while set as T1, it causes T1 to try and park (presumably) at the T0 position, causing T1 to crash into T0. I
Bug Timeline
Year +, Noticed it on stock SV04 firmware, coudnt pin it down
Expected behavior
T1 park at the X2 Max position, When T0 or T1 parks, it parks at the max and doesnt bump out a few mm
Actual behavior
T1 crashes into T0
Steps to Reproduce
Home T0 Set T1 Set tool to T0
Version of Marlin Firmware
bugfix-2.1.x 2024-03-25
Printer model
SV04 Modified
Electronics
BTT Octopus V1.1
LCD/Controller
BTT
Other add-ons
No response
Bed Leveling
ABL Bilinear mesh
Your Slicer
Cura
Host Software
OctoPrint
Don't forget to include
Configuration.handConfiguration_adv.h.Additional information & file uploads
Debug output during movements/collision bellow, video of the movements on the google drive link. In the video, the steps are G28, T1 (T0 parks and bumps out), set tool back to T0 Archive.zip
https://drive.google.com/file/d/1s2DzKM3vYhYLTyX_1aTZmSLBmtcjejQs/view?usp=sharing