- User Since
- Sep 11 2017, 7:47 AM (93 w, 2 d)
Mon, Jun 24
@karrad Sure, I'll head over there in a bit.
@karrad That is standard quality with supports enabled. I did reduce the support density a little bit, just to try and save on material.
Here was a 3 day print with the default PLA profile.
Tue, Jun 18
I created a ticket on the Quiver board about this problem. T8003
@DaniAO If it happens again when I'm working on a Quiver I'll make sure to get some pictures and add it to the Quiver board.
@DaniAO I've had it happen on both machines.
I'm not sure if lengthening the wire would really help that much. It seems like the wire would still have the risk of coming out of the crimp, like we have been seeing. When the ring terminal is tightened onto the screw under the motor it makes the neck of the connector bend, which might be a part of the problem.
Mon, Jun 17
The second drop test with the new foam went well. It looks like the retaining rings all stayed where they should have and the toolhead zip-tie did not break this time. The only problem I saw was the 5v fan wire pulled about halfway off the pins that hold it in place at the RAMBo board. I couldn't get a good angle to get a picture of it, but tried none the less. I also accidentally pulled the y-axis ground out of the connector when taking the bed off the machine to box it up for the drop test.
I just did round 2 of drop testing a Redgum and this connector became unseated again, however it did not completely come lose this time. I was able to push it back into place on the second drop test.
I noticed some warping going on at the lower layers of a print. I ran 2 tool caddies which took over a day to print, and I'm not sure if the longer than usual print time could have cause the warping.
Thu, Jun 13
Wed, Jun 12
I'll keep an eye out for that, thanks!
One thing that I noticed on a Taz Pro that I was giving a once over after the calibrators got done with it, was that the ground screw that connected the USB thumbdrive to the RAMBo was not tightened all the way. I'm not sure if this could cause the thumbdrives to short out, but it's a thought.
Tue, Jun 11
One other thing I noticed that is not in the drop test documentation is that when unscrewing the bed screws with the NinjaFlex bands on them, is that the bands tended to hold onto the screw and screw around it when loosening the bed bolts, which could cause the band to possibly break.
Mon, Jun 10
I have been working on this over the weekend as well as today, and it looks like a heating issue, possibly from the parts cooling fan sucking in hot air off the bed, which prevents PLA from cooling fast enough and leads to warping. I ran 5 test cubes so far, 3 of them at the back of the bed individually and 2 in the center of the bed with a desk fan setup behind the printer to help cool the cubes. I also ran a 6th cube with the same .gcode but no external fan blowing on the part. With all of these cubes, I used a bed temperature of 60C for all layers, to try and help reduce the warping, it seems like the higher bed temperature was causing it to be more noticeable.
Wed, Jun 5
I've been having issues with heat creep happening pretty quickly into any larger/longer prints, so I reduced the temperatures down to 210C on both hotends with some Polylite PLA. I've had a test print going for roughly 8.5 hours now and the heatsink are slightly warm to the touch, but no signs of heat creep yet. It looks like the with lower temperatures, a person might be able to increase the skin overlap percentage to try and get rid of the seam lines that are very noticeable when going between colors. I've got a few ideas for a couple more changes that might help, however I haven't had the time to test them yet. I would be happy to include any notes here, once I've had a chance to make a couple changes. I just don't want to make to many changes at once, for testing purposes.
May 22 2019
The other day I had them stripping out when tightening them by hand, without putting a tool on them. It almost seems like only a couple threads on the screws are all that holds the extrusion the the uppers.
May 15 2019
If possible we should also add to "Check z motor screws to make sure they are not cross threaded and sitting flat against the 3d printed part." I don't know if this is still a problem, but it had been a problem last week and prior. Due to the angle of the hex driver needed to get the z motor screws screwed in, they have a tendency to cross thread and go in at an angle, if not careful.
Apr 29 2019
I was having this problem with a machine I was working with on Friday. I ended up changing out the USB stick for a different one and it started reading correctly shortly after boot up.
Apr 9 2019
Here's what happens when I slice it at high speed settings. Cura LE 3.6.3.
Change was made here and closed. https://code.alephobjects.com/rTAZQUIVER42ac31574d3c329e6b6ebc8f46526930abf84c82
Apr 5 2019
Here is the cluster gcode for the 4.2mm standoff's, just in case they work after testing.
I sliced the file and set up test prints for 16 of them last night. We have them in hand now and are trying out the v2.4 of the bed corners.
Apr 4 2019
Slicing version 2.4 via T5668
Slice request complete on T6464
Everything fit together well. I did not try to pull out the inserts, due to the part not being load bearing.
4 passed with 0 failures, regarding cosmetics.
Mar 5 2019
Jan 31 2019
I checked a few of the Taz 6's over here and a couple of them seem to be a bit off. We've got one that says it's been used for 20 hours, which seems a bit low for our printers over here, and then another one that says around 2 days of print time on it, which also seems a bit low. We have another one that shows 13 days of usage, which seems a bit more in range.
Jan 26 2019
I just put 30 files on the USB drive and they were 4.2MB per file. It seems like there is a slight delay (a second or less) when cycling between the 4 screens worth of files on the LCD screen. 50 of the same files gives a delay of about 3 seconds. 70 gives a delay of about 5-6 seconds and for some odd reason the screen flashed and the z axis homed itself when pressing the USB drive button.
Most of my answers are still the same as the previous notes I left, however with the latest firmware on the machine (126.96.36.199) it looks like the level x-axis has been removed and I also was still getting a lot of false triggers from the endstop sensors, so I messed around with the Runout Detection Distance. When I set it to 30, it would still false trigger a lot, so I bumped it up to 50 and still had problems. Once I bumped it up to 200, I was finally able to complete a print with only one endstop trigger for no reason, rather than getting one every 2 minutes or so.
Dec 23 2018
I also uploaded the form I was filling out, with my answers in green, just for ease of viewing.
User Testing Feedback -Quiver Alphas
Slicer: Cura 3.6.1 and 3.2.32, just to see if it helped with z-offset and filament run out sensors
Dec 1 2018
Nov 10 2018
I forgot to add that I'm using Cura LE 3.2.31 for this.
All three profiles seem to work pretty well, however the prime tower gets positioned on the back side of the bed in the grey area. I have tried uploading the profile with a change in location for it, however Cura seems to not save it, or allow me to export it out, or even find it under the Manage Profiles. The positioning I was using for testing was X 30mm and Y 10mm which positioned the prime tower on the front left of the bed.
Nov 9 2018
I have been working on the PVA profile for the Flexydually, and once I created a material profile for it, Cura ended up finding the actual profile profiles for it. The standard profile worked out well for the impossible gears print. I am still testing the high speed and high detail profiles, but here is the material profile that I set up for it.
Nov 2 2018
I've never actually had to use a layer of glue stick when printing ABS, but usually I tweek the z-offset to raise the nozzle up just a hair from where I usually use it. I will try some ABS prints with glue stick over the weekend if you guys would like.
Sep 20 2018
Aug 30 2018
I just noticed this on Cura LE 3.2.25 and really like the layout of it compared to the previous versions. especially the LCD area. That should make things much easier when upgrading the the Mini LCD without having to find the LCD box.
Aug 18 2018
Jul 22 2018
I was just having the same problem when trying to use the pause at layer height function on a Mini 1.04 with a standard toolhead, only when it goes to resume it drops the toolhead below the bed and I powered off the machine before seeing if anything bad happened.
Jul 20 2018
It looks good so far, however the first link has a picture showing the older version of Cura, which might be confusing. The second link looks good as well. I have added these to my bookmarks.
I was hoping in the user manual, but understand it was to late for that. The guide you pointed out is a good one though, I will be bookmarking it.
Jul 14 2018
The customer just got back to us and after updating to Cura 3.2.23 he is able to resize the console window and it looks like everything is working properly now.
Jul 12 2018
Thank you, I passed the information on to the customer.
Jun 29 2018
The customer just got back to us with this information.
I just passed the information on to the customer. I will update here once I receive an update.
Jun 15 2018
I sent an e-mail over to the customer that was having this problem and will update here when he responds back.
May 31 2018
Thank you, I passed the information along to the customer.
May 25 2018
May 24 2018
I'm sorry, I forgot to add that. this is on a Taz 6, standard extruder, however it also happened on a V3 dual as well over here.
May 17 2018
Apr 26 2018
Apr 20 2018
Clearing the cache again seems to have me back up and running.
Apr 12 2018
Mainly just pictures of the security prompt that pops up when a user tries to install on a Windows machine, and also, if possible a write up on extracting a .zip file for the RAMBo driver. We don't get a whole lot of calls about it, but it could help give the customer piece on mind, if they are unfamiliar with computers.
Apr 8 2018
Helpdesk ID: 161776
Apr 7 2018
Apr 6 2018
Mar 22 2018
Clearing cache fixed the problem.
Clearing cache solved the problem.
Mar 16 2018
We've got the guide here: https://ohai.lulzbot.com/project/windows-drivers/firmware-flashing/ and it doesn't really go over extracting/saving the files once they download them, and I know for some people this is easy to figure out, but every now and then we get someone who has a very hard time trying to extract the file with 7-zip or whatever software they choose to use. It seems like when I try to walk them through it over the phone on a windows based machine it pops up with some kind of security settings and people kind of tend to panic when they see something like that pop up. If there were a few pictures of a windows machine going over how to extract and save the file it could really help out.
Mar 15 2018
Feb 18 2018
Heating failed E1 roughly 10 minutes into the print of impossible gears. Double checking that he has latest version of Cura and firmware.
Feb 17 2018
I just set up an RMA for a customer getting the same error on his V3 dual toolhead. He has Cura 2.6.69 with the latest firmware installed. E0 heating failed
Feb 16 2018
Customer got back to us with more logs.
Feb 1 2018
Jan 18 2018
Sure, I'll drop in next week with it.
I just purchased the modular bed kit for my Mini at home on Monday (foxglove) and when I went to remove the first print off the bed i gave it a tap with my hand and a putty knife. Instead of the part coming off nicely, like they usually do, if popped the whole bed off and to the left. I thought maybe I hadn't tightened the bed down enough, but it looks like this could be the problem.
Jan 12 2018
I'm sorry about that. I sent the information over to the customer and explained how to get the Cura error logs. I will update this once I get a response back from them.
Jan 11 2018
The customer just got back to us and tried doing the previous suggestion and the problem still persists. He tried loading it twice and provided a report for each crash.
Update from customer. "I was running 2.6.52 when the problem first occurred. I upgraded to 2.6.63 and still had the problem."
I just passed word onto the customer to try this, I will update with his results.