<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Hardware trigger for depth images in Items with no label</title>
    <link>https://community.intel.com/t5/Items-with-no-label/Hardware-trigger-for-depth-images/m-p/321068#M980</link>
    <description>&lt;P&gt;An Intel member with specialist ZR300 knowledge would be better able to answer your question, so I have linked.amitmoran   to this discussion for his input.&lt;/P&gt;</description>
    <pubDate>Thu, 07 Sep 2017 21:19:01 GMT</pubDate>
    <dc:creator>MartyG</dc:creator>
    <dc:date>2017-09-07T21:19:01Z</dc:date>
    <item>
      <title>Hardware trigger for depth images</title>
      <link>https://community.intel.com/t5/Items-with-no-label/Hardware-trigger-for-depth-images/m-p/321065#M977</link>
      <description>&lt;P&gt;Hello, does anyone know if the realsense cameras have any external hardware triggering capabilities for depth frame capture? We are trying to sync depth data measurements with other data sensors running on a different device/clock, and we need really high (sub-millisecond) precision alignment between the two data sources. We could try triggering from software, but the OS would add some delay, and we would lose sub-millisecond precision. Alternatively if there was some sync pulse that the board can output whenever a frame is taken, we can use that for data alignment as well. The datasheet for the ZR300 indicates there is some Trigger (from Depth Camera) for the fish-eye camera, but I'm not sure what the "from depth camera" means. Would someone be able to clarify whether we can use this trigger for depth frame collection as well as the fish-eye?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 06 Sep 2017 19:45:38 GMT</pubDate>
      <guid>https://community.intel.com/t5/Items-with-no-label/Hardware-trigger-for-depth-images/m-p/321065#M977</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2017-09-06T19:45:38Z</dc:date>
    </item>
    <item>
      <title>Re: Hardware trigger for depth images</title>
      <link>https://community.intel.com/t5/Items-with-no-label/Hardware-trigger-for-depth-images/m-p/321066#M978</link>
      <description>&lt;P&gt;The topic of how best to trigger streams in the shortest possible time, and the wish for a hardware trigger solution, was discussed in depth last month and may be useful to you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The discussion mentions how AikenControls used physical external shutters but found them ugly and expensive.&lt;/P&gt;</description>
      <pubDate>Wed, 06 Sep 2017 20:51:23 GMT</pubDate>
      <guid>https://community.intel.com/t5/Items-with-no-label/Hardware-trigger-for-depth-images/m-p/321066#M978</guid>
      <dc:creator>MartyG</dc:creator>
      <dc:date>2017-09-06T20:51:23Z</dc:date>
    </item>
    <item>
      <title>Re: Hardware trigger for depth images</title>
      <link>https://community.intel.com/t5/Items-with-no-label/Hardware-trigger-for-depth-images/m-p/321067#M979</link>
      <description>&lt;P&gt;Hi Marty, thanks for the link. It seems like the issue there was laser interference between multiple cameras so hardware triggering of the IR projector would have solved that issue, but yeah, they did mention it would be nice to have hardware trigger of sensors too. I guess I should take this to mean that there currently is no way to externally trigger the cameras outside of the SDK to take frames (although the discussion was for the SR300, and the triggering capabilities of the ZR300 wasn't really discussed). I'm still curious about the "G0" and "G1" trigger under the Motion Control Unit Functions section and the "Trigger (from Depth Camera)" under the Fisheye Camera Functions section in the ZR300 datasheet. Any insight on what those might be?&lt;/P&gt;</description>
      <pubDate>Thu, 07 Sep 2017 21:08:40 GMT</pubDate>
      <guid>https://community.intel.com/t5/Items-with-no-label/Hardware-trigger-for-depth-images/m-p/321067#M979</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2017-09-07T21:08:40Z</dc:date>
    </item>
    <item>
      <title>Re: Hardware trigger for depth images</title>
      <link>https://community.intel.com/t5/Items-with-no-label/Hardware-trigger-for-depth-images/m-p/321068#M980</link>
      <description>&lt;P&gt;An Intel member with specialist ZR300 knowledge would be better able to answer your question, so I have linked.amitmoran   to this discussion for his input.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Sep 2017 21:19:01 GMT</pubDate>
      <guid>https://community.intel.com/t5/Items-with-no-label/Hardware-trigger-for-depth-images/m-p/321068#M980</guid>
      <dc:creator>MartyG</dc:creator>
      <dc:date>2017-09-07T21:19:01Z</dc:date>
    </item>
    <item>
      <title>Re: Hardware trigger for depth images</title>
      <link>https://community.intel.com/t5/Items-with-no-label/Hardware-trigger-for-depth-images/m-p/321069#M981</link>
      <description>&lt;P&gt;I just wanted to update you that the new RealSense SDK 2.0 has a tool with a function for adding an auto-disable to an RGB control.&lt;/P&gt;</description>
      <pubDate>Wed, 13 Sep 2017 21:27:39 GMT</pubDate>
      <guid>https://community.intel.com/t5/Items-with-no-label/Hardware-trigger-for-depth-images/m-p/321069#M981</guid>
      <dc:creator>MartyG</dc:creator>
      <dc:date>2017-09-13T21:27:39Z</dc:date>
    </item>
    <item>
      <title>Re: Hardware trigger for depth images</title>
      <link>https://community.intel.com/t5/Items-with-no-label/Hardware-trigger-for-depth-images/m-p/321070#M982</link>
      <description>&lt;P&gt;Hi MartyG, what do you mean by auto-disable, do you mean for the laser projector?&lt;/P&gt;</description>
      <pubDate>Wed, 13 Sep 2017 21:33:39 GMT</pubDate>
      <guid>https://community.intel.com/t5/Items-with-no-label/Hardware-trigger-for-depth-images/m-p/321070#M982</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2017-09-13T21:33:39Z</dc:date>
    </item>
    <item>
      <title>Re: Hardware trigger for depth images</title>
      <link>https://community.intel.com/t5/Items-with-no-label/Hardware-trigger-for-depth-images/m-p/321071#M983</link>
      <description>&lt;P&gt;There isn't any more explanation yet, other than some possible hints on the comments of line 50 to 53 of this script.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://github.com/IntelRealSense/librealsense/commit/dd8d3d04fea6c9c20bb14b3dfa274a4c8772d8c0"&gt;https://github.com/IntelRealSense/librealsense/commit/dd8d3d04fea6c9c20bb14b3dfa274a4c8772d8c0&lt;/A&gt; Add auto_disabling_control to RGB controls. Tracked On: DSO-6892 · IntelRealSense/librealsense@dd8d3d0 · GitHub&lt;/P&gt;&lt;P&gt;&lt;/P&gt;-* stop raising events when the devices connected to the computer change.-* additionally, block the calling thread until all in-flight callbacks return.-* \param context Object representing librealsense session-* \param[out] error if non-null, receives any error that occurs during this call, otherwise, errors are ignored</description>
      <pubDate>Wed, 13 Sep 2017 21:41:08 GMT</pubDate>
      <guid>https://community.intel.com/t5/Items-with-no-label/Hardware-trigger-for-depth-images/m-p/321071#M983</guid>
      <dc:creator>MartyG</dc:creator>
      <dc:date>2017-09-13T21:41:08Z</dc:date>
    </item>
    <item>
      <title>Re: Hardware trigger for depth images</title>
      <link>https://community.intel.com/t5/Items-with-no-label/Hardware-trigger-for-depth-images/m-p/321072#M984</link>
      <description>&lt;P&gt;Hi xingy,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt; &lt;P&gt;&amp;nbsp;&lt;/P&gt;I was looking at this thread, I would like to add the ZR300 dev kit does not have a trigger signal that can be accessed externally.  The signals are all accessible through software.&lt;P&gt;&amp;nbsp;&lt;/P&gt; &lt;P&gt;&amp;nbsp;&lt;/P&gt;Additionally, this page, &lt;A href="https://software.intel.com/sites/products/realsense/camera/namespacers.html"&gt;https://software.intel.com/sites/products/realsense/camera/namespacers.html&lt;/A&gt; &lt;A href="https://software.intel.com/sites/products/realsense/camera/namespacers.html"&gt;https://software.intel.com/sites/products/realsense/camera/namespacers.html&lt;/A&gt;, describes fisheye_external_trigger as "Enable/disable fisheye external trigger mode. When enabled, fisheye image will be acquired in-sync with the depth image."  The G0 and G1 signals are used for gyro synchronization. This page, &lt;A href="https://software.intel.com/sites/products/realsense/camera/developer_guide.html"&gt;https://software.intel.com/sites/products/realsense/camera/developer_guide.html&lt;/A&gt; &lt;A href="https://software.intel.com/sites/products/realsense/camera/developer_guide.html"&gt;https://software.intel.com/sites/products/realsense/camera/developer_guide.html&lt;/A&gt;, under ZR300 Asynchronous APIs mentions the GPIOs. The cpp-motion-module.cpp file, &lt;A href="https://github.com/IntelRealSense/librealsense/blob/master/examples/cpp-motion-module.cpp"&gt;https://github.com/IntelRealSense/librealsense/blob/master/examples/cpp-motion-module.cpp&lt;/A&gt; &lt;A href="https://github.com/IntelRealSense/librealsense/blob/master/examples/cpp-motion-module.cpp"&gt;https://github.com/IntelRealSense/librealsense/blob/master/examples/cpp-motion-module.cpp&lt;/A&gt;, shows how to use it.&lt;P&gt;&amp;nbsp;&lt;/P&gt; &lt;P&gt;&amp;nbsp;&lt;/P&gt;Hope you find this information useful.&lt;P&gt;&amp;nbsp;&lt;/P&gt; &lt;P&gt;&amp;nbsp;&lt;/P&gt;Regards,&lt;P&gt;&amp;nbsp;&lt;/P&gt;-Yermi A.&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 19 Sep 2017 17:37:23 GMT</pubDate>
      <guid>https://community.intel.com/t5/Items-with-no-label/Hardware-trigger-for-depth-images/m-p/321072#M984</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2017-09-19T17:37:23Z</dc:date>
    </item>
  </channel>
</rss>

