berend

It looks like there are two parameters witch determine the volume: length and diameter. as far as i understand, Flyguy is talking about the length: with the force sensor you measure the force on the tube and from there you can calculate the length deviation of the bowden witch stands for a length deviation of the material volume. The measurement and calculation seems quit complex to me but really add value. A cheaper and easier way can be a feed forward in your extrustrusion (extruder acceleration: force on bowden: longer bowden: needs higher set point and visa versa) The bowden can be approached like a spring and we can predict its reaction an anticipate on it. On the other hand: Joergen and thedudevt focus is on filament diameter variation. I don't got a clue what the diameter variation profile looks like and how big is the impact on the extrusion result ? In other words: how big are the diameter differences and how local are they ? And another question from myself: Does anyone has a good document where the hole extrusion process is described? That means: from G-code to firmware calculations to motor steps to extruder gear ratios to nozzle extrusion. Grtz, Berend

Ook van belang is het model Ultimaker (lees: electronica) je hebt. Heb je toevallig een UM uit de 1e of 2e workshop ? Wat is het model van je electronica ? Berend

All, In my opinion the hot-end 'bowden-peek-brass interface' not the most serviceable part of the UM. Inspired by your idea, I picked up an older project I did some months ago despite my hot-end was working fine. - I tapped thread in a teflon hose so it can be screwed (?) inside the Peek and there it meets the brass tube. - The other end of the threaded teflon I connected to the bowden tube with a printed interface (funnel on bowden side and thread on teflon side) - The bowden is pushed in the funnel by Owen's : http://www.thingiverse.com/thing:11864 (what a piece of art is this, perfect) I know that nobody can understand the above told story so i added some pictures. (sorry for the sizes) The first test i printed (an easy one) was perfect, second test is running OK at this moment, so i don't know how reliable it is on the long term or with difficult prints. To be continued, Berend

Hi, i'm using a version 1.1 PCB in combination with an Arduino Mega 2560. At this moment it's running with Marlin firmware which was re-adjusted by Bernhard/Hendrik for a combination of 1.1 PCB with Arduino 1280. (2nd workshop config) Should i be able to use Marlin v1.0.0 B with my config ? Thanx, Berend

I assume u mean 'Max Z acceleration' from the machine menu. If this is not correct i'm curious where to find the 'Z acceleration' adjustment. Paul, sry, next time it's 'Paul's profiles' Flo, your such a modest guy Greetz, Berend

All, I examined the influence of the Netfabb option 'Toolpath->Override->Speed' on the generated feedrate for Z. Here my results: 1. The Z feedrate is affected by the Speed override. 2. The feedrate is override is calculated after Max. Z acceleration calculation. vf-low-poly-bow-tie.zip Next focus is on Z feedrate generated by SF. Have fun, Berend

Troubleshooting on the height deviation of my objects (Z axis problem) it looked at the generated code, in particular the Z moves. The goal is to find out how a z move is defined in Netfabb gcode and what values are used The approach was generating Gcode files, extract the lines where Z motion is defined and examen these. The victim of my research was a cube of 1x1x1 mm. (no cubes were harmed in this research) Result: 1. Z moves are classified as 'fast jumps' by Netfabb (Toolpath -> Visualisation -> Display fast jumps) 2. Moves (G1) with a new Z setpoint have allways the same X,Y and E as the previous step. So: Z is always moving 'alone' and is not used for printing. (This is a difference with SF where Z is moving together with X and Y) 3. With 3 of Florians profiles (Hollow standardQ, Hollow HighQ and Hollow UltraQ) the feed rate for z was the same for all profiles: 1200 So: Z moves are profile independend (for the used profiles) 4. Another parameter: Machinetype -> ... -> General Settings --> Max Z acceleration (m/s2) - can be adjusted from 0.01 to 10 -Effect of the 'Max acceleration' setting on the feed rate is displayed in the graph: HipChat-3.0.13-139.zip Conclusion: In Netfabb I can define my G1 Z feedrate from 200 to 1200 using Max Z acceleration How this results in my printed object depends of ReplicatorG, Firmware and my mechanics. Remarks: 1. Each Netfabb gcode line is filled with Z data despite its only relevant when Z motion is desired. (if communication bandwith is a problem whil printing, these Z positioning data can be filtered away easily) 2. The Max Z acceleration parameter has no influence on the Z feedrate of the gcode header. Have fun, Berend update: i just came into my mind that there is also an speed override function in Netfabb. That is my next focus.

Hi, Sprinter indeed is a firmware hack with several improvements and a different approach of positioning. In stead of moving steps step if creates a path with a acceleration-speed-deacceleration. See: http://wiki.ultimaker.com/Sprinter_firm ... _Ultimaker Sprinter has a derivative called Marlin. A it finds it key to succes in trying to keep speed constant by looking ahead in your printing sequence. See: http://wiki.ultimaker.com/Marlin_firmwa ... _Ultimaker For more close to source info and Flattr: http://bernhardkubicek.soup.io/ (Ian, be sure you had your valium before you visit this site Have fun, Berend

Hi Toni, Thx for thinking, but... the place of the header/footer you describe is the same i described in the 1st post. The header you can define here is like an 'extra' header/footer. It's placed to the top (header) and bottom (footer), additional to a Netfabb generated header/footer. So the complete header/footer consists of a user defined part AND a Netfabb defined part. For me it's interesting to know how this Netfabb generated code can be manipulated. I like to have control over the full header and footer including the Netfabb part. Looking forward to your experience with this, Berend

Thanx Dave, My reaction and some new questions The starting Z position is fine and reliable, the total object height can deviate up to +15%. Personally, i don't know about Gcode Small but it is and was always ON and i've got the same issues with Netfabb. A rootcause can be found by overshoot from Z position: the energy thats needed to stop the platform from moving down cannot be delivered - Electronics: poor stepper driver adjustment. - Mechanical: speed too high - Software: Z feedrate too high - Firmware: PID not optimal (Do the PID settings cover the 2 different Z spindles?) - Firmware: Does the PID take into account the gravity as present force ? Acceleration is no part of slicing but defining speed is. So it's good to know there is at least 1 user parameter to control Z motion. If only a limit can be set, who/what defines the operating Z feed Rate? What is a fail-safe Z Feed Rate Limit? (actually Acceleration is something usually done in FW, not in the slicer although Netfabb has in it's Machine/Extended Setup menu a Z Acceleration limit. Confusing) Thx

All, Every now and than, i experience Z positioning problems. The height of my prints is not reliable, sometimes caused by positioning overshoot, sometimes by missing steps. For troubleshoot purposes i'd like to play with Z positioning/speed/acceleration. 1. Is there a way to play with these parameters in my gcode generators (SF/Netfabb) or must i do this in the firmware (Marlin)? 2. I've got a old type of Z-spindle, the ordinary 8mm thread. Does this need special attention in settings ? 3. How is Z motion defined ? is it 'just' making an amount of steps/distance or is there a control loop with a position/speed/acc profile ? Thanks, Berend

Netfabb generated gcode contains a 'fixed' header and footer witch u can expand with a user defined gcode header/footer (Machine/...Extended Setup/Ultimaker specific) The Netfabb header contains homing (G28), temperature setpoint (M109) and some more things. I'm looking for a way to manipulate or turn OFF these Netfabb header, so i can use my own sequence. Anyone ? Grtz, Berend

Hi all, to keep things a bit clear i made an Ultimaker mindmap. Maybe it's a good tool for new Ultimaker operators. I cannot upload the file to this forum, the file extension is not accepted :( so I uploaded it to thingiverse: http://www.thingiverse.com/thing:13060 For view/edit the map i use Xmind ( http://www.xmind.net/ ) greetz, Berend

Do you preheat manually before building the code? -> Yes. Greetz, Berend

Hi, i'm no expert but as far as i know: 1) How do I know which start.gcode SF uses? On my system (Mac OS) in the ReplicatorG25 directory, each skeinforge engine has its own directory with /prefs in witch different (gcode generator) profiles are stored in separate directories. In each profile directory is a subdirectory called: alterations. In directory alterations, the start.gcode and end.gcode are stored. /ReplicatorG25/skein_engines/skeinforge-35/skeinforge_application/prefs/SF35-ULTIMAKER - Quality print/alterations/start.gcode For ReplicatorG24 it's different; its a file in a hidden directory in the root: /Users/Username/.replicatorg/sf_31_profiles/Dupli ULTIMAKER - ABS - Q/alterations So, depending on witch RepG, SF and profile you use a different stored start.gcode is used. 2) I can imagine some people wrote there own start and end files. I'm really interested in those codes! A code i use: G21 (Metric: The unit is a millimeter) G90 (Absolute Positioning) G28 Z0 ;physical home Z G92 X0 Y0 Z0 ;This is zero G91 G1 Z25.0 F400 ;Move down platform 25mm with speed 400 G92 E0 (zero the extruded length) G1 F1000 E260 ;Extrude material G1 F3000 E-20 ;A little pullback of fillament G92 E0 (zero the extruded length) M1 (Clean the nozzle and press YES to continue...) G1 Z-24.0 F400 ;Move up platform 24mm with speed 400 G1 Z-1.0 F100 ;Move up platform 1mm with speed 100 G90 G92 E0 G1 E0.00 M104 S220.00 ;Temperature set I don't know if it's perfect (especially regarding the extrusion length) but it works fine for me. Greetz, Berend