Yeah, more. Sorry.
Recently reconfigured my rig and back to using the BomeBox again. Woo! Well...urm. heh
I'm using a Behringer CMD LC-1 (Button/Knob controller), the BomeBox, a DLink 4 port powered hub, and a Squarp Pyramid.
The DLink hub is using its own power supply for power.
The LC1 only has a single USB cable for power & data. The Pyramid is deriving power and data via the hub. Normally I have a DSI Prophet 12 and an Impact LX49 plugged in.
I don't know the words for it, but the LC1 and the Prophet have their own built-in hubs (?) since they have the USB "B" type of connector on their side.
I have tested this without the Prophet 12 and the Impact as the most important part is to get the LC1 communicating to the Pyramid via the BomeBox (and data from the Box back to the LC1 for LED feedback)
If the Power is disconnected from the BomeBox, the USB Hub 'turns off'...or rather, the power is cut to the devices attached to the hub.
One step thru: - On power up, plug the LC1 and the Pyramid into the hub. - Power the hub - Lights come on, Pyramid can boot up - Now I use a separate transformer and power the BomeBox. This cuts power to the LC1 and the Pyramid and during the BomeBox bootup, the power on the devices cycles a couple of times.
I"m trying to step thru things coherently, but I have a script that is supposed to set the light feedback on the LC1 and every time it does this cycle, it barfs the lighting configuration I created.
I just had a chat with DLink support to see if there is some sort of power cycling routine that happens when the hub is plugged in (data). The rep I spoke to indicated it should not.
I have been attempting to power the Pyramid and the LC1 before powering up the BomeBox because I have 'on load' bits in the script (Global Variables and setting up the initial led feedback configuration). Should I try a different process?