<?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: labview versus labwindows in LabVIEW</title>
    <link>https://ni.lithium.com/t5/LabVIEW/labview-versus-labwindows/m-p/282852#M149259</link>
    <description>&lt;DIV&gt;Thanks alot for the response. We are not going to program the microcontroller with this tool, only communication and presenting datas. Can Labview handle MODBUS communication?&lt;/DIV&gt;</description>
    <pubDate>Fri, 28 Oct 2005 13:12:38 GMT</pubDate>
    <dc:creator>Christian_nor</dc:creator>
    <dc:date>2005-10-28T13:12:38Z</dc:date>
    <item>
      <title>labview versus labwindows</title>
      <link>https://ni.lithium.com/t5/LabVIEW/labview-versus-labwindows/m-p/282751#M149205</link>
      <description>&lt;DIV&gt;I have a few questions concerning labview and labwindows. I work for a small company and we need tools for new software development. We have considered both labview and labwindows. I have some basic knowledge from labview, but never tried labwindows my partner has only tried labwindows, but is experienced in C programming. &lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;What should we choose? We are developing a tool for processing data from a microcontroller. We need a graphical illustration of the received datas and possibilities to communicate with the mc.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Thnx.&lt;/DIV&gt;</description>
      <pubDate>Fri, 28 Oct 2005 06:38:34 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/labview-versus-labwindows/m-p/282751#M149205</guid>
      <dc:creator>Christian_nor</dc:creator>
      <dc:date>2005-10-28T06:38:34Z</dc:date>
    </item>
    <item>
      <title>Re: labview versus labwindows</title>
      <link>https://ni.lithium.com/t5/LabVIEW/labview-versus-labwindows/m-p/282829#M149246</link>
      <description>&lt;P&gt;Both will work.&amp;nbsp; Labview is much easier to learn but if you there is an experienced c programmer then the learning curve shouldn't matter.&amp;nbsp; I would suggest using Labview since it is much faster to develop and debug.&amp;nbsp; However if you are looking to program the microcontroller in addition to just processing data from the controller then a c language would make more sense.&amp;nbsp; I have programmed in both (more in c/c++ than Labwindows/cvi) and most often choose Labview for my projects.&amp;nbsp; Usually choosing labview makes the project much faster to develop and maintain but there are a few limitations in labview where it cant be used (yet).&lt;/P&gt;
&lt;P&gt;Paul&lt;/P&gt;
&lt;DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 28 Oct 2005 11:53:11 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/labview-versus-labwindows/m-p/282829#M149246</guid>
      <dc:creator>falkpl</dc:creator>
      <dc:date>2005-10-28T11:53:11Z</dc:date>
    </item>
    <item>
      <title>Re: labview versus labwindows</title>
      <link>https://ni.lithium.com/t5/LabVIEW/labview-versus-labwindows/m-p/282849#M149256</link>
      <description>&lt;P&gt;I agree with Falkpl,&lt;/P&gt;
&lt;P&gt;I am actually using CVI at the moment.&amp;nbsp; And I often miss LV.&amp;nbsp; As for programming microcontrollers, you'd be amazed at what you can do with Labview and how fast you can implement it.&amp;nbsp; I have used LV to interface with embedded OS, such as VxWorks, Linux, and to program the target using a wide variety of tools.&amp;nbsp;&amp;nbsp; From a test / system configuration point of view, so far, I could implement anything in Labview that I could do in C.&amp;nbsp; Implementing user interfaces is much faster in LV.&lt;/P&gt;
&lt;P&gt;Ray&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 28 Oct 2005 13:08:30 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/labview-versus-labwindows/m-p/282849#M149256</guid>
      <dc:creator>Ray.R</dc:creator>
      <dc:date>2005-10-28T13:08:30Z</dc:date>
    </item>
    <item>
      <title>Re: labview versus labwindows</title>
      <link>https://ni.lithium.com/t5/LabVIEW/labview-versus-labwindows/m-p/282852#M149259</link>
      <description>&lt;DIV&gt;Thanks alot for the response. We are not going to program the microcontroller with this tool, only communication and presenting datas. Can Labview handle MODBUS communication?&lt;/DIV&gt;</description>
      <pubDate>Fri, 28 Oct 2005 13:12:38 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/labview-versus-labwindows/m-p/282852#M149259</guid>
      <dc:creator>Christian_nor</dc:creator>
      <dc:date>2005-10-28T13:12:38Z</dc:date>
    </item>
    <item>
      <title>Re: labview versus labwindows</title>
      <link>https://ni.lithium.com/t5/LabVIEW/labview-versus-labwindows/m-p/282858#M149263</link>
      <description>&lt;DIV&gt;&lt;/DIV&gt;Yes, you can find different drivers for Modbus, which work in LabVIEW or you can implement the Modbus-Protocol by your own.</description>
      <pubDate>Fri, 28 Oct 2005 13:17:52 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/labview-versus-labwindows/m-p/282858#M149263</guid>
      <dc:creator>zav</dc:creator>
      <dc:date>2005-10-28T13:17:52Z</dc:date>
    </item>
  </channel>
</rss>

