vascolp

In the front of the vehicle, in the left side, there is a white arm with a gray clip claw. Behind the elbow of this arm. Difficult to spot indeed.

Not my cup of milk??

I, on the other hand, feel like a kid who want's the whole collection!

It seems +

See it in the other way. Body retraction. To fit better in a spaceship. It is really cool!

It is very cool indeed! Even the Beatle chassis shape very identifiable! It's the non cut chassis version isn't it? You could do also the short chassis version!

@Legotyres: Or, if you have a lego remote, you could try RemoteBalBla. No need for programming,it already includes support for 90º steps gearboxes.

It seems a very cool theme! Maybe you want to fix this in your text.

Ok, maybe monitor it only when you press the remote button to change speed up. Have an array with the initial theoretical 100 speeds. When you press the remote button up, get speed before, get speed after, if difference is less than a given threshold you reached maximum load speed, so recalculate the array of speeds. Now this will only decrease speeds. We have to find a way to increase speeds, in case you decouple the wagons. Maybe, when you are in step 100, you allow for a 101 step which is current 100 speed plus the step speed… if speed increases above a threshold, recalculate with new maximum. Now this is all nice theory, but speed increases will take time, most probably much more than the time it takes to get speeds before and after… so the “get speed after” must be done with some sort of delay, which will have to be tuned somehow. Using a StopWatch object in the main loop might be a possible solution for this. I foresee lots of programming fun! Whatever you do, please tell us how it worked!

Wow... I didn't knew your code! I just googled it and found it. It is indeed very similar. So similar that I went to github to see when I first used my code... initial versions are here, from april 2022. The code and the documentation of it. Regarding the problem, yes there is no simple solution for it. The maximum speed will always depend on the load. That is why I multiplied by 0.9, an heuristic to cope with that (sort of) ... but in Remote Bla Bla, I use 9 steps at most. You are using 100 steps, that is too fine, so the last steps won’t be distinguishable... I don't see a way of having a lot of steps and being able to define speed levels a priori... Maybe if you have some calibration mode, that would adjust itself to the MOC load, store it in the hub storage, and go from there. That or monitoring speeds per step constantly and dynamically adjust step speeds.

In Remote Bla Bla I had a similar problem, I wanted to be able to define steps in terms of maximum speed for each motor type. I got no-load speeds for each motor type from philohome great site, multiplied it by 0.9 and got a list of maximum speeds per device. If the device does not match... it uses 1000deg/s (why not?). Device ids are here. Something like this: def get_dev_max_speed(port_p): devs_max_speed = { 38:1377, 46:1700, 47:1780, 48:1230, 49:1150, 75:1230, 76:1150 } return devs_max_speed.get(PUPDevice(port_p).info()['id'], 1000)

Even so, you could try to do it electronically instead of, well,… destructively! Are you using pybricks? In pybricks there is the run_until_stalled() method which should do it for one LA, as @Lok24 explained. Your problem is having more than one LA. But, the run_until_stalled() is just a convenience function that does this (check it here): my_motor.run(speed) # Wait until it is stalled while not my_motor.control.stalled(): wait(10) # Stop the motor (you can also choose brake or hold here) my_motor.stop() This could easily be converted to two or more motors, so the LAs would move all at the same time and LEGO tolerances would do the rest (as long as your starting point is not very different on each LA!). If not in pybricks, there should be some similar solution? Hope it helps!

One tip: do use sub-models right from the beginning. It is easier to generate instructions if the model is divided in sub-models (and sub-sub models...). Consider how your MOC splits in major groups and build a sub-model for each part. If you don´t do it from the beginning, it is much more difficult to split.

But there is.... I got one of these because my laptop BT did not work properly with pybricks: TP-Link Bluetooth 5.0 USB Adapter, UB5A. It works very well! @nvsukhanov it looks very cool! Did not have time to test it yet but surely I will try it!

Hmmmmmmm very nice! Maybe a bit crazy, but that battery box has a built in gyro. Couldn't we use it to measure pressure? The battery weight against a cylinder?