DUEX 5 V0.8 TO DUEX 5 V0.11
-
@droftarts said in DUEX 5 V0.8 TO DUEX 5 V0.11:
@paolozampini1973 said in DUEX 5 V0.8 TO DUEX 5 V0.11:
M574 Z2 S1 P"!zstop" ?
M574 Z1 S1 P"e1stop" ?NO. Z parameter in M574 sets where the endstop is physically, on the axis. High or low. They both should be Z1. Listing them separately is incorrect, too. You also seem to have lost the inversion on the e1stop. It should be:
M574 Z1 S1 P"!zstop+!e1stop"so it doesn't do the inversion it goes towards the plus and it doesn't come back towards the minus but the thing I don't understand why it doesn't work anymore has always worked even after we put our hands on it
-
@paolozampini1973 What does M119 report when:
No switch is pressed
Z1 endstop is pressed
Z2 endstop is pressed
Both endstops are pressed
?And post the endstop configuration you are using when testing.
Ian
-
@droftarts So the problem is not the speech of switches that have to close and open because practically when you give it back home it goes up 15 mm and then it has to do the inversion towards minus putting the separated the inversion towards minus does it however I repeat not get to the switches I have now done a try to take it myself manually the switches work both tested they work it is not a problem of the switches it is a problem towards the plus and then return towards the minus towards the Switch clearly if only one axis works only l the axis is rightly placed sideways
-
@paolozampini1973 Please just do the test and report, using
M574 Z1 S1 P"!zstop+!e1stop"for configuration. It won't work with two separate M574 commands.Ian
-
@droftarts said in DUEX 5 V0.8 TO DUEX 5 V0.11:
@paolozampini1973 Please just do the test and report, using
M574 Z1 S1 P"!zstop+!e1stop"for configuration. It won't work with two separate M574 commands.Ian
25/3/2022, 17:34:11 M574 Z2 S1 P"!zstop!+!e1stop"
Error: M574: Unknown pin name 'zstop!' -
@paolozampini1973 Also, the last homeall.g does not home z; it just sets Z=0 wherever Z is.
G91 ; relative positioning G1 S2 H2 Z15 F1500 ; lift Z relative to current position G1 S1 H1 X-500 Y-500 F1500 ; move quickly to X and Y axis endstops and stop there (first pass) G1 S2 H2 X5 Y5 F1500 ; go back a few mm G1 S1 H1 X-500 Y-500 F360 ; move slowly to X and Y axis endstops once more (second pass) G1 S1 H1 Z-300 F360 ; move Z down stopping at the endstop G90 ; absolute positioning G92 Z0 ; set Z position to axis minimum (you may want to adjust this) homez.g does a move towards home, then sets Z=0 when the endstops are triggered.
G91 ; relative positioning G1 H2 Z15 F700 ; lift Z relative to current position G1 H1 Z-300 F700 ; move Z down until the endstop is triggered G92 Z0 ; set Z position to axis minimum (you may want to adjust this) However, your M208 is
M208 X500 Y500 Z320 S0, so Z axis is longer than the Z-300 move. In homez.g, changeG1 H1 Z-300 F700toG1 H1 Z-400 F700: it must be a bigger move than the axis length. Did you change M208 recently?Ian
-
@paolozampini1973 said in DUEX 5 V0.8 TO DUEX 5 V0.11:
25/3/2022, 17:34:11 M574 Z2 S1 P"!zstop!+!e1stop"
Error: M574: Unknown pin name 'zstop!'You have an extra ! in there.
AND CHANGE Z2 to Z1
Ian
-
@droftarts config (27).g
you correct the files please and I start as you send me -
@paolozampini1973 Now you are missing the +
USE THIS!
M574 Z1 S1 P"!zstop+!e1stop"Anyway, I have to go now. See my earlier post about change homez.g.
Ian
-
@droftarts said in DUEX 5 V0.8 TO DUEX 5 V0.11:
@paolozampini1973 Also, the last homeall.g does not home z; it just sets Z=0 wherever Z is.
G91 ; relative positioning G1 S2 H2 Z15 F1500 ; lift Z relative to current position G1 S1 H1 X-500 Y-500 F1500 ; move quickly to X and Y axis endstops and stop there (first pass) G1 S2 H2 X5 Y5 F1500 ; go back a few mm G1 S1 H1 X-500 Y-500 F360 ; move slowly to X and Y axis endstops once more (second pass) G1 S1 H1 Z-300 F360 ; move Z down stopping at the endstop G90 ; absolute positioning G92 Z0 ; set Z position to axis minimum (you may want to adjust this) homez.g does a move towards home, then sets Z=0 when the endstops are triggered.
G91 ; relative positioning G1 H2 Z15 F700 ; lift Z relative to current position G1 H1 Z-300 F700 ; move Z down until the endstop is triggered G92 Z0 ; set Z position to axis minimum (you may want to adjust this) However, your M208 is
M208 X500 Y500 Z320 S0, so Z axis is longer than the Z-300 move. In homez.g, changeG1 H1 Z-300 F700toG1 H1 Z-400 F700: it must be a bigger move than the axis length. Did you change M208 recently?Ian
No I haven't changed it recently this car was so configured for months this is what I was always doing Solving the problem of loss of pace and it seems that you can see that step has been resolved but I still have to try it well
-
@paolozampini1973 said in DUEX 5 V0.8 TO DUEX 5 V0.11:
@droftarts said in DUEX 5 V0.8 TO DUEX 5 V0.11:
@paolozampini1973 Also, the last homeall.g does not home z; it just sets Z=0 wherever Z is.
G91 ; relative positioning G1 S2 H2 Z15 F1500 ; lift Z relative to current position G1 S1 H1 X-500 Y-500 F1500 ; move quickly to X and Y axis endstops and stop there (first pass) G1 S2 H2 X5 Y5 F1500 ; go back a few mm G1 S1 H1 X-500 Y-500 F360 ; move slowly to X and Y axis endstops once more (second pass) G1 S1 H1 Z-300 F360 ; move Z down stopping at the endstop G90 ; absolute positioning G92 Z0 ; set Z position to axis minimum (you may want to adjust this) homez.g does a move towards home, then sets Z=0 when the endstops are triggered.
G91 ; relative positioning G1 H2 Z15 F700 ; lift Z relative to current position G1 H1 Z-300 F700 ; move Z down until the endstop is triggered G92 Z0 ; set Z position to axis minimum (you may want to adjust this) However, your M208 is
M208 X500 Y500 Z320 S0, so Z axis is longer than the Z-300 move. In homez.g, changeG1 H1 Z-300 F700toG1 H1 Z-400 F700: it must be a bigger move than the axis length. Did you change M208 recently?Ian
No I haven't changed it recently this car was so configured for months this is what I was always doing Solving the problem of loss of pace and it seems that you can see that step has been resolved but I still have to try it well
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Wed May 19 2021 14:46:37 GMT+0200 (Ora legale dell’Europa centrale)
G91 ; relative positioning
G1 S2 H2 Z15 F1500 ; lift Z relative to current position
G1 S1 H1 X-500 Y-500 F1500 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 S2 H2 X5 Y5 F1500 ; go back a few mm
G1 S1 H1 X-500 Y-500 F360 ; move slowly to X and Y axis endstops once more (second pass)
G1 S1 H1 Z-300 F360 ; move Z down stopping at the endstop
G90 ; absolute positioning
G92 Z=0 ; set Z position to axis minimum (you may want to adjust this); Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning -
@paolozampini1973 said in DUEX 5 V0.8 TO DUEX 5 V0.11:
@droftarts said in DUEX 5 V0.8 TO DUEX 5 V0.11:
@paolozampini1973 Also, the last homeall.g does not home z; it just sets Z=0 wherever Z is.
G91 ; relative positioning G1 S2 H2 Z15 F1500 ; lift Z relative to current position G1 S1 H1 X-500 Y-500 F1500 ; move quickly to X and Y axis endstops and stop there (first pass) G1 S2 H2 X5 Y5 F1500 ; go back a few mm G1 S1 H1 X-500 Y-500 F360 ; move slowly to X and Y axis endstops once more (second pass) G1 S1 H1 Z-300 F360 ; move Z down stopping at the endstop G90 ; absolute positioning G92 Z0 ; set Z position to axis minimum (you may want to adjust this) homez.g does a move towards home, then sets Z=0 when the endstops are triggered.
G91 ; relative positioning G1 H2 Z15 F700 ; lift Z relative to current position G1 H1 Z-300 F700 ; move Z down until the endstop is triggered G92 Z0 ; set Z position to axis minimum (you may want to adjust this) However, your M208 is
M208 X500 Y500 Z320 S0, so Z axis is longer than the Z-300 move. In homez.g, changeG1 H1 Z-300 F700toG1 H1 Z-400 F700: it must be a bigger move than the axis length. Did you change M208 recently?Ian
No I haven't changed it recently this car was so configured for months this is what I was always doing Solving the problem of loss of pace and it seems that you can see that step has been resolved but I still have to try it well
i did as you told me i put Z = 0 this is the result
-
@paolozampini1973 and what have you done ? home z or home all ? If it was home z then you have to home x/y first.
-
@siam oh I have overseen you was trying to home the z axis first before you can do this home y/x ( g28 x / g28 y)
-
@droftarts
G92 Z0 good
G92 Z=0 no good
M574 Z1 S1 P"!zstop+!e1stop" it works there is no difference I don't understand why
M574 Z2 S1 P"!zstop+!e1stop" it works there is no difference I don't understand whyM569 P7 S0 R1 T14:14:26:26 ; E4 X physical drive 7 goes forwards
M569 P8 S1 R1 T14:14:26:26 ; E5 Y physical drive 8 goes forwards
with these messages it seems that he no longer loses steps tomorrow I change from nema 17 to nema 23
tell me your thoughts thanks
17HS19-2004S1.pdf 23HS22-2804S.pdfhow can I return the courtesy that you have helped me ?
-
G92 Z=0 no good
That’s not a GCode command, and not one I wrote.
how can I return the courtesy that you have helped me ?
I think you mentioned $10,000 at the beginning???!!!
Ian
-
This post is deleted! -
@droftarts said in DUEX 5 V0.8 TO DUEX 5 V0.11:
G92 Z=0 no good
That’s not a GCode command, and not one I wrote.
how can I return the courtesy that you have helped me ?
I think you mentioned $10,000 at the beginning???!!!
Ian
and how much I have spent so far to carry out this project that I have not finished yet I hope to finish by next month at the latest
-
@droftarts said in DUEX 5 V0.8 TO DUEX 5 V0.11:
G92 Z=0 no good
That’s not a GCode command, and not one I wrote.
how can I return the courtesy that you have helped me ?
I think you mentioned $10,000 at the beginning???!!!
Ian
Tomorrow I will do the replacement of the motors You have seen the configuration of my pulse config
-
@paolozampini1973 said in DUEX 5 V0.8 TO DUEX 5 V0.11:
M569 P7 S0 R1 T14:14:26:26 ; E4 X physical drive 7 goes forwards
M569 P8 S1 R1 T14:14:26:26 ; E5 Y physical drive 8 goes forwardsWhat is the maximum pulse value that is firmware you can control ?