Tcm0

Currently it's not as simple as that and I didn't get the library to work (but haven't really tried it either).

The new hub can control other PUP hubs via BLE. Idk if it can control other large technic hubs. There is a library: https://github.com/nutki/spike-tools/blob/master/hub/lwp.py

The difference is that the new l motor contains a relative and an absolute position sensor while the old one contained no sensors. It might have to be calubrated etc. Of course the electronic pieces are much more expensive than they would cost normally. But it can also be related to savety regulations (it's a kid toy) etc. It's expensive on the first look, but not actually that expensive if you compare it to sbrick or something similar.

The BL prices reflect the market value, not the production cost. If people want train parts but not the electronic parts magnetic buffers, track and train base plates get expensive and the electronic parts get cheap. Sellers buy the sets to part out the other parts and the electronic parts stay as leftover (there is e.g. only one set to get the large wheels of the technic offroad crawler although they are super cool). Many, many fans don't want to switch to the new system so demand is very low for that - especially afols that are the main customer group of bricklink.

Another aspect is that PUP is pretty unpopular. The sellers buy train sets for the tracks and the train parts (which add up to maybe 80% of the price) and since popularity of pup is low they have to make them cheap to sell them. But it doesn't matter because they got most of the price back with the other parts.

I tried it with my BLED112 and it doesn't work either. The reason is that it doesn't use the default ble protocol but it translates it to another serial protocol (at least that's what I heared somewhere. No guarantee that it's true). The BLED112 is for development, not for endusers (yeah, the lines kinda collapse for this purpose). You need a "normal" BLE USB Dongle. Basically most if not all should work, just make sure that they support BLE. Dongles that support XP, vista and windows 7 plug and play for BLE probably don't work because BLE support was added with windows 8 or 8.1. Most have something like "you have to install the driver manually for Windows 7 and below". I use the iAmotus USB Bluetooth 4.0 EDR Wireless Micro Adapter [Low Energy]

Make sure that you have the right browser version. You need the google chrome canary build.

Your BT dongle might be incompatible. It's not a "normal" bluetooth dongle.

You could make your own remote control in the "Make" tab of the app and change the light color or turn it off.

Just a small addition: the volvo technic set will contain a large angular motor

But that doesn't work yet, does it? For me the link to the "local backup option" results in a 404.

the PUP system lacks a documentation like the mindstorm's HDK and the firmware development kit. The firmware is not open source. Idk if the wireless protocol features communication to the SPIKE hub. The SPIKE python environment is not properly documented. There are SOME high level functions that are documented but not all (see the reply of https://www.facebook.com/groups/SPIKEcommunity/permalink/1122397554805142/) and there is a lower level API that enables stuff like audio file playback and connection to other Powered Up hubs but that's not documented. You can only kinda work your way through it because the micropython os can tell you which classes it offers.

The EV3 can use the NXT's sensors (and RCX sensors if you use low level programming (EV3DEV) and have an adapter cable).

Regarding the file system: it has one and it can be read/ accessed with rshell. There is also a python file that can copy files to the hub in the spiketools github archive.

I'm pretty sure that they don't have employees because it's not a company ;) Just a project of two fans

Hmm. Then I think that original names with additional appends would be best. Simple medium linear motor (for the batmobile motor)Simple train motorMedium linear motor with rotation sensor (for the boost motor)Technic Large motor with position sensor (for Control+ L motor)Technic XL motor with position sensor (for Control+ XL Motor)Technic Medium angular motor with zero position marker (for SPIKE medium motor, with zero position marker is optional)Technic Large angular motor with zero position marker (for SPIKE large motor, with zero position marker is optional)

I think that the names are too similar and don't reflect the actual differences. What is the difference between a simple medium motor and a medium linear motor? In addition to that the first one is called simple, medium linear motor and the other one only medium linear motor in the lego shop. Both are called linear motor. I'm sure that both hubs will contain the same hardware and bricklink sorts pieces with the same form but different colors under different colors, not different names. Maybe lego will sell the yellow one only through lego education and the teal one only through the online shop. I don't see any reason for a different name since it's the same part - maybe add the color to the name. Regarding the motors see the above. You can't tell me that anyone understands the difference between the medium linear motor and the simple medium linear motor.

But you can't base the naming on the platform because that isn't consistent and it will be even more mixed up in the future. The simple linar motor is in wedo and powered up, the boost linear motor is for boost and powered up and the spike prime motors appear in the upcomming mindstorms set and will be included in a technic model this summer wave. I think that calling the technic large hub "technic large hub for spike prime" has the same problem because it will be included in the upcomming mindstorms set. We don't know which set might contain which motor in the future. Personally I would call them something like "motor with rotation sensor", "motor with position sensor" and/or "Motor with angle sensor". One might add something like "with zero position marker" My personal take would be something like this. Maybe add a "Powered Up:" in front: Simple medium motor (for the batmobile motor) Simple train motor Medium motor with rotation sensor (for the boost motor) Large motor with position sensor (for Control+ L motor) XL motor with position sensor (for Control+ XL Motor) Medium motor with position sensor and zero position marker (for SPIKE medium motor. I'm not sure if it's a good idea that the name is so similar to the other medium motors. Maybe call it large instead but then it would conflict with the official lego names) Large motor with position sensor and zero position marker (for SPIKE large motor) For the hubs I would stick with the normal names. Maybe add system or technic for the main type of brick connections. The idea of adding the number of ports is good: 2 port WeDo 2.0 system hub (I think that calling this WeDo 2.0 is okay because there won't be another set that uses the hub as it's not updateable) 2 port Move hub (for the boost hub. Move system hub sounds stupid. The name move kinda includes the motors) 2 port System hub 4 port Technic Hub 6 port Large Technic Hub (SPIKE and Mindstorms hub)

You are missing the SPIKE distance and the SPIKE force sensor. In addition to that I don't think that it's useful to call the motors smart or interactive. It doesn't tell you what they actually do or don't do. Oh and there will be a new battery box in this year's technic line with 2 ports.

I think that somewhere it was said that the control+ battery box will have 2 powered up plugs.

And an extension cable. That would make it easier/cheaper to get connectors

A controller interface customizer is announced. We have 2 controller interfaces in the Powered Up app currently with fixed control elements. Can we expect a fully customizable interface within the app? Yes. (https://racingbrick.com/2020/05/lego-powered-up-intervew/) I'm 99% sure that that was the plan from the beginning.

I think that the large angular motor will be available seperatly for normal customers in the future. One angular motor will be included in a technic set this summer wave if I am informed correctly (but I'm not sure if it's the large or the small one). Would be great but I doubt it. Beeing able to use game controllers with SPIKE (or powered up app) would solve so many problems. That's not entirely true. You can use a software console with SPIKE python (which is officially supported since the last app update). It can be done in python (https://github.com/nutki/spike-tools see convert_sound.py) however it didn't work for me. You can add notes

There is a slim possibility that the set contains 3 sensors and 4 motors. The ports are I/O after all.

We might see that in the future - or maybe not. Did you know that Powered Up hubs are numbered? E.g. Hub no. 2 is the control+ technic hub.