DUEX 5 V0.8 TO DUEX 5 V0.11

paolozampini1973

@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!'

droftarts

@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, change G1 H1 Z-300 F700 to G1 H1 Z-400 F700: it must be a bigger move than the axis length. Did you change M208 recently?

Ian

droftarts

@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

paolozampini1973

@droftarts config (27).g
you correct the files please and I start as you send me

droftarts

@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

paolozampini1973

@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, change G1 H1 Z-300 F700 to G1 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

@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, change G1 H1 Z-300 F700 to G1 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

@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, change G1 H1 Z-300 F700 to G1 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

SIam

@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

@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)

paolozampini1973

@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 why

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 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.pdf

how can I return the courtesy that you have helped me ?

droftarts

@paolozampini1973

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

paolozampini1973

This post is deleted!

paolozampini1973

@droftarts said in DUEX 5 V0.8 TO DUEX 5 V0.11:

@paolozampini1973

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

paolozampini1973

@droftarts said in DUEX 5 V0.8 TO DUEX 5 V0.11:

@paolozampini1973

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

@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 forwards

What is the maximum pulse value that is firmware you can control ?

droftarts

@paolozampini1973 said in DUEX 5 V0.8 TO DUEX 5 V0.11:

@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 forwards

What is the maximum pulse value that is firmware you can control ?

You shouldn't need to set the timing that high. I suggested T3:3:6:6. Did that not work? If you have to use such long pulses, I would guess it's because of running at 3.3V signalling, rather than 5V. Your drivers said they could do T2.5:2.5:5:5, so 5µs for a full step pulse, so 1,000,000 / 5 = 200,000 steps per second. With your setting, a full step pulse is 28µs, so you are limited to 1,000,000 / 28 = 35,700 steps per second. This limits you to 35700 / 200 (your steps per mm) = 178.5mm/s. The Duet 2 can realistically do around 100,000 steps per second, so getting the timing down to T5:5:10:10 would definitely help go faster.

For the Z endstop, use M574 Z1 S1 P"!zstop+!e1stop". Using Z2 works as well, because it is followed by G92 Z0. If you remove this and use Z2, homing Z will cause Z to be set to the axis maximum, of 320. So use Z1.

One more thing. In your homeall.g, each G1 command is followed by S1 or S2. These are unnecessary, and potentially confusing, as they are used to set laser power in RRF 3! The H1 and H2 parameters are correct. See https://docs.duet3d.com/User_manual/Reference/Gcodes/G1
e.g.:

G91                     ; relative positioning
G1 H2 Z15 F1500          ; lift Z relative to current position
G1 H1 X-500 Y-500 F1500 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X5 Y5 F1500       ; go back a few mm
G1 H1 X-500 Y-500 F360  ; move slowly to X and Y axis endstops once more (second pass)
G1 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)

Ian

paolozampini1973

@droftarts said in DUEX 5 V0.8 TO DUEX 5 V0.11:

T3:3:6:6 Yes I remember you told me this settings however I lose the pace

T2.5:2.5:5:5 Yes I remember you told me this settings however I lose the pace I also tried to put them 74hc14 but it is much worse from 5 times I had to put it to 4 times even 3.8V to make it work it looks very strange but it is So I finally unplugged it

paolozampini1973

@droftarts however it is also true that the mass to be moved is a lot on purpose. I sent you to show you here nema 23 they have double the torque resistance and half and the girl is shorter in fact I was waiting for your consideration and your opinion on those engines because with nema17 it goes well

droftarts

@paolozampini1973 Sorry, I don't know if NEMA 23 will run better than NEMA17 with your external drivers on your machine. You will just have to test them.

Ian