Differences

This shows you the differences between two versions of the page.

--- ece4560:piktul:calibrate [2015/03/02 14:52] – pvela
+++ ece4560:piktul:calibrate [2024/08/20 21:38] (current) – external edit 127.0.0.1
@@ Line 7: / Line 7: @@
 A summary of the procedure is packed into the following image.  Use it as a guide when reading through the rest of the calibration page.
 ;#;
-{{ECE4560:Piktul_calib_Summary.png}}
+{{ECE4560:Piktul:calib_Summary.png}}
 ;#;
@@ Line 41: / Line 41: @@
 Figure out what the servo command values are the get close to the limits, but do not hit them.  When doing this, please move the slider bar little by little until you get a feel for the appropriate limits.  Also make sure that the manipulator can move freely without hitting anything during this procedure. The associated angles, as measured by a protractor relative to the zero configuration, are the joint angle limits for your manipulator.  Each manipulator has different limits based on how it was put together.
+===== Done Calibrating: Deliverable ======
+--------------------
+Once all of the values are set and updated to reflect what works for the Piktul manipulator, take a screen capture of the calibration dialog box.  Turn that in as evidence of calibration. Next week, the lab assignment will be to confirm that the calibration is correct by comparing with the forward kinematics. That will be the true test.
+Also, turn in what values were used for the sleep joint configuration.
 ===== Manipulator Interface Code: Calibration File =====
 -----------------
 The easiest way to have the piktul know what the calibration values should be is to have saved it as a Matlab file for passing to the ''piktul'' object.  It is one of the optional arguments.  Sending the name of the calibration means that the piktul object will load those Matlab variables and overwrite the default values with those from the file.  Of course, you will still have to modify the code for the sleep joint configuration.  The rest should be automatic.  Since the piktul was built here in house and only one version exists, the coded link lengths should be correct.
+Once you have the calibration file, the ''piktul'' interface can be initialized with the parameters by loading and passing them as the argument to the ''piktul'' constructor:
+<code>
+arm  = piktul(load('pikparms.mat'));
+</code>
 ===== Manipulator Interface Code: Calibration =====
 -----------------
-The ''piktul.m'' code stub is the main interface file for the manipulator.  It is what you will be modifying to enhance the functionality of the manipulator as the course progresses.  Prior to running the code, you will need to use the setup program to identify the operational limits and calibrate the manipulator.  Calibration involves joint angle operational limits (in servo command units and degrees) plus link length measurement. Once these values have been found, the appropriate variables in ''piktul.m'' will need to be modified to reflect what you have found.
+The ''piktul.m'' code stub is the main interface file for the manipulator.  It is what you will be modifying to enhance the functionality of the manipulator as the course progresses.  Prior to running the code, you will need to use the setup program to identify the operational limits and calibrate the manipulator.  Calibration involves joint angle operational limits (in servo command units and degrees) plus link length measurement. Once these values have been found, the appropriate variables in ''piktul.m'' will need to be modified to reflect what you have found. **Note:** If you used the ''piktul_calibrate'' routine, then you do not need to be manually editing the fields here.
 Below are some of the variables you'll need to modify.  If you have any questions, feel free to ask.  Again, please be careful when changing and modifying the values.  Be prepared to turn the manipulator off if things go
@@ Line 63: / Line 73: @@
   * **alphaSleep:** Your sleep position as a joint configuration.
+---------
+;#;
+[[ece4560:manicontrol | Back ]]
+;#;