When I power it on, the LED sequence is red, yellow, green, red, and then the light turns off.
Using the LSS-Config software, I can detect COM3 and connect successfully. However, when I run “Scan All”, no servo ID is found.
If I press the button on the servo, the blue LED starts flashing. After about 10 seconds, the LED turns off again. During this time, I still cannot detect any servo ID when scanning.
I also receive the message/error shown in the attached image.
Could you please let me know what additional troubleshooting steps I should try? Is there anything else I can do to diagnose or recover the servo?
What are you using exactly to connect to the LSS servo ?
(LSS-Adapter .. other .. )
How many servos do you have and how many are connected when doing your test ?
The error usually mean you have more than one LSS connected and they are on the same ID.
You need to connect only one LSS at a time to setup the IDs, once they are set to different IDs you can connect them all.
According to the Android documentation, the recommended way to test the motor is to use the Lynxmotion LSS Configuration Software (LSS Config). The documentation specifically states:
“To test the motor, use the Lynxmotion LSS configuration software available from Lynxmotion.”
I followed this procedure and connected the servo through LSS Config, but the software is unable to detect any servo ID during the scan process. The COM port is detected correctly, but “Scan All” does not find any servo.
That’s a nice project, never heard about it.
It’s nice to see project that use our LSS smart servos.
So the LSS Config is made to setup the servos and it need a direct serial connections between your PC and the LSS.
I don’t know how their hardware work, there is a USB Type C on their board is that what you have.
Can you show me how the LSS is connected to what ? Pictures ?
This is my first time working with this device. Following the setup described in the documentation, the LSS-HT1 servo is connected to the M1 port, and the LED module is connected to the TEST RIG-1 port.
The servo and LED are powered separately through the 12V_IN_MOTOR and 12V_IN_LIGHT power inputs. The USB-A/USB-C port is connected to the device under test, and the USB-A/B port on the MEGA 2560 board is connected to my computer.
As far as I can tell, the hardware is connected according to the documentation. Could you please confirm whether this setup is correct?
Without knowing what their board do and how it use the serial port, it’s very hard for me to troubleshoot.
One thing I would try first is remove the Arduino MEGA board from it, just to make sure it’s not using the serial port & blocking you.
Is there something in the documentation that ask you to change the ID of the LSS ?
I also performed an additional test. I completely disconnected the LSS-HT1 servo and then ran “Scan All” in the LSS Configuration Software. Surprisingly, the result was exactly the same as when the LSS-HT1 was connected and powered on—the software output was identical to the screenshot I shared in my first post.
This makes me wonder whether the software is actually communicating with the servo at all, since disconnecting the servo does not appear to change the scan result in any way.
I have another question. If the MEGA 2560 board is removed from the setup, how should I connect the system to my computer?
At the moment, I am connecting my computer through the USB-A/B port on the MEGA 2560 board. If the MEGA board is not present, I am not sure what the correct connection method would be.
Could you please explain how the computer is supposed to communicate with the LSS-HT1 in that case?
Since this isn’t one of our products and I wasn’t familiar with it, I used Claude (an AI assistant) to help me go through the Android documentation and your controller firmware (gen2_production_v2.ino) so I could understand how the rig actually wires up. That cleared up what’s going on.
The short version: you’ve been scanning on the wrong COM port, and it’s not your fault, the documentation doesn’t make this obvious.
Your COM3 is the Arduino MEGA (its USB-B port). I went through the MEGA firmware and it only controls the lighting: it runs at 9600 baud and just switches the LED, night mode, A/V and buzzer outputs. There is no motor code in it and no serial passthrough to the servo. So the MEGA physically cannot talk to the LSS, which is exactly why “Scan All” finds nothing on COM3, and why unplugging the servo made no difference to your scan. LSS Config was never connected to the servo’s line.
The motor is on a separate connection. The USB Type-C port on the white board is a built-in USB-to-serial adapter wired straight to the LSS. That is the “PC to serial adapter to LSS” link that LSS Config needs. Right now you have that USB-C going to the phone, but it needs to go to your computer instead. (The phone connects to your host with its own USB cable for ADB, not through this port.)
Here’s how to proceed:
Unplug the USB-C from the phone and plug it directly into your computer.
Open Device Manager and look for a new COM port (a different number than COM3). Unplug and replug the USB-C to confirm which one it is. If no COM port appears, you likely need the USB-serial driver (CP210x / CH340 / FTDI, depending on the chip on the board).
In LSS Config, select that new COM port, set the baud rate to 115200 (the LSS default; the 9600 figure is only for the lighting board, don’t use it here), and run “Scan All.”
The motor should appear as ID 0. Please don’t change the ID, the rig is designed around ID 0.
Your servo looks healthy, by the way. The red, yellow, green LED sweep at power-on is just its normal boot sequence, so once you’re on the correct COM port it should respond.
Let me know what COM port shows up when you plug the USB-C into the PC, and what “Scan All” returns on it. That will tell us if we’re on the right track.
