RAE cameras not connecting

Yea, USB-C is not practical when using the robot (there I would suggest using robot AP like described in github repo) - but it is probably easiest way to set the robot up for use when you want to go around using RH agent - so that is why I suggested it.

I am struggling to recreate your issue. Can you show me what lsusb command returns when you plug in your robot to USB? It seems that USB is just not recognizing the device. For example this is what lsusb returns for me:

$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0bda:58e5 Realtek Semiconductor Corp. EasyCamera
Bus 001 Device 017: ID 1d6b:0103 Linux Foundation NCM (Ethernet) Gadget
Bus 001 Device 003: ID 046d:c328 Logitech, Inc. Corded Keyboard K280e
Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
Bus 001 Device 002: ID 046d:c08b Logitech, Inc. G502 SE HERO Gaming Mouse
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Where this line shows that it finds the robot:

Bus 001 Device 017: ID 1d6b:0103 Linux Foundation NCM (Ethernet) Gadget

Since it seems to me that you are using Ubuntu 20.04 it could write it in another way, but it should not be anything radically different - for example in container I spun up it shows it like this:
Bus 001 Device 018: ID 1d6b:0103 Luxonis USB Ethernet

I downloaded the luxonis/rae-ros-robot:humble-latest image and uploaded to RAE via the USB-C. I notice that when issuing the command robothub-ctl stop, the Inet4 will disappear and I cannot use the local network connection to talk to RAE to select the CONTROL button on its special webpage. Although all of configuration files are correct. I lauched the test script via the USB-C with ssh connection and after running the docker image

ros2 launch rae_bringup robot.launch.py

It successfully initialized most of the segments but failed at the camera with the reason at the bottom of this log section. This could be the cause of the same camera streaming problem reported. I hope this is the the good hint to fix in the software.

[component_container-2] [INFO] [1696266244.044478588] [rae]: Camera with MXID: xlinkserver and Name: 127.0.0.1 connected!

[component_container-2] [INFO] [1696266244.047751620] [rae]: PoE camera detected. Consider enabling low bandwidth for specific image topics (see readme).

[component_container-2] [INFO] [1696266244.128595264] [rae]: Device type: RAE

[component_container-2] [INFO] [1696266244.458754197] [rae]: Reading calibration from: /ws/src/rae/rae_bringup/config/cal.json

[component_container-2] [INFO] [1696266244.468826589] [rae]: Pipeline type: RAE

[component_container-2] [INFO] [1696266244.637219902] [rae]: Finished setting up pipeline.

[component_container-2] [ERROR] [1696266247.999111878] [rae_container]: Component constructor threw an exception: Cannot use both isp & video/preview/still outputs at once at the moment (startPipeline)

[ERROR] [launch_ros.actions.load_composable_nodes]: Failed to load node 'rae' of type 'depthai_ros_driver::Camera' in container '/rae_container': Component constructor threw an exception: Cannot use both isp & video/preview/still outputs at once at the moment (startPipeline)

For the second trial with different image, I pulled the luxonis/rae-ros-robot:humble image and uploaded to RAE via the USB-C. After accessed to the RAE using SSH and run the docker image of the luxonis/rae-ros-robot:humble. This time I was able to successfully exercise 2 test script files of ros2 launch rae_bringup robot.launch.py and ros2 launch rae_bringup bringup.launch.py. I was able to check out the motor operation with the commands of ros2 run rae_hw test_motors 5.0 16.0 16.0 756 756 32 32 and ros2 run rae_hw test_maxspeed 1.0 756 756. This is a very good progress so far. The test seemed to verify the cameras with good results, too. But the video streaming test has not yet been done. One critical issue with the robothub-ctl stop command is that it shutdown the ipv4 address of the wireless network link wlp1s0. This prevents the additional software modules to be downloaded and uppdated to RAE. The wireless connection via RAE_IP:9010 also cannot be estalished to use the wireless control method. One this issue is fixed, the remote programming and control can be done for RAE besides the RobotHub method when it is fixed as well. The missing of the robothub-core is a road block for us to use the RobotHub now. Hopefully the Luxonis team came up with a solution soon. Thanks.

Below is the sequene of commands I used to turn off the RobotHub connection and return to RAE word displayed on the screen. This is done via the USB-C connection from the laptop/ desktop Windows 11 or Linux. From the terminal box, type:

1. ssh root@192.168.197.55 -> response: root@keembay:~#
2. robothub-ctl stop -> response: root@keembay:~#
3. robothub-ctl startup disable -> response: disabling systemd services... ->disabled-> root@keembay:~#
4. Power off the RAE
5. Power back on the RAE. This time the word of RAE should display on the screen.

forty-nights

That is weird, working with many prototypes I never had that issue with the robot before. For some reason it is indeed just not figuring out that it is connected to the robot. I will have to check with other people if anyone had similar issue.

echo 'SUBSYSTEM=="usb", ATTRS{idVendor}=="03e7", MODE="0666"' | sudo tee /etc/udev/rules.d/80-movidius.rules
sudo udevadm control --reload-rules && sudo udevadm trigger

I would try adding udev rules and reboot the host device and see if that helps too (commands shown above).

Hi forty-nights
I think this might help. Skip the last part though

Thanks,
Jaka

I've recently seen a similar error from the initial post. Reboot helped.

However, I wonder if there's a command that allows to force release all the devices.

NikolayNikolov
We are working to make rae more accessible with new updates.

• try using chrome if you have not. I found things work as better on chrome.
• that happens when using the manual control?
• Does preview show? Sometimes the follow-me mode won't work unless there is image preview showing as well.

Thanks,
Jaka

jakaskerl

yes I use Chrome

when using manual controls it's the same (pressing the forward arrow but going in a left curve)

after several tests each time is different. Follow me works, but it's hard to follow because it can't go in a straight line. Sometimes both cameras stream, sometimes only the rear, and sometimes neither.

"We are working to make rae more accessible with new updates."

Great, my son is 6 years old and he really enjoys the robot!