Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FemtoBolt serial number not correctly read by ROS driver after update to firmware 1.1.2 #67

Open
bmegli opened this issue Dec 19, 2024 · 1 comment

Comments

@bmegli
Copy link

bmegli commented Dec 19, 2024

With 1.0.9 firmware:

  • driver correctly reads serial number of Femto Bolts
[12/19 10:40:27.701904][info][3412][DeviceManager.cpp:15] Current found device(s): (2)
[12/19 10:40:27.701911][info][3412][DeviceManager.cpp:24] 	- Name: Femto Bolt, PID: 0x066b, SN/ID: CL8R241010D, Connection: USB3.1
[12/19 10:40:27.701915][info][3412][DeviceManager.cpp:24] 	- Name: Femto Bolt, PID: 0x066b, SN/ID: CL838420121, Connection: USB2.1

After upgrading Femto Bolt firmware to 1.1.2

  • serial number is no longer correctly read by ROS driver
[12/19 12:51:03.377813][info][3245][DeviceManager.cpp:15] Current found device(s): (2)
[12/19 12:51:03.377827][info][3245][DeviceManager.cpp:24]       - Name: Femto Bolt, PID: 0x066b, SN/ID: CL000000000, Connection: USB3.1
[12/19 12:51:03.377832][info][3245][DeviceManager.cpp:24]       - Name: Femto Bolt, PID: 0x066b, SN/ID: CL000000000, Connection: USB3.1

With Orbbec Viewer

  • devices show also same "blank" SN/ID: CL000000000 in device list
  • after selecting device it shows the true serial number so it is still there
    • just some mechanism of reading it is broken

Some side information:

  • we needed to upgrade firmware at least to 1.1.0 to fix detection as USB 2.1 device
  • but we also need serial number to identify multiple Femto Bolts connected to same machine
@bmegli
Copy link
Author

bmegli commented Dec 19, 2024

Also, if not trying to identify Femto by serial number

  • ROS driver can read the serial number from device after connection
  • which again confirms that
    • one of mechanisms of identyfing serial number used by ROS driver during initial connection is broken
[ INFO] [1734613869.436675606]: Serial number: CL8R241010D
[ INFO] [1734613869.436697910]: Firmware version: 1.1.2
[ INFO] [1734613869.436722262]: Hardware version: 1.2
[ INFO] [1734613869.436739510]: device uid: 2-3.1-3
[ INFO] [1734613869.436753974]: device connection Type: USB3.1
[ INFO] [1734613869.436776726]: Current node pid: 5025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant