Irratic extruder behaviour + short waiting times on raspberry 2 with RS 0.70

Comments

• Repetier

  December 2015

  Please enable echo for firmware and logging for the server prints and start a print. Then you see what you have send and what firmware thinks it has received and also any communication error. Only with such a log it is possible to find the problem. You need to corellate the errors with the corresponding log lines. If in doubt post that part and describe what happens where.

  
  

  You should better get an ok for every line send or printer will stop for timeout seconds.

  
  

  Also note that on linux several programms can connect to the same port. While this works it creates a lot of errors and problems so make sure no other software opens the port on the Pi 2.
• swiftythefox

  December 2015

  Thank you for the reply!

  
  Unfortunately Marlin does not support M111 (set debug level), but I think that the logfiles help a lot already.

  
  

  Example Snippet:

  
  

  >  9:47:44.976: Error:Line Number is not Last Line Number+1, Last Line: 633

  >  9:47:44.980: Resend: 634

  <  9:47:44.981: N947 G1 X104.255 Y130.428 E33.42924

  <  9:47:44.981: N948 G1 X104.339 Y130.578 E33.43781

  >  9:47:44.981: ok

  >  9:47:44.993: Error:Line Number is not Last Line Number+1, Last Line: 633

  >  9:47:44.994: Resend: 634

  <  9:47:44.994: N949 G1 X104.47 Y130.709 E33.44706

  <  9:47:44.994: N950 G1 X105.5 Y132.729 E33.56018

  >  9:47:44.994: ok

  >  9:47:44.997: echo:Unknown command: "122"

  <  9:47:44.998: N951 G1 X106.212 Y131.331 E33.63845

  <  9:47:44.998: N952 G1 X106.517 Y130.72 E33.67252

  >  9:47:44.999: ok

  >  9:47:45.005: Error:Line Number is not Last Line Number+1, Last Line: 633

  >  9:47:45.009: Resend: 634

  <  9:47:45.010: N953 G1 X106.657 Y130.58 E33.6824

  <  9:47:45.010: N954 G1 X106.74 Y130.431 E33.69091

  >  9:47:45.010: ok

  
  

  I would have added the whole one, but I didn't see a "code" tag or an attach "file" option, so I hope that this is representative enough

  
  

  Over the whole test print it tries to resend the same line for ages, and sometimes there are even (hard coded?) echos from the firmware with "unknown command -num-". That means that they start not to understand each other the second a print starts. Before everything is fine, manual commands always get recognized.
  

  
  

  The pi2 is running on wheezy without an x-server running. The only thing I did after I copied the image to the sd card was a sudo apt-get update, then I already grepped the firmware with wget... So if there is something else blocking my com port, it must have been installed by default - something very unlikely. Or do you know of such a service that can do that on a debian/raspian flavored os?

  
  

  
  
• Repetier

  December 2015

  I'm also using debian wheezy on Pi 2 without problems. The problem I now have is that the origin of your problem was when sending line 633. There something went wrong and at the shown part server is already ignoring it since that line is not in resend buffer any more. So the question is more how we got the line out of the resend buffer so it gets ignored.

  
  

  Firmware description marlin.xml describes resend request like this

  <response type="resend">^[Rr]esend:\s*(\d+)$</response>

  and that should match what your log shows. So please post what happened around 633 with at 
  least 200 lines around it. Posts can contain 80kb now. Maybe I figure out what is going on. 
  Does not look like a other software.
• swiftythefox

  December 2015

  I wanted to post the log file, but the reduced log was still too long. can you write me a request from your address to martin.humel --- at --- gmail.com please? Then I could send you both, the .gco & the logfile without any troubles. (120k logfile + 4MB gco, but that can be cutted )

  
  

  Basically the log shows just a warmup phase (bed + extruder) and then 3x 1000 lines that show troubles with the same line number and afterwards just some sporadic errors which needed only 1 resend. 

  
  

  Just something else about the setup: I have a fully shielded USB cable that goes straight away from the printer, so we can cancel that source of error as well. Anyway, the same HW works with repetier host in 2 different OS as well, even though a pi can't be compared to a pc.

  
  

  Would you be interested in the source files (version, config etc) of my Firmware as well? (if I can find it...)

  
  

  thank you again for the support!
• Repetier

  December 2015

  We are getting more feedback from other Marlin users having problem with 0.70.0. Seems like there is a incompatible change in resend handling causing this. We will work on 0.70.1 to solve the problem. Anyhow if you could send the log to repetierdev@gmail.com it might help finding how it happens and finding the problem faster.