LSS - Communication Protocol

1

The Lynxmotion Smart Servo (LSS) protocol was created in order to be as simple and straightforward as possible from a user perspective, while at the same time trying to stay compact and robust yet highly versatile. Almost everything one might expect to be able to configure for a smart servo motor is available.

2

3

=== Session ===

4

5

A "session" is defined as the time between when the servo is powered ON to when it is powered OFF or reset.

6

7

== Action Commands ==

8

9

Action commands are sent serially to the servo's Rx pin and must be set in the following format:

10

11

1. Start with a number sign # (U+0023)

12

1. Servo ID number as an integer

13

1. Action command (one to three letters, no spaces, capital or lower case)

14

1. Action value in the correct units with no decimal

15

1. End with a control / carriage return '<cr>'

(((

Ex: #5PD1443<cr>

Move servo with ID #5 to a position of 144.3 degrees.

21

22

Action commands cannot be combined with query commands, and only one action command can be sent at a time.

23

24

Action commands are session-specific, therefore once a servo is power cycled, it will not have any "memory" of previous actions or virtual positions (as described at the bottom of this page).

25

26

=== Action Modifiers ===

27

28

Two commands can be used as action modifiers only: Timed Move and Speed. The format is:

29

30

1. Start with a number sign # (U+0023)

31

1. Servo ID number as an integer

32

1. Action command (one to three letters, no spaces, capital or lower case)

33

1. Action value in the correct units with no decimal

34

1. Modifier command (one letter)

35

1. Modifier value in the correct units with no decimal

36

1. End with a control / carriage return '<cr>'

Ex: #5P1456T1263<cr>

Results in the servo rotating from the current angular position to a pulse position of 1456 in 1263 milliseconds.

41

42

Modified commands are command specific.

)))

(((

)))

== Configuration Commands ==

50

51

Configuration commands affect the servo's current session* but unlike action commands, configuration commands are written to EEPROM and are retained even if the servo loses power (therefore NOT session specific). Not all action commands have a corresponding configuration and vice versa. Certain configurations are retained for when the servo is used in RC model. More information can be found on the [[LSS - RC PWM page>>doc:LSS - RC PWM.WebHome]].

52

53

1. Start with a number sign # (U+0023)

54

1. Servo ID number as an integer

55

1. Configuration command (two to three letters, no spaces, capital or lower case)

56

1. Configuration value in the correct units with no decimal

57

1. End with a control / carriage return '<cr>'

Ex: #5CO-50<cr>

Assigns an absolute origin offset of -5.0 degrees (with respect to factory origin) to servo #5 and changes the offset for that session to -5.0 degrees.

62

63

Configuration commands are not cumulative, in that if two configurations are sent at any time, only the last configuration is used and stored.

64

65

*Important Note: the one exception is the baud rate - the servo's current session retains the given baud rate. The new baud rate will only be in place when the servo is power cycled.

== Query Commands ==

Query commands are sent serially to the servo's Rx pin and must be set in the following format:

70

71

1. Start with a number sign # (U+0023)

72

1. Servo ID number as an integer

73

1. Query command (one to three letters, no spaces, capital or lower case)

74

1. End with a control / carriage return '<cr>'

75

76

(((

77

Ex: #5QD<cr>Query position in degrees for servo #5

)))

(((

The query will return a value via the Tx pin with the following format:

82

83

1. Start with an asterisk (U+002A)

84

1. Servo ID number as an integer

85

1. Query command (one to three letters, no spaces, capital letters)

86

1. The reported value in the units described, no decimals.

87

1. End with a control / carriage return '<cr>'

(((

Ex: *5QD1443<cr>

)))

Indicates that servo #5 is currently at 144.3 degrees.

94

95

**Session vs Configuration Query**

96

97

By default, the query command returns the sessions' value; should no action commands have been sent to change, it will return the value saved in EEPROM from the last configuration command.

98

99

In order to query the value in EEPROM, add a '1' to the query command.

100

101

Ex: #5CSR20<cr> sets the maximum speed for servo #5 to 20rpm upon RESET (explained below).

102

103

After RESET: #5SR4<cr> sets the session's speed to 4rpm.

104

105

#5QSR<cr> would return *5QSR4<cr> which represents the value for that session.

106

107

#5QSR1<cr> would return *5QSR20<cr> which represents the value in EEPROM

)))

= Command List =

| 1|**L**imp| L| | | | ✓| none|

114

| 2|**H**alt & Hold| H| | | | ✓| none|

115

| 3|**T**imed move| T| | | | ✓| milliseconds| Modifier only

116

| 4|**S**peed| S| | | | ✓| microseconds / second| Modifier only

117

| 5|**M**ove in **D**egrees (relative)| MD| | | | ✓| tenths of degrees (ex 325 = 32.5 degrees; 91 = 9.1 degrees)|

118

| 6|**O**rigin Offset| O| QO| CO| ✓| ✓| tenths of degrees (ex 325 = 32.5 degrees; 91 = 9.1 degrees)|

119

| 7|**A**ngular **R**ange| AR| QAR| CAR| ✓| ✓| tenths of degrees (ex 325 = 32.5 degrees; 91 = 9.1 degrees)|

120

| 8|Position in **P**ulse| P| QP| | | ✓| microseconds|(((

121

See details below

122

)))

123

| 9|Position in **D**egrees| D| QD| | | ✓| tenths of degrees (ex 325 = 32.5 degrees; 91 = 9.1 degrees)|

124

| 10|**W**heel mode in **D**egrees| WD| QWD| | | ✓| tenths of degrees per second (ex 248 = 24.8 degrees per second)|

125

| 11|**W**heel mode in **R**PM| WR| QWR| | | ✓| rpm|

126

| 12|Max **S**peed in **D**egrees| SD| QSD| CSD| ✓| ✓| tenths of degrees per second (ex 248 = 24.8 degrees per second)|Add modifier "2" for instantaneous speed

127

| 13|Max **S**peed in **R**PM| SR| QSR| CSR| ✓| ✓| rpm|Add modifier "2" for instantaneous speed

128

| 14|**A**ngular **S**tiffness| AS| QAS| CAS| ✓| ✓|none|

129

| 15|//N/A (removed)//| | | | | | |

130

| 16|**LED** Color| LED| QLED| CLED| ✓| ✓| none (integer from 1 to 8)|0=OFF 1=RED 2=GREEN 3= BLUE 4=YELLOW 5=CYAN 6= 7=MAGENTA, 8=WHITE

131

| 17|**ID** #| ID| QID| CID| | ✓| none (integer from 0 to 250)|Note: ID 254 is a "broadcast" which all servos respond to

132

| 18|**B**aud rate| B| QB| CB| | ✓| none (integer)|

133

| 19|**G**yre direction (**G**)| G| QG| CG| ✓| ✓| none | Gyre / rotation direction where 1= CW (clockwise) -1 = CCW (counter-clockwise)

134

| 20|**F**irst Position (**P**ulse)| | QFP|CFP | ✓| ✓| none |

135

| 21|**F**irst Position (**D**egrees)| | QFD|CFD| ✓| ✓| none |

136

| 22|**T**arget (**D**egree) **P**osition| | QDT| | | ✓| tenths of degrees (ex 325 = 32.5 degrees; 91 = 9.1 degrees)|

137

| 23|**M**odel| | QM| | | | none (integer)|

138

| 24|Serial **N**umber| | QN| | | | none (integer)|

139

| 25|**F**irmware version| | QF| | | | none (integer)|

140

| 26|**Q**uery (general status)| | Q| | | ✓| none (integer from 1 to 8)| See command description for details

141

| 27|**V**oltage| | QV| | | ✓| tenths of volt (ex 113 = 11.3V; 92 = 9.2V)|

142

| 28|**T**emperature| | QT| | | ✓| degrees Celsius|

143

| 29|**C**urrent| | QC| | | ✓| tenths of Amps (ex 2 = 0.2A)|

| | | | | | | | |

| | | | | | | | |

= Details =

__1. Limp (**L**)__

Example: #5L<cr>

This action causes the servo to go "limp". The microcontroller will still be powered, but the motor will not. As an emergency safety feature, should the robot not be doing what it is supposed to or risks damage, use the broadcast ID to set all servos limp #254L<cr>.

154

155

__2. Halt & Hold (**H**)__

Example: #5H<cr>

This action overrides whatever the servo might be doing at the time the command is received (accelerating, moving continuously etc.) and causes it to stop immediately and hold that position.

160

161

__3. Timed move (**T**)__

162

163

Example: #5P1500T2500<cr>

164

165

Timed move can be used only as a modifier for a position (P) action. The units are in milliseconds, so a timed move of 2500 milliseconds would cause the servo to rotate from its current position to the desired position in 2.5 seconds. This command is in place to ensure backwards compatibility with the SSC-32 / 32U protocol.

__4. Speed (**S**)__

Example: #5P1500S750<cr>

170

171

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.

172

173

__5. (Relative) Move in Degrees (**MD**)__

Example: #5MD123<cr>

The relative move command causes the servo to read its current position and move the specified number of tenths of degrees in the corresponding position. For example if the servo is set to rotate CW (default) and an MD command of 123 is sent to the servo, it will cause the servo to rotate clockwise by 12.3 degrees. Negative commands would cause the servo to rotate in the opposite configured direction.

178

179

__6. Origin Offset Action (**O**)__

Example: #5O2400<cr>

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).

184

185

[[image:LSS-servo-default.jpg]]

186

187

In the second image, the origina, as well as the angular range (explained below) have been shifted by 240.0 degrees:

188

189

[[image:LSS-servo-origin.jpg]]

190

191

Origin Offset Query (**QO**)

192

193

Example: #5QO<cr> Returns: *5QO-13

194

195

This allows you to query the angle (in tenths of degrees) of the origin in relation to the factory zero position.

196

197

Configure Origin Offset (**CO**)

Example: #5CO-24<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.

202

203

__7. Angular Range (**AR**)__

204

205

Example: #5AR1800<cr>

206

207

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,

208

209

[[image:LSS-servo-default.jpg]]

210

211

Here, the angular range has been restricted to 180.0 degrees, or -90.0 to +90.0. The center has remained unchanged.

212

213

[[image:LSS-servo-ar.jpg]]

214

215

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:

216

217

[[image:LSS-servo-ar-o-1.jpg]]

218

219

Query Angular Range (**QAR**)

220

221

Example: #5QAR<cr> might return *5AR2756

222

223

Configure Angular Range (**CAR**)

224

225

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.

226

227

__8. Position in Pulse (**P**)__

Example: #5P2334<cr>

The position in PWM pulses was retained in order to be backward compatible with the SSC-32 / 32U protocol. This relates the desired angle with an RC standard PWM pulse and is further explained in the SSC-32 and SSC-32U manuals found on Lynxmotion.com. Without any modifications to configuration considered, and a ±90.0 degrees standard range where 1500 microseconds is centered, a pulse of 2334 would set the servo to 165.1 degrees. Valid values for P are [500, 2500]. Values outside this range are corrected to end points.

232

233

Query Position in Pulse (**QP**)

234

235

Example: #5QP<cr> might return *5QP2334

236

237

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.

238

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).

239

240

__9. Position in Degrees (**D**)__

241

242

Example: #5PD1456<cr>

243

244

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.

245

246

Larger values are permitted and allow for multi-turn functionality using the concept of virtual position.

247

248

Query Position in Degrees (**QD**)

249

250

Example: #5QD<cr> might return *5QD132<cr>

251

252

This means the servo is located at 13.2 degrees.

253

254

__10. Wheel Mode in Degrees (**WD**)__

Ex: #5WD900<cr>

This command sets the servo to wheel mode where it will rotate in the desired direction at the selected speed. The example above would have the servo rotate at 90.0 degrees per second clockwise (assuming factory default configurations).

259

260

Query Wheel Mode in Degrees (**QWD**)

261

262

Ex: #5QWD<cr> might return *5QWD900<cr>

263

264

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).

265

266

__11. Wheel Mode in RPM (**WR**)__

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).

271

272

Query Wheel Mode in RPM (**QWR**)

273

274

Ex: #5QWR<cr> might return *5QWR40<cr>

275

276

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).

277

278

__12. Speed in Degrees (**SD**)__

Ex: #5SD1800<cr>

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.

283

284

Query Speed in Degrees (**QSD**)

285

286

Ex: #5QSD<cr> might return *5QSD1800<cr>

287

288

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.

289

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:

290

291

|**Command sent**|**Returned value (1/10 °)**

292

|ex: #5QSD<cr>|Session value for maximum speed (set by latest SD/SR command)

293

|ex: #5QSD1<cr>|Configured maximum speed (set by CSD/CSR)

294

|ex: #5QSD2<cr>|Instantaneous speed (same as QWD)

295

|ex: #5QSD3<cr>|Target travel speed

296

297

Configure Speed in Degrees (**CSD**)

Ex: #5CSD1800<cr>

Using the CSD command sets the servo's maximum speed which is saved in EEPROM. In the example above, the servo's maximum speed will be set to 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.

302

303

__13. Speed in RPM (**SR**)__

Ex: #5SD45<cr>

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.

308

309

Query Speed in Degrees (**QSR**)

310

311

Ex: #5QSR<cr> might return *5QSR45<cr>

312

313

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.

314

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:

315

316

|**Command sent**|**Returned value (1/10 °)**

317

|ex: #5QSR<cr>|Session value for maximum speed (set by latest SD/SR command)

318

|ex: #5QSR1<cr>|Configured maximum speed (set by CSD/CSR)

319

|ex: #5QSR2<cr>|Instantaneous speed (same as QWR)

320

|ex: #5QSR3<cr>|Target travel speed

321

322

Configure Speed in RPM (**CSR**)

Ex: #5CSR45<cr>

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.

327

328

__14. Angular Stiffness (AS)__

329

330

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.

331

332

A positive value of "angular stiffness":

333

334

* The more torque will be applied to try to keep the desired position against external input / changes

335

* The faster the motor will reach its intended travel speed and the motor will decelerate faster and nearer to its target position

336

337

A negative value on the other hand:

338

339

* Causes a slower acceleration to the travel speed, and a slower deceleration

340

* Allows the target position to deviate more from its position before additional torque is applied to bring it back

341

342

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.

Ex: #5AS-2<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.

Ex: #5QAS<cr>

Queries the value being used.

Ex: #5CAS<cr>

Writes the desired angular stiffness value to memory.

355

356

__15. N/A (removed)__

357

358

This command has been removed.

359

360

__16. RGB LED (**LED**)__

Ex: #5LED3<cr>

This action sets the servo's RGB LED color for that session.The LED can be used for aesthetics, or (based on user code) to provide visual status updates. Using timing can create patterns.

365

366

0=OFF 1=RED 2=GREEN 3= BLUE 4=YELLOW 5=CYAN 6= 7=MAGENTA, 8=WHITE

367

368

Query LED Color (**QLED**)

369

370

Ex: #5QLED<cr> might return *5QLED5<cr>

371

372

This simple query returns the indicated servo's LED color.

373

374

Configure LED Color (**CLED**)

375

376

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.

377

378

__17. Identification Number__

379

380

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.

381

382

Query Identification (**QID**)

383

384

EX: #QID<cr> might return *QID5<cr>

385

386

When using the query ID command, it is best to only have one servo connected and thus receive only one reply.

387

388

Configure ID (**CID**)

Ex: #CID5<cr>

Setting a servo's ID in EEPROM is done via the CID command. All servos connected to the same serial bus will be assigned that ID. In most situations each servo must be set a unique ID, which means each servo must be connected individually to the serial bus and receive a unique CID number. It is best to do this before the servos are added to an assembly. Numbered stickers are provided to distinguish each servo after their ID is set, though you are free to use whatever alternative method you like.

__18. Baud Rate__

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.

397

\*: 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.

398

399

Query Baud Rate (**QB**)

400

401

Ex: #5QB<cr> might return *5QB9600<cr>

402

403

Querying the baud rate is used simply to confirm the CB configuration command before the servo is power cycled.

404

405

Configure Baud Rate (**CB**)

Ex: #5CB9600<cr>

Sending this command will change the baud rate associated with servo ID 5 to 9600 bits per second.

410

411

__19. Gyre Rotation Direction__

412

413

"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).

414

415

{images showing before and after with AR and Origin offset}

416

417

Query Gyre Direction (**QG**)

418

419

Ex: #5QG<cr> might return *5QG-1<cr>

420

421

The value returned above means the servo is in a counter-clockwise gyration.

422

423

Configure Gyre (**CG**)

Ex: #5CG-1<cr>

This changes the gyre direction as described above and also writes to EEPROM.

428

429

__20. First / Initial Position (pulse)__

430

431

In certain cases, a user might want to have the servo move to a specific angle upon power up. We refer to this as "first position". The factory default has no first position value stored in EEPROM and therefore upon power up, the servo remains limp until a position (or hold command) is assigned. FP and FD are different in that FP is used for RC mode only, whereas FD is used for serial mode only.

432

433

Query First Position in Pulses (**QFP**)

434

435

Ex: #5QFP<cr> might return *5QFP1550<cr>

436

437

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").

438

439

Configure First Position in Pulses (**CFP**)

Ex: #5CP1550<cr>

This configuration command means the servo, when set to RC mode, will immediately move to an angle equivalent to having received an RC pulse of 1550 microseconds upon power up. Sending a CFP command without a number results in the servo remaining limp upon power up (i.e. disabled).

444

445

__21. First / Initial Position (Degrees)__

446

447

In certain cases, a user might want to have the servo move to a specific angle upon power up. We refer to this as "first position". The factory default has no first position value stored in EEPROM and therefore upon power up, the servo remains limp until a position (or hold command) is assigned. FP and FD are different in that FP is used for RC mode only, whereas FD is used for serial mode only.

448

449

Query First Position in Degrees (**QFD**)

450

451

Ex: #5QFD<cr> might return *5QFD64<cr>

452

453

The reply above indicates that servo with ID 5 has a first position pulse of 1550 microseconds.

454

455

Configure First Position in Degrees (**CFD**)

Ex: #5CD64<cr>

This configuration command means the servo, when set to serial mode, will immediately move to 6.4 degrees upon power up. Sending a CFD command without a number results in the servo remaining limp upon power up.

460

461

__22. Query Target Position in Degrees (**QDT**)__

462

463

Ex: #5QDT<cr> might return *5QDT6783<cr>

464

465

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>).

466

467

__23. Query Model (**QM**)__

468

469

Ex: #5QM<cr> might return *5QM11<cr>

470

471

This reply means the servo model is 1.1, meaning high speed servo, first revision. 1=HS (high speed) 2=ST (standard) 3=HT (high torque)

472

473

__24. Query Serial Number (**QN**)__

474

475

Ex: #5QN<cr> might return *5QN~_~_<cr>

476

477

The number in the response is the servo's serial number which is set and cannot be changed.

478

479

__25. Query Firmware (**QF**)__

480

481

Ex: #5QF<cr> might return *5QF11<cr>

482

483

The integer in the reply represents the firmware version with one decimal, in this example being 1.1

484

485

__26. Query Status (**Q**)__

486

487

Ex: #5Q<cr> might return *5Q6<cr>, which indicates the motor is holding a position.

488

489

|*Value returned|**Status**|**Detailed description**

490

|ex: *5Q0<cr>|Unknown|LSS is unsure

491

|ex: *5Q1<cr>|Limp|Motor driving circuit is not powered and horn can be moved freely

492

|ex: *5Q2<cr>|Free moving|Motor driving circuit is not powered and horn can be moved freely

493

|ex: *5Q3<cr>|Accelerating|Increasing speed from rest (or previous speeD) towards travel speed

494

|ex: *5Q4<cr>|Traveling|Moving at a stable speed

495

|ex: *5Q5<cr>|Deccelerating|Decreasing speed towards travel speed towards rest

496

|ex: *5Q6<cr>|Holding|Keeping current position

497

|ex: *5Q7<cr>|Stepping|Special low speed mode to maintain torque

498

|ex: *5Q8<cr>|Outside limits|More details coming soon

499

|ex: *5Q9<cr>|Stuck|Motor cannot perform request movement at current speed setting

500

|ex: *5Q10<cr>|Blocked|Similar to stuck, but the motor is at maxiumum duty and still cannot move (i.e.: stalled)

501

502

__27. Query Voltage (**QV**)__

503

504

Ex: #5QV<cr> might return *5QV112<cr>

505

506

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).

507

508

__28. Query Temperature (**QT**)__

509

510

Ex: #5QT<cr> might return *5QT564<cr>

511

512

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.

513

514

__29. Query Current (QC)__

515

516

Ex: #5QC<cr> might return *5QC140<cr>

517

518

The units are in milliamps, so in the example above, the servo is consuming 140mA, or 0.14A.

__**RESET**__

Ex: #5RESET<cr> or #5RS<cr>

523

524

This command does a "soft reset" (no power cycle required) and reverts all commands to those stored in EEPROM (i.e. configuration commands).

525

526

**__DEFAULT __**__& **CONFIRM**__

Ex: #5DEFAULT<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.

531

532

EX: #5DEFAULT<cr> followed by #5CONFIRM<cr>

533

534

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.

535

536

Note that after the CONFIRM command is sent, the servo will automatically perform a RESET.

537

538

**__UPDATE __**__& **CONFIRM**__

Ex: #5UPDATE<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.

543

544

EX: #5UPDATE<cr> followed by #5CONFIRM<cr>

545

546

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.

547

548

Note that after the CONFIRM command is sent, the servo will automatically perform a RESET.

549

550

=== Virtual Angular Position ===

{In progress}

A "virtual position" is one which allows for multiple rotations of the output horn, moving the center position and more. The "absolute position" would be the angle of the output shaft with respect to 360.0 degrees.

555

556

[[image:LSS-servo-positions.jpg]]

557

558

Example: Gyre direction / rotation is positive (clockwise), and origin offset has not been modified.

559

560

#1D-300<cr> The servo is commander to move to -30.0 degrees (green arrow)

561

562

#1D2100<cr> This second position command is sent to the servo, which moves it to 210.0 degrees (orange arrow)

563

564

#1D-4200<cr> The servo rotates counterclockwise to a position of -420 degrees (red arrow), which means one full rotation of 360 degrees and (420.0-360.0) stopping at an absolute position of 60.0 degrees, but virtual position of -420.0.

565

566

Although the final position would be the same as if the servo were commanded to move to -60.0 degrees, it is in fact at -420.0 degrees.

567

568

#1D4800<cr> This new command is sent which would then cause the servo to rotate from -420.0 degrees to 480.0 degrees, which would be a total of 900 degrees of clockwise rotation, or 2.5 complete rotations.

Wiki source code of LSS - Communication Protocol

Navigation

Recently Visited