Memory problem then I import a DLL on LabView 2010

[Nicolas.G]

Hello,

I have many problems with the importation of a .dll on labview.

The importation blocks at the third of fourth function, and sometimes a textbox appear (as you can see in attachement).

I tried with the import node, but it doesn't work (so, it's maybe that I don't know how to use it really).

I don't know really how to import the whole library, and I am really blocked.

There is the header and the dll in attachment too.

Thanks for your interest.

[Nicolas.G]

No idea ?

I try to find a solution, but I am really blocked.

[Jean-Philippe_C]

Hello Nicolas,

I tried to import your dll/.h on my side with LabVIEW 2010.

I have the same behaviour except the memory issue. I am wondering if it wouldn't be a problem during the dll creation.

Do you have the possibility to re-build your dll or does it comes from a third-party?

If yes, maybe this document could be useful:

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000x1OvCAI&l=en-US

For your memory problem, try this:

http://zone.ni.com/reference/en-XX/help/371361G-01/lvhowto/enable_lrg_ad_aware/ 

Regards

[Nicolas.G]

Hi,

I think the page on "how to extend the memory" will could be helpfuld. But i already read it, before, but there is only 1GB of RAM, the manipulation is useless, isn't it ?

It's impossible to rebuilt the dll, I think. It's from the company, but the it was coded by a developer who is no longer in the company, now.

And I think that they don't build another dll soon.

The problem you nust have is maybe because you need another dll, I bring them in attachment.

If you want, I posted on the Labview France thread (si jamais tu prefererais en parler en francais ; )

Thank you

[Nicolas.G]

So, I did that it said on the memory page, and I still have the same problem.

I don't know wht to do more.

[rolfk]

---

@Nicolas.G wrote:

So, I did that it said on the memory page, and I still have the same problem.

I don't know wht to do more.

---

While that DLL API does not seem to contain anything that couldn't be done in LabVIEW without intermediate DLL, it is extensive, with quite a few functions and very complicated structure parameters. This would be even for me QUITE a bit of work and sweat to get a fully working LabVIEW interface for it, and I'm not surprised at all that the import library wizard can't really make it work without problems. I would likely have to create several trial and error versions myself for some of the API functions before it would likely work.

Without wanting to discourage you, unless you have LOTS of C programming knowledge, this is never going to work without errors. You may eventually get to a stage where you do not appear to get any errors anymore, but that will absolutely not mean that you are not still corrupting memory by misconfigured parameter types or misallocated memory buffers.

My advice is simple: Avoid this hardware by all means! It will cost you in the end more money, sweat, blood and sleepless nights than the most expensive alternative solution with ready made LabVIEW drivers ever could! And I'm not kidding here! Unless you want to take this as an opportunity to get VERY VERY intimate about C datatypes, C programming in general, and how C compilers arrange data structures in memory! Many of these things are not even known to good C programmers.

[Nicolas.G]

Ok, thank you for your honesty. It has the merit to be clear.

So, I am not a boss of C programming at all, and it's not the goal of my work.

But, if it is not possible to importe a driver from this DLL, how could I to build it ?

I am a bit wasted.

Thank you again for this explanation.

[rolfk · Accepted solution]

I didn't say it's impossible, but it is very likely way above your head. You have probably two options:

1) Abandon this hardware and get some that has proper LabVIEW support.

2) Hire someone with a very good understanding about LabVIEW to C interfacing and let them create a VI library and interface DLL for you.

Good luck