<?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: Digital Input in LabVIEW</title>
    <link>https://ni.lithium.com/t5/LabVIEW/Digital-Input/m-p/380880#M190842</link>
    <description>&lt;DIV&gt;&lt;/DIV&gt;
&lt;P&gt;Yes, you can use an array of five elements and then do a search array to see which element is true. I think I would set the DAQmx Read to return a number and just wire the output to a case statement. You would have case values of 0,1,2,4,8,16 that would represent none detected, bit0 high, bit1 high, etc.&lt;/P&gt;
&lt;P&gt;The 6515 can output 30V so assuming you connect the digital output to the LED correctly, it should glow.&lt;/P&gt;</description>
    <pubDate>Tue, 20 Jun 2006 13:21:40 GMT</pubDate>
    <dc:creator>Dennis_Knutson</dc:creator>
    <dc:date>2006-06-20T13:21:40Z</dc:date>
    <item>
      <title>Digital Input</title>
      <link>https://ni.lithium.com/t5/LabVIEW/Digital-Input/m-p/379301#M190186</link>
      <description>Hi....all&lt;BR /&gt;
&lt;BR /&gt;
I am working on the identifiaction of stator coils, I have 5 types of&lt;BR /&gt;
Staor coils and I have to identify these different coils using NI 6515&lt;BR /&gt;
DAQ Card, I am using LabVIEW 8.0.&lt;BR /&gt;
&lt;BR /&gt;
But the problem is that as these 5 coils have different connectors&lt;BR /&gt;
which will give me a HIGH(DI) to my DAQ Card if that particular coil is&lt;BR /&gt;
connected.....so my problem is that I have to acquire a DI(Digital&lt;BR /&gt;
Input)....for 5 such coils simultaneously....and as only one coil will&lt;BR /&gt;
be connecting at a time, which will lead to failure for other codes for&lt;BR /&gt;
left 4 coils and it will stop the program running.....so could anybody&lt;BR /&gt;
suggest me what can I do in such a case when I have to acquire only the&lt;BR /&gt;
connected input and run the simultaneous code for that and leave&lt;BR /&gt;
others.....so that program doesnt terminates.&lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
With Regards&lt;BR /&gt;
James&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Thu, 15 Jun 2006 16:40:06 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/Digital-Input/m-p/379301#M190186</guid>
      <dc:creator>james</dc:creator>
      <dc:date>2006-06-15T16:40:06Z</dc:date>
    </item>
    <item>
      <title>Re: Digital Input</title>
      <link>https://ni.lithium.com/t5/LabVIEW/Digital-Input/m-p/379883#M190424</link>
      <description>&lt;DIV&gt;&lt;/DIV&gt;I'm not quite sure I understand the problem. Are you acquiring data from 5 separate digital input lines and you don't know which of the 5 might be connected? If you read all 5 and have data on at least one line, do you need to know which specific line is true? Since the digital read will return either a number or an array of Booleans (it depends on how you've configure the DAQmx Read), it would seem that the only failure condition would be if the number returned is 0 or if all elements in the Boolean array are false. If I'm totally misunderstanding the problem, could you provide more details?</description>
      <pubDate>Fri, 16 Jun 2006 17:03:37 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/Digital-Input/m-p/379883#M190424</guid>
      <dc:creator>Dennis_Knutson</dc:creator>
      <dc:date>2006-06-16T17:03:37Z</dc:date>
    </item>
    <item>
      <title>Re: Digital Input</title>
      <link>https://ni.lithium.com/t5/LabVIEW/Digital-Input/m-p/380791#M190789</link>
      <description>&lt;DIV&gt;&lt;/DIV&gt;
&lt;P&gt;Thanks Dennis for your reply,&lt;/P&gt;
&lt;P&gt;Yes you are correct I will be acquiring the data from 5 DI lines and at one time only 1 coil will be connected so that will give me 1 and as soon as I get 1(High) on that line I should proceed further and if no coil is connected i will be getting 0 and a messege will appear that no coil is connected.&lt;/P&gt;
&lt;P&gt;Although if I use the Read Digital&amp;nbsp;Channel example from NI examples and just use 5 lines and array of 5 boolean elements , will that work with my problem..????&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Another problem I want to discuss is that I have to glow some LED indicators having rating 24V DC&amp;nbsp;on the front panel ...so If I use the Write Data Port example from NI &amp;nbsp;and I make a constant Boolean of High(1) the data to write on the channel.........so will my indicator glow ?? I am using 6515 card and LV 8&lt;/LI&gt;&lt;/OL&gt;
&lt;P&gt;With regards&lt;/P&gt;
&lt;P&gt;James P. Martin&lt;/P&gt;&lt;P&gt;Message Edited by ramzi on &lt;SPAN class="date_text"&gt;06-20-2006&lt;/SPAN&gt; &lt;SPAN class="time_text"&gt;04:37 AM&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jun 2006 09:32:54 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/Digital-Input/m-p/380791#M190789</guid>
      <dc:creator>james_p_martin</dc:creator>
      <dc:date>2006-06-20T09:32:54Z</dc:date>
    </item>
    <item>
      <title>Re: Digital Input</title>
      <link>https://ni.lithium.com/t5/LabVIEW/Digital-Input/m-p/380880#M190842</link>
      <description>&lt;DIV&gt;&lt;/DIV&gt;
&lt;P&gt;Yes, you can use an array of five elements and then do a search array to see which element is true. I think I would set the DAQmx Read to return a number and just wire the output to a case statement. You would have case values of 0,1,2,4,8,16 that would represent none detected, bit0 high, bit1 high, etc.&lt;/P&gt;
&lt;P&gt;The 6515 can output 30V so assuming you connect the digital output to the LED correctly, it should glow.&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jun 2006 13:21:40 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/Digital-Input/m-p/380880#M190842</guid>
      <dc:creator>Dennis_Knutson</dc:creator>
      <dc:date>2006-06-20T13:21:40Z</dc:date>
    </item>
    <item>
      <title>Re: Digital Input</title>
      <link>https://ni.lithium.com/t5/LabVIEW/Digital-Input/m-p/381978#M191368</link>
      <description>&lt;DIV&gt;&lt;/DIV&gt;
&lt;P&gt;Hi Dennis&lt;/P&gt;
&lt;P&gt;I also want to ask another thing that , in the proposed machine I have a Reset and emergency botton which acts as digital inputs to my DAQ Card, so whenever the operator presses the Reset button it means the machine was stopped during some fault and also my LV program has also stopped so by pressing the Reset my all values will be initialised and by pressing emergency button my LV program as well as the machine should stop......but&lt;EM&gt;&amp;nbsp; &lt;/EM&gt;I am in a fix that these two inputs can occur any time during the test .......(means that any operator can press emergency button anywhere between the test cycle) so where can I entertain&amp;nbsp;that Emergency Digital Input&amp;nbsp;in between my LV code such that my machine and LV program should stop.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;with regards&lt;/P&gt;
&lt;P&gt;James&lt;/P&gt;</description>
      <pubDate>Thu, 22 Jun 2006 07:26:30 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/Digital-Input/m-p/381978#M191368</guid>
      <dc:creator>james_p_martin</dc:creator>
      <dc:date>2006-06-22T07:26:30Z</dc:date>
    </item>
    <item>
      <title>Re: Digital Input</title>
      <link>https://ni.lithium.com/t5/LabVIEW/Digital-Input/m-p/382320#M191526</link>
      <description>&lt;DIV&gt;&lt;/DIV&gt;There's a couple of ways that you could do this. You could put the digital read in the timeout event of an event structure. As long as you don't have any events with while loops in them (not recomended), you would check the status at the timeout value. You could also have a separate while loop that does nothing but read the inputs. You could then pass results to the main loop via a queue or even local variables.</description>
      <pubDate>Thu, 22 Jun 2006 16:37:47 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/Digital-Input/m-p/382320#M191526</guid>
      <dc:creator>Dennis_Knutson</dc:creator>
      <dc:date>2006-06-22T16:37:47Z</dc:date>
    </item>
    <item>
      <title>Re: Digital Input</title>
      <link>https://ni.lithium.com/t5/LabVIEW/Digital-Input/m-p/382366#M191546</link>
      <description>&lt;DIV&gt;&lt;/DIV&gt;
&lt;P&gt;James:&lt;/P&gt;
&lt;P&gt;Regarding your ESTOP- If possible, your estop should directly disable the equipment electrically. Do not use it solely as an input to the DAQ card for your program to monitor and stop the equipment. If your program hangs or Windoze crashes and you need to shut down the equipment in an emergency, it won't happen.&lt;/P&gt;
&lt;P&gt;I suggest you get an ESTOP that has two sets of contacts (poles). One is used to remove power or disable the equipment, the other is wired to the DAQ card to monitor that it has been pressed and take the appropriate actions in software.&lt;/P&gt;
&lt;P&gt;Just my opinion and firsthand expereince.&lt;/P&gt;</description>
      <pubDate>Thu, 22 Jun 2006 17:36:13 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/Digital-Input/m-p/382366#M191546</guid>
      <dc:creator>AnalogKid2DigitalMan</dc:creator>
      <dc:date>2006-06-22T17:36:13Z</dc:date>
    </item>
    <item>
      <title>Re: Digital Input</title>
      <link>https://ni.lithium.com/t5/LabVIEW/Digital-Input/m-p/382376#M191549</link>
      <description>Just as an addition to what AKTDM said, if you need government safety
approval for your test setup, you might have a hard time passing it
unless you have a hardware E-STOP as well.&lt;BR /&gt;
&lt;BR /&gt;
I know we've been required to do that here for some time.&amp;nbsp; It also
takes a lot of the pressure off the software, since you know no matter
what they equipment will be shut off.&lt;BR /&gt;
&lt;DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 22 Jun 2006 17:55:35 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/Digital-Input/m-p/382376#M191549</guid>
      <dc:creator>Will.D</dc:creator>
      <dc:date>2006-06-22T17:55:35Z</dc:date>
    </item>
  </channel>
</rss>

