Posts made by NicoLab28

take a look to this thread

https://forum.duet3d.com/topic/9405/first-t0-in-gcode-does-not-work

For my part, I use one at a time.
It smells good the fix

in the list of macros, File management> Macros, the right button "Run macro" does not work
Left click works

My config that works, for orion precision piezo:

M558 P5 I1 R0.4 F300 X0 Y0 Z0
G31 X0 Y0 Z-0.0 P10

M300 works at home, but not everywhere.
In homez.g, I put a beep to validate something, I have the sound.
On the other hand, if I create an M300 in a macro of the macro folder and the execution of the menu file / managment / macros, I have no sound.
But if I run it from the dashboard / macros menu I get some sound.

It's my panel7 that plays the sound

Sometimes you have to add G4 Pxxxx to block time

On one of my printer, the nozzle closes continuously, and checking this box, no more worries.
He has an M83, and S3D gives him an absolute gcode

Thank you DC42
I can still read ?651 375L, she came from duet3d.com

I have 2 others in 1651 375L, another bought directly at E3D which is not yet mounted, and the one that is mounted from also duet3d.com

The problem is that of E3d, I did not plan to install it immediately. There is another test to do?

check relative extruder, you never know

Thank you gavatron and DC42,

The problem with the T-1 is that if there is a filament loaded at the beginning of the print, it will unload it.
For now, I load my tool before,.

There is a method / trick for heating the hotend without selecting a tool?
No doubt the use of
G10 Rxx Sxx
T0
in the print file

M116 at the beginning of tpost # .g (which I already do)

@dc42

Did you report the issue on this forum? if so, please point me to the thread.

https://forum.duet3d.com/topic/8242/how-to-extrude-until-trigger/26

@nicolab28 said in How to extrude until trigger:

That's what I felt, not yet looked at what it was ...
I reconnect the new

https://forum.duet3d.com/topic/8242/how-to-extrude-until-trigger/33

I had no answer

I am seriously beginning to doubt that my servo is the culprit.
I had exactly the same symptoms, and I was not offered warranty

he selects me the tool, but not completely

it's the M109 S225 T0 the offender

I will test tonight by putting a sound in the command tpost0.g
And I will raise everything, as I will see.

I just checked, and no, neither in homeall.g

No, I do not use filament management

Here are my macros, I skip the servo macros, gotopurge and wipe

tpost0.g

G1 U0
M98 Ptpost_all.g

tpost_all.g

M98 P"GotoPurge.g"

;M291 S3 R"Test" P"Press OK to start test"

M116
M98 P"SortirServo.g"
M400
M98 P"SortirFilament.g"
M400
M98 P"RentrerServo.g"
M400
G1 E60 F300
G1 E20 F300
G1 E-5 F1800
G1 E2.5 F300
M400
G4 S4
M98 P"Wipe.g"
G1 E-2 F1800

SortirFilament.g

G92 V0
M574 V2 S1
G1 V1000 F3600 S1
M581 E1 S0 T2 C0 ; activate trigger 2 on falling edge
M582 T2 ; check filament sensor to confirm loading successful
M581 T2 S-1

G92 V0
M574 W2 S1
G92 W0

; methode stall
;M574 W2 S3 ; W2 2-> end & S3 3 = motor load detection
;M913 W50; r‚duire le courant moteur … 50% pour ‚viter le meulage
;M915 W S5 F0; régler les paramêtres de protection contre le décrochage
;G1 S1 W2000 F3600; filament d'alimentation rapide dans l'extrudeuse
;M913 W100; augmente la puissance moteur

; methode capteur

G1 W2000 F8000 S1
G92 W0
G1 W60 F2400
G92 W0

;M581 E1 S0 T2 C0 ; activate trigger 2 on falling edge
;M582 T2 ; check filament sensor to confirm loading successful
;G92 W0
;G1 W-100 F3600
;M400
;G1 W-100 F600

G1 E50:50 F300

G92 W0
M400

I tested a T0 directly in the top control bar, and it works well.
As if when I start printing, he had in memory a T0 already activated. I will test tonight with a sound (M300)

@chrishamm said in Duet Web Control 2.0.0-RC5:

Are the keyboard issues related to the height map problem I mentioned?

I was not in the heightmap, but in the macro editor. But I may be open at one point the heightmap.

I also noticed that I could not edit gcode anymore in the top bar. Neither do F5, I had to close the window for it to work again. So it's probably the same problem.
I must say that the DWC window is open 24/24, by the way, when I turn off the printer, and that I turn it on, the temperature curves are extremely long, it seemed to me that it resynchronized on the last minutes.
To check that library three.js do not have this problem too.

I just retest and with a home made, it does not load the filament, it does not execute tpost0.g

I had a doubt, because DWC told me that the home was done, after stopping the print. So I redo a test by launching a homeall, without having preloaded the tool.
And the same, no execution of tpost0.g in the print file

I also noticed something, it is that after an interruption of a print, the home seems to be still valid, on the other hand, the probing seems to preserve the babystep, whereas I force it to zero in my homez.g with the code M290 R0 S0

My problem is that I can not do homeall once my tool is loaded because the filament is engaged. I would have to put a T-1, but I have not done it yet. I know it's not perfect.
But if it's loaded, it's that the homeall has been done, so it works ...
It may happen that the homeall is not done, and that the filament is not loaded, but I just checked, homeall done with tool not loaded, the T0 of the print file does not launch the tpost0.g

FYI, I do not do anything in tpre # .g

I mean by charging the filament

I would have to check, I'm not 100% sure
but it seems to me that the home is done.

here is the beginning of my print file
G90
M83
M106 S255
M140 S130
M190 S130
M104 S225 T0
M109 S225 T0
G29 S2
M98 P "GotoPurge.g"
M98 P "Wipe.g"
G28 Z; I only redo the z for the G29
G29
; process Tool0
T0

Firmware 2.02 DWC 2.0.0-RC5

When I have no tool selected before printing, and I have a T0 in the gcode. The tool is not loaded.

By cons, if I have my tool loaded before printing, and I have T1 T2, it changes filament.
This is in the case of my MMU, where I load the filament in tpost0.g