Changes for page LSS-PRO Communication Protocol
Last modified by Eric Nantel on 2024/09/06 14:52
Change comment: There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -185,13 +185,19 @@ 185 185 186 186 == (% style="color:inherit; font-family:inherit" %)Communication Setup(%%) == 187 187 188 -====== (% style="color:inherit; font-family:inherit" %)__Reset__(%%) ====== 188 +|(% colspan="2" %)((( 189 +====== __Reset__ ====== 190 +))) 191 +| |((( 192 +Ex: #5RESET<cr> 189 189 190 - (%style="color:inherit;font-family:inherit"%)Ex:#5RESET<cr>191 - 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, note #2 for more details.194 +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, note #2 for more details. 195 +))) 192 192 197 +|(% colspan="2" %)((( 193 193 ====== (% style="color:inherit; font-family:inherit" %)__Default & confirm__(%%) ====== 194 - 199 +))) 200 +| |((( 195 195 (% style="color:inherit; font-family:inherit" %)Ex: #5DEFAULT<cr> 196 196 197 197 (% style="color:inherit; font-family:inherit" %)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. ... ... @@ -201,9 +201,12 @@ 201 201 (% style="color:inherit; font-family:inherit" %)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. 202 202 203 203 (% style="color:inherit; font-family:inherit" %)Note: After the CONFIRM command is sent, the servo will automatically perform a RESET. 210 +))) 204 204 212 +|(% colspan="2" %)((( 205 205 ====== (% style="color:inherit; font-family:inherit" %)__Update & confirm__(%%) ====== 206 - 214 +))) 215 +| |((( 207 207 (% style="color:inherit; font-family:inherit" %)Ex: #5UPDATE<cr> 208 208 209 209 (% style="color:inherit; font-family:inherit" %)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. ... ... @@ -213,7 +213,11 @@ 213 213 (% style="color:inherit; font-family:inherit" %)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. 214 214 215 215 (% style="color:inherit; font-family:inherit" %)Note: After the CONFIRM command is sent, the servo will automatically perform a RESET. 225 +))) 216 216 227 +(% class="wikigeneratedid" %) 228 +====== ====== 229 + 217 217 ====== (% style="color:inherit; font-family:inherit" %)__Confirm__(%%) ====== 218 218 219 219 (% style="color:inherit; font-family:inherit" %)Ex: #5CONFIRM<cr>