joatrash
-
Posts
57 -
Joined
-
Last visited
Content Type
Forums
Events
3D Prints
Posts posted by joatrash
-
-
OK... more testing. Look at this:
I imported the gcode files into Simplify3d just to look at them. It looks like Cura has inserted random super-fast print head movements because the red lines are exactly where the print failed. UMs original firmware seems to be able to handle the files anyway, but Tinker stops printing when it reaches those lines every time.
Any thoughts as to what could be going on? -
Ok... I've spent a couple days experimenting now and there's something going on with Tinker on a specific 3d model I am trying to print. If I go back to the original (latest) UM2+ firmware it prints fine. I now tried slicing with cura 2.5, 4.1 and 4.7 and the results are similar- the print just stops after a while as if it were finished. The same model, sliced waaaaaaay back with an early cura (2.1 I think) still prints.
The weird thing is that I went back and redid the model with different topology, made it 100% error free, manifold and watertight but the result is the same. If IS a rather detailed model though, at around 50MB. Unfortunately, I can't share this particular model, since it's a confidential file, but I'll try a different model (that I CAN share) and see if I get errors on that too. -
Is anyone having troubles with this firmware and Cura 4.7?
All of a sudden, files I'm slicing will stop printing after a couple hours as if they are finished. Had two cut out after around 2 hours and one just now after about 8 hours. No error message... the print just stops and it says "print completed" on the screen. I've verified that the gcode file is not truncted and the SD card has no errors. I can still print old gcodes just fine. -
23 minutes ago, tinkergnome said:
tbh: I don't remember such things.... should i?
Do you have a link or some more details?
I don't know if this is what was meant, but every time a print is completed, the printer has to be powered off, then on again before a new print is started. If not, when you start a new print, as the printer runs thought the prep-cycle where it "resets" the print head location and raises the bed, the print head stop switch does not register when the head reaches the back, and the motor keeps going, making the belt "jump" over gears and the entire machine shakes until you turn it off. (I personally don't have a film clip of it and I'm a little hesitant to make one for fear of causing any damage. I've just learned to power the thing off between prints... most of the time!)
-
11 hours ago, ChrisRiddell said:
Ran into a weird issue after doing a couple prints using the change filament the homing of the head fails it hits the end stops then goes crazy like it did not hit the end stops.
worked after powering off and on but does it again after doing alot of prints then trying to change the filament.
The same thing happened to me once with TW. Luckily, I was nearby and could stop it.
-
I haven't really studied all the settings, but I know that in the material settings menu, there are 4-5 different temps to set. Maybe it thinks you are printing ABS or something?
-
Tinker has settings for different nozzles and things that are automatically detected through info in the gcode file. Go into the materials settings and make sure the temp is set to 210 on the material+nozzle you are using. (If it's an old gcode file, the default nozzle is automatically set to 0.4 for heat purposes)
-
So material flow is controlled by the slicer calculations? (I mean, it needs to move more material with a 0.6 than with 0.4 nozzle.)
That's the only setting on the printer that depends on the nozzle diameter in the UltiGCode comments. All other things are part of the slicing process.
-
Yes, it seems that the line is missing from Cura_steamengine 13.12. I'll add the line when I get a chance and see. (I usually name my files accordingly... was mainly worried about the print.)
But I'm guessing the information for printing with the nozzle must be contained somewhere, or I'd have had a lot of underextrusion this last year since switching to the Olsson block! (I got an OB long before doing the full UM2+ upgrade.)
So far the print seems to be working fine. Thanks for the response! : )
I'm going to run a print now ans see what happens.
I assume that the old versions of CuraEngine do not provide any information about the nozzle size in the header of the gcode file. The UM2+ firmware will use the material temperature for the 0.4mm nozzle as a default in those cases.
This is what it looks like with the current version of Cura. If in doubt you can add the missing line and see, if it makes a difference.
; ;FLAVOR:UltiGCode ;TIME:4875 ;MATERIAL:5528 ;MATERIAL2:0 ;NOZZLE_DIAMETER:0.4 ;Generated with Cura_SteamEngine 3.0.3
-
Hello all!
So, after upgrading my UM2 to a PLUS, I needed to try this out since I wanted to keep using PID bed heating since my prints were horrible as soon as I went past Cura 14.05.
However, it seems to be misreporting which nozzle my gcode files are set for. (Didn't find anything about this upon a search, unless I completely missed it?)
Files that were exported (from Cura 14.01 or .05... OLD I know... but it has always worked) with a 0.6 nozzle setting show "nozzle 0.4" in the Tinker display. Is this just a display bug? I'm going to run a print now ans see what happens.
Cheers!
//Joe
-
I've been getting a lot of horizontal banding lately as well and I can't find the cause. It's driving me crazy. It MUST be hardware related because I'm using the same gcodes and firmware as I always have and i was getting perfect prints before.
At this time I've checked just about everything I can check, from what I reckon. My last remaining things are:
- Faulty feeder giving uneven amounts of plastic
- Worn nozzle (doesn't really look worn though)
- Loose belts (hard to know how tight is enough... I can move them easily up and down but they're not "floppy". Tried attaching a belt tightener but the belts are too tight to get it on there so I might have to make a custom one.)
- Z-motor or axis problem. I DO hear an unveven "grinding sound" when I manually press the build plate DOWN.. sounds a little like in the video you linked above... like there is sand in the mechanism. But I don't really hear any grinding when I LIFT the bed manually... only when I push it down. I wonder... when I first got my UM2, the threaded Z-axis nut was faulty, causing the bed to drop several mm in intervals. This also placed a bit of sideways pressure on the z-screw. Maybe that extra pressure has caused the motor to break down prematurely?
- Faulty feeder giving uneven amounts of plastic
-
OK, can you tell me what file(s) besides "curaengine.exe" that needs access? Can't seem to find the right one in my block list...
Thanks!
-
Aha... that may be it then. I routinely block program access to the internet, sometimes without even thinking about it. The only things I allow access to are things that actually MUST have access (like browsers).
Why would Cura need firewall access just to calculate g-code?
-
Also, I don't know if this is relevant or not, but if I load Gcode generated by 14.01 it doesn't display properly...
-
Bumping solved, thanks. (Never had the "singles" active before.)
But it still refuses to slice... the button is simply greyed out. If I switch to 0.2mm the button is no longer greyed out but it still doesn't slice... just says 0 hours. The program doesn't lock up or anything...
-
Hey guys,
Been using 140.01 since I bought my machine back in Feb. Just installed 14.03 but it refuses to slice. Same thing with 14.05RC4. I can load the model but then nothing. Have tried different models.
14.01 continues to work fine but I'd like to experiment with the increased options in the newer verions.
Also... it seems that if I load different models Cura now "pushes them out of the way" and does not allow separate models to be close to one another on the platform! 14.01 did this too, but not nearly as much.
-
Hey guys,
I've recently begun experiencing major slipping on my UM2 and it's driving me nuts. After reading through all this here, no setting I make helps fix it. I've getting maybe 1/6 slip per turn with gross underextrusion as a result.
Print speed: 40-45
Layer height: 0.1
Walls 0.8 Density 15-20%
bed temp: 55
Extruder Temp: tried 210-255 (hotter seems a liiiiiiittle better but not much)
More or less flow doesn't make a difference.
Have tried moving the filament around to make sure there is no tension. It looks like the filament sometimes twists a little in the bowden when the slip occurs.
Turning the friction screw does nothing. I am using Faberdashery PLA. I've gotten the best results using their robot silver since I got the printer, switched to black for a couple prints and the problem got worse. (Seems the metallic filaments are always the best in my printer...).
Any ideas?
-
It seems quite a few of us are having this problem right now!
The gear/pulleys seem to be made out of aluminum. I would think there is a small chance that tightening too much will damage the threads- the inset hex/allen head screw is made of hardened steel, after all. However, it'll probably be difficult to apply enough force to damage them with the thin hex wrench provided.
-
Well, I removed the two screws holding the cover and looked under it. There's a brass washer/ring held in place by four bolts to the build plate. I assume that the brass ring is threaded inside so that the screw can move it. This brass piece was NOT loose, so there is either a washer or something underneath that is faulty or the brass piece itself was machined defective. There's not much more I can do until UM get back to me with instructions. Removing two screws to look under the cover is one thing but I'm not going to start disassembling the build plate without the go-ahead from UM. (I can't fix anything until I get replacement parts anyway.) Sigh... I'm in full production of a prop kit at the moment too so I can't really afford to be without the printer for long.
-
Yeah, the Z-screw is lubricated enough- something inside is probably not screwed down correctly or has vibrated loose. I can easily move the plate up and down.
Here's a video of it:
-
Yet another discovery. My build plate is LOOSE. I can pull it up or down maybe 2-3mm. The screw doesn't seem to move, so there is something loose inside where the plate attaches to the screw...
Would the coupler be inside the housing just behind the buildplate?
-
My headache grows.
I just got home and did a test.
First, is the ultimaker 2 supposed to make a NOISE when the build plate is lowered during printing? Whenever my buildplate is lowered as part of a print, I hear a short "grinding" noise for a fraction of a second. Kind of like a "Ksssht". I felt the plate screw with my finger as this happened and I felt it turn slightly so I know that it occurs when the plate is lowered.
Second, I watched the print going and it looks like at one point, the build plate fails to lower for maybe a level or so, causing the filament to "smush" as it is printed. This creates the misaligned layer that shows in the prints.
Third, a few mm later I watched as the build plate DROPPED 1-2mm in one go with a small "kadunk"! The print immediately failed as the new layer had no old layer to grab onto and I stopped the machine.
So, the question is- what is causing this? A loose gear or something somewhere? Any ideas?
//Joe
-
Well, the hardware thing is the only thing I can come up with unless there is something wrong with the software. Wil measuring with a caliper be reliable though? I mean, the build plate is a bit "springy"- so much so that measuring 100 microns can be difficult.
Here are some more photos. I also noticed that the "split" seems to be preceded by a couple layers not aligning properly (see the red arrows). It's not in the EXACT same spot each time, but pretty close... and the differences COULD be due to the position of the bed leveling screws in comparison to the screw that holds/moves the platform. I'm going to send this to UM support as well.
Note: I did some cleanup on the blue parts... they looked just like the grey one at first with strands of plastic everywhere.
-
I am bringing this thread back, because I am seeing this problem more and more.
After printing about 1cm up (more o less) the print starts failing and "skips" a few layers and starts pulling strands of filament all over the place, only to resume again as if nothing was wrong. I'm having difficulty finding any consistent pattern besides the height, which makes me wonder if there is a hardware error or damage to the mechanisms that maybe stops the print bed from moving properly. It seems to ALWAYS happen at the same height.
Some things I can more or less conclude:
- bed or print head temp has little effect (tried different settings)
- material feed possibly catching on something does NOT appear to be the issue because I've tried many different variants and I know that at least one of them is guaranteed NOT to "catch" anywhere. If there's an issue it could be within the feeder... but why would it be so consistent?
-bed has been leveled very carefully.
-doesn't matter if I print ONE big item, one smaller item or lots of items... it happens anyway.
-it doesn't ALWAYS happen... but maybe 20-25% of the time.
I'm out of material at the moment but when I get new stuff I will TRY to catch it "in the act".
Tinker firmware - introduction
in Firmware
Posted
Haha, well looking at the screenshot... the red line seems to indicate a moment of 9000mm per minute!
But I did more digging. It looks like the problem might be hardware-related on my end. I suspect a faulty SD-card reader. (Or if it's not, then Windows is indexing the SD card even though it's not supposed to be.) Looks like errors start showing up in files when the SD card is removed. Information in the files goes missing, like here:
Broken copy on the left, error-free copy on the right.
Apologies for thinking it was a Tinker issue.
ONE puzzling thing though... the UM firmware seems to IGNORE the error and carry on, but Tinker stops. is there an extra-sensitive error-check in there?