You are not logged in.

#1 2017-11-21 14:24:15

nnnn2013
Member
Registered: 2017-11-21
Posts: 13

Direct control - RAMPS Sync - Waiting for done message from RAMPS

Hi, please help me to solve this problem.

I have:
-Raspberry Pi 3
-A4988
-Led
-Nema 17
-5 inch screen
-endstop

Wired them all according schematic from this site.
1. When i test Projector calibration, screen and shutter works. The test images appear on the screen, shutter (LED) also works
2. Step motor is also working
3. End stop is also working
4. When i send STL file to print:
   4.1. First layer appears on the screen. LED goes on.
   4.2. Then on the secon layer "RAMPS Sync - Waiting for done message from RAMPS" and it is waiting command from RAMPS.
But there is no RAMPS, i am doing direct control.
What is the problem here ?
Thanks.
Here is the log

Info    1    2017-11-21 13:50:32.919633    RAMPS Sync    Waiting for done message from RAMPS
Debug    1    2017-11-21 13:50:29.912107    Shutter    Shutter Close
Debug    1    2017-11-21 13:50:29.91174    Image    Clear screen
Debug    1    2017-11-21 13:49:39.860525    Printing    Curing for 49.999998976 seconds
Warning    1    2017-11-21 13:49:39.656643    Image    Display layer public/plates/1/1.png
Debug    1    2017-11-21 13:49:27.65625    Shutter    Shutter Open
Notice    1    2017-11-21 13:49:27.655941    Gcode    Position set to 0.04
Info    1    2017-11-21 13:49:27.655736    RAMPS Sync    Ready for the next RAMPS movement
Info    1    2017-11-21 13:49:27.655672    RAMPS Sync    Waiting for done message from RAMPS
Debug    1    2017-11-21 13:49:27.654915    Pulsing    Movement Finished Pulse 2667 / 2667 ; Height 312 / 2979 ; Time 21.789695529
Debug    1    2017-11-21 13:49:05.864994    Pulsing    Moving Down 2667 pulses 5.000625 mm
Debug    1    2017-11-21 13:49:05.864829    Pulsing    Movement Finished Pulse 312 / 312 ; Height 0 / 312 ; Time 0.571915698
Debug    1    2017-11-21 13:49:05.292628    Pulsing    Moving Down 312 pulses 0.585 mm
Debug    1    2017-11-21 13:49:05.292435    Pulsing    Moving to Layer
Debug    1    2017-11-21 13:49:05.292301    Shutter    Shutter Close
Debug    1    2017-11-21 13:49:05.292231    Image    Clear screen
Error    1    2017-11-21 13:49:05.292149    Gcode    External Call Problem exit status 1 TOKEN is unset or empty: Did you create /etc/pushover.conf or specify -T on the command line?
Debug    1    2017-11-21 13:48:36.658411    Pulsing    Movement Finished Pulse 6137 / 100000000 ; Height -2646 / 0 ; Time 5.928158951
Warning    1    2017-11-21 13:48:36.658332    Pulsing    Limit touched position reset
Notice    1    2017-11-21 13:48:36.658236    GPIO    Limit has been touched
Debug    1    2017-11-21 13:48:34.896196    WiFi    Connected to NETIS

Offline

#2 2017-11-22 06:30:50

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

Re: Direct control - RAMPS Sync - Waiting for done message from RAMPS

Remove any [[WaitForDoneMessage]] keyword from gcode boxes on both profile and setup pages.

Offline

#3 2017-11-22 09:06:32

nnnn2013
Member
Registered: 2017-11-21
Posts: 13

Re: Direct control - RAMPS Sync - Waiting for done message from RAMPS

Thanks Shahin !
I removed "Waiting for done message from RAMPS" from default resin profile and it worked.

Offline

#4 2018-03-01 00:30:03

Kaveh
Member
Registered: 2018-01-23
Posts: 23

Re: Direct control - RAMPS Sync - Waiting for done message from RAMPS

hi shahin
How to sync nanoDLP and Grbl together. [Waitfordone] not work and [delay s"] is not useful for different speeds.
thanks alot

Offline

#5 2018-03-01 06:45:43

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

Re: Direct control - RAMPS Sync - Waiting for done message from RAMPS

Use latest version of marlin as it already supports nanodlp WaitForDone on the official release.

Offline

Board footer

Powered by FluxBB