Remote Access Sharing

The Remote Access Server enables mobile clients to access the desktop of the PC running ARC. This unique client/server system routes audio between the client and server, allowing you to use the microphone on your mobile device as a remote mic for the ARC PC, and the speaker on the remote device as a remote speaker for the ARC PC. Additionally, it provides screen-sharing functionality similar to Remote Desktop.

Why Use Remote Access Server?

  • If your robot has an SBC onboard, allowing for remote control.
  • In educational institutions where devices like Chromebooks, tablets, or iPads are used to access the full ARC experience.

Network Configurations

Your robot will require a dedicated PC, which can be as cost-effective as an SBC. The SBC will need one of the following network configurations:

  1. Single WiFi & Ethernet: The robot operates in Adhoc mode, with the SBC connecting to the robot's WiFi. The SBC connects to the internet via Ethernet, while the Remote Access client can connect to either the WiFi or Ethernet network (generally Ethernet).
  2. Double WiFi: Similar to the above, but the SBC uses two WiFi interfaces—one for Adhoc mode with the robot and another for internet access. The Remote Access client typically connects to the interface with internet access.
  3. Single WiFi: Used when the robot doesn’t rely on WiFi (e.g., Arduino via USB) or its WiFi operates in Client mode, connecting to the local network. The SBC and Remote Access client connect to this local network.

Using the Remote Access Client

Main Screen UI

The main screen lets you input the IP address, port, and password. Additionally, any remote access servers on your network will broadcast and appear on the list below. Selecting one still requires you to enter the password.

Press the CONNECT button to connect to the specified Remote Access Server.

Remote Access UI

This screen mirrors the ARC PC’s monitor. Clicking or touching the screen simulates mouse clicks on the ARC PC. On devices like Chromebooks, the mouse integrates seamlessly for intuitive use.

Audio Redirection

The Remote Access Server redirects audio between the client and server. For example:

  • The client device’s microphone audio is sent to the ARC PC as its mic input in real time.
  • All audio from the ARC PC’s speaker is played through the client device’s speaker.

Audio Redirection Instructions

  1. Install the VB-Cable Virtual Audio Device Driver.
  2. Right-click the speaker icon in the ARC PC taskbar to access sound settings.
  3. Select the Cable Output (VB-Cable Virtual Cable) as the default input device.
    • Note: Leave the output device set to the PC’s default speaker.
  4. To prevent sound duplication, mute the volume on the ARC PC.

Enabling Remote Access Server in ARC

  1. From the ARC top menu, select the Options tab.
  2. Click the Preferences button to open the preferences popup window.
  3. Select the Remote Access tab to view the server settings.
  4. Check the Enable box to activate the server.
  5. Enter a memorable password.
  6. Leave other values at their defaults until you are familiar with their functionality.
  7. Click OK to save your settings.

Enabling Remote Access Server in ARC

You can verify the server’s status in the ARC Debug Log window. Messages will indicate the Remote Access Server’s activity, including audits of your audio configuration to ensure the VB-Cable virtual device is installed and selected.

In the example image above, you can see a successful configuration. The VB-Cable was discovered as the default input source, and RAS was started correctly.