Jump to content

Sariel

Eurobricks Dukes
  • Posts

    2,235
  • Joined

  • Last visited

Everything posted by Sariel

  1. I think the problem you're speaking of results from differences in parts description that exist between MLCad and Bricklink. I got a nice PDF parts list from Blakbird, I believe it takes these differences into account, and it is now included into the instruction package.
  2. This is only theoretically true. The power output from standard AA or AAA batteries drops rapidly over the time, especially with high-current-consuming XL motors. Basically, the difference you've shown is true only for fresh out-of-the-box batteries. The rechargeable AA or AAA batteries are much less prone to this effect, and the 8878 battery provides practically constant output until it runs out dry.
  3. The new battery box was included in new Train sets specifically to lower their prices. The AAA batteries provide the same performance as AA ones, but the general running time of an average motor will be shorter due to their smaller capacity. Then again, the new Train sets include a new motor which is externally identical to the older one, but internally completely changed and PF-system compatible, and it's more energy-efficient than the older one. From what I know being a member of the LEGO's PF group, the new Trains motor provides higher torque than the older one, and it should run just as long on AAA batteries as the older one did on AA ones.
  4. Well, I'm too dumb to speak for the technical side :) but the official software only allows 3 hubs at a time.
  5. I apologize for the doubled post, but the instruction is finally ready, along with a complete parts list. You can browse it at my website, download it from my newly launched Downloads section, or directly from here: http://sariel.pl/down/sariels_jeep_wrangler.zip Enjoy.
  6. Note that you can't use more that 3 hubs at once.
  7. I happen to have the WeDo kit and I just got an extra USB hub and motion sensor for it. In general, WeDo feels like Mindstorms little brother - and by little I mean much more restricted and much less intuitive. The main cons are: - limited mobility, unless you enjoy running around with your laptop in hand - limited precision, because all the motors are controlled not by counting rotations but by a simple timeout function (I've tried to build a simple 2D printed with WeDo kit and it failed even to draw a square) - limited use in general, as the kit comes with a single USB hub that can control up to two devices at once (the WeDo software can control 3 hubs at once so you can plug up to 6 devices, but the hubs don't come cheap) - restrictive programming environment, because instead of a genuine programming language you get a software that allows you to create algorithms by putting together a series of blocks, each block representing a single instruction (such as e.g. run motor for a given time, run motor at a given speed, stop motor etc.) - THE PRICE!!! As for the "programming", I have to admit that despite dealing with advanced php, js & jquery almost every day at my job, I had serious problems getting the grasp of the WeDo stuff. It will feel weird for anyone who had something to do with programming. The 'instruction blocks' I've mentioned can be combined in various configurations, but are nowhere as elastic as e.g. basic php is. For example, you can create a simple conditional statement such as if/then, but forget about if/then/else. On the interesting side, the WeDo provides 10 levels of motors speed (more than with the recent dual-dial PF handset) and can run multiple algorithms at once (namely, the WeDo algorithms can send 'messages' and be initiated on a specific type of message, thus providing the possibility for a 'mother-algorithm' to control a number of 'child-algorithms). There are two types of sensors that come with the WeDo kit: a motion sensor and a tilt sensor. The motion sensor is in fact more like a distance sensor: it detects object at distances between 15cm and 1 cm and returns a 0-10 points output indicating the distance. The tilt sensor is supposed to detect forward/backward/left/right tilts. Unfortunately, its accuracy is disastrous. It can work very well determining the tilt of a baseball bat you intend to swing, but forget about e.g. putting it into a vehicle to detect slopes. It feels like there was plenty of options that could be embedded into WeDo but were left aside. For instance the software automatically picks up the input from your computer's mic. But forget about WeDo and voice commands - you can only determine whether there is some sound or not, or you can play the voices you've recorded. The same thing applies to the motion sensor - it can measure the distance with a satisfactory accuracy, except no WeDo instruction makes real use of it - you can just determine whether something comes into range or not. Long story short, having the WeDo kit in my possession for about a year I have not been able to come up with a single practical MOC based on it. On another hand, things will probably change now that I have two USB hubs and a handy little netbook to plug them in. Still, if you hesitate between WeDo and Mindstorms, Mindstorms wins in all aspects. Some enhanced programming software and new, more interesting devices could improve WeDo's potential, but I don't really see that coming.
  8. The instructions will be available for free. I have finished roughly 75% of mine, and I intend to publish it both as a gallery in my Brickshelf folder and as a single PDF file at my website. By the way, it was your work Nico that convinced me that it's possible to make a readable instruction based on photos :)
  9. *bites*
  10. Just passing through... ;) Seriously... I've been staying away from EB for a long time, but now, as LUGPol's world domination masterplan has been exposed, I have no other choice but to join the invading Polish forces... And genuinely seriously, more on me here: http://sariel.pl/
  11. So... you just got me to finally register at Eurobricks guys :P I never expected to see such a great response to this MOC. I told Blakbird that somebody has just sent me a pretty good MLCad model of my Rubicon already... but then again, it's just a model with no instructions yet, so I can make instruction out of it or wait for Blakbird to finish his. I'm not sure which option is better - Blakbird is sure the MLCad master :) and handles this tool much better than I do, but then again there may be some inaccuracies in the photos I've taken, that I could correct from my memory... What's your opinion Eric?
×
×
  • Create New...