Lkstime.dll, labview 7.0

Hi, when I load labview 7.0, I have started getting the message:
"The application has failed to start because LKSTIME.dll was not found.
Re-installing the application may fix this problem."
Has anyone seen this problem before? What is has happened?
Before I go to the bother of re-installing everything, can someone maybe
email me the LKSTIME.dll file so I can shove it in and see if it works?
Thanks,
G

I couldn't find it in my LV directory (7.0). Could it have come from a module I don't have installed? Which modules do you have installed?
The DLL is probably located in one of the CABs on the CD of the owning software. I believe you can tell windows to search through the CABs, so you should look for it there.
However, it might be better (and even faster) to just reinstall, especially if you don't know where it should go. Also, instead of doing a full reinstallation, you can just do a repair (go to Control Panel>>Add and remove prgrams>>NI software).
Try to take over the world!

Similar Messages

Where does LKSTIME.dll come from?

Hey all,
I'm looking for what program provides LKSTIME.dll. I'm reinstalling a LabVIEW 7.1 application onto a new machine. I'm missing this .dll and looking for where this guy comes from. I see it's in i386 on my other computer.
Don

It seems like this dll is usually installed with Lookout or the DSC Module.
Matt J
Professional Googler and Kudo Addict
National Instruments

Passer un tableau à une dll labview

Bonjour
J'ai créé une dll labview avec une methode qui sert à passer un tableau de double.
Quand je passe mon tableau , j'ai une erreur memoire insufissante et ça ne fonctionne pas. je joints mon code et le projet de la dll
la methode : labview dll_tableau
le client de test pour la dll : test dll.vi
question annexe : comment fait on pour débugger une dll en labview?
Merci
Attachments:
test.zip ‏808 KB

Bonjour,
J'ai essayé de faire fonctionner votre programme. En appelant le programme test dll.vi j'obtiens bien une erreur de mémoire insuffisante. En revanche je ne comprends pas l'intérêt de la structure séquence, ni celui des différentes étapes. En n'utilisant uniquement l'étape n°2, cette erreur de mémoire n'intervient plus. Je n'ai pas été plus loin dans les tests. Aussi, à quoi de servent les différentes étapes de cette structure?
Bonne journée,
M-Junior

Error Building DLL, LabView 8.2

Hello everybody,
I'm building a
CVI application. I need some functions of LabView (related to time
series analysis), so I'm trying to build DLLs with the .VIs I need. I
followed all the steps necesary and visited all the related topics at
ni.com. I always get the following error:
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. +¡
Use the following information as a reference:
Error -2147221480 occurred at Building DLL stub.
This can be caused by illegal function or parameter
names. Please verify your names are legal C identifiers and do not
conflict with LabVIEW headers
This error code is undefined. No one has provided a
description for this code, or you might have wired a number that is not
an error code to the error code input.
Once, I got a correct DLL with no errors, so it should be possible for others.
This is an example of what I'm trying to compile:
And this is what appears, only for a moment, at the end of the
compiling (it didn't appear when I manage to build with no errors):
I'm using: LabView 8.2, LabWindows CVI 8.5, NI-DAQ 8.5, Windows XP (SP2)
Any suggestion is really appreciated.
Maybe another way to use this functions in CVI (I need functions related to spectral estimation, ARMA; MUSIC,...)
thank you!
Eduardo Tamargo
Spain

Hi Tamargo,
The following KnowledgeBases may help you find out what is happening:
Creating and Calling LabVIEW DLLs with Various Data Types from Microsoft Visual C++
What are the Differences Between "Array Data Pointer", "Array Handle", and "Array Handle Pointer"?
Calling a LabVIEW DLL from C with an Array in a Cluster as a Parameter
Have you tried developing a very simple VI with an array as an input parameter and checking if the same problem takes place when you build the DLL?
Regards,
David Oña

Parametre envoyé à une DLL Labview

Bonjour
J'ai créé une DLL sous Labview (5 Vi + 1 Global). Cette DLL ouvre un port de commication série (fixé à 1 pour l'instant).
Cette DLL est appelée par un programme tiers (BATEMC).
Elle est implantée sur plusieurs PCs différents sur lesquels le port Com à utiliser est différent.
Je voudrai passer en paramètre le N ° de port Com (1,2,3...) ou son nom (Com1,Com2, Com3...).
Pouvez vous m'expliquer comment reccupérer cette valeur ?
Merci d'avance pour votre contribution.
PS: Je suis débutant sous Labview

La ressource VISA à spécifier est polymorphe, et peut notamment être indiquée par une chaine de caractère. Après, on peut facilement étendre ça à d'autres possibilités avec les fonctions de formatage de chaines de caractères. Par exemple ici, l'option 3 montre qu'avec un type énum (ou entier!) on peut obtenir la chaine qui sera utilisée pour ouvrir une session VISA.
(Attention, il faut que la commande soit connectée au connecteur du VI et il faut l'exporter au moment de la création de la DLL pour que cela devienne un paramètre de fonction dans l'environnement d'appel).
Cdt,
Eric M. - Application Engineering Specialist
Certified LabVIEW Architect
Certified LabWindows™/CVI Developer

CALLING DLL: Labview or CVI?

I'm going to start a new project using Testand and Labview or CVI. In this project I will make a lot of calls to C++ functions packed at a DLL file. The Dll was prepared and compiled using MVC++.The function prototypes are not simple & contain structures, pointers and typdefs's.
Is it possible to call the functions from Testand,Labview,CVI?
Is it easier to call the functions from CVI compared to Labview?
Thanks,
Ofer

ofer_o wrote:
I'm going to start a
new project using Testand and Labview or CVI. In this project I will
make a lot of calls to C++ functions packed at a DLL file. The Dll was
prepared and compiled using MVC++.The function prototypes are not
simple & contain structures, pointers and typdefs's.
Is it possible to call the functions from Testand,Labview,CVI?
Is it easier to call the functions from CVI compared to Labview?
Thanks,
Ofer
Jon already mentioned that CVI will be a lot easier to deal with this than LabVIEW.
BUT!!! Make sure the DLL exports standard C functions instead of C++.
LabWindows CVI (and LabVIEW even more so) can only link to globally
exported C functions. C++ classes are completely out of reach for both
and C++ compiled global functions have both the problem of taking
sometimes C++ parameter types as well as the name decoration added by
the C++ compiler to all function names.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Passing booleans to LabView dll

I have created a Labview vi (7.1) that I have converted to a dll which uses a cluster of Booleans as a input. I set Test Stand (2.0) to pass a Structure (1 byte boundary) with Booleans as the data type (Test Stand also asks for a numeric type for some reason); is this the correct method? I get the message 'no type information in the dll' when loading the dll from Test Stand, is this normal for Structure/Cluster passing?

Hi Steve,
the No type information relates to the parameters being passed, so you have to make it up yourself in TestStand to match the setup you've given in LabVIEW when you built the .dll
LabVIEW packages booleans as U8's, so that's why it's asking for a number - there is no BOOL type itself - we address by byte only.
http://digital.ni.com/public.nsf/websearch/DBCE27265FFB554986256C9400026FE8?OpenDocument
This means that booleans are essentially a complex type, however useing U8s instead uses the same amount of space, and if you're not using clusters to simply keep them together, then you'll get prototype information out.
Useful other threads below :
http://forums.ni.com/ni/board/message?board.id=170&message.id=122260&requireLogin=False
http://forums.ni.com/ni/board/message?board.id=330&message.id=6140&requireLogin=False
Hope that helps
Sacha Emery
National Instruments (UK)
// it takes almost no time to rate an answer

Can not find size_t during import a dll and calling a function crash labview

Hello, experts
I need to use FingerLakeInstrument DLL ( see the attached) inside Labview to talk to a CCD camera. it is built from microsoft visual studio C++
I unzip FLI dll in my D:\proj\...\linfli-32 and import dll from there. created a c:\FLIDBG.txt as FLI dll needs to write debug message to it if FLISetDebugLevel() or others are called.
During importing the dll, first thing I got is <sys/types.h> ( ie size_t ) cannot be found. I have installed free version of microsoft visual studio C++
but can not find "typedef unsigned int size_t"
at the end, I just added
typedef unsigned int size_t;
in the libfli.h. Having done that, I am able to import all functions into Labview and have a user library called libfli.
However, as soon as I start calling a simple function in a test.vi, such as FLIGetLibVersion(char* ver, size_t len), which involves nothing other than the library, the labview will crash.
I created a simple C test.exe which calls many functions without any problem
any suggstion?
regards
xiaofeng
Solved!
Go to Solution.
Attachments:
libfli-32.zip ‏93 KB

Hi, Smercurio_fc
thanks for your reply. Yes, you are pointing to the right place. I have solved the crash problem.
when importing DLL into Labview using Tools\import\Shared Library (.dll), Labview automatically set the calling convention as C not as stdcall (WINAPI). it is this that later the labview crashes when a function is called. as soon as I manually re-selecte calling convention as stdcall, my test.vi works OK (see attached).
I tried Call Library Function too to call libfli.dll, as long as I select stdcall as call convetion. the test.vi works.
How do I know which Call convention I need to choose if there is no infomation from DLL provider?
as for the size_t,
I add #include <crtdefs.h> in libfli.h and
add additional include path as
C:\Program Files\Microsoft Visual Studio 10.0\VC\include. this solved the "not found" issue.
for this case I know that the DLL is built from VC++, is this right way?
again, thanks for your time.
xiaofeng
Attachments:
test.vi ‏13 KB

Calling 64-bit dll from labview 8.2 on Windows7

Hello,
I have tried the LABview driver from the OMNIDRIVER (OceanOptics) package. But when calling functions from the “OmniDriver32.dll” , LABView is crashing and says that the memory is corrupted.
I am using LABVIEW 8.2 (32-bit) running on Windows 7 (64-bit). I have tried some LABView code examples given for LABview 7.1 and 8.0. These example are using the OmniDriver32.dll (not the OmniDriver64.dll).
But maybe these example are assuming that you are on a 32-bit operating system, which is not my case.
So I have tried calling the OmniDriver64.dll. but LABView seems not to recognised the dll and can’t read the included functions.
Is there a way to call some 64-bit dll from LABview 8.2 ?
Or do I need to buy a new license for LABVIEW 64-bit ?
Thanks,
Pierre

There is no virtualization support for DLL bitness issues outside of the Windows standard directories. The Windows and System directories that an application "sees" depends on its bitness. All other directories are not mapped depending on the calling process' bitness.
So if you have installed 32 Bit LabVIEW and are not calling one of the system DLLs, you have to point the path of the DLL to the real 32 bit DLL. Pointing it to a 64 bit DLL should not even be able to get the VI compilable, since Windows will refuse to load the DLL into the 32 bit process as being an unknown file format, and that should make the VI broken.
If you need to call a system DLL you simply enter the DLL name without path and Windows will find the according DLL for LabVIEW.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Calling a DLL(with vi.lib) from a lvclass within a Packed library

Basically, I am having problem calling a DLL (which uses the vi.lib) from a packed library.
The error code I got is error code 1003. “Error 1003 occurred at Call Library Function Node in XXXXX.lvlibp”, “Labview: The VI is not excutable. Most likely the VI is broken or one of its subVIs cannot be located. Select File>>Open to open the VI and then verify that you are able to run it.   Create Summary Log.vi”
The VI that was mentioned above (Create Summary Log.vi) is one of the functions in the DLL that I am trying to call from the packed library. This VI modifies an Excel spreadsheet so it needs the vi.lib. In my DLL project, vi.lib is in my dependencies. When I compile my DLL, Labview will create four folders (NI_Excel, NI_HTML, NI_report, NI_Standard Report) at the build destination.
To problem happens when I run a Top level VI, which calls-> the lvlibp -> lvclass (within the packed library) -> DLL (uses the vi.lib Excel functions).
This problem doesn’t happen when I am not running the packed library (Only with the lvclass). So I think the problem is that DLL can’t access or find the vi.lib when it’s being called by the packed library. It seems like the packed library changes the way the DLL access the vi.lib.
Any suggestions?

Hi,
Thank you for your reply. Unfortunately, I think I might have provided wrong information. I thought the problem didn’t exist when I wasn’t running the packed library, but the truth is, the problem always exist regardless.
I would get an “error 7” when I created a simple VI that would utilize “Call Library Function Node” to call the DLL.
Error 7 occurred at Get LV Class Default Value.vi
Possible reason(s):
LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS X, and / on Linux. Verify that the path is correct using the command prompt or file explorer.
=========================
NI-488: Nonexistent GPIB interface.
Complete call chain:
     Get LV Class Default Value.vi
     NI_report.lvclass:New Report.vi
     Create Summary Log.vi
     Create Summary Log.vi.ProxyCaller
LabVIEW attempted to load the class at this path:
C:\XXX\XXX.dll\Excel\NI_Excel.lvclass
So the problem is, I don’t know how to include the NI_Excel.lvclass in my DLL. I didn’t have this problem back in 8.2, as I would just include a VI (with the excel VIs in the block diagram) in the project when I build it. This doesn’t work anymore as I am using 2011.

Memory leak in dll with an imaq-function

Hi,
I am currently writing a dll which uses the imaqImageToArray function.
Of course this function allocates new memory every time it converts a picture, and as I convert 180 pics a second and the Program shopuld run for hours that is quite a problem for me.
The solution should of course be the function free(void* MyPointer). And if I use malloc to allocate some random memory, instead of the imaqImageToArray, this works perfectly.
However when I call free() to release memory allocated by the imaqImageToArray function, the dll/LabView-Program will crash.
So I wonder what function the imaq-Functions use to allocate memory and how I can get rid of it again. Is there another imaq-function?
Thanks already!
Greetings
Solved!
Go to Solution.

Hi,
sorry for the misunderstanding. I use the imaqImageToArray function inside the .dll. The Code Hence is a c-code.
#include "extcode.h"
#include "nivision.h"
... some stuff/the dll-function etc....
uint8_t *Pointer;
Pointer = (uint8_t)imaqImageToArray(MyImage,MyRect,&Rows,&Columns);
if(Pointer!= NULL)
     free(Pointer);
... other stuff
Sadly I can't find a detailed description of the function. I assume the void* Pointer returned by imaqImageToArray points to an Array, however I am not sure wether it points to a usual c-array or a LabView Array, meaning:
typedef struct {
    int32_t dimSize;
    double Element[1];
    } LVArray;
That would explain why free(); won't work.
I think I got a step further though, as I found a function in the "extcode.h" called    DSDisposePtr(void *p). That should be the equivalent to free() for LabView Datastructures.
However even though I have included everything from the cintools directory explicitly to the project, the Linker complains about a not found externic object. Anyone knows which .lib files I need to include where to be able to use that function?
Thanks

Output on LabVIEW the TestStand step results

Hi,
I'm building on LabVIEW 8.5 a simple TestStand User Interface.
My sequences return some values but I don't know how to output them on LabVIEW.
I was thinking of a table to store the results.
Any hints on how I'm able to do so?
I apreciate all the help.
Thanks in advance.
Regards,
Daniel Coelho
Daniel Coelho
VISToolkit - http://www.vistoolkit.com - Your Real Virtual Instrument Solution
Controlar - Electronica Industrial e Sistemas, Lda

Use the TesStand ExecutionView Manager available in the TestStand tool pallet of LabVIEW and the Execution View. Then when you call our test code (dll, LabVIEW, CVI or what ever) and the return values are returned to the step.Result container based on the type of step. The ExecutionView Manager will automatically display the return value in the Execution View indicator on front panel, if it is a string, a number or a Boolean or etc.
Look at "C:\Program Files\National Instruments\TestStand 4.1\UserInterfaces\Simple\LabVIEW" as a starting point.
Notice that there is not any code that reads the return value from the test steps and displays it. The TestStand Engine automatically does it for you. Using the ExecutionView Manager and the Execution View, your LabVIEW user interface will not know when a test step is run or what the return values are without setting up events to trap UI messages from the TestStand Engine.
If all you need is to see the return value and results this is the way to go.
Omar

Prevent application from unloading dll

Hi
I have created an application that is made up of primarily two vi's, with one calling the other. The second vi, or the one that is called in turn calls/loads a dll. Now my problem is that before creating an application my vi's worked great since the dll did not get unloaded until labview was exited, however with the application it seems like if i close the second vi, or the one that calls/loads the dll then the dll is unloaded. Is there anyway to keep the dll in memory until the whole application is closed and not just the vi that calls the dll.
The solution I have used till now is to call the dll from both vi's but I rather not take that approach
thanks

reza_sed wrote:
Hi
I have created an application that is made up of primarily two vi's, with one calling the other. The second vi, or the one that is called in turn calls/loads a dll. Now my problem is that before creating an application my vi's worked great since the dll did not get unloaded until labview was exited, however with the application it seems like if i close the second vi, or the one that calls/loads the dll then the dll is unloaded. Is there anyway to keep the dll in memory until the whole application is closed and not just the vi that calls the dll.
The solution I have used till now is to call the dll from both vi's but I rather not take that approach
thanks
You don't need to call a DLL in order to have it in memory. As long as one VI in your VI tree has a reference to a DLL, and the according Call Library Node is not set to provide a dynamic DLL path (LabVIEW 8.2 and newer feature) that DLL stays in memory. No need to ever call that Call Luibrary Node. If another VI then gets into memory referencing the same DLL, LabVIEW will ask Windows to load that DLL too, but Windows seeing that the DLL is already loaded will only increment its internal load reference count.
So having a Call Library Node (or a subVI containing one) in your main VI will be enough to keep the DLL loaded. You can code something like where you put this SubVI in a case structure whose frame never gets executed. But do not disable that case by a diagram constant since LabVIEW will then optimize out the entire digram when you ever are going to build an application. Instead wire the case to a front panel control whose default value is set so that the frame will never be executed.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Error loading 'ole32.dll': Missing export '_resetstkoflw' from 'MSVCRT.DLL'

I'm getting the RT error:
Error loading 'ole32.dll': Missing export '_resetstkoflw' from 'MSVCRT.DLL'
LabVIEW RT 2011
I've reinstalled RT several times but am still seeing the error.
I only see it after closing my application.
I've attached a report of my RT system.
Any ideas on what I might be missing?
Robert C. Mortensen
Certified LabVIEW Architect
Certified LabVIEW Embedded Systems Developer
Endigit
Attachments:
ni_support.zip ‏1110 KB

Hello Robert,
I wasn't able to find too much about this error on our end, but doing a wider search it seems errors involving MSVCRT.DLL usually take place when this Microsoft C Runtime Library file is replaced by a third-party file that lacks "_resetstkoflwfunction". It's odd that the error occurs only after closing the application. Here is a third-party website I was able to find which explains this in a bit more detail, and might be a fix to try if your are comfortable: How to Fix Common Msvcrt.dll Errors?
Regards,
Deborah Y.
LabVIEW Real-Time Product Marketing Manager
Certified LabVIEW Architect
National Instruments

Imaq.dll error when boot up Windows

Hello,
I have a little Problem with Labview 8.6. After i installed the driverpack for the dvd, my Windows give my the error
Der Prozedureinsprungpunkt "ProgramFPGAs" wurde in DLL "IMAQ.dll" nicht gefunden.
my tranzlation
the entry point "ProgramFPGAs" is not found in the Dll " Imaq.dll
Labview start an run without problems, only this message at windows boot up is annoying.
was anyone a idea to fix the problem or atleast stop that messagebox
Thank you
Solved!
Go to Solution.

Hi DRhatje.
Good Morning and I hope your well today. Thanks for your post.
I think thats a pretty good translation, the error message I was thinking of can be found in the knowledgebase article below.
The suggested cause of the error is that the IMAQ.exe is set (by default) to start on startup. But if you don't have a framer grabber installed on the machine then you could well see this error. The solution is to remove the exe from the startup list on your system. The steps to do this is listed in the link below but in summary,
From the section in the screenshot you sent me you should be able to
select the "Selective Startup", then navigate to the "Startup" tab and
uncheck the IMAQBoot.exe.
If this reverts back to the default
settings on restart, this is probably an indicator that your Admin
Rights on this PC are limited.
I think that a quick way to check
this is to go to Start>Run and type "regedit". This is essentially a
more advanced way to manipulate similar settings, but if you don't have
Admin Rights on the PC then you would most probably be denied access.
In any case though, please ask one of your IT colleagues to use their
passwords and change this setting. It will get rid of the warning you
are seeing until you start using our Vision Hardware and need to
reactivate it.
Make sure you click on "Apply" before you exit this utility.
Why do I get "IMAQBoot.exe - Entry Point Not Found" error when I restart computer?
http://digital.ni.com/public.nsf/allkb/AD70B1036D5B950B8625752400578CFE?OpenDocument
This should at least remove the error message upon start up.
Please let me know how you get on and I hope this helps!
Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help!

Lkstime.dll, labview 7.0

Similar Messages

Maybe you are looking for