FIELD

[0001] The present disclosure generally relates to a surgical robotic system having one or more modular arm carts each of which supports a robotic arm and a surgical console for controlling the carts and their respective arms. More particularly, the present disclosure is directed to a system and method for registration of the modular arm carts in a surgical robotic system in relation to a surgical table.

BACKGROUND

[0002] Surgical robotic systems are currently being used in minimally invasive medical procedures. Some surgical robotic systems include a surgical console controlling a surgical robotic arm and a surgical instrument having an end effector (e.g., forceps or grasping instrument) coupled to and actuated by the robotic arm. In operation, the robotic arm is moved to a position over a patient and then guides the surgical instrument into a small incision via a surgical port or a natural orifice of a patient to position the end effector at a work site within the patient’s body.

[0003] Prior to utilizing the robotic arm, the robotic arm and the movable cart supporting the robotic arm need to be oriented around a surgical table and the orientation of the robotic arm must be known to properly control movement of the robotic arm relative to the surgical table. Thus, there is a need for a system to properly identify the orientation and placement of the robotic arms in the surgical operating room.

SUMMARY

[0004] According to one embodiment of the present disclosure, a surgical robotic system includes a movable cart, an orientation device, and a surgical console. The movable cart is positioned relative to a surgical table and includes a setup arm and a robotic arm. The orientation device includes a memory and a computer and is configured to store a zero position of the surgical table upon being placed at the zero position, link with the robotic arm, store a position of the setup arm upon being placed at the position of the setup arm, and calculate an orientation angle between the setup arm and the surgical table based on the stored zero position of the surgical table and the stored position of the setup arm. The surgical console includes an input device communicatively coupled to the robotic arm and is configured to control movement of the robotic arm and correlate the calculated orientation angle of the setup arm with movements of the input device for controlling movement of the robotic arm.

[0005] In an aspect, the setup arm includes an identification device readable by the orientation device for linking the orientation device to the setup arm and the identification device includes at least one of a near field communication chip or an optically readable code.

[0006] In an aspect, the setup arm includes an alignment member configured to align the orientation device to the setup arm upon placement of the orientation device at the position of the setup arm.

[0007] In an aspect, the surgical console is configured to determine whether two adjacent robotic arms are distanced a predetermined distance apart based on the calculated orientation angle of the setup arm.

[0008] In another aspect of the present disclosure, a surgical robotic system includes a surgical table, a first movable cart, a second movable cart, and an orientation device. The first movable cart is positioned relative to the surgical table and includes a first setup arm and the second movable cart positioned relative to the surgical table and includes a second setup arm. The orientation device includes a memory and a computer and is configured to store a zero position of the surgical table upon being placed at the zero position, link with the first setup arm, store a position of the first setup arm upon being placed at the position of the first setup arm, calculate an orientation angle between the first setup arm and the surgical table based on the stored zero position of the surgical table and the stored position of the first setup arm, link with the second setup arm, store a position of the second setup arm upon being placed at the position of the second setup arm, and calculate an orientation angle between the second setup arm and the surgical table based on the stored zero position of the surgical table and the stored position of the second setup arm.

[0009] In an aspect, the first setup arm includes a first identification device readable by the orientation device for linking the orientation device to the first setup arm and the second setup arm includes a second identification device readable by the orientation device for linking the orientation device to the second setup arm. [0010] In an aspect, the first identification device and the second identification device include at least one of a near field communication chip or an optically readable code.

[0011] In an aspect, the first movable cart includes a first brake and the second movable cart includes a second brake.

[0012] In an aspect, the surgical robotic system further includes a cart controller in communication with the orientation device. The cart controller is configured to identify the first movable cart as registered in response to the first brake being engaged and receipt of the orientation angle of the first setup arm, and identify the second movable cart as registered in response to the second brake being engaged and receipt of the orientation angle of the second setup arm.

[0013] In an aspect, the first setup arm includes a first alignment member configured to align the orientation device to the first setup arm upon placement of the orientation device at the position of the first setup arm and the second setup arm includes a second alignment member configured to align the orientation device to the second setup arm upon placement of the orientation device at the position of the second setup arm.

[0014] In an aspect, the surgical robotic system further includes a surgical console including an input device communicatively coupled to a first robotic arm of the first movable cart and second robotic arm of the second movable cart. The surgical console is configured to receive the calculated orientation angle of the first setup arm and the calculated orientation angle of the second setup arm from the orientation device, correlate the calculated orientation angle of the first setup arm with movements of the input device for controlling movement of the first robotic arm, and correlate the calculated orientation angle of the second setup arm with movements of the input device for controlling movement of the second robotic arm.

[0015] In an aspect, the computer is configured to determine whether the first movable cart and the second movable cart are spaced apart by a predetermined distance based on the orientation angle of the first setup arm and the orientation angle of the second setup arm.

[0016] In another aspect of the present disclosure, a method of registering a setup arm with a surgical table is provided. The method includes placing a first movable cart and a second movable cart around a surgical table, the first movable cart including a first setup arm and the second movable cart including a second setup arm, placing an orientation device at a zero position on the surgical table and storing the zero position in a memory of the orientation device, moving the orientation device from the zero position to the first setup arm, linking the orientation device to the first setup arm, calculating, by a computer of the orientation device, an orientation angle of the first setup arm relative to the surgical table, moving the orientation device from the first setup arm to the second setup arm, linking the orientation device to the second setup arm, and calculating, by the computer of the orientation device, an orientation angle of the second setup arm relative to the surgical table. [0017] In an aspect, the first setup arm includes a first identification device readable by the orientation device for linking the orientation device to the first setup arm and the second setup arm includes a second identification device readable by the orientation device for linking the orientation device to the second setup arm.

[0018] In an aspect, the first identification device and the second identification device include at least one of a near field communication chip or an optically readable code.

[0019] In an aspect, the first movable cart includes a first brake and the second movable cart includes a second brake.

[0020] In an aspect, the method further includes identifying the first movable cart as registered in response to the first brake being engaged and receipt of the orientation angle of the first setup arm, and identifying the second movable cart as registered in response to the second brake being engaged and receipt of the orientation angle of the second setup arm. [0021] In an aspect, the method further includes determining whether the first movable cart and the second movable cart are spaced apart by a predetermined distance based on the orientation angle of the first setup arm and the orientation angle of the second setup arm.

[0022] In an aspect, the first setup arm includes a first alignment member configured to align the orientation device to the first setup arm upon placement of the orientation device at the position of the first setup arm and the second setup arm includes a second alignment member configured to align the orientation device to the second setup arm upon placement of the orientation device at the position of the second setup arm.

[0023] In an aspect, the method further includes delivering the calculated orientation angle of the first setup arm and the calculated orientation angle of the second setup arm to a surgical console including an input device configured to control movement of a first robotic arm of the first movable cart and a second robotic arm of the second movable cart, correlating the calculated orientation angle of the first setup arm with movements of the input device for controlling movement of the first robotic arm, and correlating the calculated orientation angle of the second setup arm with movements of the input device for controlling movement of the second robotic arm.

BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Various embodiments of the present disclosure are described herein with reference to the drawings wherein:

[0025] FIG. l is a schematic illustration of a surgical robotic system including a control tower, a console, and one or more surgical robotic arms according to the present disclosure; [0026] FIG. 2 is a perspective view of a surgical robotic arm of the surgical robotic system of FIG. 1 according to the present disclosure;

[0027] FIG. 3 is a perspective view of a setup arm with the surgical robotic arm of the surgical robotic system of FIG. 1 according to the present disclosure;

[0028] FIG. 4 is a schematic diagram of a computer architecture of the surgical robotic system of FIG. 1 according to the present disclosure;

[0029] FIG. 5 is a perspective view of the setup arm and the surgical robotic arm of the surgical robotic system of FIG. 1 according to the present disclosure;

[0030] FIG. 6 is a side view of the setup arm and the surgical robotic arm of the surgical robotic system of FIG. 1 according to the present disclosure;

[0031] FIG. 7 is a schematic diagram of four setup arms positioned relative to a surgical table of the surgical robotic system of FIG. 1 according to the present disclosure; and [0032] FIG. 8 is a flowchart illustrating a method for registering a setup arm with a surgical table of the surgical robotic system of FIG. 1 according to the present disclosure.

DETAILED DESCRIPTION

[0033] Embodiments of the presently disclosed surgical robotic system are described in detail with reference to the drawings, in which like reference numerals designate identical or corresponding elements in each of the several views. As used herein the term “distal” refers to the portion of the surgical robotic system and/or the surgical instrument coupled thereto that is closer to the patient, while the term “proximal” refers to the portion that is farther from the patient.

[0034] The term “application” may include a computer program designed to perform functions, tasks, or activities for the benefit of a user. Application may refer to, for example, software running locally or remotely, as a standalone program or in a web browser, or other software which would be understood by one skilled in the art to be an application. An application may run on a controller, or on a user device, including, for example, a mobile device, an IOT device, or a server system.

[0035] As will be described in detail below, the present disclosure is directed to a surgical robotic system, which includes a surgical console, a control tower, and one or more movable carts having a surgical robotic arm coupled to a setup arm. The surgical console receives user input through one or more interface devices, which are interpreted by the control tower as movement commands for moving the surgical robotic arm. The surgical robotic arm includes a controller, which is configured to process the movement command and to generate a torque command for activating one or more actuators of the robotic arm, which would, in turn, move the robotic arm in response to the movement command.

[0036] With reference to FIG. 1, a surgical robotic system 10 includes a control tower 20, which is connected to all of the components of the surgical robotic system 10 including a surgical console 30 and one or more robotic arms 40. Each of the robotic arms 40 includes a surgical instrument 50 removably coupled thereto. Each of the robotic arms 40 is also coupled to a movable cart 60.

[0037] The surgical instrument 50 is configured for use during minimally invasive surgical procedures. In embodiments, the surgical instrument 50 may be configured for open surgical procedures. In embodiments, the surgical instrument 50 may be an endoscope, such as an endoscope camera 51, configured to provide a video feed for the user. In further embodiments, the surgical instrument 50 may be an electrosurgical forceps configured to seal tissue by compression tissue between jaw members and applying electrosurgical current thereto. In yet further embodiments, the surgical instrument 50 may be a surgical stapler including a pair of jaws configured to grasp and clamp tissue whilst deploying a plurality of tissue fasteners, e.g., staples, and cutting stapled tissue.

[0038] One of the robotic arms 40 may include a camera 51 configured to capture video of the surgical site. The surgical console 30 includes a first display 32, which displays a video feed of the surgical site provided by camera 51 of the surgical instrument 50 disposed on the robotic arms 40, and a second display 34, which displays a user interface for controlling the surgical robotic system 10. The first and second displays 32 and 34 are touchscreens allowing for displaying various graphical user inputs. [0039] The surgical console 30 also includes a plurality of user interface devices, such as foot pedals 36 and a pair of handle controllers 38a and 38b which are used by a user to remotely control robotic arms 40. The surgical console further includes an armrest 33 used to support clinician’s arms while operating the handle controllers 38a and 38b.

[0040] The control tower 20 includes a display 23, which may be a touchscreen, and outputs on the graphical user interfaces (GUIs). The control tower 20 also acts as an interface between the surgical console 30 and one or more robotic arms 40. In particular, the control tower 20 is configured to control the robotic arms 40, such as to move the robotic arms 40 and the corresponding surgical instrument 50, based on a set of programmable instructions and/or input commands from the surgical console 30, in such a way that robotic arms 40 and the surgical instrument 50 execute a desired movement sequence in response to input from the foot pedals 36 and the handle controllers 38a and 38b.

[0041] Each of the control tower 20, the surgical console 30, and the robotic arm 40 includes a respective computer 21, 31, 41. The computers 21, 31, 41 are interconnected to each other using any suitable communication network based on wired or wireless communication protocols. The term “network,” whether plural or singular, as used herein, denotes a data network, including, but not limited to, the Internet, Intranet, a wide area network, or a local area networks, and without limitation as to the full scope of the definition of communication networks as encompassed by the present disclosure. Suitable protocols include, but are not limited to, transmission control protocol/internet protocol (TCP/IP), datagram protocol/internet protocol (UDP/IP), and/or datagram congestion control protocol (DCCP). Wireless communication may be achieved via one or more wireless configurations, e.g., radio frequency, optical, Wi-Fi, Bluetooth (an open wireless protocol for exchanging data over short distances, using short length radio waves, from fixed and mobile devices, creating personal area networks (PANs), ZigBee® (a specification for a suite of high level communication protocols using small, low-power digital radios based on the IEEE 122.15.4-2003 standard for wireless personal area networks (WPANs)).

[0042] The computers 21, 31, 41 may include any suitable processor (not shown) operably connected to a memory (not shown), which may include one or more of volatile, non-volatile, magnetic, optical, or electrical media, such as read-only memory (ROM), random access memory (RAM), electrically-erasable programmable ROM (EEPROM), non-volatile RAM (NVRAM), or flash memory. The processor may be any suitable processor (e.g., control circuit) adapted to perform the operations, calculations, and/or set of instructions described in the present disclosure including, but not limited to, a hardware processor, a field programmable gate array (FPGA), a digital signal processor (DSP), a central processing unit (CPU), a microprocessor, and combinations thereof. Those skilled in the art will appreciate that the processor may be substituted for by using any logic processor (e.g., control circuit) adapted to execute algorithms, calculations, and/or set of instructions described herein.

[0043] With reference to FIG. 2, each of the robotic arms 40 may include a plurality of links 42a, 42b, 42c, which are interconnected at joints 44a, 44b, 44c, respectively. The joint 44a is configured to secure the robotic arm 40 to the movable cart 60 and defines a first longitudinal axis. With reference to FIG. 3, the movable cart 60 includes a lift 61 and a setup arm 62, which provides a base for mounting of the robotic arm 40. The lift 61 allows for vertical movement of the setup arm 62. The movable cart 60 also includes a display 69 for displaying information pertaining to the robotic arm 40.

[0044] The setup arm 62 includes a first link 62a, a second link 62b, and a third link 62c, which provide for lateral maneuverability of the robotic arm 40. The links 62a, 62b, 62c are interconnected at joints 63a and 63b, each of which may include an actuator (not shown) for rotating the links 62a and 62b relative to each other and the link 62c. In particular, the links 62a, 62b, 62c are movable in their corresponding lateral planes that are parallel to each other, thereby allowing for extension of the robotic arm 40 relative to the patient (e.g., surgical table). In embodiments, the robotic arm 40 may be coupled to the surgical table 100 (FIG. 7). The setup arm 62 includes controls 65 for adjusting movement of the links 62a, 62b, 62c as well as the lift 61.

[0045] The third link 62c includes a rotatable base 64 having two degrees of freedom. In particular, the rotatable base 64 includes a first actuator 64a and a second actuator 64b. The first actuator 64a is rotatable about a first stationary arm axis which is perpendicular to a plane defined by the third link 62c and the second actuator 64b is rotatable about a second stationary arm axis which is transverse to the first stationary arm axis. The first and second actuators 64a and 64b allow for full three-dimensional orientation of the robotic arm 40.

[0046] With reference to FIG. 2, the robotic arm 40 also includes a holder 46 defining a second longitudinal axis and configured to receive an instrument drive unit (IDU) 52 (FIG. 1). The IDU 52 is configured to couple to an actuation mechanism of the surgical instrument 50 and the camera 51 and is configured to move (e.g., rotate) and actuate the instrument 50 and/or the camera 51. IDU 52 transfers actuation forces from its actuators to the surgical instrument 50 to actuate components (e.g., end effectors) of the surgical instrument 50. The holder 46 includes a sliding mechanism 46a, which is configured to move the IDU 52 along the second longitudinal axis defined by the holder 46. The holder 46 also includes a joint 46b, which rotates the holder 46 relative to the link 42c.

[0047] The robotic arm 40 also includes a plurality of manual override buttons 53 disposed on the IDU 52 and the setup arm 62, which may be used in a manual mode. The user may press one or the buttons 53 to move the component associated with the button 53. [0048] The joints 44a and 44b include an actuator 48a and 48b configured to drive the joints 44a, 44b, 44c relative to each other through a series of belts 45a and 45b or other mechanical linkages such as a drive rod, a cable, or a lever and the like. In particular, the actuator 48a is configured to rotate the robotic arm 40 about a longitudinal axis defined by the link 42a.

[0049] The actuator 48b of the joint 44b is coupled to the joint 44c via the belt 45a, and the joint 44c is in turn coupled to the joint 46c via the belt 45b. Joint 44c may include a transfer case coupling the belts 45a and 45b, such that the actuator 48b is configured to rotate each of the links 42b, 42c and the holder 46 relative to each other. More specifically, links 42b, 42c, and the holder 46 are passively coupled to the actuator 48b which enforces rotation about a pivot point “P” which lies at an intersection of the first axis defined by the link 42a and the second axis defined by the holder 46. Thus, the actuator 48b controls the angle 91 between the first and second axes allowing for orientation of the surgical instrument 50. Due to the interlinking of the links 42a, 42b, 42c, and the holder 46 via the belts 45a and 45b, the angles between the links 42a, 42b, 42c, and the holder 46 are also adjusted in order to achieve the desired angle 91. In embodiments, some or all of the joints 44a, 44b, 44c may include an actuator to obviate the need for mechanical linkages.

[0050] With reference to FIG. 4, each of the computers 21, 31, 41 of the surgical robotic system 10 may include a plurality of controllers, which may be embodied in hardware and/or software. The computer 21 of the control tower 20 includes a controller 21a and safety observer 21b. The controller 21a receives data from the computer 31 of the surgical console 30 about the current position and/or orientation of the handle controllers 38a and 38b and the state of the foot pedals 36 and other buttons. The controller 21a processes these input positions to determine desired drive commands for each joint of the robotic arm 40 and/or the IDU 52 and communicates these to the computer 41 of the robotic arm 40. The controller 21a also receives back the actual joint angles and uses this information to determine force feedback commands that are transmitted back to the computer 31 of the surgical console 30 to provide haptic feedback through the handle controllers 38a and 38b. The safety observer 21b performs validity checks on the data going into and out of the controller 21a and notifies a system fault handler if errors in the data transmission are detected to place the computer 21 and/or the surgical robotic system 10 into a safe state.

[0051] The computer 41 includes a plurality of controllers, namely, a main cart controller 41a, a setup arm controller 41b, a robotic arm controller 41c, and an instrument drive unit (IDU) controller 4 Id. The main cart controller 41a receives and processes joint commands from the controller 21a of the computer 21 and communicates them to the setup arm controller 41b, the robotic arm controller 41c, and the IDU controller 4 Id. The main cart controller 41a also manages instrument exchanges and the overall state of the movable cart 60, the robotic arm 40, and the IDU 52. The main cart controller 41a also communicates actual joint angles back to the controller 21a.

[0052] The setup arm controller 41b controls each of joints 63a and 63b, and the rotatable base 64 of the setup arm 62 and calculates desired motor movement commands (e.g., motor torque) for the pitch axis and controls the brakes. The robotic arm controller 41c controls each joint 44a and 44b of the robotic arm 40 and calculates desired motor torques required for gravity compensation, friction compensation, and closed loop position control of the robotic arm 40. The robotic arm controller 41c calculates a movement command based on the calculated torque. The calculated motor commands are then communicated to one or more of the actuators 48a and 48b in the robotic arm 40. The actual joint positions are then transmitted by the actuators 48a and 48b back to the robotic arm controller 41c.

[0053] The IDU controller 41d receives desired joint angles for the surgical instrument 50, such as wrist and jaw angles, and computes desired currents for the motors in the IDU 52. The IDU controller 41d calculates actual angles based on the motor positions and transmits the actual angles back to the main cart controller 41a.

[0054] The robotic arm 40 is controlled as follows. Initially, a pose of the handle controller controlling the robotic arm 40, e.g., the handle controller 38a, is transformed into a desired pose of the robotic arm 40 through a hand eye transform function executed by the controller 21a. The hand eye function, as well as other functions described herein, is/are embodied in software executable by the controller 21a or any other suitable controller described herein. The pose of one of the handle controller 38a may be embodied as a coordinate position and role-pitch-yaw (“RPY”) orientation relative to a coordinate reference frame, which is fixed to the surgical console 30. The desired pose of the instrument 50 is relative to a fixed frame on the robotic arm 40. The pose of the handle controller 38a is then scaled by a scaling function executed by the controller 21a. In embodiments, the coordinate position is scaled down and the orientation is scaled up by the scaling function. In addition, the controller 21a also executes a clutching function, which disengages the handle controller 38a from the robotic arm 40. In particular, the controller 21a stops transmitting movement commands from the handle controller 38a to the robotic arm 40 if certain movement limits or other thresholds are exceeded and in essence acts like a virtual clutch mechanism, e.g., limits mechanical input from effecting mechanical output. [0055] The desired pose of the robotic arm 40 is based on the pose of the handle controller 38a and is then passed by an inverse kinematics function executed by the controller 21a. The inverse kinematics function calculates angles for the joints 44a, 44b, 44c of the robotic arm 40 that achieve the scaled and adjusted pose input by the handle controller 38a. The calculated angles are then passed to the robotic arm controller 41c, which includes a joint axis controller having a proportional-derivative (PD) controller, the friction estimator module, the gravity compensator module, and a two-sided saturation block, which is configured to limit the commanded torque of the motors of the joints 44a, 44b, 44c.

[0056] With reference to FIGS. 5-8, the surgical robotic system 10 (FIG. 1) includes an orientation device 400 which is used for calculating the orientation of each setup arm 62 of each robotic arm 40 relative to the surgical table 100. The orientation device 400 includes a memory and a processor configured to execute software and is communicatively coupled to the computers 21, 31, and 41 of the control tower 20, the surgical console 30, and the robotic arm 40 and allows for the transfer of data and information to and from the orientation device 400 and the control tower 20, the surgical console 30, and the robotic arm 40. In embodiments, the orientation device 400 may have a wired connection (e.g., USB), or may include a wireless transmitter/receiver in wireless communication with the control tower 20 and/or surgical console 30, which also may include a wireless transmitter/receiver. The wireless communication may be radio frequency, optical, WiFi®, Bluetooth® (an open wireless protocol for exchanging data over short distances using short length radio waves), etc. The control tower 20 and/or surgical console 30 may transfer data and/or real-time data from the orientation device 400. The control tower 20 or the surgical console 30 utilizes this information to correlate movement of the robotic arm 40, relative to the surgical table 100, with movements of input devices, e.g., handle controllers 38a, 38b, from the surgical console 30. In embodiments, the orientation device 400 may include a camera 402. The orientation device 400 is configured to either calculated the orientation angles of the setup arms 62 or acquire data for delivery to another component of the surgical robotic system 10 (e.g. one or more of computers 21, 31, 41) so that another component of the surgical robotic system 10 (e.g., one or more of computers 21, 31, 41) may calculate the orientation angles of the setup arms 62.

[0057] FIG. 7 illustrates an example configuration utilizing four setup arms 62, referred to individually as first setup arm 621, second setup arm 622, third setup arm 623, and fourth setup arm 624, but any number of setup arms 62 may be utilized with the surgical robotic system 10 depending on the particular need for the procedure being performed. Each setup arm 62 includes an identification device 67a, which is readable by the orientation device 400 to identify the particular setup arm 62, and an alignment member 67b which enables proper alignment of the orientation device 400 to the setup arm 62. The identification device 67a may be any suitable device readable by the orientation device 400, for example a near field communication tag, RFID tag, or optically readable tag (e.g., QR code, bar code, etc.). Thus, the orientation device 400 may include a scanning device, such as the camera 402to read the identification device 67a of the setup arm 62, or a user may manually enter the identification information of the setup arm 62 to link the orientation device 400 to the specific setup arm 62 when appropriate.

[0058] Referring to FIG. 6 specifically, alignment member 67b is shown as a recess formed in the housing of the setup arm 62 for receiving the orientation device 400, however alignment member 67b may include any suitable structure capable of assisting in ensuring the proper alignment of the orientation device 400 against the setup arm 62, such as a recess, protrusion, ledge, and/or magnetic-based or sensor-based orientation elements. [0059] FIG. 8 depicts a flow chart 600 of an illustrative method for registering alignment of a robotic arm 40 with the surgical table 100, which is described in connection with FIGS. 5-7. When setting up the surgical robotic system 10 at step 602, a user may be shown instructions for positioning the movable cart 60, which includes the setup arm 62 (e.g., the first setup arm 621), robotic arm 40, and surgical instrument 50, adjacent to the surgical table 100. The user then adjusts the setup arm 62 or the movable cart 60 to align the setup arm 62 with the surgical table 100. A single setup arm 62 may be oriented in step 602, or multiple setup arms 62 may be orientated in step 602.

[0060] In step 604, once a user adjusts the setup arm 62 or the movable cart 60 relative to the surgical table 100, the orientation device 400 is placed at a zero position 110 on the surgical table 100, for storage of the zero position 110 in the memory of the orientation device 400. The zero position 110 is a reference point (e.g., on the surgical table 100) which is utilized for calculating the orientation angles (e.g., 0a, 9b, 9c, 9d...9n) between each setup arm 62 (e.g., the first setup arm 621, the second setup arm 622, the third setup arm 623, the fourth setup arm 624, etc.) and the reference point on the surgical table 100. After the zero position 110 is stored in the memory of the orientation device 400, the orientation device 400, in step 604, is moved from the zero position 110 to the setup arm 62 (e.g., the first setup arm 621). Step 604 may include resting the orientation device 400 against the alignment member 67b of the setup arm 62 to ensure proper alignment of the orientation device 400 relative to a surface of the setup arm 62.

[0061] In step 606, the orientation device 400 is communicatively linked to the setup arm 62 (e.g., the first setup arm 461). In an aspect, once the orientation device 400 is moved to the proximity of the setup arm 62, the orientation device 400 is automatically linked to the setup arm 62 via the identification device 67a of the setup arm 62 (e.g., an RFID tag or near field communication device readable by the orientation device 400), for example, when the orientation device 400 is rested against alignment member 67b. In another aspect, the setup arm 62 includes an optically readable identification device 67a, such as a bar code or QR code, which is readable by the orientation device 400 to link the orientation device 400 to the setup arm 62. Once the orientation device 400 is linked to the setup arm 62 and placed against the alignment member 67b, in step 608, the orientation angle (e.g., 9a) between the linked setup arm 62 (e.g., the first setup arm 621) and zero position 110 of the surgical table 100 is calculated either by the orientation device 400 itself or another component of the surgical robotic system 10. The calculation may be triggered automatically upon being linked with the setup arm 62 or may be triggered upon manual activation by a user. In an aspect, the orientation device 400 or other component of the surgical robotic system 10 may be prevented from calculating the orientation angle in step 608 unless it is confirmed that the brakes 68 of the movable cart 60 are activated (e.g., engaged) to prevent inadvertent movement of the movable cart 60 during or after the orientation angle is calculated. In an aspect, the user may manually confirm that the brakes 68 are activated by inputting a manual confirmation. Alternatively, the brakes 68 may include a sensor (not shown) for the movable cart 60 to communicatively confirm the current state of the brakes 68, that is, whether the brakes 68 are activated or not.

[0062] In step 610, the orientation device 400 or other component of the surgical robotic system 10 determines the orientation of the setup arm 62 (e.g., the first setup arm 621) relative to the surgical table 100 based on the calculated orientation angle (e.g., 0a) between the linked setup arm 62 (e.g., the first setup arm 621) and the zero position 110 of the surgical table 100. If more than one robotic arm 40 is being utilized, then the user may move the orientation device 400 to the next setup arm 62 (e.g., from the first setup arm 621 to the second setup arm 622) for acquiring the orientation angle of the next setup arm 62. In step 612, the orientation device 400 or other component of the surgical robotic system 10 transmits the determined orientation of the setup arm 62 (e.g., the first setup arm 621), determined in step 610, to the surgical console 30.

[0063] In step 614, the surgical console 30 correlates the orientation of the setup arm 62 (e.g., the first setup arm 621) relative to the surgical table 100 with movements of the handle controllers 38a, 38b for manipulating the robotic arm 40 associated with the setup arm 62. Step 614 may be carried out immediately subsequent to step 612, or step 614 may be carried out after all orientation angles (e.g., 9a, 9b, 9c, 9d) for each linked setup arm 62 (e.g., first setup arm 621, second setup arm 622, third setup arm 623, fourth setup arm 624) is calculated by either the orientation device 400 or another component of the surgical robotic system 10. Thus, in an aspect, after the orientation angle 9a of the first setup arm 621 is calculated, the user may move the orientation device 400 to the second setup arm 622, where steps 606, 608, 610, and 612 are carried out for calculating the orientation angle 9b of the second setup arm 622 by either the orientation device 400 or another component of the surgical robotic system 10. Additionally, after the orientation angle 9b of the second setup arm 622 is calculated, the user may move the orientation device 400 to the third setup arm 623, where steps 606, 608, 610, and 612 are carried out for calculating the orientation angle 0c of the third setup arm 623 by either the orientation device 400 or another component of the surgical robotic system 10, and after the orientation angle 9c of the third setup arm 623 is calculated, the user may move the orientation device 400 to the fourth setup arm 624, where steps 606, 608, 610, and 612 are carried out for calculating the orientation angle 9d of the fourth setup arm 624 by either the orientation device 400 or another component of the surgical robotic system 10. These steps may be repeated for any number of setup arms 62 being used with the surgical robotic system 10. As each orientation angle (e.g., 9a, 9b, 9c, 9d) is calculated, or after all orientation angles (e.g., 9a, 9b, 9c, 9d) are calculated, step 614 may be carried out by the surgical console 30 to correlate the respective orientations of each setup arm 62 relative to the surgical table 100 with movements of handle controllers 38, 38b for manipulating the respective robotic arm 40 associated with the setup arm 62. [0064] In addition to correlating the orientation of the setup arm 62 relative to the surgical table 100 with movements of handle controllers 38, 38b for manipulating the respective robotic arm 40 associated with the setup arm 62, the surgical console 30 may utilize the data corresponding to the respective orientation angles 9a, 9b, 9c, 9d...9n to determine whether the movable carts 60 are sufficiently spaced apart so as to avoid the possibility of a collision between components of any two movable carts 60. In particular, the surgical console 30 may determine whether the movable carts 60 are spaced apart by a predetermined distance, and if not, notify the user (e.g., via an audible, visual, and/or tactile notification) that the movable carts 60 are positioned too close together and may collide as the respective robotic arms 40 are moved.

[0065] The surgical robotic system 10 according to the present disclosure is configured to perform a registration process to correlate (e.g., register) the orientation of each of a plurality of movable carts 60 and attached robotic arm 40 relative to a central point in space, such as a surgical table 100 (FIG. 7) using the orientation angles (e.g., 9a, 9b, 9c, 9d) calculated for each setup arm 62. During the registration process, the surgical robotic system 10 determines the relative orientation of the setup arms 62 of the robotic arms 40 using the orientation device 400 as described above. The surgical robotic system 10, and in particular the computer 21 of the control tower 20, is configured to execute an algorithm that computes the registration angles for each movable cart 60 based on the orientation angle 9 as input from the orientation device 400 or other components of the surgical robotic system

10 as described above with respect to FIGS. 5-8.

[0066] Furthermore, registered and unregistered notifications are sent out to the control tower 20 and the surgical console 30 to indicate the registration state of each movable cart 60. Registration is also confirmed by the operating room staff before performing tele- robotic operation of the surgical robotic system 10.

[0067] The main cart controller 41a is configured to perform the registration process and handles setting various registration states for the movable cart 60 and the robotic arm 40. In one embodiment, the main cart controller 41a is configured to set the movable cart 60 to a registered state when the following conditions are met: 1) one or more of the brakes 68 are activated to prevent the movement of the movable cart 60 (via a sensor communication or via a manual input); 2) the robotic arm 40 attached to the movable cart 60 is aligned relative to the surgical table 100 and the orientation angle is received from the orientation device 400; and 3) the surgical instrument 50 of the robotic arm 40 is coupled to an access port or trocar (not shown) that is inserted into a patient’s abdominal cavity (via a sensor communication or via a manual input).

[0068] Conversely, the main cart controller 41a is configured to set the movable cart 60 to an unregistered state when the following conditions are met: 1) one or more of the brakes 68 are deactivated to allow the movement of the movable cart 60; and 2) the surgical instrument 50 of the robotic arm 40 is decoupled to the port or trocar.

[0069] The controller 21a coordinates communication between operating room team interface (ORTI) and the main cart controller 41a of the movable cart 60. The ORTI is displayed on the display 23 of the control tower 20 as well as the second display 34. The controller 21a is also configured to confirm that each of the movable carts 60 is registered before teleoperation is enabled for the robotic arm 40 and is further configured to determine when two adjacent robotic arms 40 are too close to each other based on the registered angle. The controller 21a receives the registration status of each movable cart 60 and publishes data to the main cart controller 41a of each of the movable cart 60 and the ORTI indicating which robotic arms 40 have been user-confirmed, and warnings (e.g., audible, visual, and/or tactile) if the robotic arms 40 are placed too close together.

[0070] It will be understood that various modifications may be made to the embodiments disclosed herein. In embodiments, the sensors may be disposed on any suitable portion of the robotic arm. Therefore, the above description should not be construed as limiting, but merely as exemplifications of various embodiments. Those skilled in the art will envision other modifications within the scope and spirit of the claims appended thereto.