I have a DLL I created (in Labview) that takes in string information, does some magic crunching on it to create a password that is passed out as a string. This DLL will be called from CVI and probably from a C# application.
This should be so simple, however I cannot figure out how to pass the string in and get the modified string out of my DLL.
I've had no luck at all getting this DLL to work by trying many different things. It crashes LV, returns and error, or simply passes nothing out during my trials.
I've included the project (its small) in zipped format. Can one of you kind souls take a look at my code and tell me what I'm doing wrong, or what I need to do correctly to both, configure the DLL and then call it from LabVIEW?
I am able to read HEX file into Labview using read from Text file..I am getting data into labview in terms of string.
Problem => Now i want to load this HEX file into microcontroller using VISA-rs232 .Is it require to further conversion or i can load HEX file(in form of string) directly into microcontroller ?
I need a little help.
I want to send from LabVIEW to Arduino via serial port the string for example "ABC" and so on.
The problem is that when I send the string from LabVIEW .......the Arduino do nothing. Sometimes shows some kind of sign.
When I send the string via Visual Studio it works perfectly.
Is there someone who can help me.
I attached picture of vi and Arduino code
Thank you very much.
I've got a 3rd party DLL I call from within my application. One of the functions returns a pointer to a variable length null terminated string. I use the mysterious GetValueByPointer.xnode to dereference the string and return it's value. This works great from within the Labview development environment. I'm using 2013Sp1.
But when I compile the application into an executable, the xnode returns an error 7. It appears the DLL is returning a valid pointer, but the xnode can't dereference it. My hunch is that the pointer is crossing some kind of protected boundary, but I don't know for sure.
I suppose I could write a wrapper around the DLL call, but I really don't want to have to do that if there is a simple workaround. Any ideas?