Changes for page LSS Communication Protocol
Last modified by Eric Nantel on 2024/11/21 09:43
Change comment: There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -157,13 +157,13 @@ 157 157 SR overwrites SD / CSR overwrites CSD and vice-versa. 158 158 )))|(% style="text-align:center; width:113px" %)Max per servo 159 159 | 14|[[**LED** Color>>||anchor="H16.RGBLED28LED29"]]| LED| QLED| CLED|✓| ✓| ✓|none (integer from 0 to 8)|(% style="width:510px" %)0=Off (black); 1=Red 2=Green; 3=Blue; 4=Yellow; 5=Cyan; 6=Magenta; 7=White;|(% style="text-align:center; width:113px" %)7 160 -| 15|[[** G**yredirection (**G**)>>||anchor="H19.GyreRotationDirection"]]|G| QG| CG|✓|✓| ✓|none |(% style="width:510px" %)Gyre/rotationdirection:1= CW (clockwise)-1= CCW (counter-clockwise)|(% style="text-align:center; width:113px" %)1161 -| 16|[[** ID**#>>||anchor="H17.IdentificationNumber"]]| | QID| CID| | | ✓|none (integerfrom 0 to 250)|(% style="width:510px" %)Note:ID 254 is a "broadcast" which all servos respond to.|(% style="text-align:center; width:113px" %)0162 -| 17|[[** B**audrate>>||anchor="H18.BaudRate"]]| | QB| CB|(integer)|(% style="width:510px" %) |(% style="text-align:center; width:113px" %)9600163 -| 18|[[**F**irst Position (**P**ulse)>>||anchor="H20.First2InitialPosition28pulse29"]]| | QFP|CFP | X| ✓| ✓|none |(% style="width:510px" %)CFP overwrites CFD and vice-versa|(% style="text-align:center; width:113px" %)(((160 +| 15|[[**ID** #>>||anchor="H17.IdentificationNumber"]]| | QID| CID| | | ✓|none (integer from 0 to 250)|(% style="width:510px" %)Note: ID 254 is a "broadcast" which all servos respond to. |(% style="text-align:center; width:113px" %)0 161 +| 16|[[**B**aud rate>>||anchor="H18.BaudRate"]]| B| QB| CB| | | ✓|none (integer)|(% style="width:510px" %) |(% style="text-align:center; width:113px" %)9600 162 +| 17|[[**G**yre direction (**G**)>>||anchor="H19.GyreRotationDirection"]]| G| QG| CG|✓| ✓| ✓|none |(% style="width:510px" %)Gyre / rotation direction: 1= CW (clockwise) -1 = CCW (counter-clockwise)|(% style="text-align:center; width:113px" %)1 163 +| 18|[[**F**irst Position (**P**ulse)>>||anchor="H20.First2InitialPosition28pulse29"]]| | QFP|CFP | | ✓| ✓|none |(% style="width:510px" %)CFP overwrites CFD and vice-versa|(% style="text-align:center; width:113px" %)((( 164 164 Limp 165 165 ))) 166 -| 19|[[**F**irst Position (**D**eg)>>||anchor="H21.First2InitialPosition28Degrees29"]]| | QFD|CFD| X| ✓| ✓|none |(% style="width:510px" %)CFD overwrites CFP and vice-versa|(% style="text-align:center; width:113px" %)Limp166 +| 19|[[**F**irst Position (**D**eg)>>||anchor="H21.First2InitialPosition28Degrees29"]]| | QFD|CFD| | ✓| ✓|none |(% style="width:510px" %)CFD overwrites CFP and vice-versa|(% style="text-align:center; width:113px" %)Limp 167 167 | 20|[[**T**arget (**D**eg) **P**osition>>||anchor="H22.QueryTargetPositioninDegrees28QDT29"]]| | QDT| | | | ✓|tenths of degrees (ex 325 = 32.5 degrees)|(% style="width:510px" %) |(% style="text-align:center; width:113px" %) 168 168 | 21|[[**M**odel **S**tring>>||anchor="H23.QueryModelString28QMS29"]]| | QMS| | | | |none (string)|(% style="width:510px" %) Returns the type of servo (ST, HS, HT)|(% style="text-align:center; width:113px" %) 169 169 | 22|[[Serial **N**umber>>||anchor="H24.QuerySerialNumber28QN29"]]| | QN| | | | |none (integer)|(% style="width:510px" %) Returns the unique serial number for that servo|(% style="text-align:center; width:113px" %) ... ... @@ -208,7 +208,7 @@ 208 208 209 209 This action overrides whatever the servo might be doing at the time the command is received (accelerating, moving continuously etc.) and causes it to stop immediately and hold that angular position. 210 210 211 -====== __3. Timed move (**T**) modifier__ ======211 +====== __3. Timed move (**T**)__ ====== 212 212 213 213 Example: #5P1500T2500<cr> 214 214 ... ... @@ -216,7 +216,7 @@ 216 216 217 217 Note: If the calculated speed at which a servo must rotate for a timed move is greater than its maximum speed (which depends on voltage and load), then it will move at its maximum speed, and the time of the move may be longer than requested. 218 218 219 -====== __4. Speed (**S**) modifier__ ======219 +====== __4. Speed (**S**)__ ====== 220 220 221 221 Example: #5P1500S750<cr> 222 222 ... ... @@ -377,8 +377,10 @@ 377 377 378 378 Using the CSR 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 CSR 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) received is what the servo uses for that session. 379 379 380 -====== __14.LEDColor (**LED**)__======380 +====== ====== 381 381 382 +====== __16. RGB LED (**LED**)__ ====== 383 + 382 382 Ex: #5LED3<cr> 383 383 384 384 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. ... ... @@ -393,66 +393,65 @@ 393 393 394 394 Configure LED Color (**CLED**) 395 395 396 -Configuring the LED color via the CLED command sets the startup color of the servo after a reset or power cycle. Note that it also changes the session's LED color immediately as well. 398 +Configuring the LED color via the CLED command sets the startup color of the servo after a reset or power cycle. Note that it also changes the session's LED color immediately as well. 397 397 398 -====== __1 5.GyreRotation Direction(**G**)__ ======400 +====== __17. Identification Number__ ====== 399 399 400 - "Gyre"is definedasacircularcourse ormotion. The effect ofchangingthegyre directionisas ifyou were to usea mirrorimageofacircle.CW=1;CCW= -1. Thefactorydefaultis clockwise (CW).402 +A servo's identification number cannot be set "on the fly" and must be configured via the CID command described below. The factory default ID number for all servos is 0. Since smart servos are intended to be daisy chained, in order to respond differently from one another, the user must set different identification numbers. Servos with the same ID and baud rate will all receive and react to the same commands. 401 401 402 -Ex: #5G-1<cr> 403 - 404 -This command will cause servo #5's positions to be inverted, effectively causing the servo to rotate in the opposite direction given the same command. For example in a 2WD robot, servos are often physically installed back to back, therefore setting one of the servos to a negative gyration, the same wheel command (ex WR30) to both servos will cause the robot to move forward or backward rather than rotate. 405 - 406 -Query Gyre Direction (**QG**) 407 - 408 -Ex: #5QG<cr> might return *5QG-1<cr> 409 - 410 -The value returned above means the servo is in a counter-clockwise gyration. 411 - 412 -Configure Gyre (**CG**) 413 - 414 -Ex: #5CG-1<cr> 415 - 416 -This changes the gyre direction as described above and also writes to EEPROM. 417 - 418 -====== __16. Identification Number (**ID** #)__ ====== 419 - 420 -A servo's identification number cannot be set "on the fly" and must be configured via the CID command described below. The factory default ID number for all servos is 0. Since smart servos are intended to be daisy chained, in order to respond differently from one another, the user must set different identification numbers. Servos with the same ID and baud rate will all receive and react to the same commands (assuming same baud rate). 421 - 422 422 Query Identification (**QID**) 423 423 424 424 EX: #254QID<cr> might return *QID5<cr> 425 425 426 -When using the query ID command, it is best to only have one servo connected and thus receive only one reply .This isuseful when you are not sure of the servo's ID, but don't want to changeit. Using the broadcast command (ID 254)with only one servo will have that servo reply with its ID number (assuming the query is sent. Alternatively, pushing the button upon startup and temporarily setting the servo ID to 255 will still result in the servo responding with its "real" ID.408 +When using the query ID command, it is best to only have one servo connected and thus receive only one reply using the broadcast command (ID 254). Alternatively, pushing the button upon startup and temporarily setting the servo ID to 255 will still result in the servo responding with its "real" ID. 427 427 428 428 Configure ID (**CID**) 429 429 430 430 Ex: #4CID5<cr> 431 431 432 -Setting a servo's ID in EEPROM is done via the CID command. All servos connected to the same serial bus will be assigned that ID. In most situations each servo must be set a unique ID, which means each servo must be connected individually to the serial bus and receive a unique CID number. It is best to do this before the servos are added to an assembly. Numbered stickers are provided to distinguish each servo after their ID is set, though you are free to use whatever alternative method you like. The servo must be RESET or power cycled in order for the new ID to take effect.414 +Setting a servo's ID in EEPROM is done via the CID command. All servos connected to the same serial bus will be assigned that ID. In most situations each servo must be set a unique ID, which means each servo must be connected individually to the serial bus and receive a unique CID number. It is best to do this before the servos are added to an assembly. Numbered stickers are provided to distinguish each servo after their ID is set, though you are free to use whatever alternative method you like. 433 433 434 -====== __1 7. Baud Rate(B)__ ======416 +====== __18. Baud Rate__ ====== 435 435 436 -A servo's baud rate cannot be set "on the fly" and must be configured via the CB command described below. The factory default baud rate for all servos is 9600. Since smart servos are intended to be daisy chained, in order to respond to the same serial bus, all servos in a project should ideally be set to the same baud rate. Setting different baud rates will have the servos respond differently and may create issues. Available baud rates are: 9600 bps, 19200 bps, 38400 bps, 57600 bps, 115.2 kbps, 230.4 kbps, 250.0 kbps, 460.8 kbps, 500.0 kbps. Servos are shipped with a baud rate set to 9600. The baud rates are currently restricted to those above. 418 +A servo's baud rate cannot be set "on the fly" and must be configured via the CB command described below. The factory default baud rate for all servos is 9600. Since smart servos are intended to be daisy chained, in order to respond to the same serial bus, all servos in that project should ideally be set to the same baud rate. Setting different baud rates will have the servos respond differently and may create issues. Available baud rates are: 9.6 kbps, 19.2 kbps, 38.4 kbps, 57.6 kbps, 115.2 kbps, 230.4 kbps, 250.0 kbps, 460.8 kbps, 500.0 kbps, 750.0 kbps*, 921.6 kbps*. Servos are shipped with a baud rate set to 9600. The baud rates are currently restricted to those above. 419 +\*: Current tests reveal baud rates above 500 kbps are unstable and can cause timeouts. Please keep this in mind if using those / testing them out. 437 437 438 438 Query Baud Rate (**QB**) 439 439 440 440 Ex: #5QB<cr> might return *5QB9600<cr> 441 441 442 - Since the command to querymust be done at the servo's existingbaudrate, it cansimplybe usedto confirm the CB configuration commandwas correctly receivedbefore the servo is power cycledand the new baud rate takes effect.425 +Querying the baud rate is used simply to confirm the CB configuration command before the servo is power cycled. 443 443 444 444 Configure Baud Rate (**CB**) 445 445 446 -Important Note: the servo's current session retains the given baud rate and the new baud rate will only takeeffectwhen the servo is power cycled/ RESET.429 +Important Note: the servo's current session retains the given baud rate and the new baud rate will only be in place when the servo is power cycled. 447 447 448 448 Ex: #5CB9600<cr> 449 449 450 450 Sending this command will change the baud rate associated with servo ID 5 to 9600 bits per second. 451 451 452 -====== __1 8.FirstPosition(Pulse) (**FP**)__ ======435 +====== __19. Gyre Rotation Direction__ ====== 453 453 454 - In certain cases,a usermight want to havetheservomove toaspecificangleupon power up; werefertothis as "firstposition" (a.k.a."initial position").The factorydefaulthasno first positionvaluestoredinEEPROMandthereforeuponpowerup,theservoremainslimp until a position (orhold command) is assigned.FPandFD are differentinthatFPisusedforRC modeonly,whereas FDisused forsmart modeonly.437 +"Gyre" is defined as a circular course or motion. The effect of changing the gyre direction is as if you were to use a mirror image of a circle. CW = 1; CCW = -1. The factory default is clockwise (CW). 455 455 439 +{images showing before and after with AR and Origin offset} 440 + 441 +Query Gyre Direction (**QG**) 442 + 443 +Ex: #5QG<cr> might return *5QG-1<cr> 444 + 445 +The value returned above means the servo is in a counter-clockwise gyration. 446 + 447 +Configure Gyre (**CG**) 448 + 449 +Ex: #5CG-1<cr> 450 + 451 +This changes the gyre direction as described above and also writes to EEPROM. 452 + 453 +====== __20. First / Initial Position (pulse)__ ====== 454 + 455 +In certain cases, a user might want to have the servo move to a specific angle upon power up. We refer to this as "first position". The factory default has no first position value stored in EEPROM and therefore upon power up, the servo remains limp until a position (or hold command) is assigned. FP and FD are different in that FP is used for RC mode only, whereas FD is used for smart mode only. 456 + 456 456 Query First Position in Pulses (**QFP**) 457 457 458 458 Ex: #5QFP<cr> might return *5QFP1550<cr> ... ... @@ -463,11 +463,11 @@ 463 463 464 464 Ex: #5CP1550<cr> 465 465 466 -This configuration command means the servo, when set to RC mode, will immediately move to an angle equivalent to having received an RC pulse of 1550 microseconds upon power up. Sending a CFP command without a number (Ex. #5CFP<cr>) results in the servo remaining limp upon power up (i.e. disabled).467 +This configuration command means the servo, when set to RC mode, will immediately move to an angle equivalent to having received an RC pulse of 1550 microseconds upon power up. Sending a CFP command without a number results in the servo remaining limp upon power up (i.e. disabled). 467 467 468 -====== __1 9. First / Initial Position (Degrees)(**FD**)__ ======469 +====== __21. First / Initial Position (Degrees)__ ====== 469 469 470 -In certain cases, a user might want to have the servo move to a specific angle upon power up ; we refer to this as "first position"(a.k.a."initial position").The factory default has no first position value stored in EEPROM and therefore upon power up, the servo remains limp until a position (or hold command) is assigned. FP and FD are different in that FP is used for RC mode only, whereas FD is used for smart mode only.471 +In certain cases, a user might want to have the servo move to a specific angle upon power up. We refer to this as "first position". The factory default has no first position value stored in EEPROM and therefore upon power up, the servo remains limp until a position (or hold command) is assigned. FP and FD are different in that FP is used for RC mode only, whereas FD is used for smart mode only. 471 471 472 472 Query First Position in Degrees (**QFD**) 473 473 ... ... @@ -479,7 +479,7 @@ 479 479 480 480 Ex: #5CD64<cr> 481 481 482 -This configuration command means the servo, when set to smart mode, will immediately move to 6.4 degrees upon power up. Sending a CFD command without a number (Ex. #5CFD<cr>) results in the servo remaining limp upon power up.483 +This configuration command means the servo, when set to smart mode, will immediately move to 6.4 degrees upon power up. Sending a CFD command without a number results in the servo remaining limp upon power up. 483 483 484 484 ====== __22. Query Target Position in Degrees (**QDT**)__ ====== 485 485