Changes for page LSS Communication Protocol

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

From version < 94.1 >

edited by Coleman Benson
on 2019/02/01 12:00

To version < 213.1 >

edited by Eric Nantel
on 2024/11/21 09:18

< >

Change comment: There is no comment for this version

Summary

Page properties (4 modified, 0 added, 0 removed)
Attachments (0 modified, 2 added, 0 removed)
- LSS - LED Patterns.png
- LSS-Protocol-Backup-2020-05-01.zip
Objects (0 modified, 1 added, 3 removed)

Details

Page properties

Title

@@ -1,1
          +1,1 @@
--LSS - Communication Protocol
++LSS Communication Protocol

Parent

@@ -1,1
          +1,1 @@
--Lynxmotion Smart Servo (LSS).WebHome
++ses-v2.lynxmotion-smart-servo.WebHome

Author

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

Content

@@ -1,112
          +1,132 @@
  (% class="wikigeneratedid" id="HTableofContents" %)
--**Table of Contents**
++**Page Contents**
  {{toc depth="3"/}}
--= Serial Protocol Concept =
++= Serial Protocol =
--The custom Lynxmotion Smart Servo (LSS) serial protocol was created in order to be as simple and straightforward as possible from a user perspective ("human readable format"), while at the same time compact and robust yet highly versatile. The protocol was based on Lynxmotion's SSC-32 RC servo controller and almost everything one might expect to be able to configure for a smart servo motor is available.
++The Lynxmotion Smart Servo (LSS) serial protocol was created in order to be as simple and straightforward as possible from a user perspective ("human readable format"), while at the same time staying compact and robust yet highly versatile. The protocol was based on Lynxmotion's SSC-32 & SSC-32U RC servo controllers and almost everything one might expect to be able to configure for a smart servomotor is available.
--In order to have servos react differently when commands are sent to all servos in a serial bus, the first step a user should take is to assign a different ID number to each servo (explained below). Once this has been done, only the servo(s) which have been assigned to the ID sent as part of the command will follow that command. There is currently no CRC / checksum implemented as part of the protocol.
++In order to be able to control each servo individually with commands, the first step should be to assign a different ID number to each servo (see details on the Configure ID, or "CID" command [[here>>path:#HIdentificationNumber28ID29]]). Only the servo(s) which have been configured to a specific ID will act on a command sent to that ID. There is currently no CRC or checksum implemented as part of the protocol.
++|(% colspan="2" %)(((
  == Session ==
--
++)))
++|(% style="width:25px" %) |(((
  A "session" is defined as the time between when the servo is powered ON to when it is powered OFF or reset.
--== Action Commands ==
++**Note 1:** For a given session, the action related to a specific command overrides the stored value in EEPROM.
--Action commands tell the servo, within that session, to do something (i.e. "take an action"). The types of action commands which can be sent are described below, and they cannot be combined with other commands such as queries or configurations. Only one action command can be sent at a time. Action commands are session-specific, therefore once a servo is power cycled, it will not have any "memory" of previous actions or virtual positions (described below on this page). Action commands are sent serially to the servo's Rx pin and must be sent in the following format:
++**Note 2:** During the power-on / reset process the LSS cannot accept commands for a small amount of time (1.25 s).
--1. Start with a number sign # (U+0023)
--1. Servo ID number as an integer
--1. Action command (one to three letters, no spaces, capital or lower case)
--1. Action value in the correct units with no decimal
--1. End with a control / carriage return '<cr>'
++**Note 3:** You can ensure the LSS is ready by using a query command to check for response (ex: #[id]Q\r or #[id]QID\r described below). If the LSS is ready for commands (initialized) it will respond to the query. A timeout between 50-100 ms is recommended to compensate for drivers, OS and buffering delays.
++)))
--(((
--Ex: #5PD1443<cr>
++|(% colspan="2" %)(((
++== Action Commands ==
++)))
++|(% style="width:25px" %) |(((
++Action commands tell the servo, within that session, to do something (i.e. "take an action"). The types of action commands which can be sent are described below, and they cannot be combined with other commands such as queries or configurations. Only one action command can be sent at a time. Action commands are session-specific, therefore once a servo is power cycled, it will not have any "memory" of previous actions or [[virtual positions>>url:https://wiki.lynxmotion.com/info/wiki/lynxmotion/view/ses-v2/lynxmotion-smart-servo/lss-communication-protocol/#HVirtualAngularPosition]] (described below). Action commands are sent serially to the servo's Rx pin and must be sent in the following format:
--This sends a serial command to all servo's Rx pins which are connected to the bus and only servo(s) with ID #5 will move to a position in tenths of degrees ("PD") of 144.3 degrees. Any servo on the bus which does not have ID 5 will take no action when receiving this command.
++1. Start with a number sign **#** (Unicode Character: U+0023)
++1. Servo ID number as an integer (assigning an ID described below)
++1. Action command (one or more letters, no whitespace, capital or lowercase from the list below)
++1. Action value in the correct units with no decimal
++1. End with a carriage return **\r** or **<cr>** Unicode Character (U+000D)
--== Action Modifiers ==
++Ex: #5D1800<cr>
--Only two commands can be used as action modifiers: Timed Move (T) and Speed (S) described below. Action modifiers can only be used with certain action commands. The format to include a modifier is:
++This sends a serial command to all servo's RX pins which are connected to the bus and only servo(s) with ID #5 will move to a position (1800 in tenths of degrees) of 180.0 degrees. Any servo on the bus which does not have ID 5 will take no action when receiving this command.
++)))
--1. Start with a number sign # (U+0023)
++|(% colspan="2" %)(((
++== Modifiers ==
++)))
++|(% style="width:25px" %) |(((
++Modifiers can only be used with certain **action commands**. The format to include a modifier is:
++
++1. Start with a number sign **#** (Unicode Character: U+0023)
 . Servo ID number as an integer
--1. Action command (one to three letters, no spaces, capital or lower case)
++1. Action command (one to three letters, no spaces, capital or lowercase from a subset of action commands below)
 . Action value in the correct units with no decimal
--1. Modifier command (one letter)
++1. Modifier command (one or two letters from the list of modifiers below)
 . Modifier value in the correct units with no decimal
--1. End with a control / carriage return '<cr>'
++1. End with a carriage return **\r** or **<cr>** Unicode Character (U+000D)
--Ex: #5P1456T1263<cr>
++Ex: #5D1800T1500<cr>
--This results in the servo with ID #5 rotating from the current angular position to a pulse position ("P") of 1456 in a time ("T") of 1263 milliseconds.
++This results in the servo with ID #5 rotating to a position (1800 in tenths of degrees) of 180.0 degrees in a time ("T") of 1500 milliseconds (1.5 seconds).
  )))
--== Configuration Commands ==
--
--Configuration commands and corresponding values affect a servo's defaults which are written to and read from the servo's EEPROM. These configurations are retained in memory after the servo is reset or power is cut / lost. Some configuration commands affect the session, while others do not (see each command for details). Not all action commands have a corresponding configuration and vice versa. More information about which configuration commands are retained when in RC mode can be found on the [[LSS - RC PWM page>>doc:Lynxmotion Smart Servo (LSS).LSS - RC PWM.WebHome]]. Configuration commands are not cumulative, in that if two configurations are sent, one after the next, only the last configuration is used and stored. The format to send a configuration command is identical to that of an action 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>'
--
--Ex: #5CO-50<cr>
--
--This configures an absolute origin offset ("CO") with respect to factory origin to servo with ID #5 and changes the offset for that session to -5.0 degrees (50 tenths of degrees). Once the servo is powered off and then powered on, zeroing the servo will cause it to move to -5.0 degrees with respect to the factory origin and report its position as 0 degrees. Configuration commands can be undone / reset either by sending the servo's default value for that configuration, or by doing a factory reset (clears all configurations) described below.
--
++|(% colspan="2" %)(((
  == Query Commands ==
--
++)))
++|(% style="width:25px" %) |(((
  Query commands request information from the servo. They are received via the Rx pin of the servo, and the servo's reply is sent via the servo's Tx pin. Using separate lines for Tx and Rx is called "full duplex". Query commands are also similar to action and configuration commands and must use the following format:
--1. Start with a number sign # (U+0023)
++1. Start with a number sign **#** (Unicode Character: U+0023)
 . Servo ID number as an integer
--1. Query command (one to three letters, no spaces, capital or lower case)
--1. End with a control / carriage return '<cr>'
++1. Query command (one to four letters, no spaces, capital or lower case)
++1. End with a carriage return **\r** or **<cr>** Unicode Character (U+000D)
--(((
--Ex: #5QD<cr>Query position in degrees for servo #5
--)))
++Ex: #5QD<cr> Query the position in (tenth of) degrees for servo with ID #5
--(((
  The query will return a serial string (almost instantaneously) via the servo's Tx pin with the following format:
--1. Start with an asterisk * (U+002A)
++1. Start with an asterisk * (Unicode Character: U+0023)
 . Servo ID number as an integer
--1. Query command (one to three letters, no spaces, capital letters)
++1. Query command (one to four letters, no spaces, capital letters)
 . The reported value in the units described, no decimals.
--1. End with a control / carriage return '<cr>'
++1. End with a carriage return **\r** or **<cr>** Unicode Character (U+000D)
--There is currently no option to control how fast a servo replies after it has received a query command, therefore when sending a query command to the bus, the controller should be prepared to immediately "listen" for and parse the reply. Sending multiple queries on a bus in fast succession may result in replies overlapping and giving incorrect or corrupt data. As such, the controller should receive a reply before sending a new command. A reply to the query sent above might be:
++There is currently no option to control how fast a servo replies after it has received a query command, therefore when sending a query command to the bus, the controller should be prepared to immediately "listen" for and parse the reply. Sending multiple queries to multiple servos on a bus in fast succession may result in replies overlapping and giving incorrect or corrupt data. As such, the controller should receive a reply before sending a new query command. A reply to the query sent above might be:
--(((
--Ex: *5QD1443<cr>
++Ex: *5QD1800<cr>
++
++This indicates that servo #5 is currently at 180.0 degrees (1800 tenths of degrees).
  )))
--This indicates that servo #5 is currently at 144.3 degrees (1443 tenths of degrees).
++|(% colspan="2" %)(((
++== Configuration Commands ==
++)))
++|(% style="width:25px" %) |(((
++Configuration commands and corresponding values affect a servo's defaults which are written to and read from the servo's EEPROM.
++These configurations are retained in memory after the servo is reset or power is cut / lost. Some configuration commands affect the session, while others do not. In the Command table below, the column "Session" denotes if the configuration command affects the session. Not all action commands have a corresponding configuration command and vice versa. More information about which configuration commands are retained when in RC mode can be found on the [[LSS - RC PWM page>>url:https://wiki.lynxmotion.com/info/wiki/lynxmotion/view/lynxmotion-smart-servo/lss-radio-control-pwm/]]. Configuration commands are not cumulative. This means that if two of the same configuration commands are sent, one after the next, only the last configuration is used and stored.
++
++The format to send a configuration command is identical to that of an action command:
++
++1. Start with a number sign **#** (Unicode Character: U+0023)
++1. Servo ID number as an integer
++1. Configuration command (two to four letters, no spaces, capital or lower case)
++1. Configuration value in the correct units with no decimal
++1. End with a carriage return **\r** or **<cr>** Unicode Character (U+000D)
++
++Ex: #5CO-50<cr>
++
++This configures an absolute origin offset ("CO") with respect to factory origin of servo with ID #5 and changes the offset for that session to -5.0 degrees (50 tenths of degrees). Once the servo is powered off and on, zeroing the servo will cause it to move to -5.0 degrees with respect to the factory origin and report its position as 0 degrees. Configuration commands can be undone / reset either by sending the servo's default value for that configuration, or by doing a factory reset that clears all configurations (through the button menu or with DEFAULT command described below).
++
  **Session vs Configuration Query**
--By default, the query command returns the sessions' value. Should no action commands have been sent to change the session value, it will return the value saved in EEPROM which will either be the servo's default, or modified with a configuration command. In order to query the value stored in EEPROM (configuration), add a '1' to the query command:
++By default, the query command returns the session's value. Should no action commands have been sent to change the session value, it will return the value saved in EEPROM which will either be the servo's default, or modified with a configuration command. In order to query the value stored in EEPROM (configuration), add a '1' to the query command:
--Ex: #5CSR20<cr> immediately sets the maximum speed for servo #5 to 20rpm (explained below) and changes the value in memory.
++Ex: #5CSR20<cr> immediately sets the maximum speed for servo #5 to 20rpm (explained below) and changes the value in memory.
  After RESET, a command of #5SR4<cr> sets the session's speed to 4rpm, but does not change the configuration value in memory. Therefore:
--#5QSR<cr> would return *5QSR4<cr> which represents the value for that session, whereas
++#5QSR<cr> or #5QSR0<cr> would return *5QSR4<cr> which represents the value for that session, whereas
  #5QSR1<cr> would return *5QSR20<cr> which represents the value in EEPROM
++)))
++|(% colspan="2" %)(((
  == Virtual Angular Position ==
++)))
++|(% style="width:25px" %) |(((
++The ability to store a "virtual angular position" is a feature which allows for rotation beyond 360 degrees, permitting 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 a 360.0 degree circle and can be obtained by taking the modulus (with respect to 360 degrees) of the value. For example if the virtual position is reported as 15335 (or 1533.5 degrees), taking the modulus would give 93.5 degrees (3600 * 4 + 935 = 15335) as the absolute position (assuming no origin offset).
--The ability to store a "virtual angular position" is a feature which allows for rotation beyond 360 degrees, permitting multiple rotations of the output horn, moving the center position and more. In virtual position mode, the "absolute position" would be the angle of the output shaft with respect to a 360.0 degree circle, and can be obtained by taking the modulus (with respect to 360 degrees) of the value. For example if the virtual position is reported as 15335 (or 1533.5 degrees), taking the modulus would give 93.5 degrees (3600 * 4 + 935 = 15335) as the absolute position (assuming no origin offset).
++[[image:https://wiki.lynxmotion.com/info/wiki/lynxmotion/download/ses-v2/lynxmotion-smart-servo/lss-communication-protocol/WebHome/LSS-servo-positions.jpg||alt="LSS-servo-positions.jpg"]]
--[[image:LSS-servo-positions.jpg]]
--
  In this example, the gyre direction (explained below, a.k.a. "rotation direction") is positive (clockwise), and origin offset has not been modified. Each square represents 30 degrees. The following command is sent:
  #1D-300<cr> This causes the servo to move to -30.0 degrees (green arrow)
@@ -113,211
          +113,275 @@
  #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 plus 60.0 degrees (420.0 - 360.0), with a virtual position of -420.0 degrees.
++#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 plus 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.
++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.
++#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).
++If 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). The virtual position range at power-up is [-180.0°, 180.0°].
  )))
  = Command List =
--|= #|=Description|= Action|= Query|= Config|= RC|= Serial|= Units|=(% style="width: 510px;" %) Notes|=(% style="width: 113px;" %)Default Value
--| 1|[[**L**imp>>||anchor="H1.Limp28L29"]]| L| | | |  ✓|none|(% style="width:510px" %) |(% style="text-align:center; width:113px" %)
--| 2|[[**H**alt & **H**old>>||anchor="H2.Halt26Hold28H29"]]| H| | | |  ✓|none|(% style="width:510px" %) |(% style="text-align:center; width:113px" %)
--| 3|[[**T**imed move>>||anchor="H3.Timedmove28T29"]]| T| | | |  ✓|milliseconds|(% style="width:510px" %) Modifier only for {P, D, MD}|(% style="text-align:center; width:113px" %)
--| 4|[[**S**peed>>||anchor="H4.Speed28S29"]]| S| | | |  ✓|microseconds / second|(% style="width:510px" %) Modifier only {P}|(% style="text-align:center; width:113px" %)
--| 5|[[**M**ove in **D**egrees (relative)>>||anchor="H5.28Relative29MoveinDegrees28MD29"]]| MD| | | |  ✓|tenths of degrees (ex 325 = 32.5 degrees)|(% style="width:510px" %) |(% style="text-align:center; width:113px" %)
--| 6|[[**O**rigin Offset>>||anchor="H6.OriginOffsetAction28O29"]]| O| QO| CO| ✓|  ✓|tenths of degrees (ex 91 = 9.1 degrees)|(% style="width:510px" %) |(% style="text-align:center; width:113px" %)(((
--0
--)))
--| 7|[[**A**ngular **R**ange>>||anchor="H7.AngularRange28AR29"]]| AR| QAR| CAR| ✓|  ✓|tenths of degrees |(% style="width:510px" %) |(% style="text-align:center; width:113px" %)(((
--1800
--)))
--| 8|[[Position in **P**ulse>>||anchor="H8.PositioninPulse28P29"]]| P| QP| | | ✓|microseconds|(% style="width:510px" %)(((
--Inherited from SSC-32 serial protocol
--)))|(% style="text-align:center; width:113px" %)
--| 9|[[Position in **D**egrees>>||anchor="H9.PositioninDegrees28D29"]]| D| QD| | | ✓|tenths of degrees |(% style="width:510px" %) |(% style="text-align:center; width:113px" %)
--| 10|[[**W**heel mode in **D**egrees>>||anchor="H10.WheelModeinDegrees28WD29"]]| WD| QWD| | | ✓|tenths of degrees per second (ex 248 = 24.8 degrees per second)|(% style="width:510px" %)A.K.A. "Speed mode" or "Continuous rotation"|(% style="text-align:center; width:113px" %)
--| 11|[[**W**heel mode in **R**PM>>||anchor="H11.WheelModeinRPM28WR29"]]| WR| QWR| | | ✓| rpm|(% style="width:510px" %)A.K.A. "Speed mode" or "Continuous rotation"|(% style="text-align:center; width:113px" %)
--| 12|[[Max **S**peed in **D**egrees>>||anchor="H12.SpeedinDegrees28SD29"]]| SD| QSD|CSD| ✓| ✓|tenths of degrees per second |(% style="width:510px" %)(((
--QSD: Add modifier "2" for instantaneous speed.
++**Latest firmware version currently : 370**
--SD overwrites SR / CSD overwrites CSR and vice-versa.
--)))|(% style="text-align:center; width:113px" %)Max per servo
--| 13|[[Max **S**peed in **R**PM>>||anchor="H13.SpeedinRPM28SR29"]]| SR| QSR|CSR| ✓| ✓|rpm|(% style="width:510px" %)(((
--QSR: Add modifier "2" for instantaneous speed
++|(% colspan="10" %)[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**Communication Setup**>>path:#HCommunicationSetup]]
++| |**Description**|**Action**|**Query**|**Config**|**RC**|**Serial**|**Default**|**Unit**|**Notes**
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**Reset**>>path:#HReset]]|RESET| | | |✓| | |Soft reset. See command for details.
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**Default** Configuration>>path:#HDefault26confirm]]|DEFAULT| | | |✓| | |Revert to firmware default values. See command for details
++| |[[Firmware (% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**Update** Mode>>path:#HUpdate26confirm]]|UPDATE| | | |✓| | |Update firmware. See command for details.
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**Confirm** Changes>>path:#HConfirm]]|CONFIRM| | | |✓| | |
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**C**hange to **RC**>>path:#HConfigureRCMode28CRC29]]| | |CRC| |✓| | |Change to RC mode 1 (position) or 2 (wheel).
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**ID** #>>path:#HIdentificationNumber28ID29]]| |QID|CID| |✓|0| |Reset required after change. ID 254 is a "broadcast" which all servos respond to.
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**B**audrate>>path:#HBaudRate]]| |QB|CB| |✓|115200| |Reset required after change.
--SR overwrites SD / CSR overwrites CSD and vice-versa.
--)))|(% style="text-align:center; width:113px" %)Max per servo
--| 16|[[**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
--| 17|[[**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
--| 18|[[**B**aud rate>>||anchor="H18.BaudRate"]]| B| QB| CB| | ✓|none (integer)|(% style="width:510px" %) |(% style="text-align:center; width:113px" %)9600
--| 19|[[**G**yre direction (**G**)>>||anchor="H19.GyreRotationDirection"]]| G| QG| CG| ✓| ✓|none |(% style="width:510px" %)Gyre / rotation direction where 1= CW (clockwise) -1 = CCW (counter-clockwise)|(% style="text-align:center; width:113px" %)1
--| 20|[[**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" %)(((
--Limp
--)))
--| 21|[[**F**irst Position (**D**egrees)>>||anchor="H21.First2InitialPosition28Degrees29"]]| | QFD|CFD| ✓| ✓|none |(% style="width:510px" %)CFD overwrites CFP and vice-versa|(% style="text-align:center; width:113px" %)Limp
--| 22|[[**T**arget (**D**egree) **P**osition>>||anchor="H22.QueryTargetPositioninDegrees28QDT29"]]| | QDT| | | ✓|tenths of degrees (ex 325 = 32.5 degrees; 91 = 9.1 degrees)|(% style="width:510px" %) |(% style="text-align:center; width:113px" %)
--| 23|[[**M**odel **S**tring>>||anchor="H23.QueryModelString28QMS29"]]| | QMS| | | |none (string)|(% style="width:510px" %) Recommended to determine the model|(% style="text-align:center; width:113px" %)
--| 23b|[[**M**odel>>||anchor="H23b.QueryModel28QM29"]]| | QM| | | |none (integer)|(% style="width:510px" %) Returns a raw value representing the three model inputs (36 bit)|(% style="text-align:center; width:113px" %)
--| 24|[[Serial **N**umber>>||anchor="H24.QuerySerialNumber28QN29"]]| | QN| | | |none (integer)|(% style="width:510px" %) |(% style="text-align:center; width:113px" %)
--| 25|[[**F**irmware version>>||anchor="H25.QueryFirmware28QF29"]]| | QF| | | |none (integer)|(% style="width:510px" %) |(% style="text-align:center; width:113px" %)
--| 26|[[**Q**uery (general status)>>||anchor="H26.QueryStatus28Q29"]]| | Q| | | ✓|none (integer from 1 to 8)|(% style="width:510px" %) See command description for details|(% style="text-align:center; width:113px" %)
--| 27|[[**V**oltage>>||anchor="H27.QueryVoltage28QV29"]]| | QV| | | ✓|millivolts (ex 5936 = 5936mV = 5.936V)|(% style="width:510px" %) |(% style="text-align:center; width:113px" %)
--| 28|[[**T**emperature>>||anchor="H28.QueryTemperature28QT29"]]| | QT| | | ✓|tenths of degrees Celsius|(% style="width:510px" %)Max temp before error: 85°C (servo goes limp)|(% style="text-align:center; width:113px" %)
--| 29|[[**C**urrent>>||anchor="H29.QueryCurrent28QC29"]]| | QC| | | ✓|milliamps (ex 200 = 0.2A)|(% style="width:510px" %) |(% style="text-align:center; width:113px" %)
--| 30|[[**RC** Mode>>||anchor="H30.RCMode28CRC29"]]| | |CRC| |✓|none|(% style="width:510px" %)(((
--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.
--)))|(% style="text-align:center; width:113px" %)Serial
--|31|[[**RESET**>>||anchor="H31.RESET"]]| | | | | ✓|none|(% style="width:510px" %)Soft reset. See command for details.|(% style="text-align:center; width:113px" %)
--|32|[[**DEFAULT**>>||anchor="H32.DEFAULTA026CONFIRM"]]| | | | |✓|none|(% style="width:510px" %)Revert to firmware default values. See command for details|(% style="text-align:center; width:113px" %)
--|33|[[**UPDATE**>>||anchor="H33.UPDATEA026CONFIRM"]]| | | | |✓|none|(% style="width:510px" %)Update firmware. See command for details.|(% style="text-align:center; width:113px" %)
++|(% colspan="10" %)[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**Motion**>>path:#HMotion]]
++| |**Description**|**Action**|**Query**|**Config**|**RC**|**Serial**|**Default**|**Unit**|**Notes**
++| |[[Position in (% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**D**egrees>>path:#HPositioninDegrees28D29]]|D|QD/QDT| | |✓| |1/10°|
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**M**ove in **D**egrees (relative)>>path:#H28Relative29MoveinDegrees28MD29]]|MD| | | |✓| |1/10°|
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**W**heel mode in **D**egrees>>path:#HWheelModeinDegrees28WD29]]|WD|QWD/QVT| | |✓| |°/s|A.K.A. "Speed mode" or "Continuous rotation"
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**W**heel mode in **R**PM>>path:#HWheelModeinRPM28WR29]]|WR|QWR| | |✓| |RPM|A.K.A. "Speed mode" or "Continuous rotation"
++| |[[Position in (% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**P**WM>>path:#HPositioninPWM28P29]]|P|QP| | |✓| |us|Inherited from SSC-32 serial protocol
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**M**ove in PWM (relative)>>path:#H28Relative29MoveinPWM28M29]]|M| | | |✓| |us|
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**R**aw **D**uty-cycle **M**ove>>path:#HRawDuty-cycleMove28RDM29]]|RDM|QMD| | |✓| |-1023 to 1023 integer|Positive values : CW / Negative values : CCW
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**Q**uery Status>>path:#HQueryStatus28Q29]]| |Q| | |✓| |1 to 8 integer|See command description for details
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**L**imp>>path:#HLimp28L29]]|L| | | |✓| | |
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**H**alt & Hold>>path:#HHalt26Hold28H29]]|H| | | |✓| | |
--== Advanced ==
++|(% colspan="10" %)[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**Motion Setup**>>path:#HMotionSetup]]
++| |**Description**|**Action**|**Query**|**Config**|**RC**|**Serial**|**Default**|**Unit**|**Notes**
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**E**nable **M**otion Profile>>path:#HEnableMotionProfile28EM29]]|EM|QEM|CEM| |✓|1| |EM1: trapezoidal motion profile / EM0: no motion profile
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**F**ilter **P**osition **C**ount>>path:#HFilterPositionCount28FPC29]]|FPC|QFPC|CFPC|✓|✓|5| |Affects motion only when motion profile is disabled (EM0)
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**O**rigin Offset>>path:#HOriginOffset28O29]]|O|QO|CO|✓|✓|0|1/10°|
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**A**ngular **R**ange>>path:#HAngularRange28AR29]]|AR|QAR|CAR|✓|✓|1800|1/10°|
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**A**ngular **S**tiffness>>path:#HAngularStiffness28AS29]]|AS|QAS|CAS|✓|✓|0|-4 to +4 integer|Suggested values are between 0 to +4
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**A**ngular **H**olding Stiffness>>path:#HAngularHoldingStiffness28AH29]]|AH|QAH|CAH|✓|✓|4|-10 to +10 integer|
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**A**ngular **A**cceleration>>path:#HAngularAcceleration28AA29]]|AA|QAA|CAA| |✓|100|°/s^^2^^|Increments of 10°/s^^2^^. Only when motion profile is enabled (EM1).
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**A**ngular **D**eceleration>>path:#HAngularDeceleration28AD29]]|AD|QAD|CAD| |✓|100|°/s^^2^^|Increments of 10°/s^^2^^. Only when motion profile is enabled (EM1).
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**G**yre Direction>>path:#HGyreDirection28G29]]|G|QG|CG|✓|✓|1| |Gyre / rotation direction: 1= CW (clockwise) -1 = CCW (counter-clockwise)
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**F**irst Position (**D**eg)>>path:#HFirstPosition]]| |QFD|CFD|✓|✓|No value|1/10°|Reset required after change.
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**M**aximum **M**otor **D**uty>>path:#HMaximumMotorDuty28MMD29]]|MMD|QMMD| | |✓|1023|255 to 1023 integer|
++| |[[Maximum (% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**S**peed in **D**egrees>>path:#HMaximumSpeedinDegrees28SD29]]|SD|QSD|CSD|✓|✓|Max|0.1°/s|SD overwrites SR / CSD overwrites CSR and vice-versa
++| |[[Maximum (% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**S**peed in **R**PM>>path:#HMaximumSpeedinRPM28SR29]]|SR|QSR|CSR|✓|✓|Max|RPM|SD overwrites SR / CSD overwrites CSR and vice-versa
--|= #|=Description|= Action|= Query|= Config|= RC|= Serial|= Units|=(% style="width: 510px;" %) Notes|=(% style="width: 113px;" %)Default Value
--| 1|[[**A**ngular **S**tiffness>>||anchor="H14.AngularStiffness28AS29"]]| AS| QAS|CAS| ✓| ✓|none|(% style="width:510px" %)-4 to +4, but suggested values are between 0 to +4|(% style="text-align:center; width:113px" %)0
--| 2|[[**A**ngular **H**olding Stiffness>>||anchor="H15.AngularHoldStiffness28AH29"]]|AH|QAH|CAH| | ✓|none|(% style="width:510px" %)-10 to +10, with default as 0. |(% style="text-align:center; width:113px" %)1
--| 3|[[**A**ngular **A**cceleration>>||anchor="H15b:AngularAcceleration28AA29"]]|AA|QAA|CAA| | ✓|degrees per second squared|(% style="width:510px" %)Increments of 10 degrees per second squared|(% style="text-align:center; width:113px" %)
--| 4|[[**A**ngular **D**eceleration>>||anchor="H15c:AngularDeceleration28AD29"]]|AD|QAD|CAD| | ✓|degrees per second squared|(% style="width:510px" %)Increments of 10 degrees per second squared|(% style="text-align:center; width:113px" %)
--| 5|[[**E**nable **M**otion control>>||anchor="H15d:MotionControl28MC29"]]|EM|QEM| | | ✓|none|(% style="width:510px" %)EM0 to disable motion control, EM1 to enable. Session specific / does not survive power cycles|(% style="text-align:center; width:113px" %)
--| 6|[[**C**onfigure **L**ED **B**linking>>||anchor="H16b.ConfigureLEDBlinking28CLB29"]]| | | CLB| ✓| |none (integer from 0 to 63)|(% style="width:510px" %)0=No blinking, ; 63=Always blink; Blink while: 1=Limp; 2=Holding 4=Accel; 8=Decel; 16=Free 32=Travel;|(% style="text-align:center; width:113px" %)
--| | | | | | | | |(% style="width:510px" %) |(% style="text-align:center; width:113px" %)
++|(% colspan="10" %)[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**Modifiers**>>path:#HModifiers]]
++| |**Description**|**Modifier**|**Query**|**Config**|**RC**|**Serial**|**Default**|**Unit**|**Notes**
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**S**peed>>path:#HSpeed28S2CSD29modifier]]|S|QS| | |✓| |uS/s |For P action command
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**S**peed in **D**egrees>>path:#HSpeed28S2CSD29modifier]]|SD| | | |✓| |0.1°/s|For D and MD action commands
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**T**imed move>>path:#HTimedmove28T29modifier]]|T| | | |✓| |ms|Modifier only for P, D and MD. Time can change based on load
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**C**urrent **H**old>>path:#HCurrentHalt26Hold28CH29modifier]]|CH| | | |✓| |mA|Modifier for D, MD, WD and WR
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**C**urrent **L**imp>>path:#HCurrentLimp28CL29modifier]]|CL| | | |✓| |mA|Modifier for D, MD, WD and WR
--== Details ==
++|(% colspan="10" %)[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**Telemetry**>>path:#HTelemetry]]
++| |**Description**|**Action**|**Query**|**Config**|**RC**|**Serial**|**Default**|**Unit**|**Notes**
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**Q**uery **V**oltage>>path:#HQueryVoltage28QV29]]| |QV| | |✓| |mV|
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**Q**uery **T**emperature>>path:#HQueryTemperature28QT29]]| |QT| | |✓| |1/10°C|
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**Q**uery **C**urrent>>path:#HQueryCurrent28QC29]]| |QC| | |✓| |mA|
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**Q**uery **M**odel **S**tring>>path:#HQueryModelString28QMS29]]| |QMS| | |✓| | |Returns the model of servo (ex: LSS-ST1, LSS-HS1, LSS-HT1)
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**Q**uery **F**irmware Version>>path:#HQueryFirmware28QF29]]| |QF| | |✓| | |
--====== __1. Limp (**L**)__ ======
++|(% colspan="10" %)[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**RGB LED**>>path:#HRGBLED]]
++| |**Description**|**Action**|**Query**|**Config**|**RC**|**Serial**|**Default**|**Unit**|**Notes**
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**LED** Color>>path:#HLEDColor28LED29]]|LED|QLED|CLED|✓|✓| |0 to 7 integer|0=Off; 1=Red; 2=Green; 3=Blue; 4=Yellow; 5=Cyan; 6=Magenta; 7=White
++| |[[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**C**onfigure **L**ED **B**linking>>path:#HConfigureLEDBlinking28CLB29]]| | |CLB|✓|✓| |0 to 63 integer|Reset required after change. See command for details.
--Example: #5L<cr>
++= Details =
--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>.
++== Communication Setup ==
--====== __2. Halt & Hold (**H**)__ ======
++|(% colspan="2" %)(((
++====== Reset ======
++)))
++|(% style="width:30px" %) |(((
++Ex: #5RESET<cr>
--Example: #5H<cr>
++This command does a "soft reset" and reverts all commands to those stored in EEPROM (i.e. configuration commands). Note: after a RESET command is received, the LSS will restart and perform initilization again, making it unavailable on the bus for a bit. See [[Session>>url:https://wiki.lynxmotion.com/info/wiki/lynxmotion/view/ses-v2/lynxmotion-smart-servo/lss-communication-protocol/#HSession]], note #2 for more details.
++)))
--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.
++|(% colspan="2" %)(((
++====== Default & confirm ======
++)))
++|(% style="width:30px" %) |(((
++Ex: #5DEFAULT<cr>
--====== __3. Timed move (**T**)__ ======
++This command sets in motion the reset of 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.
--Example: #5P1500T2500<cr>
++Ex: #5DEFAULT<cr> followed by #5CONFIRM<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.
++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 exit the command.
--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.
++**Note:** After the CONFIRM command is sent, the servo will automatically perform a RESET.
++)))
--====== __4. Speed (**S**)__ ======
++|(% colspan="2" %)(((
++====== Update & confirm ======
++)))
++|(% style="width:30px" %) |(((
++Ex: #5UPDATE<cr>
--Example: #5P1500S750<cr>
++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.
--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.
++Ex: #5UPDATE<cr> followed by #5CONFIRM<cr>
--====== __5. (Relative) Move in Degrees (**MD**)__ ======
++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.
--Example: #5MD123<cr>
++**Note:** After the CONFIRM command is sent, the servo will automatically perform a RESET.
++)))
--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.
++|(% colspan="2" %)(((
++====== Confirm ======
++)))
++|(% style="width:30px" %) |(((
++Ex: #5CONFIRM<cr>
--====== __6. Origin Offset Action (**O**)__ ======
++This command is used to confirm changes after a Default or Update command.
--Example: #5O2400<cr>
++**Note:** After the CONFIRM command is sent, the servo will automatically perform a RESET.
++)))
--This command allows you to temporarily change the origin of the servo in relation to the factory zero position. The setting will be lost upon servo reset / power cycle. Origin offset commands are not cumulative and always relate to factory zero. Note that for a given session, the O command overrides the CO command. In the first image, the origin at factory offset '0' (centered).
++|(% colspan="2" %)(((
++====== Configure RC Mode (**CRC**) ======
++)))
++|(% style="width:30px" %) |(((
++This command puts the servo into RC mode (position or continuous), where it will only respond to RC PWM signal on the servo's Rx pin. In this mode, the servo will no longer accept serial commands. The servo can be placed back into smart mode by using the button menu.
--[[image:LSS-servo-default.jpg]]
++Ex: #5CRC1<cr>
--In the second image, the origina, as well as the angular range (explained below) have been shifted by 240.0 degrees:
++Change to RC position mode.
--[[image:LSS-servo-origin.jpg]]
++Ex: #5CRC2<cr>
--Origin Offset Query (**QO**)
++Change to RC continuous rotation (wheel) mode.
--Example: #5QO<cr> Returns: *5QO-13
++Ex: #5CRC*<cr>
--This allows you to query the angle (in tenths of degrees) of the origin in relation to the factory zero position.
++Where * is any value other than 1 or 2 (or no value): stay in smart mode
--Configure Origin Offset (**CO**)
++Ex: #5CRC2<cr>
--Example: #5CO-24<cr>
++This command would place the servo in RC wheel mode after a RESET or power cycle. Note that after a RESET or power cycle, the servo will be in RC mode and will not reply to serial commands. Using the command #5CRC<cr> or #5CRC3<cr> which requests that the servo remain in serial mode still requires a RESET command.
--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.
++**Important note: **To revert from RC mode back to serial mode, the [[LSS - Button Menu>>url:https://wiki.lynxmotion.com/info/wiki/lynxmotion/view/lynxmotion-smart-servo/lss-button-menu/]] is required. Should the button be inaccessible (or broken) when the servo is in RC mode and the user needs to change to serial mode, a 5V constant HIGH needs to be sent to the servo's Rx pin (RC PWM pin), **ensuring a common GND** and wait for 30 seconds. Normal RC PWM pulses should not exceed 2500 milliseconds. After 30 seconds, the servo will interpret this as a desired mode change and change to serial mode. This has been implemented as a fail safe.
++)))
--====== __7. Angular Range (**AR**)__ ======
++|(% colspan="2" %)(((
++====== Identification Number (**ID**) ======
++)))
++|(% style="width:30px" %) |(((
++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.
--Example: #5AR1800<cr>
++Query Identification (**QID**)
--This command allows you to temporarily change the total angular range of the servo in tenths of degrees. This applies to the Position in Pulse (P) command and RC mode. The default for (P) and RC mode is 1800 (180.0 degrees total, or ±90.0 degrees). In the first image,
++EX: #254QID<cr> might return *QID5<cr>
--[[image:LSS-servo-default.jpg]]
++When using the broadcast query ID command, it is best to only have one servo connected and thus receive only one reply. This is useful when you are not sure of the servo's ID, but don't want to change it. Using the broadcast command (ID 254) with only one servo will have that servo reply with its ID number. 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.
--Here, the angular range has been restricted to 180.0 degrees, or -90.0 to +90.0. The center has remained unchanged.
++Configure ID (**CID**)
--[[image:LSS-servo-ar.jpg]]
++Ex: #4CID5<cr>
--The angular range action command (ex. #5AR1800<cr>) and origin offset action command  (ex. #5O-1200<cr>) an be used to move both the center and limit the angular range:
++Setting a servo's ID in EEPROM is done via the CID command. All servos connected to the same serial bus that have 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.
++)))
--[[image:LSS-servo-ar-o-1.jpg]]
++|(% colspan="2" %)(((
++====== Baud Rate ======
++)))
++|(% style="width:30px" %) |(((
++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 115200. Since smart servos are intended to be daisy chained, in order to respond to the same serial command, all servos in a project should 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, 750.0 kbps, 921.6 kbps. Servos are shipped with a baud rate set to 115200.
--Query Angular Range (**QAR**)
++Query Baud Rate (**QB**)
--Example: #5QAR<cr> might return *5AR2756
++Ex: #5QB<cr> might return *5QB115200<cr>Since the command to query the baud rate must be done at the servo's existing baud rate, it can simply be used to confirm the CB configuration command was correctly received before the servo is power cycled and the new baud rate takes effect.
--Configure Angular Range (**CAR**)
++Configure Baud Rate (**CB**)
--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.
++**Important Note:** the servo's current session retains the given baud rate and the new baud rate will only take effect when the servo is power cycled / RESET.
--====== __8. Position in Pulse (**P**)__ ======
++Ex: #5CB9600<cr>
--Example: #5P2334<cr>
++Sending this command will change the baud rate associated with servo ID 5 to 9600 bits per second.
++)))
--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.
++|(% colspan="2" %)(((
++====== __Automatic Baud Rate__ ======
++)))
++|(% style="width:30px" %) |(((
++This option allows the LSS to listen to it's serial input and select the right baudrate automatically.
--Query Position in Pulse (**QP**)
++Query Automatic Baud Rate (**QABR**)
--Example: #5QP<cr> might return *5QP2334
++Ex: #5QABR<cr> might return *5ABR0<cr>
--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).
++Enable Baud Rate (**ABR**)
--====== __9. Position in Degrees (**D**)__ ======
++Ex: #5QABR1<cr>
--Example: #5PD1456<cr>
++Enable baudrate detection on first byte received after power-up.
--This moves the servo to an angle of 145.6 degrees, where the center (0) position is centered. Negative values (ex. -176 representing -17.6 degrees) are used. A full circle would be from -1800 to 1800 degrees. A value of 2700 would be the same angle as -900, except the servo would move in a different direction.
++Ex: #5QABR2,30<cr>Enable baudrate detection on first byte received after power-up. If no data for 30 seconds enable detection again on next byte.
--Larger values are permitted and allow for multi-turn functionality using the concept of virtual position.
++Warning: ABR doesnt work well with LSS Config at the moment.
++)))
++== Motion ==
++
++|(% colspan="2" %)(((
++====== __Position in Degrees (**D**)__ ======
++)))
++|(% style="width:30px" %) |(((
++Ex: #5D1456<cr>
++
++This moves the servo to an angle of 145.6 degrees, where the center (0) position is centered. Negative values (ex. -176 representing -17.6 degrees) could also be used. A full circle would be from -1800 to 1800 degrees. A value of 2700 would be the same angle (absolute position) as -900, except the servo would move in a different direction.
++
++Larger values are permitted and allow for multi-turn functionality using the concept of virtual position (explained above).
++
  Query Position in Degrees (**QD**)
--Example: #5QD<cr> might return *5QD132<cr>
++Ex: #5QD<cr> might return *5QD132<cr>
--This means the servo is located at 13.2 degrees.
++This means the servo is located at 13.2 degrees.
--====== __10. Wheel Mode in Degrees (**WD**)__ ======
++Query Target Position in Degrees (**QDT**)
--Ex: #5WD900<cr>
++Ex: #5QDT<cr> might return *5QDT6783<cr>
++The query target position command returns the target virtual position 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 with the last target position used.
++)))
++
++|(% colspan="2" %)(((
++====== (Relative) Move in Degrees (**MD**) ======
++)))
++|(% style="width:30px" %) |(((
++Ex: #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.
++)))
++
++|(% colspan="2" %)(((
++====== Wheel Mode in Degrees (**WD**) ======
++)))
++|(% style="width:30px" %) |(((
++Ex: #5WD90<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).
  Query Wheel Mode in Degrees (**QWD**)
--Ex: #5QWD<cr> might return *5QWD900<cr>
++Ex: #5QWD<cr> might return *5QWD90<cr>
--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).
++The servo replies with the angular speed in 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**)__ ======
--
++|(% colspan="2" %)(((
++====== Wheel Mode in RPM (**WR**) ======
++)))
++|(% style="width:30px" %) |(((
  Ex: #5WR40<cr>
--This command sets the servo to wheel mode where it will rotate in the desired direction at the selected rpm. Wheel mode (a.k.a. "continuous rotation") has the servo operate like a geared DC motor. The servo's maximum rpm cannot be set higher than its physical limit at a given voltage.  The example above would have the servo rotate at 40 rpm clockwise (assuming factory default configurations).
++This command sets the servo to wheel mode where it will rotate in the desired direction at the selected rpm. Wheel mode (a.k.a. "continuous rotation") has the servo operate like a geared DC motor. The servo's maximum rpm cannot be set higher than its physical limit at a given voltage. The example above would have the servo rotate at 40 rpm clockwise (assuming factory default configurations).
  Query Wheel Mode in RPM (**QWR**)
@@ -324,195
          +324,321 @@
  Ex: #5QWR<cr> might return *5QWR40<cr>
  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**)__ ======
++|(% colspan="2" %)(((
++====== Position in PWM (**P**) ======
++)))
++|(% style="width:30px" %) |(((
++Ex: #5P2334<cr>
--Ex: #5SD1800<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 signal and is further explained in the SSC-32 and [[SSC-32U manuals>>url:https://www.robotshop.com/media/files/pdf2/lynxmotion_ssc-32u_usb_user_guide.pdf#page=24]]. Without any modifications to configuration considered, and a ±90.0 degrees standard range where 1500 microseconds is centered, a PWM signal of 2334 would set the servo to 165.1 degrees. Valid values for P are [500, 2500]. Values outside this range are corrected / restricted to end points.
--This command sets the servo's maximum speed for action commands in tenths of degrees per second for that session. In the example above, the servo's maximum speed for that session would be set to 180.0 degrees per second. Therefore maximum speed for actions can be set "on the fly". The servo's maximum speed cannot be set higher than its physical limit at a given voltage. SD overrides CSD (described below) for that session. Upon reset or power cycle, the servo reverts to the value associated with CSD as described below. Note that SD and SR (described below) are effectively the same, but allow the user to specify the speed in either unit. The last command (either SR or SD) is what the servo uses for that session.
++Query Position in Pulse (**QP**)
--Query Speed in Degrees (**QSD**)
++Ex: #5QP<cr> might return *5QP2334
--Ex: #5QSD<cr> might return *5QSD1800<cr>
++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).
++)))
--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:
++|(% colspan="2" %)(((
++====== __(Relative) Move in PWM (**M**)__ ======
++)))
++|(% style="width:30px" %) |(((
++Ex: #5M1500<cr>
--|**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
++The relative move in PWM command causes the servo to read its current position and move by the specified number of PWM signal. For example if the servo is set to rotate CW (default) and an M command of 1500 is sent to the servo, it will cause the servo to rotate clockwise by 90 degrees. Negative PWM value would cause the servo to rotate in the opposite configured direction.
++)))
--Configure Speed in Degrees (**CSD**)
++|(% colspan="2" %)(((
++====== Raw Duty-cycle Move (**RDM**) ======
++)))
++|(% style="width:30px" %) |(((
++Ex: #5RDM512<cr>
--Ex: #5CSD1800<cr>
++The raw duty-cycle move command (or free move command) will rotate the servo at a specified duty cycle value in wheel mode (a.k.a. "continuous rotation") like a geared DC motor.
--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.
++The duty values range from 0 to 1023. Negative values will rotate the servo in the opposite direction (for factory default a negative value would be counter clockwise).
--====== __13. Speed in RPM (**SR**)__ ======
++Query Move in Duty-cycle (**QMD**)
--Ex: #5SD45<cr>
++Ex: #5QMD<cr> might return *5QMD512
--This command sets the servo's maximum speed for action commands in rpm for that session. In the example above, the servo's maximum speed for that session would be set to 45rpm. Therefore maximum speed for actions can be set "on the fly". The servo's maximum speed cannot be set higher than its physical limit at a given voltage. SD overrides CSD (described below) for that session. Upon reset or power cycle, the servo reverts to the value associated with CSD as described below. Note that SD (described above) and SR are effectively the same, but allow the user to specify the speed in either unit. The last command (either SR or SD) is what the servo uses for that session.
++This command queries the raw duty-cycle move value. 512 value means that the motor is rotating at 50% duty-cycle.
++)))
--Query Speed in Degrees (**QSR**)
++|(% colspan="2" %)(((
++====== Query Status (**Q**) ======
++)))
++|(% style="width:30px" %) |(((
++The status query describes what the servo is currently doing. The query returns an integer which must be looked up in the table below.
--Ex: #5QSR<cr> might return *5QSR45<cr>
++Ex: #5Q<cr> might return *5Q6<cr>
--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:
++which indicates the motor is holding a position.
++)))
--|**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
++|(% style="width:30px" %) |***Value returned (Q)**|**Status**|**Detailed description**
++| |ex: *5Q0<cr>|0: Unknown|LSS is unsure / unknown state
++| |ex: *5Q1<cr>|1: Limp|Motor driving circuit is not powered and horn can be moved freely
++| |ex: *5Q2<cr>|2: Free moving|Servo is rotating in duty motion / free move using the RDM command
++| |ex: *5Q3<cr>|3: Accelerating|Increasing speed from rest (or previous speed) towards travel speed
++| |ex: *5Q4<cr>|4: Traveling|Moving at a stable speed
++| |ex: *5Q5<cr>|5: Decelerating|Decreasing from travel speed towards final position.
++| |ex: *5Q6<cr>|6: Holding|Keeping current position (in EM0 mode, return will nornally be holding)
++| |ex: *5Q7<cr>|7: Outside limits|{More details coming soon}
++| |ex: *5Q8<cr>|8: Stuck|Motor cannot perform request movement at current speed setting
++| |ex: *5Q9<cr>|9: Blocked|Similar to stuck, but the motor is at maximum duty and still cannot move (i.e.: stalled)
++| |ex: *5Q10<cr>|10: Safe Mode|(((
++A safety limit has been exceeded (temperature, peak current or extended high current draw).
--Configure Speed in RPM (**CSR**)
++Send a Q1 command to know which limit has been reached (described below).
++)))
--Ex: #5CSR45<cr>
++|(% style="width:30px" %) |(% colspan="3" rowspan="1" %)If a safety limit has been reached and exceeded, the LED will flash red and the servo will stop providing torque (no longer react to commands which cause the motor to rotate). In order to determine which limit has been reached, send a Q1 command. The servo must be RESET in order to return to normal operation, though if a limit is still detected (for example the servo is still too hot), it will revert back to Safe Mode.
++| |***Value returned (Q1)**|**Status**|**Detailed description**
++| |ex: *5Q0<cr>|No limits have been passed|Nothing is wrong
++| |ex: *5Q1<cr>|Current limit has been passed|Something cause the current to either spike, or remain too high for too long
++| |ex: *5Q2<cr>|Input voltage detected is below or above acceptable range|Check the voltage of your batteries or power source
++| |ex: *5Q3<cr>|Temperature limit has been reached|The servo is too hot to continue operating safely.
--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.
++|(% colspan="2" %)(((
++====== Limp (**L**) ======
++)))
++|(% style="width:30px" %) |(((
++Ex: #5L<cr>
--====== __14. Angular Stiffness (**AS**)__ ======
++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>.
++)))
--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.
++|(% colspan="2" %)(((
++====== Halt & Hold (**H**) ======
++)))
++|(% style="width:30px" %) |(((
++Example: #5H<cr>
--A positive value of "angular stiffness":
++This command causes the servo to stop immediately and hold that angular position. It overrides whatever the servo might be doing at the time the command is received (accelerating, travelling, deccelerating, etc.)
++)))
--* 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
++== Motion Setup ==
--A negative value on the other hand:
++|(% colspan="2" %)(((
++====== Enable Motion Profile (**EM**) ======
++)))
++|(% style="width:30px" %) |(((
++EM1 (Enable Motion Profile #1) is the default mode of the LSS and is an easy way to control the servo's position with a single (serial) position command. This mode uses a trapezoidal motion profile which takes care of acceleration, constant speed travel and deceleration. Once the actual position is within a certain value of the target, it switches to a holding algorithm. The LSS commands for Angular Acceleration and Deceleration (AA/CAA/AD/CAD) Angular Stiffness (AS/CAS) and Angular holding stiffness (AH/CAH) affect this motion profile. Modifiers like SD/S and T can be used in EM1.
--* 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
++Ex: #5EM1<cr>
--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.
++This command enables a trapezoidal motion profile for servo #5
--Ex: #5AS-2<cr>
++Ex: #5EM0<cr>
--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.
++This command will disable the built-in trapezoidal motion profile. As such, the servo will move at full speed to the target position using the D/MD action commands. Modifiers like SD/S or T cannot be used in EM0 mode. By default the Filter Position Counter, or "FPC" is active in EM0 mode to smooth out its operation. EM0 is suggested for applications where an external controller will be determining all incremental intermediate positions of the servo's motion, effectively replacing a trajectory manager. To prevent having to send position commands continuously to reach the desired position in EM0/FPC active (FPC >= 2), an internal position engine (IPE) repeats the last position command. Note that in EM0 mode, the servo will effectively always be in status: Holding (if using the query status command).
--Ex: #5QAS<cr>
++Query Motion Profile (**QEM**)
--Queries the value being used.
++Ex: #5QEM<cr> might return *5QEM1<cr>
--Ex: #5CAS<cr>
++This command will query the motion profile. **0:** motion profile disabled / **1:** trapezoidal motion profile enabled.
--Writes the desired angular stiffness value to memory.
++Configure Motion Profile (**CEM**)
--====== __15. Angular Hold Stiffness (**AH**)__ ======
++Ex: #5CEM0<cr>
--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.
++This command configures the motion profile and saves it in the EEPROM. The setting will be saved upon servo reset / power cycle.
++)))
--Ex: #5AH3<cr>
++|(% colspan="2" %)(((
++====== Filter Position Count (**FPC**) ======
++)))
++|(% style="width:30px" %) |(((
++The FPC value relates to the depth of a first order filter (exponential weighted average) over the position change. This has the effect of slowing down both acceleration and deceleration while still allowing the LSS to try to reach the desired position at maximum power at all times. A smaller FPC value will reduce the smoothing effect and a larger value will increase it. To prevent having to send position commands continuously to reach the desired position in EM0/FPC active (FPC >= 2), an internal position engine (IPE) has been put in place, which is also active by default.
--This sets the holding stiffness for servo #5 to 3 for that session.
++Ex: #5FPC10<cr>
--Query Angular Hold Stiffness (**QAH**)
++This command allows the user to change the Filter Position Count value for that session.
--Ex: #5QAH<cr> might return *5QAH3<cr>
++Query Filter Position Count (**QFPC**)
--This returns the servo's angular holding stiffness value.
++Ex: #5QFPC<cr> might return *5QFPC10<cr>
--Configure Angular Hold Stiffness (**CAH**)
++This command will query the Filter Position Count value.
--Ex: #5CAH2<cr>
++Configure Filter Position Count (**CFPC**)
--This writes the angular holding stiffness of servo #5 to 2 to EEPROM
++Ex: #5CFPC10<cr>
--====== __15b: Angular Acceleration (**AA**)__ ======
++This command configures the Filter Position Count value and saves it in the EEPROM. The setting will be saved upon servo reset / power cycle.
++)))
--{More details to come}
++|(% colspan="2" %)(((
++====== Origin Offset (**O**) ======
++)))
++|(% style="width:30px" %) |(((
++Ex: #5O2400<cr>
--====== __15c: Angular Deceleration (**AD**)__ ======
++This command allows you to change the origin of the servo in relation to the factory zero position for that session. As with all action commands, the setting will be lost upon servo reset / power cycle. Origin offset commands are not cumulative and always relate to factory zero. In the first image, the origin at factory offset '0' (centered).
--{More details to come}
++[[image:https://wiki.lynxmotion.com/info/wiki/lynxmotion/download/ses-v2/lynxmotion-smart-servo/lss-communication-protocol/WebHome/LSS-servo-default.jpg||alt="LSS-servo-default.jpg"]]
--====== __15d: Motion Control (**EM**)__ ======
++In the second image, the origin, and the corresponding angular range (explained below) have been shifted by +240.0 degrees:
--{More details to come}
++[[image:https://wiki.lynxmotion.com/info/wiki/lynxmotion/download/ses-v2/lynxmotion-smart-servo/lss-communication-protocol/WebHome/LSS-servo-origin.jpg||alt="LSS-servo-origin.jpg"]]
--====== __16. RGB LED (**LED**)__ ======
++Origin Offset Query (**QO**)
--Ex: #5LED3<cr>
++Ex: #5QO<cr> might return *5QO-13
--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.
++This allows you to query the angle (in tenths of degrees) of the origin in relation to the factory zero position. In this example, the new origin is at -1.3 degrees from the factory zero.
--0=OFF 1=RED 2=GREEN 3= BLUE 4=YELLOW 5=CYAN 6= 7=MAGENTA, 8=WHITE
++Configure Origin Offset (**CO**)
--Query LED Color (**QLED**)
++Ex: #5CO-24<cr>
--Ex: #5QLED<cr> might return *5QLED5<cr>
++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. In the example, the new origin will be at -2.4 degrees from the factory zero.
++)))
--This simple query returns the indicated servo's LED color.
++|(% colspan="2" %)Angular Range (**AR**)(((
++======   ======
++)))
++|(% style="width:30px" %) |(((
++Ex: #5AR1800<cr>
--Configure LED Color (**CLED**)
++This command allows you to temporarily change the total angular range of the servo in tenths of degrees. This applies to the Position in Pulse (P) command and RC mode. The default for (P) and RC mode is 1800 (180.0 degrees total, or ±90.0 degrees). The image below shows a standard -180.0 to +180.0 range, with no offset:
--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.
++[[image:https://wiki.lynxmotion.com/info/wiki/lynxmotion/download/ses-v2/lynxmotion-smart-servo/lss-communication-protocol/WebHome/LSS-servo-default.jpg||alt="LSS-servo-default.jpg"]]
--====== __16b. Configure LED Blinking (**CLB**)__ ======
++Below, the angular range is restricted to 180.0 degrees, or -90.0 to +90.0. The center has remained unchanged.
--This command allows you to control when the RGB LED will blink the user set color (see [[16. RGB LED>>||anchor="H16.RGBLED28LED29"]] for details).
--You can turn on or off blinking for various LSS status. Here is the list and their associated value: 0=No blinking, ; 63=Always blink; Blink while: 1=Limp; 2=Holding 4=Accel; 8=Decel; 16=Free 32=Travel;
++[[image:https://wiki.lynxmotion.com/info/wiki/lynxmotion/download/ses-v2/lynxmotion-smart-servo/lss-communication-protocol/WebHome/LSS-servo-ar.jpg||alt="LSS-servo-ar.jpg"]]
--To set blinking, use CLB with the value of your choosing. To activate blinking in multiple status, simply add together the values of the corresponding status. See examples below:
++Finally, the angular range action command (ex. #5AR1800<cr>) and origin offset action command (ex. #5O-1200<cr>) are used to move both the center and limit the angular range:
--Ex: #5CLB0<cr> to turn off all blinking (LED always solid)
--Ex: #5CLB1<cr> only blink when limp
--Ex: #5CLB2<cr> only blink when holding
--Ex: #5CLB12<cr> only blink when accel or decel
--Ex: #5CLB48<cr> only blink when free or travel
--Ex: #5CLB63<cr> blink in all status
++[[image:https://wiki.lynxmotion.com/info/wiki/lynxmotion/download/ses-v2/lynxmotion-smart-servo/lss-communication-protocol/WebHome/LSS-servo-ar-o-1.jpg||alt="LSS-servo-ar-o-1.jpg"]]
--====== __17. Identification Number__ ======
++Query Angular Range (**QAR**)
--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.
++Ex: #5QAR<cr> might return *5AR1800, indicating the total angular range is 180.0 degrees.
--Query Identification (**QID**)
++Configure Angular Range (**CAR**)
--EX: #254QID<cr> might return *QID5<cr>
++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.
++)))
--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.
++|(% colspan="2" %)(((
++====== Angular Stiffness (**AS**) ======
++)))
++|(% style="width:30px" %) |(((
++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. There are no units.
--Configure ID (**CID**)
++A higher value of "angular stiffness":
--Ex: #4CID5<cr>
++* 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
--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.
++A lower value on the other hand:
--====== __18. Baud Rate__ ======
++* 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
--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.
++The default value for stiffness depending on the firmware may be 0 or 1. Greater values produce increasingly erratic behavior and the effect becomes extreme below -4 and above +4. Maximum values are -10 to +10.
--Query Baud Rate (**QB**)
++Ex: #5AS-2<cr>
--Ex: #5QB<cr> might return *5QB9600<cr>
++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.
--Querying the baud rate is used simply to confirm the CB configuration command before the servo is power cycled.
++Ex: #5QAS<cr>
--Configure Baud Rate (**CB**)
++Queries the value being used.
--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.
++Ex: #5CAS-2<cr>Writes the desired angular stiffness value to EEPROM.
++)))
--Ex: #5CB9600<cr>
++|(% colspan="2" %)(((
++====== Angular Holding Stiffness (**AH**) ======
++)))
++|(% style="width:30px" %) |(((
++The angular holding stiffness determines the servo's ability to hold a desired position under load. The default value for stiffness depending on the firmware may be 0 or 1. Greater values produce increasingly erratic behavior and the effect becomes extreme below -4 and above +4. Maximum values are -10 to +10.
--Sending this command will change the baud rate associated with servo ID 5 to 9600 bits per second.
++Ex: #5AH3<cr>
--====== __19. Gyre Rotation Direction__ ======
++This sets the holding stiffness for servo #5 to 3 for that session.
--"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).
++Query Angular Holding Stiffness (**QAH**)
--{images showing before and after with AR and Origin offset}
++Ex: #5QAH<cr> might return *5QAH3<cr>
++This returns the servo's angular holding stiffness value.
++
++Configure Angular Holding Stiffness (**CAH**)
++
++Ex: #5CAH2<cr>
++
++This writes the angular holding stiffness of servo #5 to 2 to EEPROM.
++)))
++
++|(% colspan="2" %)(((
++====== Angular Acceleration (**AA**) ======
++)))
++|(% style="width:30px" %) |(((
++The default value for angular acceleration is 100. Accepts values of between 1 and 100. Increments of 10 degrees per second squared.
++
++Ex: #5AA30<cr>
++
++This sets the angular acceleration for servo #5 to 30 degrees per second squared (°/s^^2^^).
++
++Query Angular Acceleration (**QAA**)
++
++Ex: #5QAA<cr> might return *5QAA30<cr>
++
++This returns the servo's angular acceleration in degrees per second squared (°/s^^2^^).
++
++Configure Angular Acceleration (**CAA**)
++
++Ex: #5CAA30<cr>
++
++This writes the angular acceleration of servo #5 to 30 degrees per second squared (°/s^^2^^) to EEPROM.
++)))
++
++|(% colspan="2" %)(((
++====== Angular Deceleration (**AD**) ======
++)))
++|(% style="width:30px" %) |(((
++The default value for angular deceleration is 100. Accepts values of between 1 and 100. Increments of 10 degrees per second squared.
++
++Ex: #5AD30<cr>
++
++This sets the angular deceleration for servo #5 to 30 degrees per second squared (°/s^^2^^).
++
++Query Angular Deceleration (**QAD**)
++
++Ex: #5QAD<cr> might return *5QAD30<cr>
++
++This returns the servo's angular deceleration in degrees per second squared (°/s^^2^^).
++
++Configure Angular Deceleration (**CAD**)
++
++Ex: #5CAD30<cr>
++
++This writes the angular deceleration of servo #5 to 30 degrees per second squared (°/s^^2^^) to EEPROM.
++)))
++
++|(% colspan="2" %)(((
++====== Gyre Direction (**G**) ======
++)))
++|(% style="width:30px" %) |(((
++"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. By default: CW = 1; CCW = -1.
++
++Ex: #5G-1<cr>
++
++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.
++
  Query Gyre Direction (**QG**)
  Ex: #5QG<cr> might return *5QG-1<cr>
--The value returned above means the servo is in a counter-clockwise gyration.
++The value returned above means the servo is in a counter-clockwise gyration. Sending a #5WR30 command will rotate the servo in a counter-clockwise gyration at 30 RPM.
  Configure Gyre (**CG**)
@@ -519,142
          +519,272 @@
  Ex: #5CG-1<cr>
  This changes the gyre direction as described above and also writes to EEPROM.
++)))
--====== __20. First / Initial Position (pulse)__ ======
++|(% colspan="2" %)(((
++====== First Position ======
++)))
++|(% style="width:30px" %) |(((
++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. Note that the number should be restricted to -1790 (-179.0 degrees) to +1790 (179.0 degrees) and values beyond this will be changed to 1800.
--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**)
--Query First Position in Pulses (**QFP**)
++Ex: #5QFD<cr> might return *5QFD900<cr>
--Ex: #5QFP<cr> might return *5QFP1550<cr>
++The reply above indicates that servo with ID 5 has a first position of 90.0 degrees. If there is no first position value stored, the reply will be DIS.
--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 Degrees (**CFD**)
--Configure First Position in Pulses (**CFP**)
++Ex: #5CFD900<cr>
--Ex: #5CP1550<cr>
++This configuration command means the servo, when set to smart mode, will immediately move to 90.0 degrees upon power up. Sending a CFD command without a number (Ex. #5CFD<cr>) results in the servo remaining limp upon power up. In order to remove the first position, send no value, ex: #5CFD<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 (i.e. disabled).
++|(% colspan="2" %)(((
++====== Maximum Motor Duty (**MMD**) ======
++)))
++|(% style="width:30px" %) |(((
++This command allows the user to limit the duty cycle value sent from the servo's MCU to the DC Motor driver. The duty cycle limit value can be within the range of 255 to 1023. The default value is 1023. A typical use-case for this command is active compliance.
--====== __21. First / Initial Position (Degrees)__ ======
++Ex: #5MMD512<cr>
--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.
++This will set the duty-cycle to 512 for servo with ID 5 for that session.
--Query First Position in Degrees (**QFD**)
++Query Maximum Motor Duty (**QMMD**)
--Ex: #5QFD<cr> might return *5QFD64<cr>
++Ex: #5QMMDD<cr> might return *5QMMD512<cr>
--The reply above indicates that servo with ID 5 has a first position pulse of 1550 microseconds.
++This command returns the configured limit of the duty cycle value sent from the servo's MCU to the Motor Controller. The default value is 1023.
++)))
--Configure First Position in Degrees (**CFD**)
++|(% colspan="2" %)(((
++====== Maximum Speed in Degrees (**SD**) ======
++)))
++|(% style="width:30px" %) |(((
++Ex: #5SD1800<cr>
--Ex: #5CD64<cr>
++This command sets the servo's maximum speed for motion commands in tenths of degrees per second for that session. In the example above, the servo's maximum speed for that session would be set to 180.0 degrees per second. The servo's maximum speed cannot be set higher than its physical limit at a given voltage. The SD action command overrides CSD (described below) for that session. Upon reset or power cycle, the servo reverts to the value associated with CSD as described below. Note that SD and SR (described below) are effectively the same, but allow the user to specify the speed in either unit. The last command (either SR or SD) received is what the servo uses for that session.
--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.
++Query Speed in Degrees (**QSD**)
--====== __22. Query Target Position in Degrees (**QDT**)__ ======
++Ex: #5QSD<cr> might return *5QSD1800<cr>
--Ex: #5QDT<cr> might return *5QDT6783<cr>
++By default QSD will return the current session value, which is set to the value of CSD as reset/power cycle and changed whenever an 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:
++)))
--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>).
++|(% style="width:30px" %) |**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 in EEPROM (set by CSD/CSR)
++| |ex: #5QSD2<cr>|Instantaneous speed (same as QWD)
++| |ex: #5QSD3<cr>|Target travel speed
--====== __23. Query Model String (**QMS**)__ ======
++|(% style="width:30px" %) |(((
++Configure Speed in Degrees (**CSD**)
--Ex: #5QMS<cr> might return *5QMSLSS-HS1cr>
++Ex: #5CSD1800<cr>
--This reply means the servo model  is LSS-HS1, meaning a high speed servo, first revision.
++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.
++)))
--====== __23b. Query Model (**QM**)__ ======
++|(% colspan="2" %)(((
++====== Maximum Speed in RPM (**SR**) ======
++)))
++|(% style="width:30px" %) |(((
++Ex: #5SR45<cr>
--Ex: #5QM<cr> might return *5QM68702699520cr>
++This command sets the servo's maximum speed for motion commands in rpm for that session. In the example above, the servo's maximum speed for that session would be set to 45rpm. The servo's maximum speed cannot be set higher than its physical limit at a given voltage. SR overrides CSR (described below) for that session. Upon reset or power cycle, the servo reverts to the value associated with CSR as described below. Note that SD (described above) and SR are effectively the same, but allow the user to specify the speed in either unit. The last command (either SR or SD) received is what the servo uses for that session.
--This reply means the servo model is 0xFFF000000 or 100, meaning a high speed servo, first revision.
++Query Speed in RPM (**QSR**)
--====== __24. Query Serial Number (**QN**)__ ======
++Ex: #5QSR<cr> might return *5QSR45<cr>
--Ex: #5QN<cr> might return *5QN~_~_<cr>
++By default QSR will return the current session value, which is set to the value of CSR as reset/power cycle and changed whenever an 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:
++)))
--The number in the response is the servo's serial number which is set and cannot be changed.
++|(% style="width:30px" %) |**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 in EEPROM (set by CSD/CSR)
++| |ex: #5QSR2<cr>|Instantaneous speed (same as QWD)
++| |ex: #5QSR3<cr>|Target travel speed
--====== __25. Query Firmware (**QF**)__ ======
++|(((
++Configure Speed in RPM (**CSR**)
--Ex: #5QF<cr> might return *5QF11<cr>
++Ex: #5CSR45<cr>
--The integer in the reply represents the firmware version with one decimal, in this example being 1.1
++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.
++)))|
--====== __26. Query Status (**Q**)__ ======
++== Modifiers ==
--Ex: #5Q<cr> might return *5Q6<cr>, which indicates the motor is holding a position.
++|(% colspan="2" %)(((
++====== Speed (**S**, **SD**) modifier ======
++)))
++|(% style="width:30px" %) |(((
++Ex: #5P1500S750<cr>
--|*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>|Decelerating|Decreasing from travel speed towards final position.
--|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 maximum duty and still cannot move (i.e.: stalled)
++Modifier (S) is 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.
--====== __27. Query Voltage (**QV**)__ ======
++Ex: #5D0SD180<cr>
--Ex: #5QV<cr> might return *5QV11200<cr>
++Modifier (SD) is only for a position (D) or relative position (MD) action and determines the speed of the move in tenths of degrees per second. A speed modifier (SD) of 180 would cause the servo to rotate from its current position to the desired absolute or relative position at a speed of 18 degrees per second.
--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).
++Query Speed (**QS**)
--====== __28. Query Temperature (**QT**)__ ======
++Ex: #5QS<cr> might return *5QS300<cr>
--Ex: #5QT<cr> might return *5QT564<cr>
++This command queries the current speed in microseconds per second.
++)))
--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.
++|(% colspan="2" %)(((
++====== Timed move (**T**) modifier ======
++)))
++|(% style="width:30px" %) |(((
++
--====== __29. Query Current (**QC**)__ ======
++Example: #5P1500T2500<cr>
++Timed move can be used only as a modifier for a position (P, D, MD) actions. 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. The onboard controller will attempt to ensure that the move is performed entirely at the desired velocity, though differences in torque may cause it to not be exact. This command is in place to ensure backwards compatibility with the SSC-32 / 32U protocol.
++
++**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.
++)))
++
++|(% colspan="2" %)(((
++====== Current Halt & Hold (**CH**) modifier ======
++)))
++|(% style="width:30px" %) |(((
++Example: #5D1423CH400<cr>
++
++This has servo with ID 5 move to 142.3 degrees but, should it detect a current of 400mA or higher before it reaches the desired position, will immediately halt and hold position.
++
++This modifier can be added to the following actions: D; MD; WD; WR.
++)))
++
++|(% colspan="2" %)(((
++====== Current Limp (**CL**) modifier ======
++)))
++|(% style="width:30px" %) |(((
++Example: #5D1423CL400<cr>
++
++This has servo with ID 5 move to 142.3 degrees but, should it detect a current of 400mA or higher before it reaches the desired position, will immediately go limp.
++
++This modifier can be added to the following actions: D; MD; WD; WR.
++)))
++
++== Telemetry ==
++
++|(% colspan="2" %)(((
++====== Query Voltage (**QV**) ======
++)))
++|(% style="width:30px" %) |(((
++Ex: #5QV<cr> might return *5QV11200<cr>
++
++The number returned is in milliVolts, so in the case above, servo with ID 5 has an input voltage of 11.2V.
++)))
++
++|(% colspan="2" %)(((
++====== Query Current (**QC**) ======
++)))
++|(% style="width:30px" %) |(((
++
++
  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.
++)))
--====== __30. RC Mode (**CRC**)__ ======
++|(% colspan="2" %)(((
++====== Query Model String (**QMS**) ======
++)))
++|(% style="width:30px" %) |(((
++
--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.
++Ex: #5QMS<cr> might return *5QMSLSS-HS1<cr>
--|**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.
++This reply means that the servo model is LSS-HS1: a high speed servo, first revision.
++)))
--EX: #5CRC<cr>
++|(% colspan="2" %)(((
++====== Query Firmware (**QF**) ======
++)))
++|(% style="width:30px" %) |(((
++Ex: #5QF<cr> might return *5QF368<cr>
--====== __31. RESET__ ======
++The number in the reply represents the firmware version, in this example being 368.
--Ex: #5RESET<cr> or #5RS<cr>
++The command #5QF3<cr> can also be sent and the servo will reply with a 3 numbers firmware version, for example, 368.29.14
++)))
--This command does a "soft reset" (no power cycle required) and reverts all commands to those stored in EEPROM (i.e. configuration commands).
++== RGB LED ==
--====== __32. DEFAULT & CONFIRM__ ======
++|(% colspan="2" %)(((
++====== LED Color (**LED**) ======
++)))
++|(% style="width:30px" %) |(((
++
--Ex: #5DEFAULT<cr>
++Ex: #5LED3<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.
++This action sets the servo's RGB LED color for that session.
--EX: #5DEFAULT<cr> followed by #5CONFIRM<cr>
++The LED can be used for aesthetics, or (based on user code) to provide visual status updates. Using timing can create patterns.
--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.
++0=Off (black); 1=Red 2=Green; 3=Blue; 4=Yellow; 5=Cyan; 6=Magenta; 7=White;
--Note that after the CONFIRM command is sent, the servo will automatically perform a RESET.
++Query LED Color (**QLED**)
--====== __33. UPDATE & CONFIRM__ ======
++Ex: #5QLED<cr> might return *5QLED5<cr>
--Ex: #5UPDATE<cr>
++This simple query returns the indicated servo's LED color.
--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.
++Configure LED Color (**CLED**)
--EX: #5UPDATE<cr> followed by #5CONFIRM<cr>
++Ex: #5CLED3<cr>
--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.
++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. The command above will configure the servo's LED to a Blue color.
++)))
--Note that after the CONFIRM command is sent, the servo will automatically perform a RESET.
++|(% colspan="2" %)(((
++====== Configure LED Blinking (**CLB**) ======
++)))
++|(% style="width:30px" %) |(((
++
++
++This command allows you to control when the RGB LED will blink the user set color (see RGB LED command for details). This is very useful when visually seeing what the servo is doing. You can turn on or off blinking for various LSS status. The command requires that the servo be RESET. Here is the list and their associated value:
++)))
++
++|(% style="width:30px" %) |(% style="width:200px" %)**Blink While:**|(% style="width:50px" %)**#**|
++| |No blinking|0|
++| |Limp|1|
++| |Holding|2|
++| |Accelerating|4|
++| |Decelerating|8|
++| |Free|16|
++| |Travelling|32|
++| |Always blink|63|
++
++|(% style="width:30px" %) |(((
++To set blinking, use CLB with the value of your choosing. To activate blinking in multiple status, simply add together the values of the corresponding status. See examples below:
++
++Ex: #5CLB0 to turn off all blinking (LED always solid)
++
++Ex: #5CLB1 only blink when limp (1)
++
++Ex: #5CLB2 only blink when holding (2)
++
++Ex: #5CLB12 only blink when accel or decel (accel 4 + decel 8 = 12)
++
++Ex: #5CLB48 only blink when free or travel (free 16 + travel 32 = 48)
++
++Ex: #5CLB63 blink in all status (1 + 2 + 4 + 8 + 16 + 32)
++
++RESETTING the servo is needed.
++)))
++
++|(% colspan="2" style="width:30px" %)(((
++====== RGB LED Patterns ======
++)))
++|(% style="width:30px" %) |(((
++The LED patterns below do not include those which are part of the button menu, which can be found here: [[LSS Button Menu>>url:https://wiki.lynxmotion.com/info/wiki/lynxmotion/view/ses-v2/lynxmotion-smart-servo/lss-button-menu/]]
++)))
++|(% style="width:30px" %) |[[image:https://wiki.lynxmotion.com/info/wiki/lynxmotion/download/ses-v2/lynxmotion-smart-servo/lss-communication-protocol/WebHome/LSS%20-%20LED%20Patterns.png||alt="LSS - LED Patterns.png"]]

LSS - LED Patterns.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+116.3 KB

Content

LSS-Protocol-Backup-2020-05-01.zip

Author

...	...	@@ -1,0 +1,1 @@
	1	+xwiki:XWiki.ENantel

Size

...	...	@@ -1,0 +1,1 @@
	1	+47.4 KB

Content

XWiki.XWikiRights[0]

Allow/Deny

...	...	@@ -1,1 +1,0 @@
1		-1

Groups

...	...	@@ -1,1 +1,0 @@
1		-xwiki:XWiki.XWikiAdminGroup

Levels

...	...	@@ -1,1 +1,0 @@
1		-view

XWiki.XWikiRights[1]

Allow/Deny

...	...	@@ -1,1 +1,0 @@
1		-1

Groups

...	...	@@ -1,1 +1,0 @@
1		-XWiki.XWikiAdminGroup

Levels

...	...	@@ -1,1 +1,0 @@
1		-view

XWiki.XWikiRights[2]

Allow/Deny

...	...	@@ -1,1 +1,0 @@
1		-1

Groups

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Profiles (Lynxmotion).BETA Testers

Levels

...	...	@@ -1,1 +1,0 @@
1		-view

XWiki.StyleSheetExtension[0]

Caching policy

...	...	@@ -1,0 +1,1 @@
	1	+long

Code

@@ -1,0
          +1,13 @@
++div.cmdcnt
++{
++  display:table-row;
++}
++div.cmdpad
++{
++  display:table-cell;
++  padding:16px;
++}
++div.cmdtxt
++{
++  display:table-cell;
++}

Content Type

...	...	@@ -1,0 +1,1 @@
	1	+CSS

Name

...	...	@@ -1,0 +1,1 @@
	1	+DivTextIndentation

Parse content

...	...	@@ -1,0 +1,1 @@
	1	+No

Use this extension

...	...	@@ -1,0 +1,1 @@
	1	+currentPage

Changes for page LSS Communication Protocol

Summary

Details

Navigation

Recently Visited