Eurobricks New Members
  • Content Count

  • Joined

  • Last visited

About Thyraz

Spam Prevention

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

Profile Information

  • Gender
  • Interests
    coding, robots, machines, 3d printing


  • Country
  1. Thyraz

    Powered Up - A tear down...

    I searched for quite some time on the web, but haven't seen these. But I searched for Powered Up and not Weedo as search term. Just ordered three of the 25cm versions, now I just have to wait a few weeks... Thanks a lot Technicmaster.
  2. Thyraz

    Powered Up - A tear down...

    Another question as some of you posted questions about connectors / extension cables: As we didn't see extension cables released, even after the new mindstorm set arrived, I don't think Lego will release something like that in the near future. Another idea I had was to cut the cables of the motors in the middle and attach some small connectors (male + female). Normally you can just leave these connected to stay with the default length. But you could use self made extensions using flat ribbon cables and these connectors types instead of the ones Lego uses. Does anyone know good and small 6 pin connectors? JST-SM connectors can be crimped for both, male and female and have some protecting plastic around the pins, so they won't break too easy. And they are cheap and easy to handle. But not sure how durable they are.
  3. Wow, thanks. So this is an artificial limitation on the software side. Maybe it's really a problem if you would set the 2 internal motors and two L-Motors to 100% with a lot friction. If the voltage gets too low, the hub might crash and restart. Would be interesting if this limitation also exists for other software solutions like node-poweredup or pybricks. I guess most likely not. Cause if it would be something in the firmware of the hub, the remote would also not be allowed to control it. It's more likely to be a limitation inside the Powered Up app...
  4. Oh, I just realized that Tcm0 is the short version of technicmaster0. :) I watched a lot of your videos as starting point for Powered UP. Thanks a lot for all these videos. And yes, would be awesome if you can test if the technic motors are working for you too at the move hub (but maybe only with the remote).
  5. In this video the technic and spike prime motors are used on the move hub. So what exactly is "not working" at the moment? Can't they be used in the app, just with the remote? Or can't the servo/tacho feature not be used, but simple speed control is possible?
  6. Thyraz

    Powered Up - A tear down...

    As a big fan of @Mr Hobbles node-poweredup, I started to mix it with other useful nodejs / Javascript libraries lately. Really love the possibilities this opens up. I thought I try to share some of my tests and start with using the browser gamepad API in combination with node-poweredup. Most of the stuff can already be done with Powered UP app + Powered UP remote or with BrickController2. But it gives you the best of both worlds: - You're free to code your own sequences that can be started with the gamepad buttons. - You can use analog sticks for fine-grained control. I already tested this with some Robots based on the Lego Boost Hub and 2 additional motors, and the mix of good manual controls in combination with automated movement sequences is a lot of fun. There's a first version of the sample project available here: I haven't added a readme, but installation should be quite easy if you're familiar with node-poweredup. (Otherwise look at the node-poweredup repository for necessary installations step on Windows/Linux. OS X should be fine out of the box.) - Install node.js - Download the content of the repository to a local folder - Run npm install in the directory to install the dependencies - Run npm start in the directory to start the software A node.js express server will be started that loads node-poweredup and it will automatically start chrome and connect to this node.js server. The browser frontend will ask to connect a gamepad and send gamepad events like pressed buttons or positions of the axes to the node.js backend. There's an example program.js in the package that initializes the Powered UP hub and uses the gamepad events to control it. Feel free to ask questions if you're interested to use it. This might help me to write a proper Readme on Github. ;)
  7. Ok, since the video is quite recent, this probably means that the Boost Hub can still only control the Train, Weedo 2.0 and Boost (medium) motors. For all other Powered UP motors it needs the City Hub or the Control+ (= Technic) Hub. Too bad, since it looks like it has been quite some time like that now. So, most likely there's not much hope... Does anyone know the reason? Is there a hardware incompatibility?
  8. In a lot old threads I've seen comments, that the L and XL motors would not be fully compatible with the Boost Hub in the Powered App. But that this might change with future updates. Can anyone tell me if they don't work at all or what the problems are? Or if it's maybe already fixed with the current app version? Currently I only have a Boost Hub and would like to get an additional motor with more power and the possibility for absolute positioning (servo/tacho mode). But I'm not sure if I would have to buy a new hub as well to use it... Thank you for any hints, Tobias