Rosbot XL (Jetson Nano): Problem updating SBC, How to Start instruction issue

Software
1

Good morning,

We have a Rosbot XL with a Raspberry Pi 4, and we updated it to a Jetson Nano B01 for computational needs. After we did all the electrical installation (using adapters) everything worked fine (we could boot using the Rosbot XL energy).

Then we proceed to configure the robot using the quick start guide. After the final step in step 5 “Robot configs installation,” the system automatically reboots. After reboots, the system enters in an infinite loop and never boots.

Please let us know if there are any tips related to these steps to avoid this problem.

Best,
Alberto

2

Hello @avillaj88,
it seems to me that a similar issue was recently discussed in this thread.

I would like you to read it and let me know if the problem has been solved.

3

Thank you for your answer, it works

1 Like
4

Hello @RafalGorecki,
We are facing a new problem. This time is related to microros. After following all the installation steps from the tutorial we arrived at the final which was to use the teleop, the robot did not move and the LED 2 was toggling in red. Then we tried the functional setup that we have with the Raspberry Pi and the same results.

We tried to flash the firmware with different docker versions and the results were the same the robot does not move and the LED 2 always toggling.

Finally, we tried with the repository: GitHub - husarion/rosbot-xl-autonomy: Using SLAM Toolbox and Nav2 with ROSbot XL, and when we ran the command “just start-rosbot” the command line showed the following error: “dependency failed to start: rosbot-xl-autonomy–1 is unhealthy”.

Please let us know if there are any tips related to these issues.

Best Alberto

5

Hello @avillaj88,
red diode
The red diode flashes until the computer connects to the device. So until the rosbot_ros driver (and especially the microros node) is launched, the diode will flash red.

So the question is whether the driver is launched. If so and the diode is still flashing red, it probably means problems. Firstly, I would advise:

  1. Flash the firmware
  2. Make sure that the static address is set on the Ethernet port. Communication in ROSbot XL takes place on port 8888 to IP address 192.168.77.2/24. Make sure that no other process is occupying this port.

rosbot-xl-autonomy
Have you made any changes? I’ve just tested the foxglove branch and everything works fine. If you haven’t made any changes, the culprit is most likely the lack of connection to the driver with the hardware discussed above.

The second thing that can cause problems is if you already have the driver running in another process (container, snap), in which case please stop them.

Regards

6

Hello @avillaj88,
I just found the ethernet interface name in Jetpack 6.x.x has unusual name of ethernet port.
Instead of eth0 there is a enP8p1s0 (you can check interface using ip a command), so our setup script did not configurate this inferface correctly. You should probably go to /etc/netplan/01-network-manager-all.yaml
and change

      match:
        name: eth*

in to:

      match:
        name: enP8p1s*

Then apply these changes using sudo netplan apply -d

Let me know if that was the main reason.
Regards

7

Hello @RafalGorecki,

Thank you so mouch for your quick response. Basically, the problem was the ip adress. The issue is already fixed.

Best,

Alberto

1 Like