Force stop

Belal · 2018-02-22 16:58:45

Hi,

I realized that the only difference between stop and force stop is that force stop doesn't wait for the curing to finish.

But it still do the after layer Gcode, which I found is a little bit doesn't make sense.

So my request is can force stop jump to the stop Gcode immediately without waiting to finish the after layer Gcode?

Shahin · 2018-02-22 20:53:06

It is not possible to stop GCode as they already sent to RAMPS side. If terminate command get supported by RAMPS firmwares maybe we can interrupt it and terminate print.

Belal · 2018-02-22 22:05:21

Even if I'm using waitForGpioLow after each command?
I think in this case the Gcode didn't sent as a block

Also I usually use the reset pin to reset the command is currently be executed but nano dlp sends the reset of Gcode command by command after each waitForGpioLow is done

Last edited by Belal (2018-02-22 22:09:49)

Shahin · 2018-02-23 10:55:07

The waitForGpioLow is separate mechanism for synchronization.
Only part of gcodes being sent separately when there is action keyword on gcode box.

Belal · 2018-02-23 11:37:10

Shahin wrote:

The waitForGpioLow is separate mechanism for synchronization.
Only part of gcodes being sent separately when there is action keyword on gcode box.

Exactly, So I'm expecting that when I hit the force stop button arduino complete the line is executed only because arduino doesn't have the rest of GCode at all!

and this problem I can solve by hitting the arduino reset button, so I can terminate the line being executed now.

But the problem occurs when nano dlp keep sending the rest of Gcode Line by line after each waitForGpioLow is finished

So my question is Can nanodlp jump to the stop gcode immediately without sending the rest of Gcode?
And I will take care of the Lines has been sent already

Thanks in advance.

Shahin · 2018-02-23 16:04:36

It is possible, but I guess it could create trouble for users who expect whole gcode box executed. For example if they use mechanism to save current position on nanodlp side will lose position.
Even-though forcestop should used rarely, it is not clear if it is ideal behavior.

Belal · 2018-02-23 16:27:45

I understand you, and you're right, but force stop is only used in emergency situations, Situations are corrupting my print already and I'm trying to not corrupt my vat also.
For example, it didn't wait for the curing time to finish, so when I'm using it I use it while I know that I can't resume.

Example of emergency situations is:
setting a very high cure time by mistake (this is a situation force stop is already can help with)
put wrong values in gcode (and this happing a lot)
or combination of both which is can cause a sticking which is can corrupt my vat also

So I need another way instead of cut the power off completely

Last edited by Belal (2018-02-23 16:41:13)

Shahin · 2018-02-23 19:03:26

Please, check the latest beta version see if it working as expected or not

Belal · 2018-02-25 09:02:59

here is what is happing
when I hit the Force stop button nanodlp stop sending the rest of after each layer Gcode, But it never jump to the stop Gcode

Shahin · 2018-02-27 04:22:34

Belal,

It does not goes through stop gcode and print stops completely? How was the previous behavior?

Belal · 2018-02-27 16:34:50

Shahin wrote:

Belal,
It does not goes through stop gcode and print stops completely? How was the previous behavior?

Hi Shahin,

The previous behavior was that force stop is terminating the layer be displayed immediately (before the cure time is finish) but it still goes through all the after printing gcode and all stop Gcode, even if I was using waitForGPIOLow after each command I send.

The current behavior is that if there is a layer currently displayed the layer complete its time (not as same as the previous version) but it didn't do the after print Gcode at all and never go through the stop Gcode

If there was no layer is currently displayed and command of after layer Gcode is currently in progress nanodlp doesn't send the rest of commands. and also skip the stop Gcode.

To be honest, I think that this behavior is the best So I can freeze the machine immediately and fix whatever is happened.

Of course, we need to terminate the layer currently displayed even if the cure time wasn't finished yet like the previous behavior

elshad66 · 2018-02-27 19:04:30

if something went wrong
I press stop and OK at the moment when the image goes out and the platform goes up

the platform goes up and down and the print stops
so works in Pi and Win variants

I'm using pi + mega 2560 + ramps 1,4

Last edited by elshad66 (2018-02-27 19:08:40)

Shahin · 2018-03-31 16:10:36

Try latest beta, it should prevent gcode being sent out after force stop pressed.

nanoDLP

#1 2018-02-22 16:58:45

Force stop

#2 2018-02-22 20:53:06

Re: Force stop

#3 2018-02-22 22:05:21

Re: Force stop

#4 2018-02-23 10:55:07

Re: Force stop

#5 2018-02-23 11:37:10

Re: Force stop

#6 2018-02-23 16:04:36

Re: Force stop

#7 2018-02-23 16:27:45

Re: Force stop

#8 2018-02-23 19:03:26

Re: Force stop

#9 2018-02-25 09:02:59

Re: Force stop

#10 2018-02-27 04:22:34

Re: Force stop

#11 2018-02-27 16:34:50

Re: Force stop

#12 2018-02-27 19:04:30

Re: Force stop

#13 2018-03-31 16:10:36

Re: Force stop

Board footer