Changes for page LSS Communication Protocol

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

From version < 8.1 >

edited by Coleman Benson
on 2018/03/28 13:25

To version < 64.19 >

edited by RB1
on 2018/11/19 09:32

< >

Change comment: There is no comment for this version

Summary

Page properties (4 modified, 0 added, 0 removed)

Details

Page properties

Parent

@@ -1,1
          +1,1 @@
--Main.WebHome
++lynxmotion:LSS - Overview (DEV).WebHome

Author

@@ -1,1
          +1,1 @@
--xwiki:XWiki.CBenson
++xwiki:XWiki.RB1

Tags

...	...	@@ -1,0 +1,1 @@
	1	+LSS\|communication\|protocol\|programming\|firmware\|control

Content

@@ -1,6
          +1,10 @@
++{{toc depth="3"/}}
++
++= Protocol concepts =
++
  The Lynxmotion Smart Servo (LSS) protocol was created in order to be as simple and straightforward as possible from a user perspective, while at the same time trying to stay compact and robust yet highly versatile. Almost everything one might expect to be able to configure for a smart servo motor is available.
--=== Session ===
++== Session ==
  A "session" is defined as the time between when the servo is powered ON to when it is powered OFF or reset.
@@ -39,9
          +39,27 @@
  Results in the servo rotating from the current angular position to a pulse position of 1456 in 1263 milliseconds.
--Modified commands are command specific.
++Action modifiers can only be used with certain commands.
  )))
++== Configuration Commands ==
++
++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:LSS - Overview (DEV).LSS - RC PWM.WebHome]].
++
++1. Start with a number sign # (U+0023)
++1. Servo ID number as an integer
++1. Configuration command (two to three letters, no spaces, capital or lower case)
++1. Configuration value in the correct units with no decimal
++1. End with a control / carriage return '<cr>'
++
++Ex: #5CO-50<cr>
++
++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.
++
++Configuration commands are not cumulative, in that if two configurations are sent at any time, only the last configuration is used and stored.
++
++*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.
++
  == Query Commands ==
  Query commands are sent serially to the servo's Rx pin and must be set in the following format:
@@ -69,26
          +69,46 @@
  )))
  Indicates that servo #5 is currently at 144.3 degrees.
--)))
--== Configuration Commands ==
++**Session vs Configuration Query**
--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]].
++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.
--1. Start with a number sign # (U+0023)
--1. Servo ID number as an integer
--1. Configuration command (two to three letters, no spaces, capital or lower case)
--1. Configuration value in the correct units with no decimal
--1. End with a control / carriage return '<cr>'
++In order to query the value in EEPROM, add a '1' to the query command.
--Ex: #5CO-50<cr>
++Ex: #5CSR20<cr> sets the maximum speed for servo #5 to 20rpm upon RESET (explained below).
--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.
++After RESET: #5SR4<cr> sets the session's speed to 4rpm.
--Configuration commands are not cumulative, in that if two configurations are sent at any time, only the last configuration is used and stored.
++#5QSR<cr> would return *5QSR4<cr> which represents the value for that session.
--*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.
++#5QSR1<cr> would return *5QSR20<cr> which represents the value in EEPROM
++=== Virtual Angular Position ===
++
++{In progress}
++
++A "virtual position" is one which allows for multiple rotations of the output horn, moving the center position and more. The "absolute position" would be the angle of the output shaft with respect to 360.0 degrees.
++
++[[image:LSS-servo-positions.jpg]]
++
++Example: Gyre direction / rotation is positive (clockwise), and origin offset has not been modified. Each square represents 30 degrees.
++
++#1D-300<cr> The servo is sent a command to move to -30.0 degrees (green arrow)
++
++#1D2100<cr> This second position command is sent to the servo, which moves it to 210.0 degrees (orange arrow)
++
++#1D-4200<cr> This next command rotates the servo counterclockwise to a position of -420 degrees (red arrow), which means one full rotation of 360 degrees,  stopping at an absolute position of 60.0 degrees (420.0-360.0), with a virtual position of -420.0 degrees.
++
++Although the final physical position would be the same as if the servo were commanded to move to -60.0 degrees, the servo is in fact at -420.0 degrees.
++
++#1D4800<cr> This new command is sent which would then cause the servo to rotate from -420.0 degrees to 480.0 degrees (blue arrow), which would be a total of 900 degrees of clockwise rotation, or 2.5 complete rotations.
++
++#1D3300<cr> would cause the servo to rotate from 480.0 degrees to 330.0 degrees (yellow arrow).
++
++If / once the servo loses power or is power cycled, it also loses the virtual position associated with that session. For example, if the virtual position was 480.0 degrees before power is cycled, upon power up the servo's position will be read as +120.0 degrees from zero (assuming center position has not been modified).
++)))
++
  = Command List =
  |= #|=Description|= Action|= Query|= Config|= RC|= Serial|= Units|= Notes
@@ -99,64
          +99,77 @@
  | 5|**M**ove in **D**egrees (relative)| MD| | | |  ✓| tenths of degrees (ex 325 = 32.5 degrees; 91 = 9.1 degrees)|
  | 6|**O**rigin Offset| O| QO| CO| ✓|  ✓| tenths of degrees (ex 325 = 32.5 degrees; 91 = 9.1 degrees)|
  | 7|**A**ngular **R**ange| AR| QAR| CAR| ✓|  ✓| tenths of degrees (ex 325 = 32.5 degrees; 91 = 9.1 degrees)|
--| 8|Position in **P**ulse| P| QP| | | ✓| microseconds|
++| 8|Position in **P**ulse| P| QP| | | ✓| microseconds|(((
++See details below
++)))
  | 9|Position in **D**egrees| D| QD| | | ✓| tenths of degrees (ex 325 = 32.5 degrees; 91 = 9.1 degrees)|
  | 10|**W**heel mode in **D**egrees| WD| QWD| | | ✓| tenths of degrees per second (ex 248 = 24.8 degrees per second)|
  | 11|**W**heel mode in **R**PM| WR| QWR| | | ✓| rpm|
--| 12|**S**peed in **D**egrees| SD| QSD| CSD| ✓| ✓| tenths of degrees per second (ex 248 = 24.8 degrees per second)|
--| 13|**S**peed in **R**PM| SR| QSR| CSR| ✓| ✓| rpm|
--| 14|**A**ngular **A**cceleration| AA| QAA| CAA| ✓| ✓| tenths of degrees per second squared|
--| 15|**A**ngular **D**eceleration| AD| QAD| CAD| ✓| ✓| tenths of degrees per second squared|
--| 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
--| 17|**ID** #| ID| QID| CID| | ✓| none (integer from 0 to 254)|
++| 12|Max **S**peed in **D**egrees| SD| QSD| CSD| ✓| ✓| tenths of degrees per second (ex 248 = 24.8 degrees per second)|QSD: Add modifier "2" for instantaneous speed
++| 13|Max **S**peed in **R**PM| SR| QSR| CSR| ✓| ✓| rpm|QSR: Add modifier "2" for instantaneous speed
++| 14|**A**ngular **S**tiffness| AS| QAS| CAS| ✓| ✓|none|-4 to +4, but suggested values are between 0 to +4
++| 15|**A**ngular **H**olding Stiffness|AH|QAH|CAH| | ✓|none|-10 to +10, with default as 0.
++|15b|**A**ngular **A**cceleration|AA|QAA|CAA| | ✓|degrees per second squared|Increments of 10 degrees per second squared
++|15c|**A**ngular **D**eceleration|AD|QAD|CAD| | ✓|degrees per second squared|Increments of 10 degrees per second squared
++|15d|**M**otion **C**ontrol|MC|QMC| | | ✓|none|MC0 to disable motion control, MC1 to enable. Session specific
++| 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=MAGENTA, 7=WHITE
++| 17|**ID** #| | QID| CID| | ✓| none (integer from 0 to 250)|Note: ID 254 is a "broadcast" which all servos respond to
  | 18|**B**aud rate| B| QB| CB| | ✓| none (integer)|
  | 19|**G**yre direction (**G**)| G| QG| CG| ✓| ✓| none | Gyre / rotation direction where 1= CW (clockwise) -1 = CCW (counter-clockwise)
--| 20|**F**irst Position (**P**ulse)| | QFP|CFP | ✓| ✓| none |\\
--| 21|**F**irst Position (**D**egrees)| | QFD|CFD| ✓| ✓| none |\\
++| 20|**F**irst Position (**P**ulse)| | QFP|CFP | ✓| ✓| none |
++| 21|**F**irst Position (**D**egrees)| | QFD|CFD| ✓| ✓| none |
  | 22|**T**arget (**D**egree) **P**osition| | QDT| | | ✓| tenths of degrees (ex 325 = 32.5 degrees; 91 = 9.1 degrees)|
--| 23|**M**odel| | QM| | | | none (integer)|
++| 23|**M**odel **String**| | QMS| | | | none (string)| Recommended to determine the model|
++| 23b|**M**odel| | QM| | | | none (integer)| Returns a raw value representing the three model inputs (36 bit)|
  | 24|Serial **N**umber| | QN| | | | none (integer)|
  | 25|**F**irmware version| | QF| | | | none (integer)|
--| 26|**Q**uery (general status)| | Q| | | ✓| none (integer from 1 to 8)|
--| 27|**V**oltage| | QV| | | ✓| tenths of volt (ex 113 = 11.3V; 92 = 9.2V)|
--| 28|**T**emperature| | QT| | | ✓| degrees Celsius|
--| 29|**C**urrent| | QC| | | ✓| tenths of Amps (ex 2 = 0.2A)|
--|| | | | | || |
--|| | | | | | | |
++| 26|**Q**uery (general status)| | Q| | | ✓| none (integer from 1 to 8)| See command description for details
++| 27|**V**oltage| | QV| | | ✓| millivolts (ex 5936 = 5936mV = 5.936V)|
++| 28|**T**emperature| | QT| | | ✓| tenths of degrees Celsius|Max temp before error: 85°C (servo goes limp)
++| 29|**C**urrent| | QC| | | ✓| milliamps (ex 200 = 0.2A)|
++| 30|**RC** Mode| | |CRC| |✓|none|(((
++CRC: Add modifier "1" for RC-position mode.
++CRC: Add modifier "2" for RC-wheel mode.
++Any other value for the modifier results in staying in smart mode.
++Puts the servo into RC mode. To revert to smart mode, use the button menu.
++)))
++|31|**RESET**| | | | | ✓|none|Soft reset. See command for details.
++|32|**DEFAULT**| | | | |✓|none|Revert to firmware default values. See command for details
++|33|**UPDATE**| | | | |✓|none|Update firmware. See command for details.
--= Details =
++== Details ==
--__1. Limp (**L**)__
++====== __1. Limp (**L**)__ ======
  Example: #5L<cr>
  This action causes the servo to go "limp". The microcontroller will still be powered, but the motor will not. As an emergency safety feature, should the robot not be doing what it is supposed to or risks damage, use the broadcast ID to set all servos limp #254L<cr>.
--__2. Halt & Hold (**H**)__
++====== __2. Halt & Hold (**H**)__ ======
  Example: #5H<cr>
  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 position.
--__3. Timed move (**T**)__
++====== __3. Timed move (**T**)__ ======
  Example: #5P1500T2500<cr>
  Timed move can be used only as a modifier for a position (P) action. The units are in milliseconds, so a timed move of 2500 milliseconds would cause the servo to rotate from its current position to the desired position in 2.5 seconds. This command is in place to ensure backwards compatibility with the SSC-32 / 32U protocol.
--__4. Speed (**S**)__
++====== __4. Speed (**S**)__ ======
  Example: #5P1500S750<cr>
  This command is a modifier only for a position (P) action and determines the speed of the move in microseconds per second. A speed of 750 microseconds would cause the servo to rotate from its current position to the desired position at a speed of 750 microseconds per second. This command is in place to ensure backwards compatibility with the SSC-32 / 32U protocol.
--__5. (Relative) Move in Degrees (**MD**)__
++====== __5. (Relative) Move in Degrees (**MD**)__ ======
  Example: #5MD123<cr>
  The relative move command causes the servo to read its current position and move the specified number of tenths of degrees in the corresponding position. For example if the servo is set to rotate CW (default) and an MD command of 123 is sent to the servo, it will cause the servo to rotate clockwise by 12.3 degrees. Negative commands would cause the servo to rotate in the opposite configured direction.
--__6. Origin Offset Action (**O**)__
++====== __6. Origin Offset Action (**O**)__ ======
  Example: #5O2400<cr>
@@ -180,7
          +180,7 @@
  This command allows you to change the origin of the servo in relation to the factory zero position in EEPROM. The setting will be saved upon servo reset / power cycle. Origin offset configuration commands are not cumulative and always relate to factory zero. The new origin is also used in RC mode.
--__7. Angular Range (**AR**)__
++====== __7. Angular Range (**AR**)__ ======
  Example: #5AR1800<cr>
@@ -204,19
          +204,20 @@
  This command allows you to change the total angular range of the servo in tenths of degrees in EEPROM. The setting will be saved upon servo reset / power cycle.
--__8. Position in Pulse (**P**)__
++====== __8. Position in Pulse (**P**)__ ======
  Example: #5P2334<cr>
--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
++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.
  Query Position in Pulse (**QP**)
--Example: #5QP<cr> might return *5QP
++Example: #5QP<cr> might return *5QP2334
--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.
++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.
++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 (note that if the servo is physically located at one of the endpoints, it may return a negative number if it is a fraction of a degree beyond the position).
--__9. Position in Degrees (**D**)__
++====== __9. Position in Degrees (**D**)__ ======
  Example: #5PD1456<cr>
@@ -226,10
          +226,12 @@
  Query Position in Degrees (**QD**)
--Example: #5QD<cr> might return *5QD0<cr>
++Example: #5QD<cr> might return *5QD132<cr>
--__10. Wheel Mode in Degrees (**WD**)__
++This means the servo is located at 13.2 degrees.
++====== __10. Wheel Mode in Degrees (**WD**)__ ======
++
  Ex: #5WD900<cr>
  This command sets the servo to wheel mode where it will rotate in the desired direction at the selected speed. The example above would have the servo rotate at 90.0 degrees per second clockwise (assuming factory default configurations).
@@ -240,7
          +240,7 @@
  The servo replies with the angular speed in tenths of degrees per second. A negative sign would indicate the opposite direction (for factory default a negative value would be counter clockwise).
--__11. Wheel Mode in RPM (**WR**)__
++====== __11. Wheel Mode in RPM (**WR**)__ ======
  Ex: #5WR40<cr>
@@ -252,7
          +252,7 @@
  The servo replies with the angular speed in rpm. A negative sign would indicate the opposite direction (for factory default a negative value would be counter clockwise).
--__12. Speed in Degrees (**SD**)__
++====== __12. Speed in Degrees (**SD**)__ ======
  Ex: #5SD1800<cr>
@@ -262,8
          +262,15 @@
  Ex: #5QSD<cr> might return *5QSD1800<cr>
--Note that the QSD query will return the current servo speed. Querying the last maximum speed value set using SD or CSD is not possible.
++By default QSD will return the current session value, which is set to the value of CSD as reset/power cycle and changed whenever a SD/SR command is processed.
++If #5QSD1<cr> is sent, the configured maximum speed (CSD value) will be returned instead. You can also query the current speed using "2" and the current target travel speed using "3". See the table below for an example:
++|**Command sent**|**Returned value (1/10 °)**
++|ex: #5QSD<cr>|Session value for maximum speed (set by latest SD/SR command)
++|ex: #5QSD1<cr>|Configured maximum speed  (set by CSD/CSR)
++|ex: #5QSD2<cr>|Instantaneous speed (same as QWD)
++|ex: #5QSD3<cr>|Target travel speed
++
  Configure Speed in Degrees (**CSD**)
  Ex: #5CSD1800<cr>
@@ -270,7
          +270,7 @@
  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 180.0 degrees per second. When the servo is powered on (or after a reset), the CSD value is used. Note that CSD and CSR (described below) 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.
--__13. Speed in RPM (**SR**)__
++====== __13. Speed in RPM (**SR**)__ ======
  Ex: #5SD45<cr>
@@ -280,61
          +280,88 @@
  Ex: #5QSR<cr> might return *5QSR45<cr>
--Note that the QSD query will return the current servo speed. Querying the last maximum speed value set using SR or CSR is not possible.
++By default QSR will return the current session value, which is set to the value of CSR as reset/power cycle and changed whenever a SD/SR command is processed.
++If #5QSR1<cr> is sent, the configured maximum speed (CSR value) will be returned instead. You can also query the current speed using "2" and the current target travel speed using "3". See the table below for an example:
--Configure Speed in Degrees (**CSR**)
++|**Command sent**|**Returned value (1/10 °)**
++|ex: #5QSR<cr>|Session value for maximum speed (set by latest SD/SR command)
++|ex: #5QSR1<cr>|Configured maximum speed  (set by CSD/CSR)
++|ex: #5QSR2<cr>|Instantaneous speed (same as QWR)
++|ex: #5QSR3<cr>|Target travel speed
++Configure Speed in RPM (**CSR**)
++
  Ex: #5CSR45<cr>
--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.
++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) is what the servo uses for that session.
--__14. Angular Acceleration (**AA**)__
++====== __14. Angular Stiffness (**AS**)__ ======
--{More information coming soon}
++The servo's rigidity / angular stiffness can be thought of as (though not identical to) a damped spring in which the value affects the stiffness and embodies how much, and how quickly the servo tried keep the requested position against changes.
--Ex:
++A positive value of "angular stiffness":
--{Description coming soon}
++* The more torque will be applied to try to keep the desired position against external input / changes
++* The faster the motor will reach its intended travel speed and the motor will decelerate faster and nearer to its target position
--Query Angular Acceleration (**QAA**)
++A negative value on the other hand:
--Ex:
++* Causes a slower acceleration to the travel speed, and a slower deceleration
++* Allows the target position to deviate more from its position before additional torque is applied to bring it back
--{Description coming soon}
++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.
--Configure Angular Acceleration (**CAA**)
++Ex: #5AS-2<cr>
--Ex:
++This reduces the angular stiffness 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.
--{Description coming soon}
++Ex: #5QAS<cr>
--__15. Angular Deceleration (**AD**)__
++Queries the value being used.
--{More information coming soon}
++Ex: #5CAS<cr>
--Ex:
++Writes the desired angular stiffness value to memory.
--{Description coming soon}
++====== __15. Angular Hold Stiffness (**AH**)__ ======
--Query Angular Acceleration (**QAD**)
++The angular holding stiffness determines the servo's ability to hold a desired position under load. Values can be from -10 to 10, with the default being 0. Note that negative values mean the final position can be easily deflected.
--Ex:
++Ex: #5AH3<cr>
--{Description coming soon}
++This sets the holding stiffness for servo #5 to 3 for that session.
--Configure Angular Acceleration (**CAD**)
++Query Angular Hold Stiffness (**QAH**)
--Ex:
++Ex: #5QAH<cr> might return *5QAH3<cr>
--{Description coming soon}
++This returns the servo's angular holding stiffness value.
--__16. RGB LED (**LED**)__
++Configure Angular Hold Stiffness (**CAH**)
++Ex: #5CAH2<cr>
++
++This writes the angular holding stiffness of servo #5 to 2 to EEPROM
++
++====== __15b: Angular Acceleration (**AA**)__ ======
++
++{More details to come}
++
++====== __15c: Angular Deceleration (**AD**)__ ======
++
++{More details to come}
++
++====== __15d: Motion Control (**MC**)__ ======
++
++{More details to come}
++
++====== __16. RGB LED (**LED**)__ ======
++
  Ex: #5LED3<cr>
  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.
--0=OFF 1=RED 2=GREEN 3= BLUE 4=YELLOW 5=CYAN 6= 7=MAGENTA, 8=WHITE
++0=OFF 1=RED 2=GREEN 3= BLUE 4=YELLOW 5=CYAN 6= 7=MAGENTA, 8=WHITE
  Query LED Color (**QLED**)
@@ -344,27
          +344,28 @@
  Configure LED Color (**CLED**)
--Configuring the LED color via the CLED command sets the startup color of the servo after a reset or power cycle.
++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.
--__17. Identification Number__
++====== __17. Identification Number__ ======
--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 1. 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.
++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.
  Query Identification (**QID**)
--EX: #QID<cr> might return *QID5<cr>
++EX: #254QID<cr> might return *QID5<cr>
--When using the query ID command, it is best to only have one servo connected and thus receive only one reply.
++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.
  Configure ID (**CID**)
--Ex: #CID5<cr>
++Ex: #4CID5<cr>
  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.
--__18. Baud Rate__
++====== __18. Baud Rate__ ======
--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. Standard / suggested baud rates are: 4800; 9600; 14400; 19200; 38400; 57600; 115200; 128000; 256000, 512000 bits per second. Servos are shipped with a baud rate set to 9600. The baud rates are currently restricted to those above
++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.
++\*: 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.
  Query Baud Rate (**QB**)
@@ -378,7
          +378,7 @@
  Sending this command will change the baud rate associated with servo ID 5 to 9600 bits per second.
--__19. Gyre Rotation Direction__
++====== __19. Gyre Rotation Direction__ ======
  "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).
@@ -396,25
          +396,25 @@
  This changes the gyre direction as described above and also writes to EEPROM.
--__20. First / Initial Position (pulse)__
++====== __20. First / Initial Position (pulse)__ ======
--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 serial mode only.
++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.
  Query First Position in Pulses (**QFP**)
  Ex: #5QFP<cr> might return *5QFP1550<cr>
--The reply above indicates that servo with ID 5 has a first position pulse of 1550 microseconds.
++The reply above indicates that servo with ID 5 has a first position pulse of 1550 microseconds. If no first position has been set, servo will respond with DIS ("disabled").
--Configure First Position in Pulses (CFP)
++Configure First Position in Pulses (**CFP**)
  Ex: #5CP1550<cr>
--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.
++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).
--__21. First / Initial Position (Degrees)__
++====== __21. First / Initial Position (Degrees)__ ======
--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 serial mode only.
++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.
  Query First Position in Degrees (**QFD**)
@@ -426,95
          +426,111 @@
  Ex: #5CD64<cr>
--This configuration command means the servo, when set to serial 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.
++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.
--__22. Query Target Position in Degrees (**QDT**)__
++====== __22. Query Target Position in Degrees (**QDT**)__ ======
  Ex: #5QDT<cr> might return *5QDT6783<cr>
  The query target position command returns the target angle during and after an action which results in a rotation of the servo horn. In the example above, the servo is rotating to a virtual position of 678.3 degrees. Should the servo not have a target position or be in wheel mode, it will respond without a number (Ex: *5QDT<cr>).
--__23. Query Model (**QM**)__
++====== __23. Query Model String (**QMS**)__ ======
--Ex: #5QM<cr> might return *5QM11<cr>
++Ex: #5QMS<cr> might return *5QMSLSS-HS1cr>
--This reply means the servo model is 1.1, meaning high speed servo, first revision. 1=HS (high speed) 2=ST (standard) 3=HT (high torque)
++This reply means the servo model  is LSS-HS1, meaning a high speed servo, first revision.
--__24. Query Serial Number (**QN**)__
++====== __23b. Query Model (**QM**)__ ======
++Ex: #5QM<cr> might return *5QM68702699520cr>
++
++This reply means the servo model is 0xFFF000000 or 100, meaning a high speed servo, first revision.
++
++====== __24. Query Serial Number (**QN**)__ ======
++
  Ex: #5QN<cr> might return *5QN~_~_<cr>
  The number in the response is the servo's serial number which is set and cannot be changed.
--__25. Query Firmware (**QF**)__
++====== __25. Query Firmware (**QF**)__ ======
  Ex: #5QF<cr> might return *5QF11<cr>
  The integer in the reply represents the firmware version with one decimal, in this example being 1.1
--__26. Query Status (**Q**)__
++====== __26. Query Status (**Q**)__ ======
--Ex: #5Q<cr> might return *5Q_<cr>
++Ex: #5Q<cr> might return *5Q6<cr>, which indicates the motor is holding a position.
--{Description coming soon}
++|*Value returned|**Status**|**Detailed description**
++|ex: *5Q0<cr>|Unknown|LSS is unsure
++|ex: *5Q1<cr>|Limp|Motor driving circuit is not powered and horn can be moved freely
++|ex: *5Q2<cr>|Free moving|Motor driving circuit is not powered and horn can be moved freely
++|ex: *5Q3<cr>|Accelerating|Increasing speed from rest (or previous speeD) towards travel speed
++|ex: *5Q4<cr>|Traveling|Moving at a stable speed
++|ex: *5Q5<cr>|Deccelerating|Decreasing speed towards travel speed towards rest
++|ex: *5Q6<cr>|Holding|Keeping current position
++|ex: *5Q7<cr>|Stepping|Special low speed mode to maintain torque
++|ex: *5Q8<cr>|Outside limits|More details coming soon
++|ex: *5Q9<cr>|Stuck|Motor cannot perform request movement at current speed setting
++|ex: *5Q10<cr>|Blocked|Similar to stuck, but the motor is at maxiumum duty and still cannot move (i.e.: stalled)
--__27. Query Voltage (**QV**)__
++====== __27. Query Voltage (**QV**)__ ======
--Ex: #5QV<cr> might return *5QV112<cr>
++Ex: #5QV<cr> might return *5QV11200<cr>
  The number returned has one decimal, so in the case above, servo with ID 5 has an input voltage of 11.2V (perhaps a three cell LiPo battery).
--__28. Query Temperature (**QT**)__
++====== __28. Query Temperature (**QT**)__ ======
  Ex: #5QT<cr> might return *5QT564<cr>
  The units are in tenths of degrees Celcius, so in the example above, the servo's internal temperature is 56.4 degrees C. To convert from degrees Celcius to degrees Farenheit, multiply by 1.8 and add 32. Therefore 56.4C = 133.52F.
--__29. Query Current (QC)__
++====== __29. Query Current (**QC**)__ ======
  Ex: #5QC<cr> might return *5QC140<cr>
  The units are in milliamps, so in the example above, the servo is consuming 140mA, or 0.14A.
--__**RESET**__
++====== __30. RC Mode (**CRC**)__ ======
--Ex: #5RESET<cr> or #5RS<cr>
++This command puts the servo into RC mode (position or continuous), where it will only respond to RC pulses. Note that because this is the case, the servo will no longer accept serial commands. The servo can be placed back into smart mode by using the button menu.
--This command does a "soft reset" (no power cycle required) and reverts all commands to those stored in EEPROM (i.e. configuration commands).
++|**Command sent**|**Note**
++|ex: #5CRC<cr>|Stay in smart mode.
++|ex: #5CRC1<cr>|Change to RC position mode.
++|ex: #5CRC2<cr>|Change to RC continuous (wheel) mode.
++|ex: #5CRC*<cr>|Where * is any number or value. Stay in smart mode.
--**__DEFAULT__**
++EX: #5CRC<cr>
--Ex: #5DEFAULT<cr>
++====== __31. RESET__ ======
--This command sets all values to the default values included with the version of the firmware installed on that servo.
++Ex: #5RESET<cr> or #5RS<cr>
--__**FIRMWARE** & **CONFIRM**__
++This command does a "soft reset" (no power cycle required) and reverts all commands to those stored in EEPROM (i.e. configuration commands).
--Ex: #5FIRMWARE<cr>
++====== __32. DEFAULT & CONFIRM__ ======
--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.
++Ex: #5DEFAULT<cr>
--EX: #5FIRMWARE<cr> followed by #5CONFIRM<cr>
++This command sets in motion the reset all 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.
++EX: #5DEFAULT<cr> followed by #5CONFIRM<cr>
++
  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.
++Note that after the CONFIRM command is sent, the servo will automatically perform a RESET.
--=== Virtual Angular Position ===
++====== __33. UPDATE & CONFIRM__ ======
--{In progress}
++Ex: #5UPDATE<cr>
--A "virtual position" is one which allows for multiple rotations of the output horn, moving the center position and more. The "absolute position" would be the angle of the output shaft with respect to 360.0 degrees.
++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.
--[[image:LSS-servo-positions.jpg]]
++EX: #5UPDATE<cr> followed by #5CONFIRM<cr>
--Example: Gyre direction / rotation is positive (clockwise), and origin offset has not been modified.
++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.
--#1D-300<cr> The servo is commander to move to -30.0 degrees (green arrow)
--
--#1D2100<cr> This second position command is sent to the servo, which moves it to 210.0 degrees (orange arrow)
--
--#1D-4200<cr> The servo rotates counterclockwise to a position of -420 degrees (red arrow), which means one full rotation of 360 degrees and (420.0-360.0) stopping at an absolute position of 60.0 degrees, but virtual position of -420.0.
--
--Although the final position would be the same as if the servo were commanded to move to -60.0 degrees, it is in fact at -420.0 degrees.
--
--#1D4800<cr> This new command is sent which would then cause the servo to rotate from -420.0 degrees to 480.0 degrees, which would be a total of 900 degrees of clockwise rotation, or 2.5 complete rotations.
++Note that after the CONFIRM command is sent, the servo will automatically perform a RESET.

Changes for page LSS Communication Protocol

Summary

Details

Navigation

Recently Visited