When using Femto Bolt sensors with Depthkit Studio, it is necessary to have multiple sensors simultaneously connected to one host PC. I ran into an issue while trying to update the firmware on ten Femto Bolts where the firmware update elements in the OrbbecViewer interface are inaccessible, requiring the user to physically disconnect all but one sensor at a time, slowing down the update process considerably. To reproduce:
Connect multiple Femto Bolts to the same host PC
Open OrbbecViewer
Place one of the sensors in Recovery Mode to update firmware
Observe that while OrbbecViewer does detect that sensor in Recovery Mode, a different sensor becomes active in the Camera Settings interface, which occludes the firmware path field and update buttons (see attached screenshot)
The firmware path field and update buttons are not accessible until all sensors except for the one sensor which is in Recovery Mode are physically disconnected from the PC.
This requires access to the physical USB connection of each sensor, which makes firmware updating more challenging and slower, compared to the Azure Kinect Firmware Tool which allows all of the sensors connected to the PC to be updated in automatic succession with one command-line command.
When using Femto Bolt sensors with Depthkit Studio, it is necessary to have multiple sensors simultaneously connected to one host PC. I ran into an issue while trying to update the firmware on ten Femto Bolts where the firmware update elements in the OrbbecViewer interface are inaccessible, requiring the user to physically disconnect all but one sensor at a time, slowing down the update process considerably. To reproduce:
This requires access to the physical USB connection of each sensor, which makes firmware updating more challenging and slower, compared to the Azure Kinect Firmware Tool which allows all of the sensors connected to the PC to be updated in automatic succession with one command-line command.