Last modified by Eric Nantel on 2025/06/06 07:47

From version < 16.1 >
edited by Coleman Benson
on 2018/04/13 16:11
To version < 12.1 >
edited by Coleman Benson
on 2018/04/04 12:36
< >
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -42,28 +42,6 @@
42 42  Modified commands are command specific.
43 43  )))
44 44  
45 -(((
46 -
47 -)))
48 -
49 -== Configuration Commands ==
50 -
51 -Configuration commands affect the servo's current session* but unlike action commands, configuration commands are written to EEPROM and are retained even if the servo loses power (therefore NOT session specific). Not all action commands have a corresponding configuration and vice versa. Certain configurations are retained for when the servo is used in RC model. More information can be found on the [[LSS - RC PWM page>>doc:Lynxmotion Smart Servos (LSS).LSS - RC PWM.WebHome]].
52 -
53 -1. Start with a number sign # (U+0023)
54 -1. Servo ID number as an integer
55 -1. Configuration command (two to three letters, no spaces, capital or lower case)
56 -1. Configuration value in the correct units with no decimal
57 -1. End with a control / carriage return '<cr>'
58 -
59 -Ex: #5CO-50<cr>
60 -
61 -Assigns an absolute origin offset of -5.0 degrees (with respect to factory origin) to servo #5 and changes the offset for that session to -5.0 degrees.
62 -
63 -Configuration commands are not cumulative, in that if two configurations are sent at any time, only the last configuration is used and stored.
64 -
65 -*Important Note: the one exception is the baud rate - the servo's current session retains the given baud rate. The new baud rate will only be in place when the servo is power cycled.
66 -
67 67  == Query Commands ==
68 68  
69 69  Query commands are sent serially to the servo's Rx pin and must be set in the following format:
... ... @@ -91,21 +91,25 @@
91 91  )))
92 92  
93 93  Indicates that servo #5 is currently at 144.3 degrees.
72 +)))
94 94  
95 -**Session vs Configuration Query**
74 +== Configuration Commands ==
96 96  
97 -By default, the query command returns the sessions' value; should no action commands have been sent to change, it will return the value saved in EEPROM from the last configuration command.
76 +Configuration commands affect the servo's current session* but unlike action commands, configuration commands are written to EEPROM and are retained even if the servo loses power (therefore NOT session specific). Not all action commands have a corresponding configuration and vice versa. Certain configurations are retained for when the servo is used in RC model. More information can be found on the [[LSS - RC PWM page>>doc:Lynxmotion Smart Servos (LSS).LSS - RC PWM.WebHome]].
98 98  
99 -In order to query the value in EEPROM, add a '1' to the query command.
78 +1. Start with a number sign # (U+0023)
79 +1. Servo ID number as an integer
80 +1. Configuration command (two to three letters, no spaces, capital or lower case)
81 +1. Configuration value in the correct units with no decimal
82 +1. End with a control / carriage return '<cr>'
100 100  
101 -Ex: #5CSR20<cr> sets the maximum speed for servo #5 to 20rpm upon RESET (explained below).
84 +Ex: #5CO-50<cr>
102 102  
103 -After RESET: #5SR4<cr> sets the session's speed to 4rpm.
86 +Assigns an absolute origin offset of -5.0 degrees (with respect to factory origin) to servo #5 and changes the offset for that session to -5.0 degrees.
104 104  
105 -#5QSR<cr> would return *5QSR4<cr> which represents the value for that session.
88 +Configuration commands are not cumulative, in that if two configurations are sent at any time, only the last configuration is used and stored.
106 106  
107 -#5QSR1<cr> would return *5QSR20<cr> which represents the value in EEPROM
108 -)))
90 +*Important Note: the one exception is the baud rate - the servo's current session retains the given baud rate. The new baud rate will only be in place when the servo is power cycled.
109 109  
110 110  = Command List =
111 111  
... ... @@ -125,8 +125,8 @@
125 125  | 11|**W**heel mode in **R**PM| WR| QWR| | | ✓| rpm|
126 126  | 12|**S**peed in **D**egrees| SD| QSD| CSD| ✓| ✓| tenths of degrees per second (ex 248 = 24.8 degrees per second)|
127 127  | 13|**S**peed in **R**PM| SR| QSR| CSR| ✓| ✓| rpm|
128 -| 14|**R**igidity| R| QR| CR| ✓| ✓|none|
129 -| 15|//N/A (removed)//| | | | | | |
110 +| 14|**A**ngular **A**cceleration| AA| QAA| CAA| ✓| ✓| tenths of degrees per second squared|
111 +| 15|**A**ngular **D**eceleration| AD| QAD| CAD| | | tenths of degrees per second squared|
130 130  | 16|**LED** Color| LED| QLED| CLED| ✓| ✓| none (integer from 1 to 8)|0=OFF 1=RED 2=GREEN 3= BLUE 4=YELLOW 5=CYAN 6= 7=MAGENTA, 8=WHITE
131 131  | 17|**ID** #| ID| QID| CID| | ✓| none (integer from 0 to 250)|Note: ID 254 is a "broadcast" which all servos respond to.
132 132  | 18|**B**aud rate| B| QB| CB| | ✓| none (integer)|
... ... @@ -309,38 +309,46 @@
309 309  
310 310  Using the CSD command sets the servo's maximum speed which is saved in EEPROM. In the example above, the servo's maximum speed will be set to 45rpm. When the servo is powered on (or after a reset), the CSD value is used. Note that CSD and CSR are effectively the same, but allow the user to specify the speed in either unit. The last command (either CSR or CSD) is what the servo uses for that session.
311 311  
312 -__14. Rigidity (R)__
294 +__14. Angular Acceleration (**AA**)__
313 313  
314 -The servo's rigidity can be thought of as (though not identical to) a damped spring in which the rigidity value affects the stiffness and embodies how much, and how quickly the servo tried keep the requested position against changes.
296 +{More information coming soon}
315 315  
316 -A positive value of "rigidity":
298 +Ex:
317 317  
318 -* The more torque will be applied to try to keep the desired position against external input / changes
319 -* The faster the motor will reach its intended travel speed and the motor will decelerate faster and nearer to its target position
300 +{Description coming soon}
320 320  
321 -A negative value on the other hand:
302 +Query Angular Acceleration (**QAA**)
322 322  
323 -* Causes a slower acceleration to the travel speed, and a slower deceleration
324 -* Allows the target position to deviate more from its position before additional torque is applied to bring it back
304 +Ex:
325 325  
326 -The default value is zero and the effect becomes extreme by -4, +4. There are no units, only integers between -4 to 4. Greater values produce increasingly erratic behavior.
306 +{Description coming soon}
327 327  
328 -Ex: #5R-2<cr>
308 +Configure Angular Acceleration (**CAA**)
329 329  
330 -This reduces the rigidity to -2 for that session, allowing the servo to deviate more around the desired position. This can be beneficial in many situations such as impacts (legged robots) where more of a "spring" effect is desired. Upon reset, the servo will use the value stored in memory, based on the last configuration command.
310 +Ex:
331 331  
332 -Ex: #5QR<cr>
312 +{Description coming soon}
333 333  
334 -Queries the value being used.
314 +__15. Angular Deceleration (**AD**)__
335 335  
336 -Ex: #5CR<cr>
316 +{More information coming soon}
337 337  
338 -Writes the desired rigidity value to memory.
318 +Ex:
339 339  
340 -__15. N/A (removed)__
320 +{Description coming soon}
341 341  
342 -This command has been removed.
322 +Query Angular Acceleration (**QAD**)
343 343  
324 +Ex:
325 +
326 +{Description coming soon}
327 +
328 +Configure Angular Acceleration (**CAD**)
329 +
330 +Ex:
331 +
332 +{Description coming soon}
333 +
344 344  __16. RGB LED (**LED**)__
345 345  
346 346  Ex: #5LED3<cr>
... ... @@ -505,8 +505,6 @@
505 505  
506 506  Since it it not common to have to restore all configurations, a confirmation command is needed after a firmware command is sent. Should any command other than CONFIRM be received by the servo after the firmware command has been received, it will leave the firmware action.
507 507  
508 -Note that after the CONFIRM command is sent, the servo will automatically perform a RESET.
509 -
510 510  **__UPDATE __**__& **CONFIRM**__
511 511  
512 512  Ex: #5UPDATE<cr>
... ... @@ -517,8 +517,6 @@
517 517  
518 518  Since it it not common to have to update firmware, a confirmation command is needed after an UPDATE command is sent. Should any command other than CONFIRM be received by the servo after the firmware command has been received, it will leave the firmware action.
519 519  
520 -Note that after the CONFIRM command is sent, the servo will automatically perform a RESET.
521 -
522 522  === Virtual Angular Position ===
523 523  
524 524  {In progress}
Copyright RobotShop 2018