technic hub support plans for adding support for motor c or d and ab and cd with the technic hub?

[twin1nap]

any plans to add support for the technic hub or any tips for me to add it myself, like where to start?

[undera]

Theoretically, any PoweredUp hub can be used with this library, use Hub class: https://github.com/undera/pylgbst/blob/master/pylgbst/hub.py#L49

You can also subclass it to create a class that handles specifics of some hub type, like done in: https://github.com/undera/pylgbst/blob/master/pylgbst/hub.py#L338

[twin1nap]

Im still a bit of a beginner in Python, so I dont understand the code fully, so how would I then control a hub using the hub class or make the subclass?

[twin1nap]

After reading the smarthub subclass a few times, I came to the conclusion I can just copy and paste it mostly and modify it for my own needs, but how would I get the port numbers for all the ports and for the combined ports like port_AB?

[undera]

The process of discovering port information is quite easy. You just create a piece of code that connects to your Hub, and you see the port and peripheral numbers printed to the console.

[twin1nap]

I can't get my hub to connect to my laptop for some reason when using the hub class to connect to it. I don't know if I am doing something wrong or something else is the problem, but I can't get it to connect; the code just stops when I run it, no errors. Here is my code:

from pylgbst import get_connection_bleak
from pylgbst.hub import Hub

hub_mac = "90:84:2B:4A:12:8D"
conn = get_connection_bleak(hub_mac=hub_mac)
hub = Hub(conn)

When using, for example, the Move Hub class, I can get it to connect, but then it won't show all the connected devices.

[undera]

Add yo your code the logging configuration:

import logging 
logging.basicConfig(level=logging.INFO)

[twin1nap]

Still just stops after starting it like before for some reason.

[twin1nap]

I connected the hub using the movehub class and put the logging in a while loop, and now it works. I just have to find a way to get the combined ports for controlling port A and B at the same time.

[undera]

For reference, use this doc: https://lego.github.io/lego-ble-wireless-protocol-docs/
Search in page for "CombinedMode" to find all mentions of that.

In particular, you'll need to send to Hub a message of type MsgPortInputFmtSetupCombined: https://github.com/undera/pylgbst/blob/master/pylgbst/messages.py#L483

Beware that I never tried to use combined mode myself, so you might find that some modifications to library classes are needed.

Also switching logging to DEBUG level might help if you go deeper into message exchanges.

[undera]

Actually, the message above might be wrong and you might need to do what is called "Virtual Port": https://lego.github.io/lego-ble-wireless-protocol-docs/#virtual-port-setup

Also see corresponding message type: https://github.com/undera/pylgbst/blob/master/pylgbst/messages.py#L714

[twin1nap]

Before you responded, I already had a virtual port to work using a past conversation you had that I found here, but I couldn't get it to work when I put it in the subclass I created so that I later could just use port_AB, which then would be the virtual port for ports A and B. Do you know how I could make that work?

[undera]

You can create an override __init__ constructor in hub subclass, and call the virtual port right after parent __init__. You need to make sure that at the time of creating virtual port, the both motors are already recognized.

[twin1nap]

is there a way to detect if the motors are recognized so i can make it that when they are not both recognized it wont make an virtual port making the subclass also work when it doesnt need to create a virtual port

[undera]

Since the type of your Hub uses only externally attached motors, you'd have to create a waiting loop that would check that motors are there, and once this condition is met -- perform the virtual port creation. A similar waiting is done in MoveHub here https://github.com/undera/pylgbst/blob/master/pylgbst/hub.py#L269, though it waits the pre-defined onboard devices.