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.

)))

== Query Commands ==

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

48

49

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

50

1. Servo ID number as an integer

51

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

52

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

53

54

(((

55

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

)))

(((

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

60

61

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

62

1. Servo ID number as an integer

63

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

64

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

65

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

(((

Ex: *5QD1443<cr>

)))

Indicates that servo #5 is currently at 144.3 degrees.

72

)))

73

74

== Configuration Commands ==

75

76

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

77

78

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

79

1. Servo ID number as an integer

80

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

81

1. Configuration value in the correct units with no decimal

82

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.

87

88

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

89

90

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

= Command List =

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

96

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

97

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

98

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

99

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

100

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

101

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

102

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

103

See details below.

104

)))

105

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

106

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

107

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

108

| 12|**S**peed in **D**egrees| SD| QSD| CSD| ✓| ✓| tenths of degrees per second (ex 248 = 24.8 degrees per second)|

109

| 13|**S**peed in **R**PM| SR| QSR| CSR| ✓| ✓| rpm|

110

| 14|**A**ngular **A**cceleration| AA| QAA| CAA| ✓| ✓| tenths of degrees per second squared|

111

| 15|**A**ngular **D**eceleration| AD| QAD| CAD| ✓| ✓| tenths of degrees per second squared|

112

| 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

113

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

114

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

115

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

116

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

117

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

118

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

119

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

120

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

121

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

122

| 26|**Q**uery (general status)| | Q| | | ✓| none (integer from 1 to 8)|

123

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

124

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

125

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

136

137

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

142

143

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

144

145

Example: #5P1500T2500<cr>

146

147

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>

152

153

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.

154

155

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

160

161

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

166

167

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

168

169

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

170

171

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

172

173

Origin Offset Query (**QO**)

174

175

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

176

177

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

178

179

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.

184

185

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

186

187

Example: #5AR1800<cr>

188

189

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,

190

191

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

192

193

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

194

195

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

196

197

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:

198

199

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

200

201

Query Angular Range (**QAR**)

202

203

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

204

205

Configure Angular Range (**CAR**)

206

207

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.

208

209

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

214

215

Query Position in Pulse (**QP**)

216

217

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

218

219

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.

220

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.

221

222

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

223

224

Example: #5PD1456<cr>

225

226

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.

227

228

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

229

230

Query Position in Degrees (**QD**)

231

232

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

233

234

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

239

240

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

241

242

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

243

244

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

245

246

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

251

252

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

253

254

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

255

256

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

257

258

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

263

264

Query Speed in Degrees (**QSD**)

265

266

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

267

268

Note that the QSD query will return the current servo speed. Querying the last maximum speed value set using SD or CSD is not possible.

269

270

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.

275

276

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

281

282

Query Speed in Degrees (**QSR**)

283

284

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

285

286

Note that the QSD query will return the current servo speed. Querying the last maximum speed value set using SR or CSR is not possible.

287

288

Configure Speed in Degrees (**CSR**)

Ex: #5CSR45<cr>

Using the CSD command sets the servo's maximum speed which is saved in EEPROM. In the example above, the servo's maximum speed will be set to 45rpm. When the servo is powered on (or after a reset), the CSD value is used. Note that CSD and CSR are effectively the same, but allow the user to specify the speed in either unit. The last command (either CSR or CSD) is what the servo uses for that session.

293

294

__14. Angular Acceleration (**AA**)__

295

296

{More information coming soon}

Ex:

{Description coming soon}

301

302

Query Angular Acceleration (**QAA**)

Ex:

{Description coming soon}

307

308

Configure Angular Acceleration (**CAA**)

Ex:

{Description coming soon}

313

314

__15. Angular Deceleration (**AD**)__

315

316

{More information coming soon}

Ex:

{Description coming soon}

321

322

Query Angular Acceleration (**QAD**)

Ex:

{Description coming soon}

327

328

Configure Angular Acceleration (**CAD**)

Ex:

{Description coming soon}

333

334

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

339

340

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

341

342

Query LED Color (**QLED**)

343

344

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

345

346

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

347

348

Configure LED Color (**CLED**)

349

350

Configuring the LED color via the CLED command sets the startup color of the servo after a reset or power cycle.

351

352

__17. Identification Number__

353

354

A servo's identification number cannot be set "on the fly" and must be configured via the CID command described below. The factory default ID number for all servos is 1. Since smart servos are intended to be daisy chained, in order to respond differently from one another, the user must set different identification numbers. Servos with the same ID and baud rate will all receive and react to the same commands.

355

356

Query Identification (**QID**)

357

358

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

359

360

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

361

362

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. Standard / suggested baud rates are: 4800; 9600; 14400; 19200; 38400; 57600; 115200; 128000; 256000, 512000 bits per second. Servos are shipped with a baud rate set to 9600. The baud rates are currently restricted to those above

371

372

Query Baud Rate (**QB**)

373

374

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

375

376

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

377

378

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.

383

384

__19. Gyre Rotation Direction__

385

386

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

387

388

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

389

390

Query Gyre Direction (**QG**)

391

392

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

393

394

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

395

396

Configure Gyre (**CG**)

Ex: #5CG-1<cr>

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

401

402

__20. First / Initial Position (pulse)__

403

404

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.

405

406

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

407

408

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

409

410

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

411

412

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.

417

418

__21. First / Initial Position (Degrees)__

419

420

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.

421

422

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

423

424

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

425

426

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

427

428

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.

433

434

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

435

436

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

437

438

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

439

440

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

441

442

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

443

444

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)

445

446

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

447

448

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

449

450

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

451

452

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

453

454

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

455

456

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

457

458

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

459

460

Ex: #5Q<cr> might return *5Q_<cr>

461

462

{Description coming soon}

463

464

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

465

466

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

467

468

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

469

470

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

471

472

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

473

474

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.

475

476

__29. Query Current (QC)__

477

478

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

479

480

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>

485

486

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

487

488

**__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.

493

494

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

495

496

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.

497

498

**__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.

503

504

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

505

506

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.

507

508

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

513

514

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

515

516

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

517

518

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

519

520

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

521

522

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

523

524

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.

525

526

#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