Mr Hobbles

Eurobricks Knights
  • Content Count

    599
  • Joined

  • Last visited

About Mr Hobbles

Spam Prevention

  • What is favorite LEGO theme? (we need this info to prevent spam)
    City
  • Which LEGO set did you recently purchase or build?
    Winter Village Fire Station

Contact Methods

  • Website URL
    http://

Profile Information

  • Location
    San Francisco, California

Extra

  • Country
    United States

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Mr Hobbles

    Powered Up - A tear down...

    Maybe...in my preliminary testing there's a command to retrieve it, but I'm unsure of the format of the returned data. Also the command doesn't seem to work on the Boost Move Hub. More testing required. :)
  2. Mr Hobbles

    Powered Up - A tear down...

    As a follow up, as promised, I tested your problem out this evening, and, can confirm, it happens to me too! So, the bug is not just limited to Boost motors, but to both the Boost motor and Boost color sensor too. So: Plugging 2x Boost devices into a PUP Hub will crash it and cause it to restart. :) 1x Boost device (and any other device) should work fine.
  3. Mr Hobbles

    Stopping a train at an exact spot

    The PUP motors and hub have this built in, this is what speed value 127 triggers (As opposed to value 0, which lets the motors float to a stop).
  4. Mr Hobbles

    Powered Up - A tear down...

    2x WeDo motors work fine as they are an output device only. Same with LED lights and train motors. All multiplex to port AB fine with no issues. It is only Boost motors that cause issues as they are an output device (you can sent motor drive commands to) and an input device (you can receive rotation angle notifications from) at the same time.
  5. Mr Hobbles

    Powered Up - A tear down...

    Glad you found the library useful! That's a very good point though, I don't have an example for the Duplo train yet, and I don't document the motor strings in use (Sidenode, it's "MOTOR" as opposed to "A" or "B" because it's not a port that can be unplugged or replaced with something else). I'll add it to my to-do list for this week to dig out my Duplo train and make an example. :)
  6. Mr Hobbles

    Powered Up - A tear down...

    Yes, that *might* be related to the existing bug you mention, but I'm not sure. The PUP Hub has two ports, port A and port B, that you can individually send commands to. When you plug in two identical devices (eg. two train motors or two led lights), internally, the hub creates a new virtual port, AB, that you can send a single command to, to control both motors at the same time. The problem is, that Boost motor is both an output device *and* and input device, so when it tries to create the virtual port, it crashes, as multiplexing two input devices doesn't make sense. :) Apparently Lego will fix this in the future, but they haven't yet. So, in your case, plugging in a Boost motor and a Boost sensor would be two input devices, but I don't think it should try to multiplex them though, as they aren't identical devices (they have different device ids). I'll do some testing tonight to see what it does, just out of curiosity. :)
  7. Mr Hobbles

    Stopping a train at an exact spot

    Speed value 127 is a hard stop/"brake". :) Obviously there will still be a bit of a "float" depending on the weight of the train and the speed it is going, but it's the closest you'll get without using sensors and a slowly decreasing speed to stop at an "exact" spot.
  8. Mr Hobbles

    Rechargeable batteries for powered up hubs

    Thanks for the run down! Seems like a very cool system. :)
  9. Mr Hobbles

    Rechargeable batteries for powered up hubs

    I am very intrigued with this! Can you describe the mechanism/parts a bit more? Do you use Lego 9v track? How do you connect the wheels to the battery box (PF I presume)?
  10. Mr Hobbles

    Rechargeable batteries for powered up hubs

    Right, all that may be true, but the thread title is "Rechargeable batteries for powered up hubs". I think it's important to point out that one can use standard rechargeable batteries without needing to modify your battery box or risk blowing your battery box by using too many LiPo's. NiMH rechargeable's are commonplace and provide a perfectly reasonable almost-as-good solution without risk. However if you do want to use LiPo's, @Giottist's research and solution is awesome! :)
  11. Mr Hobbles

    Rechargeable batteries for powered up hubs

    I have to back that up - I've used both Eneloop and GP ReCyko Pro rechargeable AAA's and AA's over the years with no issues. I use both a GP ReCyko charger and a cheap 16 bay one I got from Amazon. I get a few hours (maybe 3ish?) from my Powered UP trains per charge and then I charge them again. Quite convenient. I have no idea about their mAh properties, I've never cared - they just work. :) I pop six of them in a hub like any other battery and off I go.
  12. Mr Hobbles

    Powered Up - A tear down...

    Yes, and yes. :) A Boost Motor will work on a Powered UP hub, but does not support angle rotation or reporting the angle rotated. It allows speed control only. Boost Sensor is fully supported on Powered UP hub. Powered UP motor is fully supported on a Boost Move Hub. (All this is only true when used with third-party non-LEGO software to talk to the hubs)
  13. Mr Hobbles

    Rechargeable batteries for powered up hubs

    Pardon my ignorance, but why not use normal AAA rechargeables? I have about 60 Eneloop's I use with my Boost, Powered UP and WeDo 2.0 hubs with no issues.
  14. Mr Hobbles

    Documenting the LEGO PoweredUp! System

    Yeah, in fact there seem to be several references to the hardware being LPF2 (Lego Power Functions 2), as also referred to on the replacement pieces website. Interesting that the BLE protocol is called Lego Wireless Protocol 3.0 - I wonder what 1.0 and 2.0 were?!
  15. Mr Hobbles

    Documenting the LEGO PoweredUp! System

    Now THIS is something I’m very happy to see! A lot of useful information in here! I’d suspected there was a bit more to peripheral subscription modes, but wasn’t quite sure how to find out. I also didn’t realize that you can set individual motor acceleration curves. I’m eager to try all this when I get back to my PUP components in the new year. I also now wonder of this is implemented on each hub (The PUP hub and Move Hub don’t seem to implement everything the same for example) I’d also like to see some documentation for the individual peripheral commands rather than just the BLE wire protocol. Either way, I’m very happy that this is out there, and especially on GitHub. :) Such a great sharing platform.