Forums Niryo One Troubleshooting Suggest Ethernet driver

Tagged: 

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • FindingNiryo
    Participant
    Post count: 88

    To enable exploration of more computationally intense ROS applications it would be great to have an Ethernet driver for NiryoOne. The Raspberry pi could relay control and status messages to/from the arm to a more powerful computer running ROS.

    Edouard Renard
    Keymaster
    Post count: 210

    I hope I didn’t misunderstood your question @findingniryo but it’s already possible to do that, no special Ethernet driver required. You just have to plug an Ethernet cable and connect the Raspberry Pi to another computer. All the low level hardware driver is already working out of the box.

    Then you can use solutions like ROS multi-master to make both machines work together.

    dave.knee
    Participant
    Post count: 5

    I tried to connect to Niryo One via ethernet. Could not get a connection. When I did ssh over WiFi and did ‘route -n’ it appeared that the link-local address 169.254.200.200 was assigned to wlan0 instead of enx… ethernet. Is there a way to straiten this out?

    dave.knee
    Participant
    Post count: 5

    I finally got the ethernet connection working. I am using
    an old PC that does not have WiFi. I tried a dongle but it
    didn’t work. One time it did manage to authenticate to
    another network, but it failed to associate. I think the
    signal must be too weak. I’ve had trouble with WiFi dongles
    before.

    I used ssh to connect to Niryo One over WiFi with a little
    pocket computer. It is ARM based so it will not run Niryo
    Studio. I gave it these commands:

    sudo ifconfig enxb827ebced4ae up
    sudo route add 169.254.200.201 device enxb827ebced4ae
    sudo ifconfig enxb827ebced4ae 169.254.200.200

    That worked. I do have the enx… interface listed in
    /etc/network/interfaces but that does not help. I’m not too
    good at networking. Each machine seems to use another way
    of handling networking. Is there something I could do to
    the Raspberry Pi so it would boot up with ifconfig and route
    properly set up and would not have to log in with ssh?

    Edouard Renard
    Keymaster
    Post count: 210

    Good news!

    You can use the systemd functionality to execute those command lines as soon as the Raspberry Pi boots. Here’s a tutorial.

    (or find a way to permanently add those network settings. I’m not expert in that and can’t really help you from my own experience)

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.