skirtby Triffid_Hunter - Firmware - experimental, borrowed, and future
we would of course tie the endstop condition flag to the direction the axis is moving in!by Triffid_Hunter - Firmware - experimental, borrowed, and future
Did you do your volumetric calibration properly? ie when you extrude 100mm, does it push 100mm of filament into your hot end? (do this with the nozzle removed and heater disconnected or you'll waste heaps of filament)by Triffid_Hunter - Firmware - experimental, borrowed, and future
I like the way sprinter handles endstops. It keeps track of actual position, so when the endstop condition is cleared we don't need to rehome, and the print can continue without interruption. I've had wires come out of my electronics, or break, far more often than actually hitting an endstop during a printby Triffid_Hunter - Firmware - experimental, borrowed, and future
teacup supports absolute extruder codes, just define E_ABSOLUTE in your config.h perhaps this should become default now that sfact and skeinforge add in G92 E0 to prevent overflowsby Triffid_Hunter - Firmware - experimental, borrowed, and future
Andrew Diehl Wrote: ------------------------------------------------------- > While the Z (and possibly x and y) axis is homing, > the extruder does not regulate temperature and > leaves the heater in whatever state it was at when > homing began. If homing is interrupted (like by > disabling the steppers) the extruder can overheat. That would also be fixed by hooking homing into tby Triffid_Hunter - Firmware - experimental, borrowed, and future
nophead, any thoughts of the repeatability of where a microswitch first triggers, vs where it releases? ie; in teacup firmware, we hit the endstop fast, then back out really slowly and use the point where it releases as zero. Sprinter hits the endstop slow, backs out and hits it again, and uses that trigger point as zero, rather than the release point. Kliment tells me that the trigger point isby Triffid_Hunter - Controllers
Traumflug Wrote: ------------------------------------------------------- > One way to get an adjustable fan is to define it > as a heater with the just recently introduced > TEMP_NONE dummy-sensor. Then you can run your fan > with M104 S1 ... M104 S255 and turn it off with > M104 S0. TEMP_NONE isn't reliable with M109 yet, > I'll have to investigate that further. Teacup will hby Triffid_Hunter - Firmware - experimental, borrowed, and future
hall effect sensors are starting to show up, if you're interested in magnetics. Add a comparator with a little hysteresis and feed it into your existing endstop inputsby Triffid_Hunter - Controllers
NoobMan Wrote: ------------------------------------------------------- > The point which i still dont understand, is why > with acceleration, sometimes it tries to move Z at > the speed of XY. I dont see the point of Z being > part of anything, since Z is simply independent. > There is no Z move combined with anything else, so > acceleration should be limited to X+Y+E while at &by Triffid_Hunter - Firmware - experimental, borrowed, and future
I mostly use openscad for reprap things, it's CSG for programmers I might pull out blender for the odd organic shape or other fancy technique, there's an excellent blender precision CAD tutorial over at You could probably cobble a printer together for $500-600 if you do your research (come chat to us in irc://freenode.net/#reprap ) and get different pieces from various suppliers. If that's nby Triffid_Hunter - General
NoobMan Wrote: ------------------------------------------------------- > In the acceleration computing, why does the Z > speed get mixed with X/ Y ones. Why not just > buffer 3 different values for each axis for last > speed, so (for example) when the Z starts move > will just accelerate from the last Z speed > recorded instead of last X or Y speed. all axes start at zero. theby Triffid_Hunter - Firmware - experimental, borrowed, and future
Here's my start and end, which I've spent a while tuning: remove the comments, those are for reading pleasure only note lack of temperature stuff in start- I set that manually in pronterface before each print, different plastics need different temperatures! eg my green PLA prints fine at 205 but my orange PLA needs 213... start.gcode: G92 E0 ;reset extruder G1 X180 F9000 G1 Y100 G1 X205 Z0.2by Triffid_Hunter - General
just go through them a few at a time. If your print quality is decent, sell what you don't useby Triffid_Hunter - General
with or similar you wouldn't even have to take the rod out, just loosen, unclip, move the nut to the other sideby Triffid_Hunter - General
according to chrome 14.0.835.126 reprap.org/mediawiki/images/8/86/RFT_timeline2006-2012.svg This page contains the following errors: error on line 5395 at column 43: Namespace prefix inkscape for groupmode on g is not defined Below is a rendering of the page up to the first error. I get some axes and the mendel 3d view in the top left, but no graphby Triffid_Hunter - General
techzone is well known to be less than stellar quality. try ramps if you do decide to cut your lossesby Triffid_Hunter - Firmware - experimental, borrowed, and future
it should be defined in your config as REFERENCE_AVCC.by Triffid_Hunter - Firmware - experimental, borrowed, and future
4) tell people to use teacup's built in retraction instead of skeinforge retraction, perhaps get skeinforge to emit retract/reload markersby Triffid_Hunter - Firmware - experimental, borrowed, and future
rename the config.ramps.h to config.ramps1.2.h or something (hint: use git mv so the rename hits the repository) and add your config.ramps1.3.hby Triffid_Hunter - Firmware - experimental, borrowed, and future
clean up the patches in a local branch, push to your github fork and send me a pull requestby Triffid_Hunter - Firmware - experimental, borrowed, and future
Converting cubic beziers to straight line segments isn't hard. just pick a decent sized step. See the fantastic animations on wikipedia for conceptual overview.by Triffid_Hunter - Firmware - experimental, borrowed, and future
lstu012 Wrote: ------------------------------------------------------- > I'm trying to use an arduino mega1280 but I am > getting this error: > > dda.c: In function 'dda_start': > dda.c:412: error: 'AI012_WPORT' undeclared (first > use in this function) you need to use a font in which O (letter oh) and 0 (digit zero) look different. I do, and I could see your problem within aby Triffid_Hunter - Firmware - experimental, borrowed, and future
Sublime Wrote: ------------------------------------------------------- > This would > even allow you to use the same gcode for 1.75mm > filament as used for 3mm and make the gcode more > transferable between people the same way we share > stl's. If only it weren't for that pesky layer height...by Triffid_Hunter - Firmware - experimental, borrowed, and future
I didn't get the point at first, but this is going to be necessary for multiple extruders to work well. As you said in the other thread, feed skeinforge a bogus diameter so it spits out E in some volume unit (mm^3 would probably be good), then do volume->length conversion in firmware using a conversion factor provided in g-code, or associated with a particular toolhead and recalled with M6 T1by Triffid_Hunter - Firmware - experimental, borrowed, and future
I was hoping you'd come up with situations where it would be useful Varying plastics mid-print seems to be on the cards, and kliment's prusa M12 has a dual extruder carriage, and now that we're getting pretty good with extruders I think dual heads will start becoming more common. Embedding plastic properties into a gcode file would help enormously with getting those to work, especially if youby Triffid_Hunter - Firmware - experimental, borrowed, and future
I see this as part of tweaking skeinforge/sfact settings. if the slicer is spitting out wrong values, the slicer needs to be adjusted. Adjusting in firmware just separates the problem from its actual source and gives mere symptomatic relief, like taking pseudoephedrine to reduce mucus production when you have a cold. I much prefer to tackle problems at their source, rather than giving the optionby Triffid_Hunter - Firmware - experimental, borrowed, and future
or something as simple as case 226: for (uint8_t debounce = 0; debounce < 8; loopstuff()) if (READ(RESUME_PIN)) debounce++ else debounce = 0; perhapsby Triffid_Hunter - Firmware - experimental, borrowed, and future
heh you could go the virtual heater route, it is a bit roundabout though. implementing pause would be better. simplest way would be a small addition to queue_step() similar to waitfor_temp that hangs on a digital input, your resume button. You could use one of the endstops if you want to quickly knock together some code and try it out soft-resume would be a shade trickier, need to prevent the qby Triffid_Hunter - Firmware - experimental, borrowed, and future