Jump to content

AVCampos

LEGO Ambassadors
  • Posts

    1,475
  • Joined

  • Last visited

Everything posted by AVCampos

  1. Coincidentally (or not?), a new update to the PUp app has just become available, which appears (I can't fully confirm at work) to allow us to program the Batmobile in a Boost-like IDE!
  2. It does look a bit thin on the inside... I hope it's not too fragile for it diameter.
  3. I would like that very much, to have, for example, simple (Control Centre-like) automation on the AAA hub. Given that the whole programming infrastructure is already made for Boost and its hub is no "smarter" than the AAA one, this shouldn't be difficult from a technical point of view.
  4. When Technic inevitably transitions to PUp, there will be inevitably a "universal" PUp app. At least I expect so... if not, there will always be fan-made apps like BrickController 2.
  5. That makes sense; after all, it has better motors than the '65 yet costs the same.
  6. I thought that too, but I was told that this one was designed with PF in mind from the beginning.
  7. Well, its price is on par with the '65, with the benefit of having L motors instead of M.
  8. Personally, the set I'm most looking forward to see reviewed is the 42095, especially the new sprocket element.
  9. Not to mention the work it takes to research, write, photograph, and, in some cases, film the review.
  10. If a BT sniffer doesn't require hardware, I may be able to help: I have a Batmobile, a Windows PC with integrated BT 4.0 (I think it's also BLE; any way to check?), and several Android devices with BLE. What software would be needed?
  11. Yes, from my subjective observations with the Batmobile and the official PUp app, technically it's possible to activate several outputs at the same time. It would be really useful indeed if TLG published their specs for the PUp protocol. I'm optimistic about that, given their history of openness with PF and MINDSTORMS.
  12. Here's the document's thread, to keep the discussion in one place:
  13. Christian Treczoks of MBFR (LEGO® Modellbaufans Rheinland e.V.) has just shared a document containing his findings about the PUp protocol. It might be helpful for BC2. http://www.treczoks.net/PoweredUp!%20Documentation.pdf
  14. Because it's new, and has the Bluetooth controller.
  15. Having a gearbox to distribute one manual input into two or more outputs is usually a sign of PF upgradeability. If 8293 is really being discontinued as some rumours say, this would mean a PUp upgrade set in the same vein.
  16. 17101. And the hub's price isn't that good: for double that, you get in the set the hub, a servo motor, a colour/proximity sensor, and a bunch of parts.
  17. Actually, the 8063 is a recolour (sorta).
  18. Both the Boost and PUp hubs have upgradeable firmware, so that's a possibility. The WeDo 2.0 hub doesn't.
  19. I guess it's an alright parts pack, especially considering that dark azure is becoming more common with the yacht, the rally car, the Chiron, and (as far as I can see; can anyone confirm?) the new tracked racer.
  20. You mean the 88008? It's not the "M motor" as used in WeDo 2.0 and the Batmobile, but rather the servo used in Boost.
  21. What about the '95, even if only as a parts pack?
  22. You can get some ideas for single-set (including the 42055) GBC machines here: https://pv-productions.com/product-category/lego/ Too bad the instructions aren't free.
  23. It'd be very nice if the new sprocket was hollow like yours or at least with a pin hole instead of an axle hole (like this one) in order to let an independent axle pass through, but judging by available images i'm not holding much hope.
  24. The strange thing is that, on my Shield K1, SBrickController can find my SBricks, but neither BC1 nor BC2 (version 0.8) can. All the other devices I tested worked fine with BC2.
  25. No, it's also for Power Functions (if your device has infrared) and SBrick. The problem may be with your device, as all the ones I tested can find my SBricks, except my Shield K1 tablet.
×
×
  • Create New...