Jump to content

jridpath

NI
  • Posts

    5
  • Joined

  • Last visited

Everything posted by jridpath

  1. It sounds like you are trying to connect to the Linux system via telnet. LabVIEW by itself does not directly support the telnet protocol. You can use PuTTY as a client and call it from LabVIEW. There is a KB article on it here: http://digital.ni.com/public.nsf/allkb/816...625708200601E5C You can also purchase the Internet Connectivity Toolkit. It includes VIs specifically for the telnet protocol. The current shipping version will only work with LabVIEW 7.0 or higher, so you will need to udgrade as well if you choose that route. Of course if you upgrade, you will get the SMTP VIs that will allow you to connect to an SMTP server and send an email directly from LabVIEW. They were added in 7.0. There is a catch with using them and that is that they do not support SMTP authentication. If the SMTP server you are sending the email through requires a login before sending then they will not work. Also, they do not come with the Base package, so you will need Full or Pro. The TCP VIs are pretty low level. You can read and write to a port, but the protocol that is being used on that port is not taken care of for you, be it telnet, ftp, smtp, http, or whatever. You can write the code to handle sending and receiving data for a particular protocol, but that is a lot of extra work. They are really designed for creating custom client/server applications. John Ridpath
  2. Hi Jose, Well I can tell you why the code you posted is not going to work. The "Save a Copy" property on the invoke node is for saving a copy to a new file name, and it is defaulted to false anyway. I am still a beginner, but I would think the best way would be to call your sub VIs using a Call By Reference Node and to use a Close Reference VI to close it before executing the Quit VI. When you close the reference to the sub VI it will not prompt you for saving changes. Take a look at the "Dynamic Load Example.vi" that ships with LabVIEW. John Ridpath
  3. Now that is something that I was not aware of. That is pretty cool. Since it runs Windows natively, there should be no driver problems. Thanks for pointing it out to me. No one ever sent the the memo on it . John Ridpath
  4. I do not know if you can run Windows directly on any Mac, Intel based included. I think you can only run Windows through Virtual PC or Parallels. I have heard that NI-488.2 can run though Parallels, but have not confirmed it. I do know that NI-DAQmx will not run through Virtual PC. If you can run Windows directly on a Mac, and not use OS X at all, please let me know. Maybe I have the wrong assumption. John Ridpath
  5. You might want to look at using Compact FieldPoint instead of CompactRIO. You can cut the cost by using an 1804 or 1808 backplane and connecting to it via ethernet. That way you can keep the computer far outside the harsh environment. You can choose to use a BP-4 or BP-8 backplane with an RT controller for more deterministic control. Using the ethernet backplane allows you to connect to a standard PC and will not require any additional LabVIEW modules, such as RT or FPGA. This would probably be the lowest cost option, and since it will still be running under Windows, you can use all of your database VIs to easily store the data. Depending on the I/O you need, you can probably come in around the 3K range. Using a Windows system with an RT controller, (and LabVIEW 8.0 and higher), you can used shared varibles to transfer data over ethernet back to a progam running on the PC to log it to a database. This is very easy to do, now that you don't have to mess with RT FIFOs anymore. I would not suggest the Mac Mini due to driver issues. NI is not currently supporting the new Intel based Macs, and dropped RT support on Macs some time ago. I know that there has been several issues with drivers trying to run through Virtual PC on a Mac. If you choose to develop on the Mac, you will need to purchase a new Mac license for LabVIEW and the database tool kit is not available for it. The database tool kit is ActiveX based, and therefore only compatible with Windows. John Ridpath
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.