allanp

Trains would still have their remote, or do you want a simple remote with proportional joysticks? The train remote could be upgraded to have those though. The sticks would stay put acting like the accelerator lever on a train, but there could be a place to allow you to add a rubber band or a soft shock absorber to make it spring back to center.

Well that's good cos my PU overhaul would have all that

Yeah I guess so . But a bespoke smart device that comes in the box that doesn't need updating (hopefully!) and with a bunch of built in physical controls. I would hope that it wouldn't come with a bunch of errors in the code, surely they should fully test this stuff before release? But my thinking here is that it would still have Bluetooth and therefore still have connectivity to the internet. However, while it's always there as an option, it's not as reliant on it as it is now. The sets that come with CC+ (the most expensive ones that otherwise would have come with multiple hubs) would have in their printed instructions a complete, step by step guide on how to program your model on the CC+ itself. While you have the option to download a premade program, you don't have to because the book would guide you through programming it yourself. This would also help with providing documentation and helping the customer understand how to do it. So no need for internet connection for new sets, and no need for a smart device to create your own. But sure, things might still go wrong, at which point you would usually call customer service. They can then guide you through the process of allowing them to connect to your CC+ and verify the issue and either fix it for you in most cases or replace it. The optional app allows you to download premade programs and update your CC+ if you want to but it's optional. It would only ever be strictly needed for customer support to fix unforeseen problems. So it's all still there if you want or need it, but the reliance on it to make it a complete and usable product is vastly reduced, and it should still work in its current form and is still programmable long after it is no longer supported by Lego or third parties or your smart device is no longer compatible, much like the original control center and code pilot today, all while not hijacking the use of the smart device you paid for. In terms of the delay to send and receive commands via Bluetooth, is that not the case as it is now, maybe not with pybricks running on the hub, but certainly with PU as it is now? We still have to send and receive data between the hubs and the smart device don't we? Also, for programs/models that don't require feedback from sensors/encoders, would it not actually be a bit quicker, maybe about the same as pybricks, as all the program is executed on the CC+ where the controls are, and it only needs to send commands to the BLE receivers? I could be wrong on that though, as well as everything else! In any case, if you were told that this is all going to happen, with the CC+ programmable physical controller being developed as part of a complete overhaul of PU (not a whole new system, more or a revamp to try to address everyone's concerns with it), including buggy motors in an L-motor format, removable leads from the motors, micromotors and so on, what would you add/remove/change to make it a more enticing prospect to you? What really concerns you about it that we could try to address? I'm not trying to come up with something just to please me, I want us to "fix" PU together! However you must bear in mind everyone's concerns and wishes. You might not be concerned with PU being so dependent on your smart phone/tablet to be a complete package but many other people are. I'd probably be happy just going back to the simplicity of PF but having better proportional remotes, but many people like the more advanced capabilities of PU. Maybe I'm trying the please everyone and maybe it's not possible but not trying feels like giving up before you begin.

This is very impressive, well done

I wonder if we could have a whole bunch of preprogrammed blocks. For example, for an automatic gearbox we know we need to have a speed measurement from the main drive motor, so in the automatic gearbox block we can select which motor is the main drive motor and it would then know to measure its speed, and also have some control over it. We also need to know the position of whatever the control is for the accelerator, so we can select what is that control. We can select the number of gears in our sequential gearbox, the servo which rotates the cams to change the gears and the number of degrees of rotation needed for each gear change, we can also select if we have neutral and reverse gears, and where the servo needs to be rotated to to reach those gears, and which controls we want to use to get neutral and reverse. And bingo, with a single code block we have a fully functional automatic gearbox. The code block would be an actual block of code with everything already programmed, you only configure it to your needs, it would automatically work out everything for us, like it would always start in first, and shift down to first when we stop, and shift up gears if we keep the accelerator control on full, and shift down gears when the motor slows down but the accelerator is still maxed indicating a hill or heavy load, and slightly reduce motor power during shifts, speed match the motor for smooth shifting (the code block would allow you to set the ratios) and allow the shift to fully complete before making another shift and so on. Behind the scenes it could be as complicated as we want, but on the surface it only needs an easy to do configuration from us. There could be bespoke code blocks for all sorts of things, like a code block for steering multiple axles, where we can set the servos for each axle, define how many steered axles we have, define what is the main steering control and define what button should be used to switch between steering modes as well as select what preprogrammed steering modes we'd like to have. There could be another code block for RC pneumatic creations, where we can set how many circuits there are, the servo limits in either direction as well as a bias towards one way or the other, weather or not the servos should move linearly or logarithmically, an additional output that runs maxed out whenever any of the servos are at a non central position (for automatic control of a compressor) and an additional input for a pressure sensor (for if you want to control a compressor using a pressure sensor instead). Of course you could always try to configure these functions yourself using the more generic code blocks but having a whole bunch of these advanced and bespoke, preprogrammed blocks would really help to make creating custom programs for your MOCs a lot easier. And I think that not only is true for my CC+ idea (as they would come preprogrammed into the CC+ ready to use from day one) but also for PU in it's current form. What other bespoke code blocks would you find useful for any MOC you could think of building? Maybe one for controlling a manual sequential gearbox using two buttons for up/down shifts, or a block for a manual gated gearbox to mimic a stick shift (where you can select different gears directly by pressing different buttons) which would also be useful for multifunction gearboxes, or maybe a limits block which lets you set limits on the number of motor rotations due to string length on a winch drum or a linear actuator, or a load sensor block (could be more generically called a disabling block) which lets you disable different motors/outputs/inputs in certain directions when a given an input either from a sensor or some other part of the program.

You'd get that many boom pieces from 2 sets it looks like.

Ah okay, good to know. Been trying to figure out what would be possible config/programming wise with a simple, even monochrome LCD screen for CC+, though of course a nicer looking color screen or even a touch screen would be much better. Can we do only configuration or are code blocks doable? I'm thinking it could be kinda node based, you just select what input goes to what output and configure the blocks. Also trying to cut down on writing massive walls of text so here's a few ugly looking sketches, some screens are programming an excavator, others like the sequencer are for programming a sequential gearbox. I think I spent too long on this!

@Lok24 I think the modern Hornby train sets have a system of sending both power and data through just the two rails but enabling separate control of multiple trains on the same rails. Not sure how that would work with two way comms though, like for sensors.

This has got me thinking. I think I have some left over lead flashing in the shed, easy to cut with tin snips. I could get some grey PLA filament, though I have some in yellow already, make them twice as tall and cut rectangles of lead flashing to fit inside.

I was half joking, but is 11% an acceptable failure rate right off the bat? And now I'm wondering, I bought my current phone to be able to use PU, which is now over 3 years old and I have no desire to change until it stops working. I still consider it to be my new phone. But if I was to just now get my first PU set I'd be well disappointed if I found my phone wasn't new enough. What phone I happen to have shouldn't have anything to do with anything.

Which one sounds more rediculous? I can't play with my Lego because my phone isn't up to date. I can't play with my Lego because a bird pooped on my neighbours car when I was a little boy. Answer: They are both the same!

I was thinking more manned vehicles to outer space but yes you are right, and thanks for sharing Good question. Would we prefer a colourful mess inside a sleek all black shell or would we prefer all black gears and so on, so we can see all the gear trains working whilst not being an ugly mess. I think I'd prefer the latter, perhaps the only time I'd advocate for actually all black, to match the black backdrop of space and even the invisible forces of gravity that hold the planets in orbit. Alternatively it could be a purposely decorative and ornate mechanism, but that sorta brings to mind creator rather than Technic.

Sorry I'm late to the 2024 party. Names alone are hard to get a feel of how excited I should be. A space wheel loader would probably look similar to an Earth wheel loader in white I guess, with different proportions maybe. Maybe it could be autonomous and without a cab? Hmmmm. I doubt a real life one would be solar powered as it would work slower than wind erosion! But as real life ones don't exist yet I guess it'll be a futuristic design. The VTOL space cargo ship also sounds futuristic and also slightly humorous to me, I mean, is there such a thing as a space ship that isn't VTOL?! But with all these space sets I wonder if this is a whole new subtheme like the arctic sets. As much as a space shuttle could be really great, the existence of future concepts on this lineup kinda makes me doubt it a little bit, but who knows, maybe in Legos world of the future the space shuttle still flies! Oh, and one other thing, space sub theme? Technic minifigures?! @ralphie Moon is a fantastic movie, if you haven't seen the film Sunshine I'd also check that out.

@vascolp you and @Lok24 are more than welcome to discuss your thoughts and other ideas in this topic if you wish. I didn't call this topic "I'm going to fix powered up", it's "let's fix powered up". All ideas are welcome. Maybe it can also encourage us to look again at our own ideas and try to come up with ways to include other people's concerns. It was other people's comments that made me realise I should drop the physical code blocks from my first idea in this thread and also to continue with Bluetooth instead of 2.4ghz. However if you want to start a new dedicated topic you are of course free to do so. To your points in your post above. 1) We are agreed 2) It is true that this is the world we live in but I don't like this argument. We could say that we should just go along with many undesirable, and even terrible things because that's the world we live in. I don't think that should be an allowable excuse. Having optional connectivity is fine and even great, but when it's mandatory we have to deal with things like mobile phones moving on and no longer supporting PU when Lego moves on unless we rely on third party developers which we shouldn't have to do when we are paying a premium price and spending yet more time on our phones which playing with Lego should reduce and so on and so on. And besides, I want to use my phone as a phone whenever I want. I paid a lot of money for it to be hijacked by another product. Maybe I want to let someone watch YouTube on it or listen to music on or use it to follow a tutorial on how to program PU or make a phone call to my mate so I can chat to him discussing how great this Lego thing is that I'm playing with or whatever. The fact that I can't use my phone because I'm playing with my Lego, or maybe the idea that I can't even buy that Lego because my phone isn't compatible, it's all just silly to me especially when paying a premium. I could buy a tablet or some other bloody smart device, but I'd still lack physical controls, but I could buy a playstation remote and use brick controller 2, but then I would only have basic control and after all that expense I really wish I could just buy something proprietary from Lego instead that would be 1000 times better, and I know won't ever require external support from Lego or third parties. 3) Lego has a that basic train remote. I remember getting a cheap AF toy car as a child, probably £10 in today's money, and it had a similar in size and feel push button remote. For a little toy car, fine. For a £200 train set, that's on the insulting side of cheeky cost cutting. For a £580 Technic flagship, no f**king way, not even close £580? Just no! 4) we agree that a bigger remote with proportional joysticks and more buttons is desirable. I think pretty much everyone wants that! But didn't they say they struggled to make that happen, even compatibility with preexisting remotes? I can't remember the issue exactly. But if you are already willing to go as far as a bigger remote with proportional joysticks and more buttons and stuff, why not go a step further with an EV3 style chip (about 10 bucks) and an inexpensive LCD screen, and a proprietary piece of firmware in the vien of remote bla bla that allows for a whole bunch of settings and configuration options such that I have described previously? With those extra steps you can solve whatever issue is preventing them from enabling third party remote compatibility (because now they have a better one of their own) as well as elimination of all issues that stem from a smart device being mandatory, enabling more complex control from a physical remote operated creation (I think brink controller only allows for more basic configuration?) whilst still enabling everything you are asking for as it is still able to connect with a smart device as an option. So far the biggest arguments against it is that it is dreaming too big, they'll never do it, I'm pretty sure I've heard that before but we have all kinds of things that were previously only dreamt of like longer pneumatics, planetary reduction hubs and now a whole new gearbox system in the Yamaha. If you would have said in 2015 that you wanted a whole new app controlled Bluetooth based system to replace powered up and it to be released in a 4000 piece excavator with 7 motors, you would have been told "you're dreaming too big". Another big argument is the cost. Well we are already willing to pay for a bigger remote with proportional controls and Bluetooth and so on. It's really not that much of a step from there to move from having multiple chips in multiple hubs, to having a singular, more capable chip in the remote and an LCD screen and some firmware. The model itself would only need basic Bluetooth receiver's that do whatever the remote tells it to do. The final big argument is do we really need this when other things are available? Not really I guess. But I can happily leave the next big expensive flagship on the shelf. And I guess we actually do need this if you want to ditch reliance on a smart devices, ditch reliance on third parties picking up the ball Lego will drop and have complex programmable physical control. It's not about need, Lego is an expensive luxury toy, if they want to charge luxury prices then what do I want in return?

Yeah, it seems there could be quite some overlap between configuration and programming. I am thinking that in CC+ you could do basic configuration of course, IE control this motor from this controller in a way that's about as easy as with PF, but you could also apply and adjust ramp up/down settings, set a servo/motor to match a given proportional control input but also use maths, multiply it's position/speed by either a percentage which you can adjust, or multiply its position/speed by the position of another proportional control input such as a rotary dial on the CC+ (I'm thinking there would be two rotary dials) or by the value given by a rotation sensor for example. I think someone could be forgiven for calling that level of configuration a basic form of programming. It probably doesn't matter if it's called configuration or programming, I think a sophisticated enough form of programming/configuration for 99% of MOCs can be done on an LCD screen and the inbuilt controllers, of which there would be many. I think what I'm dreaming of is not too dissimilar to you, I'm dreaming a bit bigger as someone said! In any case, weather it can be done this way or that, I just feel like something like this.... ....would be really cool, as well as more authentic (real life cranes are operated from this thing!) on top of everything else including making the use of a smart device purely optional even when you need a custom program for your custom creations. It just feels more Lego to me. I may be an engineer by trade, and as such my adult engineer self can certainly appreciate the efficiency of the make do with what you have already solutions, but my inner child self, the part of me that wants to play with Lego, wants a bwiiiiiig contwollah!

What if they didn't up the price? The goal is trying to justify an already high price in a way that addresses as many control+ issues that people have as possible. How would you suggest they do it, assuming the high price is set in stone by marketing? Or do you think it's not possible?

Linking to a list of smart devices does nothing to supply you with that device. It doesn't solve the issues that come with needing a compatible smart device. I would hope that CC+ wouldn't require an update. My guitar effects pedal, which also is fully programmable on the integrated LCD screen while having the option of connection to a computer, never needed an update despite having its own integrated computer that I literally stomp on. The .....um.....wadjacallit....system architecture? That would be decided before release and any subsequent motors or sensors would follow that right? Alternatively the separate receiver's would support it (like how we had v1 and V2 recievers). For new sets, the manual would include step by step, button press by button press instructions on how to program the CC+ to control your model, all done on the CC+ itself, much like control center 2 and code pilot sets did. But you would also have the option to connect via Bluetooth to download a premade program from Lego if you want. For customer support, you would contact Lego as usual, and they can guide you through the process of having them connect to your CC+ and varify/fix any issues. Once Lego has moved on then it would be like any other Lego hardware, buy one from the second hand market and use the manual to program it yourself. Could you define the difference between configuration and programming? If we take the Liebherr load sensing as an example, and in the model we have motor a driving the winch that moves the boom in towards the crane when rotating clockwise (decreasing load) and out away from the model when rotating ccw (increasing load), and we have a touch sensor that is mechanically actuated vie some spring/lever arrangement when the load gets too heavy, and then we configure it on the CC+ such that when the sensor is activated, motor a's ccw rotation is disabled and we also set a red light to come on on another output, would that be at least a simple form of programming? If the hook is connected to motor b and we can also disable that motor as well, or tell it to half its speed of rotation. We could also add logic blocks, mathematical blocks and so on, and just select what communicates with what. I agree a touch screen would be even better, but I am trying to think of ways to keep the likely high cost as low as practical. A billion dollars? Okay, maybe I don't need the whole national power grid in the box, we could probably leave that out!

I should just quickly say that this topic isn't just for me to promote my suggestions, please feel free to add your own ideas, maybe simple changes to the existing system or a whole new system, or even just go back to 9v/pf!

This is valuable feedback so thank you for this. Many exhibitors still use the old 9v train remote. It would be nice to have a mains power option for exhibitors. Maybe that could be integrated into the simple battery and control center + like it was with the first RCX. Using Arduino etc was things you suggested we could do (and I don't wish to remove those options from those that wish to take advantage of them). Why would you suggest them if there was absolutely no need for them? It is as simple as PF for the most basic of control. Anything other than that requires a smart device to program. I know you are fine with that but I am not. I would like a solution that (at least tries to) please both of us as we lie at opposite ends of the spectrum. I had a smart phone but when PU was released my phone was not compatible so I had to buy a new one, and I'm not the only one just in this forum whose phone wasn't compatible. Imagine not being able to buy and play with a new Lego model because your phone wasn't compatible, it's kinda rediculous to my mind. And things move on, tech moves on at a mind boggling rate such that things will not be supported in a short time and we shouldn't have to rely on third party enthusiasts to pick up the ball Lego dropped. The original control center and code pilot never needed continued support from Lego or from enthusiasts and I think it's possible to reboot PU such that it doesn't need it either. When I said most Lego consumers don't know about that stuff, I mean like when I go to my local toy shop and observe the people in the Lego isle, I don't see a bunch of people who would know how to program an Arduino or know about brick controller 2 or anything like that. It's mostly kids and their parents or grandparents looking for something cool to play with. I feel something like CC+ would cater to them with its cool physical controls and easy setup with full documentation out of the box (whilst also catering to you). I think it is possible to do basic programming on the hypothetical CC+, complex enough at least to control the previously released flagships but without the inverse kinematics. A few posts ago I wrote a few examples of programming on the proposed CC+. It is much more settings based, but there could be a LOT of settings on an EV3 style chip. There could be basic and advanced modes, basic mode just hides a lot of settings to keep things simple. I'm probably not explaining that side of things that well TBH. It's quite hard for us to guage customer demand, I really don't know, but how many potential buyers are put off a very expensive RC set by there not being a remote, but some app instead. How do we know what happens in the mind of some random person as they browse the isle? I think this is one of those things where people didn't know they wanted it until they see it. Perhaps unbrickme didn't know he wanted the gearbox parts of the Yamaha until he saw it, and now he sees it, it's more fascinating than even his beloved 8043. But yeah, the price is a big thing. I don't think it necessarily comes from the unit itself, the brain of the EV3 costs 10 bucks. Lego will charge what people are willing to pay. Maybe it wouldn't be quite as cheap as I think it could be but maybe not as expensive as you think it would be. Another way to look at price, the Liebherrs biggest criticism is the price. But let's say that massive price is set in stone by marketing and can't be changed. Okay, so how do we elevate the Liebherr and it's PU system to make it's massive price feel more justified to the average consumer that's not looking at price per gram of plastic while taking into account electronics and all that stuff that us die hard fans like to do? Well, they could just have made it much bigger and taller for the sake of just being bigger, but for me it has to start with having a physical remote, and having everything you need out of the box and none of the drawbacks of being reliant on a compatible smart device. Is there a better way to do that than having something like the control center + that I'm proposing?

Actually, it wouldn't have worked out of the box for me as my smart phone was not compatible, I had to get a new one. It is clearly very difficult to please everyone, from those that want the simplicity and out the of the box readiness of PF to those that want the capabilities of PU. Both systems leave something to be desired from one side or the other. I get that we don't necessarily need a whole new system, but if we are to address all the issues and complaints surrounding PU you would need new motors, a new hub, the ability to program or at least basic configuration without the need for a computer or smart phone and so much other stuff that it basically amounts to a whole new system anyway does it not? Or at the very least a soft reboot of PU. @Lok24 appears to believe everything we want is already there, we just have to expect that third party devs will always be there, write code, use Arduino, buy a smart device, buy a third party remote, just do all that and it's all there! However, most Lego consumers don't know much about all that stuff, and many that do know of it's existence have little desire to learn it just to play with their Lego. Besides the batteries, Lego always came with everything you needed, including all documentation out of the box. Predecessors to PU such as the 90s control center and code pilot allowed all programming to be done on the unit itself, no firmware updates or computer needed. Mindstorms was understood to be an exception because coding was part of the idea of mindstorms. By melding mindstorms into Technic they seem to have compromised both. Simply putting "smart device required" on the box, whilst honest, doesn't actually do anything to help provide such a device, nor does it help to alleviate the issues that come directly from having to use a third party smart device, such as having more screen time, having to allow little Timmy to have a smart device or worse, borrow yours, having to wait for firmware updates, becoming obsolete landfill and the list goes on and on. The idea behind my.....idea....was to try to meet in the middle. It's a compromise that probably won't please many people 100%, but would hopefully mostly please most people. Being Bluetooth based, it can still have optional compatibility with smart devices and computers enabling everything the PU crowd like, but a computer or smart device is no longer a necessary requirement even if you want a custom program for a custom MOC. By having separate receiver's, basic battery box with high current limit and retaining the already existing train remote for basic sets we can have the plug and play simplicity of PF, while for the big expensive flagships we can have the control center + which enables control, configuration and programming for something like 16 motors/sensors in a simple and easy way without the need for a smart phone or computer (though the option to do so will still exist it's not mandatory for programming custom MOCs) whilst also being a totally sweet physical remote that's far better for controlling your Lego creations than a third party remote because it was specifically designed by Lego to do exactly that, instead of being designed to play computer games. Besides being unfeasible (which I don't agree with as I think it's completely feasible), what's not to like? CC+ wouldn't have to cost more than the combination of two hubs and a decent third party remote and the separate receiver's mean that smaller and/or less electronically advanced sets wouldn't have to be as expensive as the current small sets with an entire smart hub just to control two motors. It can be as simple as PF, removes all concerns over the need for a smart device while retaining all the benefits of PU.

My idea doesn't have a touch screen, just a monochrome inexpensive LCD screen, a touch screen would be even better, but probably not absolutely needed. Although some programming of MOCs is inevitable for certain things, I think it could be made simple enough so that it could be done via a simple LCD screen. The unit itself would do most of the work, all you would be doing is selecting different settings to configure the inputs and outputs.

I use spread sheets at work, they are very powerful indeed and fairly easy. But it still feels like work, the opposite of fun!

@Lok24 Well yeah of course you'd have to configure all that, by "just pairing" I meant for the communication between the control center + and the receivers. In this post I give a few examples of how you can configure to the point of being able to fully program control center + right from the unit itself, it's essentially a fully programmable physical remote, everything you need right out the box with no smart device required: But a few posts after that I said we could ditch 2.4gHz in favor of bluetooth connectivity to make compatibility with the current PU system, as well as smart devices an optional feature, but not required. A lot of complaints revolve around the need to use a smart device, the need for more screen time (one thing that playing with Lego should aim to reduce, not increase) and no physical remote being available from Lego. Doing this kind of soft reboot of PU with control center +, new motors with removable and stackable leads, separate receivers and so on aims to solve all those complaints whilst retaining as many of the benefits as is practical to do so (though things like inverse kinematics might have to go unless they supply advanced premade programs, which is also a possibility, but I don't think I'd miss inverse kinematics TBH). "Just use a smart device" is not a solution to all the complaints that stem from having to use a smart device, especially not for parents and children but not for adults fans either. With a blue tooth based control center +, Lego can still release premade programs for sets and you can still have all the same coding options available if you want it. But it's optional, you are not forced to, if you don't want to do any coding, that doesn't matter because control center + is fully programmable/configurable right on the device itself. If your smart device stops working and becomes obsolete and Lego has moved on and stopped supporting it, well that wouldn't matter either, just like the original control center from the 90s it'll still work and be fully configurable even if the 3rd party developers aren't there. Control center + would not require continued support from Lego, your smart device or any third parties to be fully functional, and it all comes in the box (as it really should for $700!) If you want to buy little Timmy a mahoosive liebherr excavator but you don't want to set him loose on a smart device, again, that doesn't matter because the set instructions come with step by step instructions on how to program your control center + based model right from the unit itself, just like they did with the previous control center sets and the code pilot of the barcode truck (which also still works), so full documentation will also be provided, which is another common complaint of PU. Exactly so if a program didn't exist you would have to code your own program.

Oh, I ditched the physical code block idea, that was my first idea in this thread but others pointed out that it would take up way too much space. PF2.0 with it's control center + doesn't use physical code blocks. Programs can be created via the integrated LCD screen or via optional connection to a PC And a year or so ago, I would have completely agreed with you. I did see a lot of potential in PU and I bought a whole new bloody smart phone because of it, but I don't think it's coming to be honest. They seem to have given up on adding physical remotes, the driver chips in the hub can only just barely handle the current motors let alone anything like a buggy motor, PU will always be smart device dependent if you want anything more than the most basic of control and I don't recall there being a new PU component this year or last year (in the Technic theme anyway). PF was only around for 10 years, PU has been around for half that already. Or maybe I am thinking of things a bit wrongly here. What if, instead of control center + being based on 2.4gHz and a whole new system, it is based on bluetooth like PU? Hmmmmm, but for control center + you would still need the smart hub to communicate with and drive the motors, yes? Or maybe not....... if they released a new basic battery box (no driver chips, current limit of 7 amps or something to protect the cables) and a new stackable bluetooth receiver (which has beefier motor driver chips in it), but the PU cables aren't stackable which is another common complaint, but the new motors could have removable and stackable leads.....hmmmm.....we are getting close to a whole new system now. Okay, so instead of PF2.0 what if it was PU2.0. It's basically the same idea I have above, with the control center +, basic battery box, separate receivers, new motors etc, but instead of being 2.4gHz it's now blue tooth based, but the cable plugs are now reverted back to the PF format, allowing stacking of plugs and compatibility of all formats including optional smart devices, PU, PF and even 9V. I mean, the PU trains didn't require a smart device did they? You just paired the hub to the physical remote. So I guess you could have any number of receivers connected to a basic battery box in the model, and then just pair them to the control center +. Is blue tooth any cheaper or better than 2.4gHz? I guess for the first year you would get a small model with basic battery box and a regular motor, a medium model with a basic battery box, a couple different motors, basic remote (like the current train remote) and receiver (with the motor driver chips). No programs, just basic RC functionality. Then for the big flagship you get a bunch of motors and receivers and basic battery boxes and control center +. It's all bluetooth based and cross compatible so they wouldn't have to call it a whole new system, but a kind of soft reset of PU with these new components. It makes the use of smart devices possible but optional. Please forgive my noobishness, load what program? If I make a MOC and there's no program that exists for that MOC, what program would I load onto it?

I don't think the control center + with PF2.0 idea is quiiiiiite as bats%$t crazy as it sounds. In terms of cost, yes, the control center itself would be more expensive to make than a single smart hub, but larger and more expensive sets require multiple hubs. You would only ever need one control center, and it would also double as a physical remote better than any third party one you could buy as it would be designed specifically to control Lego creations and somewhat mimic the real life controls of real machinery. How much would it be to buy 2 hubs directly from Lego and a decent but smaller and way less cool looking third party physical remote? And in my case a smart phone to go with it? Control center + would have a decently powerful computer chip (like maybe what EV3 had or something, about $10?) in a large but mostly empty enclosure with some physical controllers, 2.4gHz radio and an inexpensive LCD screen. It would have a massive "WOW" factor that I think would appeal to younger people. And because it uses separate receivers, smaller models could also use a much smaller and much cheaper remote for basic, direct control. The control center is only needed for the big and expensive sets but would also be available separately. And yes, that industrial piece of kit pictured above is very expensive, everything industrial is very expensive and the E-top being on there is also telling, there is a significant safety element involved in controlling a 5 axle crane with one of these things which costs a ton of money in testing and certification, and it certainly isn't sold in the numbers Lego would sell. All Lego has to do is put stupid little screws on the battery cover! I really don't know anything about Python, or using it to control smart hubs or whatever, but if you wanted to control your own MOCs then wouldn't you need to be able to code your own program or at least know how to lift parts of existing code and mash them together? Maybe I'm just from a different generation, I know as a kid I would have wanted to play with something like what is pictured above than mess about with any kind of coding software. As an adult I can better appreciate it's uses but my 12 year old self would have just seen that as "boring nerdy s$%t". Control center + somehow feels both much more like a cool toy to play with, and also much more like playing with the real thing or build for real. Part of the reason for creating this thread, and trying to come up with a new direction for when TLG eventually replaced powered up was all the complaints of no physical remote and the need for third party smart devices. Not everyone is happy for their kids to own a smart device or having to have more screen time to play with Lego, which has for me always been a way to reduce screen time. And not everyone likes buying things made by Chinese child labor to play with their Lego. And yes, I did have to buy a new smart phone as my current one at the time wasn't compatible, but I did it because I saw quite some potential in it, but less than a quarter of that potential has been reached in 4 or 5 years and now I know more about the system I think it never will be. And while 3rd party options exists, Lego Technic never used to have to rely of the existence of third party options just to make it a desirable product, doing so now is a step backwards. It's not for the sake of just wanting Lego to make everything, it for the sake of all these things mentioned above as well as having everything come in the box, no additional stuff needed, reducing screen time, increasing longevity, no need to code even for complex MOCs and if we are to have $700 price tags, making it feel more worth that price. And I must re-emphasize, PU is not here forever and will be replaced with a whole new ecosystem eventually with all new hardware being developed for it. It has happened a few times before and will happen again, each time they do they try to address the concerns of the previous system. If you would have suggested the current PU system in the PF era people would have called that bats$%t also. But please don't think I don't like or enjoy reading all your comments either in support of or against it, although I firmly support my idea I am under no illusion of it being a fully formed idea and there's always room for improvements and completely different points of view. And I admit that when I suggested the PF2.0 idea with the control center +, I did think there would be a few more people excited for it. I guess it just goes to show how hard it is to come with a successor to PU or PF that pleases everybody