New Wifi install problems, need help
-
So, today's results so far:
When homing X; Z lift, carriage moves appx. 10 mm in the correct direction, z lower to original position.
Y Home: Z lift, carriage moves appx. 10 mm in correct direction, Z lowers
Z Home: Z lift appx. 10 mmHomeall: X and Y the same as above, then calls for Z bed compensation adjust with pop up window
Once homing done, though it doesn't really home, I can move X and Y in + directions and - directions until original positioning is reached. When I try Z positioning, X carriage moves in - direction.
The endstop LEDs are all on and will trigger, turn off, when activated. Set at active high. BUT when I look at machine properties in Settings, they are all triggered Yes and when I activate, they all register as No. Perhaps I have them wired incorrectly still?
And I still don't understand what is going on with the movements. We switched Z and X (properly so) yesterday, but they are still wrong when trying for individual movement.
-
Your homeall.g file is a bit screwed up. When you do G1 X-365 Y-255 F3000 S1, movement will stop when an end stop switch is triggered. That is to say, either the X or the Y end stop switch but not both. So if for example the Y axis switch triggered but X was still 50 mm away from the end stop, then when you do the next line G1 X5 Y5 F6000 Y will move to plus 5 but X will move to 50 + 5. Then your fine homing line G1 X-365 Y-255 F360 S1 will move back until one or other switches trigger again so Y will go to zero but X will still be 50 and will therefore never be homed. You can tell on the web interface as the axis buttons only turn blue when homing has been successful. So you need individual G1 S1 moves for each axis. e.g after G1 X-365 Y-255 F3000 S1 you then need G1 X-365 F3000 S1 and G1 Y-255 F3000 S1 and the same for your fine homing (or just home each axis in turn).
HTH -
Your homeall.g file is a bit screwed up. When you do G1 X-365 Y-255 F3000 S1, movement will stop when an end stop switch is triggered. That is to say, either the X or the Y end stop switch but not both. So if for example the Y axis switch triggered but X was still 50 mm away from the end stop, then when you do the next line G1 X5 Y5 F6000 Y will move to plus 5 but X will move to 50 + 5. Then your fine homing line G1 X-365 Y-255 F360 S1 will move back until one or other switches trigger again so Y will go to zero but X will still be 50 and will therefore never be homed. You can tell on the web interface as the axis buttons only turn blue when homing has been successful. So you need individual G1 S1 moves for each axis. e.g after G1 X-365 Y-255 F3000 S1 you then need G1 X-365 F3000 S1 and G1 Y-255 F3000 S1 and the same for your fine homing (or just home each axis in turn).
HTHIan, thanks for trying to be helpful, however his homeall.g file is OK (I think) for a Cartesian printer. On a Cartesian printer, when an endstop switch is triggered, only that axis is stopped. CoreXY is different because of the shared motors.
-
@1d1:
So, today's results so far:
When homing X; Z lift, carriage moves appx. 10 mm in the correct direction, z lower to original position.It should be lifting Z by 5mm, not 10mm. Are you sure that your Z steps/mm is correct in the M92 command? You currently have it set to 4000. What pitch of leadscrew are you using for Z, is there any gearing between the motor and the screw, and are you using a 0.9 or 1.8 deg motor?
See later in my reply for correcting your endstop configuration.
@1d1:
Y Home: Z lift, carriage moves appx. 10 mm in correct direction, Z lowers
Evidently the same issues as for X (too much ZS movement, incorrect Y movement).
@1d1:
Z Home: Z lift appx. 10 mm
Is that all it does? Please post your homez.g file.
@1d1:
Homeall: X and Y the same as above, then calls for Z bed compensation adjust with pop up window
The popup window means that you have homeall.g configured to use a Z probe, but you don't have a Z probe configured. See https://duet3d.com/wiki/Configuring_RepRapFirmware_for_a_Cartesian_printer#Homing_Z.
@1d1:
The endstop LEDs are all on and will trigger, turn off, when activated. Set at active high. BUT when I look at machine properties in Settings, they are all triggered Yes and when I activate, they all register as No. Perhaps I have them wired incorrectly still?
The config.g file you published earlier has this:
M574 X1 Y1 Z1 S0 ; Set active high endstops
but S0 sets active low endstops. Change it to S1.
-
Besides, the end stops have yet to be reached by the carriages at all so even if one did the trick for all, I'm not to that point yet.
-
Ian, thanks for trying to be helpful, however his homeall.g file is OK (I think) for a Cartesian printer. On a Cartesian printer, when an endstop switch is triggered, only that axis is stopped. CoreXY is different because of the shared motors.
Ah OK. Apologies then. I'm too used to my CoreXY and assumed that Cartesian kinematics would work the same way.
Just to be clear, on a Cartesian the command G1 X-nn Y-nn S1 will move both axes until one end stop is triggered but then continue with the other axis until it's own end stop is triggered, yes? -
Vast improvements and really almost there. Rewrote the home files a bit and the homeall file. Now, the motors keep running in jerky motions after hitting the end stops so I am going to reduce the timeout idle to see if this does the job. After that, I'm hoping to have it sorted!
In 574 above I had added a "1" to each drive to make it active high. Didn't realize I needed instead to identify the drives as X1 Y2 etc and then making them active high by having it be S1 instead of S0. It's been a pain but I'm learning a lot! -
Ian, thanks for trying to be helpful, however his homeall.g file is OK (I think) for a Cartesian printer. On a Cartesian printer, when an endstop switch is triggered, only that axis is stopped. CoreXY is different because of the shared motors.
Ah OK. Apologies then. I'm too used to my CoreXY and assumed that Cartesian kinematics would work the same way.
Just to be clear, on a Cartesian the command G1 X-nn Y-nn S1 will move both axes until one end stop is triggered but then continue with the other axis until it's own end stop is triggered, yes?That's correct.
-
@1d1:
Vast improvements and really almost there. Rewrote the home files a bit and the homeall file. Now, the motors keep running in jerky motions after hitting the end stops so I am going to reduce the timeout idle to see if this does the job. After that, I'm hoping to have it sorted!
In 574 above I had added a "1" to each drive to make it active high. Didn't realize I needed instead to identify the drives as X1 Y2 etc and then making them active high by having it be S1 instead of S0. It's been a pain but I'm learning a lot!The X, Y and Z parameters specify the location of the endstops. See https://duet3d.com/wiki/G-code#M574:_Set_endstop_configuration.
I'm not sure what you mean by "keep running in jerky motions". Can you explain, or post a video?
-
Once the carriage hits the end stop, the light on the board is triggered off, but the carriage continues to push against the end stop repeatedly until I shut it off or hit emergency stop.
-
Have you corrected your M574 command, and are your endstop switches now reading correctly in the Machine Properties page?
Please share the contents of your homing files.
-
I finally managed to sort it all out! The biggest issue was that the signifiers for axis max and min were reversed in config.g. After that, there was more to figure out with Y end stop being opposite of end of travel compared to X and Z, but it is actually all together and functioning.
Thanks to all of you who spend your time and brains to help those of us just learning this stuff!!!
