T265 ability to open pipeline using serial number

[orshefi]

Hi Guys,

I'm testing #5213 to see rather all functionalities previously used by my system remains.
So far I found out that I can no longer open T265 device by serial number with enable_device api.

Here is a simple init function to check which devices & their serial number are connected, and try to open them with pipe API.

rs2::context ctx;
    auto devices = ctx.query_devices();
    for(auto dev : devices){
        std::cout << dev.get_info(RS2_CAMERA_INFO_NAME) << std::endl;
        std::cout << dev.get_info(RS2_CAMERA_INFO_SERIAL_NUMBER) << std::endl;
    }
    // Declare RealSense pipeline, encapsulating the actual device and sensors
    rs2::pipeline pipe;
    // Create a configuration for configuring the pipeline with a non default profile
    rs2::config cfg;
    // Add pose stream
    cfg.enable_stream(RS2_STREAM_POSE, RS2_FORMAT_6DOF);
    std::string serial = "0000909212111581";
    cfg.enable_device(serial);
    // Start pipeline with chosen configuration
    pipe.start(cfg);

Here is the output:

Intel RealSense T265
0000909212111581
RealSense error calling rs2_pipeline_start_with_config(pipe:0x186a580, config:0x185b600):
    No device connected

As you can see:

1. Serial number is padded with zeros - new behavior, I'm using a certain convention in my config file that is broken according to this change. (I had also tried without the padding to open the device serial - 909212111581)
2. Device is enumerated but not opened with the serial number listed
3. I also run rs-pose example and the camera was able to open and stream data with pipe API (just without the enable device API).

[radfordi]

Thanks for your report, @orshefi. I just noticed this myself, and I was wonder if this used to be the case or not. I'll put together a fix.

[JeremyBYU]

Having the same issue. I had to open the t265 individually by the sensor using sensor.open(stream_profile)

[zainmehdi]

I tried this fix but still having the same error. Rolling back to version 2.31. Any updates on it ? Thanks

[radfordi]

Hi @zainmehdi, there are two fixes available in #5615 and #5645. You'll need both.

[zainmehdi]

@radfordi Thanks alot for your reply. i already tried #5615 and it didnt work for me. I will try 5645 and update.

[orshefi]

Hi @radfordi ,

Just tested the latest development version with #5645 merged into.
The serial number indeed is in the same convention as libtm and its great.
But nonetheless, the pipe cannot start with the serial number enabled in the config.

[radfordi]

Hi @orshefi, the current development version (d363eb9) with #5645 is still missing #5615, so you'll need to merge that before it'll work.

[Andrew-fedoralabs]

Hello @radfordi,
I have pulled the dev branch, merged #5615 and built.
I am no longer getting"no device connected" but am now getting:
"RealSense error calling rs2_pipeline_start_with_config(pipe:0x7f6c1404e7c0, config:0x7f6c1404be00):
Unable to open device interface"

I have tried to run rs-multicam and it now fails with the T265 ( it was working previously with master branch, but my application was not able to open the device with serial numaber and I was getting "no device connected" leading me to find this potential fix)

Any suggestions?

Thanks.

[Andrew-fedoralabs]

I have Rolled back to v2.31.0 but it still has the "no device connected" Issue. Does anyone know what version endable_device by serial number was working with T265? Its required for my application to continue development. Thanks.

[zbynekwinkler]

I am successfully working with v2.31.0 and v2.29.0. Please check, if you are not hitting "the other problem" when T265 is not detected at all right after boot.