Jump to content

AVCampos

LEGO Ambassadors
  • Posts

    1,475
  • Joined

  • Last visited

Everything posted by AVCampos

  1. I don't know how it's implemented, but personally I'd prefer the 2nd option: the first one adds too much latency to the controls, even for a slow-moving machine like a bulldozer.
  2. I'm divided on whether I prefer one motor per function, or one motor multiplexed for several functions: in the former case it's simpler and has less points of failure (anyone remembers the outriggers on 42009?), while in the latter case the gearing is more interesting to build and see work.
  3. A Chinook? Oh no, definitely no. I'd never want a LEGO model of a military aircraft.
  4. Assuming M_longer does have the set, it's an early sample sent by LEGO. If they showed the parts page, they'd be breaching embargo, which means at the least no more early sets.
  5. It trades the ability to lock differentials with a two-speed gearbox. One might be better than the other, depending on the situation.
  6. Probably because it's cheaper and, since it's not part of a motorised drivetrain, doesn't need to be as strong.
  7. Or it could have two such mechanisms, using a single motor for selection: that way the model could have 8 functions, two at a time, using 3 motors.
  8. True, but is that a pattern or a coincidence?
  9. Just as what happened with the brick-built engines with square pistons that evolved into the dedicated parts we know today, I don't doubt we'll get somewhere in the future dedicated parts to build smaller engines.
  10. I don't know if it's technically possible, but if the hub can connect to an HID-compliant controller there should be no compatibility issues.
  11. Plus, who is to say TLG adhere to any pattern at all? It has the disadvantage of limiting what they want to produce, and I don't see any advantage in it.
  12. What TLG could do that improved on Pybricks regarding physical remotes (for which Pybricks is a bit overkill IMHO) would be an interface like BrickController 2: press a button on the gamepad, and assign it to a hub output. Then that table of assignments could be downloaded to the hub, which would then connect directly to the gamepad without further need of the mobile device.
  13. That physical PUp remote is the same we've been having for years, that came in the two City PUp trains. The difference is that, installing Pybricks on the hub, now it can connect to the remote and react to button presses. Video explanation by RacingBrick:
  14. Exactly! That's what I keep telling here whenever people get a hold of small blurry images of non-final sets and start extrapolating details.
  15. The 8110 is one such example: http://www.technicbricks.com/2011/06/multimog.html
  16. Nice entries, some are quite unexpected! Congratulations to all participants. Here are my favourites: 13: 10 33: 6 10: 4 1: 3 8: 2 14: 1
  17. Along with the LED matrix and the smaller hub, it will appear in SPIKE Essential: https://education.lego.com/en-us/products/lego-education-spike-essential-set/45345#spike™-essential
  18. Yes, and although they for some reason have different internal IDs, their characteristics are the same.
  19. And does it still have absolute position encoding, or is it "dumb" like the motor in WeDo 2.0, Batmobile and Zetros?
  20. Now that Chinese manufacturers make tiny PF-compatible micro motors, maybe TLG will finally launch some of their own, like what is happening with flip-flop beams. Hmm, they also sell sets of 8 micro LEDs connected to a single PF plug. Interesting.
  21. Such a set would be too... boring. (badum-tschhh) (no, I regret nothing)
  22. You can use this app on your main phone to get an installed app and generate the respective APK: https://play.google.com/store/apps/details?id=com.frankygoes.myapks
  23. I still don't understand what's the problem with colour coding, as long as it's not visible in the final product.
×
×
  • Create New...