Show all posts by user
People building or using RepRaps.
Re: TeaCup M105 not reporting properly / but temperature is stable - 15 years ago
stefanst Wrote: ------------------------------------------------------- > Would you like to hear more crazy hostware > problems? Seems I got plenty :-/ heh fire away, most of my 'development work' involves waiting for money to clear and parts to arrive so I can get my own printer working! > Which may have o do with my preference for running > my reprap off my Windows Laptop for now.by Triffid_Hunter - Firmware - experimental, borrowed, and future
Re: TeaCup Maximum_Feedrate units - 15 years ago
stefanst Wrote: ------------------------------------------------------- > Any idea on why my extruder isn't retracting? Does your gcode contain M101 and M103 words? we use those to trigger retraction and preload. We don't yet the differences between moves at the moment, so we can't automagically decide when to retract and when not to just yet.by Triffid_Hunter - Firmware - experimental, borrowed, and future
Re: TeaCup M105 not reporting properly / but temperature is stable - 15 years ago
glad you got it sorted we have so many problems with crazy hostware :/by Triffid_Hunter - Firmware - experimental, borrowed, and future
Re: Project: Teacup Firmware - 15 years ago
Andrew Diehl Wrote: ------------------------------------------------------- > So when can teacup make the official jump from > experimental to mainstream? when we get a heap of people documenting their successes on blogs and wiki and irc > I've been having the same success as architect. > Damn near perfect prints. lovely! thanks for the report! > Now if only there were a wayby Triffid_Hunter - Firmware - experimental, borrowed, and future
Re: TeaCup M105 not reporting properly / but temperature is stable - 15 years ago
that's extremely unusual, as the heater uses the exact same value that M105 returns. Are you looking at the serial stream, or the interface in your hostware?by Triffid_Hunter - Firmware - experimental, borrowed, and future
Re: RepRap family tree - 15 years ago
I don't like the icons, they add visual clutter without providing any more information than the filled circles. Loving the project though, I'm going to print out one of the landscape ones and stick it on my wallby Triffid_Hunter - General
Re: TeaCup Maximum_Feedrate units - 15 years ago
Sublime Wrote: ------------------------------------------------------- > The firmware is set in "mm per minute" not per > second, But you send mm per second to control it. > > So you need to set your firmware to 40 x 60 = > 2400 As far as I know, all the feedrates are mm/min throughoutby Triffid_Hunter - Firmware - experimental, borrowed, and future
Re: Project: Teacup Firmware - 15 years ago
Hi all, I've merged eeconfig, sdcard and multi-extruder into devel branch for you all to play with. It's not a complete merge, ie there's no provision in eeconfig for multiple extruders or sdcard re-pinning just yet, but please have a play anyway!by Triffid_Hunter - Firmware - experimental, borrowed, and future
Re: TeaCup Maximum_Feedrate units - 15 years ago
Hi, git checkout f555887eb58ca1ad and see if it behaves better, there was a bunch of work done on the ramping algorithm after that commit and I'm having some issues with it too. If that works for you, I'll reset master to that commit.by Triffid_Hunter - Firmware - experimental, borrowed, and future
Re: [AU] miscellaneous printed printer parts - 15 years ago
they look awesome, I can't waitby Triffid_Hunter - Wanted
Re: TeaCup M105 not reporting properly / but temperature is stable - 15 years ago
stefanst Wrote: ------------------------------------------------------- > That's the only way. Spend hours upon hours > building something you could have bought for $20 > more than what you spent on material anyway. > Otherwise what would we learn? my budget for making my printer is very low, so I have to make do with what I have available, or what I can pick up for peanuts.. Alreadyby Triffid_Hunter - Firmware - experimental, borrowed, and future
Re: TeaCup M105 not reporting properly / but temperature is stable - 15 years ago
stefanst Wrote: ------------------------------------------------------- > I made the electronics myself me tooby Triffid_Hunter - Firmware - experimental, borrowed, and future
Re: TeaCup M105 not reporting properly / but temperature is stable - 15 years ago
my readings fluctuate wildly until I added a 10uF capacitor across the sense port. With the impedances as high as they are, not only do we pick up a ton of noise, but the ADC's own sample and hold circuit affects the reading. Do you have this capacitor? Most premade electronics should have it onboard already. The interesting thing about the noise is that it should still center around the actualby Triffid_Hunter - Firmware - experimental, borrowed, and future
Re: Project: Teacup Firmware - 15 years ago
Jens_R Wrote: ------------------------------------------------------- > Did you notice it includes my endstop report > command from earlier as well? ah yes forgot about that, hopefully it doesn't break anything Architect Wrote: ------------------------------------------------------- > My outputs are now very consistant, and > worry free. i set it up hit print after the first > lby Triffid_Hunter - Firmware - experimental, borrowed, and future
Re: Project: Teacup Firmware - 15 years ago
thanks for that, patches pushed to master since they're just documentation changes. I'll fix up other branches in a bitby Triffid_Hunter - Firmware - experimental, borrowed, and future
Re: Trajectory smoothing and acceleration - 15 years ago
I'll have to try it out next time I'm firmware hacking, this page seems to hold the implementation details. I'm interested to see how this would go with maintaining geometry across long move sequences. We've been looking for a move blending algorithm for a little while, looks like we missed that page in our searching, thanks!by Triffid_Hunter - Firmware - experimental, borrowed, and future
Re: Project: Teacup Firmware - 15 years ago
looks great, and we certainly need some better documentation of teacup's gcode specifics! A few suggestions before I commit to the repository: * You've mis-titled G162, instead labelling it as G161 again * Your discussion on feedrates in G1 doesn't really apply to teacup as we suggest using ramping by default rather than reprap acceleration, as reprap accel has numerous issues and is only effectby Triffid_Hunter - Firmware - experimental, borrowed, and future
Re: Project: Teacup Firmware - 15 years ago
Jens_R Wrote: ------------------------------------------------------- > Triffid_Hunter Wrote: > > generating G- and M-code documentation with > > doxygen is an excellent idea! > > Does Doxygen support mediawiki output? no idea, I'm sure there's converters somewhere, at worst html->mediawiki > How different are the firmware > currently in development? Would it makby Triffid_Hunter - Firmware - experimental, borrowed, and future
Re: Project: Teacup Firmware - 15 years ago
Jens_R Wrote: ------------------------------------------------------- > I was thinking about that... I was searching for > the commands to home the axes on > and the Wiki page > seems to be already out of sync with the firmware. > Would it make sense to inline Doxygen-style > documentation comments in gcode_process.c and > generate that page automatically? It could be > aby Triffid_Hunter - Firmware - experimental, borrowed, and future
Re: Project: Teacup Firmware - 15 years ago
Jens_R Wrote: ------------------------------------------------------- > I picked the command number pretty much at random, > maybe there is a more sensible one. heh nope, allocation of numbers is rather arbitrary, and becomes "official" (or as close as we get) when you add it to the wiki pageby Triffid_Hunter - Firmware - experimental, borrowed, and future
Re: [AU] miscellaneous printed printer parts - 15 years ago
Greg Frost Wrote: ------------------------------------------------------- > I attempted to print your parts unattended last > night and had a filament spool jam where the > filament ended up tied in a knot around one of the > spool arms . Ill have another go tonight. yikes! that's not fun! I hope your machine is ok... does that happen much?by Triffid_Hunter - Wanted
Re: [AU] miscellaneous printed printer parts - 15 years ago
heh don't worry, Greg Frost has come though for me, he's relatively local so shipping is far more reasonable than thatby Triffid_Hunter - Wanted
Re: Teacup Firmware replicatorG & Skeinforge - 15 years ago
hariseldon78 Wrote: ------------------------------------------------------- > Just a question: i would like to add a lcd display > to my electronics, and i was thinking to use the > i2c port for this. Could it be possible to move > the extruder motor communications in the intercom > protocol? in that way we could free the 2 i2c pins > and use them for other things.. > I couldby Triffid_Hunter - Firmware - experimental, borrowed, and future
[AU] miscellaneous printed printer parts - 15 years ago
Hi, I'm after the following: * 4x thing:7218 (Greg Frost's ausxmods-belt-compatible pulley) * 3x thing:8574 (Greg Frost's bearing idler runner thingys, sized for a 608 bearing if it isn't already) * 1x attached x-end-motor_M6_fixed.stl which I have modified for M6 threaded rod * 1x attached x-end-idler_M6_fixed.stl which I have modified for M6 threaded rod * 2x attached z-motor-or-bearing-mount_by Triffid_Hunter - Wanted
Re: Arm vs AVR & SD memory card support - 15 years ago
yep, I'm using petit fat revision 8237, albeit with write support. takes about 17k of flash for me. teacup takes about 24k flash, so they both take more than half of the '328's flash. Even with the absolute minimum configuration (basically only mount, open and read), petit fat still takes about 8k flash so still wouldn't fit alongside teacup without cropping teacup's features back by a significaby Triffid_Hunter - Firmware - experimental, borrowed, and future
Re: Arm vs AVR & SD memory card support - 15 years ago
yes teacup has preliminary SD support in the 'sdcard' branch. I'm waiting for a mega to arrive so I can actually test it- can't fit both teacup and the SDFAT libraries onto my '328! I have started another project called 'soupcup' with a totally different approach. One of its features is to pre-calculate most of the per-move math and create a line of gcode including the stored values, with the abby Triffid_Hunter - Firmware - experimental, borrowed, and future
Re: Project: Teacup Firmware - 15 years ago
sliptonic Wrote: ------------------------------------------------------- > I've successfully made the switch to Teacup > firmware and I'm really liking it a lot. Thanks > go to everyone who's answered my many questions. Excellent! > With > Klimentkip/Sprinter and others I've used, the M109 > wait was typical and predictable but with Teacup, > it is much MUCH longer. Eveby Triffid_Hunter - Firmware - experimental, borrowed, and future
Re: Project: Teacup Firmware - 15 years ago
personally I like storing position internally as steps. We only need micrometers or whatever when calculating distance, and M114, neither of which needs full precision. If we run in relative mode with the current code, we'll have wandering as well if steps/mm doesn't lend itself to conversion with no precision loss. Unfortunately we can't store speed as ticks per step, as each axis has differenby Triffid_Hunter - Firmware - experimental, borrowed, and future
Re: Project: Teacup Firmware - 15 years ago
madscifi Wrote: ------------------------------------------------------- > Traumflug, I've taken a look at the patch and I > believe it solves the drift problem (although I've > yet to actually run the code). However, I think > that all uses of x_delta_um in the dda_create > function should be replaced by dda->x_delta * > UM_PER_STEP_X. My argument is that the distance > anby Triffid_Hunter - Firmware - experimental, borrowed, and future
Re: Teacup Firmware replicatorG & Skeinforge - 15 years ago
the gen3 motherboard actually uses the 644p's USART1 for rs422 whereas the ftdi connects to USART0. It has two different usarts. So of course hooking your debug rig to USART0 then trying to talk via USART1 isn't having any effect!by Triffid_Hunter - Firmware - experimental, borrowed, and future