From the github repo for uhubctl:
"While uhubctl compiles on Windows, USB power switching does not work on Windows because libusb is using winusb.sys driver,
which according to Microsoft does not support necessary USB control requests. This may be fixed if libusb starts supporting different driver on Windows"

likely this would mean that Win OS users will not get the benefit of USB on/off control. I don't see any rules
in the indi lib developer manual that precludes adding this for linux and mac platforms. Can someone with more
authority comment ?

Awaiting my PPBA anytime soon (?). Thanks for all the effort.

I wonder if Pegasus will add USB on/off control in a future firmware upgrade as I am certain people would appreciate. That could affect their UPBV2 sales a bit though. At least there is an alternate solution for Linux users.

I’ve got mine showing up in the next few days.

I’ve currently got v1.5.1 of StellarMate OS and it’s been really solid. Are any features it supports on this slightly older build?

Does the latest version of StellarMate OS support it yet?

You can switch to beta channel and get it, or wait until stable is released. I plan to have everything released before July 15th.

I see that Pegasus PPBA (indi_pegasus_ppba) v1.0 has been released in indi-full/focal 1.8.6~202007201351~ubuntu20.04.1

Unfortunately, I get a serial time-out error when trying to connect at 9600 baud with both of the available serial ports.

usbdevices on ubuntu sees this:

T: Bus=01 Lev=02 Prnt=09 Port=00 Cnt=01 Dev#= 10 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0403 ProdID=6015 Rev=10.00
S: Manufacturer=Pegasus Astro
S: Product=PPBADV revA
S: SerialNumber=PPBA4PSI91
C: #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=90mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=ftdi_sio

Also:

lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
|__ Port 4: Dev 6, If 0, Class=Hub, Driver=hub/4p, 5000M
|__ Port 1: Dev 7, If 0, Class=Vendor Specific Class, Driver=, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=pl2303, 12M
|__ Port 4: Dev 9, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 3: Dev 11, If 0, Class=Vendor Specific Class, Driver=, 480M
|__ Port 1: Dev 10, If 0, Class=Vendor Specific Class, Driver=ftdi_sio, 12M

The two attached ZWO cameras connect with no problems, but the driver attempts to connect to /dev/ttyUSB0 and immediately gets a Serial read error: Timeout error, and then trys /dev/ttyUSB1 and hangs. I don't seem to be able to input any other device paths, and the scan ports doesn't produce any alternatives.

Suggestions?

A followup to my post - upon connecting my Mac to a remote INDI session to the Ubuntu host (which is connected to the PPBA), the Mac instance of INDI connects the (remote) PPBA just fine. I did a ~4 hour session last night, with auto-dew heaters enabled, and everything seems to work as expect.

One item I don't recall seeing is the ability to control each of the 4 individual 12V ports, but will look again when I get back to my scope.

My Pocket Powerbox Advance is finally running almost flawless (USB-connection issues) on 3.4.3
One day i will understand this USB port connection error thing that sometimes happens for sure...

Now my question is as follows.

Can someone who also ownes one of this PPBA explain to me, how the "auto-dew" feature is controllable?
My proplem is that in the autodew mode, the heater gets too warm and causes blown up stars as you can see in the picture.
Upper side with heater at 10% manually
Lower side with Auto dew running at about 70% as calculated.
Is there a way of extra controll over this?

greetings
Niki