ASUS Xtion USB 3.0 Hotfix

48 Replies

Today ASUS sent along a RD version of a patch that should resolve the Xtion USB 3.0 issue. I’ve been given permission to distribute this file on a no-warranty-of-any-kind basis. In order to apply the patch download


Extract it to a folder of your choice, attach the sensor to an USB 2.0 port and execute UsbUpdate\!Update-RD108x!.bat. Once that step has completed successfully your sensor should work on USB 3.0.

According to ASUS there was an issue with ASmedia USB3.0 controller(ASM1041/ASM1042), which can be fixed by ASmedia’s new driver(1.16.1.0) and firmware(12220E). I assume the content of .zip file updates the driver and the firmware.

I’m very grateful to ASUS that ReconstructMe users are among the first to receive this patch! Please report back your results, so I can give feedback to ASUS.

Thanks,
Christoph

  • Guido Schaniel

    I’ll try and give as soon as possible a comment. Thanks.

  • Guido Schaniel

    Plug the Xtion Pro to a USB2 first, then update by the .bat. After this firmware update the Xtion Pro will be recognised under Win7 with USB3.
    I’ll will install everything, new due to the fakt all softwares doesn’t work for long time…
    feedback will follow

  • Guido Schaniel

    Jeeppiii it works!! First scan with USB3 :-) .
    After updating with USB2 port & patch.
    Deinstalled all drivers and software on new notebook.
    Installed the Sensor Driver Package x86 1.5.2.zip. Reboot and installed your great software. :-) ….
    Many Thanks.

    • MartinAnkerl

      That’s good news :)

    • Christoph Heindl

      Great, thanks for your feedback.

  • Aurora Prawiradinata

    Hi, so which one do you think works better? with Kinect or Asus? would love to hear from you!
    Thanks!

    • http://martin.ankerl.com/ Martin Ankerl

      we prefer the Asus, because it is smaller and does not need external power

  • Grega

    Does new driver for Linux exists? Because current one does not work with updated firmware.

    Thank’s

    • Qianyi

      Current OSX driver does not work with updated firmware as well.

    • Qianyi

      Current OSX driver does not work with upgraded firmware as well (Latest Mountain Lion vs. Asus Xtion Pro Live with firmware upgraded).

    • NICTA-AS

      I have managed to get the Asus Xtion Pro working with USB 3 ports under Ubuntu 12.04. We use Ubuntu 12.04 on a Mac Mini 2012 (which only has USB 3 ports).

      To get the device working I used OpenNI Unstable 1.5.4.0 (https://github.com/OpenNI/OpenNI.git) and PrimeSense Sensor Unstable 5.1.2.1 (https://github.com/PrimeSense/Sensor.git).

      After installing the driver it is necessary to change the “USB interface” that is used to BULK endpoints by uncommenting UsbInterface=2 in GlobalDefaults.ini (/usr/etc/primesense/GlobalDefaults.ini). I’ve also found it works when the interface is set to 0. The following comment from the file explains the meaning of the parameters:
      ; USB interface to be used. 0 – FW Default, 1 – ISO endpoints, 2 – BULK endpoints. Default: Arm – 2, other platforms – 1

      I’m not currently using ReconstructMe and so have not tested with it. But have confirmed it working with both NiViewer and other code we have which accesses both depth and RGB data from the Asus using OpenNI (via OpenCV).

      Thanks for providing the firmware update and everyone else for posting information on their results.

  • Qianyi

    Background: I have a Asus Xtion Pro Live, a new Macbook retina (OSX + bootcamp Win7), and a workstation. The sensor used to work well with the workstation, and OSX on Macbook. My bootcamp Win7 cannot recognize the sensor since Macbook only has two USB3.0 ports.

    After I upgraded the firmware of my sensor (on the workstation), now the bootcamp Win7 recognizes the sensor. But when I use ReconstructMe or Kinfu, the scan freezes for a while every few seconds. And ReconstructMe crashes after a freeze. I guess it is because of the RGB stream issue – if I disable RGB stream, everything works just fine.

    One more side effect: now OSX does not recognize the sensor. I tried uninstall/install the openni packages on OSX, not working. I tried another Asus sensor (without firmware update), works just fine.

    Is there any idea for fixing the RGB stream issue? Or make the sensor work for OSX? Or conveniently downgrade the firmware (I hate the idea of keeping two sensors in my backpack)?

    • Christoph Heindl

      Are you sure it is not related to a ReconstructMe issue? Do you observe the same behaviour in other tools as well?

      • Qianyi

        Yes, I can notice a time-to-time strong lag even in NiBackRecorder (comes with the latest OpenNI package) if I turn on image stream.

        As for ReconstructMe, sometimes it can overcome this lag, sometimes it crashes with the following error (see attachment). I suspect it is a timeout error.

        Wired thing is: NiViewer does not have such problem. I am still trouble shooting it.

        • Christoph Heindl

          Could you try ReconstructMeQt concerning this error?

          • Qianyi

            Hi Christoph, ReconstructMeQt works fine – although this time-to-time lag still exists (can be observed in the right side windows of ReMeQt). I think Asus still messed up something in the driver.

            • Christoph Heindl

              @bc4692a82bb6b8c5b981d673ae25ae1b:disqus: Thanks for noting. I contacted ASUS about the issue.

        • Guido Schaniel

          got the same problem :-( , sometimes it works but very slow..

        • Yougs2121

          Same problem for me too

      • Qianyi

        I have made more tests with NiViewer/NiSimpleViewer on my bootcamp Win7. With default 320x240x30Hz they work fine, but if I set the resolution to 640x480x30Hz for both depth and rgb images, I can observe a strong time-to-time lag in the depth stream.

        The sensor works perfectly with my workstation up to now.

        PS: I made a “clean” installation of the latest stable OpenNI package. So it should not be a driver issue.

        Can anyone else prove my observation?

      • Qianyi

        More test results.. platform: latest Macbook retina + bootcamp Win7 + 20.4.2.20 64-bits openni development package.

        Sensor works fine with both depth & rgb at 320x240x30Hz.Or depth only at 640x480x30Hz.
        When I run both depth & rgb at 640x480x30Hz. Rgb stream is fine, but the depth stream drops to ~10Hz.

        Sensor works fine with my workstation with USB 2.0.

        I suspect it is a throughput limitation when Xtion works with USB 3.0.

    • Grega

      I would also like to know if anybody knows where to get the old firmware back, because I also have issues with the new one. I have Asus Xtion Pro Live.

      Thank you.

      • Guido Schaniel

        http://www.openni.org/Downloads/OpenNIModules.aspx

        Hardware binaries–>stable->asus firmware upgrade tool

        there are the old files in it.

        if it doesn’t works to downgrade, maybe just copy these files to the .bat data and patch manually. I didn’t test it!

        • marcus

          Hi Guido,

          tried to downgrade in both ways. The asus firmware upgrade tool you mentioned says “Please try reconnecting USB plug and run this tool again.” while it Shows Status: Failed to connect. When I copy the files over to the hotfix folder and run the .bat file – it also throws a similar error: “Open sensor Failed: USB device not found!”. The curious thing about it is, that the Xtion Pro Live works, gets recognized by windows device manager and is able to run the samples. I only want to downgrade, because since the hotfix, the device doesn’t get recognized on my ubuntu computer anymore.

          Could you please help me to downgrade the firmware? Thank you

    • Hassan

      I am also suffering with s a similar issue. I am using Asus Xtion Pro Live Sensors, my problem was that i wanted to make multiple sensors work with my notebook which has one USB 2.0 and one USB 3.0 port. A single sensor is detected when connected to either of the ports but i wanted to use two simultaneously. When i connected both the sensors with a desktop machine one at the back and one at the front it detected both sensors. So it thought that may be the idea should be to use different usb controllers as same usb controller cannot support multiple sensors. So i order an Express card with a USB 3.0 port: ORICO PNU3-EC34. But when it arrived i found out the no Asus sensor works with that card though other USB pen drives work fine.

      Therefore i went to the OpenNI forum and posted my problem, someone replied and gave me the link to this patch/fix. When i installed the patch my sensor stopped working even when it is the only one connected. The device is detected as PrimeSense device instead of PrimeSense PS1080, but then it tells me that it failed to install the driver for this device. To my surprise now this device is not working with any machine giving the same error. :( So my guess is that the patch changed something internally in the device or something. I would really appreciate any help because my device has basically become useless now.

      • Hassan

        Okey may be the problem was that i had the older version of the driver and the OpenNI toolkit, i installed the newer versions and it seems to work now. :-)

        • Christoph Heindl

          Great!

    • Yuuki

      I sufferd same probrem on Mac OSX. I solved by

      1. make factory.bat in UsbUpdate folder

      @echo off
      UsbUpdate .UsbUpdate_Factory.ini 0 0 0
      @pause

      2. run factory.bat

      after that, the device work with OSX

      • Christoph Heindl

        Great, thanks for noting!

      • http://www.facebook.com/paul.powersOne Paul Powers

        I’ve been pulling my hair out for 2 days after using the hotfix and I just tried this with success. Thank you very much! This works guys!

  • Qianyi

    One more problem report:

    The firmware update seems to break the default configuration in Windows as well.A simple example is to run NiBackRecorder, it now lost frames and report “Add depth node failed: Error!”. I tested on two machines separately. They have the same symptom. (Where my workstation used to work fine with the old firmware).
    Verbose says the following error: 3674686 VERBOSE Depth1_Mock: Setting map output mode to 640×480, 30 fps 3675759 VERBOSE Getting property Depth1.AGCBin from server… 3682245 VERBOSE Getting property Depth1.AGCBin from server… 3687736 VERBOSE Getting property Depth1.AGCBin from server… 3693289 VERBOSE Getting property Depth1.AGCBin from server… 3699522 WARNING Failed to write Node Added nodeAddedRecord to file: Error!Add depth node failed: Error!

    I am experiencing a lot new issues after the firmware update.
    So, be careful – especially when you are in the middle of developing something.

    • Christoph Heindl

      Qianyi thanks for the report, I will escalate this to ASUS

    • Christoph Heindl

      @bc4692a82bb6b8c5b981d673ae25ae1b:disqus do you have any specifics about the ASUS device you own? serial number etc?

      • Qianyi

        @google-d1535c766311cdf0dddf2269b6cd1120:disqus The serial number is 3210-1205230181. I now figured out that the problems were almost all due to the depth stream frame lost issue, as mentioned above. Thanks for notifying ASUS about this. Btw: can you also ask ASUS if there is a mac/linux driver for Xtion after the firmware update?

        • Christoph Heindl

          I will once I get back to office.

  • Hassan

    I am also having problems with this upgrade. Can someone please inform me about a tried and tested method to get back to the old configuration?

  • Guido Schaniel

    any news or new updates? since 20 days nothing happend? Thanks

    • Guido Schaniel

      Christoph can you pls, ask asus for another update?…

      • Christoph Heindl

        I will.

  • shogo

    Hi.
    I want to downgrade my Xtion Pro Live.
    But I cannot downgrade because of “USB device not found” error.

    I read the comments below written by Grega, Guido and marcus .
    Unlikely to marcus, my laptop (Windows7 64bit ) cannot run openNI samples even after the same attempt.

    Does anyone know how to solve this problem and downgrade it ?

  • pod

    Will this fix allow to run the xtion at 1280×1024 at 30fps in a usb3 port? So far, I’m running the xtion with the stock firmware in a usb2 port and the frame rate drops a lot when I switch to 1280×1024 mode.

  • David

    I have updated my Xtion Pro, and it works now with Faro Scenect, but it will not work with reconstructmeQt. The sensor is not recognized…..

    • Christoph Heindl

      What’s the configuration you set for the sensor part?

  • Chris

    Dear Christoph,
    I am just wondering if ASUS has reacted any further on this issue? The hotfix seems to work, but generates a lag after some time running (as several users have confirmed here). Any chance to push this issue at Asus again ? Than kyou so much for your support !

    Chris

  • carlo

    just got the asus xtion pro live, did the install from the cd and installed reconstructme. it worked normally. then I installed this patch and now the camera cannot initialize anymore! also tried another pc, but nothing.. need to downgrade I guess, but how? cannot find firmware on asus site. please help!

  • carlo

    solved, missed the factory.bat trick. that worked for me. are there no other firmware updates?

  • test

    test

  • Manuel

    I make the firmware update and now my device is connecting and disconnecting all the time, I can not make the downgrade because of the comunication is not working properly.