Kelli,
I will be using this sensor to check for the presence of orings while the test is running. All I want the camera to do is to sent the pass or fail to the labview DAQ so that it can stop the test if the o-rings is not present.
The rep told me it sends 0-24v signal.
Did you read any of the links provided? I think the last one by Electromecha looks pretty useful.
https://forums.ni.com/t5/ALARM/Arbitrary-Waveform-Function-Generator-w-DAQmx/gpm-p/3530726
Also you may want to start your own thread, this one stopped getting posts about 2 years ago.
That makes sense, however, I also have LabVIEW 2014 and the example is available with the toolkit installed. Examples have stayed fairly similar between LabVIEW version since LabVIEW 2011. If you can't find it through example finder, I have also uploaded it here for your convenience.
Thank you very much Ben.
Instead of word document, how do i save the file as PDF?
Regards,
S Nagaraju
Hi Ujangsan,
I'm using 'Write to Text File Function' to log data. … directly logging it to binary text file.
What kind of data do you want to save?
Why do you use a TEXT file function to save BINARY data, when there is a "Write to Binary File" function?
So I saw hexa data, some bytes are written differently from received data.
Yes, that is because YOU have the file function configured this way.
Please read the help for WriteToTextFile to understand why and how this is happening!
tyk has already explained it to you. Basically you can't just go and create renamed copies of DLLs to manage multiple resources unless the DLL is specifically written to do so. But it would usually be more straightforward for a DLL developer to actually write the DLL in such a way that it can access multiple devices at the same time by implementing a session based device handling where the user passes a refnum or handle of some sort from function to function and the DLL manages all the information including the device state to communicate with a particular device.
If the programmer found this to cumbersome he most likely didn't care either about making sure that two different instances of the DLL would not stomp on each others feet in some way.
And managed (.Net) or unmanaged doesn't really matter in this case, both could be written in such a way that they stomp on each other in some ways, for instance by accessing a secondary low level driver library that does not protect the global communication resource (bus, interface) in a proper way with locking.
That it doesn't crash when you have the front panel open is most likely a red herring. It still somewhere somehow corrupts memory but not memory that is crucial to LabVIEWs operation at that time. By opening the front panel LabVIEW needs to allocate more memory to manage all the front panel resources and such and that changes the actual memory layout of the whole process significantly enough that your misbehaving DLL stomps somewhere into memory where it doesn't immediately lead to a crash. It still will eventually crash somewhere, for instance when you try to close the front panel or maybe when you try to close LabVIEW itself and it tries to clean up everything and stumbles over corrupted memory pointers that your DLL caused.
Hi Milleh,
your data file is SPACE limited data - but worse as it uses multplie spaces between data elements…
I could plot X vs Y like this:
Read the text file, convert all multiple spaces into single ones, convert to array data, get rid of the header and the first column (due to lines starting with SPACE chars), choose two columns to plot as XY plot…
Hi Hamster,
just because I'm curious: Which datatype do you use to hold this "80-bit signed number"?
T hank you but I dont get any error, the application cannot simply connect to the database.
I made sure that relative path is ok and both servers use different ports, but still cant read from and write to the database.
Thanks again!
Thirst thing today i will contact them and hope they respond quickly.
as im not that expirianced with programmin, making my own .net isnt the best idea i guess :/
also i will try to add a delay.
i dont want to bore you too much with this but if you have time the other day would you take a little glance inside the dll for me? maybe im just to focused on something that i oversee the little thing that would make the differnce.
appreciate your help big time!!
Hi;
my project is to build [4QAM] transmitter and receiver to transmit a text using labview comms and USRP RIO 2952,I already made this step, but my question is that:
(1) how to use the FPGA host interface to communicate between the host VI and the FPGA VI.
thanks a lot,
Hi Doha,
LabVIEW comes with a lot of example VIs and projects.
In those examples you will also find explanations on communication between host VI and FPGA…
Hi ! I hope someone could help me !
I am trying to open a connection with a computer which IP adress is
10.4.1.114 via UDP. I configured the IPv4 address of my laptop to 10.4.1.33
coupled with the subnet mask 255.255.255.0 to connect to it.
I am running the VI on Labview 2014 SP1 (32-bit) on Windows 7.
However, the message can't be reached by the other computer because there is an issue with the first function : Open UDP VI. I tried several configurations on the VI (wired/ignored some optional input/outputs & run the VI on laptop or CompactRIO 9064) and I had all the time the 3 same errors depending on the situation.
Error 1 : input parameter invalid
Error 54 : ill-formed network address
Error 60 : specified port/network address is currently in use
First, I made the VI on a project directly running on laptop. But it gave the error 1 when I wired the optional port output or the error 54 when I ignored it.
Thinking that it could be an issue about the laptop who could not have access to the other computer, I tried to implement the VI on the cRIO (IPv4 address : 10.4.1.235, connected to the private network of these computers). I also added SocketSetReuseAddr=TRUE to LabVIEW.ini. and disconnected from networks which could be damaging the communication.
When I did that, on the VI running on cRIO, I got the error 54 when I tried to run the VI with the net address input wired or the error 60 when I ignored the net address input.
To sum up, I got these issues in these contexts:
VI running on laptop + net address input wired + port output wired => error 1
VI running on laptop + net address input wired + port output wired => error 54
VI running on laptop + net address input wired + port output wired => error 1
VI running on laptop + net address input wired + port output wired => error 54
VI running on cRIO + net address input wired + port output wired => error 54
VI running on cRIO + net address input wired + port output wired => error 54
VI running on cRIO + net address input wired + port output wired => error 60
VI running on cRIO + net address input wired + port output wired => error 60
I don''t get why I got these errors in these configurations. What differences could it make to run the VI on a project on laptop or on cRIO ?
In every configuration though, I succeeded to ping to the other devices (cRIO and the other computer)
Thank you for your help !
Thank you tyk, rolfk.
tyk: I'll try to share the DLL source-code (which I inherited).
The (Win32) DLL interacts with a removable USB drive. Actually it's not a drive, it's a camera/PCB with USB port, but the people who developed the device and firmware built the API around the removable-drive interface (instead of an HID or VCP interface).
Based on your comments (tyk/rolfk), I'll look for some step that might share a resource with another DLL/copy running within the same (LabVIEW) process-space.
By the way, the error code is 0xc0000005 and it can occur about 8sec after initializing the DLL (while sitting at the breakpoint).
Thanks again!
billko wrote:I usually use a cluster of Booleans instead of an array.
So how do you get from a number to a cluster? Or do you use number to Boolean array and then array to cluster? Especially on an FPGA I'd avoid clusters and arrays (again, no idea if this is grounded). On a PC it isn't a bad idea.
hichem55 wrote:T hank you but I dont get any error, the application cannot simply connect to the database.
So the connect, the read and the write VI's don't return errors? They just don't work?
Note that the executable will not automatically pop up error dialogs, like the dev. env. You'll need to add a simple error dialog VI somewhere to get an error dialog.
PriyadarsiniS wrote:Can you define this with an example program, am new to using Dynamic data member accessor concept in LV-OOP's.
Where did you get the "Dynamic data member accessor concept" from? I don't think there is such a think. There's a "Data Member Access" concept, and there's a "Dynamic Dispatch" concept and a "Static Dispatch" concept.
Simply make a class and a child class. Add a Dynamic Dispatch VI to the parent, and find you can add the same VI to the child.
Add a Static Dispatch VI, and find you cannot add this VI to the child.
I personally never use "Data Member Access", at least not by using the option LV provides. I simply make a new VI (method). Like I said, a data access VI is a method. It's very confusing that you can make this method visible as a property node.
THANK YOU VERY MUCH !!
Following your advice I have reached my goal !
Your helps been very useful for me.
Luca
hi
thanks a lot for your help ,but I am not perfect in labview comms,just a beginner so would you mind guiding me to this material?
Hi Doha,
to start an example project select "File -> New…" in the menu to open a dialog with lots of predefined project templates. There are also Realtime and FPGA projects…
To find example VIs select "Help -> Find examples…" in the menu to open a dialog with lots of example VIs sorted by topic…
NI also offers tutorials like this one, just search for "realtime fpga labview"…
