›

Selecting print causes Repetier Server disconnect

TheJoshWTheJoshW
in Repetier-Server
Hi,
I am using Repetier Server Pro 0.93.1 and my printer uses an SKRv1.4 controller with Marlin 2.0.5.3 firmware.
Often when I select the print icon next to the item I wish to print on the print tab, the server disconnects from my device temporarily and the print job is put in the queue and not sent to the printer.  Selecting print for the queued job causes the temporary disconnect each time it is selected.  Using the LCD/knob (firmware controller) before selecting print from Repetier Server seems to contribute to the issue, but I am not certain.  Let me know if you need any logs (and how to turn them on).
Thanks.

Comments

  • RepetierRepetier
    Maybe you have undervoltage problems. See https://www.repetier-server.com/knowledgebase/undervoltage-and-throtteling-of-pi/
    Especially run 
    vcgencmd get_throttled
    and check if it returns 0x0. You can also check /var/lib/Repetier-Server/logs/server.log if you see printer disconnects which is what can happen on undervoltage.

  • TheJoshWTheJoshW
    Thanks,
    /var/lib/Repetier-Server/logs/server.log hasn't been updated since 2019 with the last entry: "2019-06-18 15:29:34: error:WifiManager::scanMode:Syntax error", not sure if this is because its logging somewhere else, or because of another issue.  Ran vcgencmd get_throttled and got 0x0.  My Pi is actively cooled and rarely exceeds 50degC on CPU and GPU and I use the recommended genuine 5.1V power supply.  The only time I get the disconnect is on pressing the print icon, I can do everything else from Repetier-Server Webapp, set temps, home, move, extrude, etc with no problems.  The SKRv1.4 is configured to get power from the power supply not USB port so that should not contribute either.
    Thanks.
  • RepetierRepetier
    Logs switches between server.log and server.log.0 so current output seems to go to server.log.0 now.
    Your power situation sounds very good.
    Since it happens always on print start you should enable logging and see which commands got send to printer until disconnect. Also enable regular logging and see messages from firmware on next connect. At least old marlin showed reset reason on start. One guess is that one of the commands you send causes a reset on firmware side. Especially now that server side is more likely. Never the less also check /var/log/syslog at the time of disconnect. Linux also disconnects usb on back EMF from printer. 

    Once you see last 20 commands being send you can replay them manually and see if any of these would cause the disconnect. Typical candidates are enabling bed and extruder. Here also the timing between them might be important. So enabling one at a time with delay could work and both same time would cause a brown out if printer cpu and reset for example.
  • TheJoshWTheJoshW
    Hi Repetier,
    Ok captured server.log.0 below:
    2020-04-26 16:05:25: Start logging...
    2020-04-26 16:05:25: Imported external command Shutdown Server
    2020-04-26 16:05:25: Imported external command Reboot Server
    2020-04-26 16:05:25: Imported external command Power off Printer
    2020-04-26 16:05:25: Imported external command Power on Printer
    2020-04-26 16:05:25: Imported external command Pi Temperatures
    2020-04-26 16:05:25: Imported external command Enclosure Environment
    2020-04-26 16:05:25: Imported allowed execute command enclosure
    2020-04-26 16:05:25: Imported allowed execute command pi_temp
    2020-04-26 16:05:25: Imported allowed execute command skr_firmware
    2020-04-26 16:05:25: Imported allowed execute command skr_gcode
    2020-04-26 16:05:25: Webdirectory: /usr/local/Repetier-Server/www/
    2020-04-26 16:05:25: Storage directory: /var/lib/Repetier-Server/
    2020-04-26 16:05:25: Configuration file: /usr/local/Repetier-Server/etc/RepetierServer.xml
    2020-04-26 16:05:25: Directory for temporary files: /tmp/
    2020-04-26 16:05:25: Reading firmware data ...
    2020-04-26 16:05:25: Starting Network ...
    2020-04-26 16:05:25: Active features:4095
    2020-04-26 16:05:25: Reading printer configurations ...
    2020-04-26 16:05:25: Reading printer config /var/lib/Repetier-Server/configs/Cotton.xml
    2020-04-26 16:05:25: Starting printjob manager thread for Cotton
    2020-04-26 16:05:25: Reading printer config /var/lib/Repetier-Server/configs/SKRV14.xml
    2020-04-26 16:05:25: Starting printjob manager thread for SKRV14
    2020-04-26 16:05:25: Recover file and job found
    2020-04-26 16:05:25: Recover file empty - ignoring
    2020-04-26 16:05:25: Starting printer threads ...
    2020-04-26 16:05:25: Starting printer thread for Cotton
    2020-04-26 16:05:25: Starting printer thread for SKRV14
    2020-04-26 16:05:25: Starting work dispatcher subsystem ...
    2020-04-26 16:05:25: Starting user database ...
    2020-04-26 16:05:25: Importing projects ...
    2020-04-26 16:05:25: Importing wifi connections from /var/lib/Repetier-Server/database/repetier-network.xml
    2020-04-26 16:05:25: Importing wifi connections from /var/lib/Repetier-Server/database/repetier-network-stored.xml
    2020-04-26 16:05:25: Initializing LUA ...
    2020-04-26 16:05:25: Register LUA cloud services
    2020-04-26 16:05:25: add G-Code-Renderer
    2020-04-26 16:05:25: Starting wifi watcher ...
    2020-04-26 16:05:25: LUA initalization finished.
    2020-04-26 16:05:25: Starting web server ...
    2020-04-26 16:05:25: Internal work dispatcher thread started.
    2020-04-26 16:05:25: Webserver started.
    2020-04-26 16:05:25: Work dispatcher thread started.
    2020-04-26 16:05:25: Websocket opened
    2020-04-26 16:05:25: Websocket opened
    2020-04-26 16:05:26: Connection started: SKRV1.4
    2020-04-26 16:05:26: Reset printer SKRV1.4
    2020-04-26 16:05:29: New SSID Not Connected
    2020-04-26 16:05:31: Websocket opened

    I also enabled logging, and the log file is 0 byte, so nothing appears to be going to the printer.
    connected.log contains:
    < 16:05:26.529: N1 M105
    > 16:05:26.531: Error:Line Number is not Last Line Number+1, Last Line: 10
    > 16:05:26.531: Response while unconnected:Resend: 11
    > 16:05:26.531: Resend: 11
    > 16:05:26.541: Response while unconnected:ok N5 P63 B32
    > 16:05:26.542: ok N5 P63 B32
    < 16:05:26.542: N1 M110
    < 16:05:26.542: N1 M110
    < 16:05:26.542: N2 M105
    < 16:05:26.542: N3 M115
    < 16:05:26.542: N4 M220 S100
    < 16:05:26.542: N5 M221 S100
    < 16:05:26.542: N6 G92 E0
    < 16:05:26.542: N7 G90
    > 16:05:26.544: ok N1 P63 B31
    > 16:05:26.544: ok N1 P63 B31
    < 16:05:26.544: N8 M82
    < 16:05:26.544: N9 G21
    < 16:05:26.544: @getip
    > 16:05:26.548: ok T:200.00 /200.00 B:60.05 /60.00 @:55 B@:22
    > 16:05:26.549: FIRMWARE_NAME:Marlin 2.0.5.3 (GitHub) SOURCE_CODE_URL:https://github.com/MarlinFirmware/Marlin PROTOCOL_VERSION:1.0 MACHINE_TYPE:CR-10S EXTRUDER_COUNT:1 UUID:6ec3b998-ee25-11e8-8eb2-f2801f1b9fd1
    > 16:05:26.549: Cap:SERIAL_XON_XOFF:0
    > 16:05:26.549: Cap:BINARY_FILE_TRANSFER:0
    > 16:05:26.549: Cap:EEPROM:1
    > 16:05:26.549: Cap:VOLUMETRIC:1
    > 16:05:26.549: Cap:AUTOREPORT_TEMP:1
    > 16:05:26.549: Cap:PROGRESS:0
    > 16:05:26.549: Cap:PRINT_JOB:1
    > 16:05:26.549: Cap:AUTOLEVEL:0
    > 16:05:26.549: Cap:Z_PROBE:0
    > 16:05:26.550: Cap:LEVELING_DATA:1
    > 16:05:26.550: Cap:BUILD_PERCENT:1
    > 16:05:26.550: Cap:SOFTWARE_POWER:0
    > 16:05:26.550: Cap:TOGGLE_LIGHTS:0
    > 16:05:26.550: Cap:CASE_LIGHT_BRIGHTNESS:0
    > 16:05:26.550: Cap:EMERGENCY_PARSER:1
    > 16:05:26.550: Cap:PROMPT_SUPPORT:0
    > 16:05:26.550: Cap:AUTOREPORT_SD_STATUS:0
    > 16:05:26.550: Cap:THERMAL_PROTECTION:1
    > 16:05:26.550: Cap:MOTION_MODES:0
    > 16:05:26.550: Cap:CHAMBER_TEMPERATURE:0
    > 16:05:26.550: ok N3 P63 B25
    > 16:05:26.551: ok N4 P63 B26
    > 16:05:26.551: ok N5 P63 B27
    > 16:05:26.551: X:0.00 Y:0.00 Z:0.00 E:0.00 Count X:0 Y:0 Z:0
    > 16:05:26.551: ok N6 P63 B28
    > 16:05:26.551: ok N7 P63 B29
    > 16:05:26.551: ok N8 P63 B30
    > 16:05:26.551: ok N9 P63 B31
    < 16:05:26.551: M117 192.168.1.37:3344
    < 16:05:26.551: N10 M155 S1
    > 16:05:26.553: ok P63 B30
    > 16:05:26.553: ok N10 P63 B31
    > 16:05:27.557:  T:200.00 /200.00 B:60.00 /60.00 @:44 B@:42
    ...
    < 16:05:41.538: @getip
    < 16:05:41.541: M117 xxx.xxx.xxx.xxx:yyy
    > 16:05:41.543: ok P63 B31
    > 16:05:41.559:  T:200.00 /200.00 B:60.05 /60.00 @:33 B@:25
    ...

    Thanks.
  • TheJoshWTheJoshW
    Hi Repetier,
    For comparison when selecting print does work, server.log.0 contains:
    2020-04-26 16:36:56: Job created: /var/lib/Repetier-Server/printer/SKRV14/jobs/00000001_Kazoo eSun PLA lw 0.4mm lh 0.2mm if 60% ext1 200.0C bed 60.0C.u
    2020-04-26 16:36:57: finish job creation /var/lib/Repetier-Server/printer/SKRV14/jobs/00000001_Kazoo eSun PLA lw 0.4mm lh 0.2mm if 60% ext1 200.0C bed 60.0C.u
    2020-04-26 16:36:58: Repetier-Informer API response: {"error":0,"data":{"receivers":2}}
    2020-04-26 16:36:58: start printjob Kazoo eSun PLA lw 0.4mm lh 0.2mm if 60% ext1 200.0C bed 60.0C on printer SKRV1.4
    2020-04-26 16:36:58: Added timelapse 20200426T163658_Kazoo eSun PLA lw 0.4mm lh 0.2mm if 60% ext1 200.0C bed 60

    Seems to be more reliable if I start Repetier-Server before I power on the printer.
    Thanks.
  • RepetierRepetier
    Your first server.log.0 only shows that it got started and connected to printer. Contains no connection lost and no print start at all. So what exactly did you at 2020-04-26 16:05:25 ? Did you boot the pi oder did you start a print and server crashed at that moment? What is the log before that time if it was a crash? Server gets restarted after a crash so it appears to be still running but you would see in web interface for a short time "Oops connection lost". Also if you run in ssh
    ps aux | grep ssh
    you would see it just started and das a differed pid then before the print start.
    If it is a crash please follow https://www.repetier-server.com/knowledgebase/debugging-crashes-hangs-on-linux/ and send me the backtrace after the crash. There I can see exactly where it crashed and might also find our why. All just in case it is a crash.
  • TheJoshWTheJoshW
    @Repetier ,
    Repetier-Server is definitely crashing the instant I select a print.  I can make it crash easily.  However if I start Repetier-Server first then power on the printer and perform all actions from within Repetier-Server webapp it does not crash.  I have sent the crash logs to repetierdev@gmail.com as requested in the debugging page.
    Thanks.

Sign In or Register to comment.