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)
2. Servo ID number as an integer
3. Action command (one to three letters, no spaces, capital or lowercase from a subset of action commands below)
4. Action value in the correct units with no decimal
5. Modifier command (one or two letters from the list of modifiers below)
6. Modifier value in the correct units with no decimal
7. End with a carriage return \r or <cr> Unicode Character (U+000D)

Ex: #5D1800T1500<cr>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).

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 # (Unicode Character: U+0023)
2. Servo ID number as an integer
3. Query command (one to four letters, no spaces, capital or lower case)
4. End with a carriage return \r or <cr> Unicode Character (U+000D)

Ex: #5QD<cr> Query the position in (tenth of) degrees for servo with ID #5The query will return a serial string (almost instantaneously) via the servo's Tx pin with the following format:

1. Start with an asterisk * (Unicode Character: U+0023)
2. Servo ID number as an integer
3. Query command (one to four letters, no spaces, capital letters)
4. The reported value in the units described, no decimals.
5. 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 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: *5QD1800<cr>This indicates that servo #5 is currently at 180.0 degrees (1800 tenths of degrees).

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. 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)
2. Servo ID number as an integer
3. Configuration command (two to four letters, no spaces, capital or lower case)
4. Configuration value in the correct units with no decimal
5. 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 QueryBy 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. 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> 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

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). 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)#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. Although the final physical position would be the same as if the servo were commanded to move to -60.0 degrees, the servo is in fact at -420.0 degrees. #1D4800<cr> This new command is sent which would then cause the servo to rotate from -420.0 degrees to 480.0 degrees (blue arrow), which would be a total of 900 degrees of clockwise rotation, or 2.5 complete rotations. #1D3300<cr> would cause the servo to rotate from 480.0 degrees to 330.0 degrees (yellow arrow).If 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°].