5.1. Introduction

There are different ways to connect the dVRK controllers depending on which version of dVRK controllers are used.

While testing the communication with the dVRK controllers, keep in mind that the number of FPGA boards (showing as either a FireWire node or and Ethernet IP) depends on the type of controller you’re using and how they are connected. See controllers.

5.1.1. FireWire only

From the beginning, the dVRK software and mechatronics have used the IEEE 1394 interface standard with the libraw1394 library under Linux to communicate between the computer and the dVRK controllers. The interface standard IEEE 1394 is also known as FireWire (Wikipedia entry). In this scenario, the controllers are daisy-chained using FireWire and the computer is also on the FireWire chain. This approach works will all generations of dVRK controllers and is the most reliable approach.

../../_images/PC-FireWire-Controllers.png — FireWire only

5.1.2. FireWire with Ethernet bridge

Starting with dVRK Software Version 2.0, Ethernet/UDP is also supported. To use Ethernet/UDP, you will need to use firmware 7+ on all your dVRK controllers, and you will need at least one FPGA V2.x board (with Ethernet jack, see FPGA versions). In this scenario, the controllers are daisy-chained using FireWire, but the computer is not on the FireWire chain. Instead, the computer is connected via Ethernet to one of the dVRK controllers. Said dVRK controller becomes the “bridge” between the computer and all the other dVRK controllers.

../../_images/PC-Ethernet-Controllers.png — FireWire with Ethernet bridge

5.1.3. Ethernet only

todo

5.1.4. Bluetooth

For the dVRK Si, the communication between the SUJ and the PC relies on Bluetooth. This was the cheapest and fastest solution to read the SUJ potentiometers without adding external wires. This solution works fine but is a bit tricky to set up.