Changes for page LSS Communication Protocol
Last modified by Eric Nantel on 2025/06/06 07:47
Change comment: Upload new image "LSS-servo-default.jpg", version 1.1
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 1 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -99,22 +99,20 @@ 99 99 | 5|**M**ove in **D**egrees (relative)| MD| | | | ✓| tenths of degrees (ex 325 = 32.5 degrees; 91 = 9.1 degrees)| 100 100 | 6|**O**rigin Offset| O| QO| CO| ✓| ✓| tenths of degrees (ex 325 = 32.5 degrees; 91 = 9.1 degrees)| 101 101 | 7|**A**ngular **R**ange| AR| QAR| CAR| ✓| ✓| tenths of degrees (ex 325 = 32.5 degrees; 91 = 9.1 degrees)| 102 -| 8|Position in **P**ulse| P| QP| | | ✓| microseconds|((( 103 -See details below. 104 -))) 102 +| 8|Position in **P**ulse| P| QP| | | ✓| microseconds| 105 105 | 9|Position in **D**egrees| D| QD| | | ✓| tenths of degrees (ex 325 = 32.5 degrees; 91 = 9.1 degrees)| 106 106 | 10|**W**heel mode in **D**egrees| WD| QWD| | | ✓| tenths of degrees per second (ex 248 = 24.8 degrees per second)| 107 107 | 11|**W**heel mode in **R**PM| WR| QWR| | | ✓| rpm| 108 108 | 12|**S**peed in **D**egrees| SD| QSD| CSD| ✓| ✓| tenths of degrees per second (ex 248 = 24.8 degrees per second)| 109 109 | 13|**S**peed in **R**PM| SR| QSR| CSR| ✓| ✓| rpm| 110 -| 14|** R**igidity|R| QR| CR| ✓| ✓|none|111 -| 15| //N/A(removed)//| | | | | | |108 +| 14|**A**ngular **A**cceleration| AA| QAA| CAA| ✓| ✓| tenths of degrees per second squared| 109 +| 15|**A**ngular **D**eceleration| AD| QAD| CAD| ✓| ✓| tenths of degrees per second squared| 112 112 | 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 113 -| 17|**ID** #| ID| QID| CID| | ✓| none (integer from 0 to 25 0)|Note:ID 254 is a "broadcast" which all servos respond to.111 +| 17|**ID** #| ID| QID| CID| | ✓| none (integer from 0 to 254)| 114 114 | 18|**B**aud rate| B| QB| CB| | ✓| none (integer)| 115 115 | 19|**G**yre direction (**G**)| G| QG| CG| ✓| ✓| none | Gyre / rotation direction where 1= CW (clockwise) -1 = CCW (counter-clockwise) 116 -| 20|**F**irst Position (**P**ulse)| | QFP|CFP | ✓| ✓| none | 117 -| 21|**F**irst Position (**D**egrees)| | QFD|CFD| ✓| ✓| none | 114 +| 20|**F**irst Position (**P**ulse)| | QFP|CFP | ✓| ✓| none |\\ 115 +| 21|**F**irst Position (**D**egrees)| | QFD|CFD| ✓| ✓| none |\\ 118 118 | 22|**T**arget (**D**egree) **P**osition| | QDT| | | ✓| tenths of degrees (ex 325 = 32.5 degrees; 91 = 9.1 degrees)| 119 119 | 23|**M**odel| | QM| | | | none (integer)| 120 120 | 24|Serial **N**umber| | QN| | | | none (integer)| ... ... @@ -123,8 +123,8 @@ 123 123 | 27|**V**oltage| | QV| | | ✓| tenths of volt (ex 113 = 11.3V; 92 = 9.2V)| 124 124 | 28|**T**emperature| | QT| | | ✓| degrees Celsius| 125 125 | 29|**C**urrent| | QC| | | ✓| tenths of Amps (ex 2 = 0.2A)| 126 -| 127 -| 124 +|| | | | | || | 125 +|| | | | | | | | 128 128 129 129 = Details = 130 130 ... ... @@ -210,14 +210,13 @@ 210 210 211 211 Example: #5P2334<cr> 212 212 213 -The position in PWM pulses was retained in order to be backward compatible with the SSC-32 / 32U protocol. This relates the desired angle with an RC standard PWM pulse and is further explained in the SSC-32 and SSC-32U manuals found on Lynxmotion.com. Without any modifications to configuration considered, and a ±90.0 degrees standard range where 1500 microseconds is centered, a pulse of 2334 would set the servo to 165.1 degrees . Valid values for P are [500, 2500]. Values outside this range are corrected to end points.211 +The position in PWM pulses was retained in order to be backward compatible with the SSC-32 / 32U protocol. This relates the desired angle with an RC standard PWM pulse and is further explained in the SSC-32 and SSC-32U manuals found on Lynxmotion.com. Without any modifications to configuration considered, and a ±90.0 degrees standard range where 1500 microseconds is centered, a pulse of 2334 would set the servo to 165.1 degrees 214 214 215 215 Query Position in Pulse (**QP**) 216 216 217 217 Example: #5QP<cr> might return *5QP 218 218 219 -This command queries the current angular position in PWM "units". The user must take into consideration that the response includes any angular range and origin configurations in order to determine the actual angle. 220 -Valid values for QP are {-500, [500, 2500], -2500}. Values outside the [500, 2500] range are given a negative corresponding end point value to indicate they are out of bounds. 217 +This command queries the current angular position in PWM "units". The user must take into consideration that the response includes any angular range and origin configurations in order to determine the actual angle. 221 221 222 222 __9. Position in Degrees (**D**)__ 223 223 ... ... @@ -291,38 +291,46 @@ 291 291 292 292 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. 293 293 294 -__14. Rigidity(R)__291 +__14. Angular Acceleration (**AA**)__ 295 295 296 - The servo'srigidity can bethought of as (though notidentical to) a damped spring in which the rigidity value affects the stiffness and embodies how much, andhow quickly the servotriedkeep the requested positionagainst changes.293 +{More information coming soon} 297 297 298 - A positive value of "rigidity":295 +Ex: 299 299 300 -* The more torque will be applied to try to keep the desired position against external input / changes 301 -* The faster the motor will reach its intended travel speed and the motor will decelerate faster and nearer to its target position 297 +{Description coming soon} 302 302 303 - Anegativevalueon the otherhand:299 +Query Angular Acceleration (**QAA**) 304 304 305 -* Causes a slower acceleration to the travel speed, and a slower deceleration 306 -* Allows the target position to deviate more from its position before additional torque is applied to bring it back 301 +Ex: 307 307 308 - Thedefault value iszeroandthe effect becomes extreme by -4, +4. There are no units, only integersbetween -4 to 4. Greater valuesproduce increasingly erratic behavior.303 +{Description coming soon} 309 309 310 - Ex:#5R-2<cr>305 +Configure Angular Acceleration (**CAA**) 311 311 312 - Thisreduces 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.307 +Ex: 313 313 314 - Ex: #5QR<cr>309 +{Description coming soon} 315 315 316 - Queriesthevaluebeingused.311 +__15. Angular Deceleration (**AD**)__ 317 317 318 - Ex:#5CR<cr>313 +{More information coming soon} 319 319 320 - Writesthe desired rigidity value to memory.315 +Ex: 321 321 322 - __15. N/A (removed)__317 +{Description coming soon} 323 323 324 - Thiscommand hasbeenremoved.319 +Query Angular Acceleration (**QAD**) 325 325 321 +Ex: 322 + 323 +{Description coming soon} 324 + 325 +Configure Angular Acceleration (**CAD**) 326 + 327 +Ex: 328 + 329 +{Description coming soon} 330 + 326 326 __16. RGB LED (**LED**)__ 327 327 328 328 Ex: #5LED3<cr> ... ... @@ -329,7 +329,7 @@ 329 329 330 330 This action sets the servo's RGB LED color for that session.The LED can be used for aesthetics, or (based on user code) to provide visual status updates. Using timing can create patterns. 331 331 332 -0=OFF 1=RED 2=GREEN 3= BLUE 4=YELLOW 5=CYAN 6= 7=MAGENTA, 8=WHITE 337 +0=OFF 1=RED 2=GREEN 3= BLUE 4=YELLOW 5=CYAN 6= 7=MAGENTA, 8=WHITE 333 333 334 334 Query LED Color (**QLED**) 335 335 ... ... @@ -477,30 +477,23 @@ 477 477 478 478 This command does a "soft reset" (no power cycle required) and reverts all commands to those stored in EEPROM (i.e. configuration commands). 479 479 480 -**__DEFAULT __& **CONFIRM**__485 +**__DEFAULT__** 481 481 482 482 Ex: #5DEFAULT<cr> 483 483 484 -This command sets in motion the resetall values to the default values included with the version of the firmware installed on that servo.The servo then waits for the CONFIRM command. Any other command received will cause the servo to exit the DEFAULT function.489 +This command sets all values to the default values included with the version of the firmware installed on that servo. 485 485 486 - EX: #5DEFAULT<cr>followedby #5CONFIRM<cr>491 +__**FIRMWARE** & **CONFIRM**__ 487 487 488 - Sinceit 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 CONFIRMbe received by the servo after the firmware command has been received, it will leave the firmware action.493 +Ex: #5FIRMWARE<cr> 489 489 490 - Note that after theCONFIRM commandissent,theservo willautomaticallyperformaRESET.495 +This command clears all user-input values in EEPROM and reverts back to factory defaults for the firmware installed. It does not overwrite any firmware updates. To revert to an older firmware version, please refer to the LSS - Firmware page. The firmware command alone does nothing other than have the servo wait for a confirmation. 491 491 492 - **__UPDATE__**__&**CONFIRM**__497 +EX: #5FIRMWARE<cr> followed by #5CONFIRM<cr> 493 493 494 - Ex:#5UPDATE<cr>499 +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. 495 495 496 -This command sets in motion the equivalent of a long button press when the servo is not powered in order to enter firmware update mode. This is useful should the button be broken or inaccessible. The servo then waits for the CONFIRM command. Any other command received will cause the servo to exit the UPDATE function. 497 497 498 -EX: #5UPDATE<cr> followed by #5CONFIRM<cr> 499 - 500 -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. 501 - 502 -Note that after the CONFIRM command is sent, the servo will automatically perform a RESET. 503 - 504 504 === Virtual Angular Position === 505 505 506 506 {In progress}
- LSS-servo-default (1).jpg
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +xwiki:XWiki.CBenson - Size
-
... ... @@ -1,0 +1,1 @@ 1 +-1 bytes - Content