greengecko

And greetings to good old leipzig. (I lived there for about 10 years) Cheers

Or t just changed color from black to white ....;-)

Hi, I just checked the shop about 5 minutes ago and the new dual extruder kit was there. and then it was really funny. I added it to my cart and then it was gone again. I could look at 2 photos for about 2 minutes and then the whole kit was gone from the shop. Any idea if this is a bug or if it was just a test ? Anyone else saw it, or was I just dreaming?

I noticed that the csv table does not show correct. here is a screenshot.

Hi, I suggested this a while ago to Daid (but he did not respond, so he was either busy or did not think it was a good idea). I had the idea especially because SteamEngine is so fast, that it would be great to have the ability to have different profiles during prints (at least switch the profile between layers). My idea was to define via a table of the following style: file to.mm profile cubetest (= a csv file (e.g. created in Excel, germans be aware csv means comma seperated not ;" which is used in the german excel version and would not work) The table defines which profile should be used at which model height (in mm). As I did not write my own slicer (which is not an easy task I guess :wink: ) I took advantage of the steam engine speed. I sliced my models using different settings and saved them as different gcode files (e.g. cubetest1, cubetest2, cubetest3 for three different profiles using different infill settings, layer height etc.,) The table above defines then at which height (in mm) of the model which profile should be used. Then I run my R script (I use R because I am most familiar with it) and let the script combine them into a single file. In principle you could do it by hand but it needs some calculation if you need different layer heights. The script is only partly intelligent. It checks only if there is no available layer and then searches for a common layer height where it can swap the profile. An example would be, you start with the first layer at 0.3 (default in Cura) and then 0.2 mm as the layer height, but would like to change to a layer height of 0.3 mm at 1mm. This is not possible, because if you add 0.3+0.2+0.2+0.2 then you end up at 0.9mm or 1.1mm but not 1.0 mm height. So the script searches for the common layer height in the profiles (in this case 0.9, because 0.3 + 0.3 + 0.3 = 0.9) and switch at 0.9 mm to your new profile. Otherwise it is pretty stupid, so if you want to print with 100% infill over a 5% infill then you probably will have trouble. Also other inconsistencies may occur. It is still in a testing phase, it ran fine with my tests. Be aware that rapidly changing the layer height is not a good idea because of under/overextrusion so change only via modest steps. You are allowed to use as many profiles in one models as you want, so define intermediate steps and do not change layer height from 0.1 to 0.3 in one layer. If there is some interest I am happy to provide a more elaborated manual and upload it to youmagine. I kind of back-engeneered Daids gcode, so if he decides to change his comments in Cura the script will be lost..... Instructions: Below I copy/pasted the R script. So to run this you need [*]R (http://cran.r-project.org/).[*]Save the script as e.g. ultibaker.R and [*]create a csv using the format above (Make sure you use exactly the same headings otherwise I will not work) [*]Create different profiles of your model and save them in the same folder. Name them with consecutive numbers and the filename your provide in the csv file, e.g. frog1.gcode, frog2.gcode, frog3.gcode etc. Start with 1. [*]Run the script (copy/paste it into the R console), it asks first for the folder and then for the csv file. [*]This will create a new file called "file_baked.gcode" in your folder. [*]Print your model using this new file Obviously observe the printing as I provide no guarantee that it works . USE IT AT YOUR OWN RISK! Happy to get feedback and even more happy if this idea will be at some stage integrated into Cura if agreed to be useful. Cheers, greengecko ############################script starts here############ path <-choose.dir(default = "", caption = "Select folder") setwd(path) settings <- read.csv(file.choose()) fn <- settings$file[1] def.heights <- settings$to.mm qualities <- settings$profile nof <-length(unique(settings$profile)) files <-list() lay.height<-NA lay.tot<-NA ####### load files and determine layerheight for (i in 1:nof) { con<-file(paste(fn,i,".gcode",sep="")) files[] <-readLines(con) close(con) index <-grep("Layer height:",files[]) layerstr <- files[][index] lay.height<-as.numeric(strsplit((gsub(";Basic settings: Layer height: ", "", layerstr))," ")[[1]][1]) #find model height index <-grep(";total_layers=",files[]) layerstr <- files[][index] lay.tot <-as.numeric( gsub(";total_layers=","",layerstr) ) } ##################################################################### #lay.height=lay.height*1000 ##################################################################### # put together at layer heights i<-1 xx<-files[] a<-regexpr(" Z",xx) hhh <- xx[a>10 & a<30] ind <-a[a>10 & a<30] hh<- as.numeric(substr(hhh,ind+2,ind+6)) model.def <- data.frame(seq=hh, l1=1) for (i in 2:nof) { xx<-files[] a<-regexpr(" Z",xx) hhh <- xx[a>10 & a<30] ind <-a[a>10 & a<30] hh<- as.numeric(substr(hhh,ind+2,ind+6)) dl <-data.frame(seq=hh, x=1) colnames(dl)[2] <- paste("l",i,sep="") model.def <- merge(model.def,dl ,by="seq", all=T) } ############################################ #define your model ############################################ #cat("Define your model from: 0 to",max(model.def$seq), "mm\n") for (i in 1:(length(qualities)-1)) cat("To",def.heights,"mm : Quality",qualities,"\n") #add the last quality for the virtual last layer+1 qualities <-c(qualities,qualities[length(qualities)]) ######## adjust if not possible and find layer chunksto=NA getlayto=NA getlayfrom[1]=0 for (i in 1:(length(qualities)-1)) { #if (i==1) from=1 else from=which(model.def$seq==def.heights) to = which(model.def$seq==def.heights) dummyto<-model.def[1:to,c(1+qualities,1+qualities[i+1])] chunksto<- max(which(dummyto[,1] == dummyto[,2])) getlayto <- sum(model.def[1:chunksto,1+qualities],na.rm=T) getlayfrom[i+1] <- sum(model.def[1:chunksto,1+qualities[i+1]],na.rm=T) } i=1 outfile<-character() #get start code from first file indexto <-min(grep(paste(";LAYER:",getlayto, sep=""),files[[qualities]])) outfile <- files[[qualities]][1:indexto-1] for (i in 2:(length(qualities)-2)) { indexfrom <-min(grep(paste(";LAYER:",getlayfrom, sep=""),files[[qualities]])) files[[qualities]][indexfrom] <- paste(files[[qualities]][indexfrom] ," QUALITY:",qualities," LAYER HEIGHT:",lay.height[qualities], sep="") indexto <-min(grep(paste(";LAYER:",getlayto, sep=""),files[[qualities]])) outfile <- c(outfile,files[[qualities]][indexfrom:indexto-1]) } i=length(qualities)-1 indexfrom <-min(grep(paste(";LAYER:",getlayfrom, sep=""),files[[qualities]])) files[[qualities]][indexfrom] <- paste(files[[qualities]][indexfrom] ," QUALITY:",qualities," LAYER HEIGHT:",lay.height[qualities], sep="") indexto <- length(files[[qualities]])-1 outfile <- c(outfile,files[[qualities]][indexfrom:indexto-1]) con<-file(paste(fn,"_baked",".gcode",sep=""), open="w") writeLines(outfile,con) close(con) ############################script finishes here############

I agree with snowy. And something else which I have mentioned probably more than a year ago is their lack of telling anyone of their developments. Not wanting any deadline or anything (though this would be nice and professional) we have not really a clue what is going on. Why not reporting on the development and tries. Sure they could benefit from some of the knowledge of the fora. Dual extrusion seems to be in the pipeline but why not having a simple table like snowy's above and give an order of priority. This list should be prominent on ultimaker web page and updated so people see what is going to come. maybe some red/orange/green indicator how far of development from offering is. What about a heated bed (actually just curiosity as I build my own). The marketing is really poor (still waiting for a site where all videos of ultimaking events are listed). Belt tensioner (one person should simply test the designs and give some official recommondation, I am sure they tried some of them, but they do not take community development seriously?!) So I completely agree they really risk to be left behind if they do not change and have a faster turnaround and involve their community better.

as far as I know (check the latest update movie) they are still developing the machine and it is not finished yet. Sold out means currently the only work on kickstarter machines and will accept no further orders at this stage. Once everything is shipped people can order machines from their website. But I think it is a good idea to wait until I heard something about quality (tolerance of filament width)

I give up. Very disappointing. No tiny response or anything after 4 weeks. ( except Diad as always). Is the maker fair still on?

Not sure why you spent 3000$ I have an ultimaker in Australia and upgraded it with V2 nozzle and extruder. Shipping isa bit dear but twice the ultimaker price seems a bit high. So how big is the print? What is the speed and I would be interested into a more color print. Happy printing.

Thanks Daid.

I really like the different speed. Setting. One step closer to allow different qualities within a print.

Anyone out there who knows if a video was shot at the event? Just a simple yes or no would be nice.

HI Daid, That is a tough questions. I personally really like the speed, but still missing some things. E.g. plugins color change does not work (others I did not test I assume it is the same) and also some other features (half layer steps at the outside to have a better quality there). This (the skinning) is in my view something that I really miss and therefore I would not use the steam engine for most of my prints if I want to have quality. On the other side for standard prints it is really superfast and great (minus some infill jumps which potentially can be problematic if the model is ripped of , though that did not happen so far). So if you release it I would clearly mark it as a beta release and let people know that due to the nature of a beta people should be catious and for example should not print larger prints unsupervised. Also it would be good to let users know what features are still missing so they can judge by themself if they would miss something. Having said this I think the new slicer is really superfast and therefore will be very appealing to most people if they do not want to use too many advanced settings.

Another request It would be great to have a possibility to start t a higher layer ( for interrupted prints)

Are there any videos on the last ulti evening from 6th of May? Is there a repository of links to all videos. I cannot find a site and theyseem to be quite scattered across sites.

Hi Just an idea. If I understand correctly a wipe tower would be a structure that needs to be printed with the model i.e. It uses plasteic and moreover slows down the print. Wouldn't it be easier to have a structure like a post in a corner of the print bed which triggers a mechanical swip from something that is attached and retracted via a spring at the print head. This would relax te necessity of a wipe tower.

I would through in my hat in the ring as well.

I sincerely agree on the different layer heights, speeds within one print. Should not be too hard to have a post "plugin"-type extension that allows the user to specify different layerheights (quality setting height and speed) for different layers. In an advanced setting it would be even better so be able to select different parts of a model (like a lasso on the surface with a defined depth ) and change the quality setting (height and speed and extrusion) for this part/surface of the model. Otherwise slicing speed is great but a nice visualisation that points out potential problems (such as overhangs) is also very important. Also to allow for a start and finishing point would be great, because sometimes the end points is somewhere where you just do not want it to be. An implementation could be to add a finishing point one layer higher then the last model layer so the path algorithm should be able to find an ending of the path below the specified endpoint. Reverse should be true with the starting point (default closest to edge x,y = (0,0)).

Thanks for the useful hints. I will try this weekend and let you know how I went. Cheers, greengecko

Hi, could not find an answer to this probably earlier asked question. So, to avoid warping and to have a sometimes prefered non-shiny smooth surface at the buttom, does it help to print PLA on a layer of heated blue tape? If so what is a good temperature to start with. Thanks in advance, greengecko

Hi , Not sure how good your german is, this might help ( and i tried it, works great) http://www.thingiverse.com/thing:26746 There is also a description in english on thingiverse (but i have not tried this) http://www.thingiverse.com/thing:12915 May be there are even more if you search for 'terrain' on thingiverse. Good luck.

Am besten Cura verwenden. Das ist fuer den Einstieg am einfachsten (verwendet den gleichen Slicer wie ReplicaterG) Hattest du bei netfabb das modell in den build bereich gezogen. Es hoert soch so an als ob du nur das raft hast slicen lassen.

First success i have my heated bed working. I am using This as a heater: http://store.qu-bd.com/product.php?id_product=30 Works great. One thing i noticed is that the temp reading of the thermistor is quite off Heating to 50C using the ulticontroller results something of about 65-70C I am using the 100k Thermistor table (option 1) in the marlin firmware. Fro the website of the provider i get the following info (see below for all details) 100k thermistor, beta3950k and i soldered a 4.7k Ohm resistor to the board. Can anyone direct me to which thermistor table can i use? Or would i need to meassure the resistance and temperature and establish my own curve once i somehow work how what the conversion from resistance to arduino value is? Any idea is apprciated. I know i could just find the correct settibg using try and error. Final question is 60 degree for PLA a good bed temperature? Thanks in advance P.s once i get my borosilicate glass I am happy to share my experiences with my heatedbed. I used a smaller 3mm normal sheet and it broke when i tried to get my print off the glass ( the was no plopp effect...) not during heating... You are looking at the heating element for your 3D printer's bed. This is a premium silicone rubber heater, normally used in industrial environments to heat large tanks of liquid. We had these custom made to be the fastest, most evenly heated elements available. They include a built in 100k thermistor for accurate readings with easy setup. They run off 12v power so no dangerous voltage and they CAN be run directly with some electronics (some electronics may require a relay due to the current draw). We have tested these with a Azteeg X1 and X3 from http://www.panucatt.com as well as the RAMPS 1.4 directly with no problems (YMMV). These heaters are flexible and WILL REQUIRE a flat build surface such as glass to mount to. 200mm x 200mm / 8"x8" Durable Silicone Rubber Construction Extremely Even Distribution of Heat Industrial Duty Cycles For Long Life Heats To 120 Degrees C in About ONE Minute (assuming adequate power supply) Integrated 100k Thermistor For Accurate and Reliable Temperature Readings Integrated Thermistor Beta Value 3950K Thermistor Leads Are Insulated and Ready To Go

I would put it simply, if you print it standing up you can use the higher resolution of the z axis. If you lay it down you could have some problems with warping of the sides (depends how solid you need the print) and also you most likely see some steps on top (also you need retraction). So I would also opt for standing up.

I had a similar experience. A great printer and then too less extruion after the first layer. Finally i found I had a plug in the hoted (only small but obviously enough to cause too much friction). So after cleaning i worked again. but I guess you have already checked when you changed your tube. Another reason could be a too thin filament diameter. Can you meassure your filament? If so adjust the value to the slicer, but make you meassure it at more than 3 points. I also ad here some problems lately.