• RAE

  • RAE cameras not connecting

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.

Hi Danilo. No luck I'm afraid:

$ lsusb | grep Gadget
$ lsusb | grep NCM
$ lsusb | grep Linux
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I have my laptop plugged into RAE via a USB-A to USB-C cable. I tried both the side and top USB-C ports on RAE. The screen still says "Connected to RobotHub".

    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).

      7 days later

      I've tried plugging into both the side and top ports of RAE with a USB cable, and neither produces any dmesg output. I've never had this cable give me issues before, but that being said, it's either RAE or the cable that is clearly not working properly.

      the issue seems to have been the cable; I'm now able to SSH into the robot using the cable. Hooray!

      The commands you suggested to stop robothub-ctl also works, and now when I launch the launch file, it doesn't give errors about acquiring the camera devices. Hooray x2!

      However, I'm still unable to view images from the robot on my own machine. that's because the robot's subnet (192.168.197.x) doesn't match my wifi network's (192.168.1.x). ROS2 doesn't support connections between robots on different subnets. I can think of two ways to fix this - 1) get RAE to connect to my wifi (without using robothub), which is something I want to do eventually anyway, 2) change the robot's IP address while connected over wifi so the subnet matches. Do you have advice on how to do either or both of these?

      Thanks!

        5 days later

        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.

          5 days later

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

          I agree on this point.

          robothub-ctl stop is not sufficient.

            a month later

            Newbee here, bough RAE to give to my children to play but its more complicated than expected(thinking will have an friendly android app), All connected and working with Robohub. I can move the robot and change colors of LED. Now I have some questions:

            • have no video streaming, should I install additional app or run some commands trough SSH

              edit: started streaming by itself, so now it is working…

            • the robot is not going straights, it drifts to the left

            • not sure how to use follow me option and "Edit face" is doing nothing.

              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!