Incessant "Wait" Commands

I have an Arduino/RAMPS loaded with Repetier Firmware that I am trying to get set up with Repetier Host. However, when I connect the printer to Repetier Host in the log it just says "wait" over and over. I can send commands to the printer; however, the motors will not move and I recieve the message "Warning: Seems like we missed a ok, got a wait - continue sending." I have checked the baud rate in the firmware and host and they match. I also have the correct COM port selected. I was able to upload sketches to the Arduino so I assume that I have the right driver installed. Any idea what is happening? 

Comments

  • Firmware sends back a "wait" if it did not get any command in the last second. As you receive this the baudrate/port/driver is ok.

    What happens if you send M115? Should return some infos in log. Also if you press reset on ramps you should get a bunch of output in log.

    Can you enable logging and show the log content after a login. That log file (in work directory) contains everything and maybe a hint. You need to restart to enable it and close host to read complete log. Next start of host deletes old log file.
  • edited July 2018
    I got the same problem. The output of M115 is:  Please advice!
    23:03:03.534 : wait
    23:03:03.589 : N216 M105*34
    23:03:03.593 : ok 216
    23:03:03.597 : T:26.05 /0 B:26.51 /0 B@:0 @:0
    23:03:04.592 : wait
    23:03:05.593 : wait
    23:03:06.106 : N217 M115*34
    23:03:06.109 : ok 217
    23:03:06.126 : N218 M220 S100*106
    23:03:06.126 : N219 M221 S100*106
    23:03:06.126 : FIRMWARE_NAME:Repetier_0.91 FIRMWARE_URL:https://github.com/repetier/Repetier-Firmware/ PROTOCOL_VERSION:1.0 MACHINE_TYPE:Mendel EXTRUDER_COUNT:1 REPETIER_PROTOCOL:2
    23:03:06.126 : N220 M111 S6*103
    23:03:06.127 : N221 T0*59
    23:03:06.128 : Printed filament:10.26m Printing time:0 days 3 hours 18 min
    23:03:06.131 : ok 218
    23:03:06.131 : SpeedMultiply:100
    23:03:06.134 : ok 219
    23:03:06.134 : FlowMultiply:100
    23:03:06.134 : ok 220
    23:03:06.135 : ok 221
    23:03:06.648 : N222 M105*37
    23:03:06.653 : ok 222
    23:03:06.656 : T:25.93 /0 B:26.51 /0 B@:0 @:0
    23:03:07.651 : wait
    23:03:08.652 : wait
    23:03:09.654 : wait
    23:03:09.711 : N223 M105*36
    23:03:09.715 : ok 223
    23:03:09.717 : T:25.93 /0 B:26.51 /0 B@:0 @:0
    23:03:10.715 : wait
    23:03:11.715 : wait
    23:03:12.717 : wait


  • wait is no problem. If you are not printing it is normal to see them from time to time. Log looks absolutely perfect.
  • The wait message corrupt the Repetier-server <--> Repetier 0.91 communication.
    I can't use the usb cable to control my printer. I need to use SD card and display control and buttons!
    OK message are not interpreted and wait(4) message are accumulated.

    how do I disable this message?

    (Or maybe I have another problem with the Arduino here)?

    Please advice!
  • De select ACK  at bottom of repetier host, this will stop the 'wait' messages
  • I couldn't find the ACK. I am running repetier-host version V2.0.5. Where is it?

    What should I do in Repetier-Server?


  • edited July 2018

  • Server has also the ACK switch in commands, the only place where you can see the wait in the server.
  • Oh. You ask me to disable the ACK message from the Arduino. Well, I did and nothing changed.

    Well, I do have a communication problem with the Arduino. I can use the printer with SD card only.

    In the following log, you can see I attempt to send G28 message to the printer with no luck:
    14:41:49.026: al Reset
    14:41:49.026: Info:Brown out Reset
    14:41:51.130: SD init fail
    14:41:51.130: Response while unconnected:ok 0
    14:41:51.130: ok 0
    14:41:58.100: Warning: Seems like we missed a ok - continue sending.
    14:41:58.100: wait
    14:41:58.100: N11 M539 S1
    14:41:58.103: N13 M117 IP:10.100.100.13
    14:42:00.104: wait
    14:42:00.159: N17 M117 IP:10.100.100.13
    14:42:01.111: Warning: Missed line detected - correcting buffer usage. (6)
    14:42:01.112: ok 17
    14:42:02.110: T:28.72 /0 B:29.19 /0 B@:wait
    14:42:17.150: wait (3)
    14:42:17.153: Warning: Missed line detected - correcting buffer usage. (15)
    14:42:17.153: ok 33
    14:42:20.154: T:28.72 /0 B:29.19 wait
    14:42:29.177: Warning: Missed line detected - correcting buffer usage. (11)
    14:42:29.177: ok 45
    14:42:34.184: T:28.72 /0 B:29.19 /0 B@:wait
    14:42:43.208: wait
    14:42:43.210: Warning: Missed line detected - correcting buffer usage. (13)
    14:42:43.210: ok 59
    14:42:46.213: T:28.72 /0 B:29.19 wait
    14:42:54.256: Warning: Missed line detected - correcting buffer usage. (10)
    14:42:54.256: ok 70
    14:43:03.265: T:28.72 /0 B:29.19 /0 B@:0 @:0
    14:43:15.272: wait (12)
    14:43:16.273: Warning: Seems like we missed a ok - continue sending.
    14:43:35.292: wait (20)
    14:43:36.293: Warning: Seems like we missed a ok - continue sending.
    14:43:36.293: wait
    14:43:36.294: N108 G28
    14:43:55.312: wait (19)
    14:43:56.313: Warning: Seems like we missed a ok - continue sending.
    14:44:02.321: wait (7)

  • The last log lines (when no ACK is reported) looks:

    14:56:50.981: N8 G90
    14:56:53.985: Warning: Seems like we missed a ok - continue sending.
    14:56:53.985: N9 M111 S6
    14:56:57.017: Warning: Seems like we missed a ok - continue sending.
    14:56:57.017: N10 M360
    14:57:00.020: Warning: Seems like we missed a ok - continue sending.
    14:57:00.020: N11 M539 S1
    14:57:03.024: Warning: Seems like we missed a ok - continue sending.
    14:57:03.029: N12 M117 IP:10.100.100.13
    14:57:10.030: Warning: Seems like we missed a ok - continue sending. (2)
    14:57:10.031: N14 M117 IP:10.100.100.13
    14:57:13.032: Warning: Seems like we missed a ok - continue sending.
    14:57:13.033: N15 M117 IP:10.100.100.13
    15:05:25.695: Warning: Seems like we missed a ok - continue sending. (164)

    And the last number is increasing. Now it 190.
  • 14:41:49.026: al Reset
    14:41:49.026: Info:Brown out Reset

    That´s the interesting Lines... it Shows that you have Problems on Power Supply.
    Reason may be that  Arduinos Onboard Regulator is overloaded or Power Supply is a Bad one.
    Thats where to seach
  • wait is not your problem. You have lots of communication errors and the brown out also does not help here. Might even be a reason communication is so bad. In fact the waits here help you resolve blocks much faster. Otherwise you would have gotten a "timeout" delay on each of these errors. SO be happy to have them.
  • Thank you for your replies!
    I have many things to investigate now. :-)

  • I have changed the power supply, and now I don't have the brown out message.
    But beside that - everything are the same:

    17:23:39.955: Warning: Seems like we missed a ok - continue sending. (187)
    17:39:00.921: start
    17:39:00.921: Info:External Reset
    17:39:00.923: Free RAM:12369
    17:39:03.025: SD init fail
    17:40:08.111: Warning: Seems like we missed a ok - continue sending. (22)

  • That is ok. Not perfect as you have communication errors, but most printers have more or less frequent com errors. The message just says it detected one and fixed it. Of course you can try different cables and baut rates to see if they get less, but as long as they are not too frequent you can good live with them.
Sign In or Register to comment.