Arrêt brutal durant l'impression

Bonjour,
Repetier server 1.0.3 est installé sur une raspi3 à jour. En cours d'impression (sur Alfawise u20 en marlin2.0.x), l'impression s'arrête brutalement. Je n'avait pas le problème avant. J'imprime le même gcode depuis la carte sd sans avoir d'arrêt brutal.
Quel peut être le problème ?
Merci

Hello,
Repetier server 1.0.3 is installed on an updated raspi3. While printing (on Alfawise u20 in marlin2.0.x), printing stops suddenly. I didn't have the problem before. I print the same gcode from the sd card without having a sudden stop.
What can be the problem ?
Thanks

Comments

  • Repetier said:
    Merci, j'ai une alimentation 5v/3A dédiée pour l'écran et une alimentation 5v/3A pour la raspberry. je vais analyser plus en détails mais les alimentations ne semblent pas être à l'origine du problème.
  • As I said in description - check what linux says. But with 2 power supplies it is not very likely:-)
  • J'ai commandé des câbles usb 2A spéciales alimentation. Je vous donnerais le résultat des tests. 
  • Bon, après 10h00 d'impression, j'ai encore eu un arrêt brutal. J'ai pourtant remplacé les câbles par ceux que j'ai reçu.
    J'ai donc 2 alimentations 3A, 2 câbles USB 2A (1 pour la raspberry, 1 pour l'écran tactile). Je vais testé avec une autre Raspberry PI3.
  • Did you check afterwards if server is showing the power problems in bolt icon? Not to expect but better double check.

    There is also an option to reset usb on timeout that helps with some printers in case it is the serial driver in linux that hangs due to some error.
  • Where is option for reset usb ?

    undervoltage : never
    cpu temperature 38°
  • In printer configuration->General->Connection->USB Reconnect on Timeout. This is an automatic reconnect which causes the driver to restart.
  • je vais tester. Merci
  • edited March 14
    Le paramètre a été modifié mais le test est un échec. A part réinstaller la version 0.86, je ne sais plus quoi faire. Merci de votre assistance. Il y a eu un plantage de repetier-server car la vidéo de la camera était figée aussi.
  • Can you please start answering in english, so I can understand and follow the read. With languages I can not understand it is very hard to read the thread only seeing not understandable messages. And when I translate that part I forget what stands in some other messages if you understand.

    What exactly happened? Did really the server restart? You need to check server.log and /var/log/syslog to see what is disturbing the prints. Always hard to say since so many things can cause print stops.
  • edited March 15
    Hi,
    Ok but a little English.
    During work, printing stops suddenly for no reason. The nozzle remains stuck to the part. 
    I modified the parameter as you requested, I replaced the usb cables and the power supplies but 
    without solving the problem.
    
    Logs
    2021-03-15 18:16:11: Connection started: U20
    2021-03-15 18:16:11: Reset printer U20
    2021-03-15 18:16:21: No valid response seen within 10 seconds from printer, restarting connection
    2021-03-15 18:16:21: Port closed for U20
    2021-03-15 18:16:21: Connection closed: U20
    2021-03-15 18:16:22: Connection started: U20
    2021-03-15 18:16:22: Reset printer U20
    2021-03-15 18:16:33: No valid response seen within 10 seconds from printer, restarting connection
    2021-03-15 18:16:33: Port closed for U20
    2021-03-15 18:16:33: Connection closed: U20
    2021-03-15 18:16:34: Connection started: U20
    2021-03-15 18:16:34: Reset printer U20
    2021-03-15 18:16:44: No valid response seen within 10 seconds from printer, restarting connection
    2021-03-15 18:16:44: Port closed for U20
    2021-03-15 18:16:44: Connection closed: U20
    2021-03-15 18:16:46: Connection started: U20
    2021-03-15 18:16:46: Reset printer U20
    2021-03-15 18:16:56: No valid response seen within 10 seconds from printer, restarting connection
    2021-03-15 18:16:56: Port closed for U20
    2021-03-15 18:16:56: Connection closed: U20
    2021-03-15 18:16:58: Connection started: U20
    2021-03-15 18:16:58: Reset printer U20
    
  • After start printer U20
    2021-03-15 18:30:58: No valid response seen within 10 seconds from printer, restarting connection
    2021-03-15 18:30:58: Port closed for U20
    2021-03-15 18:30:58: Connection closed: U20
    2021-03-15 18:31:00: Connection started: U20
    2021-03-15 18:31:00: Reset printer U20
    2021-03-15 18:31:19: MainRequestHandler::handleRequest:Assertion violation
    2021-03-15 18:31:40: MainRequestHandler::handleRequest:Assertion violation
  • Here you see attempts to connect so port is visible, but there is no response from the printer so server closes connection and opens again. Assuming it worked before you have baud rate and port set correctly. You should try if changing the end value of dtr and rts makes any difference. Also a test worth is deactivate printer in server and activate.
    Last thing is unplug usb cable and reconnect. Would it then connect again?
    The question here is mainly why do we get no more data from the printer. Depending on where the problem is different actions will lead to connecting again. It also might be that you need to reset printer to make it work again.

    You can try to set in serial connection ping pong on. This reduces the risk of communication problems but also reduces maximum transfer data. But some firmwares get problems with high communication load. Others only communicate on special rts/dtr values which automatic reconnect may prevent from being set. Once we know what the problem is we can put in the correct fix.
  • The ping-pong mode is actived. i wil test tomorow
  • Hi,
    For a 30 minute print, I have no problem. I will test a 1h00 print.
  • 1.0.4 is now released with some communication fixes that also might help.
  • the release is installed. i test for the firmware
  • Hi,
    with the last version 1.0.4, the repeater-server shutdown was abrupt during work.
    
    2021-03-21 15:08:15: Webdirectory: /usr/local/Repetier-Server/www/
    2021-03-21 15:08:15: Storage directory: /var/lib/Repetier-Server/
    2021-03-21 15:08:15: Configuration file: /usr/local/Repetier-Server/etc/RepetierServer.xml
    2021-03-21 15:08:15: Directory for temporary files: /tmp/
    2021-03-21 15:08:15: Reading firmware data ...
    2021-03-21 15:08:15: Starting Network ...
    2021-03-21 15:08:15: Active features:4095
    2021-03-21 15:08:15: Reading printer configurations ...
    2021-03-21 15:08:15: Reading printer config /var/lib/Repetier-Server/configs/U20.xml
    2021-03-21 15:08:15: Starting printjob manager thread for U20
    2021-03-21 15:08:15: Starting printer threads ...
    2021-03-21 15:08:15: Starting printer thread for U20
    2021-03-21 15:08:15: Starting work dispatcher subsystem ...
    2021-03-21 15:08:15: Starting user database ...
    2021-03-21 15:08:15: Importing projects ...
    2021-03-21 15:08:15: Importing wifi connections from /var/lib/Repetier-Server/database/repetier-network.xml
    2021-03-21 15:08:16: Importing wifi connections from /var/lib/Repetier-Server/database/repetier-network-stored.xml
    2021-03-21 15:08:16: Initializing LUA ...
    2021-03-21 15:08:16: Starting wifi watcher ...
    2021-03-21 15:08:16: Register LUA cloud services
    2021-03-21 15:08:16: add G-Code-Renderer
    2021-03-21 15:08:16: LUA initalization finished.
    2021-03-21 15:08:16: Internal work dispatcher thread started.
    2021-03-21 15:08:16: Starting web server ... 
    2021-03-21 15:08:16: Work dispatcher thread started.
    2021-03-21 15:08:16: Webserver started.
    2021-03-21 15:08:17: Connection started: U20
    2021-03-21 15:08:17: Reset printer U20
    2021-03-21 15:08:19: New SSID Docman
    2021-03-21 15:08:27: No valid response seen within 10 seconds from printer, restarting connection
    2021-03-21 15:08:27: Port closed for U20
    2021-03-21 15:08:27: Connection closed: U20
    2021-03-21 15:08:28: Connection started: U20
    2021-03-21 15:08:28: Reset printer U20
    2021-03-21 15:08:35: Websocket opened
    2021-03-21 15:08:38: No valid response seen within 10 seconds from printer, restarting connection
    2021-03-21 15:08:38: Port closed for U20
    2021-03-21 15:08:38: Connection closed: U20
    2021-03-21 15:08:39: Connection started: U20
    2021-03-21 15:08:39: Reset printer U20
    2021-03-21 15:08:49: No valid response seen within 10 seconds from printer, restarting connection
    2021-03-21 15:08:49: Port closed for U20
    2021-03-21 15:08:49: Connection closed: U20
    2021-03-21 15:08:50: Connection started: U20
    2021-03-21 15:08:50: Reset printer U20
    2021-03-21 15:09:00: No valid response seen within 10 seconds from printer, restarting connection
    2021-03-21 15:09:00: Port closed for U20
    2021-03-21 15:09:00: Connection closed: U20
    2021-03-21 15:09:02: Connection started: U20
    2021-03-21 15:09:02: Reset printer U20
    2021-03-21 15:09:12: No valid response seen within 10 seconds from printer, restarting connection
    2021-03-21 15:09:12: Port closed for U20
    2021-03-21 15:09:12: Connection closed: U20
    2021-03-21 15:09:13: Connection started: U20
    2021-03-21 15:09:13: Reset printer U20
    2021-03-21 15:09:23: No valid response seen within 10 seconds from printer, restarting connection
    2021-03-21 15:09:23: Port closed for U20
    2021-03-21 15:09:23: Connection closed: U20
    2021-03-21 15:09:25: Connection started: U20
    2021-03-21 15:09:25: Reset printer U20
    2021-03-21 15:09:35: No valid response seen within 10 seconds from printer, restarting connection
    2021-03-21 15:09:35: Port closed for U20
    2021-03-21 15:09:35: Connection closed: U20
    2021-03-21 15:09:37: Connection started: U20
    2021-03-21 15:09:37: Reset printer U20
    2021-03-21 15:09:47: No valid response seen within 10 seconds from printer, restarting connection
    2021-03-21 15:09:47: Port closed for U20
    2021-03-21 15:09:47: Connection closed: U20
    2021-03-21 15:09:49: Connection started: U20
    2021-03-21 15:09:49: Reset printer U20
    2021-03-21 15:09:59: No valid response seen within 10 seconds from printer, restarting connection
    2021-03-21 15:09:59: Port closed for U20
    2021-03-21 15:09:59: Connection closed: U20
    2021-03-21 15:10:00: Connection started: U20
    2021-03-21 15:10:00: Reset printer U20
    2021-03-21 15:10:10: No valid response seen within 10 seconds from printer, restarting connection
    2021-03-21 15:10:10: Port closed for U20
    2021-03-21 15:10:10: Connection closed: U20
    2021-03-21 15:10:12: Connection started: U20
    2021-03-21 15:10:12: Reset printer U20
    2021-03-21 15:10:23: No valid response seen within 10 seconds from printer, restarting connection
    2021-03-21 15:10:23: Port closed for U20
    2021-03-21 15:10:23: Connection closed: U20
    2021-03-21 15:10:24: Connection started: U20
    2021-03-21 15:10:24: Reset printer U20
    2021-03-21 15:10:34: No valid response seen within 10 seconds from printer, restarting connection
    2021-03-21 15:10:34: Port closed for U20
    2021-03-21 15:10:34: Connection closed: U20
    2021-03-21 15:10:35: Connection started: U20
    2021-03-21 15:10:35: Reset printer U20
    2021-03-21 15:10:45: No valid response seen within 10 seconds from printer, restarting connection
    2021-03-21 15:10:45: Port closed for U20
    2021-03-21 15:10:45: Connection closed: U20
    2021-03-21 15:10:46: Connection started: U20
    2021-03-21 15:10:46: Reset printer U20
    2021-03-21 15:10:56: No valid response seen within 10 seconds from printer, restarting connection
    2021-03-21 15:10:56: Port closed for U20
    2021-03-21 15:10:56: Connection closed: U20
    2021-03-21 15:10:57: Connection started: U20
    2021-03-21 15:10:57: Reset printer U20
    2021-03-21 15:11:07: No valid response seen within 10 seconds from printer, restarting connection
    2021-03-21 15:11:07: Port closed for U20
    2021-03-21 15:11:07: Connection closed: U20
    2021-03-21 15:11:09: Connection started: U20
    2021-03-21 15:11:09: Reset printer U20
    2021-03-21 15:11:55: Websocket opened
    2021-03-21 15:13:05: Job created: /var/lib/Repetier-Server/printer/U20/jobs/00000001_AU20_Cube20x20.u
    2021-03-21 15:13:05: finish job creation /var/lib/Repetier-Server/printer/U20/jobs/00000001_AU20_Cube20x20.u
    2021-03-21 15:13:05: start printjob AU20_Cube20x20 on printer U20
    2021-03-21 15:16:06: killing printjob AU20_Cube20x20 on printer U20
    2021-03-21 15:20:20: Websocket opened
    2021-03-21 15:22:52: MainRequestHandler::handleRequest:Assertion violation
    
    
  • > the repeater-server shutdown was abrupt during work.
    What do you mean with shutdown? If you shutdown the server the printer will stop.

    All I see here is a server start that needed some tries to establish connection and a job that was killed after 3 minutes.

    You need to provide more context and time when what happens and what you saw and did. From this I just assume you killed the print as I do not see a disconnect during print.
  • edited March 22
    Bonjour,
    Le serveur a planté seul, sans aucune intervention de ma part. Voici les journaux de l'imprimerie actuelle, qui a été brutalement stoppée.

    Recv: 15: 57: 33.100: Erreur: le chauffage a échoué, le système s'est arrêté! Heater_ID: 0
    Mesg: 15: 57: 33.103: Le micrologiciel s'est arrêté! Vous ne pouvez envoyer des commandes hôte et shell que jusqu'à ce que vous appuyiez sur l'arrêt d'urgence ou que vous redémarriez l'imprimante. L'impression en cours d'exécution est finalement arrêtée.
    Recv: 15: 57: 33.330: Erreur: l'imprimante s'est arrêtée. kill () appelé!
    Mesg: 15: 57: 35.096: Avertissement: Délai de communication - réinitialisation du tampon de communication.
    Mesg: 15: 57: 35.096: État de la connexion: Buffered: 38, commandes manuelles: 0, commandes de travail: 4
    Mesg: 15: 57: 35.096: Tampon utilisé: 38 Octet libre forcé: 0 lignes stockées: 1
    Mesg: 15: 57: 35.096: Le micrologiciel s'est arrêté! Vous ne pouvez envoyer des commandes hôte et shell que jusqu'à ce que vous appuyiez sur l'arrêt d'urgence ou que vous redémarriez l'imprimante.
    Mesg: 15: 57: 35.096: Le micrologiciel s'est arrêté! Vous ne pouvez envoyer des commandes hôte et shell que jusqu'à ce que vous appuyiez sur l'arrêt d'urgence ou que vous redémarriez l'imprimante.
    Envoyer: 15: 57: 35.096: @stopLog
  • No it is not the server that crashed. Your printer firmware detected a problem with a heater and asked the server to stop sending commands. That is why server then stopped the print. So it was on the request of your printer!

    Heater id 0 is most likely your extruder. These are the most frequent to have this error. Normally a broken wire due to all the moves and bending during print. Can be the heater or the temperature sensor. On mismatch better firmwares detect that the temperature does not react as expected and go into fail save mode. There is also the chance of a false signal if the calibration of the detection parameter is too narrow. When you enable real logging you see this in the temperatures. When they go suddenly to very hot or very cold the thermistor is the problem, otherwise more likely the heater. 
  • Indeed the wires are damaged. I will replace them and redo the tests. it is possible that this is the source of the problems.
  • Maybe. Such errors start randomly until break is completely. And for most users it is hard to distinguish which part in the chain is failing. So will see when hardware is repaired if they also stop.
  • edited March 27
    Hi, I had no problem after changing the head. it's good for the moment.
  • After several printing, the problem recurred. the logs do not indicate anything. What to do ?
  • There is always an indication. Either os disconnects and you see server trying to reconnect or serial drivers stop responding and you see timeouts in log. What usb cable are you using? Should be as short as possible and shielded to prevent any errors. Especially the driver hangs I think come from uncatched unexpected signals which better usb cable would solve. 
  • edited April 3
    I will still check the logs
Sign In or Register to comment.