Home Forums Eye Tracking Devices No connection to TobiiRex on Ubuntu

Viewing 14 posts - 1 through 14 (of 14 total)
  • Author
    Posts
  • #1548
    dt
    Participant

    Hello everyone,

    We try to get Tobii Rex to run on Linux Ubuntu.
    So we changed the firmware on Tobii Rex on Windows7:

    \Eyetracking\tobii\TobiiGazeSdk-CApi-4.0.3.627-Win64\tools>fwupgrade --auto rexdevlaptop_firmware_1.0.5.251
    69.20130705.1446.root.tobiipkg --no-version-check
    Tobii Firmware Upgrade Tool
    Automatically selected eye tracker tet-usb://REXDL-010104501771
    Valid Tobii package for g5
    
    WAITING
    
    UPLOADING FILE
    
    UPGRADING
     MD5_CHECK_OK
    SYS_IMG_UPDATED
    APPS_IMG_UPDATED
    CONF_BASE_EXTRACTED
    UPGRADE_SUCCESS
    
    DONE, rebooting 
    

    Then we plugged in TobiiRex on Linux Ubuntu on USB 2.0-Port.

    (When we use TobiiRex on Ubuntu, we recognized, that the TobiiRex-Hardware will be disconnected every 5 minutes or so and automaticly reconnects again. Is that a normal behaviour, that Tobii-Rex in USB-TCP-Mode disconnects after a defined period of time?)

    The Tobii-Hardware was identified as USB-Ethernet-Technology from Linux-Hardwarecontroller:

    lsusb 
    Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 006 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
    Bus 006 Device 002: ID 04d9:1603 Holtek Semiconductor, Inc. Keyboard
    Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 001 Device 008: ID 0525:a4a1 Netchip Technology, Inc. Linux-USB Ethernet Gadget
    Bus 001 Device 002: ID 0bda:0181 Realtek Semiconductor Corp. 
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    sudo lsusb -v -d 0525:a4a1
    Bus 001 Device 008: ID 0525:a4a1 Netchip Technology, Inc. Linux-USB Ethernet Gadget
    Device Descriptor:
      bLength                18
      bDescriptorType         1
      bcdUSB               2.00
      bDeviceClass            2 Communications
      bDeviceSubClass         0 
      bDeviceProtocol         0 
      bMaxPacketSize0        64
      idVendor           0x0525 Netchip Technology, Inc.
      idProduct          0xa4a1 Linux-USB Ethernet Gadget
      bcdDevice            3.16
      iManufacturer           1 Tobii Technology AB
      iProduct                2 Tobii IS Eye Tracker
      iSerial                 0 
      bNumConfigurations      1
      Configuration Descriptor:
        bLength                 9
        bDescriptorType         2
        wTotalLength           80
        bNumInterfaces          2
        bConfigurationValue     1
        iConfiguration          0 
        bmAttributes         0xc0
          Self Powered
        MaxPower              500mA
        Interface Descriptor:
          bLength                 9
          bDescriptorType         4
          bInterfaceNumber        0
          bAlternateSetting       0
          bNumEndpoints           1
          bInterfaceClass         2 Communications
          bInterfaceSubClass      6 Ethernet Networking
          bInterfaceProtocol      0 
          iInterface              3 CDC Ethernet Control Model (ECM)
          CDC Header:
            bcdCDC               1.10
          CDC Union:
            bMasterInterface        0
            bSlaveInterface         1 
          CDC Ethernet:
            iMacAddress                      5 2EBF05F4BCCE
            bmEthernetStatistics    0x00000000
            wMaxSegmentSize               1514
            wNumberMCFilters            0x0000
            bNumberPowerFilters              0
          Endpoint Descriptor:
            bLength                 7
            bDescriptorType         5
            bEndpointAddress     0x81  EP 1 IN
            bmAttributes            3
              Transfer Type            Interrupt
              Synch Type               None
              Usage Type               Data
            wMaxPacketSize     0x0010  1x 16 bytes
            bInterval               9
        Interface Descriptor:
          bLength                 9
          bDescriptorType         4
          bInterfaceNumber        1
          bAlternateSetting       0
          bNumEndpoints           0
          bInterfaceClass        10 CDC Data
          bInterfaceSubClass      0 Unused
          bInterfaceProtocol      0 
          iInterface              0 
        Interface Descriptor:
          bLength                 9
          bDescriptorType         4
          bInterfaceNumber        1
          bAlternateSetting       1
          bNumEndpoints           2
          bInterfaceClass        10 CDC Data
          bInterfaceSubClass      0 Unused
          bInterfaceProtocol      0 
          iInterface              4 CDC Ethernet Data
          Endpoint Descriptor:
            bLength                 7
            bDescriptorType         5
            bEndpointAddress     0x85  EP 5 IN
            bmAttributes            2
              Transfer Type            Bulk
              Synch Type               None
              Usage Type               Data
            wMaxPacketSize     0x0200  1x 512 bytes
            bInterval               0
          Endpoint Descriptor:
            bLength                 7
            bDescriptorType         5
            bEndpointAddress     0x06  EP 6 OUT
            bmAttributes            2
              Transfer Type            Bulk
              Synch Type               None
              Usage Type               Data
            wMaxPacketSize     0x0200  1x 512 bytes
            bInterval               0
    Device Qualifier (for other device speed):
      bLength                10
      bDescriptorType         6
      bcdUSB               2.00
      bDeviceClass            2 Communications
      bDeviceSubClass         0 
      bDeviceProtocol         0 
      bMaxPacketSize0        64
      bNumConfigurations      1
    Device Status:     0x0001
      Self Powered
    

    But if we try to get run the samples or to identify the Hardware with fwupgrade on Ubuntu, we get: 205 no eye tracker found:

    ./fwupgrade --auto --info-only
    Tobii Firmware Upgrade Tool
    205 No eye tracker could be found
    No tracker connected

    Eventually we tried to use the Eyetracker-Browser (from Analytics-SDK).
    Hardware will be found, it’s possible to change the firmware (so it can communicate with the hardware), but when we try to run an Example, we will get the 205-error.

    We couldn’t debug tobiigaze_get_connected_eye_tracker(url, URL_SIZE, &error_code); because of missing source-files.

    On Windows7 it works fine…

    This try was the second one on Ubuntu. The First try to change from Windows-USB- to Linux USB-TCP-Connection was successful (MinimalTracker was running on Ubuntu).
    Then we changed back to Windows and again to Linux, then we had that problem described above.

    Help is greatly appreciated.

    #1553
    Anders
    Participant

    Hi dt,

    for your first question, the issue with the REX losing connection and reconnecting again every five minutes or so: the answer is no, that is not how it should work. Losing the connection is a bad thing — even if it picks up again automatically — not only because it will affect the eye tracking reliability but also because the user calibration will be lost. Chances are that this issue is connected to the second issue though, so please see if it persists after solving #2 and contact support if that is the case.

    Second, judging from your lsusb output, the device is identified correctly as a virtual ethernet interface, but it might not be fully configured yet — it can differ between Linux distros and versions.

    You can check whether the eye tracker has been mounted as a network interface by issuing the command ifconfig -a. There should be an interface called usb0 or similar, and if you are lucky then there will also be a line starting with inet addr that shows the IP address bound to the interface. If there is no such line, use the command sudo dhclient usb0 to assign an address and then try the ifconfig again to verify that there is now an address.

    At this point it should be possible to run ./fwupgrade --auto --info-only, just like you did, without receiving the 205 error.

    #1558
    Stephan Voss
    Participant

    Hi Anders,

    i’m writing on behalf of dt as we’re working in a team.
    I followed your instructions, and ifconfig -a showed the device as usb0 and also an IP address (172.28.195.2), so there was nothing to do.
    When i ran ./fwupgrade --auto --info-only there was the same problem again (error 205). So unfortunately this didn’t solve our problem.

    Do you have any other ideas?
    Thanks in advance,
    Stephan

    #1700
    Anders
    Participant

    Hi Stephan,
    can you ping the device? (at 172.28.195.1)
    are you using the latest version of the Gaze SDK?

    #1705
    dt
    Participant

    Hello Anders,
    yes, I can ping the device at 172.28.195.1 .
    We’re using the Gaze SDK at version 4.0.3.627, which is as far as I know the latest.

    #1747
    Anders
    Participant

    Hi dt, Stephan,
    I’ve talked to the firmware team and they have a hypothesis about what could be causing the issue. They will get in touch with you.

    #1790
    kohei
    Participant

    Hello Anders,

    Could you share some more information on this issue?

    The same problem(error 205) has occurred to me when trying to run Tobii REX on Ubuntu 14.04.
    Just like in this discussion, I downgraded the REX firmware to support USB TCP/IP, but “ifconfig -a” showed the device as usb0 with the inappropriate IP address 172.28.195.2.
    Also, I ran “./fwupgrade –auto –info-only” but there was the same problem again (error 205).

    #1791
    Anders
    Participant

    Hi kohei,
    I’ll ask support to get in touch with you too.

    There is an issue with the firmware downgrade not working the way it should. We’re working on a solution but we don’t have anything that works out of the box yet. So in the mean time we have to solve the problem on a case by case basis.

    In case anyone else is dropping in on this thread: you’re welcome to support directly if you have the same problem.

    #2458
    Philip Shaw
    Participant

    I have exactly the same issue: I thought I had downgraded but I cannot connect to the REX with the software.

    Yes, I can ping 172.28.195.1 but I cannot fwupgrade or check the info or use it 🙁

    #2845

    I’m also facing the same (or a similar) problem with our two Tobii REX devices. The symptoms are:

    – Failure to connect to tobii REX with GazeSDK on Linux
    – Device gets IP address and is pingable
    – fwupdate <address> –info-only returns Failed to get device info
    – fwupdate <address> <binary> –no-version-info locks up

    Is there a known cause and a solution for this problem?

    #2870
    Anders
    Participant

    Hi Jan Willem,
    yes, the cause is known and will be addressed with a new Gaze SDK release coming soon. Please contact support if you’re in a hurry to get something up and running, they can help you with an interim solution.

    #6446
    JesseG
    Participant

    I realize I’m late to the Rex party, but I’m trying to get my Rex connected to GazeSDK on Linux (Ubuntu 16.04) for the first time and getting the “205 No eye tracker could be found” error. I’m piecing together information from the forums and remaining pages, and I see that there are HID and TCP firmwares for the Rex.

    This page ( http://developer.tobii.com/rex-firmware/ ) says that the USB-HID firmware is the maintained version, and TCP/IP is older/deprecated. However, lower down in the section “On Linux and Android” it also says that if you see “Bus XXX Device YYY: ID 2104:0001” in lsusb, you have the USB-HID firmware and “you will need to change the firmware to use the device”. These directions seem to contradict one another, so I’m not sure which firmware to shoot for.

    What I have is the USB-HID Firmware; I’m able to run “fwupgrade —auto —info-only” on windows and I get:
    Automatically selected eye tracker tobii-ttp://REXDL-030114042683
    Model: REX_Dev_Laptop
    Firmware version: 1.2.2.30200.20140815.0829.root
    (I’m using Gaze SDK 4.1.0)

    When I run the same command on Linux, I get the 205 error.

    Much of the forum activity surrounding this error on Linux is about people switching to the TCP/IP firmware and making sure the network aspects get mapped up correctly. However, I’m not sure if that is all out of date now that the USB-HID firmware exists. This page ( http://developer.tobii.com/new-tobii-gaze-sdk-released-support-usb-hid-linux-android/ ), though somewhat redacted, makes it sound like the USB-HID firmware would work with the Linux Gaze SDK, but I don’t see people using that strategy on the forums…

    So, any hints on getting the Rex to communicate with the Gaze SDK on Linux?

    Especially: Is the Rex meant to work on Linux with the USB-HID firmware? Or was the TCP/IP firmware the only firmware ever supported for Linux GazeSDK?

    I realize the whole Rex/Gaze product is discontinued, but I have a brand new Rex purchased last year and am trying to get it to work for the first time, so I appreciate any help getting set up!

    #6495
    Anders Vennström
    Participant

    Hi JesseG,

    Unfortuantely the TCP/IP was the only supported mode on Linux, so you will need to switch the tracker to TCP/IP mode to get it to work.

    //Anders, Tobii

    #6496
    JesseG
    Participant

    Thanks for the info Anders!

    That clears up my confusion! Do you know where I can find that last/best version of the TCP/IP firmware? It looks like the download links are removed now.

    Also, I assume I should flash the device from Windows, right? Since the linux software won’t detect the device until the FW swap?

    Thanks!!
    Jesse

Viewing 14 posts - 1 through 14 (of 14 total)
  • You must be logged in to reply to this topic.