New firmware 1.09i-dc42

Quote
dc42
Are you sure it is the G28 on the slicer start gcode that is slow? I seem to remember that the original start gcode in the slic3r profile provided by RRP contained a G1 command without a feed rate in it, and this caused it to execute very slowly sometimes depending on what you did previously.

Yes, I'm sure. Its only G28 Z0.

Have a look:

; perimeters extrusion width = 0.50mm
; infill extrusion width = 0.87mm
; solid infill extrusion width = 0.85mm
; top infill extrusion width = 0.85mm

G21 ; set units to millimeters
M107
M190 S65 ; wait for bed temperature to be reached
M104 S200 ; set temperature
G28 Z0
M83
M109 S200 ; wait for temperature to be reached
G90 ; use absolute coordinates
M83 ; use relative distances for extrusion
G1 F3600.000 E-4.00000
G1 Z0.360 F15000.000
G1 X61.789 Y61.278 F15000.000
...

Or is something else wrong ?

I think i had same issue but i dont really remember what i did. Was medeling a with it for a while but i did something in the homing files

Homez:
G91
G1 Z5 F2000
G90
G1 X100 Y100
G30
G1 Z0 F200

I think its F2000 in the G1 Z5

And home all:
; Ormerod 2 homeall file for use with dc42 Duet firmware
; Adjust the bed upper and lower limits in config.g (M208 commands) to get the correct homing positions
G91
G1 Z5 F2000
G1 X-240 Y-240 F2000 S1
G1 X4 Y4 F1200
G1 X-10 Y-10 S1
G90
; Adjust the XY coordinates in the following to place the IR sensor over a suitable spot
; If you are using a dc42 IR sensor then you can change the coordinates to be near the centre of the bed
G1 X100 Y104 F2000
G30
; This file leaves the head at the zprobe trigger height so that you can slip a piece of paper under it and then do G0 Z0 to check the height.
; If you prefer to send the printer to X0Y0Z0, un-comment the following lines
;G1 X0 Y0 F5000
;G1 Z0

Hmm, I haven't changed the homing files but I'll have a deeper look in my homing files.

If i press the 'Home ALL' in the web interface it uses the homing files or not ?
So I dont understand why this is fast and only by starting a print the moving in x/y to the home position is extremly slow ?

You are using G28 Z0 in your start gcode, so check your homez.g file. Chances are it has a G1 X Y command with no F parameter in it.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

Quote
dc42
You are using G28 Z0 in your start gcode, so check your homez.g file. Chances are it has a G1 X Y command with no F parameter in it.

The Homing in WebInterface doesn't use the homez.g file ?
OK, I'll check this evening and let you know.

The homing buttons in the web interface do use the homing files. However, if you have a missing F parameter in homez.g then the movement speed will.depend on what commands have been executed previously. Also if you press the Home All button then it runs homeall.g and not homez.g.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

Quote
dc42
The homing buttons in the web interface do use the homing files. However, if you have a missing F parameter in homez.g then the movement speed will.depend on what commands have been executed previously. Also if you press the Home All button then it runs homeall.g and not homez.g.

I've testet, Homing all via Web-Interface, Bed compensation via Web-Interface.
After that, I do G28 Z0 yeah, thats ist, it is slow.

Yes, you are right !
Thats it and now I finally think I understand what's going on.

The homez.g I'm using is the one you deliver with the firmware for ormerod2, it looks:

G91
G1 Z5 F200
G90
G1 X45 Y0
G30
G1 Z0 F200

So if I'm right, the G1 X45 Y0 uses the Speed F200 and this is really slow...
If I change it to G1 X45 Y0 F2000 it will be fast, or not (At the moment I can't test it) ?

Thanks a lot for all your work and your patience to explaine !

Quote
Alex74

Quote
dc42
The homing buttons in the web interface do use the homing files. However, if you have a missing F parameter in homez.g then the movement speed will.depend on what commands have been executed previously. Also if you press the Home All button then it runs homeall.g and not homez.g.

I've testet, Homing all via Web-Interface, Bed compensation via Web-Interface.
After that, I do G28 Z0 yeah, thats ist, it is slow.

Yes, you are right !
Thats it and now I finally think I understand what's going on.

The homez.g I'm using is the one you deliver with the firmware for ormerod2, it looks:

G91
G1 Z5 F200
G90
G1 X45 Y0
G30
G1 Z0 F200

So if I'm right, the G1 X45 Y0 uses the Speed F200 and this is really slow...
If I change it to G1 X45 Y0 F2000 it will be fast, or not (At the moment I can't test it) ?

Thanks a lot for all your work and your patience to explaine !

Yes, change it to G1 X45 Y0 F2000, or even F5000. I'll correct the file in my githib repo.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].