Labview 2013 missing smtp VIs from Labview 2011

We are upgrading to LabView 2013 and any VI that we open that uses SMTP is broken. It seems that NI updated the SMTP functionality but do we have to rewrite every VI that was using SMTP to mail emails from our applications? Are the old 2011 VIs avalable in 2013? Two that we use a lot are "SMTP Send Message.vi" and "SMTP Send File.vi". Where can we find these and any others for LabView 2013?

0utlaw wrote:
It appears that they've been replaced with the SMTP Email VIs available in Data Communication>>Protocols>>SMTP Email - there's .......  The old functions are still present at <root>\National Instruments\LabVIEW 2013\vi.lib\Utility\SMTP, but don't appear in the palettes.   
That's actually where I went to look for my SMTP e-mails in LV 2012.  The VI hierarchy path for these VI's is LabVIEW 2012\vi.lib\Utility\SMTP\smtpeml.llb  I thought those were the VI's the original poster was looking for and not finding.
0utlaw wrote:
- there's even a nifty-looking Send Email express VI I wasn't aware of.   
I haven't seen that in 2012.  Maybe that is a new addition to LV2013.

Similar Messages

  • Conversion of VIs from LabView 2013 to 2011

    Hi,
    I would be grateful for conversion of zipped VIs from LabView 2013 to 2011.
    Thank You,
    Michal
    Solved!
    Go to Solution.
    Attachments:
    main VIs.zip ‏38 KB

    Here you go.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Attachments:
    main VIs 2011.zip ‏27 KB

  • Please Convert Vis from Labview 2013 to Labview 2011

    Please convert the attached Vis from Labview 2013 to Labview 2011
    Solved!
    Go to Solution.
    Attachments:
    Convert from2013 to 2011.zip ‏255 KB

    Here you go.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Attachments:
    Converted to 2011.zip ‏176 KB

  • Where to download the exercise VIs from "LabView Basics II"?

    Hello everybody,
    Where can I download the files with sample Vis for "LabVIEW Basics II" course?
    In the company I currently work, they couldn't find these files. I have got only books.
    TIA,
    Yazilim.

    I think you have to purchase it. Contact NI for more information.
    Nam.
    Yazilim wrote in message
    news:[email protected]..
    > Hello everybody,
    > Where can I download the files with sample Vis for "LabVIEW Basics II"
    > course?
    > In the company I currently work, they couldn't find these files. I
    > have got only books.
    > TIA,
    > Yazilim.

  • How can I get handle(s) to and poll non-LabVIEW window(s)/application(s) from LabVIEW?

    Want to launch EXE from LabVIEW, wait for user to finish with EXE's UI, and once they closed it, return execution flow in LabVIEW. Cool, no problem.
    Used the System Exec VI and with the "wait until completion" = TRUE the EXE never launches. Not sure why.
    With the "wait until completion" = FALSE, the application runs with no problems, but now LabVIEW no longer waits.  Can't tell when user is done.
    Work around idea... Once the Sys Exec VI launches the EXE, wait and poll some Windows API call to see when the window for the specific EXE closes. Cool.
    I know G and no C.  What I would ideally like is a DLL, that I can wrap with the DLL Import Wizard.  Of course best would be a VI and the wrapped API call.
    Any ideas?
    Scott Rogers
    Sr. DSM
    Western NY

    You could try it with a pipe. With a pipe you can open an exe, and interact
    with it through a read and write reference. Although in your case the exe
    might not start, since the normal sysexec doesn't start it...
    http://forums.ni.com/ni/board/message?board.id=170&message.id=270461&requireLogin=False
    Regards,
    Wiebe.

  • Como instalar Labview 2013 SP1 si tengo instalado Labview 2013

    Buenos Días,
    tengo Instalado Labview 2013 y quisiera saber si tengo que desinstalarlo para instalar labview 2013 SP1
    Espero sus respuestas
    Gracias!
    Solved!
    Go to Solution.

    * Yo no hablo español. He utilizado Google Traductor. 
    No. Usted debe ser capaz de instalar LabVIEW 2013 SP1 en la parte superior de la original de LabVIEW 2013. No debería haber necesidad de desinstalar. Sólo asegúrese de que usted tiene el Programa de Servicio Estándar (SSP). LabVIEW 2013 Service Pack 1 es una actualización exclusiva para LabVIEW 2013 para el Programa de Servicio Estándar (SSP) a los clientes.
    descargar
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    *I do not speak Spanish.  I used Google Translator.
    No.  You should be able to install LabVIEW 2013 SP1 on top of the original LabVIEW 2013.  There should not be a need to uninstall.  Just make sure you have NI Standard Service Program (SSP).  LabVIEW 2013 Service Pack 1 is an exclusive update to LabVIEW 2013 for NI Standard Service Program (SSP) customers.
    Download
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    If someone helped you out, please select their post as the solution and/or give them Kudos!

  • VIs from LabView libraries not found in .exe built with Application Builder

    I have added VIs that are called by reference to the dynamic vi list in the App Builder, but some of them fail to run because of sub VIs that aren't found at runtime.
    These sub VIs are from the standard LabView libraries. For example: "Open/Create/Replace file.vi", "Write Key (I32).vi", "Open File+.vi" and "Read File+ (string).vi". Also, a typedef "ADC.flx.ctl" can't be found(from the Motion CustomControls library).
    Even if I have those VIs open when I compile all of my VIs (using Ctrl-Shift-Run), they can't be found when I run the executable.
    Brian Smith
    Advanced Light Source
    Lawrence Berkeley National Laboratory

    Are you running the executable on the development machine? If not, make sure that all the required drivers are installed on the target machine (i.e. NI-MOTION etc.).
    The version of the LabVIEW Runtime Engine also has to be the same as the LabVIEW development version.
    Under �Application Builder >> Target >> Build Options� make sure to choose �Single target file...�. This way all sub VIs will be compiled into the executable.
    In LabVIEW 7.1 you can choose to �Disconnect type definitions�� under the �Application Settings� in Application Builder. Does it help to remove the checkmark?
    Best regards,
    Philip C.
    Applications Engineer
    National Instruments
    www.ni.com/ask
    - Philip Courtois, Thinkbot Solutions

  • Opening LabView version 5.1 VIs in LabView Version 8.5

    We are trying to open VIs saved in LabView version 5.1 with LabView version 8.5 and we are getting error code 10.  The error message states that version 5.1 is too old to be opened in version 8.5, yet on the knowledge base files seem to indicate that it should be okay.  Can you tell us how we can open these older files in LabView 8.5?
    Thank you,
    Keir Neuman

    You can't. The earliest that 8.5 can open is version 6 VIs. See http://forums.ni.com/ni/board/message?board.id=170&message.id=271171. If you have any version of LabVIEW between 6.0 and 8.2, you can open them with that, save them and then open them with 8.5.

  • Adobe Presenter 9 and PowerPoint 2013 - Missing Import Audio from PowerPoint button

    I am only able to intermitantly use the Import button in Adobe Presenter 9 to Import Audio from PowerPoint. Why would I be able to do it on some presentations but not all? I thought it was an audio conversion issue but even when I convert the audio (when prompted by PowerPoint) it doesn't always allow me to import it.

    I have found a solution if the original PowerPoint was a ppt file, follow these steps:
    File > Save As a pptx file
    Close PowerPoint (this helps with not corrupting the file)
    Re-open the pptx file
    File > Convert
    Save with a new file name (this helps with not corrupting the file)
    You should now have the Import from Presentation button if you go to the Presenter tab and click the Import button
    I have not found a solution for pptx files yet.

  • LabVIEW 2013 locks up while loading new VI

    When attempting to load an existing VI while a project is open and the new VI caues conflicts LabVIEW shows a warning window.  If LabVIEW has a loading window open when the conflicts message appears then LabVIEW becomes unresponsive on all of its windows except for the help window.  The buttons appear to function but nothing happens.  I can move the Loading ... window around but none of the others.  I left it for 30 minutes yesterday (different VI that I was trying to load) but no joy.  I had to kill LabVIEW and lost my work.  Same situation today.  These were both examples I downloaded from this forum.
    How can I avoid this problem in the future?
    Thank you.
    See attached image
    Windows 7 64-bit
    LabVIEW 2013, updated to current
    Attachments:
    LabVIEW Hang.jpg ‏83 KB

    The problem has reoccurred 3 times this morning (see attached image for the 3rd lockup).  All with local files.  I have a LabVIEW project open, when I open a VI outside of the project (using windows explorer) I sometimes get the mxLvGetFilePathBatch.vi loading message and then LabVIEW freezes.  mxLvGetFilePathBatch loading message is the last apparent LV action every time before the lockup  This happens when the loading window opens while another LabVIEW related popup is showing.  See attached image where I was trying to examine a vi that is in my user.lib while LabVIEW was open.  In this case the VI is referenced by the project (strict static vi reference) but that is not always the case.  The first two lockups this morning were with nonproject VIs that use some of the same user.lib VIs as the project.  My user.lib is at the default location in the LabVIEW program directory.
    The attached txt file is in html format, it is a table listing my installed packages.  An export from JKI package manager, massaged with excel for readability.
    I would appreciate any ideas on how to proceed with debugging this problem.
    Attachments:
    7-15-14_3rd_hang.jpg ‏50 KB
    InstalledPackages.html.txt ‏10 KB

  • How to call a Linux exe from LabVIEW for Windows

    Hello,
    I need to call a non-LabVIEW Linux executable using LabVIEW for Windows. Any suggestions, aside from buying LabVIEW for Linux?
    Thank you,
    Chris White

    Okay, I'll throw out a few ideas and I'll let you pick which one you may think is easiest.
    1. Use the internet toolkit ($$$) or build a simple telnet client yourself in LabVIEW (use the TCP VIs in labview). This would allow you to connect to the telnet port of your linux box, login, password, and execute a command. (You'll probably want to use nohup, do a man on nohup to find out more).
    2. Install SSH daemon on your linux box, and an ssh client on your windows machine. You can't get SSH for windows from cygwin. This would be more secure, and you wouldn't need to use the TCP VIs, you could simply use the "system exec" vi to call SSH.
    3. On your linux box, install your app in inetd. Then, whenever someone connected to a certai
    n port # on the linux box, it would execute your command. A little dangerous because someone might try to connect 50 million times (or a port scan) and kill your box. You also wouldn't be able to send a dynamic command line argument.
    4. Write a small TCP application on your linux box to wait for connections (listen for command line options) and execute your command.
    You'll probably find one of these options ideal depending on your administration and programming background.

  • Is it possible to call DLL develloped with LabView 7.0 in LabView 6.0.2 VIs?

    Hello,
    I would like to devellop DLLs in LabView 7.0 and use them in LabView 6.0.2.
    Is it possible???
    I tried this operation. I generated an installer (with the LabView 7.0 runtime in) and tried to load the DLL in a LabView 6.0.2 VI.
    When I run the VI, LabView 6.0.2 is crashing...
    Here my export function prototype:
    typedef struct
    LVBoolean status;
    long code;
    LStrHandle source;
    } TD1;
    typedef struct
    long dimSize;
    unsigned char Numeric[1];
    } TD2;
    typedef TD2 **TD2Hdl;
    void __cdecl driver(LVBoolean *SendCommand, unsigned char DataToSend[], long LenDataToSend, char RHICommandString[], TD1 *errorInNoError, LVBoolean *GetAnswer, LStrHandle *FrameReceivedID, long *Da
    taLength, TD2Hdl *DataReceived, TD1 *errorOut);
    Any example ???
    Thanks for your help,
    Regards, Pascal.

    Hi Pascal,
    I made a simple dll in LabVIEW 7 and called it from LabVIEW 6.0 and it worked fine.
    I have attached the dll I built. It adds two numbers.
    double Testdll(double B, double A);
    Try using this and see if it works for you.
    Feroz
    Attachments:
    SharedLib.dll ‏17 KB
    SharedLib.h ‏1 KB
    SharedLib.lib ‏3 KB

  • Accessing the Solver AddIn to Excel from LabVIEW

    I would like to be able to set the parameters and run the Solver AddIn in Excel from LabVIEW. I know that from LabVIEW you can install the different AddIn's but is there anyway to access the actual AddIn once it has been installed?

    Hi Karin -
    I believe your answer is ActiveX.
    Briefly, ActiveX allows application a (e.g. LabVIEW) to control application B (e.g. Excel, Word, etc.) programmatically. The kicker is that application B must export that functionality to LabVIEW. We ship an example with LabVIEW that controls Excel via ActiveX, it will give you a head start. We do not provide extended support for ActiveX programming simply because there are literally thousands of applications we could control. Microsoft might be able to shed more light with an Excel ActiveX programmer's reference or some relted document.
    good luck-
    ben schulte
    national instruments

  • Mise a niveau Labview 2013 vers 2014

    Bonjour,
    Je dispose d'un programme de labview dernierement compilé avec labview 2013, et apres installation de labview 2014, j'ai essayer d'ouvrir mon programme dernierement compilé avec labview 2013,avec labview  2014, mais cela souvre mais je n'arrive pas a le compilé et il m'affiche des erreurs sur une des mes sous VI,
    Etant donné que je suis novice avec labview, puissez vous m'aider svp en m'éclairant sur cette question.
    Je vous remercie d'avance de votre réponse;
    Cordialement,

    Kathiaswe wrote:
    Hi,
    My error is: your Vi can't executed, can you corect your error. ça donne ça car j'utilise la version en français.
    Mercii
    Il n'y a définitivement pas assez d'information pour être d'une quelconque aide. Ouvrir le sous-vi en erreur et cliquer sur la flèche blanche (run) et une fenêtre d'erreur ouvrira. Poster l'information détaillée de cette fenêtre d'erreur, à partir de cet information nous seront plus en mesure de vous aider.
    Ben64

  • Please Convert from LabView 2013 to 2011

    Hello, Could someone please convert these VIs from LV13 to 11 please?
    Thanks, 
    Laura
    Solved!
    Go to Solution.
    Attachments:
    Syringe Pumps New.zip ‏953 KB

    Here you go.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines
    Attachments:
    Syringe Pumps New.zip ‏364 KB

Maybe you are looking for