[Unitree Go2 EDU] Can't reach Jetson

General Discussion
1

Hi all,

I have an issue with a Go2 EDU regarding the onboard network connections:

Normally, there should be 3 devices found in the network:

  • the MCU (192.168.123.161)
  • the router (192.168.123.100)
  • and the Jetson (192.168.123.18)

For me, it is only possible to find (ping) the MCU (and to receive ROS Messages from it). Router and Jetson can’t be found. So there is also no way to ssh to the Jetson. This issue looks very similar to the one in this thread, but unfortunately there is no activity anymore.

I attached a monitor + keyboard via a usb-c dock and I starred at a blank screen. No activity at all. Triggering a restart of the Jetson works and gives the opportunity to enter the UEFI (and the UEFI shell). In the UEFI I was able to testwise configure a network connection and as long as the Jetson stays in the UEFI shell it is possible to ping the Jetson. So it should not be a hardware issue. Anyways, if I exit the UEFI shell and continue the boot process, the “connection” is lost (and the screen turns blank again). So it seems that the Jetson is not booting up properly?

Has anybody an idea on how to fix this? Thanks in advance.

2

Does your go2 have a custom router or is it just the base version?

Seems there is damage to the Jetson. Was there any fall or damage prior to this? Was it working prior?

3

Hey, thanks for the fast reply.

Does your go2 have a custom router or is it just the base version?

I didn’t found any information about modifications regarding the router, so I would assume it is the base version.

Seems there is damage to the Jetson. Was there any fall or damage prior to this? Was it working prior?

It was working at some point. The robot is a little bit older (roughly 1 year) and a few other people worked with it before. As far as I know, there was only one occasion which might be considered as a serious fall. But actually the robot looks and works fine (besides the issue described above). It is difficult to narrow down the event that “broke” the Jetson, as most people used the robot only with remote control. The robot was sent once to the manufacturer to fix the not working side-follow-system, which might also be issue related?

In case it really is a hardware issue: Is there a way to verify this? Some kind of software tool?

4

The base version doesn’t have a router that you can ping, it’s only for custom versions like the ones that have steamdeck.

That issue is only for PC1 and if the robot can be controlled via the remote then there should be no issue of repair from the manufacturer.

Most likely it’s a hardware issue or perhaps loose cabling. Contact support@mybotshop.de for more info on debugging.