We have a number of Reach GPS modules installed into mobile robots. These modules do not have wifi access to the Internet, since they’re stuffed into metal boxes (the chassis of the robots).
We get fix data from the Reach modules over TCP via the USB/Ethernet interface at 192.168.2.15:12346, using the tcp_nmea_driver package in ROS. The interface itself is brought up as 192.168.2.2 when the host boots.
Now, on one of our robots, the driver fails to connect, so we attempt to SSH into the Reach to take a look around. When we try
we are prompted for a password, a couple of minutes passes, then we get
Write failed: Broken pipe.
I’ve seen something similar happen with generic USB/Ethernet dongles, but there’s usually something interesting in the kernel ring buffer. In this case, nothing. We’ll eventually do a site visit and replace the unit, but if anyone else has seen this, any advice would be appreciated.
P.S. Don’t know if it’s related, but ReachView (v2.9.3) shows the thing stuck at the “Connect to a wifi network” page, with no exit. There’s no wifi network to connect to, so it just sits there.