bredo
About
- Username
- bredo
- Joined
- Visits
- 27
- Last Active
- Roles
- Member
Comments
-
Works well.Thank you very much.
-
I did three things yesterday: 1. My Z probe connection was either loose/faulty or something strange was going on. After opening the electronics box the display kept flickering when auto leveling. I reversed the Z probe connection, and flickering st…
-
changed to: the svn version from tonight, and using the same settings, except:have_heated_bed=1, and bed temp set to 0.Display is normal, and it worked. Tried a second print now, bed temp set to 50. The printer rebooted as it had reached both tempe…
-
Thanks for fixing it. I am printing now and will test as soon as that is done. The com errors I got (in the log at the bottom of repetier host, windows 7/latest version from wevbsite) are:http://postimg.org/image/yjffxcihn/ Another thing I noticed…
-
Tried with#define HAVE_HEATED_BED 0and it has printed 100 layers now. the problem must be related to the heatbed routines. Seems like I get fewer of these as well, but it may be my imagination:16:52:50.866 : Warning: Missed line detected - correcti…
-
Hi Repetier First an unrelated thing you may like to hear: the babystepping works, so your fix was good. thanks. Another thing: I get lots of communication errors, sometimes unknown commands, on this printer. Using the shortest shielded usb cable …
-
Same problem here. The printer has a "mixing nozzle" and three extruders. I am now running the latest git version (work092 branch), downloaded today yesterday. I am printing PLA, and the heated bed is not used - the bed temperature is set to 0 in t…
-
I think the problem was my insane values for timeouts (stepper inactive and/or max inactive). After fixing them I have been able to do several 2 hr long prints. So this is really my own fault. Nobody needs 360000 seconds (=100 hours) timeouts...
-
Success - finally! I changed to this: #define STEPPER_INACTIVE_TIME 0L#define MAX_INACTIVE_TIME 0L(they used to be very high, I think it was 3600000, which I assumed was 1 hour.I may try to increase them, not sure.) Just completed a 1,5 hr print …
-
the display said standby. so I guess Printer::kill was called, as that is the only place this text is referenced.it was an sd print, and I was watching tv in the other room. trying again now, with KILL_IF_SENSOR_DEFECT = 0 Wish me luck. The fire ext…
-
and again....> 20:32:10.701 : ok 23628> 20:32:10.701 : SD printing byte 434714/1471800< 20:32:12.932 : N23629 M27 *58> 20:32:12.963 : ok 23629> 20:32:12.963 : SD printing byte 435003/1471800< 20:32:13.587 : N23630 M105 *3> 20:32…
-
Yes, a requested decrease in temperature may even trigger decoupling. I just tested this by starting the print at 255 degrees, then reducing temp to 245. After a short while it "error-beeped" and said:17:45:55.099 : N1927 G1 X163.955 Y49.168 E17.828…
-
An idea: could a fast drop in temperature cause the extruders and heaters to switch off, while x/y/z movement continues? The print started to come loose from the bed and it didnt need to be pretty. So I poured some acetone/abs solution on the area…
-
Almost. It failed around here::> 01:34:30.129 : ok 47891< 01:34:30.129 : N47897 G1 X60.958 Y98.88 E5.75965 *121> 01:34:30.394 : ok 47892< 01:34:30.394 : N47898 G1 X59.824 Y98.172 E5.82948 *69> 01:34:31.408 : TargetExtr0:0> 01:34:31…
-
Thank you. That helps a lot, I know where to look now What you say makes sense - I have had a few problems with the decouple functionality. At first it gave me decouple errors (dec) in the display a lot. I increased the decouple detection to 5 min…
-
And if it helps: It was a cached print. Ramps 1.4, D1 cut. More than enough amps on the power supply (one 30A for bed, one 24A for everything else), and it was connected to the computer when it failed (windows, since repetier host on mac is very old…