Page Contents

• Firmware Versions
  • Version 367
  • Version 365
  • Version 362
  • Version 368
  • Version 369 (EXPERIMENTAL)
  • Version 370 (EXPERIMENTAL)

Firmware Versions

This section contains details about official firmware releases for the the Lynxmotion Smart Servos (LSS). Information includes release date (yyyy-mm-dd), and which new features / fixes / etc. were included. It also provides and any details about known issues or other warnings. If you are unsure how to proceed to update your LSS, please see this guide.

Version 367

Released 2019-10-07

• Fixes:
  • Minor improvements to handling of low-speed motion control. More updates coming soon on this front!
  • Encoder issue that would sometimes cause random fast motion, ignoring speed restrictions.

Version 365

Released 2019-09-12

• New commands:
  • New modifiers for position commands CH & CL. Allows moving "into" an object so it can be held without going into safe mode (limiting applied current in mA). CH holds position on collision and CL goes limp instead.
• Fixes:
  • Mode 255 would sometimes stay active or cause the LSS to respond to other servo IDs

Version 362

Released 2019-05-01

• Initial production version (first official release).
• New commands:
  • CLB/QLB to control the blinking of the RGB LED during various phases of motion.
• New features:
  • Added failsafe to go from RC mode back to serial mode by placing a HIGH signal (5 V DC) on RX for 30 s.
• Fixes:
  • Improved LED patterns for clarity.
  • ID is now kept during a firmware update.

Version 368

Released 2020-04-07

Many bug fixers and new features!

• QF now reports more details on version number (QF, QF1, QF2, QF3)
• Maximum motor duty cycle can be controlled using MMD, QMMD (min25%, max100% = 1023).
  • Can set it asymmetrical by passing 2 values separated by a comma (pos limit, neg limit).
• Motion filter was added for EM0.
  • Can be controlled with FPC, CFPC, QFPC.
• IPMS system was added for EM0.
  • Controlled with IPE and QIPE

Version 369 (EXPERIMENTAL)

Released 2021-06-18

• Fixed race condition in communication resulting in occasional corrupt responses. Most prevelant but not limited to the QN command. 
• Support for baud rates higher than 250k. We've certified 9600, 19200, 38400, 57600, 230400, 250000, 460800 and 500000 baud but 750000 and 921600 have also passed our testing. Only these exact baud rates are recognized by the servo. 
• Improvement in query response time of around 15% at 250k baud and much greater now that higher baud rates can be used.

Version 370 (EXPERIMENTAL)

Released 2021-09-20
This update is a major overhaul to the communication sub-system. Expect major performance improvements and bugs!

• Backwards compatibility is a priority. This firmware shouldn't affect existing code, please report any issues. Include a reproductible command sequence if possible.
• Allows multiple commands to be sent and received as a group
• Group commands can include multiple servos without bus conflict/contention
  • Ex. #0QD#5QD#10QD\r   -   queries 3 servos at once for position
  • #0QD0QC0#5QD0QC0   -   queries 2 servos at once for position and current (milliamps). 0 required to separate commands QD and QC
• Increase in supported baud rates up to 921k (adds 500k, 750k, 921.6k) with 2 and 3Mbit coming soon
• Auto baud rate (ABR) can be enabled (off by default):
  • Ex. #254ABR1   -   Enable baudrate detection on first byte received after power-up.
  • #254ABR2,30   -   Enable baudrate detection on first byte received after power-up. If no data for 30 seconds enable detection again on next byte.
  • Warning: ABR doesn't work well with LSS Config at the moment, updated LSS Config coming soon.
• Using #254QID120 can scan the entire bus at once for servos without conflict.
  • Servos will use a simple formula to delay their response: 200usec + <id> * 120usec, where <id> is their servo ID 0 to 253.
  • The first parameter (ex. 120) indicates how many milliseconds to delay between IDs and 120usec is a safe number.
  • Warning: #254QID with no parameter will still conflict to remain backward compatibility with LSS Config.
• Configure a slot# for each servo and using (ex.) #254QD can query all servos at once without conflict
  • Ex. We have 3 servos at ID 0, 5, and 10. We want to configure them to be slots 0, 1, and 2 respectively.
    • #254SLOTCOUNT3\r  - configure 3 slots on our bus
    • #0SLOT0\r   -   we don't really have to do this one, servos default to slot 0 on power-up
    • #5SLOT1\r   -   Servo ID5 to slot 1
    • #10SLOT2\r   -   Servo ID10 to slot 2
    • #254QD\r   -   Query all servos for position
    • #254QD0QC0\r   -   Query all servos for position and current (milliamps)
  • Note: You only need to configure slots once on power-up, #254<cmd> will offset all servo replies based on slot# after this is set.
  • Note: Why not just use servo ID as slot#? Many LSS bus setups are not using sequential IDs so it's more efficient to assign slot# then expect everyone to change their robot's logical servo IDs to be sequential.
• Fixed memory leak in MMD command
• General firmware cleanup & improvements