I think dumb battery box is good for keeping prices reasonable for future motorized sets that have only on/off function requirements.

I'd wonder if the new mindstorms (51515) would allow to control other PU hubs through Bluetooth. That would allow some interesting models. I'm thinking a smart brick inside a train which controls various railside constructions along the track.

 

Also, has anyone got their hands on a Prime or Mindstorms controller and do they support the train motors and the boost sensors. As far as I know they should, but I would love to see some conformation before I commit to buying one in the future.

@UrbanErwin

I don't think that one PU-Hub will "control" another.

And the "Large Hub" is much too big for trains.

The idea (as it works already today) is that different hubs communicate via an external programm. With that your train can trigger other actions on a different hub.

Concerning Boost/Train motors: that all worked together since years. The only problem always was that the LEGO Software  did not support all that at the release date of the components.

Other software does since a long time.

  On 6/20/2020 at 11:52 AM, Lok24 said:

And the "Large Hub" is much too big for trains.

But it's good to operate as "brain". Even if can connect to more than one smart hub...

Edited June 20, 20204 yr by GianCann

Thats very true. I referred to

  Quote

I'm thinking a smart brick inside a train which controls various railside constructions along the track. 

In your scenario it's outside the train.

Has anyone used the node-poweredup library?

I've tried it on the Raspberry Pi 4 and succeeded to clone the repo, install node.js, install Visual Studio Code, install the NPM packages, compile the library, run

sudo apt-get install bluetooth bluez libbluetooth-dev libudev-dev
sudo setcap cap_net_raw+eip $(eval readlink -f $(which node))

and finally run the LED sample, but all I get is:

pi@raspberrypi:~ $ cd node-poweredup/
pi@raspberrypi:~/node-poweredup $ node examples/leds.js
Looking for Hubs...

The hub's LED turns white and blinks every few seconds but does not change the color. The hub cannot be turned off while the program is running.

I've tried the same LED sample on Windows and it works with an ASUS Bluetooth dongle. Besides the installations mentioned above for the Raspi, I had to replace the Bluetooth driver. However, the hub connects only once, if I turn it off and on again, it doesn't connect anymore until the LED sample application is restarted. As far as I understand the code, it should connect again. Or did I miss anything?

Edited June 20, 20204 yr by legotownlinz

  On 6/20/2020 at 6:29 PM, legotownlinz said:

Has anyone used the node-poweredup library?

I've tried it on the Raspberry Pi 4 and succeeded to clone the repo, install node.js, install Visual Studio Code, install the NPM packages, compile the library, run

sudo apt-get install bluetooth bluez libbluetooth-dev libudev-dev
sudo setcap cap_net_raw+eip $(eval readlink -f $(which node))

and finally run the LED sample, but all I get is:

pi@raspberrypi:~ $ cd node-poweredup/
pi@raspberrypi:~/node-poweredup $ node examples/leds.js
Looking for Hubs...

The hub's LED turns white and blinks every few seconds but does not change the color. The hub cannot be turned off while the program is running.

I've tried the same LED sample on Windows and it works with an ASUS Bluetooth dongle. Besides the installations mentioned above for the Raspi, I had to replace the Bluetooth driver. However, the hub connects only once, if I turn it off and on again, it doesn't connect anymore until the LED sample application is restarted. As far as I understand the code, it should connect again. Or did I miss anything?

Hi @legotownlinz, node-poweredup library is actually my project. :)

Unfortunately the Raspberry Pi 4 uses a different Bluetooth chipset from the 3b, which doesn't play nice with Noble, the underlying Bluetooth library node-poweredup uses. I'm working on it on slowly, but for the time being you'd need to use a Raspberry Pi 3b.

I'm unsure as to the second issue you mention, but it'd be great if you could raise an issue on the GitHub repo so we could discuss there.

Edited June 20, 20204 yr by Mr Hobbles

Looks like 4DBrix ran into the same problem and they gave up: https://www.4dbrix.com/blog/index.php?show=000004

  On 6/20/2020 at 11:39 AM, UrbanErwin said:

I'd wonder if the new mindstorms (51515) would allow to control other PU hubs through Bluetooth. That would allow some interesting models. I'm thinking a smart brick inside a train which controls various railside constructions along the track.

 

Also, has anyone got their hands on a Prime or Mindstorms controller and do they support the train motors and the boost sensors. As far as I know they should, but I would love to see some conformation before I commit to buying one in the future.

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

  On 6/21/2020 at 9:16 AM, Tcm0 said:

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

Interesting. That means that you have a virtual port on the Large Hub pointing  to a physical port on a remote connected hub?

 

  On 6/20/2020 at 11:47 PM, Mr Hobbles said:

Hi @legotownlinz, node-poweredup library is actually my project. :)

Thanks for your library, which is very clean and elegant. 

 

  On 6/20/2020 at 11:47 PM, Mr Hobbles said:

I'm unsure as to the second issue you mention, but it'd be great if you could raise an issue on the GitHub repo so we could discuss there.

Do you have plans to use the default Windows Bluetooth stack instead of WinUsb/noble? Sharing applications is difficult if the end user has to replace drivers.

  On 6/21/2020 at 9:22 AM, Lok24 said:

Interesting. That means that you have a virtual port on the Large Hub pointing  to a physical port on a remote connected hub?

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

  On 6/20/2020 at 11:47 PM, Mr Hobbles said:

I'm unsure as to the second issue you mention, but it'd be great if you could raise an issue on the GitHub repo so we could discuss there.

The reconnection issue on Windows only happens with a hub between PC and Bluetooth dongle. I could reproduce it with these two dongles, both work fine without hub and do not allow reconnections with hubs:

ASUS USB-BT400 Bluetooth 4.0 USB Adapter  (0B05 17CB, BCM20702A0 Broadcom Corporation)
DIGITUS Adapter tiny USB Bluetooth V 4.0 (0A12 0001, Cambridge Silicon Radio Ltd)

 

 

Is it true that the value of the current power functions train sets will drop wil the new powered up system for trains? I noticed for example that the price of PF rechargable battery box has moderately increased since it was retired. So, maybe a more general question, are the power functions elements decreasing in its value with the upcoming powered system? I would assume that the prices would decrease, as the PF system becomes less useful for new sets and also has quit some shortcomings with repect to PU.

@Myowntrain if TLG stops to sell them then I'm sure the prices will increase. Until PU won't become a mature and fully usable system I expect a lot of people to stick the PF, but with limited supplies the prices will go up.

  On 6/21/2020 at 10:37 AM, legotownlinz said:

Thanks for your library, which is very clean and elegant. 

 

Do you have plans to use the default Windows Bluetooth stack instead of WinUsb/noble? Sharing applications is difficult if the end user has to replace drivers.

Thanks for the kind words about the library. :)

I'm afraid I don't have plans to do so - I don't use Windows or have access to any machines that use Windows. But of course PR's are welcome from anyone who wants to improve that side of it. However while I've heard Windows BLE support isn't fantastic, other people seem to have figured out ways to get Noble working without changing drivers, see this post on another project of mine, hopefully this helps: https://github.com/nathankellenicki/nuimojs/issues/17

Regarding your reconnection issue though, I'm willing to try helping, but I don't want to clog up this forum with support requests. :) Please raise a Github issue so we can discuss - it's also more useful for posting debug logs, etc.

Edited June 22, 20204 yr by Mr Hobbles

  On 6/9/2020 at 11:25 PM, Mr Hobbles said:

@Jetro Actually that's not true. Group 3a does have absolute zero - the LPF2 mode exists and responds appropriately, always returning to the same position. Its just not marked with a black spot on the casing - I've taken to marking mine with a marker! :) My library, "node-poweredup" fully supports it. See mode 3, APOS:

 

  lpf2hubmodeinfo Port 03, type 002f (TECHNIC_XLARGE_LINEAR_MOTOR) +3s
  lpf2hubmodeinfo Port 03, hardware version 0.0.00.1000, software version 0.0.00.1000 +0ms
  lpf2hubmodeinfo Port 03, total modes 6, input modes 011110, output modes 011111 +45ms
  lpf2hubmodeinfo Port 03, mode combinations [1110] +30ms
  lpf2hubmodeinfo Port 03, mode 0, name POWER +30ms
  lpf2hubmodeinfo Port 03, mode 0, RAW min -100, max 100 +46ms
  lpf2hubmodeinfo Port 03, mode 0, PCT min -100, max 100 +28ms
  lpf2hubmodeinfo Port 03, mode 0, SI min -100, max 100 +32ms
  lpf2hubmodeinfo Port 03, mode 0, SI symbol PCT +28ms
  lpf2hubmodeinfo Port 03, mode 0, Value 1 x 8bit, Decimal format 1.0 +31ms
  lpf2hubmodeinfo Port 03, mode 1, name SPEED +30ms
  lpf2hubmodeinfo Port 03, mode 1, RAW min -100, max 100 +31ms
  lpf2hubmodeinfo Port 03, mode 1, PCT min -100, max 100 +29ms
  lpf2hubmodeinfo Port 03, mode 1, SI min -100, max 100 +30ms
  lpf2hubmodeinfo Port 03, mode 1, SI symbol PCT +31ms
  lpf2hubmodeinfo Port 03, mode 1, Value 1 x 8bit, Decimal format 4.0 +29ms
  lpf2hubmodeinfo Port 03, mode 2, name POS +30ms
  lpf2hubmodeinfo Port 03, mode 2, RAW min -360, max 360 +30ms
  lpf2hubmodeinfo Port 03, mode 2, PCT min -100, max 100 +45ms
  lpf2hubmodeinfo Port 03, mode 2, SI min -360, max 360 +30ms
  lpf2hubmodeinfo Port 03, mode 2, SI symbol DEG +29ms
  lpf2hubmodeinfo Port 03, mode 2, Value 1 x 32bit, Decimal format 4.0 +31ms
  lpf2hubmodeinfo Port 03, mode 3, name APOS +30ms
  lpf2hubmodeinfo Port 03, mode 3, RAW min -360, max 360 +30ms
  lpf2hubmodeinfo Port 03, mode 3, PCT min -100, max 100 +44ms
  lpf2hubmodeinfo Port 03, mode 3, SI min -360, max 360 +16ms
  lpf2hubmodeinfo Port 03, mode 3, SI symbol DEG +30ms
  lpf2hubmodeinfo Port 03, mode 3, Value 1 x 16bit, Decimal format 3.0 +29ms
  lpf2hubmodeinfo Port 03, mode 4, name LOAD +31ms
  lpf2hubmodeinfo Port 03, mode 4, RAW min 0, max 127 +30ms
  lpf2hubmodeinfo Port 03, mode 4, PCT min 0, max 100 +31ms
  lpf2hubmodeinfo Port 03, mode 4, SI min 0, max 127 +29ms
  lpf2hubmodeinfo Port 03, mode 4, SI symbol PCT +30ms
  lpf2hubmodeinfo Port 03, mode 4, Value 1 x 8bit, Decimal format 1.0 +30ms
  lpf2hubmodeinfo Port 03, mode 5, name CALIB +30ms
  lpf2hubmodeinfo Port 03, mode 5, RAW min 0, max 512 +30ms
  lpf2hubmodeinfo Port 03, mode 5, PCT min 0, max 100 +30ms
  lpf2hubmodeinfo Port 03, mode 5, SI min 0, max 512 +29ms
  lpf2hubmodeinfo Port 03, mode 5, SI symbol RAW +31ms
  lpf2hubmodeinfo Port 03, mode 5, Value 3 x 16bit, Decimal format 3.0 +30ms

Compare with the Technic Large Angular Motor (SPIKE Prime). Exactly the same capabilities. Notice even the hardware and software versions are the same:
 

  lpf2hubmodeinfo Port 03, type 0031 (TECHNIC_LARGE_ANGULAR_MOTOR) +4s
  lpf2hubmodeinfo Port 03, hardware version 0.0.00.1000, software version 0.0.00.1000 +0ms
  lpf2hubmodeinfo Port 03, total modes 6, input modes 011110, output modes 011111 +32ms
  lpf2hubmodeinfo Port 03, mode combinations [1110] +28ms
  lpf2hubmodeinfo Port 03, mode 0, name POWER +31ms
  lpf2hubmodeinfo Port 03, mode 0, RAW min -100, max 100 +31ms
  lpf2hubmodeinfo Port 03, mode 0, PCT min -100, max 100 +29ms
  lpf2hubmodeinfo Port 03, mode 0, SI min -100, max 100 +44ms
  lpf2hubmodeinfo Port 03, mode 0, SI symbol PCT +32ms
  lpf2hubmodeinfo Port 03, mode 0, Value 1 x 8bit, Decimal format 1.0 +28ms
  lpf2hubmodeinfo Port 03, mode 1, name SPEED +31ms
  lpf2hubmodeinfo Port 03, mode 1, RAW min -100, max 100 +45ms
  lpf2hubmodeinfo Port 03, mode 1, PCT min -100, max 100 +30ms
  lpf2hubmodeinfo Port 03, mode 1, SI min -100, max 100 +30ms
  lpf2hubmodeinfo Port 03, mode 1, SI symbol PCT +30ms
  lpf2hubmodeinfo Port 03, mode 1, Value 1 x 8bit, Decimal format 4.0 +29ms
  lpf2hubmodeinfo Port 03, mode 2, name POS +31ms
  lpf2hubmodeinfo Port 03, mode 2, RAW min -360, max 360 +30ms
  lpf2hubmodeinfo Port 03, mode 2, PCT min -100, max 100 +30ms
  lpf2hubmodeinfo Port 03, mode 2, SI min -360, max 360 +30ms
  lpf2hubmodeinfo Port 03, mode 2, SI symbol DEG +30ms
  lpf2hubmodeinfo Port 03, mode 2, Value 1 x 32bit, Decimal format 4.0 +30ms
  lpf2hubmodeinfo Port 03, mode 3, name APOS +30ms
  lpf2hubmodeinfo Port 03, mode 3, RAW min -360, max 360 +30ms
  lpf2hubmodeinfo Port 03, mode 3, PCT min -100, max 100 +31ms
  lpf2hubmodeinfo Port 03, mode 3, SI min -360, max 360 +29ms
  lpf2hubmodeinfo Port 03, mode 3, SI symbol DEG +30ms
  lpf2hubmodeinfo Port 03, mode 3, Value 1 x 16bit, Decimal format 3.0 +29ms
  lpf2hubmodeinfo Port 03, mode 4, name LOAD +32ms
  lpf2hubmodeinfo Port 03, mode 4, RAW min 0, max 127 +29ms
  lpf2hubmodeinfo Port 03, mode 4, PCT min 0, max 100 +31ms
  lpf2hubmodeinfo Port 03, mode 4, SI min 0, max 127 +29ms
  lpf2hubmodeinfo Port 03, mode 4, SI symbol PCT +31ms
  lpf2hubmodeinfo Port 03, mode 4, Value 1 x 8bit, Decimal format 1.0 +29ms
  lpf2hubmodeinfo Port 03, mode 5, name CALIB +30ms
  lpf2hubmodeinfo Port 03, mode 5, RAW min 0, max 512 +30ms
  lpf2hubmodeinfo Port 03, mode 5, PCT min 0, max 100 +30ms
  lpf2hubmodeinfo Port 03, mode 5, SI min 0, max 512 +44ms
  lpf2hubmodeinfo Port 03, mode 5, SI symbol RAW +16ms
  lpf2hubmodeinfo Port 03, mode 5, Value 3 x 16bit, Decimal format 3.0 +31ms

For final reference, this is the (much less capable) Medium Linear Motor (Boost). No APOS:

 

  lpf2hubmodeinfo Port 03, type 0026 (MEDIUM_LINEAR_MOTOR) +4s
  lpf2hubmodeinfo Port 03, hardware version 1.0.00.0000, software version 1.0.00.0000 +1ms
  lpf2hubmodeinfo Port 03, total modes 3, input modes 110, output modes 111 +46ms
  lpf2hubmodeinfo Port 03, mode combinations [110] +29ms
  lpf2hubmodeinfo Port 03, mode 0, name POWER +30ms
  lpf2hubmodeinfo Port 03, mode 0, RAW min -100, max 100 +30ms
  lpf2hubmodeinfo Port 03, mode 0, PCT min -100, max 100 +30ms
  lpf2hubmodeinfo Port 03, mode 0, SI min -100, max 100 +30ms
  lpf2hubmodeinfo Port 03, mode 0, SI symbol PCT +30ms
  lpf2hubmodeinfo Port 03, mode 0, Value 1 x 8bit, Decimal format 1.0 +30ms
  lpf2hubmodeinfo Port 03, mode 1, name SPEED +30ms
  lpf2hubmodeinfo Port 03, mode 1, RAW min -100, max 100 +30ms
  lpf2hubmodeinfo Port 03, mode 1, PCT min -100, max 100 +30ms
  lpf2hubmodeinfo Port 03, mode 1, SI min -100, max 100 +30ms
  lpf2hubmodeinfo Port 03, mode 1, SI symbol PCT +30ms
  lpf2hubmodeinfo Port 03, mode 1, Value 1 x 8bit, Decimal format 4.0 +30ms
  lpf2hubmodeinfo Port 03, mode 2, name POS +30ms
  lpf2hubmodeinfo Port 03, mode 2, RAW min -360, max 360 +30ms
  lpf2hubmodeinfo Port 03, mode 2, PCT min -100, max 100 +15ms
  lpf2hubmodeinfo Port 03, mode 2, SI min -360, max 360 +30ms
  lpf2hubmodeinfo Port 03, mode 2, SI symbol DEG +30ms
  lpf2hubmodeinfo Port 03, mode 2, Value 1 x 32bit, Decimal format 4.0 +60ms

 

Hello,

On Philos Page there are records of the Initialisation on UART communication of the Motors of Type 2E & 2F

There are reported 6 Mode (0x00 to 0x05).

Mode 0x04 is named CALIB and Mode 0x05 is called Stats.

Your Tabel shows different content for Mode 0x04 and 0x05 of this Motors.

Was there changed the Motor-firmware (HW-Version)?
Can you tell, how you get your information?

 

Johannes

 

  On 8/19/2019 at 11:15 AM, GianCann said:

Exploring the LEGO App APK file, i've found several firmware file:

 

I tried to reproduce your findings but failed.

Can you tell the Link where you found this APK File containing the Firmware Files ?

Is this the right Link and right Version (3.2.0) :

https://apkpure.com/lego%C2%AE-powered-up/com.lego.common.poweredup

 

 

  On 6/22/2020 at 1:42 PM, BrickTronic said:

I tried to reproduce your findings but failed.

With the new versions of the App, this method isn't more valid.

Sorry...

  On 6/22/2020 at 12:11 PM, BrickTronic said:

Hello,

On Philos Page there are records of the Initialisation on UART communication of the Motors of Type 2E & 2F

There are reported 6 Mode (0x00 to 0x05).

Mode 0x04 is named CALIB and Mode 0x05 is called Stats.

Your Tabel shows different content for Mode 0x04 and 0x05 of this Motors.

Was there changed the Motor-firmware (HW-Version)?
Can you tell, how you get your information?

 

Johannes

 

Yes, this has been observed elsewhere too. For some reason depending on whether you inspect the mode capabilities on the Control+ hub or the Boost Move Hub, the last two capabilities are different. I'm not sure which hub @Philo did his testing on, but its interesting that different hubs report different modes. Unless this is happening at the protocol level, perhaps the hub is doing its own interpretations? Note the software version is different on different hubs.

I use node-poweredup with DEBUG=lpf2hubmodeinfo set to find out this information.

Here is the mode information of the Technic Large Motor, attached to the Technic Medium hub (Control+):

  lpf2hubmodeinfo Port 00, type 002e (TECHNIC_LARGE_LINEAR_MOTOR) +5s
  lpf2hubmodeinfo Port 00, hardware version 0.0.00.1000, software version 0.0.00.1000 +1ms
  lpf2hubmodeinfo Port 00, total modes 6, input modes 011110, output modes 011111 +30ms
  lpf2hubmodeinfo Port 00, mode combinations [1110] +29ms
  lpf2hubmodeinfo Port 00, mode 0, name POWER +31ms
  lpf2hubmodeinfo Port 00, mode 0, RAW min -100, max 100 +29ms
  lpf2hubmodeinfo Port 00, mode 0, PCT min -100, max 100 +32ms
  lpf2hubmodeinfo Port 00, mode 0, SI min -100, max 100 +28ms
  lpf2hubmodeinfo Port 00, mode 0, SI symbol PCT +32ms
  lpf2hubmodeinfo Port 00, mode 0, Value 1 x 8bit, Decimal format 1.0 +28ms
  lpf2hubmodeinfo Port 00, mode 1, name SPEED +45ms
  lpf2hubmodeinfo Port 00, mode 1, RAW min -100, max 100 +15ms
  lpf2hubmodeinfo Port 00, mode 1, PCT min -100, max 100 +31ms
  lpf2hubmodeinfo Port 00, mode 1, SI min -100, max 100 +43ms
  lpf2hubmodeinfo Port 00, mode 1, SI symbol PCT +16ms
  lpf2hubmodeinfo Port 00, mode 1, Value 1 x 8bit, Decimal format 4.0 +30ms
  lpf2hubmodeinfo Port 00, mode 2, name POS +30ms
  lpf2hubmodeinfo Port 00, mode 2, RAW min -360, max 360 +31ms
  lpf2hubmodeinfo Port 00, mode 2, PCT min -100, max 100 +29ms
  lpf2hubmodeinfo Port 00, mode 2, SI min -360, max 360 +30ms
  lpf2hubmodeinfo Port 00, mode 2, SI symbol DEG +30ms
  lpf2hubmodeinfo Port 00, mode 2, Value 1 x 32bit, Decimal format 4.0 +30ms
  lpf2hubmodeinfo Port 00, mode 3, name APOS +30ms
  lpf2hubmodeinfo Port 00, mode 3, RAW min -360, max 360 +31ms
  lpf2hubmodeinfo Port 00, mode 3, PCT min -100, max 100 +29ms
  lpf2hubmodeinfo Port 00, mode 3, SI min -360, max 360 +30ms
  lpf2hubmodeinfo Port 00, mode 3, SI symbol DEG +30ms
  lpf2hubmodeinfo Port 00, mode 3, Value 1 x 16bit, Decimal format 3.0 +31ms
  lpf2hubmodeinfo Port 00, mode 4, name LOAD +29ms
  lpf2hubmodeinfo Port 00, mode 4, RAW min 0, max 127 +31ms
  lpf2hubmodeinfo Port 00, mode 4, PCT min 0, max 100 +31ms
  lpf2hubmodeinfo Port 00, mode 4, SI min 0, max 127 +28ms
  lpf2hubmodeinfo Port 00, mode 4, SI symbol PCT +30ms
  lpf2hubmodeinfo Port 00, mode 4, Value 1 x 8bit, Decimal format 1.0 +30ms
  lpf2hubmodeinfo Port 00, mode 5, name CALIB +31ms
  lpf2hubmodeinfo Port 00, mode 5, RAW min 0, max 512 +29ms
  lpf2hubmodeinfo Port 00, mode 5, PCT min 0, max 100 +31ms
  lpf2hubmodeinfo Port 00, mode 5, SI min 0, max 512 +29ms
  lpf2hubmodeinfo Port 00, mode 5, SI symbol RAW +30ms
  lpf2hubmodeinfo Port 00, mode 5, Value 3 x 16bit, Decimal format 3.0 +31ms

And this is the mode information of the same motor attached to the Move Hub (Boost):

 

  lpf2hubmodeinfo Port 02, type 002e (TECHNIC_LARGE_LINEAR_MOTOR) +5s
  lpf2hubmodeinfo Port 02, hardware version 0.0.00.0004, software version 1.0.00.0000 +0ms
  lpf2hubmodeinfo Port 02, total modes 6, input modes 001110, output modes 001111 +30ms
  lpf2hubmodeinfo Port 02, mode combinations [1110] +29ms
  lpf2hubmodeinfo Port 02, mode 0, name POWER +32ms
  lpf2hubmodeinfo Port 02, mode 0, RAW min -100, max 100 +28ms
  lpf2hubmodeinfo Port 02, mode 0, PCT min -100, max 100 +32ms
  lpf2hubmodeinfo Port 02, mode 0, SI min -100, max 100 +43ms
  lpf2hubmodeinfo Port 02, mode 0, SI symbol PCT +32ms
  lpf2hubmodeinfo Port 02, mode 0, Value 1 x 8bit, Decimal format 4.0 +28ms
  lpf2hubmodeinfo Port 02, mode 1, name SPEED +32ms
  lpf2hubmodeinfo Port 02, mode 1, RAW min -100, max 100 +28ms
  lpf2hubmodeinfo Port 02, mode 1, PCT min -100, max 100 +30ms
  lpf2hubmodeinfo Port 02, mode 1, SI min -100, max 100 +31ms
  lpf2hubmodeinfo Port 02, mode 1, SI symbol PCT +30ms
  lpf2hubmodeinfo Port 02, mode 1, Value 1 x 8bit, Decimal format 4.0 +45ms
  lpf2hubmodeinfo Port 02, mode 2, name POS +30ms
  lpf2hubmodeinfo Port 02, mode 2, RAW min -360, max 360 +61ms
  lpf2hubmodeinfo Port 02, mode 2, PCT min -100, max 100 +29ms
  lpf2hubmodeinfo Port 02, mode 2, SI min -360, max 360 +30ms
  lpf2hubmodeinfo Port 02, mode 2, SI symbol DEG +30ms
  lpf2hubmodeinfo Port 02, mode 2, Value 1 x 32bit, Decimal format 11.0 +30ms
  lpf2hubmodeinfo Port 02, mode 3, name APOS +45ms
  lpf2hubmodeinfo Port 02, mode 3, RAW min -180, max 179 +29ms
  lpf2hubmodeinfo Port 02, mode 3, PCT min -200, max 200 +32ms
  lpf2hubmodeinfo Port 02, mode 3, SI min -180, max 179 +29ms
  lpf2hubmodeinfo Port 02, mode 3, SI symbol DEG +31ms
  lpf2hubmodeinfo Port 02, mode 3, Value 1 x 16bit, Decimal format 3.0 +28ms
  lpf2hubmodeinfo Port 02, mode 4, name CALIB +31ms
  lpf2hubmodeinfo Port 02, mode 4, RAW min 0, max 3600 +29ms
  lpf2hubmodeinfo Port 02, mode 4, PCT min 0, max 100 +32ms
  lpf2hubmodeinfo Port 02, mode 4, SI min 0, max 3600 +58ms
  lpf2hubmodeinfo Port 02, mode 4, SI symbol CAL +31ms
  lpf2hubmodeinfo Port 02, mode 4, Value 2 x 16bit, Decimal format 5.0 +30ms
  lpf2hubmodeinfo Port 02, mode 5, name STATS +30ms
  lpf2hubmodeinfo Port 02, mode 5, RAW min 0, max 65535 +44ms
  lpf2hubmodeinfo Port 02, mode 5, PCT min 0, max 100 +32ms
  lpf2hubmodeinfo Port 02, mode 5, SI min 0, max 65535 +28ms
  lpf2hubmodeinfo Port 02, mode 5, SI symbol MIN +32ms
  lpf2hubmodeinfo Port 02, mode 5, Value 14 x 16bit, Decimal format 5.0 +29ms

 

Edited June 22, 20204 yr by Mr Hobbles

  On 6/22/2020 at 3:44 PM, Mr Hobbles said:

I'm not sure which hub @Philo did his testing on

As far as I remember, that was City hub...

  On 6/23/2020 at 9:12 AM, Philo said:

As far as I remember, that was City hub...

I think, the main difference is, that Data at Philos Page was recorded RXD & TXD Lines between Hub and Motor/Sensor by Logic-Analyser.

There was especially records available of initialisation phase at 2400Bd.

Data that Nathaniel evaluated are obviously done by BLE Requests Port-Info-Request (0x21) and Port-Mode-Info-Request (0x22).

But there seems to be some commands after Initialisation between Hub and Motor/Device that causes observed deviations.

One example would be the UART Write-Command : "0x5C 0x23 0x00 0x10 0x20 0x30 0x00 0x00 0x00 Chk-Sum" that redefined UART Data Frame of Mode 0 of the Control+ Motors. It seems to be issued by BLE-Command 0x42 (Port-Input-Format-Setup).

So deviations of Mode 4 and Mode 5 seems to be also issued after Initialisation by dedicated commands from Control+ Hub or the Control+ APP.

But I does not have a UART communication record between Control+ Hub and Motor/Sensor to can confirm this.

  On 6/23/2020 at 12:17 PM, BrickTronic said:

I think, the main difference is, that Data at Philos Page was recorded RXD & TXD Lines between Hub and Motor/Sensor by Logic-Analyser. 

Another possible difference: I recorded the initialization sequence during hub power up without any BT sync with  smart device. Any setup done on app initiative was thus not done.

  On 6/12/2020 at 5:42 PM, Mr Hobbles said:

...

The interesting thing is that it's been pointed out to me that the SPIKE Prime app received an update last week, which adds support for the new Mindstorms motors. They also seem to have different LPF2 device ids!

I'm struggling to think why these motors need new device ids if the motor is functionally the same. Perhaps just so the UI can show the appropriate coloured motors in the SPIKE Prime/Mindstorms apps? Or is there a slight functional difference between the SPIKE Prime and Mindstorms motors?
 

 e[e.FlipperMediumMotor = 48] = "FlipperMediumMotor",
 e[e.FlipperLargeMotor = 49] = "FlipperLargeMotor",
 e[e.StoneGreyMediumMotor = 75] = "StoneGreyMediumMotor",
 e[e.StoneGreyLargeMotor = 76] = "StoneGreyLargeMotor"

 

Hello,

Sorry for still questioning about Motor-Data

You shared Data of Motor ID 0x31

  lpf2hubmodeinfo Port 03, type 0031 (TECHNIC_LARGE_ANGULAR_MOTOR) +4s
  lpf2hubmodeinfo Port 03, hardware version 0.0.00.1000, software version 0.0.00.1000 +0ms
  lpf2hubmodeinfo Port 03, total modes 6, input modes 011110, output modes 011111 +32ms
  lpf2hubmodeinfo Port 03, mode combinations [1110] +28ms
  lpf2hubmodeinfo Port 03, mode 0, name POWER +31ms
  lpf2hubmodeinfo Port 03, mode 0, RAW min -100, max 100 +31ms
  lpf2hubmodeinfo Port 03, mode 0, PCT min -100, max 100 +29ms
  lpf2hubmodeinfo Port 03, mode 0, SI min -100, max 100 +44ms
  lpf2hubmodeinfo Port 03, mode 0, SI symbol PCT +32ms
  lpf2hubmodeinfo Port 03, mode 0, Value 1 x 8bit, Decimal format 1.0 +28ms
  lpf2hubmodeinfo Port 03, mode 1, name SPEED +31ms
  lpf2hubmodeinfo Port 03, mode 1, RAW min -100, max 100 +45ms
  lpf2hubmodeinfo Port 03, mode 1, PCT min -100, max 100 +30ms
  lpf2hubmodeinfo Port 03, mode 1, SI min -100, max 100 +30ms
  lpf2hubmodeinfo Port 03, mode 1, SI symbol PCT +30ms
  lpf2hubmodeinfo Port 03, mode 1, Value 1 x 8bit, Decimal format 4.0 +29ms
  lpf2hubmodeinfo Port 03, mode 2, name POS +31ms
  lpf2hubmodeinfo Port 03, mode 2, RAW min -360, max 360 +30ms
  lpf2hubmodeinfo Port 03, mode 2, PCT min -100, max 100 +30ms
  lpf2hubmodeinfo Port 03, mode 2, SI min -360, max 360 +30ms
  lpf2hubmodeinfo Port 03, mode 2, SI symbol DEG +30ms
  lpf2hubmodeinfo Port 03, mode 2, Value 1 x 32bit, Decimal format 4.0 +30ms
  lpf2hubmodeinfo Port 03, mode 3, name APOS +30ms
  lpf2hubmodeinfo Port 03, mode 3, RAW min -360, max 360 +30ms
  lpf2hubmodeinfo Port 03, mode 3, PCT min -100, max 100 +31ms
  lpf2hubmodeinfo Port 03, mode 3, SI min -360, max 360 +29ms
  lpf2hubmodeinfo Port 03, mode 3, SI symbol DEG +30ms
  lpf2hubmodeinfo Port 03, mode 3, Value 1 x 16bit, Decimal format 3.0 +29ms
  lpf2hubmodeinfo Port 03, mode 4, name LOAD +32ms
  lpf2hubmodeinfo Port 03, mode 4, RAW min 0, max 127 +29ms
  lpf2hubmodeinfo Port 03, mode 4, PCT min 0, max 100 +31ms
  lpf2hubmodeinfo Port 03, mode 4, SI min 0, max 127 +29ms
  lpf2hubmodeinfo Port 03, mode 4, SI symbol PCT +31ms
  lpf2hubmodeinfo Port 03, mode 4, Value 1 x 8bit, Decimal format 1.0 +29ms
  lpf2hubmodeinfo Port 03, mode 5, name CALIB +30ms
  lpf2hubmodeinfo Port 03, mode 5, RAW min 0, max 512 +30ms
  lpf2hubmodeinfo Port 03, mode 5, PCT min 0, max 100 +30ms
  lpf2hubmodeinfo Port 03, mode 5, SI min 0, max 512 +44ms
  lpf2hubmodeinfo Port 03, mode 5, SI symbol RAW +16ms
  lpf2hubmodeinfo Port 03, mode 5, Value 3 x 16bit, Decimal format 3.0 +31ms

 

So does new Motors with IDs (0x4B & 0x4C) contain identical Data compared to  Motor 0x31 or are there some (small) differences like between Contol+ L an XL Motors.

  On 6/26/2020 at 10:29 AM, BrickTronic said:

Hello,

Sorry for still questioning about Motor-Data

You shared Data of Motor ID 0x31

So does new Motors with IDs (0x4B & 0x4C) contain identical Data compared to  Motor 0x31 or are there some (small) differences like between Contol+ L an XL Motors.

I don't recall seeing any differences in the Control+ L and XL motors? There are RPM and power draw differences as Philo documented, but unless my memory is failing me I think the modes, capabilities and version revisions are identical. The same for the SPIKE Prime motors.

Regarding 0x4b and 0x4c, I don't think anybody actually has their hands on those motors yet, so we don't know. But I fully expect them to be identical to the Control+ motors and the SPIKE Prime angular motors.

Edited June 26, 20204 yr by Mr Hobbles