 | | challenge: LEGO copier —Joe Strout
|
| | | Here's an idea I am certainly not equipped to attempt, but I bet somebody is... The user builds some model (constraints: it must be composed of a 1x1, 1x2, and 1x4 bricks in a selection of several colors, and must be flat, i.e. two-dimensional, and (...) (20 years ago, 4-Aug-04, to lugnet.robotics)
|
| | | |
| | | | | Re: challenge: LEGO copier —T. Alexander Popiel
|
| | | | | (...) Ugh. Much harder than it sounds: either the robot needs extreme visual acuity to spot the brick boundaries (so it can tell two 1x2 bricks of the same color end-to-end from a single 1x4 brick... or, more importantly, which order a 1x1 and a 1x4 (...) (20 years ago, 4-Aug-04, to lugnet.robotics)
|
| | | | | |
| | | | | | | Re: challenge: LEGO copier —Steve Hassenplug
|
| | | | | | | (...) Here's an easy 'rule' you could add to resolve that. Just say that a given color may only be used for one size/type of piece. You don't even have to specify what colors are used, as long as any color may only represent one piece type. To make (...) (20 years ago, 4-Aug-04, to lugnet.robotics)
|
| | | | | | | |
| | | | | | | | | Re: challenge: LEGO copier —Joe Strout
|
| | | | | | | | (...) I wasn't thinking that the bot would have to exactly reproduce which same-color bricks are used side-by-side -- if I used a two 1x2 bricks, but the robot chooses to substitute a 1x4 brick, in my mind that's the same model. We'll just say the (...) (20 years ago, 4-Aug-04, to lugnet.robotics)
|
| | | | | | | | |
| | | | | | | Re: challenge: LEGO copier —Mark Tarrabain
|
| | | | | | | (...) Actually, he said "flat". So I would assume that he meant an assortment of bricks simply stuck to one baseplate, sort of like a mosaic. As for brick boundaries... I think the only thing you would need to worry about is the boundaries where the (...) (20 years ago, 4-Aug-04, to lugnet.robotics)
|
| | | | | | | |
| | | | | | | | | Re: challenge: LEGO copier —Joe Strout
|
| | | | | | | | (...) No, I meant stuck to each other. (...) That's what I had in mind too. (...) I was assuming the use of a camera, not the LEGO light sensor. But using the light sensor is a clever idea. (...) Here I expose my complete cluelessness with regard to (...) (20 years ago, 4-Aug-04, to lugnet.robotics)
|
| | | | | | | | |
| | | | | | | | | | Re: challenge: LEGO copier —Mr S
|
| | | | | | | | | Would the bricks be assembled as a wall one brick thick on its side? Like laying a cinderblock wall on its side then creating a copy? That might be done with an X-Y table arrangement with vice like sides at top and bottom of the bricks so that they (...) (20 years ago, 4-Aug-04, to lugnet.robotics)
|
| | | | | | | | | |
| | | | | | | | | | Re: challenge: LEGO copier —Shawn Menninga
|
| | | | | | | | | (...) There are some clever tricks (diff & ratchet/clutch, muxes) to expand it somewhat for some applications, but in general, yes, a single RCX can drive only three independent pulse-width modulated polarity reversible 9V outputs. -SMQ Shawn (...) (20 years ago, 4-Aug-04, to lugnet.robotics)
|
| | | | | | | | | |
| | | | | | | | | | Re: challenge: LEGO copier —T. Alexander Popiel
|
| | | | | | | | | (...) OK, just to clarify: assume an X-Y-Z space with studs sticking up in the Z direction. You mean a model that's only one stud thick in X, arbitrarily wide in Y, and arbitrarily high in Z? Yes, that would be a much simpler problem than what I was (...) (20 years ago, 4-Aug-04, to lugnet.robotics)
|
| | | | | | | | | |
| | | | | | | | | | | Re: challenge: LEGO copier —Joe Strout
|
| | | | | | | | | | (...) Yes, but not arbitrarily -- there would be some limit in width (Y) and height (Z), in order for the model to fit into the machine. (...) Yes, that's a much harder problem, which is why I was thinking to limit it to a thickness of one in X. (...) (20 years ago, 5-Aug-04, to lugnet.robotics)
|
| | | | | | | | | | |
| | | | | | | | | | | | Re: challenge: LEGO copier —T. Alexander Popiel
|
| | | | | | | | | | (...) Ah, hmm, I was expecting it to be a continuous fabric, not a holey one. That would make it harder, and in fact makes it even more important to not confuse neighboring pieces of the same color (otherwise you could lose structural integrity by (...) (20 years ago, 5-Aug-04, to lugnet.robotics)
|
| | | | | | | | | | |
| | | | | | | | | | | | Re: challenge: LEGO copier —Joe Strout
|
| | | | | | | | | | (...) Except that this is a problem pretty easily solved in code -- it's not necessary that the robot choose the same solution the original builder did; it's only necessary that it choose a solution that works. A robot that copies only continuous (...) (20 years ago, 5-Aug-04, to lugnet.robotics)
|
| | | | | | | | | | |
| | | | | | | | | | | | Re: challenge: LEGO copier —Steve Hassenplug
|
| | | | | | | | | | (...) I'm sorry, but I find this VERY funny. :) But you've already said how little you really know about building, so I guess it's OK. A robot that could copy a continuous model is something that would be very do-able. On the other hand, if you (...) (20 years ago, 5-Aug-04, to lugnet.robotics)
|
| | | | | | | | | | |
| | | | | | | | | | | | Re: challenge: LEGO copier —Joe Strout
|
| | | | | | | | | | (...) Why would that be impossible? You'd start by building up the sides; when you've done row B, then you can attach the block in row C, followed by the one in row D. So yes, this means the robot has to be able to move back and forth; it can't just (...) (20 years ago, 5-Aug-04, to lugnet.robotics)
|
| | | | | | | | | | |
| | | | | | | | | | | | Re: challenge: LEGO copier —Steve Hassenplug
|
| | | | | | | | | | | (...) Almost impossible. Personally, I'd have a hard time building this with my hands, much less building a robot to do it. It could easily require three grippers just to put the pieces together. Definitely beyond anything I'd be interesting in (...) (20 years ago, 5-Aug-04, to lugnet.robotics)
|
| | | | | | | | | | | |
| | | | | | | | | | | | Re: challenge: LEGO copier —Steve Baker
|
| | | | | | | | | | (...) No - you'd just use a touch sensor that you could lower down onto the model you are 'scanning' - it would be easy enough to measure whether there was a hole or a brick. (...) The Lego camera isn't really much use because it can't talk to the (...) (20 years ago, 5-Aug-04, to lugnet.robotics)
|
| | | | | | | | | | |
| | | | | | | | | | | | Re: challenge: LEGO copier —Joe Strout
|
| | | | | | | | | | (...) One could cheat (if you consider it that) on this pretty easily, though. Instead of hoppers containing a jumble of bricks, each feedstock source could be a neat queue of bricks in a constant orientation. Grabbing the next brick from such a (...) (20 years ago, 6-Aug-04, to lugnet.robotics)
|
| | | | | | | | | | |
| | | | | | | | | | | | Re: challenge: LEGO copier —Mark Tarrabain
|
| | | | | | | | | | (...) Actually, I think it would be a good idea to use pneumatics to push the bricks together. Any resistance met by pneumatics simply increases the air pressure required to keep pushing, rather than actually damaging any pieces. (...) Why do you (...) (20 years ago, 6-Aug-04, to lugnet.robotics)
|
| | | | | | | | | | |
| | | | | | | | | | Re: challenge: LEGO copier —Mark Tarrabain
|
| | | | | | | | (...) Okay... I think I understand... so you use some 1xN plates or bricks on the top and the bottom of the whole "picture" to hold it together, and the actual construct built can be any size of width N? Or am I still way out there? >> Mark (20 years ago, 4-Aug-04, to lugnet.robotics)
|
| | | | | | | | |
| | | | | | | Re: challenge: LEGO copier —Pavel Kyn
|
| | | | | | (...) <snip> Why not a more positive spin? Reduce complexity by limiting scope to a fixed size panel of colored blocks. Limit colors to black and white, or RGB. Allow brick boundaries to differ. The robot can now simply use 1x1 Lego building blocks (...) (20 years ago, 25-Aug-04, to lugnet.robotics)
|
| | | | | | |
| | | | | Re: challenge: LEGO copier —Iain Hendry
|
| | | | | (...) The closest I got to something like that was my half-built Duck Assembly Carousel - a dial automation with 4 positions, which would assemble the body (2x1 inverted slope), beak (2x1 plate), and head (1x1 brick with a hole in it). I didn't have (...) (20 years ago, 4-Aug-04, to lugnet.robotics)
|
| | | | | |
| | | | | Re: challenge: LEGO copier —Benton Jackson
|
| | | | I think you should start easy, with something like a mosaic copier. (20 years ago, 5-Aug-04, to lugnet.robotics)
|
| | | | |
