Missing protocol/SDK support for Delta2c_PRO_D_V001 #95
Replies: 9 comments 7 replies
|
Hello, I'm afraid I don't have a Delta-2C LiDAR or any documentation for it. I have 3irobotix Delta-2 A, B and D only. If I find Delta 2C docs I will let you know. |
|
Hi makerspet Thank you very much for your response and for clarifying the situation regarding the Delta-2C model. Even though it is not officially supported in your library, your quick reply helped me focus my efforts on the correct model and troubleshoot the hardware connections properly. I truly appreciate your help and the work you do for the community. I will keep looking for the documentation, and if I manage to uncover anything useful, I will be sure to share it here. Thanks again! |
|
Hi makerspet, Thank you so much for the update and for your help. I apologize for the delay in responding—I missed your message earlier! I really appreciate your offer to look into this with your AI tools. Since there is no public documentation for the Delta-2C, having another pair of eyes on the serial data would be incredibly valuable. "I have attached a text file containing a sample of the serial output I am receiving from the device. I hope this helps in identifying the protocol or the "Start" command structure." Please let me know if you need any additional logs, such as different power-on sequences or data captured while the motor is running. I’m happy to provide whatever you need to help figure this out. Thanks again for your time and for supporting the community! Best regards, |
|
Hi poteytoman, I've asked Claude to check your lidar.txt (thank you). Long story short, you seem to be using the wrong baud rate. Please try recapturing data at 256000 or 250000 bps. Otherwise, it seems your Delta-2C does use the usual Delta-2A/B/G protocol. |
|
Hi Kaiaai, Thank you for looking into my lidar.txt file and for the suggestions. I have already tried recapturing the data using both 256,000 and 250,000 bps as you suggested, but unfortunately, I am still not getting any meaningful results. The data stream remains static and does not reflect any movement. I appreciate you taking the time to help me with this. Thanks again for your support! |
|
Hi, thanks for your help. The Lidar puck is spinning and reaches a target RPM, but I'm having trouble getting consistent range data from it. I’ve decided to take a break from this for now and look at it again later with fresh eyes. Thanks again for your time! |
|
Hey, just wanted to give you a quick update. I finally got the DELTA2C fully reverse engineered. The protocol is completely figured out now, frame structure, byte order, sampling offsets, all of it. Turns out the correct baud rate is 115200, and the motor needs around 2.9V to work properly. Data quality is actually really good once everything is dialed in. |
|
Alright bro, I’ve got two units of these lidars and they’re pretty similar. I’ve been experimenting with the supply voltage, and it looks like 2.9V isn’t very stable — you end up with fewer valid points. But at the correct baud rate of 115200, the readings stabilize considerably. |
|
@hapynfdj thank you very much for your contribution! My Claude has checked your repo and merged Delta-2C code into kaiaai/LDS with one tweak. Based on Delta-2C data captured independently, the resolution likely remains 0.25mm, does not change to 0.5mm from Delta-2A. |



Uh oh!
There was an error while loading. Please reload this page.
Hi everyone,
I'm working on an autonomous robotics project and I'm using the Delta2C-PRO_D_V001 model.
I noticed that this specific "Pro" model is missing from the supported series. I have been analyzing the serial output, and I am consistently receiving a steady stream of data, but I cannot seem to trigger the measurement data stream.
aa 00 09 11 61 ae 00 01 fa 02 ce
The device is powered, and the motor is spinning, but the distance/angle values in the packets remain constant. Does this model require a specific "Start" command? Any documentation would be greatly appreciated.
Thank you!
All reactions