Labview and engine dyno (newbie)

I am totally new to labview. I recently purchased various parts from a
"Mustang" automotive engine dyno. I got the eddy current unit, the
load cells, and shaft encoders. I was unable to get the control unit
and a/d cards for the computer so I am researching options, and
looking for some help on the computer end. My current plans are to
hook it all up manually with a hydraulic load cell and manual current
control but down the road I'd like to ad computer control when I can
afford it.
A few questions: Will labview let me program an interface to read all
my sensors? Will an older copy of labview work? (maybe someone has an
older copy to sell?) What do I need to make the load cells work with
the computer? Do I need an amp of so
me kind? (there is an amp card in
the junction box) I'd like to be able to control the eddy current
unit with the computer also. Any feedback would be helpful. I'd like
to startout simple and maybe ad more sensors later for airflow, fuel
flow, thermocouples. I'm also doing this on a budget since I don't
have some high $$$ corporate sponsor. Thanks in advance.
Bruce
Please feel free to email me off the newsgroup.
"advanced dealer in the great material continuum"

In article , smcfarl1
@rochester.rr.com says...
> I have used the microsoft activex xml components to do what you are
> describing. The LabVIEW activex interface does not
> keep track of the open references so you have to be very carefull about
> closing all references.
> Stu
>
> > --
> > After three days in the desert fun
> > I was looking at a river bed
> > And the story it told of a river that flowed
> > Made me sad to think it was dead
>
>
>
I've looked on the microsoft site but I didn't find anything. Could you
be a little more specific? The only XML related activex I've found (via
google) is Redix, nothing by microsoft.
Thank you for your patience
eXistenZ
After three days in the desert fun
I w
as looking at a river bed
And the story it told of a river that flowed
Made me sad to think it was dead

Similar Messages

  • Version conflicts between host labview and RT engine

    there is problem that i cannt switch target to feild point. It said that "version conflicts between host labview and RT engine" . But my labview is version 7.0 and the real time module is version 7.0 too. Anyone can give me hand? Thanks

    Depending on your version of MAX, you should be able to change the version on the FP (in remote systems). If you can't do it in 3.0, try upgrading to 3.1 (you will have to search for it on the site). If that doesn't work, you can try resetting to factory default and then see if you can do this.
    Another tip, which for some reason seems to help, is updating the OS\Run-Time Engine when windows is in safe mode.
    Try these and see if they help.
    BTW, as a tip for next time, you're more likely to get a good answer for something like this if you post in the FieldPoint board.
    Try to take over the world!

  • Please help me with my electrical engineering homework : temperature control and watering system for greenhouse using labview and arduino

    temperature control and watering system for greenhouse using labview and arduino
    spesification :
    1. max temp : 28 celcius (when temperature is more than 28 celcius, fan ON)
    2. min temp : 20 celcius (when temperature is under 20 celcius, heater ON)
    3. watering system : aquaponic (grow plant and fish in separate tank but connect each other). Plant roots help filter water for fish. Fish poop for plants fertilizer. So I need a pump to distribute water.
    Please help me create VI file simulation.. I'm sorry I'm not fluent in English. May God bless you all
    Attachments:
    YOOOSHH.vi ‏88 KB

    Duplicate thread.   Please keep the discussion in that thread where you already have a response. It is also the more appropriate thread for your question.
    Lynn

  • LabVIEW Runtime engine on Windows Embedded Standard 7 P 32/64 bit?

    Did anyone ever try to install and run LabVIEW Runtime engine (2011 or later) on Windows Embedded Standard 7 P 32/64 bit?
    I am trying to figure out if this will work, for example on a Beckhoff CX5120 embedded PC. I will need to have some simple TCP/IP communication in order to exchange information with another PC, but nothing else, i.e. drivers, etc...
    I hope someone tried to do this already. I just don't have the right hardware right now to check it out.
    Solved!
    Go to Solution.

    As NI sells touch panels with WES7 installed here: http://sine.ni.com/nips/cds/view/p/lang/en/nid/210551 it's pretty safe to assume they've used the RTE on WES7.
    But yes, it's been done.

  • Large applications - Labview and other programming languages

    Hello Labview Users,
    as the forum saw this very interesting thread about large applications programmed in Labview
    (see: http://sine.ni.com/niforum/niforum?requireLogin=False&forumDU=http://forums.ni.com/ni/board/message?... ) I would like to ask the community about their experiences with Labview applications in combination with other programming languages.
    In advance: I have several years of experience in programming Labview applications starting from quick-and-dirty solutions which had to run within few hours and complex test solutions. I saw Labview growing and becoming better with the released versions and lot of things I missed in former times got implemented in the meantime. Actually I have to develop a complexe ATE solution with numerous equipment to control and numerous data to be captured and archived. Despite the Verison 8 I still feel still some drawbacks of the LV concept which let me hestitate to setup the solution completly in Labview:
    1) It is alway hard to re-use code of complex applications since it is not possible to do some kind of global search an replace of functions
    variables etc. It nearly impossible to re-use approved code structures (e.g a state machine) if the "inner part" is changing more the a little bit.
    2) If the application requires a certain flexibility (e.g. exchangeable test equipment of varying vendors) this is hard to implement since you have to define a lot of parameters through your hierarchy if you dont want use global variables which slow down your application and hide
    the code functionality.
    3) Despite modern PCs the look and feel of LV applications appears somewhat slow compared to other applications. For complex user interfaces the polling methode generates a lot of complex code. (I dont have expierence with the event-structure).
    Now my questions:
    Do you have experience of implemention of complex solutions dividingthe code modules using Labview and other languages? Which other
    languages did you use? Why did you use these languages (speed, flexibility of text based code, available library functions)? Did you found out this to improve your development time and code maintainibility?
    (I concider a solution where I do the single tests with Labview-VIs but delegate all the test sequencing and data collection stuff written in PERL which allows really very compact code)
    I'm curious what your experiences are.
    rainercats

    Given that you're asking these questions in a forum for LabVIEW users the opinions given are going to be somewhat slanted towards the general like of LabVIEW. I've been working with LabVIEW for a long time, ever since 2.something on a Mac. I've written numerous large-scale applications as well as "mundane" instrument drivers. As you've noted you're experienced with LabVIEW, so you know some of its strengths and weaknesses.
    To address your specific questions:
    (1) Yes, that has always been a limitation in LabVIEW, but I don't believe it is an overriding one to choose C over LabVIEW. Putnam provided one workaround for the search and replace of VIs. Once you've programmed in LabVIEW long enough you get used to doing it this way. Is it clumsy? Yes. As for the re-use of code structures, that's not entirely true. You can create a "template" VI (a regular VI, not a .vit) that contains the code you want to re-use and place in your palette with the "Merge VI" option set. That way you can select it from your functions palette, plop it down on your diagram, and you get the "template" VI's diagram placed right into your new VI.
    (2) This is not something that is specific to LabVIEW, as this exists with any programming language. It's not the language that limits you here, it's how you've designed your code. In a language like C++ you would go with classes. You can do the same thing in LabVIEW. IVI is another option (though not preferred by me).
    (3) As Putnam mentioned, you should be using the event structure.
    Other thoughts:
    The biggest strength I see with LabVIEW is that each VI is a miniature program, which allows development and debugging of functions a snap. With a language like C you have to write another program to call that function in order to debug it. The biggest weakness? I would say user interface. Yes, even with the event structure. Don't get me wrong, the event structure has vastly improved the way user interfaces and event handling in general are done with LabVIEW, but it simply doesn't hold muster to a program written in C or VB. ActiveX anyone? LabVIEW still doesn't do ActiveX properly in terms of actually getting the controls to work. Programming ActiveX controls is just plain aggravating what with all the property nodes taking up so much diagram space.
    It certainly makes sense to use the best tools available to you to get the job done. In my recent projects I had to write software to run automated tests on some products my company made. The test modules were written in LabVIEW. The tests executive was a proprietary engine driven by a SQL Server database. I had to write a "wrapper" DLL that interfaced between the LabVIEW code and the executive since the executive hadn't been designed to call LabVIEW DLLs directly. This allowed us to use LabVIEW as the preferred language for developing the test modules and let the guys who were fiddling with the test executive do their bit. Of course, TestStand's premise is basically that.

  • Create DLL from labview and calling it from other application

    I have an application built using Labview. I wanted to create DLL out of it. The application has
    two String inputs start and stop buttons and two status indicators.
    1. How to itegrate start and stop buttons from function prototype?
    2. Does Labview created DLLs requires labview runtime engine when it is to be called from other application?
    Can some one help on this.
    Solved!
    Go to Solution.

    Hi Yuvish,
    1) They should be boolean inputs to your VI. But does it makes sense to provide a stop button input at the start of your VI? (THINK DATAFLOW!)
    2) Yes, the LV-RTE is needed...
    Best regards,
    GerdW
    CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
    Kudos are welcome

  • Unable to determine the install root path for the LabVIEW Runtime Engine

    Hi,
    i have an issue with using a LabVIEW interop assembly in a .NET application. I get an exception "Unable to determine the install root path for the LabVIEW Runtime Engine" when calling the assembly.
    The little test program is attached below. It's called dotNETHost.exe. If you excecute the programm a dialog with an button appears. Clicking the button shall open another dialog (the LabVIEW Interop component). But the only thing I get is the exception message. The ZIP folder also contains the complete exception meassage (ExceptionMessange.jpg & ExceptionDetails.txt).
    The Interop Assembly was built with LabVIEW 2011. We use Visual Studio 2010 and .NET 4.0.. The dotNETHost.exe.config file is prepared as mentioned in Knowledge base - Loading .NET 4.0 assemblies.
    The Interop assembly contains only one simple dialog (loop is finished by clicking OK) without calling any other VIs or other DLL's.  In case of this there's also no support directory generated by the build process.
    I have no idea why it doesn' work. I hope anyone can help me.
    Thanks in advance
    Kay
    Attachments:
    Debug.zip ‏75 KB

    This may be unrelated, but Labview and .Net4.0 dont work well together. Not yet anyway. I had to compile my assembly in 3.5 to get it to work.
    Please read the following:
    http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/configuring_clr_version/
    http://digital.ni.com/public.nsf/allkb/32B0BA28A72AA87D8625782600737DE9
    http://digital.ni.com/public.nsf/allkb/2030D78CFB2F0ADA86257718006362A3?OpenDocument
    Beginner? Try LabVIEW Basics
    Sharing bits of code? Try Snippets or LAVA Code Capture Tool
    Have you tried Quick Drop?, Visit QD Community.

  • Profibus-Connection with NI LabVIEW Runtime-engine

    Hi,
    I have a Profibus network running in our porduction lane.
    Now we want to report several states of this production continously.
    Therefore I want to connect a desktop-pc via profibus to the PLC. But I want to run the VI on the PC as an application(exe) with the NI LabVIEW runtime engine because I won´t install LabVIEW on this PC. (on my development computer I have LabVIEW 2011)
    My question is:
    Does the Profibus communication work if I run the VI that way if I add the needed "additional installer" to my installer file?
    I´m quite sure that it will work but I want to check this point before ordering a Profibus-Board.
    I hope you understand my question and give me a positive answer so I can order an new Profibus-PCI-Board
    best regards
    Martin

    Hi Martin,
    the scenario you are describing sounds reasonable and that should work.
    But in general, if you buy something at NI you can always call and describe your situation. Either the sales person can help you with your decision or in more complicated cases the sales person redirects you to a support engineer.
    Best regards,
    Christoph

  • Error Code "1097.....this might corrupted LABVIEW's memory.........." appears after exit the labview and re-start labview

            I have a probelm when I use the "tool/import shared library(.dll)" wizard to generate the API from C.
            The API  works correctly when I complete the wizard, but after I exit labview and re-start labview to run the API again. The error 1097 code "......this might corrupted LABVIEW's memory.............."appears.
            The only solution now is to re-generate or update the wizard to generate the API.
            I try to find the answer in
            http://digital.ni.com/public.nsf/allkb/58596F5D41CE8EFB862562AF0074E04C?OpenDocument 
            The paragraph in above article shows
             "LabVIEW does not crash until it is closed
    The most likely problem is that the DLL function being called has corrupted the memory. If you pass arrays or strings to the DLL, the DLL function cannot dynamically resize the array. Writing beyond the last element of the array or string could corrupt the memory and this may not be obvious until LabVIEW is closed."
    But it doesn't match my case. Does someone have idea about this? I Attach my .h file for reference
    Attachments:
    test_api.h ‏1 KB
    link_test_api.h ‏1 KB

    wewe1215 wrote:
            I have a probelm when I use the "tool/import shared library(.dll)" wizard to generate the API from C.
            The API  works correctly when I complete the wizard, but after I exit labview and re-start labview to run the API again. The error 1097 code "......this might corrupted LABVIEW's memory.............."appears.
            The only solution now is to re-generate or update the wizard to generate the API.
            I try to find the answer in
            http://digital.ni.com/public.nsf/allkb/58596F5D41CE8EFB862562AF0074E04C?OpenDocument 
            The paragraph in above article shows
             "LabVIEW does not crash until it is closed
    The most likely problem is that the DLL function being called has corrupted the memory. If you pass arrays or strings to the DLL, the DLL function cannot dynamically resize the array. Writing beyond the last element of the array or string could corrupt the memory and this may not be obvious until LabVIEW is closed."
    But it doesn't match my case. Does someone have idea about this? I Attach my .h file for reference
    Which of the 2 functions do you call? How?
    The documentation of InitSocketEx() seems to indicate reversed parameter order than what the function prototype looks like!
    I indeed do not see much possibilities to pass in to small a buffer that the DLL function might be overwriting past the end. This really only leaves one more possibility:
    Your DLL is doing something largely illegal somehow. Maybe something as silly as storing the reference to the ipAdress instead of the address itself. The memory passed as parameters into a C function is generally only valid for the duration of the call. This is especially true if you use LabVIEW since LabVIEW will re- and deallocate memory buffers frequently as soon as they are not used anymore and the parameter to a Call Library node is considered to not be required anymore after the function returns.
    Rolf Kalbermatter
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Running Datasocket in labview 2013 open labview runtime engine 7.0

    Hello All,
    I am trying to communicate with a COGNEX camera using Labview 2013. I am using Datasocket to read tags from cognex OPC server.
    but when I open labview and run the code for the first time. An installer will automatically pop up trying to install labview runtime engine 7.0.
    When i cancel the installation datasocket throws an error. Again if i run second time, datasocket works fine and communicate with cognex camera using OPC.
    This problem comes everytime I open labview and run the datasocket. I cancel the installer. second time onwards when i run the code everything works fine.
    This is actually annoying and i doubt how things will work when i make an executable. 
    Need help. 
    Is this due to datasocket version installed... how to resolve this.
     

    Hi phil,
    That is interesting that you were unable to find the offending key that the installation is having trouble with.  Do you have Administrator privileges on your computer? You may even want to try to log in as the actual Administrator itself to make sure that you have access to all of the proper registry keys.  Also, I was going to say that I do think you're right with Windows XP not having the Scanreg/fix function, but there are several free programs that you can download as registry checkers.  You may want to try one of those to see if you can find the key and give it the proper permission.
    As far as the other part of your question, the Run-Time Engines are very important for LabVIEW to be able to run, but the 7.1.1 Run-Time Engine should not be affecting a LabVIEW 8.2 installation as it will use the 8.2 Run-Time Engine.  One thing that you can do is go into your Control Panel under Add or Remove Programs>>National Instruments Software and you can try and repair/modify your Run-Time Engine there.  If you already have the 7.1.1 Run-Time Engine on your computer, this is where it will show up so you can make any changes you want.  Also, if you go to www.ni.com and click on "Drivers and Updates" on the right, you will be able to find the Run-Time Engine there that you will need, but I would definitely try using a downloadable registry checker first before attempting to change any of the software that is currently on your computer.  As stated in the Knowledgebase article, this is actually an error from Windows saying that the registry key does not have the proper permission settings, so I am reluctant to say that downloading the new Run-Time Engine from our website will help much.  Please try some of these suggestions out and let me know how they work out for you. Thanks!
    Regards
    Noah R
    Applications Engineering
    National Instruments

  • Labview runtime engine plugin problem in Mac OS X

    Hi:
    We have just recently acquired a macBook Pro and am trying to test some instrumentation modules we have previously developed online for Circuit Theory courses on the MAc platform.
    These VI's are installed on lab view server and we have no difficulty accessing them in Windows XP or Vista from a browser either Firefox or IE. Of course the latest version of runtime engine is installed on the pc prior to accessing the vi using remote panel and secondly we have to disable any virus protection software.
    I have also installed the 8.5 version of LV runtime engine on the macbook with Leopard 10.5.x OS. I can see the LV plugin with the proper version in the Installed plug in check for the Safari browser. But every time the Remote panel is accessed I get a missing plugin message.
    Here is the message:
    Safari cannot find the Internet plug-in.
    The page “Blackboard Academic Suite” has content of MIME type “application/x-labviewrpvi82”, but you don’t have a plug-in installed for this MIME type. A plug-in should be available on this page:
    http://digital.ni.com/express.nsf/express?openagent&code=exck2m&
    Do you want to open the page?
    The page it suggests is the NI site for the plugin download?
    I am really in a corner and donot know what I am doing is wrong? Any help will be appreciated?
    Vishnu

    I'm not a Mac expert, but it sounds like you are missing the LabVIEW Browser Plugin which is necessary to view remote front panels.  That plugin installs with the LabVIEW runtime engine which you can find here.  I don't think Safari requires any extra configuration to work with the plugin but it might... let us know if installing the runtime engine doesn't resolve the problem.
    Travis M
    LabVIEW R&D
    National Instruments

  • CIN (Code interface node) LabVIEW runtime engine dependency

    Hello:
    Am I correct that the old style CIN (code interface node) is not dependent on what version of LabVIEW runtime engine is being used?
    However if I create a dll  from say LabVIEW 8.2 I must then alway have LabVIEW runtime 8.2 installed on any newer machine with newer version of LabVIEW?
    Thank You!

    GE Osmonics wrote:
    Hello:
    What I have are old CIN (no source) that work in LabVIEW7.1 but will not work in LabVIEW 2010 (link error, object code not loaded). 
    What I thought I could do is generate dll from the vi's that contain the CIN using LabVIEW 7.1 with application builder.
     I could use the Call Library Function from LabVIEW 2010 to load the 7.1 generated dll  to effectively do what the old CIN accomplished
    provided I installed the LabVIEW 7.1 runtime engine on my LabVIEW 2010 machine
    Thanks for the input
    If the CIN resource doesn't load you most likely changed the LabVIEW platform. LabVIEW for Windows 32 Bit and LabVIEW for Windows 64 Bit are different platforms. Just as LabVIEW for Windows and LabVIEW for Macintosh or Linux. A 32 Bit DLL, which a CIN is internally can't be executed in a 64 Bit environment at all.
    Your solution fails for more than one reason here. LabVIEW will try to load and link a LabVIEW DLL into its actual runtime environment to avoid interprocess communication latency which would be inavoidable if the DLL is started in a seperate runtime engine, which is in fact a new process. If your issue is 32 bit to 64 Bit you won't be able to link the 7.1 32 Bit DLL into your LabVIEW 64 Bit application through the Call Library Node at all.
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Install MAX with only LabVIEW runtime engine

    Hi,
    I want to know if it is possible to install MAX from the Device Driver CD, when only LabVIEW RunTime engine is installed.  There is no full installation of LabVIEW on that PC.  That's MAX 3.1.1.3004 with LabVIEW RunTime Engine 7.1.
    Patrick.

    Dear Patrick,
    The device driver CD usually does not have a single installation of MAX, but you can install MAX by installing most of the other drivers such as NI-DAQ, NI-488.2, NI-Serial, etc. MAX does not require LabVIEW, so you can have MAX and LabVIEW Run-Time without LabVIEW. Have a great day!
    Sincerely,
    Marni S.

  • Installing Labview runtime engine 2011

    Hi,
    Is it mandatory to uninstall any previous version of the Labview runtime engine before installing the 2011 verstion ?
    Thanks.

    No, you should actutally keep the older runtime engine installed in case you still have applications that depend on it. The 2011 run time will only support applications built with LabVIEW 2011.
    LabVIEW Champion . Do more with less code and in less time .

  • Load Labview runtime engine with matlab platform

    When I use labview DLL on matlab platform it loads labview runtime engine.
    Once I use "close all" command of matlab, labview runtime engine is not available any more so I want to reload it.
    How can I do this?
    If I run the DLL again an error is occurred.
    Best regards,
    Nir

    Hello Nir,
    I recommend contacting MathWorks for assistance with the exact functionality and results of close all. Based on online documentation for calling DLLs in MATLAB, you should use unloadlibrary to remove the LabVIEW DLL from memory instead of close all. If you use this method, are you able to load the LabVIEW DLL (using the loadlibrary function) and call it successfully from MATLAB?
    MATLAB® is a registered trademark of The MathWorks, Inc.
    Regards,
    Andrew Brown
    Applications Engineer
    National Instruments

Maybe you are looking for