›

printing stops on wireless connection

redlancerredlancer
in Repetier-Server
Currently have a MP Mini select with stock firmware v26.42 connected over wireless to Repetier server running on a Win10 machine. Using Simplify3D for the slicing and then sending the gcode to the server and starting the print.

Most of the time my prints are going fine, but occasionally the prints pause then restart after 10 seconds or so. Was doing a print yesterday that had about 3 stalls, then finally just stopped. Tried printing the same gcode file on the printer locally via the SD card and printed fine with no pauses.

I've seen a few other posts where the print starts/stops, but those seem to be focused around USB connections, so thought wireless might be different. Last few lines from the printer below. Not sure if there are some different setting to try for a wireless connection, or if the baud rate setting even has an effect of not using the USB connection.

21:53:50.-178: Warning: Communication timeout - resetting communication buffer.
21:53:50.-178: Connection status: Buffered:54, Manual Commands: 2, Job Commands: 5000
21:53:50.-178: Buffer used:54 Enforced free byte:15 lines stored:3
21:53:50.-178: M117 ETA 00:55:57 day 20
21:53:50.-166: N58872 M105
21:53:50.-154: N58873 M105
21:54:21.-146: Warning: Communication timeout - resetting communication buffer.
21:54:21.-146: Connection status: Buffered:55, Manual Commands: 2, Job Commands: 5000
21:54:21.-146: Buffer used:55 Enforced free byte:37 lines stored:3
21:54:21M105.-146: M117 ETE 03:02:33
21:54:21.-134: N58874 M105
21:54:21.-122: N58875 M105
21:54:52.-112: Warning: Communication timeout - resetting communication buffer.
21:54:52.-112: Connection status: Buffered:48, Manual Commands: 2, Job Commands: 5000
21:54:52.-112: Buffer used:48 Enforced free byte:37 lines stored:3
21:54:52.-112: M117 Layer 28/163
21:54:52.-100: N58876 M105
21:54:52.-88: N58877 M105
21:55:23.-87: Warning: Communication timeout - resetting communication buffer.
21:55:23.-87: Connection status: Buffered:48, Manual Commands: 2, Job Commands: 5000
21:55:23.-87: Buffer used:48 Enforced free byte:37 lines stored:3
21:55:23.-87: M117 ETA 00:57:28 day 20
21:55:23.-75: N58878 M105
21:55:23.-63: N58879



Comments

  • RepetierRepetier
    As you see in the log there are no responses from the printer any more. So there seems to be connection issue breaking the communication. Server shows it has commands send and was waiting for ok, which it never got.

    I don't think wireless is much different. USB can get com errors so wireless can also get disturbed by electronic signals. Have you already tried usb connection instead? Would assume that is more stable then wireless (is it bluetooth?)
  • redlancerredlancer
    Haven't tried USB connection to the machine that the Rep sever is currently running on. Not a bluetooth connection, have the printer set-up with a static IP address as a regular WiFi device.

    Will try a USB connection to see if there is any difference. Hopefully I can get the wireless to work since my current configuration has the server machine a ways away from my printer setup.

    -SJ

  • RepetierRepetier
    Server does not support connection to network. So you are using socat or an other serial->Network converter for communication?
  • redlancerredlancer
    running Malyan Link on the machine I'm using for the Rep Server. The Malyan app lets the wifi on the printer connect to my network, and can then connect the Rep server to the printer (via com100 iirc, not at machine right now)


Sign In or Register to comment.