Jump to content

kbalage

LEGO Ambassadors
 View Profile  See their activity

  • Posts

    1,832

  • Joined

  • Last visited

 Content Type 

Everything posted by kbalage

  1. kbalage
    Or they simply want to reveal them separately. The Defender was revealed in September 2019, and it had no trace in the 2HY 2019 catalog because of that.
  2. kbalage
    Sorry, I phrased it incorrectly. It has an encoder but no physical zero position, it is similar to the internal motors of the Move Hub. The motor will only provide a logical zero position to the hub.
  3. kbalage
    @Toastie almost :) There's the Medium Linear Motor (88008) that you missed, it has no hardware encoder so it falls in the same category as the internal motors of the Move hub (not affected by the bug). And the problem is with the TachoMotorSpeed block, the MotorPower block works well with all hubs and motors.
  4. kbalage
    @Toastie that's the expected behavior of the train motor, since that one does not have an encoder either. About your question regarding the hardware/software zero position - all the tacho motors have a sensor that measures rotation in degrees. The logical zero position will be always the "power on" position, that is used as a zero initially, but that can be updated in the app. The L/XL/Angular motors have a physical 0 position additionally, so the motor can measure the actual position relative to that physical zero mark.
  5. kbalage
    Actually the Medium linear motor works with the SetSpeed command and shows no sign of the bug with the City hub, so from the bug's perspective there's a difference between the motors that have hardware zero position (L, XL, L/XL Angular), and the one with software zero only (Medium Linear motor). This made me thinking, what about the Boost hub? The internal motors are similar to the Medium Linear motor as they have software zero only. I tested with the Boost hub and the bug does not appear with the internal motors or with the Medium linear motor attached, so this also confirms the difference between the motors with and without hardware zero. Btw it's not strictly related to this bug, but I found another anomaly during testing - the Technic L/XL/angular motors are not working at all with the Boost hub unfortunately.
  6. kbalage
    @Toastie no worries, I didn't feel being pushed :) So with my iPad Air 2, latest City hub firmware, PU app version 3.6.0 I have the following experience: The bug does appear with the City hub and the Large, Extra Large, Large Angular, Extra Large Angular motors, basically the ones with hardware encoder. The wait time is basically irrelevant, crash happens between 3 and 150 cycles randomly. The bug does not appear with the City hub and the Medium Linear motor that has software encoder only. I tested it with various wait times until 1000+ cycles. The bug does not appear with the Technic (4 port) hub with any of the motors. The code does not run the motors without encoder but that's the expected behavior. So these are some pretty special circumstances to have the bug, but it does exist. I suggest to report it via LEGO Customer Service (an e-mail works), that is the official way. I will also try to forward it through my channels.
  7. kbalage
    Definitely worthwhile to follow up, I didn't have the time yet to make longer tests to confirm your data. Family also deserves some attention on weekends, not just lego ;) Will try to run the tests this evening.
  8. kbalage
    I don't really have time to read all the previous discussion at the moment but I quickly tested the code there and it runs ok on an iPad Air 2 with the latest PU app, with a city hub and an XL Technic motor attached. Could you guys provide the exact conditions when it failed?
  9. kbalage
    Powered Up as a hardware platform might be related to Mindstorms and robotics, but the app is more related actually to the current Technic offerings since Mindstorms has its own app environment that is independent from the Powered Up app. @Hod Carrier as others said, posting a screenshot would definitely help more than a long explanation. It makes it much easier to troubleshoot your code and also to replicate it on our devices and test it. It can easily be a bug, because what you describe is definitely not a standard behavior.
  10. kbalage
    It is linked in my post above :)
  11. kbalage
    Nice explanation of the code! Actually there was a similar topic created some time ago, although not exclusively for code sharing but for other Powered Up-related tips & tricks as well. Not sure if there's a need for a separate "PU code collection" topic, but if @Jim was ok with it then it should be fine :) It'll be a challenge to keep such topic clean since people will naturally react on the publications, just like I do right now.
  12. kbalage
    I didn't have the Jaguar set for comparison but the previous GTs look like a City set next to the 8 stud wide one:
  13. kbalage
    It is medium azure I can confirm. Unfortunately I only have the Quattro from last year, the others are from the 6 stud era.
  14. kbalage
    Here's my review of the smaller sets:
  15. kbalage
    This is a video that might help you get started, and you can use my code block guide as well.
  16. kbalage
    @Celeri yes they are the same. If you check the inventory if the "set" 88012 on BL you will see that it contains that single part.
  17. kbalage
    Yes, but you need to create a code for that in the Powered Up app, using the remote as an input device.
  18. kbalage
    @Bote here is a summary about Powered Up that might help. There are also further tutorials and several videos on the webpage.
  19. kbalage
    As @R4ph mentioned the guy on the photo works for Renault, and it's a screenshot from the story where he explains how he used LEGO to model and develop a hybrid powertrain. An interesting story but has nothing to do with any new sets.
  20. kbalage
    There are many designers at TLG who were (and still are) active AFOLs before being hired, so I don't think it's necessarily true. But as you said a lot of people tend to romanticize a job at LEGO, there are certainly a lot of aspects that are less appealing and fun than the design process itself. The ability to work in a team and to work with deadlines is certainly a must.
  21. kbalage
    42070 wasn't performing that bad with a few tweaks. The off-road capabilities were mostly limited by the outriggers and the central diff, with another XL motor it could be improved further.
  22. kbalage
    Here's my unboxing and first impressions video about the BuWizz 3.0 Pro. The app used is still a beta version and the firmware will also receive updates so don't expect a very in-depth review, it's more like an overview of the features and possibilities. More content will come soon!
  23. kbalage
    It works with 2.0, I'm sure it should work with 3.0 as well. As an alternative you can also get a PU -> PF adapter for that 3rd PF motor, then you don't have to control BuWizz 3.0 and SBrick separately.
  24. kbalage
    The answer is in your question - because they are leaked images, not shared officially. Eurobricks is a Recognized LEGO community, and the status comes with certain rules. It is fine to talk about the upcoming sets but it is not ok to share leaked images.
  25. kbalage
    Welcome to Eurobricks, the forum where we don't post leaked images. I'd suggest to remove them asap.
×
×
  • Create New...