Perolav

Eurobricks Vassals
 View Profile  See their activity

  • Content Count

    14

  • Joined

  • Last visited

Posts posted by Perolav

  6. Posted · Edited by Perolav

    32 minutes ago, ultiminutes said:

    I'm guessing it's probably the same reason they hold new sets till after Christmas, New sets will always bring sales.
    They need to clear their excess stock for Christmas!

    Deng. Then i will order the batmobil. Need something fun for Christmas

  9. Posted

    34 minutes ago, imvanya said:

    Here is what the contest rules state:

    So it will be a separate set, and you are right – it is unlikely that LEGO will be able to finalize the set before the release of the new Modular Building. But who knows?

    But to finilize the Competition car with building intructions and box will take wery long time. My guess 6 mnd's

  11. Posted

    On 8/13/2019 at 8:54 PM, Brickster12 said:

    Hi,

    as the new Powered Up elements are software driven and receive firmware updates from time to time I think it might be useful to have a place to discussuss issues related to the software and updates.

    To give it a start I would like to discribe my observations after the last firmware update I performed on my hubs:

     

     

    I performed a firmware update on three of my 2-port-hubs ("Hub No. 4") on 10. Aug. 2019 through the Powered Up - App for Android. The update was performed successfully on all three hubs according to the app.

    There was no interuption of the update and my smartphone was fully charged, the hubs were running on almost new Alkaline batteries.

     

    Shortly after that I discovered a quite strange bahaviour that can be reproduced and is obviously not an intended behaviour:

     

    When using two or more hubs in range of BLE together with one or more handsets plugged in motors or lights show an abnormal behaviour when [+] or [-] buttons are pressed a couble of times.

    Expected "normal" bahaviour should be (was before the update):

    • M-motors: while [+] or [-] button on handset is pressed, motor on particular port goes +/- 100% depding on button. Releasing button, lets motor run out.
    • M-smart-motors ("Boost motor"): same as M-motor.
    • Train motors: [+] button on handset increments speed forward, [-] button increments speed backwards, [ ] button stops (breaks) motor on particular port.
    • Lights: [+] or [-] buttons increments brightness, [ ] turns off light on particular port.

    Observed bahavior after firmware update:

    • A single 2-port-hub in BLE vicinity:
      • Everything works as expected.
    • Two or more 2-port-hubs in BLE vicinity:
      • Hubs on the same channel (same LED color):
        • M-motors, M-smart-motors: pressing [+] or [-] a couple of times lets the motors on the particular port go mad: they run continuously or stuttering at random speeds. Pressing [ ] does not stop them. Occasionally they stop when pressing [+] or [-] on a random sequence.
        • Train motors: in addition to the stuttering they also show extremely rapid changes between +100% and -100% which looks like causing very hard loads on the structure (motor starts to jump when not built into something).
        • Lights: very similar like the motors but with brightness, resulting in wildly flashing lights.
      • Hubs on different channels (different LED colors):
        • Motors/lights on hub turned on first: normal bahaviour (!!)
        • Motors/lights on any other hub added to the network in BLE vicinity after the first one: same abnormal behaviour but separated by channel.
        • Using just one or multiple handsets does not make a difference.

     

    This actually means for me I: with this current firmware I cannot run two or more trains at the same time - regardless how many handsets I use. This is because all hubs in BLE vicinity form a communication network (which is desirable) and are affected of the issue.

     

    Does any one else observe this strange behaviour?

    I've raised a LEGO service ticket with a description of the issues yesterday. I have only reveived the automated feedback so far.

     

    Downloaded new firmware today. Tested it with 3 trains and it works perfectly

  12. Posted

    16 hours ago, Brickster12 said:

    The Lego support team replied that TLG will come up with an firmware update soon. However, they could not provide a date yet.

     

    Last week or so there was an update of the Powered Up app in Google Playstore but it did not contein a newer firmware as I already have on my hubs.

     

    So keep fingers crossed for the next update. ?

    I mailed the support twice ang got no reply.

  14. Posted · Edited by Perolav

    Hello my first post

    I am having problem to use the new power up with two trains and one remote

    • No. 1 train is connectet to port A on the hub
    • No.2 train is connected to port B on the hub.

    Pairing goes fine but when i try to run the trains with the remote. 

    On train work fine and no2 train goes completly bananas. as soon as i hit the run button it goes in full speed. Stop botton do not work. and the speed on the motor is chattering. 

    If i use two remotes, one to each train everything works fine.

    Just tyed to connect both hubs on port A. And pairing with one remote. Same issue as contecting to port A-B

    any one havin the same issue?