<?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 Biomechanical Applications using LabVIEW in Life Science</title>
    <link>https://ni.lithium.com/t5/Life-Science/Biomechanical-Applications-using-LabVIEW/m-p/197763#M25</link>
    <description>Is anyone combining NI vision tools with NI data acquisition tools for Biomechanical applications? I know several people who are trying to synchronize the images with the physiological data.  When they use separate systems they have to use time-stamps to match up the two signals.  This is cumbersome.  If both signals are in the same environment it's easier.</description>
    <pubDate>Fri, 25 Mar 2005 18:54:09 GMT</pubDate>
    <dc:creator>colby</dc:creator>
    <dc:date>2005-03-25T18:54:09Z</dc:date>
    <item>
      <title>Biomechanical Applications using LabVIEW</title>
      <link>https://ni.lithium.com/t5/Life-Science/Biomechanical-Applications-using-LabVIEW/m-p/197763#M25</link>
      <description>Is anyone combining NI vision tools with NI data acquisition tools for Biomechanical applications? I know several people who are trying to synchronize the images with the physiological data.  When they use separate systems they have to use time-stamps to match up the two signals.  This is cumbersome.  If both signals are in the same environment it's easier.</description>
      <pubDate>Fri, 25 Mar 2005 18:54:09 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/Life-Science/Biomechanical-Applications-using-LabVIEW/m-p/197763#M25</guid>
      <dc:creator>colby</dc:creator>
      <dc:date>2005-03-25T18:54:09Z</dc:date>
    </item>
  </channel>
</rss>

