battery charging error

[k-okada]

Hi,

I had this situation described at https://github.com/fetchrobotics/docs/blame/feac201dfde2b380a5d9af89b316024f4c53c4e7/source/care_and_feeding.rst#L44

In some cases, the charging circuit may detect an error condition and will flash the charging indicator red. After about 1 minute, the charger will attempt charging again. If the error condition persists, a support ticket should be created to address the problem.

The robot just arrived this morning and we can run with joystick for a while, after ~10 - ~30 minuets, we realized that a robot did not respond. what we tried is;

• we can pair / dis-pair the joystick, it vibrate.
• we can not see any output from HDMI cable
• we connected the laptop to the service ether cable port, and set IP of the laptop to the 10.42.42.100, but ping 10.42.42.42 did not respond.

[dbking77]

Flashing Red Charging Indicator It seems like indicator you are describing is different. Is the "charging" indicator on the side of the robot flashing red? Below is the link to a picture of the robot side panel. The charging indicator is number 6. http://docs.fetchrobotics.com/_images/access_panel_numbered.png

Service Port The service port is setup to respond to 10.42.42.42 or 10.42.42.100, these are network address of devices on the internal robot network. The service connects directly to a computer Ethernet port. By default, the service port will try to get a IP address using DHCP. Since your computer is probably not running a DHCP server, the robot will not get an IP address.

HDMI There have been issues with the HDMI port working with certain monitors if the robot does not start-up with the monitor plugged in. You might want to try power cycling the robot with the HDMI plugged in. Also, plug in a USB mouse or keyboard, at the same time. Ubuntu Linux will turn off screen output if there has been no activity for a while. Moving the mouse, or typing on a keyboard will wake up the monitor output.

[erelson]

Important typo correction to one of @dbking77's notes above:

The service port is not setup to respond to 10.42.42.42 or 10.42.42.100, these are network address of devices on the internal robot network.

[mmwise]

This discussion has moved to the Fetch support site.