a moderator would have just nuked the post out of existance rather than editing it out.
It isn’t Kapton. It is like the previous one, but from a new manufacturer, and it has our logo silkscreened on it. It uses the Honeywell thermistor that is in the Buda.
-Jeff
Thanks for all the great comments here, especially elgullitch’s great analysis.
We do spend time thinking through release timing and pricing. This can always go smoother and we are continually refining the process. The main concern is to push out new improvements quickly, and drop the price when possible.
Although it seems like a short period, we have gone through a significant transformation since TAZ 1. Before, we were much more dependent on the capacity (and will) of contract manufacturers. We now have a new building and have taken this in house. Our production speed & volume is increased, the cost is less, and the quality is improved. Nearly all of the TAZ 2 were built in the new facility. TAZ 2 were going to be built at a contract manufacturer, but they were hit in a flood: http://devel.alephobjects.com/wp/video/wp.webm
In sum, we’re improving the product, increasing quality and quantity, while reducing the price. 
Printers have the same return policy as any other product. The full policy is on the store website.
Thanks!
-Jeff
I’m not sure what the full story is there. I just came into this thread now, and as I was reading through it, I saw he had a bunch of posts that just had “—”. I clicked on his username, clicked on the show all posts by user button or whatever, and saw that every post he had was a “—”. I assumed it was a spam account or something. So I was going to ban the account, but got lazy and didn’t (I normally don’t do forum moderation though I have perms). I did delete around 5 of the “—” posts. Then I saw your comment here. I don’t know what he posted or why they are “—”. We’re not censoring posts.
Normally to censor on my servers, you have to bring an arm of the state.
http://w2.eff.org/Censorship/Indymedia/
-Jeff
Oh, I should also point out, we are working on doing upgrade paths of various improvements from version to version. All of the info is there, so users can do an upgrade themselves. But we’d like to package it up cleanly as a low cost upgrade between versions. For the TAZ 2 to 3 upgrade, this is a bit tricky as it requires a new power supply, a new heatbed, and also a flashing of the firmware.
The upgrade instructions will be created using OHAI-kit, which you can demo here:
http://ohai-kit.alephobjects.com/
The build documentation, the OHAI-kit software itself, are all released under free software/documentation GPLv3 and CC By SA licenses.
Along with upgrades, will come some of the toolheads we’ve discussed in this forum, but in a nice shiny box (e.g. things like dual & flexystruder).
Thanks,
-Jeff
Feel free to do so. Email support@lulzbot.com to get an RMA.
Thanks,
-Jeff
Edit: I should also point out, if you have a question about a return of your product or something like that, it is way better to email support@lulzbot.com than post here. If it gets mailed there, a ticket gets created. The forum is more for discussion.
I removed the posts on purpose, I did so because everyone seemed to completey disagree with my viewpoints, so even though they were all from existing customers and seeing that none of the new customers were chiming in (which did happen later) I figured I would just remove my posts since at the time I felt I was the only one that felt this way then there was no reason to leave this on the forum to be crawled by Google considering I still believe in the company Even though I did not agree with this recent strategy. By the time others were coming on and voicing their opinions I had already went ahead and removed them.
I do not want to return my TAZ 2.1, but other than the printbed and power supply, what are the differences? Can I just flash the firmware on the 2.1 and use the 3.0 files? I’d assume not, but I saw under the 3.0 folder some new config files, which I’m itching to try.
I was wondering what those were because u see 3.1 and I think 3.2, is that firmware? Are we supposed to be flashing the firmware each time with every latest release
Other than the 24V and power supply, the differences are minor. It has a few fewer printed parts, just so we can build faster–it should have no affect on operation.
You don’t want 3.0 firmware on a 2.x series. This is one of the main reasons we made the version number jump was to keep 12V firmware separate from 3.0 firmware (which required 24V). The firmware may be a bit newer, but the main change is just the 24V. I don’t know of any other changes offhand (the details would be in the git logs).
-Jeff
Don’t flash a 2.x system with 3.x firmware. The 3.x firmware is set for 24V. You likely don’t need to touch your firmware (unless you want to, of course).
-Jeff
I am curious, if the change was so minimal why bother going from 2.0 to 2.1 to 3.0 and not just go to 2.2
Going from 1.0 to 2.0 had a pretty considerable and sizable change so most would consider the jump from 2.1 to 3.0 was to be equally considerable. Unless this was all just for marketing purposes?
The other thing is I have been told to check forums for changes, new improvements etc, in checking the forums now, I am not seeing bulletins of changes, announcements, etc , instead you have go through topic after topic and dig in several pages. Would it be possible to put in an “official” firmware and hardware changelog.
While I understand there is http://devel.lulzbot.com/ its just an open directory with files which I cannot seem to find a readme or documentation on changes. I know there are always changes, but there are final milestones which are completed such as 2.0 , 2.1 and now 3.0 so couldnt there be on official milestones documentation or changelog so customers can see the changes in both software and hardware improvements.
Just a suggestion, but of course feel free to ignore
Because of the change to 24V. We wanted it to be much clearer that there was a change there, since it affects the power supply and the firmware. It is much easier for folks to remember we made the change at 3.0.
We could definitely do a better master CHANGELOG between versions. Instead it gets pushed into various changelogs in sub directories, if at all. The spec sheets and such all get updated, so they could be compared.
The final archival versions of 1.0, 2.0, 3.0, etc. all get stored on http://download.lulzbot.com/
For instance, this is the version for the TAZ 3.0 release:
http://download.lulzbot.com/TAZ/3.0/
If we do new parts for TAZ 3.0 it in the months down the road, they will be put in devel:
http://devel.lulzbot.com/TAZ/3.0/
So download.lulzbot.com will generally be static for a version, once released.
-Jeff
It would be much appreciated if there was a zip file in those folders that had the entire folder contents in them.
A change log needs to be published when you roll revision numbers. I purchased a 2.0 but received a 2.1. I have no idea what the difference is. I would like to know but I do not feel compelled to dig, search and compare part numbers and revisions to determine what changed in 2.1.
A big advantage you have as a manufacturer of these systems is that you are so open with your design. If you roll out a change I want to apply to my system, I can do that. Unfortunately, the current state of your documentation makes it very difficult to determine if a change has been made, what that change was and if it is worth my time, plastic and money to implement it on my system.
Publish a change log when you release a new version! 
I agree we need a better changelog between versions. Full code to both 2.0 and 2.1 is available:
http://download.lulzbot.com/TAZ/2.0/
http://download.lulzbot.com/TAZ/2.1/
The changes between the two is small, overall.
Thanks,
-Jeff
We do have rsync available, if that helps. The full archive is a pretty big .zip.
rsync rsync://download.lulzbot.com/
Awesome that will work a treat. Thank you very much.