LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LabVIEW function that gives the current free RAM?

That sounds like the Call Library Function didn't load up properly, and sending you a LLB won't make a difference. Instead, I'm including screenshots of the VI. It's quite simple, as it just uses the Call Library Function Node function:


Attached are also pictures of how to configure the Call Library Function Node function.


Message Edited by smercurio_fc on 05-14-2008 01:13 PM
Download All
Message 11 of 16
(1,062 Views)

Thank you very much for the detailed information. Do you think this DLL will work with an older version of LabVIEW?   I'm using LabVIEW 5.1.

If it is not a problem, can you send me the DLL file itself?

0 Kudos
Message 12 of 16
(1,040 Views)
You never said you had LabVIEW 5.1. That's important. Smiley Wink

The VI I provided was in 8.2. That was why you couldn't open the file. I have no way of backsaving to 5.1. Sorry. Maybe someone who has all the necessary versions of LabVIEW can backsave to 5.1.

While 5.1 allowed you to call library functions, the details are a little different. Also, I don't recall the exact details of how to handle clusters with DLLs back in 5.1. You will need to check the LabVIEW documentation and the Knowledge Base on the exact details.

There's no need for me to send you the DLL - it's part of Windows.
0 Kudos
Message 13 of 16
(1,032 Views)

The dll is here in ur system

c:\windows\system32\kernel32.dll

Mathan

0 Kudos
Message 14 of 16
(1,028 Views)
FYI: The exact path isn't required as long as the DLL is registered. In this case you only need to put "kernel32.dll" in the "Library name or path" textbox.
0 Kudos
Message 15 of 16
(1,024 Views)

It is working with LabVIEW 5.1 too!

Thank you very much!!

0 Kudos
Message 16 of 16
(1,011 Views)