sharpbrick / docs Goto Github PK

The TechnicLargeAngularMotorGrey has a non-understood STATS mode. Investigate it and extend model.

Discovered as part of sharpbrick/powered-up#75 and sharpbrick/powered-up#108

Is suggested by the behavior of the LED Light, the specification and the node-pweredup lib.

Lesson learnt from sharpbrick/powered-up#51

Since property support dramatically vary among hub types, add overview.

Raised by this issue on legion and the comment of @bricklife

I'd love to add documentation about the mindstorms hub here. If only it would use LWP that would help..

The LWP gatt service is not reported by the device. Compare this output from bluetoothctl in linux from the Technic Hub vs the mindstorms hub:

[bluetooth]# info 90:84:2B:5A:60:33
Device 90:84:2B:5A:60:33 (public)
        Name: Technic Hub
        Alias: Technic Hub
        Appearance: 0x1800
        Paired: no
        Trusted: no
        Blocked: no
        Connected: no
        LegacyPairing: no
        UUID: Vendor specific           (00001623-1212-efde-1623-785feabcd123)
        UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
        UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
        ManufacturerData Key: 0x0397
        ManufacturerData Value:
  00 80 06 00 41 00                                ....A.          
        RSSI: -51
        TxPower: 0

info 38:0B:3C:AE:0B:4F
Device 38:0B:3C:AE:0B:4F (public)
        Name: LEGO Hub 38:0B:3C:AE:0B:4F
        Alias: LEGO Hub 38:0B:3C:AE:0B:4F
        Class: 0x00000804
        Paired: yes
        Trusted: no
        Blocked: no
        Connected: no
        LegacyPairing: no
        UUID: Vendor specific           (00000000-deca-fade-deca-deafdecacaff)
        UUID: Serial Port               (00001101-0000-1000-8000-00805f9b34fb)
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        Modalias: bluetooth:v0397p0002d0001
        RSSI: -40
        TxPower: 0

The mindstorms hub apparently uses a BT serial port (and does not use BLE for that matter?). I have been looking around to see if someone started on reverse engineering the serial protocol for this, haven't found anything useful really.

Current Behavior
hub.VccPortControlOnAsync() or hub.VccPortControlOffAsync seems to trigger a detach on all ports with an attached device and then a registration of a LedLight (which as a device is currently not implemented).

Question

• Why is that?
• What is that for?
• Maybe VccPortControlOnAsync means to switch of the wire communication protocol and instead just supply energy? Useful for more dumb devices? However, maybe this command is used to preserve energy on the hub, but why is then a LedLight showing up.

Figure out how calibration works.