Lok24

they have metal flanges...

The robot is an EV3 ! @avalon102 is the robot already there? With all motors an sensors? Then you have to seperate it into different tasks: i.E. Move through the corridor witthout getting stick, as a first substask. How would you describe this in words? - Start driving - check distance to walls - if to near : correcct direction What does that mean: This is hard to solve Without any knowledge about set physical setup it is nearly impossible to help. Never done that, what does it mean? Which programm do you use?

I used that some years ago, but it is really tricky to bring the pick-ups to proper height, because a little bit to far and they get stuck on switches, where they have to cross the rails.

The Powered Up App was realesed with the trains in 2018, as far as I remember. First technic sets with Control+ were released one year later, 2019. Yes, it is not documented; but very many (all basic) functions are explained in the Boost Set wihich offers about 60 lessions to learn. And for all sets with PU there is a ready-to-use-app, so no need to do any programming. Yes, I mentioned that already: they are not sold outside of sets as a seperate product, so it is clear to me that they are not presented in the shop. TLG does not sell all bricks as spare parts..... The communication of the elements of Powered Up is very well documented, this is why there are that many externeal programs you can use to control. Pybricks is just a way to run programs locally, all others are remote. Advantage depends on application. You can use tablets etc or a PC or other programming tools. But yes, agreed: TLG doesnt support the product at all.

There are no "C+ elements", there are only "Powered Up components". "Control+" is just the name of one LEGO App. And there are very many ways to control any model, one of it is the LEGO power Up App. And you can control the Liebherr with it. That's not new at all, it was there form the very beginning. Followed by:: Or use your imagination to create entirely new creations using LEGO Powered Up components and bring them to life through programming. Set your models in motion and let them react to real events. Just use https://www.lego.com/de-de/search?q=powered+up , what is missing? Note: this is the shop, of course, and not an "invetory" of all components, only theose which are sold seperately. The functionallity is completely different......

Thanks @BatteryPoweredBricks, I changed initial post. It's all here: progams, installation and instructions (all in german) There are three programs: AutoBox1.12.zip ShuttleTrain 1.4.zip MotorControl 2.7.zip

I use without any problems: ASUS Micro Bluetooth USB-Stick V4.0 USB-BT400 Oh, good to hear, I thought that was cancelled. I use the remote-name meanwhile (which isn't really nice......) Below some code from MotorContol 2.7. 10 isn't really useful. If you want to store the name of a remote you need 14 bytes....... Of course you could pack two or more values in one bytes, but makes the pogram hard ro read . So I count 20 parms with my proggy, +14 makes 35. Double would be 70. 50 - 100 should be suffiicient, who needs more has to pack..... Profil_A = (20,100,10,100) #min,max,step,acc Profil_B = (10,500,5,200) #min,max,step,acc # define direction of motors dirMotorA = 1 # Direction 1 or -1 dirMotorB = -1 # Direction 1 or -1 autoacc = False # accelarate continously when holding butten # ----------------------------------------------- # Set general values # ----------------------------------------------- # assign buttons to function1 # syntax: function = "name" # name may be "A+","A-","A0","B+","B-","B0","CENTER" UP = "A+" DOWN = "A-" STOP = "A0" SWITCH = "CENTER" mode=1 # start with function number... watchdog = False # "True" or "False": Stop motors when loosing remote connection remoteTimeout =10 # hub waits x seconds for remote connect after starting hub remoteName = "" # connect this remote only # Color and brightness of Hub LEDs LEDconn = Color.GREEN*0.3 # if Hub connected, color * brightness LEDnotconn = Color.RED*0.5 # if Hub is not connect, color * brightness LED_A = Color.GREEN*0.3 # Remote Profil_A, color * brightness LED_B = Color.RED*0.5 # Remote Profil_B, color * brightness

And it is possible to reconnect the remote after loss of connection. Using this as a watchdog, for cars it might be useful stop , for trains to continue and then reconnect if train returns. It is OSError, and the method is hub.system.shutdown() And yes: you can't turn the hub off while programming is running. Push button stop program (-> blue blinking), the press and hold to turn off.

Interesting, why do you use 2 motors? And ist the large hub useful (programm), or just to start the motors

As I wrote: Pair hub 1, Pair Hub2. Hub 1: Remote press and relaese green Button Hub press and release green Button -> connected Hub 2: Remote press and hold green Button Hub press and release green Button -> connected If the hubs show different channels (colors): Hub 2 press an release green Button multiple times, till it shows same color as 1

It is not "unofficial", it's intend to do that. Just pair hub 1, then hub 2 and set the channel on Hub 2 accordingly.

What type of motors do you use? For the train motors it is very simple to cut the cable and add some extension, its only two wires! How do you use it now? Powered Up App, smart device and remote?

No. yes, you can press the button once and in 5 sec add 1 every 250ms. For non-train-motors you can use acceleration-limit. A program you find here http://www.kinderbahn.de/MotorControl2.7.zip You can set min, max, step, acceleration, auto-acc and other parameters.

my_motorA = Motor(Port.A) my_motorB = Motor(Port.B) #use any code here to set s to desired Speed s= 300 # and then run both motors: my_motorA.run(s) my_motorB.run(s*-1) Does this answer your question completely?

I think it should be - angular motor to D - XL-motor to B - L-motor to A

That's the problem, actual version code.pybricks.com (which is 3.1) always says max speed: 1000 acceleration: 2500 max torque: 260 for all XL, L and Boost motors And is was different a year ago, there I remember higher values.

Sure, but I referred ro the posting of @Feuer Zug :" Your setup definitely allows for such options with the brick built ground".

Yes, but indeed you just need one baseplate beneath the rails, have a look:

I think that it should work, @David Lechner @Pybricks should be able to answer that question; what I know is that there are some restrictions concerning the Move Hub.

This is planned. Implication is that the hubs are independent, but you can use one port at one hub as sender and one port on the other as receiver, so you can transfer information, but reduces ports to six. Or wait for the Pybricks hub-to-hub (perhabs its already available on beta) You find them all on "code.pybricks.com" on the right side, look at "powered Up devices" ; if they are suppoeted with every hub? Suppose not.

Yes it helps. thanks The table is already there, because the programm supports all kinds of motors and changes method (run or dc) accordingly when starting. And the routine was already there, because I'm pretty sure that when first realesed the were values other than 1000, I think I rember 1400 for the Boost motor. I think it would be useful if Pybricks would offer the correct values when reading control.limits()

Yes, works as you described @vascolp my hub was disordered..... But what is the "correct" value for m1.run(xx) ? How to resolve it for the different motor types?

Thanks a lot; I thougth this speed limit "1000" is a property of the motor, cause reading it when starting programm shows always the "1000" I can't test cause it is not possble to install new FW, "the Hub took too long to respond". So it's dead.

Hi @Pybricks, just had the experience that motors with rotation sensor don't reach the same rotational speed when using "run" compared with "dc". "motor.run" results in app. 1000 (according to control.limits), "motor.dc" app. 1500. Changing "1000" into higher values (2000) shows no effect, neither in "run" command nor in "control.limits." How to improve? from pybricks.pupdevices import Motor from pybricks.parameters import Port from pybricks.tools import wait # Initialize two XL-motors on port A and B. m1 = Motor(Port.A) m2 = Motor(Port.B) #start both motors m1.run(1000) m2.dc(100) #wait and show results wait(1000) print(m1.speed(),m2.speed()) Results: 991 1555 960 1570 960 1570 991 1555 991 1555

Hi, not useable without account.....