Loss of Connection
====================

A few things happen when the connection between the RDK client and the robot is lost, which can be caused by terminating a running RDK program or network interruption like unplugging the Ethernet cable.

Automatic stop
---------------

Upon loss of connection, the robot will automatically transit to :ref:`idle_mode`, which means the ongoing task will be stopped and the robot will decelerate to a complete stop then hold its position. 

Hot reconnection
----------------

After the connection is lost, the robot can be reconnected on-the-fly, thus you can restart the RDK program or re-plug the Ethernet cable to get reconnected without doing anything to the robot.

.. note::
  Because the robot has automatically transited to idle mode, ``Robot::SwitchMode()`` needs to be called again to switch control mode before new commands can be sent.