-
-
Notifications
You must be signed in to change notification settings - Fork 19.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues when switching tools (RCBugFix) #4266
Comments
Still staring at |
I can make a video if you don't believe me and I just run the commands I posted above... |
Just a thought: In #3899 T1 also moves by ~30mm (179-150 =-29) . (offset between hotends ?) |
Anything I can do, test, try to help solving this? |
Ok I did some further tests with the RCBUgFix of half an hour ago. Then I levelled the bed, I use mesh/manual bed levelling and then the strange things started. Running there script without the pauses does move the tools correct except the strange move in the last line when switching to T1 again the head moves to X150 Y100 first and instantly to X179 Y81. |
Ok I made seom videos and the behaviour really worries me. G28
M218 T1 X29.5 Y-18.1 ; set offset
G1 Z3 F3000
G1 X150 Y100 ; middle of the bed
T1 ; T1 moves to X150 Y100
T0 ; T0 moces to X150 Y100
T1 S1 ; head stays, coordinates show X179 Y81
T0 ; T0 moves to X179 Y81
; and now start strange things
T1 ; T1 moves to X150 Y100 (!) and then to X179 Y81 and file 2: G28
M218 T1 X29.5 Y-18.1 ; set offset
G1 Z3 F3000
G1 X150 Y100 ; middle of the bed
G4 S2
T1 ; T1 moves to X150 Y100
G4 S2
T0 ; T0 moces to X150 Y100
G4 S2
T1 S1 ; head stays, coordinates show X179 Y81
G4 S2
T0 ; T0 moves to X179 Y81
G4 S2
; and now start strange things
T1 ; T1 moves to X150 Y100 (!) and then to X179 Y81 And I did the following:
The only one running fine is the first file right with an EEPROM with failsafe defaults. The second file behaves not correct. So the file with the pauses is always misbehaving, maybe I get something wrong with the pause commands, maybe the are not usable or I am getting something wrong? At least the first should do the rights things as this is nothing special but it only does with default values in the EEPROM, bed levelling seems to have an influence and rebooting after bed levelling changes the behaviour again... |
Sorry something got mixed up, I accidentally switched some links, I corrected the order in my previous post... |
I've added more logging for |
I uploaded the new firmware to the machine, I did NOT load failsafe defaults this time, I just run file 1 with am M111 S255 at the very beginning.
|
Your pointing out that MBL was involved led me to a happenstance discovery. The function that handles splitting up lines when mesh leveling is enabled was failing to account for the I think I might have fixed the issue with #4310. Please test https://github.com/thinkyhead/Marlin/tree/rc_mbl_position_shift when you have a chance. This should also have the updated logging in it. |
@Alex9779 Ok, should be in better shape. Watching the compiler… |
Waiting for a working version to test... |
Sorry, had to run before Travis caught my bugs. |
I had not time to test over the weekend, now everything is merged into RCBugFix. |
Ok I did some tests and some results are still strange but I think I know why. IMHO homing should be done with T0, if an other tool is selected this should be reset... |
A maybe different thing I found is that travel moves across the centre Y line (Y100) and X150 line stop at that line... This was gone with RC6, think it was before too and is now back... Is that connected to MBL and the mesh boundaries? |
Shall I open a new issue with the problems regarding homing? |
I did muck around with the mesh bed leveling "split on boundaries" code, but I took care to try to preserve the existing behavior. If the current |
Did a single nozzle print today with RCBugFix of yesterday. Worked without issues. |
Mesh bed leveling enabled? 🎩 |
For sure! |
Crossing my fingers that all the movement and coordinate oddities will be worked out very shortly. I know I say this a lot, but I think we might be able to do the RC7 release this very weekend. |
@Alex9779 was your print successful, can we close this issue ? |
Didn't try yet, sorry... I am having some motion system issues, I think a bearing is damaged... Will take a few days to replace... |
Currently no time and I don't feel like testing... Think it works but I am going back to RC6 for some time, I have to print... |
😿 |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
I am testing dual extrusion with RCBugFix and with the new
Tx S1
commands and while a simple switch seems to work in the whole process of multiple commands there are still issues.The sequence I run is:
The text was updated successfully, but these errors were encountered: