Feb 28 2019
Sep 13 2018
Aug 23 2018
Aug 13 2018
Jun 27 2018
Jun 22 2018
Since there are no plans to update factory default FW for TAZ 6, this isn't affecting production. We'll just keep using legacy Cura for its legendary, unrivaled reliability until CuraLE gets closer?
For RMA/LRS we'll just print whatever and give them new FW, the customer can always revert back to stable factory FW if they're still using 21.08.
Jun 20 2018
@logan For an updated calibration octopus, please check this file:
@logan New Source cards only have STL files w/o gcode, and will not require updates. All of these will indicate that the customer can slice with their desired filament.
@karrad That also doesn't resolve the other scenario:
Brand new machine
Customer installs CuraLE which advises them to upgrade FW, they do so
Customer now has no compatible sample print gcodes
@karrad The gaps at the top of the legs? The whole reason we changed the model for Mini 2, because nothing we sliced in CuraLE would fix that. Had nothing to do with the Z-axis. Slicing through legacy DID fix that. Legacy/CuraLE do not provide the same quality when printed on the same machine.
You should see the exact same quality, and don't even need to re-slice if you prefer. (although please do, it will alleviate your fears.) The issue with the Mini 2 calibration gcode is due to the design of the Mini 2 belt driven Z axis, and that is sorted in T2662.
No the line is fine.
We have no concrete guidelines on what FW to install for RMA/LRS.
Updating the gcode used only for LRS doesn't solve the issue:
We encourage customers to update to the latest CuraLE, if they do so, all of the sample print gcodes they received with their printer will have this issue.
Logan just saw this issue when he was printing on a LRS updated to the newest and greatest firmware.
Cluster is seeing this on approved slices, which would all need updated. SD card master would need updated. The line is still using 21.08 for everything TAZ 6....
@logan Double checking that gcode, it looks to be sliced in 21.08 and looks pretty old. You are missing the wait for temp to be reached, along with the variable for part removal temperature:
@karrad nGen using the calibration octo in TAZ Olive
@karrad Our end gcode from TAZ Olive sample_prints:
@logan What material?
@karrad Immediately after the print finished, it is not waiting for temperature.
If I recall it would move forward as soon as the part was complete in cluster, so it would be at what ever temp it was completed at, 110 if I recall. It is also important to note that cluster is using older files and don't remember if anything has been updated or if they had seen any differance. @Shawn or @EricNugent will have more information regarding that.
@logan Do you recall what temp it moved forward?
I have double checked the end gcode, and it looks like we have the proper variable in there:
Jun 18 2018
May 18 2018
May 4 2018
Apr 17 2018
@kent I agree, these images do clearly show that the nyloc nut is being allowed to spin on the part. I can use these images to help communicate with the assemblers. Thanks for the help on this.
Apr 16 2018
@tomc I think this one can be addressed by improving the assembly technique. Can you confirm and then we can close this ticket?
I was reviewing the NCMR's in MER and found a consistent tool mark on every part with cracking.
This could be a result of the nylock not being in the correct position before tightening.
Apr 11 2018
Thank you @caguilar, this good to know. I don't want to rule out the possibility of printing issues, however knowing this will help us look into how we on the floor are building/handling these parts more closely.
@kent What part number are we talking about? Are these the Z carriage Idler AS-PR0019? If so we have been steadily receiving these and if they changed back in December, we have been using that newest model for quite a while now. The oldest stock I have on hand for these were made back on 3/30/18.
Apr 10 2018
Hey @EricNugent I looked through the history for these parts, and it looks like we updated this slice in December https://code.alephobjects.com/rTAZOLIVEee1c9c27c22e6e68d1db7009d13486dad35eacc5 . @caguilar do you think we would have just started seeing these parts in production, based on the buffer we had? @EricNugent please pull a sample of these parts from production and qualify them, with the failure @tomc is referencing in mind.
Apr 9 2018
The cracking of these parts has only started recently in the last couple weeks. It started with one or two and has crept up since. Last week we had found 9 which has been the most so far. It was first noticed at the calibration station using a flash light for inspection. Many of these have been hair line cracks that are very difficult to see by eye, but others have been very noticeable. I have left notes in the production pass down log for the weekend crew and have talked with those who build them on our end. In some cases these are cracking just by putting the 2 washers and bearings into the part without even tightening them down. Looking at the washers used for this build appears that not all washers are the same thickness and vary from about .05 to .27 mm difference. Though this is no surprise as I'm sure this has always been the case. I feel that it may point to the tolerances between the plastic part's mounting points has changed.
@seadogbrian Thank you for the report, we appreciate all feedback we can garner. We truly feel your pain as well! We have about 100 different STL files sliced for production on 3 different printers, creating about 300 gcodes we needed to go back and re-verify for cosmetic, strength, torque out, and pull out tests.
Apr 7 2018
Apr 6 2018
sorry for the double post... not sure how i did that...
The most current lulzbot cura/firmware update notes that updating may break old gcode files... In chatting with lulzbot on instagram about this issue the apparent reason is that the coordinate system had to be changed to solve another issue.
Apr 4 2018
Feb 26 2018
We are sorry to have missed this message! We are no longer developing Cura 21.08 and have since moved onto the Cura 2.6.xx builds and are currently working on a Cura 3.2.x release. You can find the latest release version of Cura LulzBot Edition here: https://www.lulzbot.com/cura and all developmental builds here: http://devel.lulzbot.com/software/cura-lulzbot/
Jan 30 2018
Jan 16 2018
Fixed in Devel for FreeCAD 0.16. Close ticket.