Jump to content
Sign in to follow this  

Problem with Labpython for a newbie

Recommended Posts

Hi all,

I'm a beginer, and I'm french, so sorry formy mystake in programing and in english.

I have to use a python script into labview 2010. I use Vi Package Manager to instal Labpython find in OpenG source. It seems that I have a problem if initialisation of Labpython

The example box of Labpython doesn't work has you can see on this Print Screen.

Thank you for your futur reply.

Thibault Menard


Share this post

Link to post
Share on other sites


Try setting the server path to whichever Python dll you have.

  • Like 1

Share this post

Link to post
Share on other sites

The easiest approach is to install Python2.5, you can use other (newer) python, but it takes some work and to be honest you can get all you need from Python2.5.

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

  • Similar Content

    • By damagor
      I have installed LabPython successfully few days ago. My goal is to experiment the possibility of calling machine learning library from python into the labview environment. So I want to run a LabPython script node that will read two local csv files for the inputs of random forest classifier. The output of the python script is the final predicted class in string format.
      What I did to make this work: I have set the server path to where my python27.dll located. The script is running fine until it comes through machine learning library. It ran but struck forever to run. I can ran this exactly same code in my cmd command. 
      I believe the issue rises with calling the machine learning library. Is there anyway that I can get around with this or suggest a better way to do without python script node? 
      Thank you,
      Labview 2015 32bits
      python 2.7 32 bits
      windows 10 

    • By damagor
      Hi there,
      I wonder anyone out there having issue installing the latest LabPython v4.0.04. The Laview system i have is 2015 32 bit, windows 10, python 2.7. I tried to install the vip package from sourceforge using VI package manager. Then it showed me error code 8 saying the installation was not completed. 
      Any thoughts anyone as to what's going on ?  Could someone who has similar experience help me out on getting Labpython installed in my LV? 

    • By Argold
      Hello there:
      I have a big project, pretty much already coded in Labview, designed to perform monte-carlo analysis on a set of applications that use data from time synchronized measurements across the electrical power system.
      The project is designed to be open source and distributable using both built .exe and vipm.  Therefore I include ONLY libraries that either come with LV or are OpenG (no third party tools that need to be purchased, and no TestStand).
      A part I have yet to code is the monte-carlo engine which needs to be end-user programmable.  I have an idea for creating my own set of commands and a labview interpreter, but before I do that, I'm thinking that many of my end users will already have some python ability.  So I'm trying to decide to use labPython.  The problem is that I have not found any documentation or examples for it yet.
      What I need to do, is have the python script, written by the user, access controls (mainly clusters or 2-D tables), overwrite the LV control values, then start a test run.  This is essentially test automation.  Python would be nice because then the user can use local variables to calculate the values to be written into the controls.
      So I'm looking for your advice:  Should I give LabPython a try?  If so can someone:
      1) point me to some documentation
      2) point me to some example code (especially how to access controls).  
      3) tell me where to go when I need to ask for help (this forum or another)
      Thank you so much.
    • By gb119
      I'm seeing a slightly weird (and inconvenient) bug with LabPython...
      I've a Windows 7 64bit machine with 32bit LabVIEW 2012 and 32 bit LabVIEW2013 and both 64bit and 32bit Python 2.7 installed (the former I use standalone, the latter is just for linking to some LabVIEW code that makes use of LabPython). My  32bit python27.dll therefore lives in C:\Windows\SysWOW64\ and I point LabPython to it (for both versions of LabVIEW) and can see in both labview.ini files that the correct key has been added.
      On LabVIEW 2012, everything work s absolutely fine.
      On LabVIEW 2013, if I load a VI containing the Python script node, it complains that it can't load lvpython.dll via a debug window message. This is uually followed by a fatal exception, which is not a massive surprise ! If I use the LabVIEW vi API to the LabPython, then I don't have load errors and LabVIEW crashes about as much as it normally does.
      The only other LabVIEW 2013 setup that I've played with are 32bit Windows 7 machines running 32bit LabVIEW 2013 only, and they seem all fine.
      My current workaround is to load the VI that creates a session in the LabVIEW vi API mode of LabPython operation, thus forcing the dll to load, which then seems to let me load and use the script node (which sort of makes sense as Windows will use the already loaded dll rather than loading it again) - but it's a little messy and doesn't explain why LabVIEW 2012 works just fine....
      Any thoughts anyone as to what's going on ?
    • By Erik Hebestreit
      I try to use LabPython with Python 2.7.8. After some difficulties in the beginning I am now able to run simple scripts and also import certain modules, for example the following:
      import numpy sampling = 1/timestep millivoltage = numpy.std(voltage)*1000 But if I now try to add a def statement (like the one below) to the script, the VI gets stuck at PYTHON Execute Script (if it is called) or throws a ZeroDivisionError (if it is just added but not called in the script):
      def test(): return 0 Are there certain things that are forbidden when using LabPython like certain statements? I just noticed that I have to put the def to the beginning.
      If I now try to add a self written module to python and try to load it the PYTHON Execute Script VI freezes as well. I attached the file.
      What would be the right way to use a self written module in LabPython? Can I put the file somewhere, where LabPython is checking? In which directory is LabPython running?
      Furthermore I wonder if there is any way to run a script file in LabPython, or do I always have to copy the code to a String-Box?
      Best, Erik
  • Create New...

Important Information

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