Hi Jason,
I've encountered similar issues with R1's before. I think it comes back to
the xports simply being unreliable. I've heard of cases in which the xports
work for a few months but unpredictably stop working at some point. There have
also been cases in which the xport never works to begin with. The latter has
been the case with some of the LoFASM ROACH-1's; xport was dead out of the box.
In one particular case this became a problem for us since we really needed to
be able to access the auto power-on feature as well as be able to force the R1
on/off remotely. We ended up programming an arduino that was used as a 'digital
finger' that emulated the pressing of the power button on the chassis itself.
Our ROACH board at LoFASM-II at the LWA North Arm is configured this way.
Best of luck,
L
Sent from my iPhone
> On Dec 3, 2014, at 18:42, Jason Ray <j...@nrao.edu> wrote:
>
> All,
>
> We're having an issue with a roach1 in GB where we can't access the xport. It
> doesn't seem to respond using a web browser to the default IP of
> 192.168.20.4. We also had our sys admin add an entry for its MAC address to
> our DHCP server and we still cannot communicate with it.
>
> As far as I know, we have never even tried to access the xport on this roach,
> much less accidentally set it to some IP we can't remember.
>
> We know our laptop is configured correctly because we can access xport on one
> of the other roaches here.
>
> A few questions -- does anyone have a suggestion on how we could get into the
> xport? Is there a way to reset it to the factory defaults by chance?
>
> We need to do this to enable the "auto power-up" feature. Is there any other
> way to enable this feature besides xport?
>
> Thanks,
> Jason
>
