A USB interface is an option, but this is not what it was designed for. We found that the ROACH1's XPORT scheme was a bit of a headache to configure off the production line, complicated the board's design, assembly and debugging, and it wasn't always as reliable as it could be. So, although ROACH-1 was equipped with a remote reboot system, we ended up using Ethernet controlled powerstrips in KAT-7 (which was needed to power cycle other items in the rack, so they were there anyway).
For these reasons, we left the remote power control capability out of ROACH2 and opted to just use external Ethernet controlled strips instead. Jason On 18 Oct 2012, at 23:24, Matt Dexter wrote: > Good question Homin. > > That prompts what is the plan when one has a rack > full of roach2 systems? > Perhaps use a networked computer tied thru a big N-way USB hub with > a USB cable to each of the Roach2 systems ? > > > > On Fri, 19 Oct 2012, homin wrote: > >> Date: Fri, 19 Oct 2012 05:16:15 +0800 >> From: homin <[email protected]> >> To: [email protected] >> Subject: [casper] remote power cycling of roach2 >> Hello Cape Town group: >> Recently we deployed a ROACH2 on site. Due to some unknown problem, we have >> to >> power cycling it from time to time. I saw there are couple of python programs >> in the Github for the power cycling and push button remotely. Could anyone >> inform me the procedure of how to use it ? >> thanks >> homin Jiang >> ASIAA >>
