ZR300 unrecognized by upboard

[EKhal]

I am trying to get ZR300 working with UpBoard (4GB RAM + 64 GB eMMC) , but device can not be recognized for some reason. I also noticed that when I do lsusb vendor id show 8027 (see below) which does not seem correct. From what I saw in other places correct vendor ID should be 8086. @

To install librealsense I used instructions published here(https://software.intel.com/sites/products/realsense/intro/getting_started.html Introduction to Intel® RealSense™ SDK for Linux: Getting Started ) on my freshly installed Ubuntu 16.04.4

robot@upboard:~$ lsusb

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus 001 Device 008: ID 0424:2530 Standard Microsystems Corp.

Bus 001 Device 005: ID 0424:4603 Standard Microsystems Corp.

Bus 001 Device 004: ID 04b4:22c3 Cypress Semiconductor Corp.

Bus 001 Device 002: ID 0451:8027 Texas Instruments, Inc.

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[MartyG]

The ZR300 is approved by Intel for use with Up Boards, so I do not think the problem is a hardware incompatibility between camera and board.

I do not see a USB 2.0 Flash storage stick plugged in. So I am guessing you have already installed Ubuntu on the board's internal storage via a USB 'boot stick' and then tried to install the RealSense SDK for Linux in Ubuntu after that once the Ubuntu OS was set up successfully?

[EKhal]

Yes you are correct. I already installed Ubuntu on the board following instructions here(https://01.org/developerjourney/installing-ubutnu-1404-lts-intel-realsense-robotic-development-kit Installing Ubutnu 14.04 LTS with the Intel RealSense Robotic Development Kit | Developer Journey.

Realsense SDK I tried to install via repository as described here (https://software.intel.com/sites/products/realsense/intro/getting_started.html Introduction to Intel® RealSense™ SDK for Linux: Getting Started)

From reading another post it seem like this might be related to cable issue discussed here ( ). Is there any way to confirm this ?

[MartyG]

The RealSense Robotic Development Kit (the bundle Intel sells containing an R200 and Up Board) comes with a USB cable to connect the camera to the OTG adapter dongle. Are you using the approved cable from a Robotic Kit, or did you purchase the ZR300 and Up Board separately and use your own cable?

The Robotic Kit also comes with a power pack. It looks like you are using your own power cable. Given RealSense's sensitivity to power supply and the camera detection issues it often causes with the USB port, I would not rule out the power cable as the source of your problem either.

[EKhal]

I am using ATX power supply that is rated to 200W, so I think power is not likely the issue here. I also tried to connect with a powered USB 3.0 hub and result is similar.

To connect, I use USB 3.0 to Micro B cable that came with ZR300 and an adapter that I purchased separately. it is possible that the adapter is the issue here.

ZR300 and the UpBoard I purchased separately.

[EKhal]

One more datapoint. I just tried to connect to iMac and looks like ZR300 is being recognized correctly. This is when I connect without the blue adapter.

$ ioreg -p IOUSB -l -w 0

....

+-o Intel RealSense 3D Camera ZR300@14510000

{

"sessionID" = 1712854679975115

"iManufacturer" = 1

"bNumConfigurations" = 1

"idProduct" = 2763

"bcdDevice" = 9340

"Bus Power Available" = 450

"USB Address" = 11

"bMaxPacketSize0" = 9

"iProduct" = 2

"iSerialNumber" = 3

"bDeviceClass" = 239

"Built-In" = No

"locationID" = 340852736

"bDeviceSubClass" = 2

"bcdUSB" = 784

"USB Product Name" = "Intel RealSense 3D Camera ZR300"

"PortNum" = 1

"non-removable" = "no"

"IOCFPlugInTypes" = {"9dc7b780-9ec0-11d4-a54f-000a27052861"="IOUSBFamily.kext/Contents/PlugIns/IOUSBLib.bundle"}

"bDeviceProtocol" = 1

"IOUserClientClass" = "IOUSBDeviceUserClientV2"

"IOPowerManagement" = {"DevicePowerState"=0,"CurrentPowerState"=3,"CapabilityFlags"=65536,"MaxPowerState"=4,"DriverPowerState"=3}

"kUSBCurrentConfiguration" = 1

"Device Speed" = 3

"USB Vendor Name" = "Intel Corp"

"idVendor" = 32902

"IOGeneralInterest" = "IOCommand is not serializable"

"USB Serial Number" = "SN_3511803433"

"IOClassNameOverride" = "IOUSBDevice"

}

[MartyG]

It is not so much a matter of power wattage as stability of the power. Even PCs with 600w server PSUs have had detection issues in the past. But your lack of success with a powered hub suggests power may not be the issue in this case. I have heard it said that the OTG adapter used can have a bearing on whether it works or not.

Up sells an OTG cable in their store that is presumably optimised for their product.

https://up-shop.org/up-peripherals/22-usb30-otg-cable.html https://up-shop.org/up-peripherals/22-usb30-otg-cable.html

[EKhal]

Thank you for the link! Let me try ordering this cable and see if it resolves the issue. Will report back with results.

[zfari]

I see, https://showbox.software/ ShowBox https://luckypatcher.pro/ Lucky Patcher https://kodi.software/ Kodi, we bought them one year and two months ago, so that is the reason for the denied request.I tried the USB Hub now but same error log, any further ideas?Thanks for the help so far!

[EKhal]

With another adapter I can now see device detected and was able to get point-cloud and other examples to work.

I decided to try another provider for the USB adapter from Amazon first (SMAKN® USB 3.0 A Female to Micro B Male OTG cable + A male to Micro 10pin male adapter) as ordering from UpBoard showed a 20+ shipping cost.

$: lsusb

Bus 002 Device 003: ID 8086:0ad0 Intel Corp.

Bus 002 Device 004: ID 8086:0acb Intel Corp.

Bus 002 Device 002: ID 0451:8025 Texas Instruments, Inc.

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus 001 Device 004: ID 0424:2530 Standard Microsystems Corp.

Bus 001 Device 003: ID 0424:4603 Standard Microsystems Corp.

Bus 001 Device 005: ID 0451:8027 Texas Instruments, Inc.

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[MartyG]

Awesome news! Thanks so much for sharing your good news and the product recommendation.