Jump to content

kbalage

LEGO Ambassadors
  • Posts

    1,833
  • Joined

  • Last visited

Everything posted by kbalage

  1. Since BuWizz uses a much higher voltage than what the 6-pack of AA batteries can provide it is not even intended to be in the same league. The motors are able to deliver the same perfomance as the PF counterparts, now with the added benefits of Bluetooth, interactivity, sensors etc. From a software perspective the platform still not has the same possiblities like SBrick for example, but it's evolving and I'm sure we'll see the necessary updates coming soon.
  2. It is pretty easy indeed, I made a quick video guide how to do it. I'd be also possible to change both sets of gears for even more torque but I don't think it'd improve further the abilities as the vehicle would simply tip over during climbing.
  3. You can actually, although the gauge is not very precise based on my experience. If your batteries are drained the hub will flash orange and you'll get a low battery warning while connecting, like this one: The app won't even let you go further. I also took a screenshot of ~50% battery level shown on that screen so there's some feedback.
  4. It would be much easier to have the embargo date/time published in UTC :)
  5. As I see it the Control+ app will only get set-specific sequences or actions, like the movements for 42100 demonstrated in the Fan Media Days interview videos. Powered Up app will get the generic blocks and can be used for MOCs. Reviews will be published at 13:00 CET which will be 14:00 for most of Europe since we are in CEST (Central European Summer Time) currently-.
  6. @TeamThrifty yes that pretty much sums it up, although the PU app also has set-specific controls for the trains and the Batmobile but that'll be the one containing the custom(isable) interface as well.
  7. @MT09 Control+ is only the name for the app created for the Technic sets. Not sure why TLG choose to introduce another name, but in reality it shares the same protocol with the previously released Powered Up components, the Boost parts and also Spike Prime which is an educational line coming next year. The aim of the dev team is to have the Powered Up app as the central "hub" that will be able to control all components. The app is constantly evolving so it's not quite there yet, as a first step hopefully it'll be updated soon with support to the new 4 port hub and the motors. Since the protocol is open there are already multiple applications that can control the Powered Up components, like the great BrickController 2 app (can control PU/PF/SBrick/BuWizz) that supports already the new hub or for desktop there's the Brick Automation Project (aimed mostly for train layouts). As far as I know the SBrick app will be also able to control the PU components soon and I'm sure more will follow, so there's an expanding 3rd party support.
  8. Spike Prime was delayed anyway until next year so there'll be a lot of time for the Powered Up app to catch up with the support :)
  9. Maybe I am one of the few who does not enjoy any slow motion destruction videos, regardless if it is a Lego car, a phone or anything else. Destroying something for "fun" that would be otherwise working and useful is totally against my nature.
  10. The Control+ app has only set-specific controls at the moment for 42099 (and most likely will be expanded with controls for 42100). You can use it now to control a similar vehicle with 2 XL motors and one L motor for steering but that's all at the moment. The Powered Up app will be the platform to control custom creations but that'll first require an update to support the new hub and motors, and also a more sophisticated (preferably customisable) interface that can be used to control custom creations. It has a basic interface currently with two sliders but that's pretty limited. Some 3rd party apps like BrickController 2 are introducing support for the new elements so hopefully it'll be possible to control them at least with those apps (until the official update comes).
  11. Ask this guy, I'm sure you can come up with a great idea together! He makes good quality stuff and can help with the design as well.
  12. I have no clue what are they teasing but I really don't like pointless destruction.
  13. That's exactly the aim - Powered Up and Boost sharing the same protocol and connectors, Spike Prime as well for the Education line. I'm sure the next generation of Mindstorms will follow them.
  14. Might use a different approach, BrickController 2 requires the same access. Quote from that topic: More info: Android 6.0 changes"To access the hardware identifiers of nearby external devices via Bluetooth and Wi-Fi scans, your app must now have the ACCESS_FINE_LOCATION or ACCESS_COARSE_LOCATION permissions"
  15. Needed for the Bluetooth connection, it is Android's "fault".
  16. The fact that you don't need them does not mean that no one would like to have sensors, interactive motors, gyros etc. You can easily use rechargeable AA/AAA batteries. Accessible everywhere, easy to use, no headache for LEGO with shipping built-in batteries. Also easy to swap which won't be the case e.g. when the battery dies in a BuWizz. The volume of the Control+ hub is not significantly bigger than the volume of the PF AA battery box, it also has better mounting points. The L/XL motors are truly longer, that's a disadvantage, but they have more mounting points. On the other side we won't need to use the weirdly shaped Servo motor anymore. ? Let's wait and see some more tests with other real-life applications. Do you know already the price of the new elements? Both the AA and the AAA PU hub has a removable battery chamber, it has the potential to be replaced with a rechargeable battery unit. I see this as the single main disadvantage of the PU system compared to PF but it was needed to be able to create interactive motors and sensors. We provided feedback on this to the Powered Up HW team with some ideas like an unpowered port replicator, hopefully they'll be able to provide a proper solution with time. Rant over.
  17. It is allowed for everyone who purchases the set, only not allowed for the ones who got the set for review from TLG.
  18. 42070 is the typical victim of some unlucky naming and false perception based on the look. People think if it is called "All terrain" and it looks like an Ural truck it HAS to be the best off-roader ever. I expect a similar fate for 42099 btw
  19. Amazing and very accurate recreation, I love it!
  20. @allanp I would LOVE to see a Dodge RAM, it's a shame the chances are so low..
  21. Why not buying 42099 instead and do your own version? :)
  22. Minimum requirements should be similar to the Powered Up or Boost Android/iOS apps as they share the same protocol.
  23. I expect this Btw I still can't wrap my head around that flagship that has half the piece count of 42099. It could be a nice wheeled alternative of 42065/42095 to offer a base set of Powered Up parts, but how that will become a flagship is still a mystery...
×
×
  • Create New...