IDEX HOMING ISSUES
-
@Rollux Are your end stops working properly? Are the motors running in the right direction?
-
@Proschi78 end stops trigger when either touched by motor or by finger for testing, motors all go in correct direction (when working). When homing z, the axis still drops back 5 mm after touching off, lifting 5 and dropping again, these lines have been removed so shouldn't be doing that but only probes once and not twice.
-
@Rollux Looking at your config.g, unless I missed it, I don't see any M669 command to define the Kinematics for your machine. I'm not sure what the default is but it may be Cartesian - it almost certainly won't have a U axis by default. Send M669 without any parameters to see what it reports. Link to documentation is here https://docs.duet3d.com/User_manual/Reference/Gcodes#m669-set-kinematics-type-and-kinematics-parameters
-
@deckingman said in IDEX HOMING ISSUES:
M669
6/3/2024, 4:48:42 PM M669
Kinematics is Cartesian, no segmentation, matrix:
1.00 0 0 0
0 1.00 0 0
0 0 1.00 0
0 0 0 1.00im wondering if there is some stuff "stuck" in the mb6hc cache/memory that might be affecting things?
-
-
@Rollux
increase the x value to x-450; called to home all axes ; ; generated by RepRapFirmware Configuration Tool v3.4.1 on Sun May 26 2024 18:23:03 GMT+0800 (Australian Western Standard Time) G91 ; relative positioning G1 H2 Z5 F6000 ; lift Z relative to current position G1 H1 X-450 Y-430 U0 F1800 ; move quickly to X Y and U axis endstops and stop there (first pass) G1 H2 X5 Y5 U-5 F6000 ; go back a few mm G1 H1 X-450 Y-4300 U0 F360 ; move slowly to X Y and U axis endstops once more (second pass) G90 G1 F6000 X243 Y200 G30 ; absolute positioning G29 S1 ; this loads the contents of /sys/heightmap.csv
-
@Proschi78
Increased the x value to x-450.
Individual homing works fine when selected separately.
Home all on the other hand is inconsistent still. During "home all", when the x axis triggers the end stop, the y axis will also trigger even though it has not yet hit the end stop. Bltouch will lower, trigger, raise 5mm then drop 5mm (not sure where else the lines of code for this are found as i have removed all i can find as i want the z axis to not drop down after probing).
Also, the z axis moves up or down when making manual moves via the panel due or dwc. Ifeel there is something somewhere that is conflicting. All the boards were well outdated (3.3 beta from memory) as they have been sitting for a while so wondering if a hard reset of the main board and the 3xc are in order? -
@Rollux
try this as homeallM561 G91 G1 H2 Z5 F6000 ; raise head 4mm to keep it clear of the bed G1 H1 X-450 Y-450 U0 F3000 ; coarse home X, Y and U G1 X5 Y5 U-5 F3000 ; move 4mm away from the homing switches G1 H1 X-400 Y-430 U0 F600 ; fine home X, Y and U G90 ; absolute positioning ; Now home Z using the Z probe G1 X243 Y200 F3000 ; move to bed centre for probing G30 ; probe the bed and set Z height G1 x-450 y-430 U0 F3000 G29 S1
-
@Proschi78
Y axis doesnt move. Wont re home manually without a re boot. Reboot the board, Y axis "triggers" at the same point as the x axis regardless of position.
Thinking will reset the mainboard and re flash firmware as something may be hanging around from all the updates and the like. -
@Rollux If all the individual homing files work, then you could call them individually for home all.
e.g. homeall could be..........
M98 P"homex.g" M98 P"homeu.g" M98 P "homey.g" M98 P"homez.g"
Try that - if it works, then the problem is with your homeall.g, if it doesn't then the problem is elsewhere.
-
@deckingman
Success there on the first try. Then move everything around and try again. X and U axis home perfectly. . Y axis jumps and then does nothing and get the following error: Error: in file macro line 17: M98: expected a string expression.Going to have a look at the y axis endstop
m119
Endstops - X: at min stop, Y: at min stop, Z: no endstop, U: at max stop, Z probe: not stoppedAs it is one the "pcb board" style ones, wondering if it has failed but that doesnt explain why it works once or twice then nothing.
-
Replaced the endstop with a pare makerbot pcb style. Same issue. Check wiring, all is good. Hard reset. All homed perfectly, repeatedly. Then back to the same issue of the y axis bumping in the opposite direction if the end stop and failing to home.
-
"Home all" using individual axis works as expected. However, homing individual axis via dwc or panel due, Y axis does not want to work. Incredibly confusing.
-
Current homeall.g
This works somewhat, the U axis homes after x,y,z regardless of U axis position.Also when homing z, the z jumps up and down and the x and y jump around. Video Attached of whats happening.
G91 ; relative positioning G1 H2 Z5 F6000 ; lift Z relative to current position G1 H1 X-450 F5000 ; move quickly to X Y and U axis endstops and stop there (first pass) G1 H1 U0 F5000 G1 H1 Y-450 F5000 G1 H2 X5 F6000 ; go back a few mm G1 H2 U-5 F6000 G1 H2 Y5 F6000 G1 H1 X-450 F360 ; move slowly to X Y and U axis endstops once more (second pass) G1 H1 U0 F360 G1 H1 Y-450 F360 G1 F6000 X243 Y200 G30 G90 ; absolute positioning G29 S1 ; this loads the contents of /sys/heightmap.csv [Home All.mp4](/assets/uploads/files/1717502002687-home-all.mp4)
-
-
It looks to me like the mesh bed compensation is going on a total roller coaster ride. Can you disable it before homing
-
@Proschi78 said in IDEX HOMING ISSUES:
@Rollux
try this as homeallCan you take over the code with copy paste for homeall that I posted here?
M561 G91 G1 H2 Z5 F6000 ; raise head 4mm to keep it clear of the bed G1 H1 X-450 Y-450 U0 F3000 ; coarse home X, Y and U G1 X5 Y5 U-5 F3000 ; move 4mm away from the homing switches G1 H1 X-400 Y-430 U0 F600 ; fine home X, Y and U G90 ; absolute positioning ; Now home Z using the Z probe G1 X243 Y200 F3000 ; move to bed centre for probing G30 ; probe the bed and set Z height G1 x-450 y-430 U0 F3000 G29 S1
-
@Proschi78 Will give this a try tomorrow, unable to connect to the printer at the moment as having internet/router issues and pc vs printer location makes ethernet connection not viable.
-
@Proschi78
Tried the above and the movement behaviour became consistently erratic. Not sure as to why. Reverted back to the below and seems to be have "settled" to a somewhat normal behaviour. Potentially might reset the mbh6c and expansion board back to square one. Potentially the firmware updates may have left some things stuck which shouldnt be the case but never know as all the boards were still on 3.2 beta firmware when started up this time round.
M561 G91 ; relative positioning G1 H2 Z5 F6000 ; lift Z relative to current position G1 H1 X-450 F5000 ; move quickly to X Y and U axis endstops and stop there (first pass) G1 H1 U0 F5000 G1 H1 Y-450 F5000 G1 H2 X5 F6000 ; go back a few mm G1 H2 U-5 F6000 G1 H2 Y5 F6000 G1 H1 X-450 F360 ; move slowly to X Y and U axis endstops once more (second pass) G1 H1 U0 F360 G1 H1 Y-450 F360 G1 F6000 X243 Y200 G30 G90 ; absolute positioning G29 S1 ; this loads the contents of /sys/heightmap.csv