Simultaneous Tools working

Dougal1957

Thanks David for the confirmation 2-3 seconds is considerably faster than a reboot.

Doug

p.s. see you at TCT.

CJ.BRAVO

@dougal1957

if I enter in the console I still need the g-code to complete the move.

Because it is a prototype extruder I want the ability to change settings on the fly and not have to wait for the last g-code command to finish it's move. that's why I hit the emergency every time. of course I can reduce feed amount that shortens the move time but it distrusts the flow.

T3P3Tony

@CJ-BRAVO how about sending a move that was segmented into lots of short moves (1000 lines of G1 E1 for example). Then changes to feed rate or extrusion multiplier would be quick to come into effect.

deckingman

@t3p3tony said in Simultaneous Tools working:

@CJ-BRAVO how about sending a move that was segmented into lots of short moves (1000 lines of G1 E1 for example). Then changes to feed rate or extrusion multiplier would be quick to come into effect.

- or even 100 lines of 10mm would do the job I'd have thought.

CJ.BRAVO

interesting but I lost you..

How should I do it?

in the command console, a g-code file or a macro?

would I be able to change the temperature at the same time ?

deckingman

@cj-bravo said in Simultaneous Tools working:

interesting but I lost you..

How should I do it?

in the command console, a g-code file or a macro?

would I be able to change the temperature at the same time ?

Any test editor such as notepad++. You just want the line G1 E1 (to extrude 1mm of filament). Then copy and paste that onto the next line. Then copy and paste those 2 lines to give you 4 and keep repeating it. If you want, use G1 E10 so that you only have to copy and paste 100 lines to get 1000 mm but you'll only be able to interrupt extrusion every 10mm.

So you end up with
G1 E10
G1 E10
G1 E10
G1 E10
etc.

Save that as a text file then rename it so that it is "filename".g rather than "filename".txt and you can run it as a gcode file. Or simply delete the extension and you can run it as a macro.

Edit. So instead of one long 1000 mm move, you end with multiple shorter moves that are carried out consecutively. When that is running, you can enter any gcode command "on the fly" and it will get executed in between those shorter moves. So if you can be arsed to make 1,000 off 1mm moves, it will respond fast. But if you can't and only have 100 moves of 10mm, you'll have to wait a bit longer before any command you enter will get executed. In a nutshell, you can't easily interrupt a move that has already started, but you can easily do something in between moves.

CJ.BRAVO

@deckingman

Hey, it's been a while..

So I've got an external trigger connected that running plenty of G1 E1 lines and the idea is ti be able to stop it any time I want. I triggered the code but the M0 / M1 ain't doing anything.... I remember I was able to to do it a while back with the same lines in the macros but not sure why its not working at the moment.

thoughts?

to recap: i'm looking to run an extruder for an unlimited time with the ability to stop it when ever an external trigger is hit.

thanks!

dc42

Would a long extruder move terminated early by triggering an endstop switch meet your requirement?

CJ.BRAVO

@dc42

yes. that can work... how would I pull such a move?

deckingman

@CJ-BRAVO said in Simultaneous Tools working:

@deckingman

Hey, it's been a while..

So I've got an external trigger connected that running plenty of G1 E1 lines and the idea is ti be able to stop it any time I want. I triggered the code but the M0 / M1 ain't doing anything.... I remember I was able to to do it a while back with the same lines in the macros but not sure why its not working at the moment.

thoughts?

to recap: i'm looking to run an extruder for an unlimited time with the ability to stop it when ever an external trigger is hit.

thanks!

I think what David is suggesting would be a firmware feature that would do what you originally asked for. The idea of using a number of shorter move segments was just an idea to get around the existing limitation that a trigger will wait for the current move to finish.

If David is suggesting a firmware modification, that might take a while because he has a lot of other stuff to do. In the mean time it might be best to try and get the segmented move approach working. So how are you initiating the M581 trigger and what are the lines that you have in the associated macro? A good way to see if the macro is being run is to use M291 at the beginnning to print a message.

fma

Is it not possible to create a dummy U axis, with the same accel/speed than the extruder axis, and use this G-Code:

G1 U1000 E1000

I think the U axis can be stopped by triggering an endstop (wired on E0?). Am I wrong?

T3P3Tony

@fma you can use an endstop and then G1 H1 so it acts like a homing move. If its easier to use an actual extruder axis in your application then the best bet is to send lots of very short moves and we have been saying.

fma

If the U axis hits the enstop, does the move:

G1 U1000 E1000

also stops E motor?