advice on identifying no device connected for OSX and librealsense

[smcdo5]

I've been at this all day, I have no problems compiling (have compiled with XCode, Clang5, GCC7), but I can't get any of the realsense demos / tools to recognize a device is actually connected :/ The only "progress" I made is probably just a bug, if I launch realsense-viewer with the camera plugged in it will ask "Connect a RealSense Camera or Add Source". If I unplug and replug, the dialogue will go away, but nothing will actually happen.

$ lsusb -t  Bus 000.Dev 001: USB 3.0 Bus,  |__ Bus 020.Dev 003: BRCM20702 Hub, 12M  |__ Bus 020.Dev 006: Bluetooth USB Host Controller, 12M  |__ Bus 020.Dev 002: Apple Internal Keyboard / Trackpad, 12M  |__ Bus 020.Dev 013: Intel(R) RealSense(TM) 3D Camera (Front F200), 5G

It's definitely connected, also to USB3 (that's all I've got). I know the camera works, it's got no problems doing things on Linux on the same computer.

I've tried building stable releases, latest development branch, etc. I'm not sure how to continue, are there any alternative tools I can use here? On linux I would use the classic GStreamer approach described back in the day here:

http://solsticlipse.com/2015/01/09/intel-real-sense-camera-on-linux.html intel RealSense camera on Linux

Truth be told, my entire API was originally using this before I decided to reframework and just use the official SDK / be able to support this camera model on non-linux.

I'm game for an adventure, but need some steering as to which rabbit hole to jump down next. Would libusb be the problem? libuvc? Thanks for any thoughts

Message was edited by: stephen mcdowell bad formatting on lsusb output

[MartyG]

This post on the Librealsense forum may be of use to you.

https://github.com/IntelRealSense/librealsense/issues/127 Apple OSX H/W / USB issues · Issue # 127 · IntelRealSense/librealsense · GitHub

[smcdo5]

LOL. So it occurred to me why people keep mentioning the SDK 2 is new. v1.12.1 works just fine. It seems librealsense2 has dropped support for the F200?

Should I open an issue on GitHub for this, or is the F200 officially no longer supported?

[MartyG]

Yes, the SDK 2.0 is for SR300, D415 and D435.

The F200 has long been unavailable for purchase, and even its successor the SR300 is about to be retired (D415 and D435 will be the main models, going forward, used with SDK 2.0). But the older cameras continue to receive help support on this forum..

[smcdo5]

Harumph. That saddens me. I wonder why they removed the existing implementation. Tried the XCode build (ewww), same results.

P.S. I totally should have seen this sooner, it's stated explicitly on the README: https://github.com/IntelRealSense/librealsense# overview GitHub - IntelRealSense/librealsense: Intel® RealSense™ SDK

[MartyG]

I posted another link about OSX Librealsense problems above. I think you sent your LOL message at the exact time that I sent mine, so my message ended up behind it. Here it is again in case you missed it.

https://github.com/IntelRealSense/librealsense/issues/127 Apple OSX H/W / USB issues · Issue # 127 · IntelRealSense/librealsense · GitHub

OSX support in SDK 2.0 is a 'coming soon' feature. You can keep track of its latest releases on this page.

https://github.com/IntelRealSense/librealsense/releases/ Releases · IntelRealSense/librealsense · GitHub

Sadly I have to go 'off shift' for the day now. If you have further questions, please post them here and I will pick them up in my inbox first thing Friday morning. Have a great day!

[smcdo5]

I posted another link about OSX Librealsense problems above. I think you sent your LOL message at the exact time that I sent mine, so my message ended up behind it. Here it is again in case you missed it.

Yeah I think so. I tried the XCode build of librealsense2 for shiggles, but (as expected with the knowledge of my device being legacy) nothing is registered.

OSX support in SDK 2.0 is a 'coming soon' feature. You can keep track of its latest releases on this page.

As far as I can tell it works very well, or at the very least the build system produces executables that can link and run without issue. I have not an SDK2.0 compatible device, though, so I can't speak as to whether or not the driver side is working.

A brief survey of the v1.12.1 API seems to reveal that the frameworks are very similar, but the SDK 2.0 seems a lot nicer / much more seamless. I wonder if some of the API differences were only possible by explicitly dropping support for the legacy devices. Components in v1.12.1 have a decent amount of enumerating constants / attributes for e.g. F200 or R200 specifically. Kudos to the masterminds behind the rework, the new API is very sleek!

Thanks for all of you help today Marty

[MartyG]

You're very welcome. Please come back to the forum any time that you have questions. Have a great weekend!

[MartyG]

As you asked about Mac OSX support in SDK 2.0 recently, I thought I'd let you know that the OSX documentation has been updated.

https://github.com/IntelRealSense/librealsense/blob/master/doc/installation_osx.md librealsense/installation_osx.md at master · IntelRealSense/librealsense · GitHub