New LEGO Hub support - 42176 Porsche GT4 e-Performance

[toorisrael]

Hi.
Can we get some info about the work-in-progress for the new hub?
Will it be possible to run Pybricks on this hub?
Is there something we can do to help you support this hub?

It has been already added to LEGO Control+ app (public version), also it seems it can enter bootloader probably through LEGO Wireless Protocol. I couldn't get it to connect to the other hub running Pybricks Firmware with LWP3Device(0x84, name=None, timeout=10000), so probably there are slight changes.

[dlech]

I have to wait a few more days to get one in the USA - not available to buy until 1 Aug.

[dlech]

If you want to try to do a Bluetooth packet capture of the firmware update or other various operations, that could be helpful to see how it is different from other hubs.

[toorisrael]

Already tried it before Control+ update, HUB is broadcasting:
Device 34:68:B5:1C:BD:3E detected with RSSI -50
Advertisement Data: AdvertisementData(local_name='Technic Move ', manufacturer_data={919: b'\x00\x84\x02\xff\x01\x00'}, service_uuids=['00001623-1212-efde-1623-785feabcd123'], tx_power=0, rssi=-50)
Manufacturer ID: 919
Manufacturer Data: b'\x00\x84\x02\xff\x01\x00' length: 6

and the old Technic Hub running official LEGO firmware:
Device 90:84:2B:7E:AE:82 detected with RSSI -66
Advertisement Data: AdvertisementData(local_name='Technic Hub', manufacturer_data={919: b'\x00\x80\x06\x00a\x00'}, service_uuids=['00001623-1212-efde-1623-785feabcd123'], tx_power=0, rssi=-66)
Manufacturer ID: 919
Manufacturer Data: b'\x00\x80\x06\x00a\x00' length: 6

I will soon try to capture communication with Control+ (but sadly firmware update happend only once, so I'm just guessing it was a command through LWP3).

[dlech]

local_name='Technic Move ',

Hmm... we already have a TechnicHub and a MoveHub. Do we call this one hub = TechnicMoveHub() or is that too confusing? It is kind of a combination of those two hubs, so it does kind of make sense to me.

[vascolp]

Mechnic? Mochnic?
:-)

[toorisrael]

I've managed to connect to the hub with this modification to brickcontroller2 Android app, so it seems it still uses similar LWP3. Although ports controlling doesn't work.
The name TechnicMoveHub is fine for me.

[legomania76]

Could you please explain to me how I can update the brickcontroller2 app on my Android phone? I'd love to be able to control my Porsche GT4 e-Performance with my PS5 controller.

[toorisrael]

And here is the device list scan with sharpbrick/powered-up

Scan Started. Please select the Hub (using a number keys or 'q' to terminate):
1: 132 (with address 34:68:B5:1C:BD:3E)
1
Selected 132 with key 1
Discover Ports. Receiving Messages ...
.............................................................................................................................................................................................................................................................
Discover Ports Function: 252 / 252
- Hub: 0x00 / 0
  - Port: 0x32 / 50
    - IOTypeId: 86 / 0x0056 / 86
      Revision: SW: 0.0.0.2, HW: 0.0.0.1
      Capabilities: Output Input
      ModeCombinations: []
    - Mode 0: Name: POWER, Symbol: PCT, Capability: Input Output
      - DataSet: 1x SByte, TotalFigures: 1, Decimals: 0
        Input Mapping: Absolute
        Output Mapping: Absolute
        Raw Min:    -100, Max:     100
        Pct Min:    -100, Max:     100 (pass-through)
        SI  Min:    -100, Max:     100 (pass-through)
    - Mode 1: Name: SPEED, Symbol: PCT, Capability: Output
      - DataSet: 1x SByte, TotalFigures: 4, Decimals: 0
        Output Mapping: Absolute
        Raw Min:    -100, Max:     100
        Pct Min:    -100, Max:     100 (pass-through)
        SI  Min:    -100, Max:     100 (pass-through)
    - Mode 2: Name: POS, Symbol: DEG, Capability: Input Output
      - DataSet: 1x Int32, TotalFigures: 4, Decimals: 0
        Input Mapping: Relative
        Output Mapping: Relative
        Raw Min:    -360, Max:     360
        Pct Min:    -100, Max:     100 (scaling)
        SI  Min:    -360, Max:     360 (pass-through)
    - Mode 3: Name: GOPOS, Symbol: DEG, Capability: Input Output
      - DataSet: 1x Int16, TotalFigures: 4, Decimals: 0
        Input Mapping: Relative
        Output Mapping: Relative
        Raw Min:    -180, Max:     179
        Pct Min:    -100, Max:     100 (scaling)
        SI  Min:    -180, Max:     179 (pass-through)
    - Mode 4: Name: STATS, Symbol: DEG, Capability: Output
      - DataSet: 3x Int32, TotalFigures: 10, Decimals: 0
        Output Mapping: Absolute
        Raw Min:       0, Max: 4.2949673E+09
        Pct Min:       0, Max:       0 (scaling)
        SI  Min:       0, Max: 4.2949673E+09 (pass-through)
  - Port: 0x33 / 51
    - IOTypeId: 86 / 0x0056 / 86
      Revision: SW: 0.0.0.2, HW: 0.0.0.1
      Capabilities: Output Input
      ModeCombinations: []
    - Mode 0: Name: POWER, Symbol: PCT, Capability: Input Output
      - DataSet: 1x SByte, TotalFigures: 1, Decimals: 0
        Input Mapping: Absolute
        Output Mapping: Absolute
        Raw Min:    -100, Max:     100
        Pct Min:    -100, Max:     100 (pass-through)
        SI  Min:    -100, Max:     100 (pass-through)
    - Mode 1: Name: SPEED, Symbol: PCT, Capability: Output
      - DataSet: 1x SByte, TotalFigures: 4, Decimals: 0
        Output Mapping: Absolute
        Raw Min:    -100, Max:     100
        Pct Min:    -100, Max:     100 (pass-through)
        SI  Min:    -100, Max:     100 (pass-through)
    - Mode 2: Name: POS, Symbol: DEG, Capability: Input Output
      - DataSet: 1x Int32, TotalFigures: 4, Decimals: 0
        Input Mapping: Relative
        Output Mapping: Relative
        Raw Min:    -360, Max:     360
        Pct Min:    -100, Max:     100 (scaling)
        SI  Min:    -360, Max:     360 (pass-through)
    - Mode 3: Name: GOPOS, Symbol: DEG, Capability: Input Output
      - DataSet: 1x Int16, TotalFigures: 4, Decimals: 0
        Input Mapping: Relative
        Output Mapping: Relative
        Raw Min:    -180, Max:     179
        Pct Min:    -100, Max:     100 (scaling)
        SI  Min:    -180, Max:     179 (pass-through)
    - Mode 4: Name: STATS, Symbol: DEG, Capability: Output
      - DataSet: 3x Int32, TotalFigures: 10, Decimals: 0
        Output Mapping: Absolute
        Raw Min:       0, Max: 4.2949673E+09
        Pct Min:       0, Max:       0 (scaling)
        SI  Min:       0, Max: 4.2949673E+09 (pass-through)
  - Port: 0x34 / 52
    - IOTypeId: 87 / 0x0057 / 87
      Revision: SW: 0.0.0.2, HW: 0.0.0.1
      Capabilities: Output Input
      ModeCombinations: []
    - Mode 0: Name: POWER, Symbol: PCT, Capability: Input Output
      - DataSet: 1x SByte, TotalFigures: 4, Decimals: 0
        Input Mapping: Absolute
        Output Mapping: Absolute
        Raw Min:    -100, Max:     100
        Pct Min:    -100, Max:     100 (pass-through)
        SI  Min:    -100, Max:     100 (pass-through)
    - Mode 1: Name: SPEED, Symbol: PCT, Capability: Output
      - DataSet: 1x SByte, TotalFigures: 4, Decimals: 0
        Output Mapping: Absolute
        Raw Min:    -100, Max:     100
        Pct Min:    -100, Max:     100 (pass-through)
        SI  Min:    -100, Max:     100 (pass-through)
    - Mode 2: Name: POS, Symbol: DEG, Capability: Input Output
      - DataSet: 1x Int32, TotalFigures: 4, Decimals: 0
        Input Mapping: Relative
        Output Mapping: Relative
        Raw Min:    -360, Max:     360
        Pct Min:    -100, Max:     100 (scaling)
        SI  Min:    -360, Max:     360 (pass-through)
    - Mode 3: Name: GOPOS, Symbol: DEG, Capability: Input Output
      - DataSet: 1x Int16, TotalFigures: 4, Decimals: 0
        Input Mapping: Relative
        Output Mapping: Relative
        Raw Min:    -180, Max:     179
        Pct Min:    -100, Max:     100 (scaling)
        SI  Min:    -180, Max:     179 (pass-through)
    - Mode 4: Name: STATS, Symbol: DEG, Capability: Output
      - DataSet: 3x Int32, TotalFigures: 10, Decimals: 0
        Output Mapping: Absolute
        Raw Min:       0, Max: 4.2949673E+09
        Pct Min:       0, Max:       0 (scaling)
        SI  Min:       0, Max: 4.2949673E+09 (pass-through)
  - Port: 0x35 / 53
    - IOTypeId: 88 / 0x0058 / 88
      Revision: SW: 0.0.0.1, HW: 0.0.0.1
      Capabilities: Input
      ModeCombinations: []
    - Mode 0: Name: 6LEDS, Symbol: BIN, Capability: Input
      - DataSet: 2x SByte, TotalFigures: 8, Decimals: 0
        Input Mapping: SupportsNull Absolute Discrete
        Raw Min:       0, Max:      63
        Pct Min:       0, Max:       0 (scaling)
        SI  Min:       0, Max:      63 (pass-through)
  - Port: 0x36 / 54
    - IOTypeId: 89 / 0x0059 / 89
      Revision: SW: 0.0.0.1, HW: 0.0.0.1
      Capabilities: Output Input
      ModeCombinations: []
    - Mode 0: Name: PLAYVM, Symbol: na, Capability: Input Output
      - DataSet: 8x SByte, TotalFigures: 4, Decimals: 0
        Input Mapping: Discrete
        Output Mapping: Discrete
        Raw Min:    -100, Max:     100
        Pct Min:    -100, Max:     100 (pass-through)
        SI  Min:    -100, Max:     100 (pass-through)
  - Port: 0x37 / 55
    - IOTypeId: TechnicMediumHubTemperatureSensor / 0x003C / 60
      Revision: SW: 0.0.0.1, HW: 0.0.0.1
      Capabilities: Input
      ModeCombinations: []
    - Mode 0: Name: TEMP, Symbol: DEG, Capability: Input
      - DataSet: 1x Int16, TotalFigures: 5, Decimals: 1
        Input Mapping: SupportFunctionalMapping20 Absolute
        Raw Min:    -900, Max:     900
        Pct Min:    -100, Max:     100 (scaling)
        SI  Min:     -90, Max:      90 (scaling)
  - Port: 0x38 / 56
    - IOTypeId: TechnicMediumHubAccelerometer / 0x0039 / 57
      Revision: SW: 0.0.0.1, HW: 0.0.0.1
      Capabilities: Input
      ModeCombinations: []
    - Mode 0: Name: GRV, Symbol: mG, Capability: Input
      - DataSet: 3x Int16, TotalFigures: 3, Decimals: 0
        Input Mapping: SupportFunctionalMapping20 Absolute
        Raw Min:  -32768, Max:   32768
        Pct Min:    -100, Max:     100 (scaling)
        SI  Min:   -8000, Max:    8000 (scaling)
    - Mode 1: Name: CAL, Symbol: , Capability: Input
      - DataSet: 1x SByte, TotalFigures: 3, Decimals: 0
        Input Mapping: SupportFunctionalMapping20 Absolute
        Raw Min:       1, Max:       1
        Pct Min:    -100, Max:     100 (scaling)
        SI  Min:       1, Max:       1 (pass-through)
  - Port: 0x39 / 57
    - IOTypeId: TechnicMediumHubGyroSensor / 0x003A / 58
      Revision: SW: 0.0.0.1, HW: 0.0.0.1
      Capabilities: Input
      ModeCombinations: []
    - Mode 0: Name: ROT, Symbol: DPS, Capability: Input
      - DataSet: 3x Int16, TotalFigures: 3, Decimals: 0
        Input Mapping: SupportFunctionalMapping20 Absolute
        Raw Min: -28571.42, Max: 28571.42
        Pct Min:    -100, Max:     100 (scaling)
        SI  Min:   -2000, Max:    2000 (scaling)
  - Port: 0x3A / 58
    - IOTypeId: TechnicMediumHubTiltSensor / 0x003B / 59
      Revision: SW: 0.0.0.1, HW: 0.0.0.1
      Capabilities: Input
      ModeCombinations: []
    - Mode 0: Name: POS, Symbol: Deg, Capability: Input
      - DataSet: 3x Int16, TotalFigures: 3, Decimals: 0
        Input Mapping: SupportFunctionalMapping20 Absolute
        Raw Min:    -180, Max:     180
        Pct Min:    -100, Max:     100 (scaling)
        SI  Min:    -180, Max:     180 (pass-through)
  - Port: 0x3B / 59
    - IOTypeId: 93 / 0x005D / 93
      Revision: SW: 0.0.0.1, HW: 0.0.0.1
      Capabilities: Input
      ModeCombinations: []
    - Mode 0: Name: ORINT, Symbol: QUA, Capability: Input
      - DataSet: 4x Int16, TotalFigures: 3, Decimals: 0
        Input Mapping: SupportFunctionalMapping20 Absolute
        Raw Min:   -1000, Max:    1000
        Pct Min:    -100, Max:     100 (scaling)
        SI  Min:      -1, Max:       1 (scaling)
  - Port: 0x3C / 60
    - IOTypeId: Voltage / 0x0014 / 20
      Revision: SW: 0.0.0.1, HW: 0.0.0.1
      Capabilities: Input
      ModeCombinations: []
    - Mode 0: Name: VLT L, Symbol: mV, Capability: Input
      - DataSet: 1x Int16, TotalFigures: 4, Decimals: 0
        Input Mapping: Absolute
        Raw Min:       0, Max:    4200
        Pct Min:       0, Max:     100 (scaling)
        SI  Min:       0, Max:    4200 (pass-through)
    - Mode 1: Name: VLT S, Symbol: mV, Capability: Input
      - DataSet: 1x Int16, TotalFigures: 4, Decimals: 0
        Input Mapping: Absolute
        Raw Min:       0, Max:    4200
        Pct Min:       0, Max:     100 (scaling)
        SI  Min:       0, Max:    4200 (pass-through)
  - Port: 0x3D / 61
    - IOTypeId: 92 / 0x005C / 92
      Revision: SW: 0.0.0.1, HW: 0.0.0.1
      Capabilities: Input
      ModeCombinations: []
    - Mode 0: Name: ChgAct, Symbol: Var, Capability: Input
      - DataSet: 4x Int16, TotalFigures: 4, Decimals: 0
        Input Mapping: Absolute
        Raw Min:       0, Max:       0
        Pct Min:       0, Max:       0 (pass-through)
        SI  Min:       0, Max:       0 (pass-through)
    - Mode 1: Name: PlyAct, Symbol: Var, Capability: Input
      - DataSet: 4x Int16, TotalFigures: 4, Decimals: 0
        Input Mapping: Absolute
        Raw Min:       0, Max:       0
        Pct Min:       0, Max:       0 (pass-through)
        SI  Min:       0, Max:       0 (pass-through)
    - Mode 2: Name: Last, Symbol: Var, Capability: Input
      - DataSet: 3x Int16, TotalFigures: 4, Decimals: 0
        Input Mapping: Absolute
        Raw Min:       0, Max:       0
        Pct Min:       0, Max:       0 (pass-through)
        SI  Min:       0, Max:       0 (pass-through)
    - Mode 3: Name: Total, Symbol: Var, Capability: Input
      - DataSet: 3x Int32, TotalFigures: 4, Decimals: 0
        Input Mapping: Absolute
        Raw Min:       0, Max:       0
        Pct Min:       0, Max:       0 (pass-through)
        SI  Min:       0, Max:       0 (pass-through)
  - Port: 0x3E / 62
    - IOTypeId: 94 / 0x005E / 94
      Revision: SW: 0.0.0.1, HW: 0.0.0.1
      Capabilities: Input
      ModeCombinations: []
    - Mode 0: Name: GEST_BITMAP, Symbol: , Capability: Input
      - DataSet: 1x SByte, TotalFigures: 3, Decimals: 0
        Input Mapping: SupportFunctionalMapping20 Absolute
        Raw Min:       0, Max:     255
        Pct Min:       0, Max:     100 (scaling)
        SI  Min:       0, Max:     255 (pass-through)
  - Port: 0x3F / 63
    - IOTypeId: RgbLight / 0x0017 / 23
      Revision: SW: 0.0.0.1, HW: 0.0.0.1
      Capabilities: Input
      ModeCombinations: []
    - Mode 0: Name: COL 0, Symbol: IDX, Capability: Input
      - DataSet: 1x Int16, TotalFigures: 2, Decimals: 0
        Input Mapping: Discrete
        Raw Min:       0, Max:      25
        Pct Min:       0, Max:     100 (scaling)
        SI  Min:       0, Max:      25 (pass-through)
    - Mode 1: Name: RGB 0, Symbol: RGB, Capability: Input
      - DataSet: 3x SByte, TotalFigures: 2, Decimals: 0
        Input Mapping: Absolute
        Raw Min:       0, Max:     255
        Pct Min:       0, Max:     100 (scaling)
        SI  Min:       0, Max:     255 (pass-through)

Also Control+ communication bt dump:
controlpluscommunication.zip

And full ble advertising packet:

Any ideas why older hub can't connect to this one through LWP3Device?

[DanieleBenedettelli]

from pybricks.hubs import TechnicHub
from pybricks.parameters import Color
from pybricks.tools import wait
from pybricks.iodevices import LWP3Device

hub = TechnicHub()
hub.light.blink(Color.YELLOW, [250, 250])
wait(50)
#print("Searching for the car. Make sure it is on and blinking its HUB light.")
porsche = LWP3Device(0x84, name=None, timeout=15000)
wait(50)
#print("Connected!")
hub.light.on(Color.GREEN)
wait(50)
while True:
    #controlling code goes here
    #print("All good!")
    wait(500)

I can't get my Technic Hub to connect to the Technic Move Hub, it always times out.

[toorisrael]

PBDRV_BLUETOOTH_PERIPHERAL_OPTIONS_PAIR | PBDRV_BLUETOOTH_PERIPHERAL_OPTIONS_DISCONNECT_HOST

After mentioned firmware update changing LED color works, but program terminates/hub disconnects just a second later.

[DanieleBenedettelli]

I updated the Prime Hub with the new firmware, it connects but as soon as I try changing the LED light, the Technic Move Hub disconnects and this error is returned:
line 15, in
RuntimeError: Unknown error

while sending LWP3 Direct Commands using the nRF Connect App on Android works!

[DanieleBenedettelli]

@laurensvalk

Maybe the new Race Hub requires pairing, just like the XboxController. To test this, you could try replacing PBDRV_BLUETOOTH_PERIPHERAL_OPTIONS_NONE with PBDRV_BLUETOOTH_PERIPHERAL_OPTIONS_PAIR on line 215 in pybricks/iodevices/pb_type_iodevices_lwp3device.c.

In fact, you can save yourself some trouble and achieve automatic disconnecting just like the XboxController by setting it to:

PBDRV_BLUETOOTH_PERIPHERAL_OPTIONS_PAIR | PBDRV_BLUETOOTH_PERIPHERAL_OPTIONS_DISCONNECT_HOST

We could make that automatic based on the detected hub ID during scanning.

Above was confirmed by @NStrijbosch !

Taking a step back though, it might be a easier to skip the intermediate Pybricks hub for now and connect directly to the new Race Hub from your computer with a Python script using something like Bleak for easier debugging.

Should we modify the firmware from source and rebuild, or did you already add this mods into latest fw?

[dlech]

FYI, I've made a PR that adds a pair argument to LWP3Device if anyone wants to try it out.

porsche = LWP3Device(0x84, pair=True)

Firmware is available at: pybricks/pybricks-micropython#259 (comment)

Seems to be working OK on SPIKE Prime. I haven't tried it on a Technic Hub. (And pairing isn't possible with City or Move hub)

[DanieleBenedettelli]

Out of curiosity I tried using the poweredup device list with the new hub, but I got this error:

Selected 132 with key 1 Discover Ports. Receiving Messages ... System.Exception: Per leggere o scrivere l'attributo, è necessaria l'autenticazione. (0x80650005) at SharpBrick.PoweredUp.WinRT.WinRTPoweredUpBluetoothCharacteristic.NotifyValueChangeAsync(Func2 notificationHandler) in /home/runner/work/powered-up/powered-up/src/SharpBrick.PoweredUp.WinRT/WinRTPoweredUpBluetoothCharacteristic.cs:line 38
at SharpBrick.PoweredUp.Bluetooth.BluetoothKernel.ReceiveBytesAsync(Func2 handler) in /home/runner/work/powered-up/powered-up/src/SharpBrick.PoweredUp/Bluetooth/BluetoothKernel.cs:line 75 at SharpBrick.PoweredUp.Protocol.LegoWirelessProtocol.ConnectAsync(SystemType knownSystemType) in /home/runner/work/powered-up/powered-up/src/SharpBrick.PoweredUp/Protocol/LegoWirelessProtocol.cs:line 49 at SharpBrick.PoweredUp.Cli.DevicesList.ExecuteAsync(SystemType knownSystemType) in /home/runner/work/powered-up/powered-up/src/SharpBrick.PoweredUp.Cli/Commands/DevicesList.cs:line 29 at SharpBrick.PoweredUp.Cli.Program.<>c__DisplayClass4_2.<<Main>b__6>d.MoveNext() in /home/runner/work/powered-up/powered-up/src/SharpBrick.PoweredUp.Cli/Program.cs:line 78

The error in english is something like "To read or write the attribute, authentication is required."
Why? I am on Win 11.

By using the nRF app I could change the LED color by sending
08 00 81 3F 17 51 00

but I can't get it to bootloeader mode with the command:
0B:00:10:4C:50:46:32:2D:42:6F:6F:74

0x0B 0x00 0x10 0x4C 0x50 0x46 0x32 0x2D 0x42 0x6F 0x6F 0x74
11 0x00 FWUP L P F 2 - B o o t
maybe the safety string changed...

[dlech]

"authentication is required." Why?

Only LEGO can answer this. 😄 Maybe they wanted to make it "more secure"?

but I can't get it to bootloeader mode with the command:

This hub doesn't have the same bootloader as the supported Pybricks hubs. It uses Texas Instruments Over the Air Download (OAD) for firmware updates (same as LEGO Mario and friends). This is what the extra F000XXXX-0451-4000-B000-000000000000 service is on the hub.

[DanieleBenedettelli]

Ah, here's what that's for!
@toorisrael I can't find the hub using windows Bluetooth device search.
I can't see the hub on Wireshark once it's connected to the nRF app to send some test commands. It just disappears from the stream once it's connected to the phone . Any hint?

[toorisrael]

It can be paired with only one device at a time

[DanieleBenedettelli]

I could not find any way, nor manual nor programmatical, to scan and then pair the Technic Move Hub to my Windows 11 laptop.
Using the nRF Connect Desktop application, I could pair and successfully send a command to the hub.
The pairing process produces this log
2024-08-03T10:22:08.872Z INFO Storing bond info for device 7C:E2:69:CD:45:0D 2024-08-03T10:22:08.872Z DEBUG Bond info: {"7C:E2:69:CD:45:0D":{"keys_own":{"enc_key":{"enc_info":{"ltk":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"auth":false,"ltk_len":0,"lesc":false},"master_id":{"ediv":0,"rand":[0,0,0,0,0,0,0,0]}},"id_key":{"id_info":{"irk":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0]},"id_addr_info":{"address":"00:00:00:00:00:00","type":"BLE_GAP_ADDR_TYPE_PUBLIC","addr_id_peer":0}},"sign_key":{"csrk":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0]},"pk":{"pk":[15,203,0,153,187,143,105,255,119,140,128,235,191,37,116,155,202,184,207,122,76,251,51,135,236,172,46,17,252,5,213,68,184,249,106,124,102,87,31,206,178,56,78,117,63,91,194,163,243,163,172,195,63,73,187,1,233,15,62,221,252,130,0,77]}},"keys_peer":{"enc_key":{"enc_info":{"ltk":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"auth":false,"ltk_len":0,"lesc":false},"master_id":{"ediv":0,"rand":[0,0,0,0,0,0,0,0]}},"id_key":{"id_info":{"irk":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0]},"id_addr_info":{"address":"00:00:00:00:00:00","type":"BLE_GAP_ADDR_TYPE_PUBLIC","addr_id_peer":0}},"sign_key":{"csrk":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0]},"pk":{"pk":[74,131,165,161,175,5,208,141,92,81,251,164,217,141,27,226,56,64,95,253,215,96,107,204,105,122,124,152,206,160,130,55,122,58,158,7,110,103,217,13,117,218,101,12,192,231,12,238,157,215,93,94,227,184,44,176,122,129,245,78,206,101,127,21]}}}}

Which development tools could I use on Windows to connect and communicate with the hub?

[toorisrael]

I've done it like this to get device list:





To interact with the device probably mentioned bleak python's module will be the best, or any other BLE terminal tool. But actually I've not tried that yet, as I'm at the beginning of my adventure with BLE :) I've tried that before only to read broadcasted data from older Technic Hubs running Pybricks FW.

[DanieleBenedettelli]

Thanks. I know how to add devices on Windows.
The point is that my windows Bluetooth settings do NOT show the Technic Move hub at all.
I wonder why. Do you have any 3rd party driver installed? Which dongle are you using?

[toorisrael]

This is just integrated PC motherboard's Bluetooth adapter, no additional drivers installed

[DanieleBenedettelli]

But I bet you are on Windows 10.
I tried with Windows 10, it listed the device, although it could not connect.
On Windows 11, BLE is not supported adequately.

[toorisrael]

That's correct, both my PC and laptop run Win 10.

[toorisrael]

Here's an example python's bleak script to connect and interact with Technic Move hub (Chat GPT helped a lot). Tested under Windows 10,
only for changing status LED color: bleak-terminal

python bleak-terminal.py
Found devices:
0: Technic Move   (34:68:B5:1C:BD:3E)
Select device index to connect: 0
Connected to 34:68:B5:1C:BD:3E
Available characteristics:
0: 00002a00-0000-1000-8000-00805f9b34fb (Properties: read, write)
1: 00002a01-0000-1000-8000-00805f9b34fb (Properties: read, write)
2: 00002a04-0000-1000-8000-00805f9b34fb (Properties: read)
3: 00002aa6-0000-1000-8000-00805f9b34fb (Properties: read)
4: 00002ac9-0000-1000-8000-00805f9b34fb (Properties: read)
5: 00002a05-0000-1000-8000-00805f9b34fb (Properties: indicate)
6: 00001624-1212-efde-1623-785feabcd123 (Properties: write-without-response, write, notify)
7: f000ffc1-0451-4000-b000-000000000000 (Properties: write-without-response, write, notify)
8: f000ffc2-0451-4000-b000-000000000000 (Properties: write-without-response, write, notify)
9: f000ffc5-0451-4000-b000-000000000000 (Properties: write-without-response, notify)
Enter command (read/write/exit): write
Enter characteristic index to write: 6
Enter data to write (in hex): 0800813F11510002
Data written
Enter command (read/write/exit): exit
Disconnected

[DanieleBenedettelli]

You were faster than me! I was working on the same thing. I propose we join forces to create a complete communication library, using this sources to speed up things https://github.com/pybricks/pybricksdev/tree/master/pybricksdev/ble/lwp3

Important: since I can't manually pair my hub on windows 11, and that could happen to others, I suggest you add
await client.pair(2) after connection in order to write to characteristics later.

Let me know how we can collaborate.

[toorisrael]

Thanks for the tip, just tried without Windows pairing, and it works indeed after pairing in python.

Thanks for the source. I've used brickcontroller2 source code and LWP3 docs for now.

You can of course create pull request or contact me by Steam or root89 on Discord (I've no idea how adding on Discord works and if the name is enough) if you want to discuss something. Also creating issue on LEGO-Porsche-Controller github would be fine for me.

[DanieleBenedettelli]

I tested another command, the
https://lego.github.io/lego-ble-wireless-protocol-docs/index.html#output-sub-command-startspeedfordegrees-degrees-speed-maxpower-endstate-useprofile-0x0b
0D 00 81 32 11 0B 68 01 00 00 32 64 7F 00

that works on LEGO BOOST Move Hub (changing port from 32 to 00, makes motor A rotated by 360 degrees), but not on the new hub,
which returns 05:00:05:81:05, which is an error meaning Command NOT recognized.
Any idea of what I am missing?

[toorisrael]

I'm not sure what's going on with those gopos commands. 0e008134110d2800000032647e00 should rotate the motor 40 deg at 50% speed, insteed it crashes the hub.
It's taken from here and recreated like this.
This is part of the dump from the new hub:

  - Port: 0x34 / 52
    - IOTypeId: 87 / 0x0057 / 87
      Revision: SW: 0.0.0.2, HW: 0.0.0.1
      Capabilities: Output Input
      ModeCombinations: []
    - Mode 0: Name: POWER, Symbol: PCT, Capability: Input Output
      - DataSet: 1x SByte, TotalFigures: 4, Decimals: 0
        Input Mapping: Absolute
        Output Mapping: Absolute
        Raw Min:    -100, Max:     100
        Pct Min:    -100, Max:     100 (pass-through)
        SI  Min:    -100, Max:     100 (pass-through)
    - Mode 1: Name: SPEED, Symbol: PCT, Capability: Output
      - DataSet: 1x SByte, TotalFigures: 4, Decimals: 0
        Output Mapping: Absolute
        Raw Min:    -100, Max:     100
        Pct Min:    -100, Max:     100 (pass-through)
        SI  Min:    -100, Max:     100 (pass-through)
    - Mode 2: Name: POS, Symbol: DEG, Capability: Input Output
      - DataSet: 1x Int32, TotalFigures: 4, Decimals: 0
        Input Mapping: Relative
        Output Mapping: Relative
        Raw Min:    -360, Max:     360
        Pct Min:    -100, Max:     100 (scaling)
        SI  Min:    -360, Max:     360 (pass-through)
    - Mode 3: Name: GOPOS, Symbol: DEG, Capability: Input Output
      - DataSet: 1x Int16, TotalFigures: 4, Decimals: 0
        Input Mapping: Relative
        Output Mapping: Relative
        Raw Min:    -180, Max:     179
        Pct Min:    -100, Max:     100 (scaling)
        SI  Min:    -180, Max:     179 (pass-through)
    - Mode 4: Name: STATS, Symbol: DEG, Capability: Output
      - DataSet: 3x Int32, TotalFigures: 10, Decimals: 0
        Output Mapping: Absolute
        Raw Min:       0, Max: 4.2949673E+09
        Pct Min:       0, Max:       0 (scaling)
        SI  Min:       0, Max: 4.2949673E+09 (pass-through)

and from the old one for comparison:

  - Port: 0x00 / 0
    - IOTypeId: TechnicLargeLinearMotor / 0x002E / 46
      Revision: SW: 0.0.0.1000, HW: 0.0.0.1000
      Capabilities: Output Input LogicalCombinable LogicalSynchronizable
      ModeCombinations: [0000000000001110]
    - Mode 0: Name: POWER, Symbol: PCT, Capability: Output
      - DataSet: 1x SByte, TotalFigures: 1, Decimals: 0
        Output Mapping: Absolute
        Raw Min:    -100, Max:     100
        Pct Min:    -100, Max:     100 (pass-through)
        SI  Min:    -100, Max:     100 (pass-through)
    - Mode 1: Name: SPEED, Symbol: PCT, Capability: Input Output
      - DataSet: 1x SByte, TotalFigures: 4, Decimals: 0
        Input Mapping: Absolute
        Output Mapping: Absolute
        Raw Min:    -100, Max:     100
        Pct Min:    -100, Max:     100 (pass-through)
        SI  Min:    -100, Max:     100 (pass-through)
    - Mode 2: Name: POS, Symbol: DEG, Capability: Input Output
      - DataSet: 1x Int32, TotalFigures: 4, Decimals: 0
        Input Mapping: Relative
        Output Mapping: Relative
        Raw Min:    -360, Max:     360
        Pct Min:    -100, Max:     100 (scaling)
        SI  Min:    -360, Max:     360 (pass-through)
    - Mode 3: Name: APOS, Symbol: DEG, Capability: Input Output
      - DataSet: 1x Int16, TotalFigures: 3, Decimals: 0
        Input Mapping: Relative
        Output Mapping: Relative
        Raw Min:    -180, Max:     179
        Pct Min:    -200, Max:     200 (scaling)
        SI  Min:    -180, Max:     179 (pass-through)
    - Mode 4: Name: LOAD, Symbol: PCT, Capability: Input Output
      - DataSet: 1x SByte, TotalFigures: 1, Decimals: 0
        Input Mapping: Relative
        Output Mapping: Relative
        Raw Min:       0, Max:     127
        Pct Min:       0, Max:     100 (scaling)
        SI  Min:       0, Max:     127 (pass-through)

Looks like there are some changes in Mode 3 GOPOS/APOS. Maybe someone figures this out.

[toorisrael]

My understanding of LWP3 commands few days ago was almost none, now I understand it much better, but command for turning steer motor 45 deg:

0e008103110d2d00000064647e00

works fine with Large motor on Technic Hub (port 0x03), but

0e008134110d2d00000064647e00

which seems fine for me is still crashing Technic Move Hub (port 0x34 here). Maybe it requires some initialization or uses another method to convert degrees to bytes? Arguments count seems correct.

[DanieleBenedettelli]

I am publishing a video of my successful reverse engineering process and the protocol soon on my GitHub account. In short, we can't use the LWP3 yet. Il mar 6 ago 2024, 12:36 toor ***@***.***> ha scritto:

…

My understanding of LWP3 commands few days ago was almost none, now I understand it much better, but command for turning steer motor 45 deg: 0e008103110d2d00000064647e00 works fine with Large motor on Technic Hub (port 0x03), but 0e008134110d2d00000064647e00 which seems fine for me is still crashing Technic Move Hub (port 0x34 here). Maybe it requires some initialization or uses another method to convert degrees to bytes? Arguments count seems correct. — Reply to this email directly, view it on GitHub <#1733 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALJJ3TKJPVUTFDINUAI3R4TZQCRLFAVCNFSM6AAAAABLUREGGSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMRVGIZTQNQ> . You are receiving this because you commented.Message ID: ***@***.***>

[toorisrael]

Ah, good to know. Steering could be still implemented using power mode and getting motor angle, although there will be much more work to do.

[toorisrael]

I've added some basic steering support to my python script. As it's using power mode it will be dependent on battery level. Tested with 35-45%, maybe I will fix and clean it if nobody finds better way soon. It's quite fun to play anyway.

P.S. I hope it will be possible to easily order new tires 😃

[DanieleBenedettelli]

Here's the protocol used by the CONTROL+ app, and the working script to control the car using the XBOX controller
https://github.com/DanieleBenedettelli/TechnicMoveHub
The video that tells the story of this reverse engineering is out tomorrow at 3PM (CEST)
https://youtu.be/2zeW6gNV7Jo

[toorisrael]

Commands seems to still work fine even if PLAYVM is used to calibrate steering. Here are some useful commands:

#subscribe to steering motor angle changes - this will overwrite any other reading, as it updates for any change (to unsubscribe set last byte to 0x00)
command = bytes([0x0A, 0x00, 0x41, steeringmotor, 0x02, 0x00, 0x00, 0x00, 0x00, 0x01])

#reset encoder at current angle to 0 degrees
command = bytes([0x0b, 0x00, 0x81, steeringmotor, 0x11, 0x51, 0x02, 0x00, 0x00, 0x00, 0x00])

#controll brightness of all 6LEDS - last byte is brightness 0-100%, the byte before is LED mask
"09008135115100ff00"

For me the only thing that was not working was gopos, I wonder if it could be because PLAYVM takes control of this one.

[toorisrael]

So after more testing, setting drive motors power directly gives instant response, drifts on some surfaces and all those things I love in this car. It does not bug with PLAYVM if its power is set all the time to 0 (it ignores the drive motors completely this way). I've also added 'power x' command and '-power x' command line parameter to limit power between 25% and 100% (for kids).

You may also want to update your PLAYVM led bytes with one extra:

LIGHTS_ON_ON = 0
LIGHTS_ON_BRAKING = 1
LIGHTS_OFF_OFF = 4
LIGHTS_OFF_BRAKING = 5

[DanieleBenedettelli]

What if to control the motors by degrees we try using
0B 00 81 32 11 51 03 (4 angle bytes) ?
Instead of the 0D command?

[toorisrael]

I'm not sure how to correctly implement it, but maybe you figure something out, as partially it works for me:

0b00813211510200000000 - direct write pos reset encoder (this works)
0b00813211510378000000 - direct write gopos 120 deg? (doesn't work)
07008132115103 - direct write gopos unspecified angle? (this works)

Enter data to write, use controller or type 'help':
angletobytes 120
Angle 120 bytes representation: 78000000
Enter data to write, use controller or type 'help':
0b00813211510200000000
0b00813211510200000000 written
Data written
Read data: 050082320a [Port Output Command Feedback] Port 50 OK
Enter data to write, use controller or type 'help':
0b00813211510378000000
0b00813211510378000000 written
Data written
Read data: 0500058105 [Error] Port Output Command->Command NOT recognized
Enter data to write, use controller or type 'help':
07008132115103
07008132115103 written
Data written
Read data: 050082320a [Port Output Command Feedback] Port 50 OK

Edit: With direct write to motor port in mode 3 there should be 2 bytes representing angle, for example:
09008132115103ff00 will work, but using this for a second time or using any other input will crash the hub. I'm still missing some understanding here.

[DanieleBenedettelli]

I think we're not issuing wrong commands, it's just the firmware to have bugs.
Their priority was making the PLAYVM functionality work, and the rest is still incomplete.

[legomania76]

Could you please explain to me how I can update the brickcontroller2 app on my Android phone? I'd love to be able to control my Porsche GT4 e-Performance with my PS5 controller. But for the life of me I don't know how to update the code to make it work..

[BertLindeman]

Hi,

As you state

But for the life of me I don't know how to update the code to make it work..

then probably the best way to get BrickController2 supporting the LEGO Porsche GT4 is posting an issue at the source of the BrickController2 and ask the maintainer to add this device.

Bert

[legomania76]

Hi Bert,

Thanks, I just posted an issue.
Really wish I could've found a way to use Android Studio to update the code and build a functioning .apk file to install on my phone. Even with help of ChatGPT I couldn't do it.

Can't win them all I guess, hopefully the app will be updated.

André

[basco]

Is it possible to control the porche with a 88010 powered up remote control?

[DanieleBenedettelli]

Yes, https://github.com/DanieleBenedettelli/TechnicMoveHub Il ven 6 dic 2024, 20:01 Basco ***@***.***> ha scritto:

…

Is it possible to control the porche with a 88010 powered up remote control? — Reply to this email directly, view it on GitHub <#1733 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALJJ3TOCQY4T5V2EEVQLFUL2EHYALAVCNFSM6AAAAABLUREGGSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNBYHAZDCOI> . You are receiving this because you commented.Message ID: ***@***.***>

[DanieleBenedettelli]

Yes! https://github.com/DanieleBenedettelli/TechnicMoveHub/blob/main/LEGO%20Technic%2042176%20RC%20Handset%2088010.py Il ven 6 dic 2024, 20:01 Basco ***@***.***> ha scritto:

…

Is it possible to control the porche with a 88010 powered up remote control? — Reply to this email directly, view it on GitHub <#1733 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALJJ3TOCQY4T5V2EEVQLFUL2EHYALAVCNFSM6AAAAABLUREGGSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNBYHAZDCOI> . You are receiving this because you commented.Message ID: ***@***.***>

[basco]

Nice! But how do i flash new firmeware to the hub with the pybricks tool?

[kocouj1]

Hi, it's nice that you created this demo code. Problem is that it doesn't work with my GT4 Lego and I don't know why. It connects to it (based on debug messages and also LED on Lego), joystick works (I can see debug messages) but that's all. No movement of wheels. Does it still work for you?

[DanieleBenedettelli]

There's no Pybricks firmware for that hub yet. I send messages to the hub with its factory firmware. Please read the documentation in my repository. Il sab 7 dic 2024, 16:27 Basco ***@***.***> ha scritto:

…

Nice! But how do i flash new firmeware to the hub with the pybricks tool? — Reply to this email directly, view it on GitHub <#1733 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALJJ3TNHS3OV4SUYZHKN3332EMHURAVCNFSM6AAAAABLUREGGSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNBZGQ3DGMQ> . You are receiving this because you commented.Message ID: ***@***.***>

[basco]

ah, i'm new to all this.... so i already succeeded in making the audi etron work with the 88010 remote with pybricks, that was easy. So what do i have to do make the porche work woth the remote is progam the remote? so that it can talk to the standard firmware in the Porches hub? thanks!!

[basco]

ps. i read the readme but it's does not include steps to make it actually work.... i think...

[basco]

where does the python code go? how to make the 88010 send the right commands? do i need to download the py code to the remote? i'm missing something essential........ any help is welcome!

[DanieleBenedettelli]

The python script runs on your computer, and acts as a bridge between the remote and the Porsche hub. Il dom 8 dic 2024, 10:35 Basco ***@***.***> ha scritto:

…

where does the python code go? how to make the 88010 send the right commands? do i need to download the py code to the remote? i'm missing something essential........ any help is welcome! — Reply to this email directly, view it on GitHub <#1733 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALJJ3TJD3HTP2SWLTMBF73T2EQHG7AVCNFSM6AAAAABLUREGGSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNBZHA2DSMI> . You are receiving this because you commented.Message ID: ***@***.***>

[basco]

Ah, oke, well i could make it work like this, but it will be a bit difficult for my son to use the laptop as an intermediate device...

[basco]

Is it expected that there will be firmware for pybricks for the Porche? The Lego app is not the most intuitive to use...

[basco]

how hard would it be to develop a custom pcb for signed hubs?

[ConchasCode]

This seems to be really bad news for future community inittiatives like yours! :(
Better if TLG choose not to turn it on, but as ususal they're very good at shooting on their own feet...

[Gehirnacrobat]

Has anyone bothered to contact Lego yet?
Or do we just assume that they won't hand over the license key?

[wattenre]

I tried via multiple ways (I also have written directly to one of the developers), but I didn't got a (positive) response (at all).

After multiple E-Mails, the support confirmed me, that they will hand over the suggestions I made to their management, but I don't know if something will happen at all.

Has anyone else been able to find out anything new in the meantime?

I bought one additional Technic Hub on bricklink and I'm controlling it now via the Asus ROG Ally X (Windows Gaming Handheld) by running a python script and using the internal XBOX controller. This works fine, but it is only enabling me to use the functions the GT4 e-Performance is currently running with. It's not a replacement at all for the coding possibilities we normally have with Pybricks.

[basco]

i hope lego will open up their hub. if not, i'm seriously thinking of designing a custom pcb, and while i'm at it, for all hubs as well.

[Aizatulin]

Hi,
Why doesn't MoveHab support the LWP3Device class? Is it still unfinished in Pybricks? Or is it a common reason like the new hub?

[Aizatulin]

I see, thanks.
But the BOOST Move hub is drawn in the description of the LWP3Device class and this is confusing. )

[dlech]

The BOOST Move hub, running official LEGO firmware, can be remotely controlled using the LWP3Device. So that picture is incomplete, but the intention is to show all hubs that can be remotely controlled. Also missing from that picture are the Mario/Luigi/Peach "hubs" and the new Technic Move hub.

[Aizatulin]

That's how. And I have a problem, I can't connect TechnicHub with BOOST. I tried many times, on three hubs. No way. That's why I asked about the class. But if it can be controlled, what could be the reason that there is no connection?

[dlech]

If you want to start a new discussion and share the code you tried that isn't working, we can have a look.

[Aizatulin]

Ok, I've opened a new discussion.

[sascha024]

Guten Tag

Ist es möglich motor a und motor b unabhängig voneinander zu steuern

Mit freundlichen Grüßen

[pavel-svoboda]

Guten Tag

Ist es möglich motor a und motor b unabhängig voneinander zu steuern

Mit freundlichen Grüßen

Ja, es geht.

Yes, you can drive all 3 motors independently. The code of Prof. Bricks works eventually, however, you must tweak the code. The motors have extra codes in his scripts, so you may address them individually.

[DanieleBenedettelli]

You can control the motor power (or speed, I don't remember), while trying to control the angle will crash the hub. Il lun 21 lug 2025, 10:02 pavel-svoboda ***@***.***> ha scritto:

…

Guten Tag Ist es möglich motor a und motor b unabhängig voneinander zu steuern Mit freundlichen Grüßen Ja, es geht. Yes, you can drive all 3 motors independently. The code of Prof. Bricks works eventually, however, you must tweak the code. The motors have extra codes in his scripts, so you may address them individually. — Reply to this email directly, view it on GitHub <#1733 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALJJ3TNLRKBTMK2WZU7QM3D3JSNCJAVCNFSM6AAAAABLUREGGSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGOBTGEYTMOA> . You are receiving this because you commented.Message ID: ***@***.***>