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 ?
Read More...
if you run kstars-bleeding on your OS and try the driver out, please do report any bugs with voluminous detail: either log files
or your observations. That way, we can all make it better 
Read More...
I am wondering if the pegasus power box advance (PPBA ) driver can incorporate USB hub per-port power control.
From the readme on the git repo
github.com/mvp/uhubctl
, it looks like Windows users may be out of luck.
If so, would that preclude developing the driver further so that hub control is available for linux users ? I received
this info from Evans as Pegasus Astro:
the USB Hub supports ON/OFF for each port in software.
You can check more about that here:
github.com/mvp/uhubctl
Example
$ uhubctl
Current status for hub 20-14, vendor 2109:2813, 4 ports
Port 1: 0103 power enable connect [0403:6015 Pegasus Astro PPBA revA PPBA4ZNGNY]
Port 2: 0100 power
Port 3: 0100 power
Port 4: 0100 power
E.g I want to turn off port 2:
ubctl -p2 -a 0
Current status for hub 20-14, vendor 2109:2813, 4 ports
Port 2: 0000 off
Sent power off request
New status for hub 20-14, vendor 2109:2813, 4 ports
Port 2: 0000 off
Verification
$ uhubctl
Current status for hub 20-14, vendor 2109:2813, 4 ports
Port 1: 0103 power enable connect [0403:6015 Pegasus Astro PPBA revA PPBA4ZNGNY]
Port 2: 0000 off
Port 3: 0100 power
Port 4: 0100 power
- Dean
Read More...
actually, Anthony H beat me to it. It might be available on the bleeding edge nightly builds. you
can see the activity on github here:
tinyurl.com/yb7qepfu
There are some other features not coded into the driver that could be added, including
detection of deviced on the I2C channel (temp/humid sensor, external motor controller) and
control of the USB hub.
Read More...
from what I see on indi repo on github the c++ code for UPB driver already handles V1 and V2, so it should work if you select upb
Read More...
I have all the available command tables Pegasus Astro has posted and commands/responses in some cases
are different between devices. For example, PC command on the hub means print uptime in ms but on UPB it means
print power consumption, turning a port on or off on the hub is U1:b for example, but on UPB its PU:b .
Read More...
indilib on github has a fix for the Pocket Power Box (PPB) driver to acknowledge connection to the PPBA during handshake.
However, there is no support for the 4 port USB3 hub. That feature set is part of the Ultimate Power Box. I have forked the indilib
repo and intend to write the driver for PPBA ... currently waiting for Pegasus Astro to provide the serial command table specifically
for PPBA.
Read More...
thanks for the info: you give me hope! I bought the official pi case which is the worst one to get in terms of cooling.
Installed one of these lil guys (
tinyurl.com/yc2smjyc
) and by mounting it to a drillled 1..25" hole in the case top
the temp went from 80+ down to consistent 40C. didnt even use the supplied heat sinks. im thinking its a router
placement issue. like they say, its location location location!
- Dean
Read More...
Hi Jo,
picked up a new Archer A9 recently to replace my old C5. I did a test set up if the C5 in bridge mode wired direct to main C9 router... worked, but the
5GHz signal to the pi outside on the balcony is still too weak . Which extender do you use / recommend ?
Read More...
the OS already boots and runs direct off an SSD so not sure what advantage a RAM disk provides.
I think this is about wifi bandwidth because when the pi is "close" to my router, it is blazing fast over VNC whether on
2.4 or 5 GHz channel.
Read More...
so far ... not really. I got the 8Gb with the goal of either headless to indi server or VNC remote to KStars/Ekos with
SSD boot and hoping for a boost to laggy interaction over wifi: exploring with the cutting edge, a work in progress.
I tried remote headless with wifi 2.4GHz remote indi server with local KStars/Ekos but ran into a wall transferring
captures to the local client. I am trying KStars/Ekos on the pi so all plate solves and captures store to the SSD (very fast!!!) ,
control is done remote over VNC, but my LAN 2.4 GHz wifi or the way the pi 4B is set up results in laggy response.
I cant use 5GHz wifi effectively due to where the imaging rig is sited relative to the router. Oddly, my 3B+ setup
runs better than the pi 4B 8Gb with VNC.
Read More...
for me, even with pi4B+ 8Gb, the VNC desktop control is sluggish. Could be I'm on a 2.4GHz channel and also I learned using the
official pi case is the worst option for cooling the cpu. Hot cpu = messed up pi response: waiting for a brushless fan from amazon
and a dual channel wifi extender to boost my signal (or switch to 5GHz).
Read More...