You are not logged in.

#1 2017-04-03 08:21:02

Gatto
Member
Registered: 2017-02-14
Posts: 75

Curing time calculation win64

"Curing time" timer starts when?

Actually If I set 9 secs I have 6 secs from shutter open to close, why?

Offline

#2 2017-04-03 19:24:23

Shahin
Administrator
Registered: 2016-02-17
Posts: 3,541

Re: Curing time calculation win64

Are you sure you do not have any other option effecting cure time? such as dynamic cure?

Offline

#3 2017-04-04 06:10:50

Gatto
Member
Registered: 2017-02-14
Posts: 75

Re: Curing time calculation win64

Shahin wrote:

such as dynamic cure?

Sure, every field is empty.

Offline

#4 2017-04-04 12:34:15

Shahin
Administrator
Registered: 2016-02-17
Posts: 3,541

Re: Curing time calculation win64

I could not reproduce the issue please, share the debug file.

Offline

#5 2017-04-06 07:42:58

Gatto
Member
Registered: 2017-02-14
Posts: 75

Re: Curing time calculation win64

https://we.tl/ZaSbc9q3fx

set to 6 seconds, shutter is open for 3 seconds

Offline

#6 2017-04-06 08:35:08

Shahin
Administrator
Registered: 2016-02-17
Posts: 3,541

Re: Curing time calculation win64

I got it wrong, image being displayed for 8seconds as intended but shutter opens only for 6 seconds, is it right?

If I understand the issue correctly this time, the problem is some servo motors could require relatively long time to open and close which eat into cure time.
You have two options,
1. Move shutter codes into main gcode box (before and after layer) and send open command before movement started or split movement in two parts and send shutter open in the middle.
2. Get faster servo
3. In my experience small servo motors are not suitable for 3d printer workload so they will burn sooner or later, so it is much more reliable just to open them once for the whole printing session.

Offline

#7 2017-04-06 08:50:48

Gatto
Member
Registered: 2017-02-14
Posts: 75

Re: Curing time calculation win64

Shahin wrote:

I got it wrong, image being displayed for 8seconds as intended but shutter opens only for 6 seconds, is it right?

If I understand the issue correctly this time, the problem is some servo motors could require relatively long time to open and close which eat into cure time.
You have two options,
1. Move shutter codes into main gcode box (before and after layer) and send open command before movement started or split movement in two parts and send shutter open in the middle.
2. Get faster servo
3. In my experience small servo motors are not suitable for 3d printer workload so they will burn sooner or later, so it is much more reliable just to open them once for the whole printing session.

No servo motor used, M106 just set a PWM port, time for operation is 20ms ...

Offline

#8 2017-04-06 20:05:53

Shahin
Administrator
Registered: 2016-02-17
Posts: 3,541

Re: Curing time calculation win64

Based on your log file.

		2017-04-06 00:38:20.588443 Transfering Data ;M106 S38 ; 20W↵;M106 S50 ; 30W↵;M106 S68 ; 50w↵;M106 S100 ; 66w↵;M106 S130 ; 80w↵M106 S255↵↵
		2017-04-06 00:38:20.599967 Received Data From RAMPS: ok 0↵
		2017-04-06 00:38:20.600962 Done message from RAMPS has been received
		2017-04-06 00:38:20.604466 Received Data From RAMPS: Z_move_comp↵
		2017-04-06 00:38:20.607492 Received Data From RAMPS: Fanspeed:255↵
		2017-04-06 00:38:20.787659 Display layer public/plates/3/50.png
		2017-04-06 00:38:20.788158 Curing for 8 seconds
		2017-04-06 00:38:28.838881 Shutter Close
		2017-04-06 00:38:28.838881 Clear screen
		2017-04-06 00:38:28.839894 Transfering Data M106 S0↵↵

On 38:20.58 shutter open gcode sent to RAMPS.
On 38:20.78 start displaying layer.
On 38:28.83 shutter closed.

I believe NanoDLP sent gcodes to RAMPS on exactly correct time. If your servo is fine, you need to investigate issue on RAMPS side maybe one of these commands cause delay on shutter on RAMPS side.

Offline

Board footer

Powered by FluxBB