Contact Us
CiiS Lab
Johns Hopkins University
112 Hackerman Hall
3400 N. Charles Street
Baltimore, MD 21218
Directions
Lab Director
Russell Taylor
127 Hackerman Hall
rht@jhu.edu
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| courses:456:2023:projects:456-2023-01:project-01 [2023/05/10 19:47] – [Project Report And Status] bbanks15 | courses:456:2023:projects:456-2023-01:project-01 [2023/05/11 04:01] (current) – [Reports and presentations] bbanks15 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ======Transparency Optimization of the Galen Surgical System with a Frequency Domain Admittance Controller Design====== | ======Transparency Optimization of the Galen Surgical System with a Frequency Domain Admittance Controller Design====== | ||
| - | **Last updated: 5/9/2023 at 8:13 PM** | + | **Last updated: 5/10/2023 at 3:55 PM** |
| Line 295: | Line 295: | ||
| The following transfer functions for the X, Y, and Z axis were obtained for the real Galen robot system identification. Note that the actual system features a few new errors introducing variables. Two prominent variables that will be addressed here are the delay and the motor backlash. | The following transfer functions for the X, Y, and Z axis were obtained for the real Galen robot system identification. Note that the actual system features a few new errors introducing variables. Two prominent variables that will be addressed here are the delay and the motor backlash. | ||
| - | Table 2. The resultant real Galen system identification transfer functions and estimated delays | + | {{: |
| - | Velocity Component Transfer Function Estimated Delay (s) Quality of Match | + | |
| - | Vx 9.883e04/ | + | |
| - | Vy 1.607e07/ | + | |
| - | Vz 2.075e04/ | + | |
| The tfest MATLAB estimator was able to estimate the transfer functions in addition to measuring the time delays. This time delay could be caused by several factors. A few of these factors are due to the control processing delay between communication from the mid-level control to low-level to ROS and the actual robot. The delay is also a result of the lagging time in the acceleration or inertia of the robot hardware. This is especially present in the case of motor backlash. When the commanded velocity or present velocity of the robot reaches zero, especially on robot initialization, | The tfest MATLAB estimator was able to estimate the transfer functions in addition to measuring the time delays. This time delay could be caused by several factors. A few of these factors are due to the control processing delay between communication from the mid-level control to low-level to ROS and the actual robot. The delay is also a result of the lagging time in the acceleration or inertia of the robot hardware. This is especially present in the case of motor backlash. When the commanded velocity or present velocity of the robot reaches zero, especially on robot initialization, | ||
| - | + | {{: | |
| - | Figure 12 The output position of the real Galen robot, the velocity, and an fft of the velocity noise | + | |
| + | //The output position of the real Galen robot, the velocity, and an fft of the velocity noise// | ||
| - | Observe figure | + | Observe |
| We also can see that the output velocity of the robot, in orange, is a rather noisy signal. This is due to the fact that we only have access to the position measuring crtk_command tools that observe the motor encoders. To get the velocity of the position signal, we use a finite differentiation method between the current timestep and the previous time step to derive the position.This introduces lots of noise, and in order to utilize a more precise velocity signal for feedback control it is important to filter the data. | We also can see that the output velocity of the robot, in orange, is a rather noisy signal. This is due to the fact that we only have access to the position measuring crtk_command tools that observe the motor encoders. To get the velocity of the position signal, we use a finite differentiation method between the current timestep and the previous time step to derive the position.This introduces lots of noise, and in order to utilize a more precise velocity signal for feedback control it is important to filter the data. | ||
| Line 312: | Line 309: | ||
| We ran an fft on the finite differentiated velocity to observe what appropriate cutoff frequency should be used and deemed 75 Hz was an appropriate frequency to use in a first order low pass filter. | We ran an fft on the finite differentiated velocity to observe what appropriate cutoff frequency should be used and deemed 75 Hz was an appropriate frequency to use in a first order low pass filter. | ||
| - | Figure 12 shows an example of the response of the Z axis identification. This axis showed the smallest time delay of the 3 identified systems. We notice that this time delay is large rather large on the X axis and there are many factors still to be investigated that could be causing this. There is much more work to be done on the real system implementation and testing. | + | The above figure also shows an example of the response of the Z axis identification. This axis showed the smallest time delay of the 3 identified systems. We notice that this time delay is large rather large on the X axis and there are many factors still to be investigated that could be causing this. There is much more work to be done on the real system implementation and testing. |
| Line 318: | Line 315: | ||
| For our current approach, we chose to start simply with a single axis where we were most confident to obtain a good admittance response. We found the Z to have the smallest time delay and the stability analysis was deemed the most stable according to the following maps. | For our current approach, we chose to start simply with a single axis where we were most confident to obtain a good admittance response. We found the Z to have the smallest time delay and the stability analysis was deemed the most stable according to the following maps. | ||
| - | + | {{: | |
| - | Figure 13 Upper bound (with human and environment) impedance and Lower bound (only human) impedance stability and transparency maps for the Galen z axis. | + | |
| + | //Upper bound (with human and environment) impedance and Lower bound (only human) impedance stability and transparency maps for the Galen z axis.// | ||
| With the above results we were able to select a set of gains for the human only contact impedance case and test them on the real Galen robot. | With the above results we were able to select a set of gains for the human only contact impedance case and test them on the real Galen robot. | ||
| - | + | {{: | |
| - | Figure 14 User interacting with the Galen robot end effector to apply a wrench | + | |
| + | // User interacting with the Galen robot end effector to apply a wrench// | ||
| The admittance gains of 8kg and 20Ns/m were chosen for the mass and damping values respectively. A test was run for 10 seconds with the robot in gravity compensation mode. The user was instructed to wait 5 seconds and then apply an upwards input on the robot end effector. The following plot was obtained for the input reference velocity vs the input user force. | The admittance gains of 8kg and 20Ns/m were chosen for the mass and damping values respectively. A test was run for 10 seconds with the robot in gravity compensation mode. The user was instructed to wait 5 seconds and then apply an upwards input on the robot end effector. The following plot was obtained for the input reference velocity vs the input user force. | ||
| - | + | {{: | |
| - | Figure 15 The recorded input reference velocity as calculated from the admittance controller and the measured true force from the Galen robot end effector sensor. | + | |
| + | //The recorded input reference velocity as calculated from the admittance controller and the measured true force from the Galen robot end effector sensor.// | ||
| As anticipated, | As anticipated, | ||
| Line 394: | Line 396: | ||
| * Project Final Report | * Project Final Report | ||
| * {{: | * {{: | ||
| - | |||
| * Project Mentor' | * Project Mentor' | ||
| - | + | * {{ : | |
| ======Project Bibliography======= | ======Project Bibliography======= | ||